Turbo Unbrick for Android 4.4.4 - 5.1

[kers wan]

friend and achieve to light !
but no where to put files

 

[guis40]

I have a xt1225 , I could put it in fastboot but when I type the codes in the error cmd he could help me please

 

[Tariq16]

Help bricked droid turbo

Please help me i have bricked my droid turbo xt1254
My scneario
1. I unlocked my bootloader by sunshine on su-44 & took update to su-49
2. I went back to kitkat every thing was fine until i took the update that is around 235mb(Also i was on twrp here)
3. After update everything goes blank & it was showing the qualcomm port i.e "9008"

4. I flash turbo unbrick 5.1 file, now i have a screen of bootloader, but i cannot flash any of the file "gpt.bin, radio.img,bootloader.img "
it says pre flash validation failed

Please help i cant afford another:crying:

 

[kitcostantino]

im not sure that there are unbrick files for that system version yet. what info does the bootloader say? (bootloader version, etc)
also, just as a warning, Motorola typically makes downgrading impossible. bootloader versions lock in and prevent downgrading.

-King of Unsolicited Advice

 

[Tariq16]

im not sure that there are unbrick files for that system version yet. what info does the bootloader say? (bootloader version, etc)
also, just as a warning, Motorola typically makes downgrading impossible. bootloader versions lock in and prevent downgrading.

-King of Unsolicited Advice

I have done unbrick will update the procedure steps later

 

[Adityawa9220]

Help Me

C:\Minimal ADB and Fastboot>.\qboot blank-flash
opening device: \\.\COM42
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.012s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.009s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.012s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.012s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.011s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.006s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)

C:\Minimal ADB and Fastboot>pause
Press any key to continue . . .

 

[fsiddique]

I have the xt1225 that was running the brazil marshmallow soak test. If I downgraded to kit kat and accidentally let the lollipop OTA install, would I need different unbrick files since coming from a marshmallow gpt.bin? Any help would be appreciated since I can't get past greeting device for command mode using the files in the OP.

Edit: nevermind I just needed to use the right qualcomm drivers

 

[bishop0114]

Can this be used to downgrade from su-49 and then root/bootloader unlock?

 

[RLShiftyDoggit]

Can this be used to downgrade from su-49 and then root/bootloader unlock?

No you cannot downgrade the OTA and I believe if you even attempted to try and downgrade the BL you'd end up with a bricked device your SOL unless you sell it and get a DT running SU4TL-44 or SU3TL-39

I'd say if you wanna try running sunshine on SU4TL-49 the worst case it won't work I don't think it would harm the device (but there's always a risk) so try it see what happens if your gutsy enough

 

[ChazzMatt]

I'd say if you wanna try running sunshine on SU4TL-49 the worst case it won't work I don't think it would harm the device (but there's always a risk) so try it see what happens if your gutsy enough

Sunshine team says no, Sunshine will NOT work on SUTL-49. There's a whole thread devoted to it, that Sunshine team member @jcase started to warn people NOT to take SUTL-49 back in May 2016.

Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).

If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.

 

[Duckoy]

C:\Minimal ADB and Fastboot>.\qboot blank-flash
opening device: \\.\COM42
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.012s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.009s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.012s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.012s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.011s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM42
OKAY [ 0.006s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)

C:\Minimal ADB and Fastboot>pause
Press any key to continue . . .

same problem... my xt1254 hardbricked

 

[nimms]

Are these mbn files device specific or chipset specific (805 /8084).
Can i use them to revive note 4 sprint version? (Same chipset.)

 

[RLShiftyDoggit]

Are these mbn files device specific or chipset specific (805 /8084).
Can i use them to revive note 4 sprint version? (Same chipset.)

I believe they are device specific I'm unsure (haven't been able to find much info on the .mbn)

 

[samsfan]

Hi all,

Do you think this turbo unbrick method could work with a N910F (Note 4)?

Thanks

 

[dantexperia]

Please help, "sdl-open-multi:target error"

