Database Users

[CLOSED] - [ROM] [HP iPAQ hw6900] [WWE] WM6.1 build 21057

English project closed.

hi
he will be work on HP hw6910?

hola a todos.
es real esta rom ?????

zbebus
Yea. BUT! not now. Now only rom work with this bootloader version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
because i have 6915 with this boot =P
Then i'll tell if someone have different version what to do
PS Also we will work on "NO GSM" problem

cant wait, ill beta test for sure
i have the g.39 bootloader, and also suffer from the "no gsm" issue.
at current the device is sitting in a drawer getting rather lonely!
i dont care if it bricks the hw6915, its been sitting in the drawer for over a year!!

Is this rom for G3 or G4 flash models?

I can confirm the flash works on 6955 series phones

some instructions....

well there are links to the files in the 4pda forum at the top.
one BIG CAVEAT as Vervol stated is:
Vervol said:
Yea. BUT! not now. Now only rom work with this [vG. 39] bootloader version.
Click to expand...
Click to collapse
First the warnings and then the steps
Warning:
Steps confirmed to work using Windows XP on a G4 based flash device if you're not sure look it up in your device:
Start/System/HP Asset Viewer/
under the heading "Flash Chip Type"
if you have any other Flash chip type it is not confirmed to work and may cause your PDA to be inoperable.
Steps:
1. put pda into bootloader mode: hold two buttons next to Send and End + power + push reset button with stylus
(with activesync running) extract the SPL vG.39.7z file and double click on "Command Prompt"
2. then type in :
Code:
pdocwrite spl -n0 -b 0x20000 0 0x80000
wait till it's done
3. double click on the activesync logo in the taskbar, make sure to disable usb connection to the device.
4. extract the 6915_ENG.7z file and run the Sable_RUU.exe file and by now it should start flashing....
5. when it's finished flashing double click activesync again and re-enable usb connections and that's it.

Experience so far...
NOTE: These files only flashes the O.S so it wont' affect those with the NO-GSM problem.
So in order to get more people to try this, I'd like to share what I've tried so far :
What works:
Phone: Sending and receiving calls
SMS : sending and receiving messages
Wifi: Connects to both Open networks, WEP, and WPA WPA-PSK (though there is a known bug with WEP and WPA in WM6.1, right now a workaround is switching wifi on and off really quickly and it connects fine without using odyssey access client) but other than that it works normally. A possible patch could fix this, but I haven't tested it out yet
Camera: Takes both photos and video
Notes: Audio note recording feature works.
What doesn't work:
GPS: I haven't managed to get this working so far but it might just be an issue with settings (the program I tried was Garmin Mobile XT)
MMS: I can't seem to find feature in messaging app.
Bluetooth: Profiles are missing so I can't properly pair with devices EDIT: I tried this again and managed to pair with a headset
Haven't tried:
Tethering: Since I don't have a data plan with my provider, it doesn't allow me to use GPRS/Edge except to check account information on mobile browser or unless I buy a 24/hr package in bulk so I haven't tested this.
....But I did manage to make a GPRS connection to check my account info.
O.k good luck everyone

Is this rom multilanguage? does it have spanish?

great news, i hope this proyect get more stable and we can upgrade our olds Hp 6915

tOz666 said:
Is this rom multilanguage? does it have spanish?
Click to expand...
Click to collapse
It's in english, it does support changing the basic regional settings like before... but I am sure the possibility for other languages is more likely once more people start getting involved with dissecting the ROM in kitchens.

Please can you upload to some service available outside Russia ?
Thanks

dreamH6 said:
Please can you upload to some service available outside Russia ?
Thanks
Click to expand...
Click to collapse
Uploaded it [here]
ROM + SPL

Spiaatie said:
Uploaded it [here]
ROM + SPL
Click to expand...
Click to collapse
thanks a lot, but... I have a G3 flash and 0.38 bootloader ....
does anyone has tested on this version?

I am not sure it would be compatible

Ok... did more testing of Bluetooth devices, and it does pair with headsets

I figured I would post some stuff from the asset viewer of before and after, and to see if people have the same version:
before is linked here
AFTER:
Memory
System ROM Size : 128MB
System RAM Size : 64MB
ROM Is Flash : Yes
Flash Chip Type : G4
Flash Block Size : 256KB
PSM Driver Version : N/A
Version
Product Revision Level :
ROM Date : 06/02/12
ROM Revision : 1.21UK.00 ENG
Extended ROM Version : N/A
OS Version : Windows CE 5.2
Bootloader Version : G.39
XIP Version : 1.0.0.0
Display
Color : No
Horizontal Pixels : 240
Vertical Pixels : 240
Color Depth : 65536
Display Type : TFT
Panel ID : 0
System
Manufacturer : Hewlett-Packard Company
Product ID : 414750-001
Model ID : hp iPAQ hw6955
Processor Type : PXA270-416MHz
Processor Revision : C5
Language : ENGLISH
UUID: -x-------------------
Camera
Module Present : Yes
Hardware Revision : 9650
Hardware Driver Version : 0.8.0
Software Driver Version : 4.1.0
Software Version : 1.0.21
Camera API Interface Version : 1.0.7
Camera Information : 1.3 MP 8X Zoom
Bluetooth
Radio Present : Yes
Firmware Version :
Hardware Revision :
Driver Version : 1.7.1.6700
Software Version : 1.7.1.6700
MAC Address : ---------------
Wi-Fi
Radio Present : Yes
Firmware Version : (missing)
Hardware Revision : (missing)
Driver Version : 1.00.00
Software Version : 2.0.53
IP Address : -----------------
MAC Address : -----------------
GSM
Radio Present : Yes
N/A
N/A
N/A
N/A
N/A
IMEI Number : --------------------
GPS
GPS Present : Yes
Status : N/A
Manufacturer : Global Locate
Revision Level : N/A
Driver Version : 2.00
Firmware Version : 4.1099.123.0
Software Version : 0.14.2214.0

jambongo said:
well there are links to the files in the 4pda forum at the top.
one BIG CAVEAT as Vervol stated is:
First the warnings and then the steps
Warning:
Steps confirmed to work using Windows XP on a G4 based flash device if you're not sure look it up in your device:
Start/System/HP Asset Viewer/
under the heading "Flash Chip Type"
if you have any other Flash chip type it is not confirmed to work and may cause your PDA to be inoperable.
Steps:
1. put pda into bootloader mode: hold two buttons next to Send and End + power + push reset button with stylus
(with activesync running) extract the SPL vG.39.7z file and double click on "Command Prompt"
2. then type in :
Code:
pdocwrite spl -n0 -b 0x20000 0 0x80000
wait till it's done
3. double click on the activesync logo in the taskbar, make sure to disable usb connection to the device.
4. extract the 6915_ENG.7z file and run the Sable_RUU.exe file and by now it should start flashing....
5. when it's finished flashing double click activesync again and re-enable usb connections and that's it.
Click to expand...
Click to collapse
Hi Jambongo! Can you please tell me if second half of step 1 and the whole step 2 - is only for bootloader upgrading? or is it some sort of patch for bootloader? Also please advice what's code instruction all about? Is it the same code for all ipaq 6900 series? And finally, did you manage to get the GPS running again? If so, I might just give it a go also.. Thanks a lot
Best regards,

