4.1.2 altered build.prop file can't receive OTA update - Nexus 7 Q&A, Help & Troubleshooting

A while back I altered my build.prop file and accidently deleted it. I didn't make a backup so I restored it with one that someone posted and I haven't had any problems.
However since I did that, the OTA update that I got notified for did not install.
My boot loader is unlocked and I am rooted with stock recovery.
How can I update to 4.1.2 manually and still keep root?
I understand there are plenty of posts about this but everyone has a different problem and I'm just trying to get the correct information. Thanks for any help.
Sent from my Nexus 7 using xda app-developers app

somerandomname1 said:
A while back I altered my build.prop file and accidently deleted it. I didn't make a backup so I restored it with one that someone posted and I haven't had any problems.
However since I did that, the OTA update that I got notified for did not install.
My boot loader is unlocked and I am rooted with stock recovery.
How can I update to 4.1.2 manually and still keep root?
I understand there are plenty of posts about this but everyone has a different problem and I'm just trying to get the correct information. Thanks for any help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Download the OTA update JZO54K-fromJRO03D
Download SuperSu or Superuser
put the OTA update and SuperSu or Superuser in a in your /sdcard/Download directory
Flash ClockworkMod recovery from fastboot
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-grouper.img
Code:
> fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
Boot recovery from the fastboot menu
Install the OTA update, then install SuperSu or Superuser.

Thanks man appreciate it.
Sent from my Nexus 7 using xda app-developers app

this actually didn't work...everything was working fine, but it aborted and mentioned my build.prop file as the reason why...

somerandomname1 said:
this actually didn't work...everything was working fine, but it aborted and mentioned my build.prop file as the reason why...
Click to expand...
Click to collapse
Here's the build.prop from JRO03D load that up and try again. If that fails, you can manually update to 4.1.2 from the factory image without modifying user data.

this worked my friend, thanks.

I'm having the exact same problem, same circumstances, down to the update not taking because I accidentally deleted a system file, except the file in question is the gmail .odex file because I deleted that to install the unreleased gmail 4.2 app. Any help?
EDIT: Fixed thanks to user comminus via PM. Cheers.

Related

[Q] Nexus 4.2.1 UPDATE failed with Clockwork mod

Can you please help me answer how to install OTA updated with CWM installed. I get this error saying the installation aborted .. it boots into CWM
is there any step by step method to get the new update on nexus 4
Thanks
you need stock rom, no modifications made, and stock kernel for it to work
Download and extract the original 4.2 and fastboot flash system system.img and it'll restore all missing apps.. I had to do it earlier to allow the system to install the update
Sent from my Nexus 4 using xda app-developers app
I reflashed stock recovery but now the update isn't available. Any ideas?
billybennett said:
I reflashed stock recovery but now the update isn't available. Any ideas?
Click to expand...
Click to collapse
update manually.
So I got my update but it keeps failing during install. I'm rooted and every time the update starts it kicks over to CWM recovery and stops with a message something like, "do you want to install this untrusted zip file" I say yes but it still fails. I have even tried to manually install the update through CWM but that fails too. My N7 is rooted but otherwise stock, I have not removed any stock apps or flashed roms or kernels so WTF must I do???
Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham
zelendel said:
Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham
Click to expand...
Click to collapse
I don't know where, but I saw a few posts about working updates to 4.2.1 with CWM recovery.
However, I'm not getting it to work.
How do I get rid of the recovery without loosing the root?
If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.
You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham
4.2.1 update getting installation aborted
Hey, can some please post the stock Nexus 4 v4.2 build.prop file? I can't seem to install the v4.2.1 update without it...
Thanks...
zelendel said:
You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham
Click to expand...
Click to collapse
Successfully installed OTA here while rooted with CWM recovery, though everything else is stock.
billybennett said:
If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.
Click to expand...
Click to collapse
Hey,
got an Error over here with stock recovery and root.
However, tengen says he made it with CWM and root - maybe it's because I'm using stuff like Busybox or the Pimp my Rom APK?
EDIT: I think its because of the %-BatteryMod I'm using. I'll try to flash the custom rom.
Greetings

