Hey guys,
So for a couple of hours I've tried quite a few of guides, but I can't fix my problem.
I'm trying to flash the stock ROM from Oneplus, but I get an error that says the following (just typing everything so I don't miss anything for you guys)
Installing '/sdcard/Oneplus_Bacon_OxygenOS-201601190107.zip'
Checking for MD5 file
Skipping MD5 check: no MD5 file found
This package is for "Oneplus" devices, this is a "bacon"
E:Error executing updater binary in zip '/sdcard/Oneplus_Bacon_OxygenOS-201601190107.zip'
Error flashing zip '/sdcard/Oneplus_Bacon_OxygenOS-201601190107.zip'
Updating partition details..."
I currently have no OS on. When I go to the Reboot button and press any of the buttons there, it firstly comes up saying that I have no OS installed. When clicking OK to that, it comes up with a message that my system is not rooted. I have an option to "Do Not Install" and the "Swipe to Install". The same thing happens no matter what I press (the phone just restarts instantly"
I'm running TWRP v2.7.0.0
Any help is greatly appreciated
Using TWRP to install stock rom's
In most cases TWRP cannot install "Stock" roms, mostly due to an issue with "updater scripts." If you want to use the Stock rom than you'll have to go back to the Stock recovery.
Side note: I wanted to use OxygenOS on mine; however, I wanted to keep it rooted so I found a "TWRP safe" version of OxygenOS online. Be cautious if you attempt that because you'll more than likely lose functionality of your Sim/Radio (will have to flash a baseband in the recovery) if you decide to flash another custom Rom over OxygenOS.
Use oneplus one flashtool or bacon toolkit to flast stock rom. Find in tools sections for flashtools
Related
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Saw the probable solution on another post.
mdecaminop said:
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Click to expand...
Click to collapse
In these forums somewhere I read that the unroot was done using Super su's full unroot option. However it apparently left behind a few files that caused the OTA to fail. So what he did was to uninstall Supersu, reinstall Supersu and update the binary. Then use full unroot function... Maybe it will work for you if you have unrooted using SUpersu...
Unrooting, locking the bootloader, and flashing the stock recovery doesn't allow you to take OTA's.
There is THIS thread, providing OTA files that can be flashed in TWRP or CWM. And are official files from Nvidia.
You have to flash these every time there's an OTA, or just flash a full stock image through fastboot, and never root or flash a recovery.
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
mycologik said:
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
Click to expand...
Click to collapse
Well it seems my second hand tablet has been rooted as well ... I've got the exact same problem that yours ...
Is there a way to go back as out of the box ?
I bought a China set of OPO last month. I thought this phone originally installed Color Os rom and then re-installed to CM11s 44s version when it selling. When I turned on the phone for the first time, I already get the update notification for the 05q version. So, I tried to update it but it failed to update it for many times that I tried. My phone rebooted when I clicked "flash updates" and loading for a while then failed in cyanogen recovery. I also tried with manually update with downloaded zip file and installed it in cyanogen recovery. It still failed with mentioned "system 7..." message. Is there any way to fix this problem if I want to flash cm11s latest update firmware, rather than use other custom roms? ??
It's impossible to know what the seller did to the phone before you got it so it's probably a good idea to flash the stock images and start from scratch. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
If your bootloader is locked you'll need to unlock it, but be aware that doing so wipes all user data. Install TWRP recovery and make a nandroid backup of your current setup just in case. Then flash the stock images using fastboot.
Transmitted via Bacon
Actually, what does "system error 7" means when installation?
Here you go
johnsin5393 said:
Actually, what does "system error 7" means when installation?
Click to expand...
Click to collapse
Here you will find what is System 7 error and how to fix it.
http://forum.xda-developers.com/showthread.php?t=2522762
So I saw that an official version of Xposed was posted for 5.1. I tried flashing the zip like in the instructions but I keep getting
Code:
error executing updater binary in zip xposed-v72-sdk22-arm.zip
and bootloops. This is the replacement tablet I got from Nvidia for the recall and I unlocked the bootloader an have TWRP installed. I tried running the uninstall zip, even though it didnt have xposed installed before, but that didn't work. I'm tempted to just factory reset and try again but I'd like to get it working with my current settings before resorting to that if possible. I also had this issue with romracer's port of xposed. What else could I do to get it to work?
Error with bliss pop and cm 12
I know this is an older thread but I have recently tried to root and install a custom rom and I get the same error. I have the most current version of TWRP flashed and I have looked up others who have installed both CM 12 and bliss pop, to follow their steps. For example formating the casch and system before install, and every time I get the same error. What am I doing wrong? Any help would be greatly appreciated.
some more Information? any errortext?
Sorry I didn't explain that, it's the same error as the first post. "Error executing updater binary in zip" then it will list the path of the zip with the rom I'm trying to install.
Hello XDA Developers
I have been trying to flash a custom rom on my Google Pixel which is running Android Oreo and I have gotten as far as unlocking the bootloader and installing TWRP. How ever when I attempt to flash any zip file it just says error installing zip and I have no idea what's going on. TWRP sometimes even has trouble mounting the proper partitions so it's a bit of a hit and miss. Id really like to install a custom ROM. I thought maybe it was a bad zip file but I have tried several different ROMs and they all throw up the same error.
Update: Okay I have figured out that installing newer versions of TWRP doesn't work with some of the ROMs and it's better to use the older versions but you have to figure out which one that is if they don't tell you. I was able to successfully install a custom ROM.
Dunno if this advice is any good but don't set a pin code or password on the phone leave it unlocked it's easier for TWRP to read the partitions that way.
I've tried to flash a custom rom (Corvus OS,) but it always ends in an error saying
"Updater process ended with signal: 4
Error installing ZIP file (then here's the path)
Updating partition details...
...done"
I'm not sure what to do. The phone is a Redmi Note 7 lavander, Orange Fox is the latest (I just installed it today.)
AuFox0912 said:
I've tried to flash a custom rom (Corvus OS,) but it always ends in an error saying
"Updater process ended with signal: 4
Error installing ZIP file (then here's the path)
Updating partition details...
...done"
I'm not sure what to do. The phone is a Redmi Note 7 lavander, Orange Fox is the latest (I just installed it today.)
Click to expand...
Click to collapse
Different ROM and different custom recovery but same issue:
Update Error signal 4 while installing LineageOS ROM
Here is the guide to help you Update Error signal 4 while installing lineageos rom. Follow the guide carefully to get rid of Error 4.
officiallineageos.com
A little update. Have tried other roms (Evolution X and Havoc,) and both have been successful. Is probably something about the rom (or maybe something I did wrong, or something wrong with my phone.)