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

how to recover?

Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.

algnerd said:
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
Click to expand...
Click to collapse
Boot.img , recovery.img , cust.img , system.img.

Claleale said:
Boot.img , recovery.img , cust.img , system.img.
Click to expand...
Click to collapse
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?

algnerd said:
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
Click to expand...
Click to collapse
Yes

Claleale said:
Yes
Click to expand...
Click to collapse
Flashing cust and system returned failes
For cust: (failed remote: partition error)
For syst: (failed remote: sparse flash write failure)

Since I was running nougat before messing up the phone, it had to be System and Boot extracted from the nougat update

By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice... I would never flash that but okay, that's why we are here
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM / AICP?

Schlengge said:
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice...
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM?
Click to expand...
Click to collapse
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )

algnerd said:
...
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
You have to use the report button on your own OP. In the report text box, just ask mods to close your thread. The mod who is assigned to this forum will handle your request.

algnerd said:
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers

thomasedwardbullen1986 said:
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
Click to expand...
Click to collapse
May god have mercy on your soul.
For the downgrade, I didn't use the b161 directly. I flashed some oeminfo provided in the same folder as the TWRP. Then used b150 ans the three boutons method. Worked like a charm.
Hope it will help you downgrade your phone.

I have the same problem, someone could explain it to me step by step, please

ask help
Hello
My name is EL HADJI MODOU SOW.I request your help concerning a big problem that I meet with my phone huawei P9 lite vns-l31c113b364 (these is the serial number 4TE0216B08004097) .in fact I wanted to activate the second sim then j I made a mistake handling the shot the system is corrupt and now I can not use my phone. I tried to flash it but I can not find a good frimeware. All the flash files that I find are working except the cust.img , vendor.img and product.img. what happens when I flash the cust.img (H: \ SRKToolHuawei-Lod-Chong-V2.0-20161002> fastboot flash cust CUST.img
target reported download size of 471859200 bytes
sending 'cust' (435462 KB) ...
OKAY [10.711s]
writing 'cust' ...
FAILED (remote: partition error)
finished. total time: 10.729s).
please help me I'm really teriified
this is my email:[email protected]

TWRP on Nougat

I saw where someone said you could flash B20 bootloader and flash TWRP on Nougat, is this true? Is anyone working on a guide for Nougat TWRP and root. On another note I thought that I read that ZTE would be bringing Wifi calling for Nougat with carries such as T-Mobile? I was unable.to find it under options and assume that it is not possible, anyone have any idea about this.
Thanks

I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?

jim262 said:
I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?
Click to expand...
Click to collapse
I got TWRP 3.0.4 installed (as well as 3.0.3-1)... It installed sucessfully via Fastboot for me, I even flashed SU, but I couldn't get my phone to boot into the OS (tried with and without SU).......It just hung at the boot pre-boot screen (where it warns you the bootloader is unlocked). I'd restart it, and it always hangs at that screen..... Only way to fix it was to boot back into TWRP, revert back to B29 (using DrakenFX guide) and then update to Nougat again. I spent about 16 hours straight working on this on Tuesday, before I gave up and decided to keep it stock until a custom ROM comes out, soon (Z.A.D. v.4), hopefully?

I have an issue where I installed B15 but whenever I boot my phone, it hangs on the Linux Tux logo. Any fix?

xDaDeevellopar said:
I have an issue where I installed B15 but whenever I boot my phone, it hangs on the Linux Tux logo. Any fix?
Click to expand...
Click to collapse
You probably pushed the power button to "Start"? Try letting it sit there about 10-15 seconds, if it won't boot...This is the exact same problem I had. I had to go back to B29, then do the update again. There is now a B15 "return to stock" walk-through, that may be the quicker route.....But I know returning to B29, turning on OEM Unlock in Dev options and then taking the update via your SD card was what I did (3 times in one day).

Flash signed TWRP with tennear's tool (axon7tool):
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://we.tl/dv78KwQZCY
and then follow this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
3 files and 10 minutes of your time for TWRP + unlocked bootloader

bornlivedie said:
Flash signed TWRP with tennear's tool (axon7tool):
https://forum.xda-developers.com/axo...overy-t3514254
https://we.tl/dv78KwQZCY
and then follow this guide:
https://forum.xda-developers.com/axo...-stay-t3461165
3 files and 10 minutes of your time for TWRP + unlocked bootloader
Click to expand...
Click to collapse
Those 2 XDA links don't work, take me to a generic XDA 404 error page (on both)...the WeShare page worked.

tele_jas said:
Those 2 XDA links don't work, take me to a generic XDA 404 error page (on both)...the WeShare page worked.
Click to expand...
Click to collapse
That's because I copypasted lol
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165

bornlivedie said:
That's because I copypasted lol
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Click to expand...
Click to collapse
If my bootloader is already unlocked, can I skip that part (the 2nd link)?? Or is it necessary?

