Database Users

MX4 bootloop brick after trying to update I firmware on A phone

SOLVED:
Hi,
I just bricked my MX4 after trying to update system image from 4.5.6 to 4.5.7 using this guide:
Extract I version update.zip
use sdat2img to create system image
dd system image to system partition on live phone and reboot.
I used the same procedure successfully before, x-updating 4.5.4A ti I then updating to 4.5.6I.
After updating to 4.5.7, the phone goes into an infinite loop of Meizu splash screen, Flyme balloon, reboot.
I can enter fastboot and official recovery, but can't flash any partition from fastboot.
The bootloader is still locked.
Does anyone have any advice for unbricking?
Update:
The bootloop suddenly froze up for long enough for me to use adb to push an update.zip to the "sdcard" root. Have now flashed 4.2.8A from recovery and booted the phone.
As I had to clear all data I will unlock bootloader before trying anything else.

Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me

bobslesbricoleurs said:
Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me
Click to expand...
Click to collapse
Hi,
I managed to push 4.2.8.2 to sdcard then do a normal recovery reflash.
Have now successfully unlocked using the .apk method.
Now I need to find out if I can use that unlocked bootloader to flash recent "I" firmwares, or if I can only flash the unfinished cyanogen (would like to wait 'til that's a bit more polished before using it.
Anyway. Happy to have my phone back!

Maybe that newest 4.5.7I need a new kernel so you'll need to update to 4.5.7A before flashing system.img or you can flash directly 4.5.7I but you'll need to use fastboot flash boot boot.img
If a rom/firmware needs a specific kernel it'll bootloop if you don't flash it

Can I flash 4.5.7 I now that I have unlocked bootloader and custom recovery? If I understand the unlock threads correctly, I think I will relock the bootloader, or even brick if I try to flash the complete update.zip. Can I flash system and boot partitions using fastboot?

Fully BRICKED.
Now I FULLY bricked it (no more recovery).
Had successfully upgraded to 4.5.7 "I" and was installing super su for full root, before disabling update, but had forgotten that I still had official 4.2.8 rom as update.zip on "sdcard" root.
rebooted to TWRP recovery for full su install and recovery found the update.zip and flashed it.
Result: Bootloop, No recovery, locked fastboot, no possibility to flash anything.
Aaargh!

Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)

Fixed with large hammer! Goodbye Meizu!
Learnincurve said:
Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Fixed with large hammer! Goodbye Meizu!

fastboot boot recovery.img isn't a command at all... It's fastboot flash recovery C:/path/to/recovery.img

Unable to flash TWRP (remote: dtb not found)

When I try to flash TWRP (via "fastboot flash recovery twrp.img" then "fastboot boot twrp.img") I receive the following error:
Downloading 'boot.img'
OKAY [1.477s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.534s
I've tried manually booting it into recovery with power button and volume down but it just freezes on the oneplus logo where I have to turn off and on again.
Any help is greatly appreciated!

I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3

that link just saved me!

I tried this recovery (I had the same problem as the OP) but although I can boot into twrp, I get stuck on the oneplus logo if I try a normal boot?
Sent from my Nexus 9 using XDA-Developers mobile app

I managed to get it working by flashing CM after flashing the recovery.
Sent from my Nexus 9 using XDA-Developers mobile app

Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?

pitrus- said:
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
Click to expand...
Click to collapse
Actually, fastboot boot twrp.img boots the TWRP image without flashing it.
fastboot flash recovery twrp.img flashes the TWRP image to the recovery partition.
Both are valid commands and have their uses.
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.

Spannaa said:
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Click to expand...
Click to collapse
That's exactly what I meant to convey.

Similar problem while flashing recovery
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help

bhanuodin said:
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
Click to expand...
Click to collapse
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.

pitrus- said:
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
Click to expand...
Click to collapse
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.

bhanuodin said:
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
Click to expand...
Click to collapse
The bootloader (also called fastboot) comes with the original ROM. In your case you're already on the newer bootloader since you flashed OOS3 which means you will have to flash recoverys and ROMs compatible with this newer bootloader.
This TWRP should be compatible
https://dl.twrp.me/oneplus2/twrp-3.0.2-1-oneplus2.img.html
Also you can't run ROMs not compatible with this newer bootloader (which means pretty much any ROM that's not using the official Cyanogenmod source tree for building). That is except for OOS3 or newest HOS of course since these are made for the newer bootloader.
However I would say the error message you get might be caused by bad cable, faulty driver setup, faulty fastboot tool version or in worst case damaged partition layout on phone. The last one can be fixed by the Qualcomm OOS2 factory restore solution.

