Database Users

Droid Ultra (possible Maxx) brick recovery

I want to post my findings here. It could be useful for developers playing with bootloaders, and for users who accidentally break their Droid.
DISCLAIMER: I am not responsible for any damage, caused to your phone, when you did something using information from this thread. Be extremely careful shorting any pins (and to do at YOUR OWN RISK)
There is two types of bricked device (by bricked I mean no fastboot available):
1. Device does not boot up, but responding to USB VIDID = 05c6:9008 = QHSUSB_DLOAD mode
This is qualcomm standard emergency download mode. This device become serial port (it is required drivers for Windows), and could be flashed with special protocol.
Attached is package which successfully recover Droid Ultra.
Once you see device with VIDID = 05c6:9008 = QHSUSB_DLOAD, you should run this command:
python qdload.py MPRG8960_MOTO.bin -ptf _ultra/partitions.txt
after this you should be able to use fastboot to flash desired official image back.
Tested on Windows, drivers for QHSUSB_DLOAD now included into package, serial port auto detection added, same command use. For both windows and linux you should have Python >= 2.6 installed, and PySerial installed.
2. Device not responding to USB, but start responding after battery disconnect (you need to disassemble your phone) as VIDID = 05c6:f006 = Qualcomm modem mode.
In most cases this mean that you has HARD bricked device. I still could not provide soft way to switch from this mode to QHSUSB_DLOAD mode, so currently with this situation you has only one possibility - is to find pin, which will force device to QHSUSB_DLOAD mode. For droid Ultra (and I believe Maxx) you could find this pin marked on picture attached. On my picture you could see, that I remove shield completely, but you could reach this pin by opening shield cup only. This is the shield near display connector. This pin should be grounded to force QHSUSB_DLOAD mode. Once you see device with VIDID = 05c6:9008 - STOP shorting pin to ground and follow unbrick 1 procedure.
If you not stopping SHORT ping to gound, you may have issues with uploading images in step 1 !!!
This both unbrick tested on Droid Ultra, but I assume it should work on Droid Maxx as well (I include _maxx folder with files for maxx).
Instruction to generate partitions.txt from working phone (Note you could have different name instead of mmcblk0):
1. adb shell dd if=/dev/block/mmcblk0 of=/sdcard/pt.bin bs=1024 count=10
2. adb pull /sdcard/pt.bin .
3. ./gpt_parser.py pt.bin > partitions.txt
Edit: Split package into 5 packages: 1. Image files for MAXX, 2 Image files for ULTRA, 3. Loader .bin for Motorola_8960 4. Window drivers for QHSUSB_DLOAD mode, 5. qdload.py script
qdload.py script updated to V1.2 with lot of usefull info printed.
move gpt_parser.py script to main post

VBlack said:
I want to post my findings here. It could be useful for developers playing with bootloaders, and for users who accidentally break their Droid.
DISCLAIMER: I am not responsible for any damage, caused to your phone, when you did something using information from this thread.
There is two types of bricked device (by bricked I mean no fastboot available):
1. Device does not boot up, but responding to USB VIDID = 05c6:9008 = QHSUSB_DLOAD mode
This is qualcomm standard emergency download mode. This device become serial port (it is required drivers for Windows), and could be flashed with special protocol.
Attached is package which successfully recover Droid Ultra.
Once you see device with VIDID = 05c6:9008 = QHSUSB_DLOAD, you should run this command:
python qdload.py MPRG8960.bin _ultra/partitions.txt
after this you should be able to use fastboot to flash desired official image back.
I didn't test it on Windows, but it could work, you just need to specify COM port, by additional parameter to qdload.py:
python qdload.py -tty COM10 MPRG8960.bin _ultra/partitions.txt
2. Device not responding to USB, but start responding after battery disconnect (you need to disassemble your phone) as VIDID = 05c6:f006 = Qualcomm modem mode.
In most cases this mean that you has HARD bricked device. I still could not provide soft way to switch from this mode to QHSUSB_DLOAD mode, so currently with this situation you has only one possibility - is to find pin, which will force device to QHSUSB_DLOAD mode. For droid Ultra (and I believe Maxx) you could find this pin marked on picture attached. On my picture you could see, that I remove shield completely, but you could reach this pin by opening shield cup only. This is the shield near display connector. This pin should be grounded to force QHSUSB_DLOAD mode. Once you see device with VIDID = 05c6:9008 - follow unbrick 1 procedure.
This both unbrick tested on Droid Ultra, but I assume it should work on Droid Maxx as well (I include _maxx folder with files for maxx).
Click to expand...
Click to collapse
WOW! Nice job, bud.
I would normally ask you to add a disclaimer to be extremely careful shorting any pins (and to do at YOUR OWN RISK), but anyone who needs to do this is already in a pickle, and their device useless.
Great work, impressive.

samwathegreat said:
WOW! Nice job, bud.
I would normally ask you to add a disclaimer to be extremely careful shorting any pins (and to do at YOUR OWN RISK), but anyone who needs to do this is already in a pickle, and their device useless.
Great work, impressive.
Click to expand...
Click to collapse
Done, I also add note about stop shorting this pin to ground once you get to QDL MODE, since it will cause eMMC instability, and may forbid to flash images.
Add: Package repacked with drivers for windows and updated version of qdload.py with windows serial port auto detection.

