Develop Bugs

ERROR 7 when installing a zip

Hello, guys. I just ran into an error I had never seen before while flashing a new firmware on my T320. After searching around, I found more people have reported it as well on many devices and I've tried most solutions, to no avail.
When installing a zip for a lineage 16 rom, I got an error 7 message, which implies a mismatch between the rom and the device being flashed. I'm sure they should be a match, so I proceeded with the most common solution (when you know it's a match), which is to remove the device-checking code from within the zip. That didn't work, I got a "invalid zip file format" error.
I haven't tried many different roms after this in order to exclude the possibility this being actually a incompatibility issue but I'm worried because, when first flashing, I wiped the device quite carelessly. I'm afraid I might have "over-wiped" something important. I have TWRP installed, version 3.1.1.0, and did the wiping using it's built in tools.
Is there something I should never wipe, risking breaking it beyond repair? Is there a special procedure to perform or option to choose when zipping the rom back after removing the device-checking code?
Thanks for any advice,
Horácio.

horaciosalles said:
Hello, guys. I just ran into an error I had never seen before while flashing a new firmware on my T320. After searching around, I found more people have reported it as well on many devices and I've tried most solutions, to no avail.
When installing a zip for a lineage 16 rom, I got an error 7 message, which implies a mismatch between the rom and the device being flashed. I'm sure they should be a match, so I proceeded with the most common solution (when you know it's a match), which is to remove the device-checking code from within the zip. That didn't work, I got a "invalid zip file format" error.
I haven't tried many different roms after this in order to exclude the possibility this being actually a incompatibility issue but I'm worried because, when first flashing, I wiped the device quite carelessly. I'm afraid I might have "over-wiped" something important. I have TWRP installed, version 3.1.1.0, and did the wiping using it's built in tools.
Is there something I should never wipe, risking breaking it beyond repair? Is there a special procedure to perform or option to choose when zipping the rom back after removing the device-checking code?
Thanks for any advice,
Horácio.
Click to expand...
Click to collapse
A Slimroms file just made it through, so it's not destroyed, it's a matter of compatibility, somehow.

update the TWRP to 3.3.1.0

I have the same problem with T320 and was using TWRP 3.3.1.0, lineage-16.0-20191211-UNOFFICIAL-mondrianwifi.zip . I was able to install RR-N-v5.8.10-20190128-mondrianwifi-Unofficial.zip.
Any idea why?
Thanks

thro14 said:
I have the same problem with T320 and was using TWRP 3.3.1.0, lineage-16.0-20191211-UNOFFICIAL-mondrianwifi.zip . I was able to install RR-N-v5.8.10-20190128-mondrianwifi-Unofficial.zip.
Any idea why?
Thanks[/Q]
I got it working now. I downloaded 16.0 again. In TWRP- Factory reset, Advance wipe-chose Dalvick, Data, System & Cache.
This time I did not "Format Data". Not sure which did it (download or not format data).. Hope it helps.
Click to expand...
Click to collapse

having this same problem says "this package is for mandrainwifi , this device is . "

Trevorlay said:
having this same problem says "this package is for mandrainwifi , this device is . "
Click to expand...
Click to collapse
Make sure you have the latest twrp. If it still doesn't work, you could try messing with wiping/not wiping.

Updater process ended with ERROR 7- How can I fix this error?

Dear XDA-Developers,
After trying for many hours searching different forums and websites looking for help, I decided to make an account here and ask for help here.
I am currently on a Rooted OnePlus 5t with OxygenOs 9.0.3. I have not updated my phone in a really long time and decided to do so now.
I decided to dirty flash the full official ROM for OxygenOs 9.0.11 which was released recently with TWRP.
At first, I was on an older version of Blu_sparks recovery but replaced it with the newest TWRP from their website (Dumpling 3.3.1-0).
When I first tried to flash it, I got this error message:
failed: no space left on device
E1001: failed to update system image.
Updater process ended with ERROR 7:
Error installing zip file 'sdcard/download/Oneplus5Toxygen_43_OTA_054...
After trying multiple other recoveries, trying to flash with and without the compatibility zip and also trying to flash earlier versions of OxygenOS with different TWRP versions, I still get the same error message from TWRP as above.
Since it says that I supposedly don’t have enough free space, I looked for a way to change that and came across a thread which suggested to free some space by removing system apps that are not unnecessary, I tried doing that and flashing it again, but that also wasn’t successful.
My phone also has more than 10gb of free space.
I also tried to change the „assert“ line in the updater-script of the update, but I did not find any such line in the updater-script document in the zip file?
Does anyone know what causes this error message and what I can do to successfully update my phone?
And I was also wondering what would happen if I just let my phone regularly update it over settings?
It says that root is detected and my phone would be un-rooted once the after updating.
However, the update shown is only 1839mb so I’m very hesitant to do it.
But if I went through with this, would I just have to reroot my phone?
Will my recovery be replaced with the stock recovery, or will it remain TWRP?
Will my Bootloader get locked again?
Thank you so much for taking the time to read this, I appreciate it.
With kind regards,
Mutambo23

