How To UnBrick A Hard Bricked Moto X
Hii , First of all I wanna thanks to this awesome scrpit by @s5610 who brought my phone from dead to alive , I think i am the first guy to unbricked the hardbricked phone using this script lol , My phone was hardbricked because i was testing my kernel and entered wrong path in partition due to which i got hard bricked i was worried for my phone , Service Center was asking for 7k in Indian Rupees , i was hopeless then i gave a try to this method , followed all steps written here and then finally i entered to fastboot menu of 30.B7 Kitkat As i was using 30.B7 Bootloader earlier and then i flashed My gpt.bin and S-partition and flashed my stock rom voilla !! and my phone booted the aim was to share this post was this method was on page 42 and only less guys have seen this post , so i created a new thread regarding this
All Credits Goes to - @s5610
s5610 said:
Unbricking Guide for any Moto X Gen 1 (wire trick)
Download, and unpack supplied zip to any disk, C: or D:, in root folder. Install driver by launching Qusb.drv.inst.msi, then open Windows' Device Manager, and see if you got "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
If yes, you see it, go to software part below. If it's not there, a full disassemble of the phone is needed to get close to back side of motherboard (google for "iFixit Teardown Moto X Guide" for step-by-step instruction).
So, when you are inside, disconnect the battery first. No need to pull it out, it's glued. Now get to back side of motherboard, and very very gently gain access to the lower left corner of ARM+DRAM shield (see picture). I've done it with Stanley knife. Also you can use miniature nippers - but very carefuly! Once you get access to inner space of shield, use tiny wire to short special pin to the ground (see picture), then connect USB cable, and in the moment when you see "QHSUSB_DLOAD" device (or "Qualcomm HS-USB QDLoader 9008" if driver is installed) pop out in Windows' Device Manager, quickly remove the wire. The goal is to have "Qualcomm HS-USB QDLoader 9008" in "COM & LPT ports" section of Device Manager. If it is achieved, we are done with hardware, and move on to soft part.
Now software part. Go to unzipped C:\Python27 folder, launch bat-file, and wait until finish:
RUN_blank_bootloader_flash.bat
(if you got error like "No data read from USB..." etc, just skip to next step)
Next launch either
- .Boot_KK_4.4.2_B4.exe,
or .Boot_KK_4.4.4_B7.exe,
or .Boot_LP_5.0.2_BC.exe,
or .Boot_LP_5.1.0_BD.exe,
or .Boot_LP_5.1.0_BE.exe
- depends on Android version your phone has last time. If you don't know what you need, begin with first one.
Wait 10 seconds, then launch next bat-file, and wait until finish:
RUN_moto_x_bootloader_flash.bat
Phone should go into fastboot mode! If it doesn't, repeat previous step trying higher version. But don't try to flash BC, BD, and BE, if you didn't install Lollipop on this phone!
OK. Disconnect the USB cable, connect the battery, connect again USB cable (fastboot don't work, if don't see battery). Launch next bat-file:
RUN_gpt.bin_flash.bat
The phone will get in fastboot, ready to be flashed by appropriate firmware. If it is official RSD (SBF), delete from xml strings consisting gpt.bin and motoboot.img for safe flashing.
...
Download link: http://www.mediafire.com/download/3e38rr3wy28s071/Moto.X.Unbrick.zip
This guide was brought to you by s5610
Links that this guide is based on (where I took files and general idea):
http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
http://forum.xda-developers.com/mot...-moto-x-t2629057[/url[/QUOTE][/QUOTE][/QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Not sure if additional thread is necessary )
UPDATED
The best resurrection method for Moto X is here.
Can Someone re-upload that file? Thanx!
Please upload the mediafire link...
Plz plz.. I have bricked my phone. It seems that this procedure will work for me. Please upload and save my life.
even i have bricked my moto x...need a working download link..please.
https://drive.google.com/file/d/0B3EDzuzDCakzdWxHa2RWVDJhRXc/view?usp=sharing
Cannot install qsub.drv.inst.msi on my windows 10...says failed to attribute and failed to delete qcusbser.sys.
Thanks
Can we write the full firmware through Qload 9008 mode ???
HI I have a question. I bricked my gf's phone while trying to unlock the bootloader and I am not able to turn the phone on. Only positive feedback is that when I plug it in to the computer, I can hear a notification on my computer. I followed your guide. I can see the "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
Then I followed your software instructions. When I run the RUN_blank_bootloader_flash.bat, I get the following
Code:
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
qflash - com3 is an invalid port
Invalid COM port enteredBlank flashing successful
Device will now enumerate in fastboot mode
Then, I followed the rest of the instructions by trying each .Boot .exe and waitng 10 seconds and finally with RUN_moto_x_bootloader_flash
but I am getting the following error.
Code:
C:\Users\cxx\Desktop\Python27>python qdload.py MPRG8960.bin -ptf _boot\partiti
ons.txt -pt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com3
Traceback (most recent call last):
File "qdload.py", line 815, in <module>
main()
File "qdload.py", line 762, in main
tty = openTTY(args.ttyPort)
File "qdload.py", line 174, in openTTY
tty = serial.Serial(port=tty_path, baudrate=115200)
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 38, in __init
__
SerialBase.__init__(self, *args, **kwargs)
File "C:\Python27\lib\site-packages\serial\serialutil.py", line 282, in __init
__
self.open()
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 66, in open
raise SerialException("could not open port %r: %r" % (self.portstr, ctypes.W
inError()))
serial.serialutil.SerialException: could not open port 'com3': WindowsError(2, '
The system cannot find the file specified.')
C:\Users\cxx\Desktop\Python27>pause
Press any key to continue . . .
please help.
Thanks.
Device Shows As USB Input
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks
shengslogar said:
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks
Click to expand...
Click to collapse
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.
liveroy said:
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.
Click to expand...
Click to collapse
Will do! I think I did try charging it awhile ago, but I'll give it another shot.
can my phone be unbricked?? here is the error log:
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has
een reset back to blank flash mode. Usually this is caused by power supply issu
s. Please try again with battery eliminator if it persists
Unexpected target reset, bailing out after 2 retries
I am trying to install the drivers and it will show up as qhsusb_dload for about 5 seconds then reverts back to Relink HS USB QDloader 9008. Should i try the wire trick? It will say that the Qhsusb drivers are installed but always changes.
At start sorry for my English.
My phone is totally bricked after my tries to unbrick my phone (Windows Device Recovery)
Phone isn't reacting. No charge vibration, don't turning on, just NOTHING. Lumia is only reacting when i connect it by cable to my laptop. How i can unbrick that phone :x Please help me ;c
feherneoh said:
Could you please give some additional info? What happens when you connect it to PC?
Click to expand...
Click to collapse
PC detect QHSUSB_Bulk and pc makes a "connection info" voice
Download and install Windows device Recovery Tool
Download from Lumiafirmware.com your model's Emergency files and ffu file
Locate thor2.exe and open a command line in that directory
Emergency and SFFU programming for Collins and Alpha:
thor2 -mode emergency -hexfile "{downloaded hexfile, full path!}" -mbnfile "{downloaded mbnfile, full path!}" -ffufile "{downloaded ffufile, full path!}.ffu"
If you copy the files in your thor2.exe subdirectory, you may drop the double quotes.
Look at this Thread:
https://forum.xda-developers.com/wi...nt/fix-dead-phone-bricked-bootloader-t3496232
Hi, so I'm one of those idiots that bricked their phone. The good news (for me at least) is I bought it for $24 to play around with and learn WP. Well I'm learning! What not to do that is. So I wanted to try WP10 and ended up bricking it. After flashing some sketchy ported win 10 rom (the three bin files as opposed to an FFU) it was in an endless reboot loop where it would just show NOKIA and then reboot. I tried to restore it but the sketchy rom had changed the product ID. So I futzed with the boot loader (this is all in WPInternals by the way) and locked it. I can't unlock it because my FFU file doesn't match the product id and I can't re-flash the sketchy rom because WPInternals crashes every time I try. Now the phone just boots to ERROR: Unable to find a bootable option...
So...after a couple of days of reading and trying different things (long story short, the phone has some unknown product id that doesn't match my backup product id (or the ATT 920 FFU).
So I've been trying to start with restoring the boot loader like so:
Code:
thor2 -mode emergency -hexfile FAST8960_PHI_ATT.hex -mbnfile RM820_msimage_v1.0.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 FAST8960_PHI_ATT.hex -mbnfile RM820_msimage_v1.0.mbn -orig_gpt
Process started Wed May 31 19:53:04 2017
Logging to file thor2_win_20170531195304_ThreadId-3536.log
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)
So as you can see I can't get thor to communicate in emergency mode with the phone (I can in uefiflash mode). In device manager the phone shows up as "Care Suite USB Connectivity" under USB devices.
This is where I am stuck and very much need your help!
Doug_M said:
Hi, so I'm one of those idiots that bricked their phone. The good news (for me at least) is I bought it for $24 to play around with and learn WP. Well I'm learning! What not to do that is. So I wanted to try WP10 and ended up bricking it. After flashing some sketchy ported win 10 rom (the three bin files as opposed to an FFU) it was in an endless reboot loop where it would just show NOKIA and then reboot. I tried to restore it but the sketchy rom had changed the product ID. So I futzed with the boot loader (this is all in WPInternals by the way) and locked it. I can't unlock it because my FFU file doesn't match the product id and I can't re-flash the sketchy rom because WPInternals crashes every time I try. Now the phone just boots to ERROR: Unable to find a bootable option...
So...after a couple of days of reading and trying different things (long story short, the phone has some unknown product id that doesn't match my backup product id (or the ATT 920 FFU).
So I've been trying to start with restoring the boot loader like so:
Code:
thor2 -mode emergency -hexfile FAST8960_PHI_ATT.hex -mbnfile RM820_msimage_v1.0.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 FAST8960_PHI_ATT.hex -mbnfile RM820_msimage_v1.0.mbn -orig_gpt
Process started Wed May 31 19:53:04 2017
Logging to file thor2_win_20170531195304_ThreadId-3536.log
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)
So as you can see I can't get thor to communicate in emergency mode with the phone (I can in uefiflash mode). In device manager the phone shows up as "Care Suite USB Connectivity" under USB devices.
This is where I am stuck and very much need your help!
Click to expand...
Click to collapse
if you have full backup image of your phone(win32Disk image tool). then you put your phone in mass storage mode(keep press and hold camera button on reboot) and write image file.
A AJAY said:
if you have full backup image of your phone(win32Disk image tool). then you put your phone in mass storage mode(keep press and hold camera button on reboot) and write image file.
Click to expand...
Click to collapse
I can't seem to put it in mass storage mode. The phone will turn on if off (not getting past the error mentioned previously of course). And I can force it to reboot by holding vol down and power. But holding vol down, vol up or camera key after the vibration doesn't work as it should. In each case all that happens is the phone vibrates as it should, then the nokia logo is displayed, then the error message (unable to find boot option) displays for less than a second and finally the phone reboots.
Solved! Googling led me to useing vpl mode. That gave me an error which further googling I saw another person who also couldn't flash 059L848 but the developer version of the rom 059R2L5 worked. I tried that and now as I type this my phone is at the Welcome screen! Sweet!
Wow! Congratulations, I sold mine, but if I had not, I would have given it a try.
Best regards,
Joachim
Have a similar problem but I keep getting an error message of "The FFU file is not correctly signed or not signed for this device." I also put W10M on a Lumia 1020 and now have a constant error message of "Unable to find bootable option".
I'm so frustrated over this. Hoping to get it fixed and back to original WP8.1.
Seeking help!
---------- Post added at 06:55 PM ---------- Previous post was at 06:51 PM ----------
Doug_M said:
Solved! Googling led me to useing vpl mode. That gave me an error which further googling I saw another person who also couldn't flash 059L848 but the developer version of the rom 059R2L5 worked. I tried that and now as I type this my phone is at the Welcome screen! Sweet!
Click to expand...
Click to collapse
Can you give me more details on how you solved this? Thanks.
I just thought of something else: when I installed W10M on my Lumia, I changed it to make it appear as a Lumia 950XL. I used InterOP tools and RegEdit. Could this be related to the FFu signature problemas I'm getting today? How would I change these values?
WPInternals info: https://1drv.ms/u/s!Ag-KZVVb9pL6q5pd7wcC32KiUZzfjQ
Hi, I had a Lumia 925 and wanted to jailbreak it since I found a few people who did this and I wanted it for my own reasons. Anyway, as with all the guides, I used the Windows Phone Internals tool. I downloaded all of the files from LumiaFirmware.com and I opened Windows Phone internals, selected Unlock bootloader and added all of the files (rebooting to Flash mode, of course) and it wouldnt let me start. It would always say: The OS version is not supported. Use a donor-FFU. I tried with another FFu, but it still did not work (I tried flashing the downloaded rom and trying again, but same thing). Anyway, now I did something and now the device is recognised in Windows as "Qualcomm QHSUSB-DLOAD". How can I restart the phone? Windows Phone Internals does not recognize it.
By the way, this is my first time doing things, I may have done something wrong. I did download all drivers, in case you are wondering
Hi,
open windows device manager and use the windows/nokia emergency driver for your device. Then look for thor2.exe, it is a part of WindowsDeviceRecoveryTool.
Open a command prompt window.
Type/paste thor2 -mode emergency -hexfile D:\Packages\Products\RM-994\FAST8930_BATMANROW.hex -mbnfile D:\Packages\Products\RM-994\RM994_msimage_v1.0.mbn -ffufile D:\Packages\Products\RM-994\RM994_3056.40200.1407.0002_RETAIL_eu_euro2_1168_02_405247_prd_signed.ffu
REPLACE my product RM994 with your product and the file names too. Replace D:\Packages\Products with the directory on your PC. You get the emergency files from lumiafirmware.com.
Contact me if there are problems, we will sort that out.
Regards,
Joachim
Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast
Audoghast said:
Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast
Click to expand...
Click to collapse
While your phone is in fastboot and connected to your laptop; How is it shown in device manager?
Good evening.
I found the solution to unbrick my Oneplus Nord CE 5G and here it is.
Status: - normal start leading to Qualcomm Crash Dump screen
- Recovery mode into TWRP possible but no transfer of files to/from phone
- No Fastboot possible
Procedure:
Install Qualcomm USB Drivers from
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
You may have to launch the command prompt as admin and type:
bcdedit /set testsigning on
I did not have to do it because the Qualcomm Driver installation did it for me.
After restart you will see the following message in the lower right side of your PC:
Testmode Windows 10 Pro + build number
To get rid of end at the very end type:
bcdedit -set testsigning off
Download the following package:
Europe: https://onepluscommunityserver.com/...BA/R/OnePlus_Nord_CE_EU_OxygenOS_11.0.9.9.zip
India:
https://onepluscommunityserver.com/...R/OnePlus_Nord_CE_India_OxygenOS_11.0.4.4.zip
These packages contain the MSM Download Tool and the respective files. Beware that you have to get the correct bundle for your phone. Other bundles contain MSM Download Tool too but will not be compatible and the tool generates a failure message.
Launch MSM and type OTHER at login.
Target was EU in my case.
Then click on start.
Now your phone needs to boot into EDL mode. It worked for me from the TWRP Reboot screen but supposedly starting the phone by holding the volume up and down buttons for 45 seconds does the same.
The screen will be totally black, no beep, no vibration, no feedback.
Then connect the USB cable and MSM will start working. After about 5 minutes the phone should be back to normal.
ADB commands worked again too (phone was being recognized as USB device under device manager). However, fastboot did not work. The device was listed as other device in the manager.
After updating the driver using the following files everything worked:
https://drive.google.com/drive/folders/1D96njoYn-n3alu3ggaK3Kw8hMGLKhJVg
Now I am back to rooting and will report about that too.
Good luck