Dev Alpha to death after wipe

Similar Questions

• 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.

• 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

• 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.

• 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

• Dev alpha may not work after update to OS10.0.6.386

  Hi all. It seems that my alpha dev cannot restart after the update. It takes 2 hours to restart, but failed. How could I solve this problem?

  Revive my dev alpha (which means alpha is turned off or has not started):
  1 disconnect the alpha of the PC
  2. start DM BB 7.1
  3. connect alpha PC
  DM BB cannot communicate with the connected device.
  Note: This will be auto-start your device. Can take up to 20 minutes if the 1st reboot.

  If you have successfully updated to R6, click Cancel.
  Otherwise, click Update, followed by repair, etc.

  On DM, click on connect to the device (status bar below on the right).

• Video HTML5 don't play online on Dev Alpha after update to 10.9.9.339

  Dev Alpha used to play HTML5 videos inline (similar to the PlayBook), which has helped some cool design if you were paying attention.

  After the update to 10.9.9.339 videos are no longer play online (the device trying to play their full-screen and displays the video controls even if it has not been specified according to the HTML5 specification), and the layout is broken.

  I wasn't able to find a way to force videos to play online as before, nobody knows how to do this on a device BB10?

  Here is a simple example of HTML code:

  
    
  

  Grateful for your help!

  Check out this thread:

  http://supportforums.BlackBerry.com/T5/Web-and-WebWorks-development/HTML5-video-issue/m-p/2085959/hi...

• Strange behavior of audio subsystem after update Dev Alpha 10 to 10.0.9.388

  Hello world!

  Has anyone noticed a strange behavior of the behavior of 10.0.9.388 audio subsystem firmware. Recently, after firmware update Dev Alpha 10 to 10.0.9.388 subsystem audio misbehavies in the following way:

  (1) if the external headphones/speakers connected to the audio line-out looks to be preprocessed by low-pass filter and surround effect. The device reported by AudioManager is/dev/snd/pcmPrefferedp. Would it be a bug in formware and re-routing audio internal speaker to the line-out socket did not exclude specific pre-treatment?

  (2) on the previous firmwares if audio goes out of the internal speaker and then the helmet is connected to Jack line out change of itinerary was seemlesly happening and he kept playing with headphones without additional measures in the application. Now, peripheral audio is not consume audio samples and so crashes until it is closed and reopened.

  On the previous firmwares were not all the problems of this kind. Would be - what a few unlucky flashing firmware try (if it is still possible) or bug of 10.0.9.388.

  It will be good to hear comments & thoughts about these questions.

  Best regards

  Dmitry.

  I suggest to create two entries Issue Tracker: https://www.blackberry.com/jira

• 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.

• 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.

• BlackBerry Q10 Dev Alpha C - stuck on "essential gestures."

  Hey guys,.

  I accidentally placed an emergency call after loading the last 10.3 OS on my Dev Alpha C through the tutorial from gesturest. He asks me to swipe down from the top where the only option is 'emergency call '. I don't see a way to pass the tutorial of gestures to extinguish the GMS. Can someone help me out here?

  Okay, it looks like I had to do a battery pull and then just keep tapping the button 'try '. Finally he moved me to a screen where I could slip into an application and tutorial actions. Huge PITA, but I hope I am the case of edge here.

  Rion

• 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.

• BB10 dev alpha - stuck in Configuration - does not load the license agreement (r2320)

  I successfully upgraded Dev Alpha A 10.0.09.2320 with automatic charger.

  Device, rebooted, installed new drivers, etc etc, all the other things worked well, BUT

  The device is unable to complete the installation, because it gets stuck on the license agreement page.

  I am connected to wifi. The wifi works. It's worked before. It won't let me even to select a country, it shows an error that the network does not, repels me a page, and I have to disconnect / reconnect to wifi before it allows me to 'sweep left to continue' again.

  Any suggestions?

  I managed to make it work by (sigh) with the help of roaming data connection (after restart). Now it is stuck on the screen of a software update. He has rightly "Software Update" and nothing else on the screen. The Act of working is the Emergency call.

  Update: after another reboot, after you turn off roaming data once again, it gave me an option to start or turn off the phone, but it says something about "blackberry infrastructure? Does this mean that it will work only with BlackBerry Internet Service in the future?

  Edit: so bad, yet another restart that he lets me actually left-scan-ignore the update of the screen without anything do. Sorry for the false alarm, I'll leave it here for anyone to find.

• BB10 Dev Alpha Simulator Dev Mode doesn't work

  Hello!

  I have a problem with BlackBerry 10 Dev Alpha Simulator. When I go into the VM for the 10 Dev Alpha settings BlackBerry Simulator and enable development mode, the icon of the Mode of development will not displayed it.

  I can't see the IP address of Simulator and install my application.

  Screenshot:

  

  U can not find the icon of the mode of development in the Simulator. What you have to do, it is after switching to the mode of development for sure, go into settings,-> select network from the drop-down list-> note in ipv4 ip address... And it's ip address, you use the mode of development.

• Black box around since Dev Alpha 10.0.9.2320 Slider control updated

  I upgraded my Dev Alpha 10.0.9.2320 yesterday, and since then, the bbUI.js slider controls have a black box around the control.  I have attached a picture of my app on before the update and after.  The same thing is present in the samples of bbUI.js, as the example of cursor has a dark background, it is more difficult to see.  It doesn't go with the wave, the device.  Is this a bug or do I need to change something?

  

  Ryan, it's the same for me.  Try to catch the last bbui of github code, and then build your application again and it should be fine on the new version of the OS from yesterday.