[Q] New Motorola Milestone 2 is not working after 2 days... (can't turn on)

Hi,
I bought Motorola Milestone 2 from UK(probably) two days ago and so far everything was fine. I tested WiFi and other tools and it worked pretty well.
Today, I had some auto-reboots when I was using phone, phone usually stopped during starting... but it backs to normal. Then I was calling to my friend, and decided to "END CALL", but nothing happened (I was unable to close this calling 'menu'). During this other apps works fine (I checked browser), then I decided to TURN OFF the phone.
Now I have problems with turning it on, during start I see motorola's logo, then it blinks for a moment and finally screen turns 80% black (a bit brighter than black one, there is some light ). I can't turn off the phone using top button, I have to pull out the battery. When phone is connected to USB, small white diode is working and I can TURN OFF the phone (but I have still the same problem during start).
I tried removing SIM card, SD card, both of them, I don't have "recovery menu" when I am pressing down X key and turning POWER ON (same things happen) - maybe I am doing something wrong during pressing Xkey and power key(??). I have only ARROW UP + POWER ON bootloader menu.
I spent over 6hours for searching solution - no results so far.
What should I do? THANKS IN ADVANCE FOR ANY SUGGESTIONS.
I logged to motoblur and my software version is 62.2.16.A953.Retail.en.GB.

I dont have a milestone 2, i have the original milestone though, and to fix this id just have to load the screen that comes up when you press the UP button on the dpad (arrow). Then plug your phone to your PC, open RSD lite and once your device has been detected you go ahead and flash a stock SBF file.
Hope that helps

XtriFe said:
I dont have a milestone 2, i have the original milestone though, and to fix this id just have to load the screen that comes up when you press the UP button on the dpad (arrow). Then plug your phone to your PC, open RSD lite and once your device has been detected you go ahead and flash a stock SBF file.
Hope that helps
Click to expand...
Click to collapse
Hi, I am thinking about it, I downloaded 5 different SBF files, but I am not sure which I should use in my motorola. I have it on my moto's box: SM, A953, GB, RETAIL, SLVR so it probably comes from UK.
Which version of RSD Lite should I use? I have RSD Lite 4.9
MILS2_U6_2.2.19_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20OPTAU_P022_A016_M006_HWp2a_Service1FF.sbf.gz
MILA2_U6_3.12.0_SIGNED_US1MILESTONE2RETBRB125LA016.0R_GSXMILETRETBRLA_P026_A009_M012_HWp2a_Service1FF.sbf.gz
MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20O2DE_P038_A015_HWp2a_Service1FF.sbf.gz
MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20RTDACH_P016_A005_HWp2a_Service1FF.sbf.gz
MILS2_U6_2.2.19_SIGNED_USAMILESTONE2B1B80VF00B.0R_USXMILE20VFAU_P032_A012_M005_HWp2a_Service1FF.sbf.gz
MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_UCXMILE20RTGB_P029_A007_HWp2a_Service1FF.sbf.gz
My next problem is when I connect my moto with USB cable, I have something like this in RSD Lite app:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x007012
DRM Version: N / A
AP Die ID: 27200210dc245f010000d8fe0300
BP Die ID: 0000000000000000000000000000
AP Public ID: 48caac38e2b174c29ad89848c7df4d1dd7a87422
BP Public ID: 0000000000000000000000000000000000000000
Are N/A's okay? I do not want to destroy my phone after 2 days ;( (it's my 1st smarhphone)
edit: Well, I loaded the last SBF file and click START in RSD lite... - everythin was fine there but nothing happened with my phone, still the same problem. Any suggestions?

BTW. What will happen if I install another SBF file (german one instead of GB?)

saqus said:
BTW. What will happen if I install another SBF file (german one instead of GB?)
Click to expand...
Click to collapse
Will occur error halfway. You definitely need to flash the UK SBF rom. Follow below link http://megaupload.com/?d=Q29778GX
If you click the link and find out this message appear (The file you are trying to access is temporarily unavailable. Please try again later.) dun worry, try later. Is totally working. Just fix my unit just now with this UK SBF rom. Mine unit is bought from Clove, UK. Cheers...

Hm, I downloaded this file already from another site & I used it - nothing happened.
I will test this version now.
What is a bit weird, when I plug the phone in socket, I can see battery level animation but still can't turn on the phone, nothing happens after motorola's logo.

saqus said:
Hm, I downloaded this file already from another site & I used it - nothing happened.
I will test this version now.
What is a bit weird, when I plug the phone in socket, I can see battery level animation but still can't turn on the phone, nothing happens after motorola's logo.
Click to expand...
Click to collapse
Did you do it the right way? Mine unit auto turn on after finish flash the SBF rom. Then finally disconnect the usb cable.

My moto also turn of after finish, but I see only motorola logo and then blank screen again...
Which version of RSD Lite should I use? I have 4.6 now.

Use version 4.9
Sent from my Milestone 2 XDA App

I am uploading video right now with not working moto on Youtube You will show how amazing it is
http://www.youtube.com/watch?v=KHIZlyt6y94
ENJOY !

saqus said:
I am uploading video right now with not working moto on Youtube You will show how amazing it is
http://www.youtube.com/watch?v=KHIZlyt6y94
ENJOY !
Click to expand...
Click to collapse
Ill give you $300 for it. lol
Seriously though, its a matter of flashing the right SBF the right way. Find out how to get to the Bootloader on the milestone 2. On my milestone 1 all i have to do is keep the DPAD-UP button while turning the phone on.
Once you get there, plug your usb cable to your PC and RSD Lite will detect your phone which will let you flash your SBF file again. Id recommend flashing an UK stock one.
Also, have you installed the proper motorola USB drivers? remember you need to install the appropiate drivers depending on what OS you're using. (ie. Windows 7 x64, theres x64 motorola USB drivers you need to install)
I can imagine how sad you might be right now (after reading your comment on your youtube vid) but really, in my opinion, your phone is anything but permanently bricked
Let me know how that goes.
Good luck

To start Milestone2 into bootloader mode you should turn the phone on while holding the Volume Down and Camera buttons together.

