Turbo Unbrick for Android 4.4.4 - 5.1

ilia3367

Senior Member
Oct 29, 2007
255
203
73
53
Emerald City
There are a few types state of brick of the phone. Let's review two of them:
1. “Softbrick” - the state when the system is not booting, but the PC recognizes the phone as “ADB Device” and the phone can boot to bootloader mode. This state is like a baby's runny nose and can be healed by the simple reflash using RSDLite (the tool avaliable for everybody), or by reflashing the parts of firmware via fastboot.
2. 'Hardbrick' - the hard case that needs a lot of work and knowledge. Sometimes hardware intervention needed in order to fix the phone (test-point contacts closure, battery disconnection, etc). Sometimes the phone could not be repaired without motherboard replacement.
We'll review the phone recovery after the second type of bricking.
The phone in “hardbrick” state is recognized by PC as:
- “Unknown device”. In this case you need to install the Qualcomm USB drivers on PC by hands from the attached file "Qualcomm_USB_Drivers.7z" (download it and unpack to any path you want). The phone will be recognized by PC as “Qualcomm HS-USB Diagnostics 9008” device after the driver's installation. Sometimes it is needed to disconnect the phone and to hold the power button during 20-30 seconds to recognize the phone.
- “Qualcomm HS-USB Diagnostics 9008” (nothing happens when you press the buttons on the phone). No needed installation driver's in this case.
The PC will see your phone as shown on picture.

Then the wonderful utility “TURBO-UNBRICK” comes to the rescue. This is a small program but it makes a great job.
Unpack the archive that includes the utility, connect the phone to PC and run “go” file. And you will observe that your brick will become alive! You will see the next picture at your revived phone's screen:

It's almost a win but you need to make some more actions.
Put the files gpt.bin, radio.img, bootloader.img (also attached), to the “C:\adb” folder on your PC and run the next commands in the command line:
Code:
fastboot flash partition gpt.bin
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot reboot
Now you can enjoy! Your friend is alive and greets you by its bootanimation. In that case when you've broken the firmware and the phone is not booting after the bootanimation, you need reboot in bootloader and reflash the firmware by RSDLite.

Android 4.4.4
Link to download the attached files

Android 5.1
Link to download the attached files
 
Last edited:

kinglove1211

Member
Jul 27, 2014
46
15
0
Bloomington
Too bad we can't use this to reprogram the turbos to be the xt1250 so that the bl can be unlocked.I bricked my phone purposely to try and flash the XML of the moto maxx and it will only let me flash the system for the turbo.It does unbrick your phone though,did it 3 times in a row so it definitely works.:)
 
  • Like
Reactions: kitcostantino

chiranjiv97

Member
Apr 8, 2015
6
0
0
failed to flash gpt.bin :(

When i try to flash the given files, flashing of gpt.bin results into "remote failure" and says "preflash validation failed". Rest all the files are flashed perfectly. But cannot flash gpt.bin. Please help :(
 

ilia3367

Senior Member
Oct 29, 2007
255
203
73
53
Emerald City
When i try to flash the given files, flashing of gpt.bin results into "remote failure" and says "preflash validation failed". Rest all the files are flashed perfectly. But cannot flash gpt.bin. Please help :(
This method is intended for Verizone Motorola Droid Turbo. gpt.bin for this phone . What's your phone? Try to flash through motofastboot.
 

chiranjiv97

Member
Apr 8, 2015
6
0
0
This method is intended for Verizone Motorola Droid Turbo. gpt.bin for this phone . What's your phone? Try to flash through motofastboot.
I
Yess I know, I used Motorola droid turbo Verizon xt1254, running on quark 21.44.12. I'm not quite sure about how to use the motofastboot? It'll be great if you can help, thanks a lot :D
 

Zanny1540

New member
Jul 1, 2015
2
1
0
This happened to my phone and I tired using the TURBO-UNBRICK you provided, but it gets to 'flashing singleimage' and I get 'Target ERROR: 7 - Open multi failed, unkown error FAILED (sdl-transfer-image:send-image:sdl-open-multi:target error)

My phone bricked after I started the Lollipop update. No idea what happened. I started the update, went back to work, checked half an hour later and phone was dead. Any help would be great, this is the closest I've gotten to getting it fixed.

~Zanny
 
  • Like
Reactions: fernando9000

DarkLey

Senior Member
Apr 2, 2012
116
38
58
Florianopolis
I did everything descripted in this thread, but my device keeps rebooting (I can hear the USB disconnecting and reconnecting) and still shows up as a QDLoader in device manager. Plus the screen is still black. Any toughts?

Edit: is this singleimage (msimage_901_0228_0000) right? Usually it's a .bin file, but this one is a .mbn
 
Last edited:

chiranjiv97

Member
Apr 8, 2015
6
0
0
Download this archive
Unpack it to C: \ drive
Copy this folder gpt.bin
Flash it command - mfastboot flash partition gpt.bin
Hey, sorry was away! but the link is broken, it says removed due to violation of terms :/ and i cannot post the link in the quote coz xda is preventing me -.-