Related
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
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]
So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.
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.
Hi guys
I destroyed my leEco le pro 3 x722
After passing the custom rom
Now the device is locked on fastboot only
There is no system and no recovery
The problem I have now is the decryption. If the oem unlock is I can update it. Please help oem unlock
The device does not respond to commands
Everything is written
PS C: \ adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (39337 KB) ...
OKAY [0.895s]
writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.940s
How can oem unlock in another way ????
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
You installed Batyan's 20s developer ROM
In the past I opened the boot loader but when I tried Rum Miwi did not work
I wanted to go back to the official 26s Rom
Unfortunately everything has lost and the device is ruined
I did not see the warning of testing
How is the solution now
The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/
sk8223 said:
The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/
Click to expand...
Click to collapse
Yes, unfortunately, the device is locked
Updated 26s
The manufacturer must find us a solution
Thank you for the kind word
sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium
mchlbenner said:
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Unfortunately I do not know how to scroll
Our Lord is wrong
PS C:\adb> fastboot devices
7b61ab59 fastboot
PS C:\adb> fastboot flash emmc_appsboot.mbn
unknown partition 'emmc_appsboot.mbn'
error: cannot determine image filename for 'emmc_appsboot.mbn'
PS C:\adb> fastboot flash emmc_appsboot.zip
unknown partition 'emmc_appsboot.zip'
error: cannot determine image filename for 'emmc_appsboot.zip'
That file has to be in adb main file.
Sent from my LEX727 using xda premium
mchlbenner said:
That file has to be in adb main file.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
If you have a file please give me the link
Or where I find it
I think you talk about different terminals.
The X722 with 26S strock brick CAN NOT FLASH FOR FASTBOOT.
Greetings.
fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn
meangreenie said:
fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn
Click to expand...
Click to collapse
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...
toufik_d said:
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...
Click to expand...
Click to collapse
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.
how you wiped everything?
do you have recovery?
F.J.V said:
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.
Click to expand...
Click to collapse
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium
mchlbenner said:
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Of course.
That's what I say, for X720 and X727.
For X722 DOES NOT WORK
Greetings.
danielpinto8zz6 said:
how you wiped everything?
do you have recovery?
Click to expand...
Click to collapse
I wanted to restore the official order
The device is running on fastboot only