yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo General] 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
[Verizon Motorola Droid Turbo General] 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.
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
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
[Verizon Motorola Droid Turbo General] 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?
[Verizon Motorola Droid Turbo General] 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?
[Verizon Motorola Droid Turbo General] kitcostantino:
kk fxz if youre on mofo 5.1 will take you back to stock.
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
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
[Verizon Motorola Droid Turbo General] rgerrans:
Thanks for confirming
[Verizon Motorola Droid Turbo General] 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?
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
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
[Verizon Motorola Droid Turbo General] 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:
[Verizon Motorola Droid Turbo General] 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?
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
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?
[Verizon Motorola Droid Turbo General] antoniomalta:
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 :/
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
Hey [MENTION=3250376]ChazzMatt[/MENTION] 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
[Verizon Motorola Droid Turbo General] caesd:
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!
[Verizon Motorola Droid Turbo General] antoniomalta:
i was in the kit kat but my cousin took my phone and update it by ota Then it bricked : /
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
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 ----------

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
[Verizon Motorola Droid Turbo General] caesd:
I can not access the SD card, appears on the computer as

Not specified

> Fastboot quark S
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
Alright then you need the adb drivers and fastboot drivers installed watch rootjunkys video on YouTube on how to unbrick the droid turbo it will be the same processes to unbrick your maxx just use the maxx ota zip should be able to find that on the motofirmware site
[Verizon Motorola Droid Turbo General] antoniomalta:
when i try to go to recovery, it come back to the screen that i attached in the other reply. and i dont know what zip are you talking about sorry :/ also i don't know how to push him because my phone just recognise fastboot comands, when i try adb it says waiting for device :/ thanks for the help until now, i really appreciate.
[Verizon Motorola Droid Turbo General] caesd:
I can use the firmware XT1254, XT1225 in ??

if not, where I think this firmware with bat file.?
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
Straight up you can try it I have no clue if it'll work man

---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------

You have fastboot commands great your device can be saved just go to YouTube watch rootjunkys video on to unbrick the droid turbo fallow the steps but using maxx firmware and you are set my friend
[Verizon Motorola Droid Turbo General] antoniomalta:
it fail to flash everything i try :/ , i'm think thasts because i instaled the 6.0.1 last week before the downgrade, i lost my hope now. probably i'm gonna have to change the motherboard , well i'm gonna start saving money for it. Thanks for the help bro.
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
YOU CANNOT DOWNGRADE android LP or M without unlocked bootloader try flashing the 6.0.1 update via fastboot

PS shoulda told me that from the beginning would have saved you so much time and effort
[Verizon Motorola Droid Turbo General] caesd:
I tried to use the files, STOCK 5.0.2 for the XT1225 with the files of the XT1224, but gives the same error.

> FAILED (remote failure)

> (Bootloader) Preflash validation failed

> (Bootloader) invalid partition name dow

> (Bootloader) invalid partition name cache

> (Bootloader) invalid user data partition name

What should I do?
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
If you have the XT1225 you have to use a XT1225 ROM as the bootloader has a device check to make sure the ROM is for that specific device that's why I said a turbo one wouldn't work most likely as it would show up as XT1254 droid turbo I have no clue if there's a difference between the XT1224 and XT1225 so whatever specific model you have go get that one and flash it via fastboot again and should boot right up bro
[Verizon Motorola Droid Turbo General] caesd:
Unfortunately, the same as in xt1224 firmware, same mistakes!
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
Honestly man I'd talk to [MENTION=3250376]ChazzMatt[/MENTION] I think he has a XT1225 he might be your guy I'm literally running out of ideas lol probably doesn't help I've been up for 24hrs straight
[Verizon Motorola Droid Turbo General] caesd:
I also have no idea what to do , the probema is the OEM , to the RSD Lite , when it arrives in the process 2 oem appears filed and stop.

does he know ?
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
Idk you'd have to ask him
[Verizon Motorola Droid Turbo General] ChazzMatt:
Your cousin owes you a new phone. ;)

---------- Post added at 05:43 AM ---------- Previous post was at 05:36 AM ----------

The scenario presented to me in PM was the phone was bricked but then somehow in fastboot the bootloader was re-locked. Now they can't flash any images due to error messages. And they can't unlock the bootloader, which they re-locked, using the OEM unlock method.

I've only unlocked bootloader on my XT1225 phones using Motorola website code. I would suggest trying that to unlock the bootloader again?

You can flash a factory stock image with a locked bootloader but you have to do every step correctly or risk bricking. Whereas with UNlocked bootloader if you make a mistake (I did before), you can try again. UNlocked bootloader is very forgiving. NEVER, never re-lock your bootloaders! Unlocked bootloader is freedom, locked bootloader is slavery.

______

OK, try this:

[Tutorial] How to Flash Different Official Firmware

http://xdaforums.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724

You want 5.0.2. For the guy at the top, since your cousin tried to install the 5.02. OTA your bootloader is either upgraded to Lollipop and you can't downgrade or your bootloader is corrupted. Either way, you want to flash stock 5.0.2 for your phone, using that guide. Once you have 5.02. bootloader, even when you downgrade to 4.4.4, you have to skip flashing the 4.4.4 bootloader. You can NOT downgrade bootloaders.

