Autoloader dev Alpha 10.0.9.1103 (Windows).

Is there a chance that I can get the autoloader of Alpha Dev 10.0.9.1103 for Windows? Since I've upgraded to the new version... my camera died!

https://developer.BlackBerry.com/Native/downloads/FETCH/autoload-DevAlpha-10.0.09.1103.exe

Tags: BlackBerry Developers

Similar Questions

The skin lack of asset Classes after Dev Alpha update 10.0.9.1103

Ouch, last night I presented version of my app BB10 - this morning I am updating my Dev Alpha and the app works more... :-(

It seems that the problem is with some qnx.fuse.ui controls:

When I create a drop down list I get this error:
```
Error: Skin Asset Class with identifier scroll_bar does not exist!
    at qnx.fuse.ui.theme::ThemeBase/getSkinAsset()[E:\hudson\workspace\BB10_0_09-AIR_SDK_API\src\qnxui\src\qnx\fuse\ui\theme\ThemeBase.as:67]
```
And for the SegmentedControl of it:
```
Error: Skin Asset Class with identifier segmented_control_background does not exist!
    at qnx.fuse.ui.theme::ThemeBase/getSkinAsset()[E:\hudson\workspace\BB10_0_09-AIR_SDK_API\src\qnxui\src\qnx\fuse\ui\theme\ThemeBase.as:67]
```
I updated to beta 4 of the SDK and checked that qnx.fuse.ui.skins.QNXSkins is packed.

My own code is no not no matter what count, I was going to just to use the default value.

Does anyone know what I can do to fix this?

Anna

My app: Get set - get up! Get ready for the revolution snooze.

Inspired by a known issue with 64-bit Win mentioned in the release notes for the beta 4 SDK, the DONKEY just removed from the packaging and the path of construction, cleaned the project and added fees (4.6 FB) - and now everything works!

(Note that my previous SDK installation has been at the same location as new and my path to the donkey was exactly the same as it is now, in C:\Program Files (x 86), so if anyone has weird questions it might just be useful to import donkeys even if files program Program Files (x 86) vs problem described in the release notes does not apply.)

My app: Get set - get up! Get ready for the revolution snooze.

After wiping Dev Alpha, it gets stuck

I recently installed the updated BB10 with the hub. I found that something was wrong with the update that I couldn't connect to BBID little matter what I tried. So, I did a cleanup of security of the device.

Now when it restarts, it shows a litte with a USB phone to a computer. When I plug it into the USB or the phone or the computer acts as something that happened.

If I don't touch it, the dev alpha turns off, then when I turn it on again, same thing the usb screen. I need to finish a few apps and test them, I don't know what to do. Can someone help me?

The automatic charger for Windows and connect the device to the computer windows using a US cable. Run the automatic charger. It starts by itself. If this isn't the case, keep the button of the unit alpha dev for at least 15 seconds.
The autoloader should now be able to connect to the romantic boot and start updating your device and wipe all content.

BlackBerry 10 Dev Alpha is not updated to 10.1 to 10.2

I'm trying to update my device BlackBerry 10 Dev Alpha OS 10.1 to 10.2. I'm refernce documentation for it. I downloaded Autoload-DevAlphaC - 10.2.0.1157.exe try to update. But the command line stops without updating. Then I tried with loading auto-DevAlphaA_B - 10.2.0.1157.exe. Here he updates without any error in the command line. But the device does not start after that.

Then, I go down to the previous version of the OS using the load auto-DevAlphaA_B - 10.1.0.1485.exe. Now the unit start with OS 10.1

Why is this happening?

I don't think that Dev Alpha (A) could be upgraded to version 10.2. I have tried both official and leaked OS but neither can start the device again. So currently my Dev Alpha holds only still 10.1.1485.

If you really want to try 10.2, try using Dev Alpha B/C or official Z10/Q10.

The driver installation failed BlackBerry Dev Alpha 10

When I plug my dev alpha bb10 into my computer, it says driver installation failed. Office software Blackberry cannot pick it up. What should I do?

Try going into the menu alpha dev (small gear top-right). Go to storage & sharing. Set the «Connect to Windows» USB connections

Who can help, mines on auto and never given trouble. There's a first time for everything.

"Security error" loading 10.2 beta on Dev Alpha

Hey guys!

I get a "security" error when loading the OS to the Dev Alpha 10.2 beta and my BURNING device keeps flashing. I downloaded the automatic charger more than 3 times just to check if my autoloader has been altered only.

No work around for this problem? I'd appreciate your opinion! Thank you!

You can load 10.1 to fix June 30 of the error. Get it from this page: update the software of the device BlackBerry 10 Dev Alpha

Please send this error that you are getting the upgrade from 10.2 to [email protected], which can help you.

BB Dev Alpha - another problem after security wipe

Initially, the unit has lost ability to connect on the computers (it's not recognized on any computer to which it was connected).

So I decided to do a security wipe. After the wipe whenever the phone tried to load the operating system, the progress has reached 100% and stopped. I downloaded the autoloader driver DevAlpha A / B 10.1.0.1485 and tried to reinstall the operating system with its help, but he refused to install with error messages "OS is not material", "this file does not match the device. Then, I downloaded an older version of dev alpha drivers (DevAlpha 10.0.10.263 autoloader), but he got the same errors.

After updating these attempts of the device reached the start progress 100%, then restarts, once and once more. Software link cannot start the firmware recovery process. It is also interesting that the device hardware ID is not listed here.

I have read a number of topics dealing with similar issues of DevAlpha on the support forums, but some of the solutions are outdated and others do not work for my device. Can someone give advice? Thank you

P.S. here is the log of 10.1.0.1485 driver:

C:\Downloads\Programs>Autoload-DevAlphaA_B-10.1.0.1485
RIM Wireless Device Command-Line Auto-Programmer Version 3.10.0.29 (Win32) [Apr
 1 2013 19:59:10]
Copyright 2012 Research In Motion Limited

Connecting to Bootrom:
Resetting Device: Connected

[       Uploading RAM Image 0x80238984 ] [############## 100 ##############]

QCFMv1/v2 Hybrid File
    containing: Radio

    Signature Trailer:
       EC521_512 Signer: 0x48584E51 (QNXH-OS-1)
       EC521_256 Signer: 0x4C584E51 (QNXL-OS-1)
[                  Writing  0x006E0000 ] [############## 100 ##############]

QCFMv1/v2 Hybrid File
    containing: IFS, OS, User File System

    IFS/OS Version:        10.1.0.1485 DEV
        Hardware ID:       0x06001A06 RIM BlackBerry Device
        Metrics Version:   3.18
        Build Date:        Apr 13 2013
        Build Time:        10:23:20
        Build User:        ec_agent
        STP Protocol Ver:  0.0.4 (release OS)

    Signature Trailer:
       EC521_512 Signer: 0x48584E51 (QNXH-OS-1)
       EC521_256 Signer: 0x4C584E51 (QNXL-OS-1)
--> OS does not match hardware. (C: 0X06001A06 H: 0X8500240A O: 0X051D0001 )

Error: Failed to load images.

Error: This file does not match this device!

And here is the log from 10.0.10.263:

C:\Downloads\Programs>Autoload-DevAlpha-10.0.10.263.exe
RIM Wireless Device Command-Line Auto-Programmer Version 3.10.0.15 (Win32) [Dec
20 2012 22:31:59]
Copyright 2012 Research In Motion Limited

Connecting to Bootrom:
Resetting Device: Connected

[       Uploading RAM Image 0x8022E584 ] [############## 100 ##############]

QCFMv1/v2 Hybrid File
    containing: IFS, OS, User File System

    IFS/OS Version:        10.0.10.263 DEV
        Hardware ID:       0x06001A06 RIM BlackBerry Device
        Metrics Version:   3.18
        Build Date:        Jan 27 2013
        Build Time:        11:33:05
        Build User:        ec_agent
        STP Protocol Ver:  0.0.4 (release OS)

    Header Version:        2.0
       Num Chunk Headers:  6
       Headers Length:     65120

    Chunk Header:
       Type:          0x06
    Chunk Header:
       Type:          0x08
    Chunk Header:
       Type:          0x06
    Chunk Header:
       Type:          0x05
    Chunk Header:
       Type:          0x09
    Chunk Header:
       Type:          0x89
    Signature Trailer:
       EC521_512 Signer: 0x48584E51 (QNXH-OS-1)
       EC521_256 Signer: 0x4C584E51 (QNXL-OS-1)
--> OS does not match hardware. (C: 0X06001A06 H: 0X8500240A O: 0X051D0001 )

Error: Failed to load images.

Error: This file does not match this device!

This means that you run z10 full os on your alpha dev b. To correctly flash has another version to it, make sure you download Z10 STL100-1 automatic loader, no Dev Alpha B one.

WebWorks app no longer works after update of Dev Alpha

So I tried to transfer my playbook to the BB DevAlpha application and it worked very well mostly on the alpha of dev, but since the update, I can't open up my application. It will open to a blank black screen just and do nothing at all. In closing, I get an error: "application does not handle the message 'Quit' and was slayed. It seems that the app is the gel, but it could also simply not start at all.

Nothing appears in the web Inspector, so I think that it is not starting.

The app was developed originally on the playbook in which she worked well, he also worked for the most part very well (with the exception of a question of content layout) on the BB Dev Alpha of the original OS. But after the update of the OS. It doesn't seem to work at all.

So I am really confused as to why it suddenly stopped working.

What is wrong with him?

Read this:

https://developer.BlackBerry.com/HTML5/documentation/getting_started_with_bb10_ww_sdk_2007056_11.htm...

For each web page in your application, you must include a script tag that links the webworks - version > .js file:
You must copy the webworks - version > file .js in your application. Make sure that your application uses the version of this file that corresponds to the current version. You can find thewebworks - version > .js file in one of the following locations, depending on your platform:
- Windows XP: C:\Program Search SDK WebWorks Motion\BlackBerry 10 version > \Framework\clientFiles
- Windows 7: C:\Program Files (x 86) \Research Motion\BlackBerry 10 Development Kit SDK WebWorks version > \Framework\clientFiles
- Mac OS: Developer/SDK/Research In Motion / BlackBerry WebWorks SDK 10 version > / framework/clientFiles

BlackBerry Dev Alpha insists the point on the Bluetooth connection mode.

Hello.

I tried several times updated BlackBerry Dev Alpha to the new firmware with the instructions on the website to update. Make sure that all the steps I did. I have tried but no luck. Desktop software did not update. I tried the troubleshooting, but I couldn't find any chance to try several times and it get messages that he has made available.

I clicked on update and repair. When you click Repair, no fading, rather office continue to find the update software and finally sometimes found. When it concluded, Office Automation application password for the bluetooth connection (I'm sure bluetooth was disabled on device and my laptop) and it continued just as the device was only pretending to be connected with bluetooth. Then it starts to download. But even once, it never ends.

I already have:

> Remove the registry as indicated

> set the USB for windows

> enable development mode

> set file sharing on

> run the troubleshooting steps.

No luck, I found . Everyone knows the same symptom?

Yes of course. My Dev Alpha is updated at the moment. Even though she insisted update on Bluetooth connection mode, when install just re - check again if the connection is available and I just reconnect the device to continue the installation.

Script to change the element using screen orientation does not not on Dev Alpha in Portrait mode

OK, so I wanted to update my application WebWorks Testing (https://github.com/SCrid2000/WebWorks-Testing) to make it easier to test webworks apps for the difference in screen resolution between the Alpha of Dev and the 10 next of BlackBerry.

Basically, instead of opening your html, js and css files directly in the test application, the update would be to open your files in an iframe in the app. The iframe will resize itself based on the orientation of the device.

The javascript function looks like this:
```
function displayCurrentOrientation() {

    if (window.orientation === 0) {
        document.getElementById("currentOrientation").width = '1280px';
        document.getElementById("currentOrientation").height = '720px';
        return false;
    }
    if (window.orientation === 90) {
        document.getElementById("currentOrientation").width = '720px';
        document.getElementById("currentOrientation").height = '1280px';
        return false;
    }
    if (window.orientation === 180) {
        document.getElementById("currentOrientation").width = '1280px';
        document.getElementById("currentOrientation").height = '720px';
        return false;
    }
    if (window.orientation === -90) {
        document.getElementById("currentOrientation").width = '720px';
        document.getElementById("currentOrientation").height = '1280px';
        return false;
    }
}
```
Now it works just perfect on the PlayBook (but of course, this isn't much help for the screening of the BB10)

However, on the Dev Alpha it ONLY works in the LANDSCAPE; in other words, if the application is launched in the landscape, the iframe rezises and everything is just perfect. If the test application is started in portrait mode, the iframe is still resized to the size of portrait.

Anyone have any suggestions for what I'm doing wrong? I am quite at a loss here (and since this is a free application and open source, I'm not too motivated to spend another couple hours trying to fix lol).

Thank you.

Shane

Nevermind, turns out it only is not yet supported by BB10.

The size of the screen wrong (Dev Alpha)

OK - I have this

A Dev Alpha is 1280 x 768 - I trust the source of this info (BB guy)

Try something silly like that...

Alert (window.innerWidth + 'x' window.innerHeight);

I get the numbers - gimme a sec...

Thing stupid password

570 x 342

Huh?

Hi, I had the same problem. You must add the following:
```
 
```
Source: http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/How-to-set-up-the-viewport-for-a...

Have a great day!

Blocked dev Alpha B PIN device

My Dev Alpha B has been blocked recently. I already wrote several times to:

[email protected]

[email protected]

[email protected]

[email protected]

Especially I have not yet received response. [email protected] guys have even asked to confirm if the device is still blocked but then he stopped also reply on my email. Can someone help from Blackberry, please?

[email protected] finally unlocked it

Impossible to test in app dev alpha A

Hello

I need to test in-app on my alpha dev A. I purchase followed all of the steps for testing in sandbox mode. But when I try to add the release that it does not show the option for alpha dev and so I get the "Not available for this device" message when trying to download app on app World sandbox mode.

I need to test in-app. How can I do?

I've just loaded Alpha-A Dev with the last external beta, 10.0.10.263 and was able to find and install downloaded applications only for Z10 models that dev Alpha was not as a device supported successfully.

After making the changes on the supplier portal, it may take up to 6 hours for those on the device because of caching.

installation bar on Dev Alpha: 810/var/tmp/bar_665560 failure: cannot access the Member "META-INF/MANIFEST. MF'

Can someone tell me what in the world does that mean? Get this error when trying to install my application signed my BB10 Dev Alpha device. This error is new to me.

I troubleshoot-made with Marco a little offline time. Here were the issues being not package and deploy properly, I hope this will help others as well in the future.

The problem was just a few things.

Config.Xml

-Lack of ownership application in the widget element ID
```
http://www.w3.org/ns/widgets"
      xmlns:rim="http://www.blackberry.com/ns/widgets"
        version="2.0.0.0" id="your_app_id_goes_here">
```
Index.html

-Lack a script include. I always use the Web Inspector Network tab to make sure all my includes load. It's amazing to see how many times I did it personally

-Lack of script include the WebWorks JavaScript BB10. Don't forget with BB10, we include this

-Missing "webworksready" event listener. In the case of Marco, that didn't alter his app, but we must wait for this event before calling WebWorks API now.

Practical links

Example of file config.xml blackBerry 10

https://developer.BlackBerry.com/HTML5/documentation/code_sample_creating_a_bb_widget_config_documen...

Examples of 10 blackBerry applications

https://github.com/BlackBerry/BB10-WebWorks-samples

Dev Alpha Red LED flashing (10111011) after update 10.0.6.545

I upgraded my Dev Alpha 10.0.6.545 today and after the update has been done the WiFi is connected but when I tried to browse it wasn't working, so I decided to restart the device to see if, after this, it would work. When I tried to turn on the red light started flashing on the next in the sequence 10111011. I tried to repair the unit by using the Software Desktop 2.4.0 (version 16), which is the same one I used to update the Dev Alpha.

He began to download the firmware to fix the device, but when it finished and started to install it collapsed it and wasn't moving forward for ~ 1, then I removed the unit and tried again (3 times) and it's the same thing.

Any ideas?

Seriously guys, 10 is my new lucky number. On the 10th try to repair it it fixed within 10 minutes.

You must be persistent for Dev Alpha updated to work as much as I've seen it here by searching on the forums... haha

Autoloader dev Alpha 10.0.9.1103 (Windows).

Similar Questions

Maybe you are looking for