Develop Bugs

[Q] Getting Error while try to upgrade from 4.2.1 to 4.2.2 Stock?

Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.

You're rooted, which means you edited the system, which means the OTA probably won't install. Always better to go back to 100% stock and re-root

ftrack said:
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
Click to expand...
Click to collapse
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170

Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
Huh.. I've received JDQ39 ota, I forgot to remove TWRP before hand, but it still went through anyway. It installed fine, surprised the hell out of me actually. TWRP 2.4.1.0. Didn't have any other mods though. Not even rooted.
Sent from my Nexus

Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
you can definitely install the OTA with a custom recovery. it however will not install if you modified any /system files, bootloader or radio do not match.

Oh really? That surprises me honestly. Although I never tried it, I always assumed every partition needed to have unmodified stock files (adding extra files does not matter). Apparently the recovery partition is an exception.

Petrovski80 said:
Oh really? That surprises me honestly. Although I never tried it
Click to expand...
Click to collapse
+1
I was really surprised, in a good way! xD

Does rooting only removes the ability for OTA updates?

Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4

Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app

You just need to have the stock recovery to receive OTAs.

Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4

Takes 10 seconds to reflash the stock recovery.

UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.

Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app

rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.

Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?

It was common on other platforms I've used, but I don't know about here.

Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.

phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.

TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2

nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.

Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)

phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?

Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.

If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?

[Q] OTA JSS15R While Rooted

Currently trying to update my Nexus 7 to JSS15R (8MB OTA that may have helped multitouch issue?)
I am running rooted stock ROM, unlocked bootloader etc. Current build number is JSS15Q.
I've heard the newer versions of SuperSU have the OTA fix built in. I haven't been able to update though. I noticed there was an update and I went to update my Nexus 7. It went to update like it should, but I got an error and it never changed.
Flashed the OTA fix thinking it would help. No.
Forced OTA update by stopping Google Framework. No.
Flashed SuperSU 1.65 and tried to update again. No.
Any suggestions on what I should do? Manually flash the update without loosing root or an data?

Did you reflash the ota after you flashed supersu?
What was the error message?

sfhub said:
Did you reflash the ota after you flashed supersu?
What was the error message?
Click to expand...
Click to collapse
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.

When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.

church said:
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
Click to expand...
Click to collapse
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.

datallboy said:
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
Click to expand...
Click to collapse
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.

church said:
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
Click to expand...
Click to collapse
I found a zip for the ota update, don't remember where, but should I be able just to flash it with TWRP without loosing anything?

It will lose the option to blend milkshakes

church said:
It will lose the option to blend milkshakes
Click to expand...
Click to collapse
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.

Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.

church said:
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
Click to expand...
Click to collapse
Stock recovery is on my device. I'm temporarily booting TWRP with the Nexus Toolkit so I can flash things.

datallboy said:
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
Click to expand...
Click to collapse
Next time you have an error with stock recovery (android fallen down) press/hold power, then press/release VolUp, then release Power.
This will show you the error log.
As to your current problem, if your unit won't download and notify you about JSS15R download it by hand and place in your virtual sdcard, then temporary boot into tarp and choose install, selecting the ota zip.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
datallboy said:
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Click to expand...
Click to collapse
Install the ota update.zip, then before reboot, immediately install supersu.
Do it that way and you won't lose root.

Forced OTA and it failed. I had already flashed the superSU.zip before
If you can't read this is the log...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop" [numbers and letters]
E: Error in /cache/(update file.zip)
(Status 7)
Installation aborted.
Any way to manually flash the update? Because SuperSU OTA isn't working.

So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.

Guhrasoh said:
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Click to expand...
Click to collapse
Now that you mention it I tweaked it with PimpMyRom. I'll take that off and try to update.

I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.

datallboy said:
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
Click to expand...
Click to collapse
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.

sfhub said:
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
Click to expand...
Click to collapse
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.

datallboy said:
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
Click to expand...
Click to collapse
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.

sfhub said:
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
Click to expand...
Click to collapse
I'll probably just backup apps + data and use JSS15R factory image. Made the mistake of not making a backup of my build.prop.
Good thing it's a Nexus Device!

Stock Kernel and Recovery for HTC M8 1.54.401.10

I'm trying to get my HTC M8 back to stock so I can get the new 4.4.3 update, however, I am unable to find the stock kernel for my device.
It is software version 1.54.401.10.
I flashed to the elementalx kernel and put on a TWRP recovery.
I am able to download the update but when it installs, it just goes into recovery.
I made a backup of the original kernel a few months ago however it doesn't seem to be on my phone anymore.
When I look for stock kernels they all seem to be different versions than my device.
Can someone give me a bit of advice?
There are numerous guides for other versions but none mentions my software version.