Hi, i am having the same problem.
some background: I was on Oxygen OS 2.x.x, i wanted to upgrade to Exodus 6. I had the older version of TWRP. So I tryed to install the new twrp image within twrp. When i rebooted i couldnt boot into twrp, receiving the same error message as in OP title, when using fastboot.
Using the tool all in one toolkit I was able to flash stock recovery.
But I still cant flash Twrp.
I can still boot into system though.
Any advice? Thanks.

That explains why you're having problems. You're doing it the wrong way.
First you must upgrade the bootloader by either flashing the convert to Marshmallow zip file which also installs the correct TWRP for the new bootloader (easiest way). Or you could flash the latest official OOS3, then fastboot flash the latest TWRP and from there format system and flash the ROM that's using the newer bootloader.

Does that Link work with oneplus x also? Having same problem as Higgings when trying to install twrp and cyanogenmod.

thnx a lot for sharing
:good:
Higgings said:
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
Click to expand...
Click to collapse

Yet Another Bootloop Thread

Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!

Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.

jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?

bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps

Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
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.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.

bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
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.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that

Please help. Not sure what to do next.

Hi all,
I have a Moto G5 Plus that I brought on Amazon Prime day (11/07/17). and after trying to install TWRP I have ran into problems.
Heres what happened and where I'm left.
1) I unlocked the Bootlloader via moto website. No problems I now receive the BS message about the phone being unlocked.
2) Tried flashing twrp_3.1.1-0_potter.zip using "fastboot flash recovery twrp_3.1.1-0_potter.img"
Whenever I performed this command and rebooted in recovery I was never taken into the TWRP screen, but taken a screen showing a droid on it back with a message saying no command. I found how to bring up the command menu, but trying to flash the custom roms from the stock recovery always failed.
3) I used this article https://forum.xda-developers.com/g5-...-plus-t3605667 and found using this did allow me to boot into the TWRP screen. The only difference i noticed was that when i used the article mentioned above to get into TWRP the phone displayed the Moto boot ami before going into TWRP. It never did this when i used the Flash command manually.
4) Once in TWRP i flashed supersu and the RR .img, wiped cache etc..
On exiting TWRP I was asked whether I wanted TWRP installed as a system app, i selected yes to this question and now.....
5) BRICKED!!!
My moto will only boot into fastboot now and I get this message:-
Start up failed:
the bs about software repair assistant etc.
ap fastboot Flash Mode (secure)
Error: failed to load kernel!
Fastboot Reason: Fall-through from charge boot mode
usb....
6) I tried using this article https://forum.xda-developers.com/g5-plus/how-to/npn25-137-33-stock-firmware-t3577081
But I'm unsure of this version to use?
My question is can anyone help me to at least get my phone working again. Thanks will be paid.

JammieB said:
I have a Moto G5 Plus that I brought on Amazon Prime day (11/07/17). and after trying to install TWRP I have ran into problems.
Click to expand...
Click to collapse
Which Amazon Moto G5 Plus did you buy on Prime Day? The cheaper subsidized Amazon Prime version with ads or the more expensive non subsidized version without ads?
Apparently you cannot unlock the bootloader on the subsidized ad based Amazon Prime version. This is well discussed. One such discussion from the Lenovo/Moto support forum:
https://forums.lenovo.com/t5/Moto-G5-Moto-G5-Plus/Is-there-anyway-to-unlock-my-Moto-G5-Plus-from-Amazon/td-p/3638019
If one does a forum search on this site they'll find past discussions indicating the bootloader on Amazon Prime subsided Moto G5 Plus phones cannot be unlocked.

Try the Toolkit.
Once in it flash the TWRP and boot_image and try rebooting. If that doesn't work flash the Stock ROM and then flash the TWRP and boot_image. Once you get those flashed you should be able to flash the latest TWRP using fastboot.
Please let me know if that fixed it.
Thanks,
CP

cyber_prometheus said:
Try the Toolkit.
Once in it flash the TWRP and boot_image and try rebooting. If that doesn't work flash the Stock ROM and then flash the TWRP and boot_image. Once you get those flashed you should be able to flash the latest TWRP using fastboot.
Please let me know if that fixed it.
Thanks,
CP
Click to expand...
Click to collapse
Thanks for the suggestion, however I have tried this toolkit already and when connecting the USB cable, the toolkit only ever says connecting to device, but never manages to actually connect. As such, no command from the toolkit can be run, as when tried I get a "no device" message.
Also when I try to use the toolkit to install Windows 64bit driver, the install stops telling me I have a newer driver installed already.
Do you think I should uninstalled the newer device driver or should the toolkit still connect using the newer driver?