VBlack said:
I want to post my findings here. It could be useful for developers playing with bootloaders, and for users who accidentally break their Droid.
DISCLAIMER: I am not responsible for any damage, caused to your phone, when you did something using information from this thread. Be extremely careful shorting any pins (and to do at YOUR OWN RISK)
There is two types of bricked device (by bricked I mean no fastboot available):
1. Device does not boot up, but responding to USB VIDID = 05c6:9008 = QHSUSB_DLOAD mode
This is qualcomm standard emergency download mode. This device become serial port (it is required drivers for Windows), and could be flashed with special protocol.
Attached is package which successfully recover Droid Ultra.
Once you see device with VIDID = 05c6:9008 = QHSUSB_DLOAD, you should run this command:
python qdload.py MPRG8960.bin _ultra/partitions.txt
after this you should be able to use fastboot to flash desired official image back.
I didn't test it on Windows, but it could work, you just need to specify COM port, by additional parameter to qdload.py:
python qdload.py -tty COM10 MPRG8960.bin _ultra/partitions.txt
Tested on Windows, drivers for QHSUSB_DLOAD now included into package, serial port auto detection added, same command use. For both windows and linux you should have Python >= 2.6 installed, and PySerial installed.
2. Device not responding to USB, but start responding after battery disconnect (you need to disassemble your phone) as VIDID = 05c6:f006 = Qualcomm modem mode.
In most cases this mean that you has HARD bricked device. I still could not provide soft way to switch from this mode to QHSUSB_DLOAD mode, so currently with this situation you has only one possibility - is to find pin, which will force device to QHSUSB_DLOAD mode. For droid Ultra (and I believe Maxx) you could find this pin marked on picture attached. On my picture you could see, that I remove shield completely, but you could reach this pin by opening shield cup only. This is the shield near display connector. This pin should be grounded to force QHSUSB_DLOAD mode. Once you see device with VIDID = 05c6:9008 - STOP shorting pin to ground and follow unbrick 1 procedure.
If you not stopping SHORT ping to gound, you may have issues with uploading images in step 1 !!!
This both unbrick tested on Droid Ultra, but I assume it should work on Droid Maxx as well (I include _maxx folder with files for maxx).
Click to expand...
Click to collapse
This is great!! Mind if i add it here? With proper credits of course? Or quote you?
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057

Sure, no problem, but you need your own set of files for moto x (could be obtained from fastboot oficial image), and partitions.txt.
partitions.txt you could obtain using following instruction from working phone:
1. adb shell dd if=/dev/block/mmcblk0 of=/sdcard/pt.bin bs=1024 count=10
2. adb pull /sdcard/pt.bin .
3. ./gpt_parser.py pt.bin > partitions.txt
Edit: gpt_parser moved to main post.

VBlack said:
I want to post my findings here. It could be useful for developers playing with bootloaders, and for users who accidentally break their Droid.
DISCLAIMER: I am not responsible for any damage, caused to your phone, when you did something using information from this thread. Be extremely careful shorting any pins (and to do at YOUR OWN RISK)
There is two types of bricked device (by bricked I mean no fastboot available):
1. Device does not boot up, but responding to USB VIDID = 05c6:9008 = QHSUSB_DLOAD mode
This is qualcomm standard emergency download mode. This device become serial port (it is required drivers for Windows), and could be flashed with special protocol.
Attached is package which successfully recover Droid Ultra.
Once you see device with VIDID = 05c6:9008 = QHSUSB_DLOAD, you should run this command:
python qdload.py MPRG8960.bin _ultra/partitions.txt
after this you should be able to use fastboot to flash desired official image back.
I didn't test it on Windows, but it could work, you just need to specify COM port, by additional parameter to qdload.py:
python qdload.py -tty COM10 MPRG8960.bin _ultra/partitions.txt
Tested on Windows, drivers for QHSUSB_DLOAD now included into package, serial port auto detection added, same command use. For both windows and linux you should have Python >= 2.6 installed, and PySerial installed.
2. Device not responding to USB, but start responding after battery disconnect (you need to disassemble your phone) as VIDID = 05c6:f006 = Qualcomm modem mode.
In most cases this mean that you has HARD bricked device. I still could not provide soft way to switch from this mode to QHSUSB_DLOAD mode, so currently with this situation you has only one possibility - is to find pin, which will force device to QHSUSB_DLOAD mode. For droid Ultra (and I believe Maxx) you could find this pin marked on picture attached. On my picture you could see, that I remove shield completely, but you could reach this pin by opening shield cup only. This is the shield near display connector. This pin should be grounded to force QHSUSB_DLOAD mode. Once you see device with VIDID = 05c6:9008 - STOP shorting pin to ground and follow unbrick 1 procedure.
If you not stopping SHORT ping to gound, you may have issues with uploading images in step 1 !!!
This both unbrick tested on Droid Ultra, but I assume it should work on Droid Maxx as well (I include _maxx folder with files for maxx).
Click to expand...
Click to collapse
this should be stickied for all of android. while i realize your methods were device specific, i'm guessing there are enough similarities in your situation that it can be applied globally.