r2beta0 said:
To start Milestone2 into bootloader mode you should turn the phone on while holding the Volume Down and Camera buttons together.
Click to expand...
Click to collapse
Wow, it's second method I think. I used KPAD+UP + POWER and it is also working.
Do you know another method to open RECOVERY MENU (originally X+POWER ON)?
Can someone tell me is this information about device in RSD LITE is good? (my previous post, bolded part)
http://screenshotuploader.com/s/lFoNJoaXJvJ
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-----------------
Seriously though, its a matter of flashing the right SBF the right way. Find out how to get to the Bootloader on the milestone 2. On my milestone 1 all i have to do is keep the DPAD-UP button while turning the phone on.
Click to expand...
Click to collapse
I used DPAD-UP + POWER ON and I had Bootloader menu.
Once you get there, plug your usb cable to your PC and RSD Lite will detect your phone which will let you flash your SBF file again. Id recommend flashing an UK stock one.
Click to expand...
Click to collapse
I did it (with UK stuff).
Also, have you installed the proper motorola USB drivers? remember you need to install the appropiate drivers depending on what OS you're using. (ie. Windows 7 x64, theres x64 motorola USB drivers you need to install)
Click to expand...
Click to collapse
I think Yes, I have 32bit version.
I can imagine how sad you might be right now (after reading your comment on your youtube vid) but really, in my opinion, your phone is anything but permanently bricked
Click to expand...
Click to collapse
I have exam session right now and I am not thinking about this phone
I think also it is bricked, but there is still a hope!
If nothing new happen during few days (no new ideas) I will send it to repair-service ( I've just received bill from my seller ).

You've got to that RSDLite screen, seems like the program is detecting your phone ok. Go ahead and flash the UK ROM and see how it goes.

I flashed it several times before! When it reboot whole system, I see moto logo and then the same problem - nothing after... :\

Can anyone test something for me with milestone2?
Switch off the phone.
Hold X + POWER ON during the whole test (do not release keys!)
Will it stay on Motorola logo (when you release key it will open RECOVERY SCREEN)?
MY SELLER SAID THAT MY PHONE COMES FROM GERMANY (MOTOROLA'S SHOP FOR EMPLOYERS) BUT IT IS WITH ENGLISH SOFTWARE (and it obviously was). SHould I use another SBF file than GB?

saqus said:
Can anyone test something for me with milestone2?
Switch off the phone.
Hold X + POWER ON during the whole test (do not release keys!)
Will it stay on Motorola logo (when you release key it will open RECOVERY SCREEN)?
MY SELLER SAID THAT MY PHONE COMES FROM GERMANY (MOTOROLA'S SHOP FOR EMPLOYERS) BUT IT IS WITH ENGLISH SOFTWARE (and it obviously was). SHould I use another SBF file than GB?
Click to expand...
Click to collapse
You can use any EU software as long as the bands are compatible. German, GB, EU etc., etc.

I have a similar problem and I'm trying to flash a new SBF, but after flashing I get a checksum error and cant get it to work...
I've activated log, and this is what I get:
14:53:51, March 14, 2011
Line: 527
ERROR: AP Die ID: 237001055bf45e010000d8ff0100
14:53:51, March 14, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
14:53:51, March 14, 2011
Line: 541
ERROR: AP Public ID: 38607a9e7df8020ec7cca49460878683e6aaa390
14:53:51, March 14, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
14:57:43, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x65A6, Phone: 0x67A6
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:57:44, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 33 checksums. File: 0x4C1B, Phone: 0x4E1B
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:08, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 39 checksums. File: 0xA01, Phone: 0xC872
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:08, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 40 checksums. File: 0xFDFF, Phone: 0x4A65
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:08, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 45 checksums. File: 0x6C96, Phone: 0x6E96
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:20, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 66 checksums. File: 0x3C24, Phone: 0x2C0E
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:20, March 14, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
14:58:20, March 14, 2011
Line: 597
ERROR: Flash failure: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x65A6, Phone: 0x67A6 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=32
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

I didn't have anything similar to your problem - In my case everything was OKAY when I flashed my phone (of course phone didn't turn on ).

Yes same problem ... Very strange !!!
Since yesterday my MM2 is briqued on boot animation ....
I have test RSDlite (it's not the first time I use it) but nothing (with 2 SBF different)
RSDLite :
1) Download firmware ==> Ok
2) Installation ==> Ok
3) Reboot ==> block on boot animation .... (look screen say "reboot manually.." but my MM2 is power on )
Please Help me ......
Thanks in advance !
In SWDL.txt you can see :
04/07/11 14:08:52 [Device ID: 0] Please manually power up this phone.
04/07/11 14:08:52 00000f08 Phone.cpp
In file "FlashErrorLog04_07_10_49_19.log"
10:50:08, April 07, 2011
Line: 527
ERROR: AP Die ID: 2b10011191095f010000d8ff0200
10:50:08, April 07, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
10:50:08, April 07, 2011
Line: 541
ERROR: AP Public ID: a97b57b8d28c0bbcc1507d9c960995e319ee21db
10:50:08, April 07, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
Who can help please .... ???

[INFO][R&D] I9300 UART and NVDATA guide

