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.
hello everyone I just have a couple question regarding my honor 6x USA version. I am still stock MM 6.0 EMUi 4.1....
1. Will I receive ota updates if I have successfully unlocked bootloader and installed root?
2. I have also tried to back up my device via twrp and get a failed error. Is this caused by backing up the oem info?
1. Last time it didn't work for me. The update got downloaded, rebooted to recovery, but TWRP was unable to install it via the command from update app. So I did force-update and live happily...
2. You need to be more specific about the error. It's basicly a hard copy, so not much can go wrong.
Reep1324 said:
1. Last time it didn't work for me. The update got downloaded, rebooted to recovery, but TWRP was unable to install it via the command from update app. So I did force-update and live happily...
2. You need to be more specific about the error. It's basicly a hard copy, so not much can go wrong.
Click to expand...
Click to collapse
The error occurred during the process of backing up data...Error 255 I also believe it said something about tar fork?
http://lmgtfy.com/?q=TWRP+Error+255
Hi, my son's phone became unusable after clicking on an MMS link. I have since been able to unlock and get TWRP installed on it. After that I am unable to flash ANY kind of firmware on it (PRA-LX2). It had already updated to the latest version of EMUI droid 6. No matter trying to flash via Fastboot, sideload or SD card nothing works. In some places I found info saying that one can't flash lower versions of Android as the latest update changes the partitions. Huawei says the latest update is unavailable for download, so no way to get it as obviously HiSuite does not work.
If anyone can help me out I'd be very grateful. If there is any other info anyone needs about this problem please just let me know and I'll do my best to find what you need to help. Thanks
1N51D10U5 said:
Hi, my son's phone became unusable after clicking on an MMS link. I have since been able to unlock and get TWRP installed on it. After that I am unable to flash ANY kind of firmware on it (PRA-LX2). It had already updated to the latest version of EMUI droid 6. No matter trying to flash via Fastboot, sideload or SD card nothing works. In some places I found info saying that one can't flash lower versions of Android as the latest update changes the partitions. Huawei says the latest update is unavailable for download, so no way to get it as obviously HiSuite does not work.
If anyone can help me out I'd be very grateful. If there is any other info anyone needs about this problem please just let me know and I'll do my best to find what you need to help. Thanks
Click to expand...
Click to collapse
**SOLVED** using PRA-LX1 oeminfo
1N51D10U5 said:
**SOLVED** using PRA-LX1 oeminfo
Click to expand...
Click to collapse
Did you flash the PRA-LX2 firmware or you let the recovery to flash PRA-LX1??
Hello after updating to Oreo 8.0.0 my Nokia drop network signals. I have to restart it many times to get back network. Is it only me getting this issue or is there anyother.
Also stock camera app not working.
Whenever i open it it says couldn't connect to camera. On other hand all other application working fine.
Did you install it manually or via updater? Did you install the homebrew Oreo from hikari_calyx? Do you have a custom recovery installed? @sargodian2
1st i installed original Nougat with OST LA. Then notification pop up for oreo 8.0.0 i just i stalled it. Then i unlocked bootloader and i stall chinese twrp.
I just checked today there's another update. V8.1.
How i can install it ?
Just let the device to download it and install.
Or install it manullay.
I have unlocked bootloader.
And chinese twrp installed.
sargodian2 said:
I just checked today there's another update. V8.1.
How i can install it ?
Just let the device to download it and install.
Or install it manullay.
I have unlocked bootloader.
And chinese twrp installed.
Click to expand...
Click to collapse
DON'T! It will brick your device, you cannot install this update. To your signal problem: try clearing cache + dalvik
Hello! As there isn't a forum for the Poco M5 yet, I'm posting it here. I received MIUI 14 via OTA, I downloaded it, it was installed and the phone asked to reboot. After it rebooted, I got a message saying that it was not possible to update and that I need to download and try again. I've tried 4 times (via OTA) and the same thing always happens, after rebooting it doesn't install the update. What can I do? Thanks for your help!
Danylyca said:
Hello! As there isn't a forum for the Poco M5 yet, I'm posting it here. I received MIUI 14 via OTA, I downloaded it, it was installed and the phone asked to reboot. After it rebooted, I got a message saying that it was not possible to update and that I need to download and try again. I've tried 4 times (via OTA) and the same thing always happens, after rebooting it doesn't install the update. What can I do? Thanks for your help!
Click to expand...
Click to collapse
Download the recovery ROM and update it through recovery mode:
Xiaomi Recovery Mode: Full Guide for Mi, Redmi, POCO
What is Recovery Mode and Recovery ROM. What's the difference between it and OTA. How to enter recovery mode and make a Hard Reset.
miuirom.org
Yes, I know about that solution but I really want to understand why this is happening and I would prefer to update via OTA instead oof forcing the update via recovery
pl1992aw said:
Download the recovery ROM and update it through recovery mode:
Xiaomi Recovery Mode: Full Guide for Mi, Redmi, POCO
What is Recovery Mode and Recovery ROM. What's the difference between it and OTA. How to enter recovery mode and make a Hard Reset.
miuirom.org
Click to expand...
Click to collapse
Danylyca said:
Yes, I know about that solution but I really want to understand why this is happening and I would prefer to update via OTA instead oof forcing the update via recovery
Click to expand...
Click to collapse
From what I found, MIUI 14 on Poco M5 is a major Android version-changing update, from Android 12 to 13. There is no OTA update found on the internet, only Recovery and Fastboot.
It would be either a bug of Xiaomi server that gives you an update announcement with OTA, or it had detected a wrong phone version and pushed a wrong device OTA that does not fit, so it won't flash. Or other reasons.
Try force stop the updater, clean the updater data and cache. Then check the update and see if it gives you a correct update.
This update file would be quite large, a few GB.
Recommend to do back of your data and apps, so in case anything happened, you might need factory reset or data wipe.
Since this is a major update, incompatibility is to be expected.