640k said:
this should be stickied for all of android. while i realize your methods were device specific, i'm guessing there are enough similarities in your situation that it can be applied globally.
Click to expand...
Click to collapse
It is Qualcomm specific. Most of current Qualcomm chips has emergency download mode. the only problem is to have proper load file MPRG8960.bin is for 8960 chips family, and looks like Motorola specific (maybe I'm wrong). So for sure not all Android device could use this, but most Qualcomm device should be fine, you just need model specific set of files, which, for example, Motorola provides with fastboot flashable images.

good points and good observations. this thread definitely shouldn't get buried in a single (aging) device. there's good info here.

I don't know if it is a problem, but I used this script to try and unbrick my phone.
When running as #1 as you state above, there is a "finished with errors" after the script. So I looked at it and saw that "MPRG8960.bin" was going to be pushed to the phone and the next line states "File not found "MPRG8960.bin." Looking at the files, the file it was looking for was named "MPRG8960_MOTO.bin," so I changed it to the file it was looking for and it worked great.
I'm a noob when it comes to the guts of programming and utilities, but it's something I spotted and figured I would let you know.

This seems really promising for my bricked xt907...

HamBone625 said:
This seems really promising for my bricked xt907...
Click to expand...
Click to collapse
Op has no fix files for the M, they have never been leaked.

HamBone625 said:
This seems really promising for my bricked xt907...
Click to expand...
Click to collapse
Since XT907 use same Qualcomm chip MSM8960 - you could try to use this utility, but first you need to obtain partitions.txt from working XT907 according to instructions.
Files needed you could take from latest firmware package (sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn, rpm.mbn, emmc_appsboot.mbn is aboot.mbn)

MOTO X
Hi. Can somebody post the partitions.txt for the moto X? please
To get the partition.txt from a working moto X it has to be root?
thanks

When I execute the script on my Droid Mini, with their proper partitions txt file and the MBN files from the ULTRA, I got this:
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com64
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960_MOTO.bin' to addr 0x2a000000...
Executing...
Found TTY port: com64
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending secureMode...
Sending openMulti ...
LOG: Open multi failed, unknown error
ERROR: 0x00000007: Open multi failed, unknown error
Sending SBL Reset...
Done, with errors!!!

Where I can get the MBN files for a Droid Mini?

Hi, you could try to find it inside one of official (fastboot) package for empty flashing like in Ultra package. It fails in very strange place - I will look at it on Monday.
Sent from my XT1080 using Tapatalk

VBlack said:
Hi, you could try to find it inside one of official (fastboot) package for empty flashing like in Ultra package. It fails in very strange place - I will look at it on Monday.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I tried the MBN files from a 4.4 fastboot from an Ultra and from the Droid Mini too, but i'm getting this errors, I don't know what's wrong or what I'm doing worng.
My phone powers up and can enter to fastboot, but it fails to boot, when i use "fastboot reboot" it reboot to QHSUSB_DLOAD... but well, something is wrong,,,

HELP
When i do the third step yo obtain partitions.txt (./gpt_parser.py pt.bin > partitions.txt)
i got a message
can't create partitions.txt: Read-only file system
any help?

C:\droid_ultra>python qdload.py MPRG8960_MOTO.bin -ptf _ultra/partitions.txt
'python' is not recognized as an internal or external command,
operable program or batch file.

BUZZAPT said:
When i do the third step yo obtain partitions.txt (./gpt_parser.py pt.bin > partitions.txt)
i got a message
can't create partitions.txt: Read-only file system
any help?
Click to expand...
Click to collapse
You should execute it on PC in writable folder.
Sent from my XT1080 using Tapatalk

[GUIDE] Debrick: Hard Bricked YU Yureka

I will support this method. Please note that the following are UNOFFICIAL steps and these will not be supported officially...So don't mention about this to Customer Care​
xdafirmware.com posted two CPBs for Yureka & Yureka Plus & claimed that it is possible to flash them using YGDP. I don't have any bricked one near by, so can you please check?
Flashed a Yureka Plus via fastboot & it looks ok: http://pastebin.com/RtCSQCB7
Click to expand...
Click to collapse
Thanks to @Titokhan for reporting and Testing.
Here is the link for Yureka: http://xdafirmware.com/yu-yureka-ao5510

This method has been shared by DoomLord. Please note that the following are UNOFFICIAL steps and these will not be supported officially...So don't mention about this to Customer Care
Setting up
Step 1] Install QPST (2.7.422) tool - We will be using the QFIL tool which is part of QPST package
Step 2] Install the Qualcomm Download Mode Driver 9008 on Windows PC
The required drivers are in the folder QualcommDownloadModeDriver_9008
For 32-bit Windows OS open Allx86 & double click on dpinst32.exe to start the driver installer (accept all prompts)
For 64-bit Windows OS open Allx64 & double click on dpinst32.exe to start the driver installer (accept all prompts)​
Boot YUREKA to Qualcomm HS-USB QDLoader 9008 mode
Note: This is a forced Download mode which is different from normal mode, so this is a must step !
Step 1] Power off the device/remove the battery and the re-insert after few seconds.
Step 2] Open the back cover, unscrew all the screws for the inner cover. Pry open the inner cover to expose the 6 tap points next to the headset plug.
Step 3] With the battery connected, short the top two tap points on the right side, This is illustrated in the attached image.
Step 4] With the two tap points shorted, plugin the USB cable. The device will enter (9008) QDL mode. If the Qualcomm driver is installed correctly, the device will show up as a serial device.
Flashing YUREKA Hard-brick Recovery files in Qualcomm HS-USB QDLoader 9008 mode
Note: The files needed for low level device recovery are in the YUREKA_Bootloader_Recovery folder, keep the folder in root of any drive (because: there shouldn't be any space in folder location).
Step 1] Open the QFIL tool, if you complete previous steps correctly, it will detect the device as: Qualcomm HS-USB QDLoader 9008 (COMx)
{
"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"
}
Step 2] In Select Programmer path browser to the folder with those files and select: prog_emmc_firehose_8936.mbn
Step 3] The Select Build section will automatically select the base folder with those files
Step 4] Now click on Load XML
Step 4a] First you will be asked to select the RawProgram file, browse to the folder with those files and select rawprogram0.xml
Step 4b] Next you will be asked to select the Patch file, browse to the folder with those files and select patch0.xml
Step 5] Finally click on “Download” to start the flashing process.
Keep watching the Status log, After flashing is over the following status log will be shown:
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 52.9502MB
Throughput: 10.59004M/s
Reset Phone
Waiting for reset done...​Step 6] The device will now boot and get stuck at the YU boot logo! The device will be continuously vibrating
Congratulations the device is now revived!
Step 7] Close the QFIL program, Disconnect the device and remove the battery for few seconds
Step 8] Reinsert the battery and now keeping the VOLUME UP button pressed connect device to PC – this will trigger FASTBOOT mode
Step 9] Now flash Lollipop (64-bit) factory images via fastboot!
Thanks to:
DooMLoRD for the Actual process.
tirta.agung and
XDAReserved

You may want give an idea how to do this
short the top two tap points on the right side not everyone is a knows about electrical stuff
I would recommend a copper wire for this two to work

Zenns said:
You may want give an idea how to do this
short the top two tap points on the right side not everyone is a knows about electrical stuff
I would recommend a copper wire for this two to work
Click to expand...
Click to collapse
Yes, addon advises are welcome to make it easy, but in the first place it is not for noob !
Noob users can get the replacement, instead wondering in unknown plane.
That is why @DooMLoRD have not given files, and only hinted how to .

Not working.
Sahara failSahara fail everytime.

shekhawat2 said:
Sahara failSahara fail everytime.
Click to expand...
Click to collapse
Just recently joint and want to try the hard process, Please call CC and get the replacement.

quakze said:
Just recently joint and want to try the hard process, Please call CC and get the replacement.
Click to expand...
Click to collapse
I am trying this process from last 4 days from here: http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040 but getting the same error every time. :crying:
I have called CC, ill get replacement after few days, till then i want to try with it bricked, so that i can unbrick it myself next time as it was my 2nd time i hardbricked it. If you can, please help me.

