Database Users

Erased phones recovery

Hi I have the XT1570, running unlocked and with rooted but stock 5.1.1. I have run in to some issues with the recovery part.
Firstly I wanted to go back to the recovery and flash a stock recovery so I could get the OTA for MM, i did that using fastboot, and the flash worked fine according to fastboot, however once i rebooted into recovery it would not load, got an error message, I forget now something about dumping back to bootloader.
Anyway i fixed it got TWRP back on again, then tried a different stock recovery, same thing same error, so i thought I would easily get back to TWRP by the same method, flash again. I was wrong, now fastboot told me , target reported max download size of 536870912 bytes
error: cannot load 'twrp-2.8.7.1-clark': No error
Remember this is the exact same TWRP image i have just flashed not 5 mins before.
So i thought ok then, maybe an old image is in there taking up space or something.
C:\Users\David\Desktop\Mfastboot\Mfastboot>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.017s]
finished. total time: 0.019s
Now I get the message:
Invalid boot image header.
Error:failed to load kernel
Boot up failed.
I presume I have deleted everything in the recovery partition, and so messed it up good, but I dont know how to fix it at this point.
I also erased the cache along the way (via fastboot) as I tried to get the OTA update to work anyway just to see what would happen, so I had to erase the cache to cancel updates
I must reiterate, I can boot into Android and use my phone no issues, at all, just I have no recovery at all and this means updates arent going to work, also i cant seem to find a reliable source for a stock recovery.
Some step by step help would be appreciated, as I am not an expert by any means on this.
Thank you.

Also my device was bought in China as that is where I am, it does indeed have the code name XT1570, dual sim, I would assume it is basically the same as the XT1572 asian. I do also have an original backup of the phone after unlocking bootloader, before root, which was my next port of call after changing the recovery back to stock.

fixed it i was just being foolish, someone delete this thread it is of no use.

Can you explain how you fixed it? I too have deleted the recovery in an attempt to flash twrp, but now neither twrp nor the stock recovery are there?
Tapatalk'd from my Twisted, Racing Nexus 5

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

Can not install rom stock, and error during upgrade via ota?

After flashing some roms I came across the following situations:
1: mtp on recovery twrp no longer works. (Previously used normally)
2: I can not install any rom custon (even those based on rom stock)
3: I can not install rom 19S or larger via fastboot (bootloader)
4: I can not install any rom stock (even if I use official recovery)
* Fastboot flash system system.img
Target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Please help me!

Help please, I can not install any roms!
1: mtp on recovery twrp no longer works. (Previously used normally)
2: I can not install any rom custon (even those based on rom stock)
3: I can not install rom 19S or larger via fastboot (bootloader)
4: I can not install any rom stock (even if I use official recovery)
* Fastboot flash system system.img
Target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Please help me![/QUOTE]

Turn ON in dev options;
-OEM unlock
-Debugging
Turn on your phone in bootloader mode, turn on ADB and write;
- "fastboot oem unlock-go"
Download TWRP that should work with your model (x720 or x727, pick correct) and flash it through bootloader.
- "fastboot flash recovery twrp.img" (or another name that your TWRP image in adb folder have)
- "fastboot boot twrp.img" (as same)
After this, your phone should be in Recovery <TWRP> mode. It should ask about keep System Read only.
- Swipe to Allow Modification
If this steps won't help you, you should make wipe. But if you can't install OS now, it's riskable, so I won't to guide you there.
* or if your trouble is a upgrade from stock to stock OS, unlocked bootloader and TWRP can be a problem.

Rone3285 said:
After flashing some roms I came across the following situations:
1: mtp on recovery twrp no longer works. (Previously used normally)
2: I can not install any rom custon (even those based on rom stock)
3: I can not install rom 19S or larger via fastboot (bootloader)
4: I can not install any rom stock (even if I use official recovery)
* Fastboot flash system system.img
Target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Please help me!
Click to expand...
Click to collapse
marik1 said:
Turn ON in dev options;
-OEM unlock
-Debugging
Turn on your phone in bootloader mode, turn on ADB and write;
- "fastboot oem unlock-go"
Download TWRP that should work with your model (x720 or x727, pick correct) and flash it through bootloader.
- "fastboot flash recovery twrp.img" (or another name that your TWRP image in adb folder have)
- "fastboot boot twrp.img" (as same)
After this, your phone should be in Recovery <TWRP> mode. It should ask about keep System Read only.
- Swipe to Allow Modification
If this steps won't help you, you should make wipe. But if you can't install OS now, it's riskable, so I won't to guide you there.
* or if your trouble is a upgrade from stock to stock OS, unlocked bootloader and TWRP can be a problem.
Click to expand...
Click to collapse
I was with the rom "GROSSOSHOP 18S", then cleaned all data including system, and installed rom "MIUI 8 VillarLeg V2", after testing the rom I tried to go back to stock, I did the following:
1 - I cleaned all data including system
2 - put the rom rom in the internal memory and rename to update.zip
3 - I tried to install the rom, but got stuck in: patching system image unconditionally
After several attempts to install rons, only to achieve with "GROSSOSHOP 17S" via fastboot. It seemed that everything was solved, but I can not install any more roms except for fastboot, I already tried with stock recovery and twrp, but it does not work at all!

Check dev options and oem unlock...

VNS-L31 P9 Lite Bricked

