Turbo Unbrick for Android 4.4.4 - 5.1 - Verizon Motorola Droid Turbo General

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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
https://drive.google.com/open?id=0B-o0d4PkVUwBflNNbF96UWx1N1JtVkY5S1JrM25lemIxVFgtTEdwb0lEUmxqYzlqc2VfZzg&authuser=0
Android 5.1
Link to download the attached files
https://drive.google.com/open?id=0B...l3YThKNE5iWkw3eVgtNzl5aXQwTTdCNElBVTd5VWc5V3c

Thanks bud, I wasn't able to register with my gmail account.

Turbo unbrick
Wish I had this a month ago,had to send my phone off to be jtagged.I'm sure I'll need it again.Thank you for your work.

kinglove1211 said:
Wish I had this a month ago, had to send my phone off to be jtagged. I'm sure I'll need it again. Thank you for your work.
Click to expand...
Click to collapse
I also went through it . Therefore, I decided to share this experience. :highfive:

ilia3367 said:
Link to download the attached files
https://drive.google.com/open?id=0B-o0d4PkVUwBflNNbF96UWx1N1JtVkY5S1JrM25lemIxVFgtTEdwb0lEUmxqYzlqc2VfZzg&authuser=0
Click to expand...
Click to collapse
Latest Radio / Firmware ?
Where's the img of recovery, I need?

@ilia3367,
Thank you for the great contribution, it is good to know you are unbrickable with these tools.

Great info should be in android development

arohrmann said:
Latest Radio / Firmware ? Where's the img of recovery, I need?
Click to expand...
Click to collapse
Firmware - 21.44.12
Radio - MDM9625_104351.17.02.71.13R
IMG recovery need not.

Will this technique work on a Droid Maxx?
Sent from my XT1254 using XDA Free mobile app

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.

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

chiranjiv97 said:
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
Click to expand...
Click to collapse
This method is intended for Verizone Motorola Droid Turbo. gpt.bin for this phone . What's your phone? Try to flash through motofastboot.

ilia3367 said:
This method is intended for Verizone Motorola Droid Turbo. gpt.bin for this phone . What's your phone? Try to flash through motofastboot.
Click to expand...
Click to collapse
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

chiranjiv97 said:
I'm not quite sure about how to use the motofastboot? It'll be great if you can help, thanks a lot
Click to expand...
Click to collapse
Download this archive https://drive.google.com/open?id=0B-o0d4PkVUwBR0FiUHNKRUxIXzQ&authuser=0
Unpack it to C: \ drive
Copy this folder gpt.bin
Flash it command - mfastboot flash partition gpt.bin

have you tried the mot dev manager? that should detect a brick and set back to factory. rsdlite could also be used

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

Anybody tried this tools for xt1254 ?

will this work if i bricked it after installing 5.1?

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

ilia3367 said:
Download this archive
Unpack it to C: \ drive
Copy this folder gpt.bin
Flash it command - mfastboot flash partition gpt.bin
Click to expand...
Click to collapse
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 -.-

Related

[Q] Google nexus 7 (2012) - Unrooting leads to total failure(no recovery, no boot up)

