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
Related
I have been trying to get my S3 to take the update from LG8 to Ll3, and it fails no matter what I try. I am running totally stock LG8 that I rooted using the toolkit posted in the development section. I don't have any APKs that I altered, but every time I try to flash the update, I get a "status 7" error. I tried it on both internal and external SD using CWM recovery. I tried flashing stock recovery via Odin and then let the phone download it over the air and attempt to install itself, and I even tried running the update in TWRP. Every time I get the same status 7 error.
I am coming from HTC phones and have never had these kinds of issues, so I'm pulling out my hair. Can anyone offer any suggestions? I know it must be something stupid I'm overlooking, but I've searched everywhere and can't seem to find the answer.
Sounds like a bad DL. Just grab it from here. http://forum.xda-developers.com/showthread.php?t=1743923
Or here http://forum.xda-developers.com/showthread.php?t=1904099
Or odin flash LI3- http://forum.xda-developers.com/showthread.php?t=1919919
A lot less stressful
The procedure that myn posted over here is pretty staight forward and foolproof too.
Have you solved your issue yet?
I am getting the status 7 error as well even with Myn's procedure. Others are having the problem. Only thing I can think of is the current image file has changed enough to not allow the update to go through. However, I have not removed or modified any stock apks and backed my whole system up with TB right after rooting so no reason for mine to not work. Binary file should be good since it is working for other S3 users.
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
cfonte100 said:
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
Click to expand...
Click to collapse
I was able to get mine to work using Myn's method. Seems flashing newest CWM recovery did the trick. Was trying to flash via TWRP and didn't think it would matter but apparently it does. Just followed his post and all upgraded without issue.
Back to your issue.....what state is your phone at currently? What recovery is installed and what version are you running? Surely we can get this resolved for you.
what does the log say when it fails? I mean in addition to status 7. If you don't see anything go under advance>show log. it's probably a failure in the checks it does before the flash. Have u modified your build.prop? is your baseband and build both lg8? That log will tell you what's wrong.or as I mentioned above you could follow 1 of my links and avoid tha headache
I have a Yakju Maguro which is currently running JOP40D. I recently installed the ClockWorkMod v6.0.2.3 recovery, and rooted my phone. Now I received the notification for the 4.2.2 OTA update, but as expected CWM gives me an error when attempting to install it. It says "Install Untrusted Package?" and gives me Yes or No as options. Until now, I've always been weary to try the Yes option, so I've always gone for No, and the update obviously didn't install.
So my question is, will it actually work if I select Yes? And if it doesn't, in what condition will my phone be after it fails? Will it boot into the old OS, or will I have to manually re-flash a ROM?
I've tried googling the problem but no one seems to be facing the same exact condition as me. Eveyone reports that the installation simply fails with CWM, and I've never seen any mention of a Yes/No prompt. Also, I haven't found any thread that mentions in what condition the phone will be after the failure, so I'm trying to figure out what's going on.
In addition, I've manually downloaded the "07501b11ad3b.signed-yakju-JDQ39-from-JOP40D.07501b11" zip file from the Google website. Will I be able to flash that instead from CWM, make things simpler?
Thanks for any help.
Disclaimer: I am no developer just someone who has done a ton of research in the last day
This may be a long post due to my extensive troubleshooting issues, so here's some background.
OP5T is the first android I've owned and I have had it for about a year. I rooted it right after I received it and haven't updated it since. With the release of Oreo, I entertained the idea of updating my firmware, which I knew meant that I'd need to factory reset my device. Yesterday was the day I decided to do it and man I regret it. Long story short, I fully uninstalled Magisk through the app, attempted to fully remove the root by means of 'full unroot' in the SuperSU app, which failed. I then was stupid enough to fully wipe my device using TWRP (I think I checked the box for every partition in 'advanced wipe'). I was then stuck in a boot loop. Eventually, I managed to use fastboot to boot recovery to TWRP. I have been stuck in this state ever since.
I am currently using 3.2.1-x | blu_spark v8.61 and previously used Magisk.
The main ROM I have been attempting to flash is OnePlus5TOxygen - 5.1.5
- https://www.oneplus.com/support/softwareupgrade/details?code=7
- https://forum.xda-developers.com/oneplus-5/how-to/oxygen-os-5-1-5-signed-zip-t3832336 (not sure how
these are different but their filenames differ so I have tested both
The errors I have received in my troubleshooting process:
- The most infamous: Error 7
- E1001: Failed to update system image
- no file_contexts
- and a host of others I have weeded out using xda as a resource, such as many partition errors, vendor issues,
etc.
- Failed to read command: No error (terminal result when attempting to flash some ROMS through ADB)
The steps I have taken to remedy these errors:
Let me just say I have consulted tons of xda threads regarding error 7, and none work for me. I have attempted to flash using several of the latest versions of TWRP, finding the most success with blu_spark. I have attempted to sideload the ROMS, push them using ADB, and directly place them in the internal storage and no method works. I always get Error 7, with the exception below.
I have attempted to flash stock ROMS for OOS versions 5.1.4, 5.1.5, custom ROMS recommended by xda threads pertaining to the same issue, and many variations of these. Since there are no assert statements in the update_script found in the stock ROMS, which many people mentioned on the forums, I have attempted to approach error 7 from a different angle.
- Each stock ROM starts with this function, which when deleted gets rid of the 'vendor partition is not existed'
error getprop("ro.display.series") == "OnePlus 5T" || abort("E3004: This package is for
"OnePlus 5T" devices; this is a "" + getprop("ro.display.series") + "".");
is_part_existed("/dev/block/bootdevice/by-name/vendor") || abort("vendor partition is not existed, exit
ota!!");
- Even when deleting that, I found there to be two more errors that would appear every time I attempted to
flash, caused by two block_image_update functions that result in errors E1001 and E1002: These both have to do
with updating the system or vendor image.
I have attempted to delete any combination of these. If I don't delete all three functions, I will get an error pertaining to the function I didn't delete. If I do delete them, the ROM will install up to 47% every time and it will cancel (no error). This has happened for all stock ROMS I have flashed, and I have swapped to the latest stock recovery multiple times with no luck.
Additionally, I reformatted data multiple times, set the system partition to ext4, attempted to fix the file system, attempted to mount system in read only to see if that would fix the system update error, all to no avail. I also delete the cache after each ROM flash attempt as well.
I have spent at least 10 hours trying every troubleshoot option I came across on the forums and nothing has helped, which is why I am making this now. I have attempted to flash the current firmware for OP5T with every flash attempt ending with the string '...done' in the terminal, even though nothing has been changed or installed. Every time I try to reboot, it still tells me that I have no OS installed, and I can tell since my internal storage is currently using only around 100MB of usable memory. I have also locked my bootloader, wiped the device, switched to stock recovery, and attempted to clean flash the latest OS with no luck.
In conclusion, it seems that I have deleted my OS so there is nothing to boot to (I go straight to bootloader), there is an error or something missing in my filesystem that is preventing me from fully installing any ROM, and I have tried everything suggested on these forums for similar issues with very limited success. I have done much more than what I mentioned here, and if anything useful comes to mind I will update this post.
(I am also a Computer Science college student that needs a working phone drastically and have already spent so much time diagnosing this issue rather than study that I am ashamed)
I am on the brink of contacting OnePlus, even though I feel as though they wouldn't be much help, or sending this to a repair shop.
Any suggestions/ideas would be greatly appreciated. I will attempt to be as active as possible on this forum as well.
Read my post in this thread, second post. You are fine, as you can still get into TWRP, you are just using a really old version of TWRP, and further complicating things by trying to flash treble ROMs.
Update to the latest version of Bluesparks TWRP which you can flash from your current TWRP, then reflash the full factory ROM. Note it will replace recovery if it is successful.
^^ +1. As long as you can boot into recovery, you are fine. The trick is installing a ROM that is compatible with your TWRP.
I am using codeworkx TWRP 20180822 and running the last Oreo build of Omnirom. First update your TWRP image, then find your OREO rom and install that. You may need to format data with the new TWRP first.
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.
Ive got a Pixel 6 Pro that was running Proton AOSP 12.4.1. Wanted to flash back to the original Android ROM. I downloaded the correct one from the dev page at google and tried to sideload it, but it always stops at 47% and gives this "Signature Verification Failed, error 21". It says it is failing to verify whole-file signature. After spending a couple hours looking onine, I am coming up empty for resolutions. Anyone have any ideas? It has failed in the same way 10 straight times. I should mention I have redownloaded the file to ensure there is no corruption, and even tried different months of the file.
cregets said:
Ive got a Pixel 6 Pro that was running Proton AOSP 12.4.1. Wanted to flash back to the original Android ROM. I downloaded the correct one from the dev page at google and tried to sideload it, but it always stops at 47% and gives this "Signature Verification Failed, error 21". It says it is failing to verify whole-file signature. After spending a couple hours looking onine, I am coming up empty for resolutions. Anyone have any ideas? It has failed in the same way 10 straight times. I should mention I have redownloaded the file to ensure there is no corruption, and even tried different months of the file.
Click to expand...
Click to collapse
It sounds like you want to go back to stock? If so, one of the best ways is to use Android Flash Tool. Just need to have OEM unlocking enabled in Developer Options.
As an aside, among other things you can:
1. Flash the factory image via fastboot
2. Sideload the full OTA image
Lughnasadh said:
It sounds like you want to go back to stock? If so, one of the best ways is to use Android Flash Tool. Just need to have OEM unlocking enabled in Developer Options.
As an aside, among other things you can:
1. Flash the factory image via fastboot
2. Sideload the full OTA image
Click to expand...
Click to collapse
I've tried the Android Flash tool and for some reason, It will not run. It always says "Network Error
HEAD request failed: Unknown network error". Couldn't figure out why, tried 3 different browsers, and a reset of data on the phone, no help. Does it need to have a SIM card in it to flash from the site?
As for #1, I haven't tried that yet.
#2 is the method I am currently using and getting the "Signature Verification Failed, error 21"
Not sure what else to do. I've seen a few posts that recommend flashing the partition as I might have a bad partition, but that seems unlikely as the phone was functioning 100% correctly before attempting to reflash.
cregets said:
I've tried the Android Flash tool and for some reason, It will not run. It always says "Network Error
HEAD request failed: Unknown network error". Couldn't figure out why, tried 3 different browsers, and a reset of data on the phone, no help. Does it need to have a SIM card in it to flash from the site?
As for #1, I haven't tried that yet.
#2 is the method I am currently using and getting the "Signature Verification Failed, error 21"
Not sure what else to do. I've seen a few posts that recommend flashing the partition as I might have a bad partition, but that seems unlikely as the phone was functioning 100% correctly before attempting to reflash.
Click to expand...
Click to collapse
Try #1
Remember proton is A12 and only one factory image has the correct bootloader if you want to stay on A12. Research a lot!!! Because a mistake in how, what you flash if wrong will break your device. Search on A12 bootloader, A13 / A12 different slots.
+1...be cautious...google's bootloader anti-rollback ain't no joke for Pixel 6 series phones. It's a one way ticket back to google for repair (or local repair shop maybe). I found out the hard way after flashing the wrong patched boot.img. The trigger isn't 'armed' until you've booted into A13 once...THEN if for any reason, like booting the backup/update slot, even unintentionally, will brick your 6...it will turn itself off and not power back again, no matter what u try. So, yeah...tread carefully, thar be dragons!
edit: iirc, there is/was a way to turn off sig verification. I would make that a last resort tho...it's a key to help prevent installing 'tainted' app..
Flashing from Fastboot worked, ty for the help.