Hi!, my device is: "Moto Maxx XT1225"; i tried many times this tuto, but not good results for me.
My device just is recognized how "Qualcomm HS-USB QDLoader 9008".
In the end of process for "unbrick" using "qboot" i have "sdl-transfer-image" error; i attached one screenshot.
Please i need help for relive my Moto Maxx, thanks!

 

[aamszia]

phone recovered but unable to flash now .. GPT error

---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------

C:\Program Files\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s

C:\Program Files\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.078s

C:\Program Files\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.081s

C:\Program Files\Minimal ADB and Fastboot>fastboot flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 2.787s]
writing 'radio'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.803s

C:\Program Files\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.
mg
target reported max download size of 536870912 bytes
sending 'bootloader' (2163 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.096s

C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
rebooting...

finished. total time: 0.003s

C:\Program Files\Minimal ADB and Fastboot>

 

[hassan784]

got this error in droid turbo

i got this error on droid turbo
tell me how to fix


greeting device for command mode
opening device: \\.\COM20
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM20
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM20
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM20
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM20
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM20
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM20
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM20
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM20
OKAY [ 0.004s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)

 

[mathk]

Hi!, my device is: "Moto Maxx XT1225"; i tried many times this tuto, but not good results for me.
My device just is recognized how "Qualcomm HS-USB QDLoader 9008".
In the end of process for "unbrick" using "qboot" i have "sdl-transfer-image" error; i attached one screenshot.
Please i need help for relive my Moto Maxx, thanks!

did you install the official motorola usb driver where you can find in some twrp or root threads for droid turbo or maxx xt1225?
I found that my pc can't recognize the phone in bootloader mode when I didn't install it.

---------- Post added at 10:41 PM ---------- Previous post was at 10:34 PM ----------

Hi all,

Do you think this turbo unbrick method could work with a N910F (Note 4)?

Thanks

Doesn't Odin help?

 

[dantexperia]

Hi everyone!, i not find any solution about my error "sdl-transfer-image"; my "XT1225" still continue bricked, only mode "Qualcomm 9008". The "qboot blank-flash" method not working, every time I run I have the same "sdl-transfer-image" error, please i need help, any other method for unbrick?, jtag?, factory cable?, someone help me?; if I can corrupt the "boot", would have some possibility that the method "qboot" works for me ?, because, for many was the only solution this method... Excuse me for my bad english...

 

[Tariq16]

What i did

Please help me i have bricked my droid turbo xt1254
My scneario
1. I unlocked my bootloader by sunshine on su-44 & took update to su-49
2. I went back to kitkat every thing was fine until i took the update that is around 235mb(Also i was on twrp here)
3. After update everything goes blank & it was showing the qualcomm port i.e "9008"

4. I flash turbo unbrick 5.1 file, now i have a screen of bootloader, but i cannot flash any of the file "gpt.bin, radio.img,bootloader.img "
it says pre flash validation failed

Please help i cant afford another:crying:

I unbrick this on windows 7, usb 2.0 port with all specific drivers pre required.

As i was on lollipop so i downloaded files of 5.1 "https://drive.google.com/drive/folders/0B-o0d4PkVUwBfnhobDFpNkZIazl3YThKNE5iWkw3eVgtNzl5aXQwTTdCNElBVTd5VWc5V3c download "Turbo_Unbrick_5.1" folder only. The other files uploaded "bootloader.img,gpt.bin,radio.img" are of build SU-44 i.e why i got pre-flash validation failed error.

1. Important to remember check which build no was your last , As i took update to SU-49, so i was flashing su-44 bootloader files that is why i got pre-flash validation.
2. I was already on SU-49 & have already upgraded my bootloader so i flashed SU-49 bootloader files, here is the full link http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327.
Direct link SU-44 bootloader https://www.androidfilehost.com/?fid=24391638059060254,
Direct link SU-49 bootloader https://www.androidfilehost.com/?fid=24572369360125980
3. Now Download the files according to your previous bootloader build no & extract.
4. Put the files gpt.bin, radio.img, bootloader.img, to the “C:\adb” folder on your PC and run the next commands in the command line:

fastboot flash partition gpt.bin
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot reboot

Hope this help