Hi here !
I own a VNS-L31
Bootloader is unlocked
I tried to update to Android 7, but I bricked it because of the recovery was a TWRP for Android 6
Now, the device is bricked to the loading screen.
So, I tried with fastboot to flash files.
fastboot flash boot BOOT.img -> OK
fastboot flash recovery RECOVERY.img -> OK
but :
fastboot flash system SYSTEM.img -> I get the same error :
target reported max download siez of 471859200 bytes
sending sparse 'system' <451240 KB>
OKAY ( 20.390s)
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. Total time: 20.720s
Click to expand...
Click to collapse
I tried with the toolkit to flash the 4 images, but I always get the same answer : no device detected! blabla
However, the drivers are installed. I installed HISuite before all these...
What I can do now with myt brick :
boot to fastboot mode
boot to eRecovery (but no way to download anything, I doesn't work...)
nothing else.
I read this forum and all posts relative to P9 Lite brick, but I can't do anything until the SYSTEM.img file is written to the phone
Thank you for reading me

1. Download adb drivers...search on Google adb all in one installer it's on xda forums.
2. Download adb minimal package also search on Google and it's also on xda.
Try those 2first .

Kcetin20 said:
1. Download adb drivers...search on Google adb all in one installer it's on xda forums.
2. Download adb minimal package also search on Google and it's also on xda.
Try those 2first .
Click to expand...
Click to collapse
Hi
ADB drivers are already installed, by the method you given.
I can use ADB, the P9 is recognized.
The problem occurs always and only with the toolkit. My device is not recognized with it...
I can flash recovery, I was able to use dload, I pushed a Nougat firmware, and now, I have a TWRP recovery, but the phone is always blocked.
With the recovery, I noticed another problem. As you can see on the picture, partitions cannot be mounted. I don't know why...
https://goo.gl/photos/BPb6AHnDMD11gXSS6

Gnubox said:
Hi
ADB drivers are already installed, by the method you given.
I can use ADB, the P9 is recognized.
The problem occurs always and only with the toolkit. My device is not recognized with it...
I can flash recovery, I was able to use dload, I pushed a Nougat firmware, and now, I have a TWRP recovery, but the phone is always blocked.
With the recovery, I noticed another problem. As you can see on the picture, partitions cannot be mounted. I don't know why...
https://goo.gl/photos/BPb6AHnDMD11gXSS6
Click to expand...
Click to collapse
This device is really hard to flash some firmwares....
if you're out of options you can try to use DC Phoenix it cost 10-15$ i believe : https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial

I would try to re-flash Nougat by the dload method first. You could also try to flash VNS-L31C432B160. For some reason it is more readily accepted by a bricked VNS-L31 than other full firmware.
If that fails, I'd resort to DC Phoenix.

essential phone soft bricked after i tried to root with magisk

EDIT: FIXED
hi everyone, ive already rooted an essential phone in that past so i was a bit overconfident i guess, i followed all the steps in the main post https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976 but when i went to twrp to install the boot img and magisk zip i got an error that i couldnt mount to system, i realized that i had forgotten to set my mount to system so i rebooted into twrp to re instally but through system mount. it just went into a bootloop, so i decided to return my phone back to stock and redo..... well now i can wipe the device or use a flashall, my phone has no data at all, is still recognized in fastboot but it just wont work. i get errors:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.006s
and:
when trying to use fastboot -w, phone still dosent boot and flashall fails because the phone hasnt been wiped, any help please? im phoneless right now, an yes i have tried different usb cords and ports. thank you so much!
edit: not sure if its working yet but i just wiped everything through twrp so that twrp uninstalled and now the back to stock flashall seems to be working, fingers crossed!
edit 2: it goes through the whole back to stock script with everything in adb but when its done it restarts and keeps doing that. ive stopped it the second it says done as well (after it finished writing all of system b) but when i start my phone it just immediately reboots into recovery or bootloader.....

nominath654 said:
hi everyone, ive already rooted an essential phone in that past so i was a bit overconfident i guess, i followed all the steps in the main post https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976 but when i went to twrp to install the boot img and magisk zip i got an error that i couldnt mount to system, i realized that i had forgotten to set my mount to system so i rebooted into twrp to re instally but through system mount. it just went into a bootloop, so i decided to return my phone back to stock and redo..... well now i can wipe the device or use a flashall, my phone has no data at all, is still recognized in fastboot but it just wont work. i get errors:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.006s
and:
when trying to use fastboot -w, phone still dosent boot and flashall fails because the phone hasnt been wiped, any help please? im phoneless right now, an yes i have tried different usb cords and ports. thank you so much!
edit: not sure if its working yet but i just wiped everything through twrp so that twrp uninstalled and now the back to stock flashall seems to be working, fingers crossed!
edit 2: it goes through the whole back to stock script with everything in adb but when its done it restarts and keeps doing that. ive stopped it the second it says done as well (after it finished writing all of system b) but when i start my phone it just immediately reboots into recovery or bootloader.....
Click to expand...
Click to collapse
"fastboot -w" is the command to wipe all user data.
Why are you trying to wipe things through twrp?
Back to stock and add?
The script is run vis fastboot.
Which ROM are you trying to install?
Get either the latest 8.1 or P Beta from the ROM threads.
Try flashing one of those.
Did you unlock_critical?

tech_head said:
"fastboot -w" is the command to wipe all user data.
Why are you trying to wipe things through twrp?
Back to stock and add?
The script is run vis fastboot.
Which ROM are you trying to install?
Get either the latest 8.1 or P Beta from the ROM threads.
Try flashing one of those.
Did you unlock_critical?
Click to expand...
Click to collapse
hi, i had soft bricked so i tried to wipe everything to flash back to stock, anyway i got it to work, was being stupid. ill update the thread. TY!