Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, 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, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
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.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, 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, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
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.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
Click to expand...
Click to collapse
I think that i figured out something, I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Did you try reflash twrp latest version?
Related
So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?
SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.
hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good:
I need some help with flashing a GSI Image on BV9500 pro. I managed to flash it one time, and then due a nandroid restore, I had to flash the stock rom.
Now, whenever I try to reflash the LineageOs 17 GSI image or the AOSP, the phone is always stuck at the Blackview logo. I tried everything, wiping the partitons before flashing, using the decrypt, OEM and bootloader unlocked. Nothing works.
Fixing the contents doesn't do anything either.
I have TWRP installed and can access it without any problems.
Any ideas or suggestions?
denis9rafael said:
I need some help with flashing a GSI Image on BV9500 pro. I managed to flash it one time, and then due a nandroid restore, I had to flash the stock rom.
Now, whenever I try to reflash the LineageOs 17 GSI image or the AOSP, the phone is always stuck at the Blackview logo. I tried everything, wiping the partitons before flashing, using the decrypt, OEM and bootloader unlocked. Nothing works.
Fixing the contents doesn't do anything either.
I have TWRP installed and can access it without any problems.
Any ideas or suggestions?
Click to expand...
Click to collapse
I'm using the same phone and most of the gsi roms doesn't boot up.. I only had success with resurrection remix and havoc os but they were too buggy. I think we can't set selinux to permissive that's the huge problem with this phone...
Sorry for my bad English grammar,
I have stucked in TWRP for all this day, flashed many different roms and got the same message :
"E1001: Failed to update system/vendor image.
Updater process ended with ERROR:7
Error installing zip file '...' "
My base is 11.0.4 xiaomi.eu rom (MIUI 11, Android 10), start flashing 11.0.3 custom rom (MIUI 11, Android 9) and got that ERROR, then flashed Havoc/ASOiP rom, end up with flashing STOCK MIMAX3Global_V11.0.2.0.QEDMIXM on Mi offficial site via TWRP but still no luck, samething.
I have already tried lastest TWRP 3.3.1, 3.2.3, PitchBlack Recovery, and modified Updater-Script aswell (Delete 1st line).
Thank you for your help ! :crying:
Have you tried any of these tips?
Did you tried any android 10 ROMs?
I'm not sure if the downgrade from 10 to 9 is possible at all
I had wiped my system partition at one point and got this as well. Fixed by using the mi flash tool and the full system image (not a twrp / orange fox rom) and then wiped my data partition to get rid of the boot password. I don't know if anti rollback effects 10 to 9. Look into it though. You're looking for a fastboot rom. Just make sure to not "clean and lock". I'm having trouble finding the fastboot rom I found to fix it but it should come in a .tgz file. Good luck
I decided to install Pixel Experience for my Mi 9 SE today with TWRP but I kept getting the message "android.process.media" has stopped so I decided to wipe dalvik, cache and system. After that, I reflashed the firmware and rebooted then my phone got bricked into a fastboot loop.
Then for hours I had tried hundreds of ways, including using XiaomiFlash that said flash vendor error (with the Global ROM) and using XiaomiTool v2 that somehow got the TWRP on (but unable to mount /system_root so I cannot flash anything else).
Then I followed this video and changed the datatype of /system but now I got the error:
"E3004: This package is for "grus" devices; this is a "".
Updater process ended with ERROR: 7....." So Error installing the ROM.
Can anyone please tell me what to do because I think I am about to go crazy
You had to FORMAT (not wipe) DATA (not system)
xanxusokumura said:
I decided to install Pixel Experience for my Mi 9 SE today with TWRP but I kept getting the message "android.process.media" has stopped so I decided to wipe dalvik, cache and system. After that, I reflashed the firmware and rebooted then my phone got bricked into a fastboot loop.
Then for hours I had tried hundreds of ways, including using XiaomiFlash that said flash vendor error (with the Global ROM) and using XiaomiTool v2 that somehow got the TWRP on (but unable to mount /system_root so I cannot flash anything else).
Then I followed this video and changed the datatype of /system but now I got the error:
"E3004: This package is for "grus" devices; this is a "".
Updater process ended with ERROR: 7....." So Error installing the ROM.
Can anyone please tell me what to do because I think I am about to go crazy
Click to expand...
Click to collapse
Hi, this is probably coming a little too late, but when something like this happens, you should reflash the stock ROM provided by Xiaomi:
https://c.mi.com/oc/miuidownload/detail?guide=2
Using either their MiFlash tool or doing it yourself from terminal via the flash_all script. Usually, the phone should be working again afterwards.
lachesis197 said:
Hi, this is probably coming a little too late, but when something like this happens, you should reflash the stock ROM provided by Xiaomi:
https://c.mi.com/oc/miuidownload/detail?guide=2
Using either their MiFlash tool or doing it yourself from terminal via the flash_all script. Usually, the phone should be working again afterwards.
Click to expand...
Click to collapse
Hi, im stuck in the same spot, my mi9se wont let me install any custom rom, i get error 7, 1 and everything but i cannot get out of the stock rom, can you please share the steps that you use (if you know) to sucessfully flash a custom rom on this cellphone?
Do not WIPE system and vendor. Just use the standard button in the first page of WIPE in the TWRP. I had the same problem with that and I got the solution only by flashing the Fastboot ROM (here: https://c.mi.com/in/miuidownload/detail?guide=2) with Mi Flash tool. Search more information about the instructions.
I saw something about flashing the vbmeta.img to solve the problem with the fastboot loop and without the fastboot rom, but I didn't check.
sebashebe said:
Hi, im stuck in the same spot, my mi9se wont let me install any custom rom, i get error 7, 1 and everything but i cannot get out of the stock rom, can you please share the steps that you use (if you know) to sucessfully flash a custom rom on this cellphone?
Click to expand...
Click to collapse
I got this error too and I solved with this TWRP version: https://forum.xda-developers.com/t/grus-recovery-twrp-3-4-0-2-mi9se.3949328/
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
shim80 said:
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
Click to expand...
Click to collapse
Try to flash V12.5.3.0.QFLCNXM with Twrp/O.f (TWRP is newer than this OF.)
then
reboot Twrp/O.F
Wipe/format data type yes
reboot Twrp/O.F
Flash rom
Sometimes the flashing of the recovery ROM does not work with the Twrp/O.F in this case use Miflash with a fastboot rom.
If you're still trying to figure this one out, I think I know how to solve your issue installing LOS.
You most likely used TWRP v3.70, am I right?
You should use TWRP v3.61 coz that was the last stable version that worked, the only thing is that you might need to find another custom recovery other than the official TWRP after installing an Android 12 custom ROM like LOS 19.1.
Lineage OS has their own recovery so you'd probably need to use that if you want to update it.
Same issue with me. yesterday. Though mine is fixed.
My workaround was: I installed the official 12.5.3 MIUI using OrangeFox. After boot, I tried installing PixelExperience using Pixel recovery. There I got successfully installed a custom ROM. Alhough I am not sure if the mounting/encryption of Internal SD is the cause.