shekhawat2 said:
I am try this process from last 4 days from here: http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040 but getting the same error every time. :crying:
I have called CC, ill get replacement after few days, till then i want to try with it bricked, so that i can unbrick it myself next time as it was my 2nd time i hardbricked it. If you can, please help me.
Click to expand...
Click to collapse
I am busy with porting tonight, will work with you tomorrow.
BTW, send a private massage about ur contact details, so that we can have a chat while debricking.

@quakze Just one question Yureka has MSM 8939 and these files are for MSM 8936. So this means that both these means snapdragon 610 and 615 share same firehose files.

quakze said:
I am busy with porting tonight, will work with you tomorrow.
BTW, send a private massage about ur contact details, so that we can have a chat while debricking.
Click to expand...
Click to collapse
This is the error i am getting:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download

Need help. I juat only need qfil thats all i have everything except that qfil please gv me a link.

sahara error
Sahara error.
This is the error i am getting:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(S tring sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownload ArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download

ud3240 said:
Sahara error.
This is the error i am getting:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(S tring sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownload ArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Don't skip this step !
Boot YUREKA to Qualcomm HS-USB QDLoader 9008 mode
Note: This is a forced Download mode which is different from normal mode, so this is a must step !
Step 1] Power off the device/remove the battery and the re-insert after few seconds.
Step 2] Open the back cover, unscrew all the screws for the inner cover. Pry open the inner cover to expose the 6 tap points next to the headset plug.
Step 3] With the battery connected, short the top two tap points on the right side, This is illustrated in the attached image.
Step 4] With the two tap points shorted, plugin the USB cable. The device will enter (9008) QDL mode. If the Qualcomm driver is installed correctly, the device will show up as a serial device.

quakze said:
Don't skip this step !
Boot YUREKA to Qualcomm HS-USB QDLoader 9008 mode
Note: This is a forced Download mode which is different from normal mode, so this is a must step !
Step 1] Power off the device/remove the battery and the re-insert after few seconds.
Step 2] Open the back cover, unscrew all the screws for the inner cover. Pry open the inner cover to expose the 6 tap points next to the headset plug.
Step 3] With the battery connected, short the top two tap points on the right side, This is illustrated in the attached image.
Step 4] With the two tap points shorted, plugin the USB cable. The device will enter (9008) QDL mode. If the Qualcomm driver is installed correctly, the device will show up as a serial device.
Click to expand...
Click to collapse
Bro i done all the steps including that shorting 2 Points. As i said my YU was detected as qual 9008 But final reaults is fail. Sahara error

ud3240 said:
As i said my YU was detected as qual 9008 But final reaults is fail. Sahara error
Click to expand...
Click to collapse
It will be detected as qual 9008, without shorting the two points also !

How??
quakze said:
It will be detected as qual 9008, without shorting the two points also !
Click to expand...
Click to collapse
Oh Really?? How?? Tell me procedure I will definitely try. Help me and have you unbrick your phone using this method? Help

Thank you for this guide but I'm unsure if i go throgh with this or not because theres A Yu sticker on one of the screws and i believe they will not consider the warranty if i take it out.
I hardbricked the phone today while updating from CM11 to CM12 via flash tool fastboot windows method. Now nothing happens. The led light doesnt light up when charging,no screen shows and nothing is detected on pc.
Still waiting for the callback from Yu. Lets see

zeeshanonlyme said:
Thank you for this guide but I'm unsure if i go throgh with this or not because theres A Yu sticker on one of the screws and i believe they will not consider the warranty if i take it out.
I hardbricked the phone today while updating from CM11 to CM12 via flash tool fastboot windows method. Now nothing happens. The led light doesnt light up when charging,no screen shows and nothing is detected on pc.
Still waiting for the callback from Yu. Lets see
Click to expand...
Click to collapse
Take a sharp knife or compass remove the whole sticker without damaging it.
And its a home pickup, so no technician will be there to check, but carrier guy !
Try this in the mean time, UR phone is getting replaced by YU.

quakze said:
Take a sharp knife or compass remove the whole sticker without damaging it.
And its a home pickup, so no technician will be there to check, but carrier guy !
Try this in the mean time, UR phone is getting replaced by YU.
Click to expand...
Click to collapse
Ya but say while taking out the sticker i damaged it, will my warranty be void?
And how long did it take for yours to get replaced?

zeeshanonlyme said:
Ya but say while taking out the sticker i damaged it, will my warranty be void?
And how long did it take for yours to get replaced?
Click to expand...
Click to collapse
No technician will come to check the phone while replacing at UR door step, so be cool and go ahead and try.
If U get the waybill no. in first three days, it will take total 10 - 12 days !

Problem ROM LENOVO YOGA TABLET 2

Hello guys!
A person of my family has bought a Lenovo Yoga Tablet 2 1050F from China. The problem is there are only chinese and english language to select. The firmware are chinese, and i have downloaded a firmware with multilanguage from NEEDROM.
I not know how can i flash this firmware, I have instaled Phone Flash Tool 4.4.4., but when I try to start flash and the device it reboots in Flashboot mode, my computer not detect the device, and the operation finish without any profit result for me.
Device start normal boot when I unplug the usb cable.
Thank for all.
ABOUT DEVICE:
- Model number: YOGA Tablet 2-150F
- Android 4.4.2
- Software version: YOGA Tablet 2-1050f_150428
- Build number: YOGATablet2-1050F_S000175_150428
Serial Num: BaytrailD482531E
DROIDBOOT VERSION 2.0
PRODUCT: YT2_10_PR
Please, help me.

Best to install adb and fastboot.
Do adb devices from command prompt and see if they it displays your device
You need to go on to device manager when you phone is in fastboot mode, connected to your PC. There WILL be a ! Next to your device.
Click update driver and then select from my PC Not windows update. Select the the driver installed when in normal mode and select adb driver
Sent from my SM-G901F using Tapatalk

Hi Rob
VictorVL90
In the settings when you go to Language and input,can you change to the language you want there.