You want to flash ALL the sparse chunks, however many there are. Each image has a different amount. The example shows 8 -- but that's just an example. That was the mistake I made. :( But I had an unlocked bootloader, so no harm was done, except my phone wouldn't boot. I then went back and flashed ALL the sparse chunks.

Find and download stock 5.0.2 for your phone from here:

http://xdaforums.com/showpost.php?p=63217981&postcount=31
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
Yeah no shiet I tried everything I could think of
[Verizon Motorola Droid Turbo General] ChazzMatt:
I just edited my post to show a better guide than that one.
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
Yeah I only know the XT1254 funny part is its my first Motorola phone
[Verizon Motorola Droid Turbo General] ChazzMatt:
True, but both the people I was helping in that post have XT1225. I'm more familiar with that, as I own three of those. And the XT1225 (and XT1250) bootloader can be unlocked via Motorola website code.

The Moto XT1225 was also my first Motorola phone. Before that I owned Nexus (Samsung, LG) phones or LG non-Nexus phones. I really like LG a lot. Only with the XT1225 did Motorola finally make an Android top tier phone that could compete with LG.

2013 5.2" 1080p LG G2 smacked the 2013 4.7" 720p Moto X (which was basically a copy of 2012 4.7" 720p LG G1, "Optimus G"). (And Google agreed. They based the Nexus 5 on the exemplary LG G2.)

2014 5.5" 1440p LG G3 smacked the 2014 5.2" 1080p Moto X (which was basically a copy of the 5.2" 1080p LG G2).

Finally with the specs of the 5.2", 1440p Quark and the Moto Nexus 6 (which was too big to use) did Motorola finally make top tier phones that could compete with LG's phones. The Quark is the size the gen6 Nexus should have been, but that's another topic. ;)

I own three of these, so I really like this phone!
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
That's why I recommended you lol yeah I had the Samsung Galaxy S1 T-Mobile exhibit then a crappy prepaid net 10 phone then a nexus Samsung it was the crespo 4g had that running CM9 then the lg optimus net or something like that I was gonna go nexus again but I didn't see it in the Verizon store and the s6 I knew didn't have a unlocked bootloader so turbo it was now side note anyway to unscrew these two or are they SOL?
[Verizon Motorola Droid Turbo General] jcp15963:
Holy Crap Thanks

Hours and hours of searching. Tid Bits here and there, but noting useful. My cautionary story: I bought an XT1250 Moto Maxx (American Version) of the Turbo with out the name or bloat. Never thought they would update it...... so I converted to an XT1254 Turbo. Low and behold they actually upgraded the xt 1250 so I tried to go back to KitKat and upgrade to Lollipop. HUGE MISTAKE. F#@$#% everything up. Spent hours on the internet trying to sort it out and THIS was the site that actually helped. Thank You....So much

To add to this forum: Now that i have my XT1250 back working - as a - Droid Turbo, is there ANYWAY to bring it back from Turbo to stock XT1250 Moto Maxx. When the above fix worked, only parts of the phone worked . It would constattly reboot., WIFI would not work. I had to completely reflash Droid Turbo to get it to work perfectly. I am leaving Verizon after much customer service hate and lies and going back to AT&T, i know the Turbo will work on AT&T, but i would rather have my phone flashed as the stock XT1250 Moto Maxx. I it even possible? to flash back to stock xt1250? My bootloader is still unlocked, but there doesnt seem to be a full XT1250 zip file out there to try and flash, just the OTA. Tried sideloading that with adb and from sd card, neither worked. Any suggestions? any help? Any links to XT1250 full Lollipop .zip files? Thanks.
[Verizon Motorola Droid Turbo General] kers wan:
friend and achieve to light !

but no where to put files
[Verizon Motorola Droid Turbo General] 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
[Verizon Motorola Droid Turbo General] 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:
[Verizon Motorola Droid Turbo General] 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
[Verizon Motorola Droid Turbo General] Tariq16:
I have done unbrick will update the procedure steps later:)
[Verizon Motorola Droid Turbo General] 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 . . .
[Verizon Motorola Droid Turbo General] 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
[Verizon Motorola Droid Turbo General] bishop0114:
Can this be used to downgrade from su-49 and then root/bootloader unlock?
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
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
[Verizon Motorola Droid Turbo General] ChazzMatt:
Sunshine team says no, Sunshine will NOT work on SUTL-49. There's a whole thread devoted to it, that Sunshine team member [MENTION=2376614]jcase[/MENTION] started to warn people NOT to take SUTL-49 back in May 2016.
[Verizon Motorola Droid Turbo General] Duckoy:
:rolleyes: same problem... my xt1254 hardbricked
[Verizon Motorola Droid Turbo General] nimms:
Are these mbn files device specific or chipset specific (805 /8084).

Can i use them to revive note 4 sprint version? (Same chipset.)
[Verizon Motorola Droid Turbo General] RLShiftyDoggit:
I believe they are device specific I'm unsure (haven't been able to find much info on the .mbn)
[Verizon Motorola Droid Turbo General] samsfan:
Hi all,

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

Thanks
[Verizon Motorola Droid Turbo General] 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!
[Verizon Motorola Droid Turbo General] 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>
[Verizon Motorola Droid Turbo General] 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)