During the last weeks I was researching how to build a cable to establish an UART connection to my I9300. This guide should work but is still work in progress. Feel free to contribute.
Info: this is a guide for the international version I9300 with XMM6260 modem. The SGH-I747-variant uses a different baseband/modem from Qualcomm.
Warning: This guide allows you to interface your device at a very low level. You might brick your device or damage vital parts of it. A lot of this stuff is undocumented and there might be side effects. Be warned!
Short technical explanation:
By using a custom build USB cable you can establish a serial connection to your phone. It offers a UART interface to the XMM6260/X-Gold 626 modem used in the I9300.
The longer technical explanation:
The I9300 uses a FSA9485 USB Port Multimedia Switch (https://www.fairchildsemi.com/products/analog-mixed-signal/switches/accessory-switches/FSA9485.html) behind the MicroUSB port. This IC can detect what kind of accessories are plugged to your USB port. The detection is done by a resistor wired between GND and ID pin of the USB cable. Using a resistance level of 523K will trigger the UART Mode. While in UART mode the I9300 will use the D- and D+ pins of the MicroB-plug as serial TX/RX data lines.
What to to with it?
While booting you can see debugging output of the secondary bootloader (not that much though, mainly eMMC initialize). Once booted you can see modem output and send commands to it. Another option is to show "PDA" messages, but i never managed to get any output with this setting.
You can communicate to your modem using AT-commands. For more information I recommend reading E:V:A's great post "[XMM6260][X-GOLD 626] Modem Specification / Documentation / Hack-Pack". While his guide is focussing on the SGS2, i want to keep this guide I9300 specific.
How to build a cable?
Stuff you need:
A USB to serial converter supporting 3,3V(!) TTL levels (lots of this stuff around, check eBay or your local electronics supplier. Common chipsets are FTDIs FT232RL or Silicon Labs CP21xx, just make sure it supports 3,3V!)
A USB MicroB plug (like this https://www.sparkfun.com/products/10031 or I just sacrificed a cable for soldering directly to the connector which works too)
a resistor with 523K resistance (close value will work)
some wires
a soldering iron
Wire it like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to use it (tested with I9300XXELL4 (Android 4.1.2):
Install the drivers for your USB to serial converter (running linux your device will most likely be autodetected and assigned to /dev/ttyUSB0 or similar)
On your I9300 Dial *#7284# and set UART mode to "modem"
use your favorite serial console and set the following parameters for the serial port: rate: 115200 baud, data: 8 bits, parity: none, stop bit: 1, software flow-control: enable
I prefer using the "screen"-command on linux: "screen -t 'ttyUSB0 115200 8n1' /dev/ttyUSB0 115200,-ixoff,-ixon"
Now connect your UART-cable to the phone (it will power up on its own due to the FSA9485 chip, no need to worry)
If you see console output like this you got it right:
Code:
PMIC rev = PASS2(2)
BUCK1OUT(vdd_mif) = 0x05
BUCK3DVS1(vdd_int) = 0x20
[MMC] there are pending interrupts 0x00010000
cardtype: 0x00000007
SB_MMC_HS_52MHZ_1_8V_3V_IO
mmc->card_caps: 0x00000311
mmc->host_caps: 0x00000311
mmc_initialize: mmc->capacity = 30777344
�
AST_POWERON
AST_POWERON
AST_POWERON
Now you should be ready to send AT-commands to your phone.
Try send a simple "AT" and your phone should respond with "OK"
Code:
AT
OK
If everything above works you successfully managed to establish a serial console to your baseband processor. congratulations! proceed to the next post for tested AT commands.
Another warning at this time: Do not send random characters/commands to your modem. This is an easy way to brick your network connection or even your entire phone.
Troubleshooting:
check the wiring, maybe you switched TX/RX data lines
on linux check user rights on your /dev/ttyUSBX device, check with superuser if unsure
to be extended
THX to:
E:V:A for his great guides about modems/AT commands in general and the XMM6260
the Replicant project: http://www.replicant.us/
many other guys gave me a hint in the right direction which I forgot to mention here

Supported AT commands on the I9300
Please take this warning serious! As this is a debugging console to your baseband/modem the wrong command can easily overwrite vital data on you phone. Think before typing!
I won't go into detail about AT command syntax here. I recommend to read the following infos before trying any own approaches:
http://en.wikipedia.org/wiki/Hayes_command_set
http://www.codeproject.com/Articles/85636/Introduction-to-AT-commands-and-its-uses
http://forum.xda-developers.com/showthread.php?p=53175152#post53175152
AT commands are modem specific. Not all commands work on all modems, but there are still some general commands working on most phones!
Working AT commands:
AT+CLAC --> gives a list of all supported AT commands, though there are more commands which are undocumented, following output on I9300:
Code:
ATS
ATD
ATA
ATO
ATE
ATH
ATV
ATZ
ATl
ATm
ATQ
ATX
AT&F
AT&D
AT&C
AT\Q
AT+CGSMS
AT+CMGD
AT+CMGF
AT+CMGL
AT+CMGR
AT+CMGS
AT+CMGW
AT+CMMS
AT+CMSS
AT+CNMA
AT+CNMI
AT+CPMS
AT+CSCA
AT+CSCB
AT+CSMS
AT+XCSSMS
AT+XSMS
AT+XTESM
AT+CSDH
AT+CSAS
AT+CRES
AT+CMGC
AT+CSMP
AT+CGREG
AT+COPN
AT+COPS
AT+CREG
AT+CSQ
AT+XBANDSEL
AT+XCOPS
AT+XCSPAGING
AT+XEONS
AT+XREG
AT+XAACOPS
AT+XUBANDSEL
AT+XRAT
AT+CPLS
AT+CPOL
AT+XHOMEZR
AT+XCSQ
AT+CHUP
AT+CMOD
AT+CMUT
AT+CTFR
AT+VTS
AT+XCALLSTAT
AT+XDTMF
AT+XVTS
AT+CSTA
AT+CVHU
AT+VTD
AT+CCWE
AT+CR
AT+CRC
AT+XPROGRESS
AT+XREDIAL
AT+CAOC
AT+XLIN
AT+CCFC
AT+CCWA
AT+CHLD
AT+CLCC
AT+CLCK
AT+CLIP
AT+CLIR
AT+CNAP
AT+COLP
AT+COLR
AT+CPWD
AT+CSSN
AT+CUSD
AT+CCUG
AT+CBST
AT+CEER
AT+CGACT
AT+CGANS
AT+CGATT
AT+CGAUTO
AT+CGCLASS
AT+CGCMOD
AT+CGDATA
AT+CGDCONT
AT+CGDSCONT
AT+CGEQMIN
AT+CGEQNEG
AT+CGEQREQ
AT+CGEREP
AT+CGPADDR
AT+CGQMIN
AT+CGQREQ
AT+CGTFT
AT+XCGCLASS
AT+XDNS
AT+XGAUTH
AT+FCLASS
AT+CRLP
AT+XNVMPLMN
AT+XNVMMCC
AT+CBC
AT+CCID
AT+CCLK
AT+CFUN
AT+CGMI
AT+CGMM
AT+CGMR
AT+CGSN
AT+GSN
AT+CIMI
AT+CMEE
AT+CMUX
AT+CNUM
AT+CPIN
AT+CPWROFF
AT+CRSM
AT+CSCS
AT+CSIM
AT+CSVM
AT+CTZR
AT+CTZU
AT+IPR
AT+XCTMS
AT+XGENDATA
AT+XPINCNT
AT+XLOG
AT+XMER
AT+XSIMSTATE
AT+TRACE
AT+XL1SET
AT+XSIO
AT+XDLCTEST
AT+XPOW
AT+XCEER
AT+XEER
AT+XTRACECONFIG
AT+XMUX
AT+XFDOR
AT+XFDORT
AT+XCONFIG
AT+XAPP
AT+XHSDUPA
AT+XCAP
AT+CPIN2
AT+XDATACHANNEL
AT+CONNECTPORT
AT+CAMM
AT+CACM
AT+CCHO
AT+CCHC
AT+XCSP
AT+NEER
AT+CUAD
AT+XUICC
AT+XLEMA
AT+XSYSTRACE
AT+CLAC
AT+CPUC
AT+CLAN
AT+CGLA
AT+CRLA
AT+CPAS
AT+XSVM
AT+XNOTIFYDUNSTATUS
AT+XRXDIV
AT+XRXDIV3GRAB
AT+XMAGETKEY
AT+XMAGETBLOCK
AT+CPOS
AT+CPOSR
AT+CMOLR
AT+CMTLR
AT+CMTLRA
AT+XCPOSR
AT+XSETCAUSE
AT+XSPEECHINFO
ATV1 --> Enables verbose command results mode
ATE0 --> Turns off local echo
AT+SERIALNO=1,0 --> shows serial number
AT+CGSN --> shows IMEI
AT+XGENDATA --> shows modem version:
Code:
+XGENDATA: " SP6260_M0_MODEM_03.1241_DB121008 2012-Dec-10 11:25:46
PDB_NOT_AVAILABLE
*SP6260_M0_MODEM_03.1241*"
ATi --> shows device info:
Code:
Manufacturer: SAMSUNG
Model: I9300
Revision: I9300XXELL4
IMEI: XXXXXXXXXXXX
AT+HEADINFO=1,1 - Shows device information, "Unique Number" is not that unique. If you copy EFS you copy number.
Code:
+HEADINFO:1,1,1
Model Name = GT-I9300
Country/customer = -
Customer Code = DBT
Date = -
Charger = -
S/W version = I9300XXELL4
Unique Number = CVTXXXXXXXXXXXX
Memory Name = -
Sec Code = -
AT+IMEITEST=1,0 - shows "corrupted!!" with damaged EFS, not yet tested with good EFS
Code:
+IMEITEST:1,corrupted!!
AT+MSLSECUR=1,0 --> Some information I found indicates this is the first security mechanism. You need to send a device specific code to unlock write mode (AT+MSLSECUR=2,<UNLOCK CODE>). I saw examples in this form: AT+MSLSECUR=2,<SERIAL NUMBER>_<HEXADECIMAL KEY> but was not able to generate it.
AT+AKSEEDNO=1,0 --> It seems to be a challenge/response security mechanism: You have to respond to this challenge with another AT-command (AT+AKSEED=2,<RESPONSE CODE>). See next post for details.
Code:
AT+AKSEEDNO=1,0
+AKSEEDNO:1,16799-25-329

Some related technical infos
EFS:
The modem stores its settings in your /efs partition (mmcblk0p3), more precisely in your nv_data.bin file. It might be wise to do a backup. (More information on EFS)
Modem Firmware:
Your modem is running a Real Time Operation System (RTOS) named ThreadX. It is stored in modem.bin and different versions can be flashed by Odin.
The ServiceMode.apk-application talks directly to the modem RTOS.
AKSEED
This seems to be a challenge-response security algorithm. Maybe somebody has a clue as i would love to find out how it works.
I have collected some AKSEED examples from the web:
Challenge: 29987-125-1427 - Correct response: 16096-95-115
Challenge: 8299-182-209 - Correct response: 7928-94-124
Challenge: 767-207-25 - Correct response: 309-93-128

nv_data.bin
If you attempt to change the nv_data.bin within Android it will get restored from .nv_data.bak and .nv_core.bak. It is protected by a special MD5-hash which is stored in nv_data.bin.md5/.nv_data.bak.md5/.nv_core.bak.m5. The MD5-hash is generated from nv_data.bin, but can not be generated using a normal MD5-algorithm. If no backup is present a default nv_data.bin is created.
I assume the ril-daemon is responsible for checking the correct checksum and restoring the backup.
There are some offsets of interest in nv_data.bin (just assumptions, may be different on some modem firmwares):
I believe the modem settings related part starts at Offset 0x180000 with the String "SSNV".
0x181469 - Network Lock (i think its 5 bytes starting from 0x181469: Network Lock, Subset Network Lock, SP Lock, CP Lock, Data Lock)
0x18800F-0x188011 - Product Code (DBT,XEO,etc.)
0x188021-0x188023 - Product Code (DBT,XEO,etc.)
0x18815F-0x188165 - Serial Number
0x194004-0x194023 - Modem Version
0x194049-0x194053 - Firmware Version (I9300XXELL4,I9300XXDLIB,etc.)
0x18146e, 0x18148e, 0x1814ae, 0x1814ce, 0x1814ee - 5 times the same value, most likely a hash of the Unlock Code. The hashes are separated by "4A" hex. The hash is generated different than on SGS2 - see here
If anybody has further information regarding offsets, stored data and used encryption please post here or contact me!

MD5 generation: (cat nv_data.bin; echo -n Samsung_Android_RIL) | md5sum
EDIT: echo -n, not echo - n
Sent from my GT-I9305 using XDA Free mobile app

.NetRolller 3D said:
MD5 generation: (cat nv_data.bin; echo - n Samsung_Android_RIL) | md5sum
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
nice one...but you have to stop ril-daemon on device before replacing or it will revert to nv_data.bin from backup:
Code:
stop ril-daemon

The data at 0x180004 to 0x180033 in nv_data.bin seems to be related to the AT+MSLSECUR command:
AT+MSLSECUR=1,0 on a phone with undamaged /efs responds the serial number:
Code:
AT+MSLSECUR=1,0
+MSLSECUR:1,RFXXXXXX
if you copy these offsets from undamaged /efs to another phone the data gets scrambled:
Code:
AT+MSLSECUR=1,0
+MSLSECUR:1,��Lb�šV��Ƨo~
if you edit these offsets to all "FF"s:
Code:
AT+MSLSECUR=1,0
+MSLSECUR:1,0000000000
so i assume it is somehow crypted by the serial number or another physical(?) unique identifier

AT+EGMR command
Does the AT+EGMR command work?

Lumia 520 - Unable to find a bootable option

A friend has asked me to look at this Nokia Lumia 520, apparently it turned on one day and displayed this error message "unable to find a bootable option. Press any key to shutdown"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nokia Software Update for Retial recognises the phone and says software can be installed:
This downloads fine and starts the install process, however always fails with the message "phone not supported by nokia software updater retail"
I have also tried using NaviFirm+, searching for the product code 059S3T5 which lets me download the RM914_3058.50000.1425.0006_RETAIL_eu_euro1_327_06_452364_prd_signed firmware.
However i'm unable to flash this with the Nokia Care Suite, it states: 0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed or not signed for this device.
Has anyone got any suggestions on what else i can try to flash this firmware? or to try fix the phone?
I was following the tutorial here Flash/unbrand Lumia devices thinking if the firmware was re flashed all would be fine.
Cheers for any advice

Have you try with this
http://www.microsoft.com/en-us/mobile/support/faq/?action=singleTopic&topic=FA142987

Thanks for the suggestion, I have tried that, it will download the firmware too, however fail before flashing it stating the device is not supported.

InsaneNutter said:
Thanks for the suggestion, I have tried that, it will download the firmware too, however fail before flashing it stating the device is not supported.
Click to expand...
Click to collapse
I think win partition is crash. (like memory damage/corruption)
Hardware related problems.

InsaneNutter said:
A friend has asked me to look at this Nokia Lumia 520, apparently it turned on one day and displayed this error message "unable to find a bootable option. Press any key to shutdown"
Nokia Software Update for Retial recognises the phone and says software can be installed:
This downloads fine and starts the install process, however always fails with the message "phone not supported by nokia software updater retail"
I have also tried using NaviFirm+, searching for the product code 059S3T5 which lets me download the RM914_3058.50000.1425.0006_RETAIL_eu_euro1_327_06_452364_prd_signed firmware.
However i'm unable to flash this with the Nokia Care Suite, it states: 0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed or not signed for this device.
Has anyone got any suggestions on what else i can try to flash this firmware? or to try fix the phone?
I was following the tutorial here Flash/unbrand Lumia devices thinking if the firmware was re flashed all would be fine.
Cheers for any advice
Click to expand...
Click to collapse
Hi,
Have you sorted your phone out yet?

BruceKDallas said:
Hi,
Have you sorted your phone out yet?
Click to expand...
Click to collapse
Hi,
Nope i could never fix the phone, I spent loads of time messing about with it however think it was a hardware related problem.
I've given it back to my friend and shes since got a new phone.

I am into the same situation... NOKIA 520 RM-914 Code 059S7H0
"ERROR: Unable to find a bootable option. Press any key to shut down". Any button I push, the phone is going in bootloop ending with this ERROR...
I have tryed first with Windows Device Recovery Tool (WDRT) 3.1.4 to repair it, but no success...
In WDRT my Lumia is not detected automatically, so i must choose manually device manufacturer. To be detected I must restart the Lumia when DWRT is trying to detect it.
The Phone is detected as LUMIA phone, firmware version: unknown, Software available on server: 3058.50000.1425.003.
When I try to install the software after I download the package, the result is:
"Operation ended with failure. The software is not correctly signed or not signed for this device."
The NOKIA driver is seen as NOKIA BOOTMGR.
Then I've search on the internet about this problem and I've found this thread.
I tried the advanced mode with thor2.exe, I downloaded manually the firmware for my device Lumia 520, RM-914, Code 059S7H0
I opened Command Prompt as administrator, then used the command:
cd c:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\
I used the command line to extract gtp0.bin from ffu image:
thor2 -mode ffureader -ffufile "C:\rm-914\RM914_3058.50000.1425.0003_RETAIL_eu_hungary_422_03_447211_prd_signed.ffu"
The result was 2 files, gpt0.bin and GPT1.bin. I renamed gpt0.bin as msimage.mbn.
RKH of the device is:
RKH of SBL1: F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD
RKH of UEFI: F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD
I've downloaded the hex file for my Lumia RM-914 to have the 2 files HEX.hex and msimage.mbn for the command line:
thor2 -mode emergency -hexfile "C:\TEMP\HEX.hex" -mbnfile "C:\TEMP\msimage.mbn" -orig_gpt
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.1
thor2 -mode emergency -hexfile C:\TEMP\HEX.hex -mbnfig_gpt
Process started Sun Dec 06 23:12:08 2015
Debugging enabled for emergency
Initiating emergency download
Operation took about 10.00 seconds.
THOR2_ERROR_CONNECTION_NOT_FOUND
THOR2 1.8.2.18 exited with error code 84000 (0x14820)
The Phone is still in NOKIA BOOTMGR mode...
If I try to disconnect the phone and restart, it goes into the the same message:
"ERROR: Unable to find a bootable option. Press any key to shut down", not showing me the RED screen like it should be.
If I go into the next step for flashing the device with the command line:
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile "C:\RM-914\RM914_059S7H0_3058.50000.1425.0003_037.vpl"
the screen changes into a big NOKIA logo, the driver goes from NOKIA BOOTMGR into NOKIA FLASH...
Thor2 is running on Windows of version 6.1
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\RM-914\RM914_059S7H0_3058.5
0000.1425.0003_037.vpl
Process started Sun Dec 06 23:22:20 2015
Logging to file C:\Users\Marta\AppData\Local\Temp\thor2_win_20151206232220_Threa
dId-3864.log
Parsing VPL file C:\RM-914\RM914_059S7H0_3058.50000.1425.0003_037.vpl
Successfully parsed VPL
Flashing .ffu file RM914_3058.50000.1425.0003_RETAIL_eu_hungary_422_03_447211_pr
d_signed.ffu (SW version 3058.50000.1425.0003)
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Boot Manager detected
Check status of battery
State of charge 8, charging current 282
Protocol version 1.1 Implementation version 1.16
Detecting UEFI responder
HELLO success
Lumia Boot Manager detected
Check status of battery
State of charge 8, charging current 266
Protocol version 1.1 Implementation version 1.16
Booting to FlashApp
Reboot to FlashApp command sent successfully.
DetachFrom connection
Verifying that device is online
Device is online
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Size of one transfer is 2363392
Size of buffer is 2359296
Number of eMMC sectors: 15269888
Platform ID of device: Nokia.MSM8227.P6036.1.2
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0019
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file C:\RM-914\RM914_3058.50000.1425.0003_RETAIL_eu
_hungary_422_03_447211_prd_signed.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 1.15 Implementation Version 1.28
DevicePlatformInfo: Nokia.MSM8227.P6036.1.2
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 19
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU async version 3 supported.
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 15269888
CID: Samsung, Size 7456 MB
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
Unable to send ECHO REQ or ECHO REQ not supported
Get security Status...
Security Status:
Platform secure boot is enabled.
Secure eFUSE is enabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get RKH of the device...
RKH of the device is F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C
868FD
Get ISSW Version...
Get ISSW Version, SKIPPED!
Get system memory size...
Size of system mem: 524288 KB
Read antitheft status...
Requested read param 0x41545250 is not supported by this flash app version.
Send backup to RAM req...
Clearing the backup GPT...SKIPPED!
Successfully parsed FFU file. Header size: 0x000e0000, Payload size: 0x000000006
2900000, Chunk size: 0x00020000, Header offset: 0x00000000, Payload offset: 0x00
000000000e0000
RKH match between device and FFU file!
Option: Skip CRC32 check in use
Start sending header data...
FlashApp returned reported error in SecureFlashResp!
Status: 0x1106, Specifier: 0x8000000E
FA_ERR_FFU_SEC_HDR_VALIDATION_FAIL
Send of FFU header failed!
[IN] programSecureFfuFile. Closing C:\RM-914\RM914_3058.50000.1425.0003_RETAIL_e
u_hungary_422_03_447211_prd_signed.ffu
programming operation failed!
0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not co
rrectly signed or not signed for this device.
Operation took about 3.00 seconds.
THOR2_ERROR_FA_SIGNATURE_FAIL
THOR2 1.8.2.18 exited with error code -100658938 (0xFA001106)
Here, after this step, if the flash is 100% succesful, the screen must change in Green,
mine finished with the same error: "The FFU file is not correctly signed or not signed for this device..."
I guess the most of us are into the same situation, I can't make the device to skip the signature check... Any sugestions?

have you jtag?

As far as I read, JTAG is a toolbox for repairing Phones which have the same problem, but what we are trying to do is without this toolbox, we have a dead phone at home. Microsoft said is a hardware failure and they must change complete motherboard, but with Jtag Toolbox can be repaired without change anything, just a complete writing of the bootloader and software. I don't want to buy the toolbox just to repair my Lumia 520, I don't need it, I'm just a home user not a repairing company...

melhisedec said:
As far as I read, JTAG is a toolbox for repairing Phones which have the same problem, but what we are trying to do is without this toolbox, we have a dead phone at home. Microsoft said is a hardware failure and they must change complete motherboard, but with Jtag Toolbox can be repaired without change anything, just a complete writing of the bootloader and software. I don't want to buy the toolbox just to repair my Lumia 520, I don't need it, I'm just a home user not a repairing company...
Click to expand...
Click to collapse
are you should to find testpoint for qcom9008. and flashing phone.

Mine was running everything give I install windows 10 just give the battery does not know dai was appearing this message (Erro Unable to find a bootable option error. Press any key to shut down,) Lumia 925 Brazil
---------- Post added at 03:41 AM ---------- Previous post was at 03:36 AM ----------
Mine was running everything give I install windows 10 just give the battery does not know dai was appearing this message (Erro Unable to find a bootable option error. Press any key to shut down)

Usually, is the main problem with Lumia Software update and stupid engineers from Microsoft does not fix it...

you deleted header partition, and lumia don't power on. help you only jtag.

I didn't know anything about this problem of almost any Lumia device until my phone has done the automatic software update from Win8 to 8.1 or 10, I don't know which one... And the the phone restarted with this stupid problem:
"ERROR: Unable to find a bootable option. Press any key to shut down"...
I have one week of searching over the internet to fix this but i couldn't make it...
If i can remove or unlock the bootloader, maybe I can force the phone to be Flashed with WDRT 1.34 and no more error:
"The FFU file is not correctly signed or not signed for this device."

melhisedec said:
I
Click to expand...
Click to collapse
Only you can help the programmer and all) nokia, wpinternals not flashing it. pins or seek to enter the 9008 regime (disassembly required).
partition table got off
i know this problems on my lumia 720(1 motheboard- After the firmware is not those files, 2 motherboards- After stitched sbl3 not true - died).
jtag helped to you, and me.

InsaneNutter said:
Hi,
Nope i could never fix the phone, I spent loads of time messing about with it however think it was a hardware related problem.
I've given it back to my friend and shes since got a new phone.
Click to expand...
Click to collapse
Cool. I had the same issue and many other issues with my 520. I have a very cool way of fixing this and all other issues if you struggle to start the phone up. If you are interested, let me know and I will explain to you. Very easy and process takes about 5 minutes.
Cheers

BruceKDallas said:
Cool. I had the same issue and many other issues with my 520. I have a very cool way of fixing this and all other issues if you struggle to start the phone up. If you are interested, let me know and I will explain to you. Very easy and process takes about 5 minutes.
Cheers
Click to expand...
Click to collapse
How did you do ?

melhisedec said:
As far as I read, JTAG is a toolbox for repairing Phones which have the same problem, but what we are trying to do is without this toolbox, we have a dead phone at home. Microsoft said is a hardware failure and they must change complete motherboard, but with Jtag Toolbox can be repaired without change anything, just a complete writing of the bootloader and software. I don't want to buy the toolbox just to repair my Lumia 520, I don't need it, I'm just a home user not a repairing company...
Click to expand...
Click to collapse
Did you follow http://forum.xda-developers.com/showthread.php?t=2515453 correctly?

InsaneNutter said:
A friend has asked me to look at this Nokia Lumia 520, apparently it turned on one day and displayed this error message "unable to find a bootable option. Press any key to shutdown"
Nokia Software Update for Retial recognises the phone and says software can be installed:
This downloads fine and starts the install process, however always fails with the message "phone not supported by nokia software updater retail"
I have also tried using NaviFirm+, searching for the product code 059S3T5 which lets me download the RM914_3058.50000.1425.0006_RETAIL_eu_euro1_327_06_452364_prd_signed firmware.
However i'm unable to flash this with the Nokia Care Suite, it states: 0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed or not signed for this device.
Has anyone got any suggestions on what else i can try to flash this firmware? or to try fix the phone?
I was following the tutorial here Flash/unbrand Lumia devices thinking if the firmware was re flashed all would be fine.
Cheers for any advice
Click to expand...
Click to collapse
hy bro try this...... http://forum.gsmhosting.com/vbb/f67...mc-error-unable-find-bootable-option-1931094/ i have sucses

feherneoh said:
I have seen this error millions of times on 520, and could fix it always
what you'll need:
PC
micro USB cable
WPInternals
.hex loader for 520
.ffu for 520
T4 screwdriver
Small wire
All you have to do is to short the resistor on eMMC clock lane, and connect USB, phone will be in emergency mode. You can either select unlock or relock in WPInternals, but for unlock, be sure to use an SBL3, because that won't fix the problem on its own.
The best would be selecting relock, then flashing the ffu, so EFIESP gets fixed
If you need help finding that resistor, PM me
Click to expand...
Click to collapse
Ok, so I found the resistor on a picture in another forum - so I just short it out and connect to USB while still shorted?

How to Flash with Nokia care suite 5

Warnings
All members of xda-developers, and the author can not be held responsible for any damage to any of your devices after applying the following
try at your own risk
1 ) Download and install Nokia care Sute 5 Latest Working
For Lumia 635 or otherirst Windows Phone 8.1 devices: RM-974, RM-975, RM-976, RM-977, RM-978, RM-979, RM-1010, RM-1027. link :- Nokia Care Suite PST 5.0 5.1.83.1414
2)you can use NaviFirm+ 3.2 (click here)
UPDATE :
first you need to know your mobile product code
if remove battery your product type and code will be printed there
or
open Extras + info you will see RM type like RM-xxx and choose your desired product code to flash
3 ) After installing Nokia care suite ,create a newfolder with a Name " Products" at C:\ProgramData\Nokia\Packages
it will become C:\ProgramData\Nokia\Packages\Products
Now create Your RM-xxx empty folder ,for lumia 1520 The folder name will be RM-937
in order to see hidden programdata folder click on show hidden folder in view
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
check your device product code list by searching like example "lumia 1520 product codes seidea.com" open first link all product code list will be there
,select Vietnam firmware for field test,in windows phone 10 10149 build we got field test by selecting 3G only in sim settings ,but we will have polling frequency and selective bands for battery save ,so i choose vietnam
in my case its look like "059V318 VAR APAC VN CV WHITE" Here VN= Vietnam.
for Lumia 1520 INDIA These are product codes which had "IN" at 4th place in sentance
059V3M9 VAR IMEA IN CV BLACK
059V3N0 VAR IMEA IN CV WHITE
059V3N1 VAR IMEA IN CV YELLOW
059V3N2 VAR IMEA IN CV RED
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
5) open Navifirm and it asks for login,so click on cancel
choose your 7 letter product type and paste at search bar and press enter as seen below
click on browse and navigate to C:\ProgramData\Nokia\Packages\Products\RM-937 clik ok
and untick "Use product code as final path"
see below screen shot
click on Download to Download All Files ,it takes Time According to Internet speed
if you done correctly you will see all downloaded firmware files at C:\ProgramData\Nokia\Packages\Products\RM-937
Now open Nokia care suite and click on Product support tool for store 5
6 ) click on file ---> Open Prouct and type your phone model and select correct rm of rour phone
7 ) click on programming and select recovery
8 ) click on updated list , your phone product number and all informaton willl display ,connect your phone click start
9 )it check data packages of Firmware ask for press volumue up+power button untill it vibrates ,do the same thing click retry
10 ) check at your phone screen flashin already started ,dont distruct flashing ,keep your pc awake untill it shows recovery completed
you will flashed to desired version of Firmware .you will get full sys freespace