pug1 said:
Best to install adb and fastboot.
Do adb devices from command prompt and see if they it displays your device
You need to go on to device manager when you phone is in fastboot mode, connected to your PC. There WILL be a ! Next to your device.
Click update driver and then select from my PC Not windows update. Select the the driver installed when in normal mode and select adb driver
Sent from my SM-G901F using Tapatalk
Click to expand...
Click to collapse
work, but... stop at 26%
02/24/16 20:09:15.881 INFO : Phone Flash Tool V 4.4.4-1 Win32 External (build on Mon Apr 28 09:56:35 UTC 2014)
02/24/16 20:09:15.881 INFO : Using xFSTK version: 1.5.3
02/24/16 20:09:15.959 INFO : Using Android Debug Bridge version 1.0.31
02/24/16 20:09:15.959 INFO : OS version detected: Windows 8 (x64)
02/24/16 20:09:16.147 INFO : Adb and fastboot binaries OK
02/24/16 20:09:16.147 INFO : Phone Flash Tool initialized successfully
02/24/16 20:09:16.163 INFO : Loading Flash file ...
02/24/16 20:09:16.163 INFO : Ready to flash!
02/24/16 20:09:40.479 INFO : Loading Flash file (C:/Users/Víctor Valle/Downloads/YOGA-Tablet-2-1050F/YOGA-Tablet-2-1050F/target_bin/flash.xml)
02/24/16 20:09:40.479 INFO : GP_Flag is set to 0x80000045
02/24/16 20:09:40.479 INFO : Ready to flash!
02/24/16 20:09:46.464 INFO : Port 0/3: Flashing OS
02/24/16 20:09:46.464 INFO : Port 0/3: fastboot -s INTD482531E flash osloader "C:/Users/Víctor Valle/Downloads/YOGA-Tablet-2-1050F/YOGA-Tablet-2-1050F/target_bin/efilinux.efi"
02/24/16 20:09:48.604 INFO : Port 0/3: fastboot -s INTD482531E boot "C:/Users/Víctor Valle/Downloads/YOGA-Tablet-2-1050F/YOGA-Tablet-2-1050F/target_bin/droidboot.img"
02/24/16 20:09:51.381 INFO : Port 0/3: sleep 25000 ms
02/24/16 20:10:16.384 INFO : Port 0/3: fastboot -s INTD482531E oem wipe ESP
02/24/16 20:13:56.682 WARNING: Port 0/3: Process TIMEOUT Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s INTD482531E oem wipe ESP"
02/24/16 20:13:58.690 WARNING: Port 0/3: Retry to execute fastboot -s INTD482531E oem wipe ESP
Click to expand...
Click to collapse

VictorVL90 said:
work, but... stop at 26%
Click to expand...
Click to collapse
Have you installed http://forum.xda-developers.com/showthread.php?p=48915118#post48915118.
I use this method without fail on win10 pro
Sent from my SM-G901F using Tapatalk

Try using this Rom , tinyurl.com/hn9m7rc
also copy the easyimage zip file in the download to a memory card in the tablet to enable you to set the country code.
It is clean,it's the one I used.

pug1 said:
Have you installed http://forum.xda-developers.com/showthread.php?p=48915118#post48915118.
I use this method without fail on win10 pro
Sent from my SM-G901F using Tapatalk
Click to expand...
Click to collapse
GREAT! Tablet work full 100%
Thanks!

One more question...
Occasionally, the System try to update a patch, but the installation always failure. What can i do for prevent this automatically update?

VictorVL90 said:
One more question...
Occasionally, the System try to update a patch, but the installation always failure. What can i do for prevent this automatically update?
Click to expand...
Click to collapse
Usually you are asked if you want to install the update,just say no.

VictorVL90 said:
One more question...
Occasionally, the System try to update a patch, but the installation always failure. What can i do for prevent this automatically update?
Click to expand...
Click to collapse
Are you on stock unrooted firmware? If so you could try going into stock recovery and factory reset. Then try to let the update install. I would always go with an update.

corasman said:
Usually you are asked if you want to install the update,just say no.
Click to expand...
Click to collapse
Impossible to say no. It appears on the screen counts down and automatically restart.

All is correct. I have rooted the device and i have frozen the process that causes update.
Now I can say that everything is correct.
Very thanks!

[GUIDE][REDMI 3] Backup eMMC and install unlocked bootloader with TWRP

Simplest method of backup eMMC and install unlocked bootloader with TWRP.
May be used for locked and unlocked devices.
Devices: Redmi 3 and Redmi 3 Pro.
Benefits of this method:
1) no need device unlock
2) no need to install MiFlash/MiPhone
3) not need to download and install any ROM
4) it requires only one reboot
Manual:
1) unpack ZIP-file "redmi3_emmcdl_twrp.zip"
2) connect the device to a computer via USB
3) by holding down VolUp + Power run preloader and select "download"
4) if you installed the drivers in the Device Manager, you should see the device "Qualcomm HS-USB QDLoader 9008 (COM21)"
5) in Windows Explorer, open the folder that contains the previously unzipped file emmcdl.exe
6) do partial backup of eMMC: execute dump_emmc.cmd (the first 200 MB is enough)
7) do backup system partitions: execute dump_parts.cmd
8) the contents of the folder dump_emmc and dump_parts need to copy in a safe place!
9) [OPTIONAL] do install the patched bootloader and a special version of TWRP: execute install_aboot_twrp.cmd
10) now you need to reboot the device (you hold VolUp + Power button)
11) [OPTIONAL] boot into TWRP and make a backup current installed firmware (boot, system, data, cust)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After these actions should not be flashing the ROMs, which contains a emmc_appsboot.mbn and any MBN-files !!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Waiting for English manual.......... an method to quickly backup/restore bootloader lock state would come really useful as even custom ROMs seem randomly relock BL and unlocking procedure is becoming pita
Sent from my phone by Tapatalk

Downloading flash programmer: prog_emmc_firehose_8936.mbn
Successfully open flash programmer to write: prog_emmc_firehose_8936.mbn
Expecting SAHARA_END_TRANSFER but found: 0
!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!
Dumping data to file .\dump_parts\aboot.img
Dumping at start sector: 0 for sectors: 0 to file: .\dump_parts\aboot.img
Programming device using SECTOR_SIZE=512
<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="1048576"/></data>

