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.
Related
Hello,
is there an OTA package which i can flash with a stock recovery (my phone i locked, i don't like to have an unlocked bootloader)?
I am on 4.0.2 right now...
No, you need to be rooted or unlocked to flash the OTA package. Just wait for the official one, it will probably be pushed sometime during easter
I'm still waiting for the OTA aswell
I was pretty sure that the OTA process just downloads a file which will be flashed via the stock recovery. So if someone would have this stock OTA package (update.zip) i can just place in the internal storage and reboot into stock recovery. At least on my HTC Hero at 1.5 -> 1.6 it was working this way...must have remembered something wrong there...
bluefisch200 said:
Hello,
is there an OTA package which i can flash with a stock recovery (my phone i locked, i don't like to have an unlocked bootloader)?
I am on 4.0.2 right now...
Click to expand...
Click to collapse
Haven't tried it myself (since I am rooted and unlocked) but I recon that you can unlock (and loose ALL your data), root, flash the onetime CWM Recovery, flash the 4.0.4 stock image (by which you will loose root), relock (and loose ALL your data again).
At the end you would be completely stock again. That can all be done through the GNEX toolkit by Mskip that can be found here: Link.
You can download the official Google image from here: Link
bluefisch200 said:
I was pretty sure that the OTA process just downloads a file which will be flashed via the stock recovery. So if someone would have this stock OTA package (update.zip) i can just place in the internal storage and reboot into stock recovery. At least on my HTC Hero at 1.5 -> 1.6 it was working this way...must have remembered something wrong there...
Click to expand...
Click to collapse
that was probably right with the htc hero, also on my htc desire..because the ota package was picked by the stock recovery from the sdcard
but the stock recovery on our galaxy nexus with ics, expect the ota to be on the /cache partition..without root u can't write in that partition, only the os itself can write there
bluefisch200 said:
Hello,
is there an OTA package which i can flash with a stock recovery (my phone i locked, i don't like to have an unlocked bootloader)?
I am on 4.0.2 right now...
Click to expand...
Click to collapse
If you are on yakju, root using this method (note you only need temp root, so only do up to step 6), then place the update file from here to /cache and reboot into stock recovery and flash.
efrant said:
If you are on yakju, root using this method (note you only need temp root, so only do up to step 6), then place the update file from here to /cache and reboot into stock recovery and flash.
Click to expand...
Click to collapse
Thank you
Btw. it's easier to just root the OS (go above step 6) instead of only go to 6...for the cp command you will need busybox...i have seen "cat" somewhere but i couldn't figure out how it works...but i seems to be that you can copy files without installing busybox since cat is supported from android at stock...
bluefisch200 said:
Thank you
Btw. it's easier to just root the OS (go above step 6) instead of only go to 6...for the cp command you will need busybox...i have seen "cat" somewhere but i couldn't figure out how it works...but i seems to be that you can copy files without installing busybox since cat is supported from android at stock...
Click to expand...
Click to collapse
Correct, that is why I used cat in my directions instead of cp, as you would not have busybox installed if you are not root...
I'm still on 4.0.1
Is there any way to force an OTA update to 4.0.2 or 4.0.4 without rooting. Or manually install an update with a .zip update through stock recovery rather than CWM. I am unable to get any OTA updates it says my system is up to date which it clearly isnt.
Merio90 said:
Is there any way to force an OTA update to 4.0.2 or 4.0.4 without rooting. Or manually install an update with a .zip update through stock recovery rather than CWM. I am unable to get any OTA updates it says my system is up to date which it clearly isnt.
Click to expand...
Click to collapse
No..................
Sent from my Galaxy Nexus using Tapatalk
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
sblantipodi said:
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
Click to expand...
Click to collapse
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
mwalt2 said:
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
Click to expand...
Click to collapse
is there a way to undo this process once done?
sblantipodi said:
is there a way to undo this process once done?
Click to expand...
Click to collapse
Naturally, backtrack your steps.
beekay201 said:
Naturally, backtrack your steps.
Click to expand...
Click to collapse
Can I safely remove all the files copied from the zip ?
sblantipodi said:
Can I safely remove all the files copied from the zip ?
Click to expand...
Click to collapse
Yes.. Restoring whatever in the process..if you modified anything that was there already.
Galaxy Nexus 4.3 NO ROOT w/ SuperSU_1.51.zip
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
innerspace said:
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
Click to expand...
Click to collapse
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
download the most current supersu.zip and flash it in recovery.
if you're using a toolkit (i bet you are) STOP IT.
Zepius said:
download the most current supersu.zip and flash it in recovery.
about 2 minutes prior to your reply, I updated the "Toolkit" along with all the other items (supersu, img, etc..)
And after that, my device is rooted again.
Although, the main reason I started all of this was to update my device's build further, but it seems the OTA update is now gone... I'll have to wait for it appear again and see how it goes...
Zepius said:
I'll keep that in mind...
if you're using a toolkit (i bet you are) STOP IT.
Click to expand...
Click to collapse
Thanks for the reply!
Much appreciated!
Click to expand...
Click to collapse
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
I did, though I'm fuzzy on how exactly, and no, no toolkits here. IIRC I ended up wiping, updating recovery, and then manually flashing, but I had to do it multiple times to get root to stick. Sorry I don't have any better info to provide, glad to hear a) I wasn't the only one who experienced this problem, and b) you got your root back.
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 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!
I am sorry if this question is answered already, but is there any way one can get the OTA again once the device is rooted? I mean by unroofing and factory reset or whatever means....
After rooting, OTA is still working but you'll probably lose root after it, excepted if your Superuser has an " OTA Survival " feature. In this case, you'll have to flash a stock ROM, and root it.
Sent from my Nexus 7
azvlean said:
After rooting, OTA is still working but you'll probably lose root after it, excepted if your Superuser has an " OTA Survival " feature. In this case, you'll have to flash a stock ROM, and root it.
Sent from my Nexus 7
Click to expand...
Click to collapse
be careful if you have a custom recovery, accepting an OTA might screw your device up.
sk8trix said:
be careful if you have a custom recovery, accepting an OTA might screw your device up.
Click to expand...
Click to collapse
Thanks for replying.
Will the custom recovery be overridden by the stock one? Or is there any chance of bricking the device?
sriram18981 said:
Thanks for replying.
Will the custom recovery be overridden by the stock one? Or is there any chance of bricking the device?
Click to expand...
Click to collapse
no sometimes what happens is the files dont install and you either get a reboot screen or some sort of black screen and then you might need to fix things with a toolkit through the pc or some hard kind of fix, t happened to me on a motorola Atrix a while back.
sriram18981 said:
I am sorry if this question is answered already, but is there any way one can get the OTA again once the device is rooted? I mean by unroofing and factory reset or whatever means....
Click to expand...
Click to collapse
If your phone or tablet is rooted but with Stock Recovery the OTA should work just fine as long as you haven't modified any system files that get updated through the OTA. The bigger the update is the more likely it is you will lose root and that the OTA will find modified files. On Nexus devices I've personally never seen more than an error message if the OTA fails. At most I've only ever seen "unexpected contents in" error with whatever (modified) file is the problem. The OTA will always fail if you have a custom recovery but it's not really a big deal, you can always flash the OTA update zip in your custom recovery (TWRP?), more often than not before the OTA even rolls out to your device you can find the OTA zip here or on another website.