How to update?

Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Jms122589 said:
Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You will need the stock kernel and your /system partition must be completely unmodified. Bootloader state and recovery don't matter. After accepting an update you will lose your custom recovery and root, so you will have to reflash but that's no big deal.
Sent from my Nexus 7 using Tapatalk HD
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Jms122589 said:
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
udimars30 said:
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
Click to expand...
Click to collapse
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Jms122589 said:
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Correct. Just extract system.img and boot.img from the package you download, then plug your tablet into USB, boot it into the bootloader, and do the following two commands:
fastboot flash boot boot.img
fastboot flash system system.img
If you want to wipe data, also do:
fastboot erase cache
fastboot erase userdata
That'll get you back to complete stock.
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Jms122589 said:
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Extract them to your desktop somewhere, then do fastboot from the command prompt.
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
sorry but i didn't get this part 'As long as you do that and you don't let root apps modify files on your /system partition' and to flash all that i need unlock bootloader??
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
udimars30 said:
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
Click to expand...
Click to collapse
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
oldblue910 said:
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
Click to expand...
Click to collapse
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
udimars30 said:
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
Click to expand...
Click to collapse
I'm on Twitter and G+. Just click on my name over on the left of this post and you can find links to my profiles.

Got update on rooted stock with TWRP

Hello,
My wife has a Nexus 4.
I unlocked the bootloader, flashed TWRP, rooted it, and installed busybox.
Yesterday she handed me her phone and it was sitting in TWRP.
She said she got a message saying there was an update and she clicked okay.
I asked her if she saw anything going on but she wasn't paying attention so I didn't know if the update was applied or not.
So... I just rebooted the system from within TWRP.
Looking at her "about phone" it still shows that she is on 4.2.1 and when I check for updates it says she is up to date.
Questions:
What to do now?
Why wasn't the update applied? ... in the past on my Nexus 7 I have done OTA updates with rootkeeper installed and TWRP applied them automatically.
Was the update file deleted from her phone or can I find it somewhere in TWRP and apply it?
Is it like a normal .zip that you install or is it another process?
I'm in the same situation, unsure what to do.
I don't want to have to to do a factory reset for a minor update.
EDIT: Also installing the OTA.ZIP in TWRP fails
Got there in the end:
a) If you want to keep your data & settings and are running the stock rom; only flash boot.img, system.img, and recovery.img (optional) with fastboot.
Here is the JOP40D factory image if you need it. occam-jop40d-factory-ca7602f0.tgz - 327.21 MB
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
alexroborock said:
Got there in the end:
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
Click to expand...
Click to collapse
There must be a better way to do this.
That is a huge security risk flashing someone else's untrusted image onto your phone.
What about adb sideload?
You can download the image directly from Google
Sent from my Nexus 4 using Tapatalk 2
You need stock recovery for the ota update to work.
Sent from my Nexus 4 using xda app-developers app
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
silverramsrt said:
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
Click to expand...
Click to collapse
Did you lose root?
Rizy7 said:
Did you lose root?
Click to expand...
Click to collapse
Yes. The update replaced the recovery_from_boot.p or whatever file and the insecure boot image I had. I just reflashed TWRP, did a factory reset and installed CM anyway.

[Q] OTA update to 4.2.2 problems

My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium
Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app
heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??
How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.

[Q] Can't install 4.4.2 OTA update due to font file

I have a Nexus 7 (2012) with 4.4, rooted, TWRP 2.6.0.0. I'm trying to update to the 4.4.2 OTA update, but it's not working. Whether I run it from the system notification prompt or try to install the file manually (in /cache) via TWRP, it fails with this error:
"/system/fonts/Roboto-Bold.ttf" has unexpected contents.​
Then it says there's an error executing the updater binary, an error flashing zip file, etc. All the standard stuff when it bombs out of an install.
I did change my font using ROM Toolbox Pro a while back, but I restored the original font and tried running it again. Still got the error. I tried downloading a fresh copy of the .ttf file and replacing the one in /system/fonts, but still got the error. It seems a little silly for the whole update to crash due to a font file, but whatever...
Can anyone help me figure out what's going on, and how to get this OTA to install properly? Thanks in advance!
Probably it's easier to flash the 4.4.2 factory image resp. system.img and boot.img of it manually than trying to recover the correct 4.4 state.
There are already some posts where I described how to do it and there is also a post in my blog describing the process.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Probably it's easier to flash the 4.4.2 factory image resp. system.img and boot.img of it manually than trying to recover the correct 4.4 state.
There are already some posts where I described how to do it and there is also a post in my blog describing the process.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well, after every failure, it reboots and goes right back to functioning perfectly as it was on 4.4. But, I will consider the direct flash of 4.4.2 if no one else has any other suggestions. Thanks!

Categories

Resources