I would like to tell you my problem, I have a Mate 9 MHA-L09C432B368.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in XDA
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
Help
Hello how are you. I had the same problem, I could not access to erecovery or recovery and worse to the system. only ERROR MODE appeared on the screen, Func NO: 11 (recovery image) Error NO: (image Failed!) .. could enter fastboot mode. with PHONE Unlocked and FRP Unlock but I took it to the official technical service of my country and they told me that it had no solution. at the time of testing on my computer I was left with PHONE Relocked and FRP lock in the fastboot. I have the code of my Bootloader and the FRP even though I can not unlock it to install files to my phone. help
hybrid09 said:
I would like to tell you my problem, I have a Mate 9 MHA-L09C432B368.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in XDA
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
Click to expand...
Click to collapse
I think I can help the same happened to me. Is FRP still unlocked?
Re: I stuck with my Mate 9 Error mode numbers 11 and 2
Newrooter22 said:
I think I can help the same happened to me. Is FRP still unlocked?
Click to expand...
Click to collapse
Hi my phone have bootloader and FRP unlocked you can fix your phone for this error mode 11 and 2 ?
I wanted to ask please if this Thread can be closed since I could solve the problem, I share the solution which I obtained through a partner of the website HTC Mania @rodrigocarlosqm to which I am immensely grateful. Thanks to your generosity I was able to recover my phone and I do not want as a paperweight, the arrangement was simple buy credits in dc phoenix, in my case download the official version oreo 368, extract the update.app file and place it in the flashing program, restart the cell phone, in case it does not do so automatic do not panic turn it off and let it turn on normally, enter the recovery stock, make a wipe, then restart and return to the recovery in this case make a wipe hard reset, restart and terminate once that happens the phone it will restart again and once this is done, the operating system will start without any inconvenience. Thank you very much to everyone who helped with the help and ideas. I could find the result and I would like to thank @rodrigocarlosqm again, he was the one who helped me recover the brick he had. For all those who are in the same situation please I hope you can solve it before any query is at your disposal. Thank you all.
Related
Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.
Ferguson35000 said:
Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.
Click to expand...
Click to collapse
I'm stil stuck.
Is there anybody able to help me ?
Thank you.
Ferguson35000 said:
I'm stil stuck.
Is there anybody able to help me ?
Thank you.
Click to expand...
Click to collapse
I got this problem when installing CWM too. I believed the problem is in this line:
fastboot flash recovery CWM-6.0.5.0-peregrine.img
Click to expand...
Click to collapse
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
UncolourTV said:
I got this problem when installing CWM too. I believed the problem is in this line:
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
Click to expand...
Click to collapse
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.
Ferguson35000 said:
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.
Click to expand...
Click to collapse
I have the same issue with this program under linux or windows, it doesn't recognize my device. I have activated USB debug, tried under bootloader or with the phone normally started but nothing better.
only fastboot boot recovery.img works.
You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues
hacktrix2006 said:
You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues
Click to expand...
Click to collapse
Thank you for answering.
I will try this then come back.
Ferguson35000 said:
Thank you for answering.
I will try this then come back.
Click to expand...
Click to collapse
Same error :
I still have the mismatch thing with mfastboot ...
Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.
hacktrix2006 said:
Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.
Click to expand...
Click to collapse
Hello, I have bought the phone less than one month ago.
It was directly on 4.4.4 after unpacking.
Have you tried renaming the CWM file? Maybe the "-" are a problem although I highly doubt it. Did you try re downloading the file? Running the command window as an administrator? Last resort, you could use TWRP, I'm running on this currently and haven't had any problems installing/flashing ROMs with it and imo prefer it over CWM.
Click to expand...
Click to collapse
I have tried both and they both have the same problem :/ CWM as well as TWRP...
Still no idea what happens.
same problem
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on
kosamuky said:
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on
Click to expand...
Click to collapse
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you
Back to stock
Ferguson35000 said:
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you
Click to expand...
Click to collapse
Yes its normal if you have unlocked your bootloader
To get back to stock, download a stock Fw for your device model and region, you can find a link for one if you enter the moto g section of this site and head to moto 4g lte android development section (only section specifically for peregrine model) unpack the fw files into your fastboot directory (windows) reboot your phone to fastboot mode (where u saw the status code) then press control + shift + right click to launch a command prompt window here (from within fastboot directory in windows) then copy and paste these fastboot commands 1 by 1 pressing enter each time until compete.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
So you mean, it is compulsory to have stock ROM in order to install the recovery ?
Because my problem is not to return to stock, it is to install a proper recovery (CWM or TWRP) in order to boot on it without my computer.
Thanks for your help
No but I think your problem is you have corrupt the recovery partition size maybe through bad flash or something so ur unable now to flash a recovery as the partition size is for different device or damaged and flashing cwm will no longer work as the cwm image is too big or too small for the allocation assigned to it as the devices core partition table has changed (can happen when u flash something for the falcon when you have a peregrine), I would flash back to stock via that method to restore to stock partition sizes and then reroot and flash cwm again after, just a guess from my own understanding.
Sent from my XT1039 using XDA Free mobile app
Guys I had the same trouble installing the recovery with the mismatched partition size message. This message is normal and the recovery is already installed on your device. The problem i had when selecting the recovery with the following black screen was that I used the Power Button instead of the up Button.
5) using volume down scroll to recovery and then use volume up to select
I was using cm13 sprout 4 and twrp recovery. Was getting error unfortunately ---- apps stopped again again from different apps.
So simply thought of wiping cache and dalvik from twrp . It gave error e: can't mount /cache. So thought of formattig data but by mistake instead of factory reset, i formatted my android. Now i have no os installed just a twrp and unlocked bootloader with me.
now it gives error also E: can't mount/ system also.
pls help, i have only this night to fix it , tight schedule ahead
Try to flash 4.4.4 (posted here) with SPTools. Then install TWRP and update to 6.0.1.
thanks for reply bro!!
but is their any alternate to sp flash tools.
As my sp flash tool does not detect my device. I have tried it many times on different pcs.
MihaiSG said:
Try to flash 4.4.4 (posted here) with SPTools. Then install TWRP and update to 6.0.1.
Click to expand...
Click to collapse
thanks for reply bro!!
but is their any alternate to sp flash tools.
As my sp flash tool does not detect my device. I have tried it many times on different pcs.
i have tried before on this thread also.
http://forum.xda-developers.com/sparkle-v/general/stock-firmware-t2889509/page5
#41
today i tried these commands in fastboot :
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
all commands finished successfully but strangely their no change in my device.
then i tried flashing cwm recovery
fastboot flash recovery cwm.img
but when i boot in recovery it was twrp only.
so i think the flash command from fastboot is not working.
pls help...
Now i managed to get my friends pc and flashed stock rom using sp flash tool , everything went smoothly without any error but strangely nothing happened in device. It remains same without any os . Is my device completely damaged?? :'(
i am attaching logs
please someone reply....
ghanta said:
i am attaching logs
please someone reply....
Click to expand...
Click to collapse
I used sp flash tool format+download option and flashed stock rom. Now its not even booting or charging anymore. Went to service center they simply said its dead buy a new one...
It is being detected by sp flash tools even now also.
Is their anyone who can help me out here???
i don't want to loose my device
please,anyone help
ghanta said:
I used sp flash tool format+download option and flashed stock rom. Now its not even booting or charging anymore. Went to service center they simply said its dead buy a new one...
It is being detected by sp flash tools even now also.
Is their anyone who can help me out here???
i don't want to loose my device
please,anyone help
Click to expand...
Click to collapse
Hi.. i am also facing the same problem. Did you solve it?? Or what did you do?
I have to buy a new phone.
It is still lying in one corner waiting for any solution if you can find
Karbonn Sparkle V
I have the same issue of mounting system as well as cache and data partition shows error and does not mount.
I did use below commands which completed successfully but does affect my device:
fastboot oem unlock (Press Vol+)
fastboot flash preloader preloader_sprout.bin
fastboot flash protect1 protect_f.img
fastboot flash protect2 protect_s.img
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash secro secro.img
fastboot flash para para.img
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot oem lock (Press Vol+)
fastboot reboot
Rajesh Jakhal
Got a solution!
This is kind of late but I hope this helps other people who have the same issue and are viewing this thread!
Take the battery out of your phone and connect it to your computer. Use SP flash tools and flash the stock rom, using the option, "Format All + Download"
You may have to press a button or button combination to get SPFT to recognize your phone. My phone's volume rockers don't work so I cant help you with that, it was pure luck for me!
Once you let it flash, let the phone boot. It will take some time, longer than usual but it WILL boot. And the bootloader will be locked, so be prepared to start tinkering from scratch!
Hello everyone
I'm in a huge trouble, I flashed recovery partition using twrp on oreo firmware by mistake and now I can't enter to bootloader mode to reflash recovery using the extracted recovery.img from UPDATE.APP.
I already tried:
dload folder with UPDATE.APP and pressing volume down, volume up and power button
Press & hold power button and plug the USB cable
Neither of them work, and my phone is stucked in ERROR MODE saying:
Attention!
Plase update system again
Error!
Func NO: 11 (recovery image)
Error No: 2 (load failed!)
Please help, I do not what to do or at least enter to bootloader to reflash the custom recovery.
Hi, I have the same problem. Were you able to fix it?
plug in usb, hold power and vol down until you get to fastboot.
If you are on OREO now, make sure to extract recovery_ramdisk and recovery_kernel, and flash both in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
fastboot flash recovery_kernel RECOVERY_KERNEL.img
If you can't find RECOVERY_RAMDISK you're using a nougat update.app.
ante0 said:
plug in usb, hold power and vol down until you get to fastboot.
If you are on OREO now, make sure to extract recovery_ramdisk and recovery_kernel, and flash both in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
fastboot flash recovery_kernel RECOVERY_KERNEL.img
If you can't find RECOVERY_RAMDISK you're using a nougat update.app.
Click to expand...
Click to collapse
Hi,
I would like to know where to find RECOVERY_KERNEL.img, as there's no UPDATE.APP contains it.
I have the very same problem, but I managed to enter the fastboot though.
Another question, how to flash the erecovery partitions, it seems it has been blocked from access.
thanks.:good:
liuyujack said:
Hi,
I would like to know where to find RECOVERY_KERNEL.img, as there's no UPDATE.APP contains it.
I have the very same problem, but I managed to enter the fastboot though.
Another question, how to flash the erecovery partitions, it seems it has been blocked from access.
thanks.:good:
Click to expand...
Click to collapse
Woops. There's no recovery_kernel. There's ERECOVERY_KERNEL.
Recovery most likely uses regular KERNEL.
You can flash erecovery partitions in twrp, using dd.
ante0 said:
Woops. There's no recovery_kernel. There's ERECOVERY_KERNEL.
Recovery most likely uses regular KERNEL.
You can flash erecovery partitions in twrp, using dd.
Click to expand...
Click to collapse
Thanks for the explanation. however, to leave the error mode, I flashed recovery_ramdisk, ramdisk, kernel, and system, but it still stuck there the moment I leave the fastboot with the same error code.
Do you know why this is or have any solution?
Thanks.
liuyujack said:
Thanks for the explanation. however, to leave the error mode, I flashed recovery_ramdisk, ramdisk, kernel, and system, but it still stuck there the moment I leave the fastboot with the same error code.
Do you know why this is or have any solution?
Thanks.
Click to expand...
Click to collapse
Same error code as: Error!
Func NO: 11 (recovery image)
Error No: 2 (load failed!)
?
ante0 said:
Same error code as: Error!
Func NO: 11 (recovery image)
Error No: 2 (load failed!)
?
Click to expand...
Click to collapse
yes, exactly
ante0 said:
Same error code as: Error!
Func NO: 11 (recovery image)
Error No: 2 (load failed!)
?
Click to expand...
Click to collapse
liuyujack said:
yes, exactly
Click to expand...
Click to collapse
additional information:
fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.007s]
finished. total time: 0.007s
as: Error!
Func NO: 14 (no image found)
Error No: 2 (load failed!)
similar one here. Is there any solution?
liuyujack said:
yes, exactly
Click to expand...
Click to collapse
Hi !
Did you find a solution ?
I have the same errors, Desperately looking for a solution.... Did anyone get it figured out?
Thanks
I finally figured it out. Hopefully this will help somebody else. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
seti007 said:
I finally figured it out. Hopefully this will help somebody else. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
Click to expand...
Click to collapse
Could you do a guide for that?
Has anyone found a solution.? Im about ready to jump the gun on dc phoenix. But if someone found an alternative, it would really help.
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Click to expand...
Click to collapse
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
SubwayChamp said:
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
Click to expand...
Click to collapse
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
bob_bricoleur said:
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
Click to expand...
Click to collapse
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
SubwayChamp said:
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
Click to expand...
Click to collapse
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
bob_bricoleur said:
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
Click to expand...
Click to collapse
Some times causes different results flashing the fastboot full image through EDL mode (download mode) instead of through fastboot mode.
It could be the issue the TWRP version if there is other available.
And you could try deleting the recovery partition with fastboot erase recovery, then boot (don´t flash yet) to recovery using fastboot boot whateveriscalled.img, then in TWRP flash the TWRP image or the installer zip, then reboot for first time to TWRP and try again.
Merry Christmas guys,
I have a really unusual situation.
First time that I have tried all tricks I know and I can't get myself out of this difficult situation.
I was trying to update Magisk with a patched boot file and after a reboot I was not being able anymore to access the system but only this black screen with the Crashdump Mode is appearing.
I can access the Fastboot screen, but no way to reboot to the TWRP recovery or to flash another boot.img, even through some pc flashing utilities.
Is there anything to try through another slot or something else?
I also tried:
fastboot flash boot_a boot.img
and I get this error:
FAILED (remote: Flashing is not allowed for Critical Partitions)
But my bootloader is unlocked and other commands like fastboot reboot works normally.
After I flashed through fastboot the images of boot, abl, dtbo, fw I can only access the TWRP recovery where everything is decrypted.
Any other ideas?
Try booting temporary into TWRP by using this command
fastboot boot twrp.img
If you can't use MSMDownloadTool