After backup, how do i restore flashed image?

Do you have the source code of emmcdl.exe?
Can we do this on a linux box?

yangyangnau said:
Do you have the source code of emmcdl.exe?
Can we do this on a linux box?
Click to expand...
Click to collapse
https://github.com/binsys/emmcdl

Thank you, installing now CM13 on Redmi3pro (ido)
Just done my Redmi3 pro with your fine tool. Working like a charm, thank you! Now I'm installing my beloved CM13 on this device - so glad!! You are my hero! :highfive:

Does this mean we do not have to ask a unlock bootloader from Xiaomi?

parphane said:
Does this mean we do not have to ask a unlock bootloader from Xiaomi?
Click to expand...
Click to collapse
@remittor any answer?

parphane said:
Does this mean we do not have to ask a unlock bootloader from Xiaomi?
Click to expand...
Click to collapse
This, please update anyone?

I had error message:
error driver qdloader not found
Press any key to continue
In my device driver redmi 3 was detected as Quallcom hs USB qdloader 9008 com 21
Any ideas to solve my problem

edmone said:
I had error message:
error driver qdloader not found
Press any key to continue
In my device driver redmi 3 was detected as Quallcom hs USB qdloader 9008 com 21
Any ideas to solve my problem
Click to expand...
Click to collapse
I have the same problem...

can someone upload this file to another host..funny i try 23 times to download and in 96% download stopped

parphane said:
Does this mean we do not have to ask a unlock bootloader from Xiaomi?
Click to expand...
Click to collapse
1. This means you shouldn't ask anyone to what you want with your own things
2. This means you shouldn't wipe all your data to 'unlock' what had not intended to have any locks once you bought it to your ownership
3. This means you shouldn't backup (nor 'sync') all your personal data to the Google cloud services just to save them from erasure upon unlocking.
All these bootloader locks have nothing to secure. There is no real problem to solder off eMMC (eMCP) IC and read out all your 'secret' personal data with a HW eMMC/NAND programmer or even generic SD card reader (tiny soldering req'd) for any phone/tab/other MID. The only reason mfr's do solder generic SD's in the BGA cases (called eMMC), hide docs, implement locks, close full file system from user even for reading and exploring and do a bunch of other bad things is intention to force user send all his sensitive personal data to the Google's and other OS/Dev mfr's clouds to make them able to fully control any people's activity. It's a Matrix guys who wants to control your brain and soul not simply some cheap device. Don't give up! Do not 'sync' your personal data with any clouds and do not use any 'accounts' and Gapps at all where possible!
Thank you remittor for the perfect method!
There is also should be used to backup any device's partition's, whole media and state. It will greatly help to recover data in case of the device's SW and even partly eMMC failure. Once a patched aboot will give us ability to write the whole eMMC media, there should be the way to fix OEM's locking data structure to locking back in any cases (e.g. flashing original non-patched aboot). One could find the locking flags and publish results.

remittor said:
Simplest method of backup eMMC and install unlocked bootloader with TWRP.
May be used for locked and unlocked devices.
Devices: Redmi 3 and Redmi 3 Pro.
Benefits of this method:
1) no need device unlock
2) no need to install MiFlash/MiPhone
3) not need to download and install any ROM
4) it requires only one reboot
Manual:
1) unpack ZIP-file "redmi3_emmcdl_twrp.zip"
2) connect the device to a computer via USB
3) by holding down VolUp + Power run preloader and select "download"
4) if you installed the drivers in the Device Manager, you should see the device "Qualcomm HS-USB QDLoader 9008 (COM21)"
5) in Windows Explorer, open the folder that contains the previously unzipped file emmcdl.exe
6) do partial backup of eMMC: execute dump_emmc.cmd (the first 200 MB is enough)
7) do backup system partitions: execute dump_parts.cmd
8) the contents of the folder dump_emmc and dump_parts need to copy in a safe place!
9) [OPTIONAL] do install the patched bootloader and a special version of TWRP: execute install_aboot_twrp.cmd
10) now you need to reboot the device (you hold VolUp + Power button)
11) [OPTIONAL] boot into TWRP and make a backup current installed firmware (boot, system, data, cust)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After these actions should not be flashing the ROMs, which contains a emmc_appsboot.mbn and any MBN-files !!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
hello, redmi 3s prime penguin logo only shows please say solution without any mobile data loss contact - 9106142185

[FIX][LUMIA]Dead Phone,Bricked bootloader,infinite boot loop,Boot Failed etc.

Hello all lumia owners ,with the release of windows phone internals there is a great rush to unlock bootloader and install custom rim.
In previous post I have posted about unlocking bootloader and enabling root access but what if you have bricked your lumia?
In That case Please read this thread and fix your lumia.
Lumia can be bricked by bad updating phone or disconnection in update or something else it might also be bricked by flashing custom Rom.
REQUIREMENTS
1.Windows Device Recovery Tool (WDRT)- Get it here
2.FFU image for your phone.(Larger than 1gb)(If you have custom rom then skip ffu image and jump to method 2) - check here
3.Drivers (Installed with WDRT)
Instruction
Method 1
1.Install WDRT and run it.
2.Dont Connect your phone, just click on I can''t find my device button.
3.Let it to Search for a Device.
4.Connect your device via USB cable.
4.Start Up your lumia by pressing power button.
5.If it is not starting,Struck on logo,or just a boot loop it can be read by WDRT.
6.WDRT will show device with unknown manufacturer, o's version etc.
7.Dont Flash software with it Just close it.
8.Go to http://www.lumiafirmware.com/info and read all instruction and follow it to manual flash flu file.
9.Wait Until all is done and reply if this fixed your lumia.
Method 2 (Easy)
If you didn bricked your device in flashing or unlocking bootloader then Its better to jump out method 1 as it is more easy for you.
Or if you have custom rom for your phone and not want to download full original ffu then stay here.
1. Install Windows device recovery tool.
2. Go to :
For 32bit window.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
For 64bit window.
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
Or whatever install folder you selected.
3. Hold shift and right click on your mouse and click open command windows here.
4. Paste thor2 -mode uefiflash -ffufile " " in cmd and click enter.(This will start searching your phone)
4. Press And Hold Poweroff + Lower Volume Button (Dont release it if your phone turn on automatically)(Especially in Bootloop).
5. Connect your phone to PC ( of course using USB cable).
6. if it detect Your device it will take you to Flash Screen (Ignore errors as it appear becuase in ffu location we take " " and its completely normal.)
7. Run Windowsphone internals and now it will detect your phone in flash mode.
8. Now you can Flash Custom rom (if bootloader unlocked) or just flash stock ffu image (dont need unlocked bootloader.)
Done
I will try to find more and more method to fix brick lumia until then this method is best or just send device to service center if this didn't fixed.

