Hey guys,
Running a rooted oneplus x with latest cyanogenmod (CM) nightly installed. I tried updating the latest nightly and got the following error:
updater process ended with ERROR: 7
Error installing zip file '/external_sd/cm-13.0-20161101-NIGHTLY-onyx.zip'
- I had CM recovery installed, and was getting the same error.
- I tried to update the CM recovery but I get the same error.
- I managed to install TWRP 3.0.2.0 recovery, and still no luck. Same error.
- Tried installing the latest Oxygen OS (downloaded from their site) and still same error.
- As per other forums, I've tried editing the updeater-script and still no luck. I deleted the first line, then saved and zipped. When I try to flash with that it says "can not find updater-script" even though I put the file type back to the way it was, and in the same spot.
any thoughts?
thanks!
You can try to change ONE to ONEPLUS in updater-script, do not delete the lines just change one to oneplus & then try to flash with twrp.
Same answer as in OP forum :
Before flashing, you should have done that.
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Now, if it doesn't work, it can be quite complicated....
Try updating the TWRP or use CM recovery
http://forum.xda-developers.com/showpost.php?p=69423690&postcount=60
Related
I've searched through the forums, but haven't found an answer, so I'm starting a new thread.
I received a G Watch as a gift last weekend, and it had a problem on the initial configuration. It wasn't able to connect and download any updates, so I manually flashed the updated firmware. Everything is working fine, and I'm on build LDZ22D. I was able to use G Watch Restore Tools V9 to flash system and recovery (and, in fact, boot, although that didn't seem to do anything), which got my watch up to an earlier version.
I then tried LG G Watch Return to Stock LDZ22D to get to my current build. However, I'm notified that there's an update available, but I'm not able to install it. When I try to install it through the regular user interface, it boots to recovery.
I've tried using the stock recovery, but had no luck with getting anything other than the android with the sore tummy appearing. I've used TWRP to try to flash update.zip (the stock downloaded update) and also tried this image.
When I try to apply update.zip through TWRP recovery, it gives me an error.
E: Error executing updater binary in zip '/cache/update.zip'
Package expects build fingerprint of lge/platina/dory:5.1.1/LDZ22D/19259530:user/release-keys or lge/platina/dory:5.1.1/LCA43/2160025:user/release-keys; this device has lge/cm_dory/dory:4.4.2/KVT9L/561735d166:eng/test-keys
It looks like the release keys are set to a nexus 7 build number (I don't understand how that's even possible). Is there a way to rewrite those keys? I understand they're part of the digital signing process, but I'm not sure why they didn't reset when I used the return to stock tool to flash my current image, which is the actual LDZ22D build. I appear to have a key mismatch. I've tried reflashing boot.img, system.img, and recovery.img manually (the ones included in the return to stock download), but they don't seem to work.
I get the same error when I try to flash the update I downloaded through ADB sideload. I'm frustrated, since my watch gives me this error, then after I reboot, it goes ahead and downloads the update.zip again, killing my cell data plan.
I'd love any help or insight into this. Is there a way to turn off the verification of the keys, or write the actual keys associated with my build? I'm new to working with a watch, and I've got limited experience working with phones/tablets through custom recovery. I'm not interested in a custom rom for my watch - I just wanted to get it to run properly on the stock image, and had a whack at getting it set up through developer options instead of letting it error out when I first got it.
Thanks in advance!
Still working on it
Okay, after quite a bit more research, it appears that my recovery.img doesn't match the rest of the build. I've tried the LDZ22D recovery.img, but it doesn't respond to any user input.
I'm now trying the factory image files from this post.
It seems there are a few people having problems getting to LCA43 recently. If you have an unlocked bootloader by now, you can try this method (TWRP restore from my LCA43 system+boot backup).
Hope this helps.
Dear all,
I am trying to install CM12 on my LG G2 mini. I have root access.
First I tried installing the CM12 zip file through a through Google Play downloaded version of TWRP, but in the recovery it gave the error: stage_empty & stage_fill in the bottom of the screen.
Afterwards, I tried to install a LG G2 mini specific version of TWRP through Rashr, and when it tried to install the TWRP zip, it gave the same above mentioned error in the recovery.
What am I doing wrong?
Kind regards,
Janberto
janberto said:
Dear all,
I am trying to install CM12 on my LG G2 mini. I have root access.
First I tried installing the CM12 zip file through a through Google Play downloaded version of TWRP, but in the recovery it gave the error: stage_empty & stage_fill in the bottom of the screen.
Afterwards, I tried to install a LG G2 mini specific version of TWRP through Rashr, and when it tried to install the TWRP zip, it gave the same above mentioned error in the recovery.
What am I doing wrong?
Kind regards,
Janberto
Click to expand...
Click to collapse
These errors are related to bitmap images. I was not able to find much information about these errors.
I need some more info about the state of your phone. Are you able to access it? If so, what android version do you have installed? If not, what do you experience when you try to access it?
mobiusm said:
These errors are related to bitmap images. I was not able to find much information about these errors.
I need some more info about the state of your phone. Are you able to access it? If so, what android version do you have installed? If not, what do you experience when you try to access it?
Click to expand...
Click to collapse
Tnx for your reply!
In the end I managed to flash TWRP and thereafter CM13.
However, Google play does not work, and when I flash CM13 again the crooked version of GApps is still installed. I will try to install the 05-03-2016 release of CM13 today and install GApps from opengapps.
Hope it will work
janberto said:
Tnx for your reply!
In the end I managed to flash TWRP and thereafter CM13.
However, Google play does not work, and when I flash CM13 again the crooked version of GApps is still installed. I will try to install the 05-03-2016 release of CM13 today and install GApps from opengapps.
Hope it will work
Click to expand...
Click to collapse
I'm glad to hear it goes better
Hoping someone might see this as useful......it sure has been a 12hr nightmare! This all started because my N9 LTE was AWFUL SLOW, like going from one app to the other took 20 seconds for it to do anything, hit a text box and 20-30sec for the keyboard to pop up, all not normal, my wife has a Galaxy Tab 2 and it's 100times faster so I decided I would try and install a custom ROM........... after spending 12hrs trying to install CM13 on my Nexus 9 LTE and it giving me errors upon booting to using TWRP I did a bunch of wipes and formatting, rooted the device, tried to get it back to factory ROM etc. and then I thought I might have a bricked the tablet :'( Here's my story.
After ~8hrs of trying to install stuff from the first custom ROM I tried, then CM13 and of course reading A LOT of websites and trying to install CM13 with it not working I decided to do a clean install of CM13 and follow the steps in this thread to make it work: http://forum.xda-developers.com/nexus-9/orig-development/rom-cyanogenmod-13-nexus-9-lte-t3273566
Installation instructions
-Check if you have the latest bootloader (3.48.0.0135) and updated /vendor partition from the latest image OR just flash latest image (MMB29K) (it says here MMB29k but latest is MMV29V so I used that)
-Flash a custom recovery
-Factory Reset
-Install ROM
-Install GApps
First Step was Flashing the Latest factory Image. I went to this Website: https://developers.google.com/android/nexus/images#volantisg
Downloaded the MMB29V, used 7Zip to get to the proper folder/files.
Used this Method here to flash to factory: http://www.droidviews.com/restore-nexus-9-stock-using-factory-images/
I was able to get this to work:
fastboot flash bootloader bootloader-flounder-3.43.0.0XXX.img
fastboot reboot-bootloader
Then I tried this:
fastboot –w update image-volantis-mmb29v.zip
However I get an error saying:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1985890160 bytes
error: update package missing system.img
I then tried to install these files manually and the system.img always fails.
After trying that several times trying to wipe then re-install etc. it didn't work and it was midnight and I was getting a little panicked, then I come across this thread: http://forum.xda-developers.com/nexus-9/help/marshmallow-ota-update-bricked-nexus-9-t3334871 and I thought WOW, thank god a solution and I'll get to have Android N, kinda cool.
I download the proper OTA file from here for my LTE model: https://developer.android.com/preview/download-ota.html
file: volantisg-ota-NPC56X-2-2edd174f.zip
I installed this file in the ADB/Fastboot folder then per the directions on my Tablet I went to recovery and, Wiped Cache chose “Apply Update from ADB”.
I then opened the command prompt, checked the device was connected using "ADB Devices", confirmed it’s there so then I tried: "adb sideload volantisg-ota-npc56x-2-2edd174f.zip"
It started working, got to ~35% then I get:
Code:
Total xfer:1.00x
on the command prompt window
and also
Code:
This Package is for "Flounder_LTE" devices; this is a "flounder"
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
on the tablet
So I thought that was weird since I clearly have an LTE device so I decided to download and try the regular N9 OTA image file: volantis-ota-NPC56X-2-3fa71d1a.zip
I then opened the command prompt, checked the device was connected using "ADB Devices", confirmed it’s there so then I tried: "adb sideload volantis-ota-npc56x-2-3fa71d1a.zip"
It WORKED!!! Felt like at least something was successful after 12hrs of screwing around with this.
Booted up everything was good went into the setup and all is good.....EXCEPT now I don't have LTE :'( my N9 is at 2% battery life so I will let it charge overnight and tomorrow and try and figure out how I can do this over again............if someone has thoughts or suggestion on something I did wrong in order to get CM13 in here I'm all ears.
Thanks!
Ok, in case someone reads this in the future, this morning after a little bit of sleep and the Tablet having fully charged I decided to try things again since I wasn't happy with Android N without LTE working.
Steps I took:
-Flashed Factory Img using adb/fastboot, used the MMB29R factory image as that's what I noticed was listed on the CM13 I was trying to install. This wasn't working using the Flash.All however I was able to manually flash all the files including system.img which was previously giving me errors so that was good. The unit booted up in the factory image but I didn't do anything I just booted to Fastboot so I could install CM13.
-I installed TWRP, made sure on first reboot after install to boot to recovery
-Moved the CM13 and Gapps-Pico to the N9
-Used TWRP to install the CM13 then Gapps
-Rebooted, all seemed to work, HOWEVER, I was getting the "Unfortunately Google Play Services has Stopped" and "Unfortunately Setup Wizard has Stopped" upon boot, can't go past this so I was frustrated.
-Found a link that said in ADB to type
Code:
pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
however this didn't do anything for me
-Tried to install another Gapps, downloaded the mini version, that didn't work either
At this point, I decided maybe CM13 isn't for me....most people would have stopped a long time ago I think lol
I decided to flash the latest stock version, MMB29V and just use that, maybe I'll try again sometime.
If you sign up for the Android Beta Program (https://www.google.com/android/beta) Android N will be sent to your device as an OTA. I had no problem upgrading to N this way on my WiFi Nexus 9. When you hit the page any device that's eligible to enroll will be displayed.
I am trying to update my oneplus 3 to the latest oxygen os 5.0 which has oreo. Every time i update the phone weather it be from the settings or manually from a zip file with deleted assets I still get the error 7 (as I am using TWRP 3.1.1-2). Everywhere says to delete assets and I still get the error, I am 100% sure I have the correct update as I got the update zip directly from the directory. Any one know what to do?
Bruucio said:
I am trying to update my oneplus 3 to the latest oxygen os 5.0 which has oreo. Every time i update the phone weather it be from the settings or manually from a zip file with deleted assets I still get the error 7 (as I am using TWRP 3.1.1-2). Everywhere says to delete assets and I still get the error, I am 100% sure I have the correct update as I got the update zip directly from the directory. Any one know what to do?
Click to expand...
Click to collapse
Yeah, I had the exact same problem. Tried removing the getprop lines from updater-script etc, that returned error 3. Then I realised there was a new TWRP version (3.2.0), so installed that, and flashed the original downloaded OS. Worked perfectly! You'll need to reinstall TWRP and re-root after that, though
Got an update notification on my nexus 6p with installed RR-P-v7.0.2 on it. After installing this OTA update i got an infinite booting screen. I loaded back into twrp and got a password prompt to mount partitions (i didn't have any passwords anywhere on my phone before). I could neither access internal storage from within recovery, nor from pc. Installed newest version of TWRP (3.4.0), didn't help. Did a full wipe, which finally helped and allowed me to see and transfer files to my internal storage. Downloaded RROS-Q-8.5.9 zip from official site, tried to install again, which resulted in same error as before. Then i found out that i can load the system even with this error presenting, but i CAN'T install magisc. I don't know if it is me, who does something wrong or is it error in system zip? Also before each attempt to reinstall RROS-Q-8.5.9 i see logs, that magisc binaries r missing, i don't know if that might be the reason of vendor error in the end. The only way i can fix it is flash official vendor.img and flash older system image. But i really want to have RROS-Q-8.5.9 on my phone, with magics. Initially i posted it in 'Nexus 6P Q&A, Help & Troubleshooting', but no1 responded, so i duplicated this post here in case some1 knows the answer. Please help.
I'm sorry for being unfriendly. I'm lazy.
Most android10rom for angler cannot be flashed without using this twrp. If you want to switch back to pie rom, use the official twrp.
Then your latest post is on the nexus6 shamu thread.
Everyone makes a mistake because the terminal names are very similar. So don't complain to kae.
https://androidfilehost.com/?fid=4349826312261691698
For the time being, there are few posts on this device, so I think it's okay to write here.
https://forum.xda-developers.com/nexus-6p/development/9-0-resurrection-remix-v7-0-t3892786
Thank you for your response anyway. Tho i managed to flash the rom without getting this vendor error at the end. Steps i did: flashed back to RR7.1.2, did a backup, wiped everything including system, than flashed new RR8.6.0, which flashed fine with no errors. After this i flashed magisk right away, and it went fine (it couldn't before, cuz of the error 'failed to mount /vendor' after attempting to flash OS zip), with exception of an error 'failed to mount /vendor (no such device)'. Still i've got nexus 6p with android 10 and root, which can't update, cuz of the permanent vendor error after i flashed magisk.
Next time i will need to flash anything, i will use TWRP u suggested. Thank you again.