Any kernel doesn't matter.
Your problem is you don't flash stock recovery.
TWRP or any custom recovery don't work for OTA.

ckpv5 said:
Any kernel doesn't matter.
Your problem is you don't flash stock recovery.
TWRP or any custom recovery don't work for OTA.
Click to expand...
Click to collapse
How can I put the stock recovery back?

I put the stock recovery on and tried to update however I get a red triangle with an exclamation mark now...
why's it not taking properly?

I'm new to this obviously. I've figured out that's just how the stock recovery is. Now I'm trying to figure out why the ota doesn't work with the stock recovery.
I get this error when I try to install the update.
/system/lib/modules/adsprpc.ko has unexpected contents. Installation aborted.

robgo said:
I'm new to this obviously. I've figured out that's just how the stock recovery is. Now I'm trying to figure out why the ota doesn't work with the stock recovery.
I get this error when I try to install the update.
/system/lib/modules/adsprpc.ko has unexpected contents. Installation aborted.
Click to expand...
Click to collapse
This means that something of the system has been changed by you, so the ckecksum of the OTA doesn't match the configuration of your system and thus abort the installation process.
Sent from my HTC One_M8 using XDA Free mobile app

robgo said:
I'm new to this obviously. I've figured out that's just how the stock recovery is. Now I'm trying to figure out why the ota doesn't work with the stock recovery.
I get this error when I try to install the update.
/system/lib/modules/adsprpc.ko has unexpected contents. Installation aborted.
Click to expand...
Click to collapse
This means your ROM is modified, not pure stock.
I suggest you make a backup with your current ROM and restore the pure stock backup that I posted here : http://forum.xda-developers.com/showthread.php?p=54564526#post54564526
1. flash back the TWRP recovery
2. make backup of your current one
3. restore pure stock backup that I linked above
4. flash stock recovery
5. reboot then do the OTA

robgo said:
I'm new to this obviously. I've figured out that's just how the stock recovery is. Now I'm trying to figure out why the ota doesn't work with the stock recovery.
I get this error when I try to install the update.
/system/lib/modules/adsprpc.ko has unexpected contents. Installation aborted.
Click to expand...
Click to collapse
@robgo please close this thread http://forum.xda-developers.com/htc-one-m8/help/ota-update-4-4-3-t2856172. To open up two threads to aks the same question doesn't help to get to a solution any faster ....
Regarding the error. It means what @ckpv5 and I already told you.

ckpv5 said:
Any kernel doesn't matter.
Your problem is you don't flash stock recovery.
TWRP or any custom recovery don't work for OTA.
Click to expand...
Click to collapse
Oh ok, I didn't know the kernel apparently doesn't matter when doing OTA's and here I am telling him to go back to stock kernel because it's a kernel related error he has...
Best I keep out of this one then, I never even flashed another kernel.

BerndM14 said:
Oh ok, I didn't know the kernel apparently doesn't matter when doing OTA's and here I am telling him to go back to stock kernel because it's a kernel related error he has...
Best I keep out of this one then, I never even flashed another kernel.
Click to expand...
Click to collapse
Right ... it's kernel related error but to be precised, it's the kernel module error.
Flashing a stock kernel without flashing stock module, the same error will occur.

Trouble installing an ota

One or two days ago I received an ota notification. Every time I try installing the small update, the tablet boots into TWRP, and I don't know what to do next. Why does it not simply install? The nexus 7 is rooted with an unlocked boot loader. Can anyone give me a tip on how to get the update installed?

Snowby123 said:
One or two days ago I received an ota notification. Every time I try installing the small update, the tablet boots into TWRP, and I don't know what to do next. Why does it not simply install? The nexus 7 is rooted with an unlocked boot loader. Can anyone give me a tip on how to get the update installed?
Click to expand...
Click to collapse
With 5.1.1 if the system is altered such as rooting or putting a custom recovery on the device, the update won't install. You have to go back to Pure stock to receive and install updates over the air.

Batfink33 said:
With 5.1.1 if the system is altered such as rooting or putting a custom recovery on the device, the update won't install. You have to go back to Pure stock to receive and install updates over the air.
Click to expand...
Click to collapse
Thank you very much! I am glad that some one had an explanation!

How can I restore to stock recovery for LMY48L? There is no LMY48L factory image, so I can't just extract the recovery out of there. Is there any way I can manually apply the LMY48L OTA's recovery to the recovery image in the LMY47V factory image to get a "stock" LMY48L recovery?b
EDIT: Never mind, it looks very complicated. I ended up just flashing LMY47V recovery and system images, then re-updating to LMY48L, then finally updating to LMY48P. I didn't mean to hijack the OP's thread, but I asked here because it looked like he would run into the same issue as I did.