It seems that Microsoft Care Suite has come out .
Really worry about the latest lumias` support by Nokia Care Suite , but can`t find a way to get Microsoft Care Suite as my Emergency Tool . I love flashing.

To delete.

anaheiim said:
There is no software called Microsoft Care Suite, at least not now (hope that Nokia Care Suite will not be abandoned, and will be updated).
Click to expand...
Click to collapse
Maybe. Hoping we can still get such powerful tool in the future.

anaheiim said:
There is no software called Microsoft Care Suite, at least not now (hope that Nokia Care Suite will not be abandoned, and will be updated).
Click to expand...
Click to collapse
Did't you find yet the way how to flash with NSU/LSRT every Lumia even 535 ? After changing PC sure we can
http://www.windowsmania.pl/poradnik...wariantu-oprogramowania-programem-lsrt-19445/

To delete.

cant see folder on step 8. already enabled hidden files. preferences set in here: C:\ProgramData\Nokia\Packages\RM-937\Products
OS: win7 64bit,
need this to try win10 on lumia 1520 using this tut that refers me here to increase sys space
http://forum.xda-developers.com/win...thod-how-to-install-windows-10-phone-t3044746

To delete.

trying/downloading it now. thanks. would you know any updated / clean win10 how-to for lumia 1520?
---------- Post added at 05:46 AM ---------- Previous post was at 04:58 AM ----------
i can see the downloaded ffu in the recovery/properties table but the START button stays disabled even after clicking the loaded firmware....