tele_jas said:
If my bootloader is already unlocked, can I skip that part (the 2nd link)?? Or is it necessary?
Click to expand...
Click to collapse
Those steps are meant to unlock the bootloader.
You don't need any of it. You already have TWRP (skip step 1) and bootloader unlocked (skip step 2) so yeah...
What do you want exactly?

bornlivedie said:
Those steps are meant to unlock the bootloader.
You don't need any of it. You already have TWRP (skip step 1) and bootloader unlocked (skip step 2) so yeah...
What do you want exactly?
Click to expand...
Click to collapse
My bootloader is unlocked (back when ZTE actually provided the unlocking)....adb fastboot works on my phone as well and I've flashed TWRP (3.0.4 and 3.0.3-1) and it's booted into TWRP, but I cannot boot into the actual OS...My phone goes all black and just hangs there, I think this may be booting directly into EDL mode and not the OS? I can plug my phone into the computer and my computer makes noises as if a USB device has been attached, but my screen is completely black. If I push the start button while the phone is booting (to bypass the bootloader is unlocked warning screen), I boot to a small penguin screen.
The only thing I can do from there is revert back to stock B29, then update back to stock B15.
I want to be able to install TWRP, root my phone, on Nougat, and be able to use my phone too?

tele_jas said:
My bootloader is unlocked (back when ZTE actually provided the unlocking)....adb fastboot works on my phone as well and I've flashed TWRP (3.0.4 and 3.0.3-1) and it's booted into TWRP, but I cannot boot into the actual OS...My phone goes all black and just hangs there, I think this may be booting directly into EDL mode and not the OS? I can plug my phone into the computer and my computer makes noises as if a USB device has been attached, but my screen is completely black. If I push the start button while the phone is booting (to bypass the bootloader is unlocked warning screen), I boot to a small penguin screen.
The only thing I can do from there is revert back to stock B29, then update back to stock B15.
I want to be able to install TWRP, root my phone, on Nougat, and be able to use my phone too?
Click to expand...
Click to collapse
Then follow this:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
and flash this:
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I think I know what happened to you... did you by any chance allow system modifications in TWRP? That makes the OS bootloop if you have Nougat.

bornlivedie said:
Then follow this:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
and flash this:
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I think I know what happened to you... did you by any chance allow system modifications in TWRP? That makes the OS bootloop if you have Nougat.
Click to expand...
Click to collapse
The MiFlash program found my phone, but failed every time I ran it.. So, I just bit the bullet and downloaded the latest TWRP 3.0.4-1 and flashed that.....And it worked! I then flashed SU, my fonts and changed my Emoji's....I'm about there with customization, and it's all booting up just fine!
But, yes the first few times I did allow system modifications......But I also did this last time too and it's working fine?

[Solved] Bricked and can't write system

I erased everything in an attempt to unbrick it but that was a mistake. What I have tried and results:
-twrp recovery tried to install the latest stock firmware but got error with mounting system.
-fastboot flash update update.zip didn't solve it
-fastboot seperatly flashing each image, extracted by the update extractor tool. Result:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (451240 KB)...
OKAY [ 23.882s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 23.958s​-fastboot -w to reformat and try again. Result:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.012s​OEM is unlocked, I have tried updating from the SD and using the three buttons but I get the wrong format error. Downloaded the MM version as well but I get the incompatible error. Can't download from the erecovery or Hi-Suite. Help please

Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method

d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.

Badwolf9 said:
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.
Click to expand...
Click to collapse
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.

I believe ur in nougat beta... Just flash oem info and flash again the nougat from there you can start again and downgrade peacefully

your bootloader is locked

Sh0m1 said:
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.
Click to expand...
Click to collapse
Thank you! I followed the instructions here with a slight variation. Because trying to install the update.zip file always gave me errors I extracted the update.APP with the update extractor tool and flashed cache,system,boot with fastboot. Then I opened the custom recovery, installed the other zip file and continued as instructed.

mjz2cool said:
your bootloader is locked
Click to expand...
Click to collapse
No it wasn't. This was my first thought as well.

Badwolf9 said:
No it wasn't. This was my first thought as well.
Click to expand...
Click to collapse
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked

mjz2cool said:
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked
Click to expand...
Click to collapse
fastboot oem device-info
Also if it was locked I wouldn't be able to flash anything.

d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
where can I find the oeminfo file?

islandman75 said:
where can I find the oeminfo file?
Click to expand...
Click to collapse
This is the L21 - SingleSIM:
https://www.dropbox.com/s/97uad8vc3pwppnq/oeminfoORIGINAL.img?dl=0
And the L21 - DualSIM:
https://www.dropbox.com/s/fq99atzszg2sq1y/oeminfoDUAL.img?dl=0

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.