Greetings;
the *.ffu file won't be found at: http://www.lumiafirmware.com/info (for most devices).
That's some misleading website info; copied to several tutorials.
Reference: "Tutorial: Unbrick Lumia Devices"
Considering your System drive is " C: "
Open: C:\Program Data\Microsoft\Packages\Products\RM-<Number>
* Where <Number> will be your device release model number.
Note: You can check Code & Release Model Number on the back of your phone by removing your battery.
Inside that folder you can see that you have some required files to recover your device from Bricked states.
i.e: the *.ffu file.

Hi,
My phone crashed during the bootloader unlock process. I think My hex codes were not in sync with the ffu.
Now my PC does not detect the phone enither does it vibrates or shows any activity on the screen.
When I tried the above methods, I get the following error message.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile " "
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile
Process started Sat Jun 17 05:30:45 2017
Logging to file C:\Users\siddh\AppData\Local\Temp\thor2_win_20170617053045_ThreadId-10580.log
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
Operation took about 1 minute, 0 seconds.
THOR2_ERROR_NO_DEVICE_WITHIN_TIMEOUT
THOR2 1.8.2.18 exited with error code 84003 (0x14823)
Is there any way I can create a temporary bus between the phone and that thor utility to send a bootloader handshake?

Hi,
My phone crashed during the bootloader unlock process. I think My hex codes were not in sync with the ffu.
Now my PC does not detect the phone enither does it vibrates or shows any activity on the screen.
When I tried the above methods, I get the following error message.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile " "
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile
Process started Sat Jun 17 05:30:45 2017
Logging to file C:\Users\siddh\AppData\Local\Temp\thor2_win_201706 17053045_ThreadId-10580.log
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
Operation took about 1 minute, 0 seconds.
THOR2_ERROR_NO_DEVICE_WITHIN_TIMEOUT
THOR2 1.8.2.18 exited with error code 84003 (0x14823)
what i do now? is that any way to recreat my lumia phone?

swapnilnaikwadi said:
Hi,
My phone crashed during the bootloader unlock process. I think My hex codes were not in sync with the ffu.
Now my PC does not detect the phone enither does it vibrates or shows any activity on the screen.
When I tried the above methods, I get the following error message.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile " "
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile
Process started Sat Jun 17 05:30:45 2017
Logging to file C:\Users\siddh\AppData\Local\Temp\thor2_win_201706 17053045_ThreadId-10580.log
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
Operation took about 1 minute, 0 seconds.
THOR2_ERROR_NO_DEVICE_WITHIN_TIMEOUT
THOR2 1.8.2.18 exited with error code 84003 (0x14823)
what i do now? is that any way to recreat my lumia phone?
Click to expand...
Click to collapse
Same problem? did you find a solution?

YOU ARE THE MAN.
my 930 was bricked by wpinternals misuse and this simple guide fixed it!!
my nokia was completely dead, and you sir, saved my 930 with this recommended guide!!

rgxHost said:
Greetings;
the *.ffu file won't be found at: http://www.lumiafirmware.com/info (for most devices).
That's some misleading website info; copied to several tutorials.
Reference: "Tutorial: Unbrick Lumia Devices"
Considering your System drive is " C: "
Open: C:\Program Data\Microsoft\Packages\Products\RM-<Number>
* Where <Number> will be your device release model number.
Note: You can check Code & Release Model Number on the back of your phone by removing your battery.
Inside that folder you can see that you have some required files to recover your device from Bricked states.
i.e: the *.ffu file.
Click to expand...
Click to collapse
if it is possible to recover data from a damaged lumia, I do not want to lose data

Greetings; using Nokia firmware tool will reset your device to factory settings (on mine, reverts back to windows 8).
Best regards;

Hi all, i have a bricked lumia 1320 with samsung emmc. When i power it on, it says: unable to find boot options
This problem started when i downgraded from windows 10 mobile to lumia denim using WDRT. The flashing procedure went well and, at reboot, the error message appeared on screen.
i've tried with thor2, windows phone internals, WDRT to unbrick the device but i failed. Do you have other suggestions? I read that exists a way to restore the device using jtag or atf box but i don't want to buy a 100$ peripheral for a one-time procedure