bennor3814 said:
Which Amazon Moto G5 Plus did you buy on Prime Day? The cheaper subsidized Amazon Prime version with ads or the more expensive non subsidized version without ads?
Apparently you cannot unlock the bootloader on the subsidized ad based Amazon Prime version. This is well discussed. One such discussion from the Lenovo/Moto support forum:
https://forums.lenovo.com/t5/Moto-G5-Moto-G5-Plus/Is-there-anyway-to-unlock-my-Moto-G5-Plus-from-Amazon/td-p/3638019
If one does a forum search on this site they'll find past discussions indicating the bootloader on Amazon Prime subsided Moto G5 Plus phones cannot be unlocked.
Click to expand...
Click to collapse
Im 100% confident that my moto has had its bootloader unlocked and that I was not sold a Moto G5 Plus with amazon ads.....
Thanks for your suggestion though.

FIXED back to stock rom. Here's what I did:-
1) Downloaded the stock rom from https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084
Used the mega link it took 5mins (1.4 mbps) to download.
2) Then run these commands:- (thanks to https://forum.xda-developers.com/member.php?u=5033408)
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (gave error about bootloader)
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot oem lock
fastboot reboot
It still see the annoying unlocked bootloader screen, but my moto boots into the stock rom.
I'm not giving up on getting a custom rom onto this device, but thanks to anyone who's helped me to get back to square one.

JammieB said:
Thanks for the suggestion, however I have tried this toolkit already and when connecting the USB cable, the toolkit only ever says connecting to device, but never manages to actually connect. As such, no command from the toolkit can be run, as when tried I get a "no device" message.
Also when I try to use the toolkit to install Windows 64bit driver, the install stops telling me I have a newer driver installed already.
Do you think I should uninstalled the newer device driver or should the toolkit still connect using the newer driver?
Click to expand...
Click to collapse
I didn't install the drivers with the toolkit. Was your phone connected to it in fastboot mode? That's what I had to do to get it to detect mine.
If you can't get the toolkit to work you can still use fastboot to flash the included version of TWRP and the modified boot_image. They're located in TOOLKIT_DIR\resources\app.asar.unpacked\files.
CP

Moto G4 xt1625 Amazon variant bricked with Oreo

Hi I flashed the ATHENE_RETAIL_8.1.0_OPJ28.111-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in my Moto G4 Amazon variant phone.
Now the phone is stocked at logo.
Has anyone root this model with bootloader locked ?

meolivares06 said:
Hi I flashed the ATHENE_RETAIL_8.1.0_OPJ28.111-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in my Moto G4 Amazon variant phone.
Now the phone is stocked at logo.
Has anyone root this model with bootloader locked ?
Click to expand...
Click to collapse
You cannot root with a locked bootloader.

i have the same issue, wondering if any solution out yet ?

henser said:
i have the same issue, wondering if any solution out yet ?
Click to expand...
Click to collapse
Could try LMSA Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs

sd_shadow said:
Could try LMSA Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
i've just tried, tried rescue but i got an error when trying to install flashboot flash error. Says Flash failed, try again. stuck at 68 Percent

Currently looking in to flashing this.
Did you all try to flash the rom as a single file in twrp or similar or did you try to flash individual files to individual partitions?
With fastboot like:
DO NOT USE FOR THIS PHONE, SHOWN AS EXAMPLE!
sudo fastboot flash bluetooth BTFM.bin
sudo fastboot flash dsp dspso.bin
sudo fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
I used this kind of code for flashing new software to my G7
(Sudo is for using these commands in linux)

Restore
Just follow those steps, doesn't matter if you have the bootloader locked.
Important:
Next time, unlock the bootloader and install a custom recovery, twrp is the most common. After that flash the 8.1, it will reboot several times like if it has a problem but thats just the android config. Don't panic if you see it reach the homescreen and reboot, 3 or 4 times. It will do that untill you see the finishing progress bar prompt when it boots to homescreen

will give a try with this to see if it works.
edit tried, with 7.0 and the second command says preflash validation failed, with 8.1.0 the phone says okay all the commands but when i reboot the phone gets stuck on the blue m logo