To delete.

i followed them step by step and, got a green sd card, but when i select the xap and apply the mod, the wpcustom will just exit and there is no cahnge in the icon of hacked pfd, when launched, pfd will just run as usual(connects to ms etc)
in the links you give, im on #6, it will not go to #7, the registry is not opened after executing #6. i have pfd on SDCard, i havegreen sd card permission....
4.Now you can see “SD Card Permissions” as green color.
5.After changing SD Card permissions click on browse xap button.
6.Browse and select Custom_pfd.xap from SD card and click Apply XAP Button.
7.After successfully applying custom_pfd tool to preview for developers goto Preview for Developers apps.
8.Now your phone is hacked and you can edit registry of your WP8.1.
>> i will be trying this one now since it seems there is not much i can do,
1. Download Firmware update with this product code 059V3T3 it should be version 02540.00019.14484.37003
and variant name "RM-937 VAR APAC TW CV BLACK", note the color doesn't really matter, the part that
matters is RM-937 VAR APAC TW CV, the FW is the same, so the color won't make any difference,

To delete.

if u want flash !?
try Austrailian Firmware , latest with Denim and had field test features(2g/3g/4gsignal lock),hope this will work after Windows phone 10 update
dont try to check ##3282 code in ffu with winhex ,just download and flash,it may change crc value,file will corrupted,check australian FWs version number for u r device and download
Get Ready for next WP 10 Preview 2(coming Soon)