I made a program that unbricks your device, recovers from QHSUSB_DLOAD, QHUSB_DLOAD.
It's called...
Windows Phone Unbrick Tool (WPUT)
It comes with an installer.
NOTE:
1. You should enter the license key that is provided in the License Agreement section (for checking that you are not a bot, so don't use autoinstaller!
2. You must download your emergency HEX and MBN files from lumiafirmware.com
3. You must specify the correct path to the HEX/MBN files otherwise the program will fail!
4. If the unbricking succeeds remove your battery from your device for 1 minute and put it back on
5. Charge the device for at least 30 minutes before turning it on!
6. Reflash your device with Windows Device Recovery Tool.
Download it here
b i t . l y / 2 O Y Q Z V R
(REMOVE THE SPACES)

gmirz2005 said:
I made a program that unbricks your device, recovers from QHSUSB_DLOAD, QHUSB_DLOAD.
It's called...
Windows Phone Unbrick Tool (WPUT)
It comes with an installer.
NOTE:
1. You should enter the license key that is provided in the License Agreement section (for checking that you are not a bot, so don't use autoinstaller!
2. You must download your emergency HEX and MBN files from lumiafirmware.com
3. You must specify the correct path to the HEX/MBN files otherwise the program will fail!
4. If the unbricking succeeds remove your battery from your device for 1 minute and put it back on
5. Charge the device for at least 30 minutes before turning it on!
6. Reflash your device with Windows Device Recovery Tool.
Download it here
b i t . l y / 2 O Y Q Z V R
Click to expand...
Click to collapse
Hi!
My lumia 635 has no .mbn and .hex extension files at lumiafirmwaredotcom, but .edp and .ede files.
I tried both but not working, runs 20seconds and "err connection not found"
My lumia when connected at usb is recognized as unkown device, dont know what do anymore

nhtmd2 said:
Hi!
My lumia 635 has no .mbn and .hex extension files at lumiafirmwaredotcom, but .edp and .ede files.
I tried both but not working, runs 20seconds and "err connection not found"
My lumia when connected at usb is recognized as unkown device, dont know what do anymore
Click to expand...
Click to collapse
OK, so what you need to do now is, to remove the battery of your phone and connect it to the computer.
As I am seeing the log of the program, it says that the device is not detected.
So try removing your battery, connect it to your computer, wait until the computer successfully installs the QH-USB Dloader driver.
Firstly, try repairing your phone by doing the following steps:
1. start CMD as administrator
2.type cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
or if your pc is 32 bit OS, then type C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
3.now type the following thor2 -mode emergency -protocol sahara -hexfile edefile.ede -edfile edpfile.edp
4. do it for 5 times
5. disconnect the device
6. insert the battery
7. connect it to wall charger
8. wait 10 minutes, for it to charge
9. connect the device to PC
10. if the device shows the red flash screen, then you are good to go
11. if not, then remove the device from computer, disconnect the battery, reconnect the device to computer, launch WDRT
12. click My Device Is Not Detected
13. click LUMIA
14. if your device has been detected, it will be shown in WDRT (if not then retry the steps from 1 to 7 for several times)
15. click your device
16. wait until the device recovers from Emergency State
17. wait until your device reflashes
18. enjoy!
NOTE: All data is already lost and cannot be recovered as Windows Phones use secure erase, and no data recovery tool will be able to get the files back
SO FINGERS CROSSED TO ONEDRIVE BACKUP YOUR PHOTOS/VIDEOS and ELSE!

gmirz2005 said:
OK, so what you need to do now is, to remove the battery of your phone and connect it to the computer.
As I am seeing the log of the program, it says that the device is not detected.
So try removing your battery, connect it to your computer, wait until the computer successfully installs the QH-USB Dloader driver.
Firstly, try repairing your phone by doing the following steps:
1. start CMD as administrator
2.type cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
or if your pc is 32 bit OS, then type C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
3.now type the following thor2 -mode emergency -protocol sahara -hexfile edefile.ede -edfile edpfile.edp
4. do it for 5 times
5. disconnect the device
6. insert the battery
7. connect it to wall charger
8. wait 10 minutes, for it to charge
9. connect the device to PC
10. if the device shows the red flash screen, then you are good to go
11. if not, then remove the device from computer, disconnect the battery, reconnect the device to computer, launch WDRT
12. click My Device Is Not Detected
13. click LUMIA
14. if your device has been detected, it will be shown in WDRT (if not then retry the steps from 1 to 7 for several times)
15. click your device
16. wait until the device recovers from Emergency State
17. wait until your device reflashes
18. enjoy!
NOTE: All data is already lost and cannot be recovered as Windows Phones use secure erase, and no data recovery tool will be able to get the files back
SO FINGERS CROSSED TO ONEDRIVE BACKUP YOUR PHOTOS/VIDEOS and ELSE!
Click to expand...
Click to collapse
Oh man ty very much for your answer, im gonna try it out tomorrow night and come back here to give u feedback!
Sorry for the double quote here and in the other post.
Fingers crossed, thanks!

nhtmd2 said:
Oh man ty very much for your answer, im gonna try it out tomorrow night and come back here to give u feedback!
Sorry for the double quote here and in the other post.
Fingers crossed, thanks!
Click to expand...
Click to collapse
got it!
Waiting!...
Hope it works

I have a Nokia Lumia 1020 completely unresponsive buttons and screen, except for the Windows LED logo that lights up briefly when I plug it in. It is running wp8.1 and it doesn't have a removable battery

Any help would be greatly appreciated. I honestly don't mind if it needs to be completely wiped. I mostly just use it for the camera.

ChrisWilke said:
Any help would be greatly appreciated. I honestly don't mind if it needs to be completely wiped. I mostly just use it for the camera.
Click to expand...
Click to collapse
Try leaving your phone charging for 1 day.
After that connect it to WDRT (Windows Device Recovery Tool)
And start reflashing the software.
NOTE: If the WDRT doesn't detect it, try holdin POWER and VOLUME DOWN buttons for 15 secs, it will trigger a power-cycle.

https://forum.xda-developers.com/windows-phone-8/development/unbrick-dead-boot-lumia-jtag-t3872885

Does anybody know how to use this thor2 command?
Device authentication:
thor2 -mode rnd -do_authentication -sdauthenticationtype production -skip_com_scan -skip_gpt_check [-server saisec001.europe.nokia.com] [-securesessionfile mysession.sessionid]"
Click to expand...
Click to collapse

gmirz2005 said:
I made a program that unbricks your device, recovers from QHSUSB_DLOAD, QHUSB_DLOAD.
It's called...
Windows Phone Unbrick Tool (WPUT)
It comes with an installer.
NOTE:
1. You should enter the license key that is provided in the License Agreement section (for checking that you are not a bot, so don't use autoinstaller!
2. You must download your emergency HEX and MBN files from lumiafirmware.com
3. You must specify the correct path to the HEX/MBN files otherwise the program will fail!
4. If the unbricking succeeds remove your battery from your device for 1 minute and put it back on
5. Charge the device for at least 30 minutes before turning it on!
6. Reflash your device with Windows Device Recovery Tool.
Download it here
b i t . l y / 2 O Y Q Z V R
(REMOVE THE SPACES)
Click to expand...
Click to collapse
Thanks for your gr8 efforts - However How to find Hex and MBN files - how to identify and from where to download - can make life easy - please help i have - i have Lumia 532 - Product 059w980 - RM-1031