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!
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.
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
Step one : Go to the right forum.
Wrong subforum, but basically it's because you're rooted. The easiest solution is to just flash the system.img file from the factory image via fastboot and you should be good to go :good:
Thread moved to the right sub-forum and to the right section...
arviverona said:
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
Click to expand...
Click to collapse
ota updates only work on devices that are not modified i.e. patched but you can still be rooted (aosp browser, mods to system will bork any ota). if you do not know how to reverse the patch/mod you applied to you device you need to reflash a stock version of the system (search for stock images) then apply the ota.
OP: Uninstall stickmount (doing so will copy back the stock debuggerd), and try the OTA again.
Thanks guys!
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,
arviverona said:
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,
Click to expand...
Click to collapse
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.
mdamaged said:
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.
Click to expand...
Click to collapse
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)
Duffmantp said:
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)
Click to expand...
Click to collapse
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.
mdamaged said:
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.
Click to expand...
Click to collapse
Actually I dont have stickmount installed, if that makes a difference.
Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Well then your debuggerd should be stock, and this is all just academic. If the update fails, it won't be due to the debuggerd (unless there is some other app I do not know about that messes with debuggerd and you have that installed).
Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.
wantabe said:
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.
Click to expand...
Click to collapse
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.
mdamaged said:
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.
Click to expand...
Click to collapse
That's it!
Hi,
I thought that after rooting OTA won't be available but I just got a notification about an update.
Is it safe to click "restart and install"? will it keep the device rooted?
if not, what's the easiest way to update?
nirfun said:
Hi,
I thought that after rooting OTA won't be available but I just got a notification about an update.
Is it safe to click "restart and install"? will it keep the device rooted?
if not, what's the easiest way to update?
Click to expand...
Click to collapse
Last time I updated, I noticed that TWRP took over the updating process if you have it flashed.
While updating, TWRP wont let the updating script to replace the recovery partition, so TWRP remains after the update, after that you have the option to flash more zips if you wish to.
I'd recommend you reflash SuperSU after the update.
nirfun said:
Hi,
I thought that after rooting OTA won't be available but I just got a notification about an update.
Is it safe to click "restart and install"? will it keep the device rooted?
if not, what's the easiest way to update?
Click to expand...
Click to collapse
TWRP wont flash the update... You can use Flashfire, get the latest firmware from here https://developers.google.com/android/images and flash using flashfire....
mcerk02 said:
TWRP wont flash the update... You can use Flashfire, get the latest firmware from here https://developers.google.com/android/images and flash using flashfire....
Click to expand...
Click to collapse
Should I download the OTA or full firmware?
Does it make sense the OTA is 1.1 GB?
nirfun said:
Should I download the OTA or full firmware?
Does it make sense the OTA is 1.1 GB?
Click to expand...
Click to collapse
I dont know what makes the OTA so large... I could be wrong but it is probably an OTA you would get if you were to be updating from M-N or something.... I just went right for the full firmware package, if you never used flashfire here is all the instructions https://flashfire.chainfire.eu/ but its pretty simple, click the + button at bottom right, click flash firmware package, select the files to flash and it will start doing its thing, I chose not to flash recovery when you get to that point, I was concerned it was gonna flash the stock recovery so didnt want to do that....
I flashed the OTA but now my root is gone
mcerk02 said:
TWRP wont flash the update... You can use Flashfire, get the latest firmware from here https://developers.google.com/android/images and flash using flashfire....
Click to expand...
Click to collapse
Last time I ran the update OTA, TWRP ran the update script just fine...
Hey guys! I have enrolled to beta program to get 7.1.1 so now I am on 7.1.1 October 5 patch. But I got a security update patch and I thought that I've done nothing with my root to the /system so I tried to update my phone using restart & update function in "System Update" . It brought up TWRP with some failed script. Now I'm on October 5 patch and I don't have any notification about system update and it shows that my system is up to date. How can I get and flash the November 5 security update? Please help
tauio111 said:
Last time I ran the update OTA, TWRP ran the update script just fine...
Click to expand...
Click to collapse
I heard others say this as well, I have NEVER had TWRP flash an OTA for me....
---------- Post added at 10:01 PM ---------- Previous post was at 09:55 PM ----------
Suren Manukyan said:
Hey guys! I have enrolled to beta program to get 7.1.1 so now I am on 7.1.1 October 5 patch. But I got a security update patch and I thought that I've done nothing with my root to the /system so I tried to update my phone using restart & update function in "System Update" . It brought up TWRP with some failed script. Now I'm on October 5 patch and I don't have any notification about system update and it shows that my system is up to date. How can I get and flash the November 5 security update? Please help
Click to expand...
Click to collapse
Here s the page for the 7.1.1 download, I would imagine it has the latest security update.... https://developer.android.com/preview/download.html
mcerk02 said:
I heard others say this as well, I have NEVER had TWRP flash an OTA for me....
---------- Post added at 10:01 PM ---------- Previous post was at 09:55 PM ----------
Here s the page for the 7.1.1 download, I would imagine it has the latest security update.... https://developer.android.com/preview/download.html
Click to expand...
Click to collapse
It says that flashing factory image will prevent getting future OTAs. So should I check that webpage every month to get the security updates? Os there a way to get OTAs back?
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
Suren Manukyan said:
It says that flashing factory image will prevent getting future OTAs. So should I check that webpage every month to get the security updates? Os there a way to get OTAs back?
Click to expand...
Click to collapse
Not getting OTA's while rooted is nothing new.... You can check that page every now and then if you wanted to....
mcerk02 said:
Not getting OTA's while rooted is nothing new.... You can check that page every now and then if you wanted to....
Click to expand...
Click to collapse
Well actually now I got the OTA. The problem is I don't know how to flash it. Because FlashFire is not working anymore.
If you can figure out where is downloaded to I am sure flashfire will flash it, When mine was downloaded I couldn't find the file in system/cache or anywhere else so I gave up and just flashed the whole firmware package.... If you find it, let me know how it goes...
nirfun said:
Should I download the OTA or full firmware?
Does it make sense the OTA is 1.1 GB?
Click to expand...
Click to collapse
Yes it makes sense. These are not incremental OTA zips that you may be used to from previous Nexus devices.
mcerk02 said:
I dont know what makes the OTA so large... I could be wrong but it is probably an OTA you would get if you were to be updating from M-N or something....
Click to expand...
Click to collapse
This is a full OTA patch. The quick explanation is that these OTA zips will update over whatever you have installed (custom rom, stock, rooted, etc) and will patch every partition to the zips OTA level. You could be on OTA #1, 2, 6, 11 or whatever, the zip will update over each previous update.
Sent from my Nexus 5X using Tapatalk
mcerk02 said:
If you can figure out where is downloaded to I am sure flashfire will flash it, When mine was downloaded I couldn't find the file in system/cache or anywhere else so I gave up and just flashed the whole firmware package.... If you find it, let me know how it goes...
Click to expand...
Click to collapse
I think it is in data/ota_package/update.zip. I can see it with root browser but FlashFire doesn't see it.
Guys? No one knows how to update a rooted phone through OTA and without FlashFire?
Suren Manukyan said:
Guys? No one knows how to update a rooted phone through OTA and without FlashFire?
Click to expand...
Click to collapse
adb sideload an OTA image (file does not exist for 7.1.1 developer preview 2, fyi):
https://developers.google.com/android/ota
or
follow section 11 of my guide to update via fastboot:
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
adb sideload an OTA image (file does not exist for 7.1.1 developer preview 2, fyi):
https://developers.google.com/android/ota
or
follow section 11 of my guide to update via fastboot:
http://forum.xda-developers.com/showthread.php?t=3206930
Click to expand...
Click to collapse
As I said I've found a zip called update.zip in data/ota_package. Can it be the OTA , can I try to sideload it?
Suren Manukyan said:
As I said I've found a zip called update.zip in data/ota_package. Can it be the OTA , can I try to sideload it?
Click to expand...
Click to collapse
Supposing you have no other mods installed and no other changes to /system have been made, unroot, reboot, then see if you can adb sideload that update.zip. If it fails, you have two ways on how to do so successfully and without Flashfire like you asked.
Sent from my Nexus 5X using Tapatalk
Just unlocked, rooted (w/Magisk), and installed TWRP about a week ago. I'm on the stock ROM with the Feb security update. The March security update is pushing to my phone but fails install due to the previous mentioned items. I'm reading that a few problems are popping up that are contributed to the update so I'm holding off on installing it for now. How can I get it to quit trying to install it and showing the notification in the status bar? You can't dismiss the notification and if you reboot it tries to install the update again..
How did you install TWRP and keep it across updates?
Thanks for the response! I'm not 100% sure what you're asking, but I installed TWRP and magisk while on 8.1.0 and the Feb 2018 security update. A week or two later the March security update was released and pushed to my phone as an OTA but it fails install due to (and I'm guessing) the unlocked bootloader and root. Now I constantly have a failed install message in my notification bar and it won't go away. How can I keep the phone from attempting to install the OTA Update knowing it will fail?
the ota update is failing to install because your phone is rooted. the bootloader can be unlocked, but otas will fail to install if the os is not completely stock.
if you manually flash the march update, whether it's the ota or the full factory image, the notifications about an update being available or the failed install will go away.
altwu said:
the ota update is failing to install because your phone is rooted. the bootloader can be unlocked, but otas will fail to install if the os is not completely stock.
if you manually flash the march update, whether it's the ota or the full factory image, the notifications about an update being available or the failed install will go away.
Click to expand...
Click to collapse
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Gulfstream 650 said:
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Click to expand...
Click to collapse
When I got the notification to update, I just long pressed on it and hit the toggle to turn off notifications from whatever it was that it said it was coming from...Google play services I think?
Sent from my Pixel XL using XDA Labs
I flashed the full March Factory Image using the bat.all script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
kboya said:
I flashed the full March Factory Image using the flash-all.bat script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
Click to expand...
Click to collapse
Did you try turning off automatic update in Developer mode.
No, to me that is a no no especially if you have Flashfire installed
Gulfstream 650 said:
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Click to expand...
Click to collapse
kboya said:
I flashed the full March Factory Image using the bat.all script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
Click to expand...
Click to collapse
same here. no problems with the march update + magisk. i've never updated using an ota. i always flash the full factory image.
Gulfstream 650 said:
Thanks for the response! I'm not 100% sure what you're asking, but I installed TWRP and magisk while on 8.1.0 and the Feb 2018 security update.
Click to expand...
Click to collapse
Let me elaborate:
Right now, if you install TWRP permanently, you don't get any OTAs. So you must install a full image. When you install the full image, TWRP get's wiped. So you always have to install TWRP using your computer. That's a real hassle for me.
Or is there any easy way how you can install a full image, while keeping TWRP or reinstalling TWRP on top without using a computer?
fiverings said:
Did you try turning off automatic update in Developer mode.
Click to expand...
Click to collapse
I'm not sure if this is a question to me or the OP!
Me? No, there's no need as once flashed any OTA notification is redundant and no longer displayed. Anyway, I usually dl and flash the new factory image when it's posted online. The whole process takes maybe 20 mins including the dl time. Also, if there are any "new issues" with a release, as the OP is suggesting, it's just as easy to go back a month with the previous factory image (easier as it's already dl'd)
kboya said:
I'm not sure if this is a question to me or the OP!
Me? No, there's no need as once flashed any OTA notification is redundant and no longer displayed. Anyway, I usually dl and flash the new factory image when it's posted online. The whole process takes maybe 20 mins including the dl time. Also, if there are any "new issues" with a release, as the OP is suggesting, it's just as easy to go back a month with the previous factory image (easier as it's already dl'd)
Click to expand...
Click to collapse
Good point, it's fairly easy to revert to the previous version if problems crop up. I'm going to go ahead and make the plunge. **edit** installed the March image and reinstalled TWRP and Magisk, so far so good.
Cool. Hope it stays that way.