Related
Will i be able to apply the ota after i root my device i dont want to brick it or loose root?
Thankyou in advance
garner said:
Will i be able to apply the ota after i root my device i donty want to brick it or loose root?
Thankyou in advance
Click to expand...
Click to collapse
Yes but you'll need too root again after I believe.
recklesslife85 said:
Yes but you'll need too root again after I believe.
Click to expand...
Click to collapse
thanks for your reply hope it wont brick the device!
garner said:
thanks for your reply hope it wont brick the device!
Click to expand...
Click to collapse
It won't.
The OTA's come in one of two ways. An incremental package (where it updates from Revision X to revision Y and a full package).
The full package is a full ROM - it wipes /system and pushes everything.
The incremental update is much smaller and patches existing files. This is what you'll be getting. In order to do this the OTA does an assert on every file it wants to patch and makes sure that it hashes out to its expected value. If the hashed value does not match the expected value the update WILL NOT APPLY. You'll get error(7) and it will tell you which assert failed.
So, if you root and don't change anything in /system, flash a new kernel, use an insecure boot image then you'll be able to apply the OTA fine. You will need to fix the permissions on the su binary though as it will recursively chmod /system (su will still be there but with the wrong permissions). Flash the su update package again though and you'll be fine.
krohnjw said:
It won't.
The OTA's come in one of two ways. An incremental package (where it updates from Revision X to revision Y and a full package).
The full package is a full ROM - it wipes /system and pushes everything.
The incremental update is much smaller and patches existing files. This is what you'll be getting. In order to do this the OTA does an assert on every file it wants to patch and makes sure that it hashes out to its expected value. If the hashed value does not match the expected value the update WILL NOT APPLY. You'll get error(7) and it will tell you which assert failed.
So, if you root and don't change anything in /system, flash a new kernel, use an insecure boot image then you'll be able to apply the OTA fine. You will need to fix the permissions on the su binary though as it will recursively chmod /system (su will still be there but with the wrong permissions). Flash the su update package again though and you'll be fine.
Click to expand...
Click to collapse
Thankyou for clearing that up with me, i might just wait till after the ota release then do it
krohnjw said:
It won't.
The OTA's come in one of two ways. An incremental package (where it updates from Revision X to revision Y and a full package).
The full package is a full ROM - it wipes /system and pushes everything.
The incremental update is much smaller and patches existing files. This is what you'll be getting. In order to do this the OTA does an assert on every file it wants to patch and makes sure that it hashes out to its expected value. If the hashed value does not match the expected value the update WILL NOT APPLY. You'll get error(7) and it will tell you which assert failed.
So, if you root and don't change anything in /system, flash a new kernel, use an insecure boot image then you'll be able to apply the OTA fine. You will need to fix the permissions on the su binary though as it will recursively chmod /system (su will still be there but with the wrong permissions). Flash the su update package again though and you'll be fine.
Click to expand...
Click to collapse
what if I just unlock the bootloader and leave everything else the way it is?
rock7632 said:
what if I just unlock the bootloader and leave everything else the way it is?
Click to expand...
Click to collapse
You'll have no problems.
krohnjw said:
You'll have no problems.
Click to expand...
Click to collapse
cool, thanks. I plan on unlocking the bootloader as soon as I get the phone
I followed the directions to unlock the bootloader and root that are posted in the development forum.
Today I decided to try the OTA update.
It reboots to install it, tries to for a very short time and then goes to the picture of an android with an exclamation point. No Idea why, so I'll probably just go a different route.
I don't think mine did that. I was unlocked + rooted (but no CWM flashed or anything) - it rebooted to apply the update, I got a little progress bar for a minute and then it was done.
Restore Root after OTA
Hi,
Can anyone please help with guidance on how to restore root after an OTA update? Running stock ICS ROM (unlocked bootloader) and rooted using Superboot R3.
Can I just simly run the superboot again to root the device?
Thanks,
SAM
jasbur17 said:
I followed the directions to unlock the bootloader and root that are posted in the development forum.
Today I decided to try the OTA update.
It reboots to install it, tries to for a very short time and then goes to the picture of an android with an exclamation point. No Idea why, so I'll probably just go a different route.
Click to expand...
Click to collapse
This is exactly what mine did last night, (found the update from O2) now it wont see the update again ?
What do i need to do to get the update again ? and why didnt it work the 1st time ?
sidhaarthm said:
Hi,
Can anyone please help with guidance on how to restore root after an OTA update? Running stock ICS ROM (unlocked bootloader) and rooted using Superboot R3.
Can I just simly run the superboot again to root the device?
Thanks,
SAM
Click to expand...
Click to collapse
A little bump as I'm looking for the same answer, could anyone help me on this one please
Sorry, ignore my question, found out the answer in the superboot guide. Thanks!
Yes, just run the root batch file again.
r3k0 said:
This is exactly what mine did last night, (found the update from O2) now it wont see the update again ?
What do i need to do to get the update again ? and why didnt it work the 1st time ?
Click to expand...
Click to collapse
Do you have clockwork recovery installed?
I think that OTA fails if you have an alternative recovery.
I have root and unlocked bootloader, i flashed the original recovery over clockwork one...let's wait and see if OTA apply succesfully.
lesilent said:
Do you have clockwork recovery installed?
I think that OTA fails if you have an alternative recovery.
I have root and unlocked bootloader, i flashed the original recovery over clockwork one...let's wait and see if OTA apply succesfully.
Click to expand...
Click to collapse
The OTA update zip should get downloaded to /cache. You can then use CWM recovery to flash that if you don't want to revert to stock recovery.
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
For me the same problem.
I think something went wrong during the update. The installation of the update was already 30 minutes ongoing and nothing happened. After resetten the phone it started up with still 4.0.1 and no system update availiable.
Anyone an idee what went wrong?
---------- Post added at 11:53 AM ---------- Previous post was at 11:13 AM ----------
chrisjaffe said:
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
Click to expand...
Click to collapse
See following guide : http://forum.xda-developers.com/showthread.php?p=20843237
Worked for me. The problem is that I have CWM recovery installed.
People use this phone on stock?
Sent from my Galaxy Nexus using Tapatalk
I'm having the same problem. I think it's because CWM borks the update. Any ideas anyone? I was hoping to only do OTA updates until/if I start installing custom roms.
chrisjaffe said:
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
Click to expand...
Click to collapse
You cannot install OTA the updates if you are rooted and have Clockwork Recovery installed. The only way you can update to 4.0.2 is to either install one of the many custom roms available or revert back to the stock recovery.
dr9722 said:
You cannot install OTA the updates if you are rooted and have Clockwork Recovery installed. The only way you can update to 4.0.2 is to either install one of the many custom roms available or revert back to the stock recovery.
Click to expand...
Click to collapse
Not true:
http://forum.xda-developers.com/showthread.php?p=20843237
Laintsurge said:
I'm having the same problem. I think it's because CWM borks the update. Any ideas anyone? I was hoping to only do OTA updates until/if I start installing custom roms.
Click to expand...
Click to collapse
Yeah, I had the same problem, but see link from above: http://forum.xda-developers.com/showthread.php?p=20843237
dr9722 said:
You cannot install OTA the updates if you are rooted and have Clockwork Recovery installed. The only way you can update to 4.0.2 is to either install one of the many custom roms available or revert back to the stock recovery.
Click to expand...
Click to collapse
True.
EddyOS said:
Not true:
http://forum.xda-developers.com/showthread.php?p=20843237
Click to expand...
Click to collapse
Your link contradicts your reply.
Thanks for the replies all.
The problem is that I do not have CWM installed, and my GN is not rooted. I am very happy with stock ICS so this is the first phone I have had in over 10 years that I have not installed a custom ROM on.
One thing to note is that I did force the install of 4.0.1. I was experiencing the volume bug and had to leave on a road trip so i could not wait for the first OTA to roll out to me. But to do that I did fastboot boot not fastboot flash for CWM so after a reset I am back on the stock recovery.
So any other ideas how to get the update to restart? The bootloader is obviously unlocked if that makes any difference.
Thanks,
cj
sstang2006 said:
True.
Your link contradicts your reply.
Click to expand...
Click to collapse
I'm not sure what you are reading, but here it is:
1) Whether you have root or not, it makes no difference.
2) Having CWM vs. stock recovery does make a difference, but only somewhat. In both cases, you CAN install the OTA update. It's just that the procedure is a little different. With the stock recovery, the OTA will install automatically. With a custom recovery (like CWM) it will install, but you have to install it manually.
efrant said:
I'm not sure what you are reading, but here it is:
1) Whether you have root or not, it makes no difference.
2) Having CWM vs. stock recovery does make a difference, but only somewhat. In both cases, you CAN install the OTA update. It's just that the procedure is a little different. With the stock recovery, the OTA will install automatically. With a custom recovery (like CWM) it will install, but you have to install it manually.
Click to expand...
Click to collapse
1- No one said root will make a difference.
2- This thread is regarding a user who receives an OTA update. If he does not have the factory recovery it will fail.
chrisjaffe said:
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
Click to expand...
Click to collapse
sstang2006 said:
1- No one said root will make a difference.
2- This thread is regarding a user who receives an OTA update. If he does not have the factory recovery it will fail.
Click to expand...
Click to collapse
Unless I'm reading the original post incorrectly, the thread is about a user who received the OTA update and it didn't install. His questions were: 1) What caused this? and 2) How to get the update to process?
Saying that the OTA will fail if he doesn't have the stock recovery, I suppose, addresses his questions but, instead of just saying that, would it not be more helpful to tell him that the OTA doesn't install automatically with CWM, it just needs a different install process, which EddyOS pointed him to), instead of just saying it will fail. In any case, you are correct -- lets just tell all users to flash back the stock recovery to install OTA updates.
I have the same problem. I flashed google Yakju images over my bell yakjuxx images. Boot loader is unlocked obviously but not rooted and no cwm.
I did however flash a different radio, not sure if that was my issue. Now the update has disappeared so I can't retry.
Quidlor said:
I have the same problem. I flashed google Yakju images over my bell yakjuxx images. Boot loader is unlocked obviously but not rooted and no cwm.
I did however flash a different radio, not sure if that was my issue. Now the update has disappeared so I can't retry.
Click to expand...
Click to collapse
Again, see the thread that EddyOS and davomgz linked to above. Instructions are there. Make sure your read the thread, and not just the first post.
efrant said:
Unless I'm reading the original post incorrectly, the thread is about a user who received the OTA update and it didn't install. His questions were: 1) What caused this? and 2) How to get the update to process?
Saying that the OTA will fail if he doesn't have the stock recovery, I suppose, addresses his questions but, instead of just saying that, would it not be more helpful to tell him that the OTA doesn't install automatically with CWM, it just needs a different install process, which EddyOS pointed him to), instead of just saying it will fail. In any case, you are correct -- lets just tell all users to flash back the stock recovery to install OTA updates.
Click to expand...
Click to collapse
In his first post he did not specify which recovery he had.
chrisjaffe said:
Thanks for the replies all.
The problem is that I do not have CWM installed, and my GN is not rooted. I am very happy with stock ICS so this is the first phone I have had in over 10 years that I have not installed a custom ROM on.
One thing to note is that I did force the install of 4.0.1. I was experiencing the volume bug and had to leave on a road trip so i could not wait for the first OTA to roll out to me. But to do that I did fastboot boot not fastboot flash for CWM so after a reset I am back on the stock recovery.
So any other ideas how to get the update to restart? The bootloader is obviously unlocked if that makes any difference.
Thanks,
cj
Click to expand...
Click to collapse
(I suppose you have the GSM version because of your ATT logo)
As you are describing right now, you are not rooted and in stock recovery.
Try flashing manually the OTA 4.0.2 which you can find here: http://download.peteralfonso.com/maguro
If it fails, then the original OTA 4.0.1 you forced was not the real OTA from google, so reflash the 4.0.1 from the above link and then flash 4.0.2.
If you have he CDMA version then find the OTA for that.
efrant said:
Again, see the thread that EddyOS and davomgz linked to above. Instructions are there. Make sure your read the thread, and not just the first post.
Click to expand...
Click to collapse
Thanks efrant! Those instructions worked.
I DID however discover something that I have not seen posted anywhere.
It would appear (for obvious reasons) that the OTA updates checks for version integrity. Due to me installing a different radio (Bell GN radio) the OTA update aborted itself and I saw the abort again when trying to manually update. This time I could see that the "radio" was mentioned and aborted. I re-installed the original Yakju radio from ITL41F and did the manual OTA update and it worked!
Now I just have to re-install the Bell GN radio image.
Quidlor said:
Thanks efrant! Those instructions worked.
I DID however discover something that I have not seen posted anywhere.
It would appear (for obvious reasons) that the OTA updates checks for version integrity. Due to me installing a different radio (Bell GN radio) the OTA update aborted itself and I saw the abort again when trying to manually update. This time I could see that the "radio" was mentioned and aborted. I re-installed the original Yakju radio from ITL41F and did the manual OTA update and it worked!
Now I just have to re-install the Bell GN radio image.
Click to expand...
Click to collapse
Yeah, I should mention that in the first post. (You could have also removed the assert in the updater-script file, and it would have installed.)
efrant said:
Yeah, I should mention that in the first post. (You could have also removed the assert in the updater-script file, and it would have installed.)
Click to expand...
Click to collapse
Can I prevent this problem for future OTA updates? Say 4.0.3 is pushed out, should I remove the assert in the update-script file now? or wait until it says "there's an update available"?
I don't want to have to manually update every time because I used a different radio.
Thank you very much for the answers. I did not mean to cause such a fuss. I am aware of how to flash the image manually, as I did that to force the 4.0.1 update.
I guess what (as it turns out) I was really asking was, What caused this to stop? And how to I retry/restart the automatic update?
The only other info that I can think that is relevant here is that I am sure that I forced the actual OTA. I wonder if something happened during the flash, or since, that corrupted something that the update is checking.
Oh and it is an unlocked GSM Nexus though I am currently in the UK for about 6 months so I have given up my ATT contract for a Pay-as-you-go Lebara SIM while here.
Thanks again for the answers, next time I'll try to be more clear the first time.
cj
Quidlor said:
Can I prevent this problem for future OTA updates? Say 4.0.3 is pushed out, should I remove the assert in the update-script file now? or wait until it says "there's an update available"?
I don't want to have to manually update every time because I used a different radio.
Click to expand...
Click to collapse
When the next update comes out, you can either either flash back the original radio before updating, or remove the assert in the update-script file in the new update.
Hi to everbody here
I googled and found lots of tutorials how to update to yakju.but what i dont understand will i be able to ota and install the update after i change to yakju? i just want to switch it to yakju and after that to install updates over air normally? Whats the easiest way?
Thanks
Theres how to instructions here. Search: imm76d 4.0.4 yakju/maguro repacks, it's odin way to do it and easiest
Sent from my Galaxy Nexus using xda premium
errepu Medical
But thats when you have yakju version??im on yakjuxw!
arydrsr Excerpts
I have the Canadian galaxy nexcus so is its not on yakju.all i want is to change it to yakju and then receive ota updates and install them.
aldenh said:
I have the Canadian galaxy nexcus so is its not on yakju.all i want is to change it to yakju and then receive ota updates and install them.
Click to expand...
Click to collapse
Use this to convert to yakju. Make sure you do all the optional steps in part D, and you will receive every OTA update. yakju is the first build that receives OTA updates, so I'm not sure I understood your initial concern.
efrant said:
Use this to convert to yakju. Make sure you do all the optional steps in part D, and you will receive every OTA update. yakju is the first build that receives OTA updates, so I'm not sure I understood your initial concern.
Click to expand...
Click to collapse
My concern was that when i switch to yakju and receive ota updates in the future im not able to install them.because some reprted their not able to install the updates they get the notification but when they go to install it shows up a error or something.
aldenh said:
My concern was that when i switch to yakju and receive ota updates in the future im not able to install them.because some reprted their not able to install the updates they get the notification but when they go to install it shows up a error or something.
Click to expand...
Click to collapse
That is because those people did something wrong...
efrant said:
That is because those people did something wrong...
Click to expand...
Click to collapse
So when i do it like in this link that you posted im not gonna have problems receiveing and installing ota updates in the future?
aldenh said:
So when i do it like in this link that you posted im not gonna have problems receiveing and installing ota updates in the future?
Click to expand...
Click to collapse
not unless you modify some of the system files. if you leave everthing stock, you will get the OTAs properly and not have any issues.
aldenh said:
So when i do it like in this link that you posted im not gonna have problems receiveing and installing ota updates in the future?
Click to expand...
Click to collapse
Not if you follow the steps, and do the optional steps in part D. No problems.
Notes on optional items and other issues:
4) WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the corresponding boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically, but it will install using a custom recovery like CWM. See this thread for details.
Click to expand...
Click to collapse
what does this mean then??
means thats if you want the update to install, you need to have the radio, boot.img and recovery from the stock version that you are on. if you dont, it will fail on install.
aldenh said:
what does this mean then??
Click to expand...
Click to collapse
Exactly what Zepius said and what I said before: you need to do the optional steps in part D.
Ok now I understand thank you guys
are they any known issues with this 4.0.4 version?because i dont have any issues with this 4.0.1 version but I want better battery life and camera performance.
aldenh said:
are they any known issues with this 4.0.4 version?because i dont have any issues with this 4.0.1 version but I want better battery life and camera performance.
Click to expand...
Click to collapse
I personally have no issues whatsoever, but some have indicated that they have signal loss issues. There are threads on the topic. A quick search will pull them up...
EDIT: Regardless, you can always go back to 4.0.2 or even 4.0.1 if you want...
aldenh said:
are they any known issues with this 4.0.4 version?because i dont have any issues with this 4.0.1 version but I want better battery life and camera performance.
Click to expand...
Click to collapse
These are the exact reasons why I went to 4.0.4 as well.
I think that it's worth it and I haven't had any issues either. In fact, it also fixed my random signal drop problems on the Rogers network as well.
Hi,
I did it and everything went good.but after i was done with everything a backed up my files with the galaxy nexus root toolkit 1.4 before and when i was restoring my files with that app it said something like "modifiying boot bla bla" cant remeber so im worried that now the boot file is different and im not gonna be able to install the updates when i receive ota updates in the future??
aldenh said:
Hi,
I did it and everything went good.but after i was done with everything a backed up my files with the galaxy nexus root toolkit 1.4 before and when i was restoring my files with that app it said something like "modifiying boot bla bla" cant remeber so im worried that now the boot file is different and im not gonna be able to install the updates when i receive ota updates in the future??
Click to expand...
Click to collapse
That's right, if you have a different kernel (contained in the boot.img), the next updates will not work. You need to flash the stock kernel. Like in the link I had posted earlier.
That's what happens when you try to take shortcuts by using toolkits -- you could have easily backed up your data yourself by running a nandroid script...
efrant said:
That's right, if you have a different kernel (contained in the boot.img), the next updates will not work. You need to flash the stock kernel. Like in the link I had posted earlier.
That's what happens when you try to take shortcuts by using toolkits -- you could have easily backed up your data yourself by running a nandroid script...
Click to expand...
Click to collapse
But i locked the bootloader again before i did the restore so you think the boot file now is different??
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!
i have tried to update when the notification came out.
it failed so i tried to unroot and updated again.
it also failed so i downloaded the zip file of JWR66Y and tried to install through recovery mode.
but it showed me that
warning: no file_contexts assert failed "/system/build.prop"........
and then abort.
anyone have the same problem?
i don't know how i can update.
you modified your build.prop
thats why its failing.
you need a stock build.prop to proceed to use the OTA.
Zepius said:
you modified your build.prop
thats why its failing.
you need a stock build.prop to proceed to use the OTA.
Click to expand...
Click to collapse
How?
I am new in this
eric_22 said:
How?
I am new in this
Click to expand...
Click to collapse
how you modified it? i dont know. some mod you installed, a custom kernel, anything really.
if you need a stock build.prop, you need to find it and replace the one on your phone.
Or you could back up your phone to your p.c and flash the stock image from your p.c
Sent from my Galaxy Nexus using Tapatalk 4
Zepius said:
how you modified it? i dont know. some mod you installed, a custom kernel, anything really.
if you need a stock build.prop, you need to find it and replace the one on your phone.
Click to expand...
Click to collapse
i just replace the build.prop downloaded from internet and when i reboot the phone, it stop in the GOOGLE scene.
How am i suppose to do?:crying:
Problem solved.
i Just flash the JWR66Y and it works.