Database Users

[ERROR] DFT ANDROID SEND PARTITON DATA failed

I installed a NAND android rom but I didnt like it, so i downloaded a different one, went to usb flasher, ran the DFT android installer but then i get this:
Error Description: send partition data failed
Info: .\RSPL\RSPL.cpp (802)
Error Description: flash write failed
Info: .\RSPL\RSPL.cpp (586)
On the phone it told asked me if i wanted to clear an old partition so i pressed yes but still didnt work. I am new to this "flashing android to hd2", pls help this is getting very annoying

faizan445 said:
I installed a NAND android rom but I didnt like it, so i downloaded a different one, went to usb flasher, ran the DFT android installer but then i get this:
Error Description: send partition data failed
Info: .\RSPL\RSPL.cpp (802)
Error Description: flash write failed
Info: .\RSPL\RSPL.cpp (586)
On the phone it told asked me if i wanted to clear an old partition so i pressed yes but still didnt work. I am new to this "flashing android to hd2", pls help this is getting very annoying
Click to expand...
Click to collapse
try this : http://forum.xda-developers.com/showthread.php?t=945427

no workie
Looked promising but it didnt work, thanks for the reply tho

If you are using Vista or Win7,
you need to run the DFT.exe as Admin.
Right klick on DFT.exe
and then run as Administrator.

Im using winxp 32bit sp2 i still tried to run as admin but still not working... im going back to the SD version of android for now......

[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 .... ???

Failed to flash OLYFR_U4_1.2.6

Hello everyone,
I lost root after updating my Atrix (lesson learned the hard way) and I was trying to flash back to 1.26 to reroot using RSD Lite, but I keep getting "Error sending RAM download for bootloader". I tried some different settings mentioned in forums, I even did a factory restore as a hail mary, but I still get the same error message.
I'm not sure if this is related, but my SD card slot stopped detecting my cards (I tried 2).
Here is the error log from RSD Lite
20:04:54, May 18, 2011
Line: 976
ERROR: Phone[0000]: Error sending RAM download for bootloader. Device API Error: 0xE003003F Command: ADDR
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp
Device ID: 0
20:04:54, May 18, 2011
Line: 1194
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
20:04:54, May 18, 2011
Line: 610
ERROR: Flash failure: Phone[0000]: Error sending RAM download for bootloader. Device API Error: 0xE003003F Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
20:09:04, May 18, 2011
Line: 1506
ERROR: Error getting subscriber unit information.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
20:09:54, May 18, 2011
Line: 1506
ERROR: Error getting subscriber unit information.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Click to expand...
Click to collapse
Your help would be most appreciated.
Thanks.

hamooding said:
Hello everyone,
I lost root after updating my Atrix (lesson learned the hard way) and I was trying to flash back to 1.26 to reroot using RSD Lite, but I keep getting "Error sending RAM download for bootloader". I tried some different settings mentioned in forums, I even did a factory restore as a hail mary, but I still get the same error message.
I'm not sure if this is related, but my SD card slot stopped detecting my cards (I tried 2).
Here is the error log from RSD Lite
Your help would be most appreciated.
Thanks.
Click to expand...
Click to collapse
Not sure about your error, but Gingerbreak can be used to root any version of software on the phone. So you may not need to flash back down.

Hey man,
Thanks for the help, I tried to do gingerbreak but as I said, my SD card slot wasn't working, so I googled around, and found this: web.me.com/frankvanhuet/Site/Motorola_Atrix.html (cant link url, new user :S), anyways that fixed it up and I continued on to root and sideload. Hope this will help someone.
Thanks!

Hi there...my version is 4.1.2.6.
I want to install that gingerBlur rom and after reading what u posted i got a little scared to do so :/
But it seems that u got it working right? I thought I was doomed.
Ty for your answer it did help me

[Q] defy+, erased eMMC memory, realy dead

Hi all,
please forgive me for my bad english.
I done very stupid thing.
I mounted MMC from recovery console and after that formatted from PC
internal memory.
Now I can't turn on phone.
When I start RSD Lite and attach the phone I see only BLANK OMAP 3630.
It takes about 30 seconds. I tried to flash full SBF (dfp-231) with selected
TI blank flash option, but I have fail state and termination of communication with
phone.
I have attached a picture from RSDlite.
Here is a part of log from RSD lite:
04/22/12 01:53:07 Multi upgrade started for 1 phones
04/22/12 01:53:07 [Device ID: 0] Flashing phone.
04/22/12 01:53:20 ERROR: Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F - on device ID 0.
04/22/12 01:53:20 ERROR: Flash failure: Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F (Error Code: e003009f),
Detailed Error Details: Direction of the Error=1000, Command Value=0, Code Group Number=No Codegroup - on device ID 0.
04/22/12 01:53:20 [Device ID: 0] Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F
04/22/12 01:53:20 ERROR: Failed flashing process. - on device ID 0.
04/22/12 01:53:20 Multi upgrade finished.
Can someone help me, please?

RSd then config then flex options and tick to omap blank flash....
Sent from my MB526 using xda premium

Thank you,
but I wrote in my first post:
"I tried to flash full SBF (dfp-231) with selected
TI blank flash option."
I found similar thread but I didn't seen solution
http://forum.xda-developers.com/showthread.php?t=1203418&page=2
from other site
http://www.mod2xtreme.com/showthread.php?t=11397

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

racabgd said:
Thank you,
but I wrote in my first post:
"I tried to flash full SBF (dfp-231) with selected
TI blank flash option."
I found similar thread but I didn't seen solution
http://forum.xda-developers.com/showthread.php?t=1203418&page=2
from other site
http://www.mod2xtreme.com/showthread.php?t=11397
Click to expand...
Click to collapse
hey i have the same problem as u.....did u get a solution to this?

unfortunatelly
rahul_saklani said:
hey i have the same problem as u.....did u get a solution to this?
Click to expand...
Click to collapse
No, I got new one...
Regards,

racabgd said:
No, I got new one...
Regards,
Click to expand...
Click to collapse
but was there any explanation to dis problem......why does it happen?

read carefully my first post
rahul_saklani said:
but was there any explanation to dis problem......why does it happen?
Click to expand...
Click to collapse
*****************************************************
I done very stupid thing.
I mounted MMC from recovery console and after that formatted from PC
internal memory.
*****************************************************

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?