I recently dropped and broke my N5 so I got a newer one. It came with KK, so I rooted it and it's great. I decided to download LL over the OTA, so I did and it downloaded. After then downloading it then asked if I wanted to install and restart, so I said yes. It then rebooted into TWRP. At that point I had no idea what to do or whether the phone was even supposed to do that. Not knowing what to do I simply rebooted the phone. But when it rebooted it was still in KK and of course it was still rooted. Of course LL is nowhere to be found. Anyone have an idea what went wrong, because I don't? Why did the download take me to TWRP? And what do I have to do if I again decide to install LL? Thanks.
You have to be 100% stock for the OTA to install, meaning TWRP has to go. You gotta flash the stock recovery and undo any changes you might have made to /system.
Related
OK, so the MotoDev team advised me to return my phone to stock before installing JB, which will be pushed to my phone tomorrow morning...
What do I need to insure my system won't crash?
I have an unlocked bootloader, and am rooted. I already did a factory reset on my device. Some system apps are gone though, as I have deleted them (mostly Google stuff though, nothing crucial). Will I be good to go? (And yes, I will save the SBF and post it, no worries, have a Dev Host account and will upload).
In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:
hagforz said:
In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:
Click to expand...
Click to collapse
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
If you want to grab the update package and save it you should prevent it from being deleted. I know that twrp could not install asa14 OTA update when I got it so it was just hanging there in /cache along with md5 (or sha1, I can't remeber) checksum file.
I do not know if there are other ways of saving the update package nor if devs actually need it. But ASA14 got to my bootloader unlocked, gsm modded, rooted stock rom and after booting to recovery it just stayed there, no install happend (I installed it manually) because twrp did not pass the command properly or what ever the reason.
This update is coming from motorola directly, not sprint, right?
Anyway, perhaps someone can give you more accurate details. I personally would flash twrp and see if updated arrives. Because /cache is wiped by the update installer after installation. All automated process. After device boots to recovery it installs the package, wipes caches and reboots, if I am not mistaken.
I believe for the past updates we had the best luck by reverting the recovery back to stock as well. You have missing APKs that you removed so those will very likely be looked for by the update and will fail the update process if missing.
So if all goes well this should be the bare minimum I'd say for getting the update to work:
MAKE A BACKUP, don't want to have a bricked phone yeah? I mean you could have Jelly Bean on it finally... but still bricked...
Revert the recovery to stock if you installed TWRP or ClockworkMod, adb reboot bootloader | fastboot flash recovery recovery.img
Restore any and all apps you deleted from the stock image, either by restoring fully to stock or putting them back manually, wouldn't hurt to do another update check in the play store for them as well.
Temp unroot with OTA Rootkeeper
Download the update, reboot it, do a song and dance, ???, profit.
Now, you might try to restore root asap, it may or may not work, we won't know till we try.... I'm using Superuser 3.1.3 and on their website it claims its for arm devices 2.0-4.1 so maybe it'll work. Your bootloader should still be unlocked I'd imagine, so you can reflash your custom recovery and make a new backup.
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
JustinBieber said:
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
Click to expand...
Click to collapse
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
robbham78 said:
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
Click to expand...
Click to collapse
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
charesa39 said:
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
Click to expand...
Click to collapse
Thanks guys, I didn't know everything had to be stock! plus I found out that xposed will also break the ota
There's an OTA help desk sticky thread in general that tells you everything you need to know
Sent from my Nexus 5 using Tapatalk
I have a Nexus 5 running stock Lollipop (5.0). My phone is rooted and has CWM Recovery installed. I've tried to update OTA to 5.0.1 twice now. Both time, it has downloaded the update and rebooted as usual. Then CWM Recovery prompts me to install the update. After hitting "Yes" it appears to install the update and then informs me that root may have been lost. I've tried saying both "yes" and "no" to fixing that. In both cases, I've retained root, but my phone remains at 5.0 instead of 5.0.1.
From my limited rooting knowledge, I can see flashing the factory image would be the most straightforward way to updating, but obviously that would wipe my phone. Titanium can only back up so much. Plus I want a simpler way to do this in the future. To me, it seems another solution would be to revert to the stock recovery and have that install the update. However, I don't know how to revert to the factory recovery without flashing the factory image. All of that being said, what is the best way to OTA with a stock ROM but a custom recovery?
KomradeNikolai said:
I have a Nexus 5 running stock Lollipop (5.0). My phone is rooted and has CWM Recovery installed. I've tried to update OTA to 5.0.1 twice now. Both time, it has downloaded the update and rebooted as usual. Then CWM Recovery prompts me to install the update. After hitting "Yes" it appears to install the update and then informs me that root may have been lost. I've tried saying both "yes" and "no" to fixing that. In both cases, I've retained root, but my phone remains at 5.0 instead of 5.0.1.
From my limited rooting knowledge, I can see flashing the factory image would be the most straightforward way to updating, but obviously that would wipe my phone. Titanium can only back up so much. Plus I want a simpler way to do this in the future. To me, it seems another solution would be to revert to the stock recovery and have that install the update. However, I don't know how to revert to the factory recovery without flashing the factory image. All of that being said, what is the best way to OTA with a stock ROM but a custom recovery?
Click to expand...
Click to collapse
It's been said about a million times on this forum:
You have to be stock or the OTA won't work. Stock system, stock recovery, stock kernel etc. Extract and flash files from the factory image just don't flash the userdata.img file.
Yaz75 said:
It's been said about a million times on this forum:
You have to be stock or the OTA won't work. Stock system, stock recovery, stock kernel etc. Extract and flash files from the factory image just don't flash the userdata.img file.
Click to expand...
Click to collapse
Thanks. I don't spend much time on here and I didn't see a post that gave me something concrete.
I'm currently downloading the 5.0.1 factory image from Google, but since it's such a large file and my internet is quite slow, it's going to be over an hour yet before its finished. That being said, I downloaded the .zip version of the OTA update as linked on phandroid and attempted to install it with CWM. Dispite the fact that I'm running Lollipop, I got the following error. I've shortened the name of the .zip because its quite long.
-- Installing: /sdcard/0/Download/***.zip
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of google/hammerhead/hammerhead:5.0/LRX21O/1570415:user/release-keys or google/hammerhead/hammerhead:5.0.1/LRX22C/1602158:user/release-keys; this device has google/hammerhead/hammerhead:4.4/KRT16M/893803:user/release-keys
E:Error in /data/media/0/Download/***.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I flashed the factory image for Android 5.0 a couple of weeks ago so I don't see any reason why it should see the KRT16M fingerprint. Any ideas?
EDIT: Never mind. Looks like this has the same effect and won't work if I'm not completely stock. I'll just wait for the factory image to download and flash that. Correct me if I'm wrong.
I am getting the same error.
KomradeNikolai said:
I'm currently downloading the 5.0.1 factory image from Google, but since it's such a large file and my internet is quite slow, it's going to be over an hour yet before its finished. That being said, I downloaded the .zip version of the OTA update as linked on phandroid and attempted to install it with CWM. Dispite the fact that I'm running Lollipop, I got the following error. I've shortened the name of the .zip because its quite long.
I flashed the factory image for Android 5.0 a couple of weeks ago so I don't see any reason why it should see the KRT16M fingerprint. Any ideas?
EDIT: Never mind. Looks like this has the same effect and won't work if I'm not completely stock. I'll just wait for the factory image to download and flash that. Correct me if I'm wrong.
Click to expand...
Click to collapse
I actually tried reverting to stock recovery using Flashify. Though it shows success but when I try to run the update, it doesn't get past the recovery mode, android with the red exclamation mark. Not sure where I am going wrong with it specially when I have been flashing since last 3 years.
I just got this from a friend, it's the original that he never sent back for replacement. I planned to replace the battery myself and use it. I installed Resurrection Rom and somehow the file system got corrupted. No idea how it happened as the tablet already had TWRP and all I did was transfer over the rom files/gapps, recovery wipe, installed and restarted. Bootloader is unlocked.
How can I remedy this without running the risk of getting my bootloader brick from the kill switch?
EDIT:
Could it be that I went from LP to MM?
I got this fixed. I found this nv-recovery-image-shield-tablet-wifi-update3_1_1.zip in another thread, ran that and restored the tablet, stayed in fastboot and pushed the latest TWRP, booted into TWRP, and flashed Blisspop. I'm back up and running.
Alright, so it has been a while since I last tried custom roms only to go back to official EUI, so bear with me as this is probably a basic dumb question.
So I had TWRP and the official EUI. I saw that there was an OTA update and normally used the update app on the phone. It downloaded the rom, and booted into twrp which started flashing the rom. So far so good. I let it do its thing as it took some minutes... once it was ready it showed a dialog asking if I wanted the flashing process to rewrite the boot partition or let TWRP own it. I wasn't really sure which one to pick, but as I "swipes to unlock", the phone restarted anyway without letting me pick any of the two.
Now It only boots into recovery mode (TWRP). This is probably easy to fix in TWRP, but I am not sure how. Can anyone help?
Thank you.