General December update woes...

The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 4 (and A9 for a/b slots), hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. I always thought corruption must have been there before, but now I'm not so sure.
update: flashed the last build from November using flash.android.com and was able to get my system back. 2nd flash for that build worked.

Alekos said:
The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 9, hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. Corruption must have been there before, but now I'm not so sure.
If anyone has any fastboot tricks - I'd try anything at this point.
Click to expand...
Click to collapse
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back

mac796 said:
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back
Click to expand...
Click to collapse
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message.
I tried flashing 4 different Factory Image builds (flashing manually the Factory Image not ota). The android flash tool (webiste) completes but same message appears after it restarts.

Alekos said:
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
I tried flashing 4 different Factory Image builds. The android flash tool completes but same message appears after it restarts.
Click to expand...
Click to collapse
You're trying to flash with fastboot right? Use that Android flash tool. You'll see a link to it in the factory image page. I went through the same thing you did, I got the corrupt device. at the very end It'll ask you to Lock the bootloader just don't do it if you want to stay unlocked.

Oh maybe I misunderstood you tried that and it's not recognizing it

mac796 said:
Oh maybe I misunderstood you tried that and it's not recognizing it
Click to expand...
Click to collapse
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.

Alekos said:
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.
Click to expand...
Click to collapse
That's no good. Hope it works out. I had a hell of a time getting mine back too

mac796 said:
That's no good. Hope it works out. I had a hell of a time getting mine back too
Click to expand...
Click to collapse
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
a few reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.

Alekos said:
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
Lots of reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.
Click to expand...
Click to collapse
I'm glad you got out of it

I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section

victoraran said:
I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section
Click to expand...
Click to collapse
so if I didn't have "OEM unlocking" enabled - I'd have a brick right now. just actually trying to help someone else that also got the corruption message and can't get back into Android to enable oem unlock. Recovery doesn't work (like my situation).
What a mess...

That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.

Battery life is awesome, still on 44% at half 10 at night from half 6 this morning

prohibido_por_la_ley said:
That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.
Click to expand...
Click to collapse
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.

Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Well in the 4 years of me being on Android I've never had it happen.

I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.

JodyBreeze901 said:
I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.
Click to expand...
Click to collapse
same

Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Why not just adb sideload the OTA image, rather then flashing on both slots the factory image? It just sounds a bit of a hassle to me.
I know, I used to fastboot flash without -w my nexuses as well, but that was before the OTA images were available.

prohibido_por_la_ley said:
Well in the 4 years of me being on Android I've never had it happen.
Click to expand...
Click to collapse
yeah it's super rare. been flashing images and ota's since Nexus 4. But it happens.
I usually get the updates right away but sometimes I'll update the ota. I usually reflash the factory image every year after the beta. just seems odd how it corrupted the device. couldn't get into the system at all (or recovery/rescue modes).

yolandabecool said:
same
Click to expand...
Click to collapse
apparantly it has something to do with Bluetooth? I don't know how, but if you can get into safe mode and disable Bluetooth, clear cache/data for it and update all your google service apps, it can fix it (keeping Bluetooth off while restarting phone in regular mode) - but I couldn't load Android.
The trick to getting into Safe Mode is this: Turn off the device. Hold down power and and as soon as you see the "G" Logo, hold volume down. it will directly boot you to Safe mode. cool little trick. you'll have to manually enable wifi because it gets turned off.
At this point, if you can, enable OEM Unlocking. at least you'll be able to save the device if anything serious happens (like what I went through). the pixel repair website also works but I couldn't get into "Rescue Mode"

Question Bricked for Days and usable WiFi is $$$ for vanlife, help!

I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.

When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.

bigdog1459 said:
When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.
Click to expand...
Click to collapse
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.

nastyneighbor said:
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.
Click to expand...
Click to collapse
Damn. I'm sure you have tried some of the manual flashing guides out there too?

nastyneighbor said:
I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.
Click to expand...
Click to collapse
Not sure when you said you used "Stock Recovery Flash Tool" if you meant the "Android Flash Tool". But just in case you didn't, that can force flash partitions with it. Probably your best shot.
Android Flash Tool
flash.android.com

Android Flashing Tool online unbricked me the other day. You have to be patient with the tool as it took me several tries. It will totally wipe your phone, but at this point you just need to rescue your device. Keep us posted.