hi,
i had download firmware for my lumia 735 but product support tool for store 5 not recognized my smartphone.
Help me, please.

Sicily98IT said:
hi,
i had download firmware for my lumia 735 but product support tool for store 5 not recognized my smartphone.
Help me, please.
Click to expand...
Click to collapse
does your firmware detected check the path ,use supplied data cable only,uninstall nokia usb driver in controlpanel restart connect your device ,it will install drivers automatically ,use win 7 or higher,sure it will detect

Next Build For Phones Coming on tomorrow 10th April Friday at 10AM pst,check your insider app and check for update ..this build got great features ,how already updated to WP 10, Enter correct Values in patched preview app,because all devices supported now,you will update to your phones relevent image,
be sure to have 300MB sys freespace ,check in insider app if not try my tutorial

Hello I am taking that error
DEV_REPORTED_ERROR_DURING_PROGRAMMING: 0x00030003
Exception:
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: DEV_REPORTED_ERROR_DURING_PROGRAMMING: 0x00030003
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
Click to expand...
Click to collapse
My phone is stuck at recovery mode now. Can you help me please?

does your phone fully charged(>60%),you follow screen shots correctly,make your phone full charge (charge it for 2 hrs even though it's blank) then try again ,it will work-------------

billpao said:
Hello I am taking that error
Invalid response from device, incorrect message id
Exception:
Nokia.Murzim.InvalidResponseException: Invalid response from device, incorrect message id
bei Nokia.Murzim.Uefi.BootManager.MurzimBootManager.InfoQuery()
bei Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
bei Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
Click to expand...
Click to collapse
My phone is stuck at recovery mode now. Can you help me please?
Click to expand...
Click to collapse
i get the same error with my lumia 920. i want to go back to wp8.1 instead of wp10
problem is:
-) lumia software recovery tool cant connect to the phone (i should press vol down and power, but that just restarts my phone and it still wont be recognized)
-) windows phone recovery tool just restarts my phone 3 times and also says, that it cant connect to my phone (i should press vol down and power, but that just restarts my phone and it still wont be recognized)
-) nokia care suite 5 ****s up with the above error message.

freakedenough said:
i get the same error with my lumia 920. i want to go back to wp8.1 instead of wp10
problem is:
-) Lumia software recovery tool cant connect to the phone (i should press vol down and power, but that just restarts my phone and it still wont be recognized)
-) windows phone recovery tool just restarts my phone 3 times and also says, that it cant connect to my phone (i should press vol down and power, but that just restarts my phone and it still wont be recognized)
-) Nokia care suite 5 ****s up with the above error message.
Click to expand...
Click to collapse
Main and important step is Phone Should vibrate if Tool trying to flash
simple steps
1) first place Firmware Appropriate folder
2) go to recovery--> start ,it will check firmware files first time and popup will come to retry
3> at this time hold volume down first it become 0 and vibrates
simultaneously hold power button without leaving volume down
shutdown slider will come don't touch it and wait until display off
then release power button for 1 sec and repress immediately
phone will vibrates, tool will start flashing process
high end devices like 1520 will vibrate volume down+power press at a time
its depend upon device ,if at a time doesn't work follow above method