Turbo Unbrick for Android 4.4.4 - 5.1

[RLShiftyDoggit]

that's insanely awesome if it actually happened, bc motos bootloaders typically, even in a bricked state, will not allow a lower version. that would mean some major awesomeness for those stuck on 5.1.1

Well is there anyway you could make it happen with the unbricking tool?

Sent from my XT1254 using XDA Free mobile app

 

[kitcostantino]

i honestly think that was smoke and mirrors in the first place, at least in terms of the perception someone downgraded bl

 

[RLShiftyDoggit]

Idk man idrc about that anymore bro working on roots been a huge chunk of my time and with that I've also learned that guy was full of it just impossible

Sent from my XT1254 using XDA Free mobile app

 

[kitcostantino]

yup. i was shooting some sarcasm. the best around had already confirmed that was impossible. as much as i wish this was the case, the only two viabilities are if a proper exploit is found/released or if Moto just simply allows bl unlock. neither are likely at this point.

 

[RLShiftyDoggit]

yup. i was shooting some sarcasm. the best around had already confirmed that was impossible. as much as i wish this was the case, the only two viabilities are if a proper exploit is found/released or if Moto just simply allows bl unlock. neither are likely at this point.

Trust me I've tried ****ing around w the BL while my other devs are working on the Root exploit so yeah good luck cracking the BL

Sent from my XT1254 using XDA Free mobile app

 

[mastertr]

Out of curiosity, can you downgrade firmware if it's still the same Android version? For example, going from 44 to 39, would that be possible since they're both Lollipop?

 

[rgerrans]

I need to go back to stock from a Mofo rooted 5.1 It looks like this would allow me to do so since it will install the correct bootloader, radios, img, etc. Amy thoughts on if it might cause issues doing so?

 

[kitcostantino]

kk fxz if youre on mofo 5.1 will take you back to stock.

 

[RLShiftyDoggit]

Out of curiosity, can you downgrade firmware if it's still the same Android version? For example, going from 44 to 39, would that be possible since they're both Lollipop?

no you cant due to the kernel security update due to the kernel it wont let you downgrade same with SU3TL-39 to SU3TL-38 wont allow you to either

 

[rgerrans]

kk fxz if youre on mofo 5.1 will take you back to stock.

Thanks for confirming

 

[caesd]

Help

Hello , I tried unbrik is 4.4.4 , installed the drivers , connected the phone, recognized the device as Qualcomm HS- USB Diagnostics 9008 but when I run the file "go" , there is no picture on the phone, and when I click on Power + volume- the computer to recognize the device and prompt it ..

USB controllers ( Universal Serial Bus )

> USB Unknown Device ( Failure Device Descriptor Request)

How can I solve this?

 

[RLShiftyDoggit]

Hello , I tried unbrik is 4.4.4 , installed the drivers , connected the phone, recognized the device as Qualcomm HS- USB Diagnostics 9008 but when I run the file "go" , there is no picture on the phone, and when I click on Power + volume- the computer to recognize the device and prompt it ..

USB controllers ( Universal Serial Bus )

> USB Unknown Device ( Failure Device Descriptor Request)

How can I solve this?

Op posted this should fix it

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.

Spoiler

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:

Spoiler

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:


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

Spoiler

Android 5.1
Link to download the attached files

Spoiler

Also its post #1 if you need to see the spoilers also id recommend updating your turbo to LP SU4TL-44 you can find the OTA at rootjunkys DL site then side load it to your phone update via stock recovery then go get kingroot root the phone it can take a couple times to get root access then use sunshine it's like 20$ unlock your bootloader then flash TWRP recovery after that's all done I'd recommend wipe data factory reset if you want to stay stock that's fine just go get superSU zip and flash via twrp you'll have stock and root and less likely to end up with this issue again cheers

 

[antoniomalta]

so i have an moto maxx xt1225, i know this was not intended for him, but i'm tried and now i'm able to boot to the fast boot, but i cannot flash the firmware of the moto maxx, if i download the droid turbo firmware i'm gonna be able to flash it? and after that i'm gonna be able to unlock the bootloader and flash the right firmware? thanks for your time 0:fingers-crossed:

 

[caesd]

I resolve one part

The Maxx is in fastboot screen but with (Device is Locked. Status code: 0) , the ROM does not pass through adb , continues in fastboot screen and does not install the rsd , I can not unlock the bootloader because of failure to OEM ! What do I do?

 

[RLShiftyDoggit]

so i have an moto maxx xt1225, i know this was not intended for him, but i'm tried and now i'm able to boot to the boot loader, but i cannot flash the firmware of the moto maxx, if i download the droid turbo firmware i'm gonna be able to flash it? and after that i'm gonna be able to unlock the bootloader and flash the right firmware? thanks for your time 0:fingers-crossed:

Go grab maxx ROM technically turbo and maxx are the same and you might get it to boot but there are some differences in the kernel so all steps apply in post one just use a maxx ROM

---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------

The Maxx is in fastboot screen but with (Device is Locked. Status code: 0) , the ROM does not pass through adb , continues in fastboot screen and does not install the rsd , I can not unlock the bootloader because of failure to OEM ! What do I do?

Can you get into your bootloader?

 

[antoniomalta]

Go grab maxx ROM technically turbo and maxx are the same and you might get it to boot but there are some differences in the kernel so all steps apply in post one just use a maxx ROM

---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------



Can you get into your bootloader?

when i try to flash the bootloader, the gpt.bin and the radio i receive this error:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
and when i try to use rsd lite it also give me a error.
i don't know what to do now :/

 

[RLShiftyDoggit]

Hey @ChazzMatt can you help shine a lil light on this

---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------

when i try to flash the bootloader, the gpt.bin anda the radio i receive this error:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
and when i try to use rsd lite it also give me a error.
i don't know what to do now :/

Preflash validation failure means its not accepting the signature now where you on KitKat or LP when it bricked

 

[caesd]

Go grab maxx ROM technically turbo and maxx are the same and you might get it to boot but there are some differences in the kernel so all steps apply in post one just use a maxx ROM

---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------



Can you get into your bootloader?

I can not take a picture but I have access to the Start however nothing happens, Restart bootloader nothing recovery mode nothing, Power Off it off, Factory nothing happens, Barcodes appear bar codes, BP tools anything QCOM also nothing Bootloader logs nothing . What do I do? I can not unlock the bootloader because of the OEM, and I can not flash stock!

 

[antoniomalta]

Hey @ChazzMatt can you help shine a lil light on this

---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------



Preflash validation failure means its not accepting the signature now where you on KitKat or LP when it bricked

i was in the kit kat but my cousin took my phone and update it by ota Then it bricked : /

 

[RLShiftyDoggit]

I can not take a picture but I have access to the Start however nothing happens, Restart bootloader nothing recovery mode nothing, Power Off it off, Factory nothing happens, Barcodes appear bar codes, BP tools anything QCOM also nothing Bootloader logs nothing . What do I do? I can not unlock the bootloader because of the OEM, and I can not flash stock!

OK can you access the phones memory at all like your internal SD card

---------- Post added at 11:00 PM ---------- Previous post was at 10:57 PM ----------

i was in the kit kat but my cousin took my phone and update it by ota Then it bricked : /

OK go into BL like you are connect it via computer you should be able to load the zip onto the internal memory then go to your recovery enter it then you should see a dead Andy the Android saying no command then hit vol up + pwr then you'll get the option to update via zip should fix it