thanks for the tip. i'm trying the android flash tool again now. and will keep trying it until it at least passes the download stage. and yes i tried all the manual flashing guides out there...and hybrid combos of all as well. i mean i'm positive its my fault for missing SOMEthing somewhere but many hours have been spent with overall negative progress.
my track record is still zero hard bricked devices or soft ones I couldn't fix over all these years so i'm not too worried but i could use my phone back haha
will keep posted as requested. ty again.

I know this doesn't help your immediate situation, but when flashing anything like custom kernels, I would advise not to use some random app to flash it with, just follow the directions in the OP of the kernel's thread, and make sure you have up to date Platform Tools and driver. CleanSlate and many or all the custom kernels also require flashing more than just the boot.img.
Good luck, I hope you get it back working for you.

Hey guys, the Android Flashing Tool finally worked for me and I am up and running again. Thanks for your help and tips. Hacking phones is more important every year and thus I truly value your skills and advice. This community must survive the new world order. much love folks

Question "Couldn't install system update" for each monthly security update

Hi,
As soon as I've received my Pixel in October I unlocked its bootloader and rooted it. Ever since, each time there is a system update available, I get an error saying "Installation problem" if I try to install it manually in the settings and an notification saying "Couldn't install system update, tap for more infos" when the device try to install it over night. So every time I have to update my pixel using a computer, but it never ends well and I end up losing my data (I have backups but it's still infuriating). What is going on ? I can't find anything online to help me.
Since that time, there was also a message saying "Your device is corrupted and cannot be trusted" when I was turning my phone on (right before the Android logo), but I've managed to remove it using the "disable vbmeta verification" option during the last update. Are those linked ?
I don't know if it helps, but I've attached screenshots of my magisk modules and the error message with this post.
Thank you by advance !

That's because your boot partition has been modified and signature does not match. It therefore refuses to update in order to protect you from mismatches.
You need to perform the updates manually, which means downloading the factory image and modifying the installer script (flash-all.sh) to remove the wipe (-w parameter to 'fastboot update'). You will also extract the new boot image and reapply magisk to it if you intend to retain root privileges.

Papipoulpe said:
Hi,
As soon as I've received my Pixel in October I unlocked its bootloader and rooted it. Ever since, each time there is a system update available, I get an error saying "Installation problem" if I try to install it manually in the settings and an notification saying "Couldn't install system update, tap for more infos" when the device try to install it over night. So every time I have to update my pixel using a computer, but it never ends well and I end up losing my data (I have backups but it's still infuriating). What is going on ? I can't find anything online to help me.
Since that time, there was also a message saying "Your device is corrupted and cannot be trusted" when I was turning my phone on (right before the Android logo), but I've managed to remove it using the "disable vbmeta verification" option during the last update. Are those linked ?
I don't know if it helps, but I've attached screenshots of my magisk modules and the error message with this post.
Thank you by advance !
Click to expand...
Click to collapse
As stated earlier, since you are rooted your boot partition is modified and thus you are failing due to not passing the pre-OTA block verifications.
You can:
1. Try the "Install to Inactive Slot" method in Magisk. Note that this has been hit or miss for users.
2. Update via Pixel Flasher. You can keep root this way.
3. Flash the stock boot image to unroot, update via OTA and then re-root.
4 Update via Android Flash Tool. You will have to re-root afterwards.
5. Flash the Factory Image and then re-root. There is a way to keep root via this method by modifying your flash-all.bat file. Search the forums for the guides.
6. Sideload the OTA and then re-root.

Thanks you two for your answers. So does everyone with a rooted pixel do this every month or have I f*cked up something during previous installs that invalidates my os ?

Papipoulpe said:
Thanks you two for your answers. So does everyone with a rooted pixel do this every month or have I f*cked up something during previous installs that invalidates my os ?
Click to expand...
Click to collapse
Every month is a bit overkill, but essentially yes.

Papipoulpe said:
Thanks you two for your answers. So does everyone with a rooted pixel do this every month or have I f*cked up something during previous installs that invalidates my os ?
Click to expand...
Click to collapse
Yes everyone who is rooted must manually update

I just use flashtool and never have problems
I would start fresh with flashtool. Check only* the boxes 'wipe device' and 'force flash partitions'
When you want to update, use flashtool with none of the boxes checked. Get the boot.img file from the factory image, patch it, boot it then direct install. Never fails for me.

fil3s said:
I just use flashtool and never have problems
I would start fresh with flashtool. Check only* the boxes 'wipe device' and 'force flash partitions'
When you want to update, use flashtool with none of the boxes checked. Get the boot.img file from the factory image, patch it, boot it then direct install. Never fails for me.
Click to expand...
Click to collapse
Simpel as that . i do it also that way