Dear developers and other users!
I have been looking for same issues but I was unable to find answer for my problem.
About a year ago I unlocked and rooted my nexus 7 tablet to use special apps on it.
Today I tried to unroot and lock my device. On my laptop the program(Nexus Root Toolkit) said it was successful so I just needed to reboot the tablet.
After rebooting it stopped on the Google screen with a "Booting failed" text on the top left corner like that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think I have uninstalled android from the device but I can't Intsall a new one because recovery mode doesn't work and Android is not going to boot.
I can only use Bootloader. Bootloader looks like that:
Once I started my tablet it started in bootloader mode but every other startup fails on Google screen.
Please help me to use my tablet as before without root.
What should I do and how should I do that to get it work again?
Any help would be highly appreciated ​
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Carlyle_f said:
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Eurioin said:
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Click to expand...
Click to collapse
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Pirateghost said:
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Click to expand...
Click to collapse
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Fix your drivers then. Fastboot is the surefire way to fix your issue.
#stayparanoid
Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Its much easier on a Linux machine. All you need to do is open terminal and type "sudo apt-get install android-tools-adb android-tools-fastboot" and hit enter. Then extract the .tar file and double click "flash-all.sh" and choose run in terminal. Absolutely no driver headaches.
If you have access to a Linux machine (mint/ubuntu) or if you can dualboot Linux, this will really help
Sent from my GT-I8190 using Tapatalk
I too have this same issue...
Exception is my Nexus is locked... everytime I try to unlock it, it tries to reboot and never comes back on...
What am I doing wrong?
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type
fastboot oem unlock
Click to expand...
Click to collapse
(this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
fastboot update image-nakasi-kot49h (this was the firmware that I needed to "update")
Click to expand...
Click to collapse
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
fastboot oem lock
Click to expand...
Click to collapse
And now I am using Android 4.4.4 on my nexus 7 tablet
Eurioin said:
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type (this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
And now I am using Android 4.4.4 on my nexus 7 tablet
Click to expand...
Click to collapse
I was hopeful that this would work for me.... I am using a win 8.1 machine and the downloaded fastboot and adb seemed to work fine.
I go to do a fastboot unlock and I get the following:
(bootloader) erasing userdata...
(bootloader) erasing userdata done...
(bootloader) erasing cache...
(bootloader) erasing cache done...
(bootloader) unlocking....
FAILED (remote: (Unknown error code))
finshed. total time: 7.902s
So..... Anyone ? The tablet does ask if I want to Unlock the Bootloader... I select yes and hit the power button to select... yet the tablet goes back to the android screen... The top of the screen says Unlocking now...... yet it doesn't...
Please help...

My OPT Stuck in 1+ logo and not enter to TWRP and cannot get inside bootloader

Please help I can Open my OPT
Ahmed Shawky said:
Please help I can Open my OPT
Click to expand...
Click to collapse
Please I ned any help
My mobile not open
I can not Unlock the boatloader
Huh. There is no information on your post. What do you think XDA is? Can't help until you tell your situation.
Nobody can solve your problem until you explain what happened.
Sent from my ONE A2003 using Tapatalk
Please elaborate on what happened to your phone. Till then check these links out for a possible fix:
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
http://forum.xda-developers.com/oneplus-2/general/guide-to-stock-t3341130
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
I have similar problem, so maybe not generating new threat...
I got OP2 from friend. He used Oxygen 2.x (don't know exactly) and decided to flash some custom ROM. And something went wrong
He brought me today his phone and:
- fastboot works,
- device is locked and impossible tu unlock (FAILED (remote: oem unlock is disabled))
- after 2 hours of work I got stock recovery working (using some Chinese Qualcomm recovery tool).
But: I can't unlock BL, I can't flash anything via fastboot (because ->locked), ADB doesn't work too (cant push any file to devices).
When turning on phone it's in bootloop, but I can enter fastboot or stock recovery.
I tried almost all solutions from her and OP forums, but everything false because of locked BL.
ANY ideas? My short knowledge ends here There is probably no any data in device (no system, userdata etc.).
I don't have USB-C pendrive / cable so I cant flash anything from stock recovery. If I'll get USB-C pendrive will it be possible to flash stock ROM with stock recovery?
Does it show up in fastboot devices?
Sent from my Nexus 7 using Tapatalk
Try first-aid for oneplus 2. It's worked for me twice before. It's on XDA but I don't have a link. Search for it. I'm pretty sure it'll work.
EggZenBeanz said:
Does it show up in fastboot devices?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, It shows. But not much possible to do because of locked BL.
McCullyCullen said:
Try first-aid for oneplus 2. It's worked for me twice before. It's on XDA but I don't have a link. Search for it. I'm pretty sure it'll work.
Click to expand...
Click to collapse
I tried but with no success. All this tools works flashing .img's from fastboot. It's useless for me...
Have you tried the fastboot oem unlock using the device id as part of the command string?
Sent from my ONE A2003 using Tapatalk
No. How to do this?
vonski said:
Yes, It shows. But not much possible to do because of locked BL.
I tried but with no success. All this tools works flashing .img's from fastboot. It's useless for me...
Click to expand...
Click to collapse
try this...... "fastboot -i 0x2a70 oem unlock-go"
worked for me
Thank, but :
C:\Android_sdk\sdk\platform-tools>fastboot -i 0x2a70 oem unlock-go
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.007s
Same...
It sounds like the ability to unlock the bootloader is disabled in developer options. I think, but I'm only guessing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONE A2003 using Tapatalk
Yes, but I can't boot to system (probably memory is empty- no data) and switch OEM Unlock.
I've got only fastboot and stock recovery.
do any of these help you? I guess you could say your phone is hard bricked due to not booting to OS and not having TWRP recovery?
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
I used this tutorial but I can't get device correctly installed as Qualcomm. I'll try on other pc.
Tapatalk @ OnePlus X
vonski said:
I have similar problem, so maybe not generating new threat...
I got OP2 from friend. He used Oxygen 2.x (don't know exactly) and decided to flash some custom ROM. And something went wrong
He brought me today his phone and:
- fastboot works,
- device is locked and impossible tu unlock (FAILED (remote: oem unlock is disabled))
- after 2 hours of work I got stock recovery working (using some Chinese Qualcomm recovery tool).
But: I can't unlock BL, I can't flash anything via fastboot (because ->locked), ADB doesn't work too (cant push any file to devices).
When turning on phone it's in bootloop, but I can enter fastboot or stock recovery.
I tried almost all solutions from her and OP forums, but everything false because of locked BL.
ANY ideas? My short knowledge ends here There is probably no any data in device (no system, userdata etc.).
I don't have USB-C pendrive / cable so I cant flash anything from stock recovery. If I'll get USB-C pendrive will it be possible to flash stock ROM with stock recovery?
Click to expand...
Click to collapse
Fastboot this, it will DELETE EVERYTHING(no exceptions) (maybe except firmware) and install seraph08's cm13.
https://s.basketbuild.com/devs/Seraph08/oneplus2/fastboot img files
or flash stock OOS2.x official via stock recovery(if MTP or ADB works in stock recovery)
No idea about USB OTG, try dont buy. Might work in TWRP, dont think itll work on stock
or try the soft brick recovery on his basketbuild or other various available threads
Edit: you said fastboot works and then you said it doesnt work, confirm.
I used other PC and other tool including system.bin and userdata.bin. And it finally worked. Unbricked

this aint a phone.. Its Spawn from the darkest most vile debths of confusion!

First off i am not a noob. kinda.
the story:
I received this phone its a xt1625 prime variant (i think) already booting straight into boot loader (no system, recovery, bpmode, qmode)
just right into boot loader. So i figured it just needs flashed lets hit xda, get knowledge. it is now going on 6 months of off and on trying to flash this evil entity. this boot loader on here is like herpes, you cannot get rid of it (so i have heard). I have attempted every tutorial, downloaded every rom, twrp, firmware, etc possible to even imagine. Even tried all this in windows. ubuntu, etc. by every firmware i mean every link from here firmware.center/firmware/Motorola/Moto G4 (plus), add your own http, for every variant. and yet this boot loader remains. Even put it under a magnet from a 12' sub woofer over night. Taken the battery out for a week, overloading the chip with a car battery, nothing, the evil thing remains.
so my question is did i miss anything? also does anyone know the name and address of whomever wrote the coding for the gpt.bin,oem.img,modem,boot.img?
i'd like to have a chat with them personally.
oh and just for the record motorola will gladly replace the $159 dollar phone for $125 dollars, but have no idea how to fix it.
some of the firmware AMZ_NPJS25.93-14-7 through 14-10 will flash all the way then reboot into boot loader like nothing happened.
no blur or ota updates will flash/sideload stating that they are looking for athene and not athene_amz. yet no retail athene firmware will flash just athene_amz. absolutely no Mp firmware at all just Npjs. but only 7,8,10. which does nothing as i said before.
Can you post the get var info for this device please?
1) boot the device to bootloader
2) connect to your computer via USB
3) in the ADB terminal, type 'fastboot getvar all' without quotes and post the output here please, should be a list of device variables
Up to you if you wish to blank out the imei.
Have you unlocked your bootloader first?
motorola will not unlock the bootloader, which led me to believe its a prime.
i will do the getvar when i am home from work tonight.
and. thanks for responding
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

			
				
http://tinypic.com/r/qz554x/9
https://drive.google.com/file/d/1eF_el1N2Ve_APninuzEqvOlTSG1kSXCE/view?usp=drivesdk
those are getvar results.. or sad attempts at displaying them.
Thanks for the getvar log. According to the log:
The bootloader is locked (OEM_locked secure state), so no flashing any old ROMs. Also expected from devices with Amazon firmware, Motorola unlock keys won't work. G4 XT1625 as you mentioned
Unfortunately, the device is flashed with the latest NPJ25.93-14.7 US firmware for Amazon devices. Unfortunately we don't have access to that firmware (not been leaked on firmware.center or the Motorola Firmware Team on Android File Host), and because of the above locked bootloader, other firmware will be rejected as you've discovered. Therefore, you likely will have to wait for a leak of NPJ25.93-14.7 or later Amazon firmware for another try.
Can I ask what you mean by the device booting straight to bootloader - do you mean that powering on you'll only get the bootloader, and attempts to boot to recovery/start just send you back to the bootloader?
how would one go about formatting a phone like a hard drive just totally wipe it. Start new i am guessing it couldn't be that easy or every one would.
yes no attempt to start at all. everything leads back to fastboot mode.
its like the other partitions are not even there.
@Saul-66 as echo92 has previously said there is no latest stock images available to flash on your Amazon device,
but i have a little experiment to test,
you can try flashing older firmware but with latest gpt and Bootloader,
Also keep in mind if it boots, don't take OTA, it will brick again your device.
For safety, i will go steps by steps after confirmation of result.
First clean adb/fastboot folder if you have extracted any firmware in it, keep adb/fastboot files, or extract again in new folder, (Just for clean work and confusion)
Get OTA Update zip of September patch for Amazon device from here: https://forum.xda-developers.com/moto-g4-plus/how-to/amazon-prime-ads-moto-g4-september-t3703034
Take gpt.bin and Bootloader.img from that zip. (Delete remaining) put in adb/fastboot folder.
For now, use gpt and Bootloader commands only:
- fastboot flash partition gpt.bin
- fastboot flash bootloader bootloader.img
Tell us if those are getting flashed ?
Put screenshot of command prompt screen.
Then i will tell you next thing to go..
echo92 said:
Thanks for the getvar log. According to the log:
The bootloader is locked (OEM_locked secure state), so no flashing any old ROMs. Also expected from devices with Amazon firmware, Motorola unlock keys won't work. G4 XT1625 as you mentioned
Unfortunately, the device is flashed with the latest NPJ25.93-14.7 US firmware for Amazon devices. Unfortunately we don't have access to that firmware (not been leaked on firmware.center or the Motorola Firmware Team on Android File Host), and because of the above locked bootloader, other firmware will be rejected as you've discovered. Therefore, you likely will have to wait for a leak of NPJ25.93-14.7 or later Amazon firmware for another try.
Can I ask what you mean by the device booting straight to bootloader - do you mean that powering on you'll only get the bootloader, and attempts to boot to recovery/start just send you back to the bootloader?
Click to expand...
Click to collapse
Well if nothing else at least part of the mystery is solved. thank you for the light at the end of the tunnel!
____Mdd said:
@Saul-66 as echo92 has previously said there is no latest stock images available to flash on your Amazon device,
but i have a little experiment to test,
you can try flashing older firmware but with latest gpt and Bootloader,
Also keep in mind if it boots, don't take OTA, it will brick again your device.
For safety, i will go steps by steps after confirmation of result.
First clean adb/fastboot folder if you have extracted any firmware in it, keep adb/fastboot files, or extract again in new folder, (Just for clean work and confusion)
Get OTA Update zip of September patch for Amazon device from here: https://forum.xda-developers.com/moto-g4-plus/how-to/amazon-prime-ads-moto-g4-september-t3703034
Take gpt.bin and Bootloader.img from that zip. (Delete remaining) put in adb/fastboot folder.
For now, use gpt and Bootloader commands only:
- fastboot flash partition gpt.bin
- fastboot flash bootloader bootloader.img
Tell us if those are getting flashed ?
Put screenshot of command prompt screen.
Then i will tell you next thing to go..
Click to expand...
Click to collapse
There is no bootloader.img in Blur_Version.25.231.5.athene_amz.amz.en.US.zip
so i would have to probably take it out of ATHENE_AMZ_NPJ25.93-14.5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ?
Edit: they both say BL:B1.06 so should be the same in theory.
Saul-66 said:
There is no bootloader.img in Blur_Version.25.231.5.athene_amz.amz.en.US.zip
so i would have to probably take it out of ATHENE_AMZ_NPJ25.93-14.5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ?
Click to expand...
Click to collapse
In above post, you said, mystery is solved!
Then there is no need of those files right ? Or i didn't get it?
(Additionally: Bootloader wasn't updated in September patch, so it may be not included in that zip.)
____Mdd said:
In above post, you said, mystery is solved!
Then there is no need of those files right ? Or i didn't get it?
(Additionally: Bootloader wasn't updated in September patch, so it may be not included in that zip.)
Click to expand...
Click to collapse
part of the mystery is solved. tis what i said.

moto g4 stuck in fastboot mode (Hard brick)

hi, yesterday mi moto g4 xt1621 was working well but today when i switch it on it didn't show me the boot logo and started in fastboot mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so i tried to went to the recovery and it gave me an error which said: "start up failed:
your device didn't start up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant
AP Fastboot Flash mode (secure)
Fastboot reason: failed to initialize partition table
error: no bootimage found. skip to fastboot
boot up failed
i tried a lot of things, when i connected it to my pc recognizes it as Fastboot athene_13mp S
and i didn't get the software repair assistant
and
i don't know what to do if someone could help me, I would be very grateful
have you found the solution
adithya11198 said:
have you found the solution
Click to expand...
Click to collapse
unfortunately i haven't found the solution yet
System lost perhaps?
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
null2025 said:
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
Click to expand...
Click to collapse
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Omega Adrek said:
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Click to expand...
Click to collapse
Ok thanks adrek, i'm going to try it when my PC recognizes my smartphones again, it's another problem which I have but I don't want to bother you with that
Rom flashing failed . What should I do?
adithya11198 said:
Rom flashing failed . What should I do?
Click to expand...
Click to collapse
As the message says, it can't find a bootlogo. (usually logo.bin). If you've got a locked bootloader, you must have all key partitions, including logo.bin on the same patch level (and as such you may have to flash all partitions).
Which firmware did you try to flash and what flashing commands did you use, and can you show us the outputs of said commands?
This will help You : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
thank you
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you really much omega adrek, it worked, my moto g4 owe you its life

MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL

FOR ALL XIAOMI
BOOTLOADER MUST BE UNLOCKED
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
-----------------------------------------------------------------------------------------------------------
All your data will be erased
IMPORTANT
*****Please note that the clean all and lock box is checked by default*****
*****The path must be C:/MIFLASH/rom folder*****
Download the latest version of MI FLASH here :
https://xiaomiflashtool.com/
Extract the files from Miflash zip and place them in a folder named Miflash at the root of your hard drive.
Download a Fastboot Rom here https://xiaomifirmwareupdater.com/archive/miui/lmi/
Or
https://xiaomirom.com/en/series/ more firmwares.
Others devices
(Some devices have several versions hence the importance of knowing the code name)
https://xiaomifirmwareupdater.com/
https://xiaomirom.com/en/series/
EUXM=EEA Europe
MIXM=Global
TRXM=Turkey
RUXM=Russia
INXM=India
JPXM=Japan
IDXM=Indonesia
TWXM=Taiwan
CNXM=China
DEV=Public Beta
____________________________________________________________________________
TIPS:UNROOT BEFORE AND REMOVE LOCKSCREEN SECURITY
Battery charged at least 65%.
_______________________________________________________________________________________
-----------------Chinese device does not relock the bootloader--------
with a non-chinese rom,it will brick your device.
__________________________________________________________________________________________________________________________________
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
_____________________________________________________________________________
Open the TGZ file with 7-zip(or others)
_________________________________________________________________________
______________________________________________________________________
Move the folder to Miflash
​
_______________________________________________________________________________________________
Rename it​************************************ No long name, space, special characters.*********************************
_____________________________________________________________________________________________________
Launch MIFLASH and install drivers
_____________________________________________________________________________________________________
Select Rom folder
_________________________________________________________________________________________
Start the phone in fastboot mode(press and hold the power button and volume down button at the same time) and plug in to the pc.
REFRESH
Check the box at the bottom right CLEAN ALL.
Flash the rom.
At the end of the flash, miflash indicates an error (normal, no problem).
error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
the phone restarts unplug in.
​
Or easier one click method (which i prefer) if miflash gives some errors in flashing or installing.
Just connect phone in fastboot to pc, open fastboot rom and click on bat files to flash.
If I want to lock the bootloader (EU version) and return the phone to its stock state, then I have to select 'clean all and lock' or is there a specific reason on why selecting 'clean all'?
jovanv said:
If I want to lock the bootloader (EU version) and return the phone to its stock state, then I have to select 'clean all and lock' or is there a specific reason on why selecting 'clean all'?
Click to expand...
Click to collapse
select 'clean all and lock'
(unlock or lock erase data)
I did this when I first got the phone and flashed stock EU rom, Will do it again if no one else responds with any other methods, and I really need to use phone and hassle each time to set everything up after reflashing
Thanks
Can i re-lock the bootloader after root/Magisk ?
conmaxanhle said:
Can i re-lock the bootloader after root/Magisk ?
Click to expand...
Click to collapse
Better to unroot before
NOSS8 said:
Better to unroot before
Click to expand...
Click to collapse
Ok i will complete uninstall magisk and follow your guide
Hi, I'm trying to flash stock MIUI so i can do a clean flash of another custom ROM. But I'm stuck with an error that's MiFlash Tool is giving me.. The error says: Length cannot be less than zero. Parameter name: length. Does anyone know a fix for this? When i try to double click the flash_all bat my cmd just closes instantly when it opens. Pretty new to this so I'm worried i might brick something. Thanks
janjambon said:
Hi, I'm trying to flash stock MIUI so i can do a clean flash of another custom ROM. But I'm stuck with an error that's MiFlash Tool is giving me.. The error says: Length cannot be less than zero. Parameter name: length. Does anyone know a fix for this? When i try to double click the flash_all bat my cmd just closes instantly when it opens. Pretty new to this so I'm worried i might brick something. Thanks
Click to expand...
Click to collapse
Did you use the last Miflash?
Did you rename the rom folder?
did you use usb 2 port?
is the phone in fastboot mode?
Yes, latest MiFlash and called the folder 1204. I've tried both usb 2 and 3 with no luck. My phone is in fastboot mode but I must say i tried flashing the stock rom with XiaomiTool v2 since it did recognize my phone but it gave an error while flashing the super.img. So I'm pretty scared if ill reboot it will be stuck.
Also installed all drivers neccesary with my device called android phone -> android bootloader interface in Device Manager
janjambon said:
Yes, latest MiFlash and called the folder 1204. I've tried both usb 2 and 3 with no luck. My phone is in fastboot mode but I must say i tried flashing the stock rom with XiaomiTool v2 since it did recognize my phone but it gave an error while flashing the super.img. So I'm pretty scared if ill reboot it will be stuck.
Click to expand...
Click to collapse
This is surely the first attempt with XiaomiTool v2 that blocks, try to restart and then reflash with Miflash.
Anyway you will not be able to reset it without restarting
Make sure the ROM file has been extracted completely with no corrupted files.
Extract the ROM file in the root directory such as drive C:\ or D:\.
Make sure no single space in the folder name path.
Ensure the Mi Flash tool is run as Administrator (Right-click > Run as administrator).
NOSS8 said:
This is surely the first attempt with XiaomiTool v2 that blocks, try to restart and then reflash with Miflash.
Anyway you will not be able to reset it without restarting
Make sure the ROM file has been extracted completely with no corrupted files.
Extract the ROM file in the root directory such as drive C:\ or D:\.
Make sure no single space in the folder name path.
Ensure the Mi Flash tool is run as Administrator (Right-click > Run as administrator).
Click to expand...
Click to collapse
MiFlash is in this path along with the clean stock rom 12.5.4 global: C:\Program Files\Xiaomi\MiFlash
Should i plug out my phone, restart it, enter fastboot and try again?
janjambon said:
MiFlash is in this path along with the clean stock rom 12.5.4 global: C:\Program Files\Xiaomi\MiFlash
Should i plug out my phone, restart it, enter fastboot and try again?
Click to expand...
Click to collapse
1/move the miflash folder and the rom directly to C:/
retry flashing
It doesn't work unplug the phone and reboot in Fastboot mode and try again
NOSS8 said:
1/move the miflash folder and the rom directly to C:/
retry flashing
It doesn't work unplug the phone and reboot in Fastboot mode and try again
Click to expand...
Click to collapse
Flashing wont work because everytime i press refresh my phone doesn't show up and it gives me the error length can not be less than zero. Tried putting it directly in C:/ too. Thanks for taking your time btw I'm really grateful. I'm also a bit hesitant of restarting my phone because of fear for bootloops. Is that the only option you know?
My end goal is to flash the new hentai OS with android 12 and i was wondering (since i know how to do adb sideload) if i could sideload it now when it's in fastboot. Or should i try to firstly fix going back to stock MIUI?
janjambon said:
Flashing wont work because everytime i press refresh my phone doesn't show up and it gives me the error length can not be less than zero. Tried putting it directly in C:/ too. Thanks for taking your time btw I'm really grateful. I'm also a bit hesitant of restarting my phone because of fear for bootloops. Is that the only option you know?
Click to expand...
Click to collapse
Restart the phone and try again
NOSS8 said:
Restart the phone and try again
Click to expand...
Click to collapse
Plugged it out, restarted it back in fastboot and plugged it back in. Still the same error message.
janjambon said:
My end goal is to flash the new hentai OS with android 12 and i was wondering (since i know how to do adb sideload) if i could sideload it now when it's in fastboot. Or should i try to firstly fix going back to stock MIUI?
Click to expand...
Click to collapse
janjambon said:
Plugged it out, restarted it back in fastboot and plugged it back in. Still the same error message.View attachment 5431607
Click to expand...
Click to collapse
Did you extract the rom folder from the TGZ file?

Categories

Resources