Related
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
I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
exhibit679 said:
I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
Click to expand...
Click to collapse
You must return to stock before you attempt to install that zip. That means you cannot be rooted or have custom recovery in place
I've got a stock N5 I bought from Google on LMY48B and there's still no update for me.
Does anyone know what the roll-out timeline is for the LMY48I?
When should I conclude that I'm not going to get it OTA and resign myself to factory wipe and flashing the image?
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Nemesis02 said:
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Click to expand...
Click to collapse
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
moeREM said:
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
Click to expand...
Click to collapse
I have the same problem her as well with my nexus 5 it keeps saying error with little droid I've tried side loading manually but it didn't work also tried hard reset and wiping cache but nothing solved the problem so i just figured out the problem is the package it self
Same problem here
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
lpganesh said:
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This possibility makes me spend a lot of time, becouse i have lcd_density changed and all apps when i restore a backup are not in the main screen.
walt disney said:
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Click to expand...
Click to collapse
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Working - confirmed
cloney said:
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Click to expand...
Click to collapse
Thanks, confirmed that this method worked. Managed to update my rooted nexus 5 to LMY48I
Tried to install ota update after reverting to stock recovery using Simple Recovery Switcher app. However, also the error message, with little Android picture also appears. Please help
I assume this removed your root, though.
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Pastorelli's said:
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Click to expand...
Click to collapse
I'm with you, not going to try to flash these things, there are a few zip files out there dated a couple days ago, apparently the zips aren't tested prior to release since everyone is getting failure when flashing the zip file.
Is there really no method to apply OTA updates on rooted/modified devices (e.g. modify the update.zip itself to bypass whatever checks it performs)?
Same problem here- only had a custom recovery and root. brought back the stock recovery and did full unroot from SuperSu.
OTA update installtion stops with "Error".
Just flash the system image from the update.
Sent from my Nexus 5 using Tapatalk
Thanks, I ended up doing this http://forum.xda-developers.com/showpost.php?p=62288667&postcount=196
(flashing stock system, boot and recovery from my current version, letting OTA update install and re-rooting according to http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905)
I guess i could have flashed the new version just the same.
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.
I wanted to update my nexus 5 to marshmallow OTA, so I went and checked for system updates and downloaded the next update for it which I think is LMY48I. After downloading the update I press restart and install. So after shutting down the and the Google boot logo shows it says updating system for a little while then it says error. What is the problem and how can i fix it?
Is the phone running an unrooted stock rom with stock recovery?
Yes
And thanx
Yes
Sent from my Nexus 5 using XDA Forums
Strange. Maybe backup your data and flash a stock ROM using fastboot commands?
Okay but I tried sideloading updates through fastboot commands but it doesn't recognize my phone once I go bootloader mode so will it work for stock rom? And it also says I need to update my adb where can I find the latest?
Hello everybody, I hope to find help here.
My phone is the HTC One A9, Europe Version ("hiaeuhl"). Recovery is TWRP 3.0.2-0.
The background story is that I already managed to install Cyanogenmod after downgrading the original ROM to Version 1.10 and unlocked the bootloader with the HTC Unlock tool. I also managed to decrypt the device.
I'd like to update my system regularly, but unfortunately the last running version is the cm-13.0-20160904-NIGHTLY-hiaeuhl.zip from September 4th.
If I try to install the latest versions of Cyanogenmod (for example from September 9th) I always get the error
hiae.veryfy.trustzone() failed to read current TZ version: -2
Updater process ended with ERROR 7
I already tried to remove the lines that check this in the file updater_script inside the ROM's zip, then I could install the update, but afterwards I was stuck in a boot loop.
The error has nothing to do with the encryption, it apears with and without device encryption, and it has nothing to do which system (original or custom) is installed before flashing. It is also indifferent if I try the update via the system's update function or directly in TWRP. It's the fact that the Cyanogenmod version from September 4th is the last working for me. I definetly chose the right one for hiaeuhl, but it seems the developers have added a feature that makey my device incompatible to this ROM.
If there is anything I can do to update my system again, please let me know.
Have the same issue.
We need to update it, but I don't know how
jira.cyanogenmod.org/browse/NIGHTLIES-3351
Here is how I could solve the issue:
- flashing the latest stock firmware (and let it possibly completely update)
- install TWRP via fastboot
- from TWRP a factory reset
- install new version of the Cyanogenmod from TWRP
It worked for me, now I can use my beloved custom Rom
The Same Problem
I have exactly the same Problem, last working CM-Update was the 3rd September
Did you try my solution? With the older CM Rom versions for the HTC A9 you had to downgrade the stock rom, otherwise the CM wouldn't have started after the installation. Now it seems that the stock rom has to be the latest one (for me the 1.56) that you are able to flash the latest CM versions.
I do not have the latest stock Rom, my os is 1.27.161.6, seems actually cm needs 1.57, i am unlocked and s-off
You should probably find the right version for your phone here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
You should take the one with the right cid for your phone (which you can find with "fastboot getvar all" in the fastboot mode)
Thanks, i will try it and report
The last build i found for my version is 1.27. this is what i have
Hmmm... then I guess you have to wait until the new version appears in the forum. Seems that you have a device with vodafone branding. Since you already set S-off you also have the possibility to change your cid to one of the existing newer firmwares.
Is there a solution without going back to stock?
I'm not an expert, but I don't think so. It seems that the version number of the stock rom is stored somewhere even after changing the system to Cyanogenmod, and this version has to be the latest one. So unfortunately, as far as I know, you'll have to do the flashing procedure again...
thanks Silberhase, now i am on CM 13 again. Thats what i did: wrote Supdercid, searched a ruu-version for my build, found a 1.56.401.70 version, flashed this, then flashed twrp 3.0.2.0 again, factory reset - without factory reset i was not able to install cm, format data, recovery, latest cm update, flash gapps, restore my other data with titanium, done....
I'm glad to hear it worked for you!
Yes, but next Problem or better i actually do not know what problems will raise. After updating today successfully to last cm build phone is encrypted... TWRP requires password for decryption. Problem all over forums. Today i habe no fun to Format data again and restore all.
That's also what I experienced. Other users reported that the current TWRP version 3.0.2.0 can't handle the encryption of the HTC One A9. And every update will encrypt the device again. As a workaround you can do this:
- copy the downloaded update from /sdcard/cmupdater to the external memory card
- boot to the recovery (when asked for password push the cancel button) and install both the update and the gapps again (without wiping anything) from the memory card.
Its a pity, all worked perfectly. Installed last cm.. Which encrypted phone. Restored my backup. All Working. Updated apps, want backup again.... .... Error opening /system/addon.d (not a directory)..error in generating tarlist......Create tarfork()
Process Ended with error 255
I'm trying to help as much as I can even though I have no experience with all this. I never did a backup
Maybe you find the answer here:
http://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462
Maybe it helps to mount "system" in TWRP and then delete /system/addon.d. But it seems that this step has to be repeated before every backup.
Any news to this theme? Is Twrp able to handle A9 again in new Version?
The recent version 3.0.2.0 of TWRP is available for the A9 but can't handle it's encryption. It works anyway if you are willing to use some workarounds.