Hi all,
Just got a Nexus 7. Say if I root my device with the Toolkit, will it be able to get future updates when Google releases them? And if it's posible, will a update from Google remove the root hack?
stan2 said:
Hi all,
Just got a Nexus 7. Say if I root my device with the Toolkit, will it be able to get future updates when Google releases them? And if it's posible, will a update from Google remove the root hack?
Click to expand...
Click to collapse
You'll always be able to update. It's more a matter of whether or not you'll need to undo some of the changes you made. Changes that cause OTA updates to fail include: custom kernels, modified system apks, etc. It really depends on what the OTA update is patching.
If the only change is adding root, you'll most likely be able to install OTA updates, but will need to re-flash supersu or fix the permissions on the su binary manually.
Sent from my Nexus 4
comminus said:
You'll always be able to update. It's more a matter of whether or not you'll need to undo some of the changes you made. Changes that cause OTA updates to fail include: custom kernels, modified system apks, etc. It really depends on what the OTA update is patching.
If the only change is adding root, you'll most likely be able to install OTA updates, but will need to re-flash supersu or fix the permissions on the su binary manually.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks for your reply.
So re-rooting is needed after an update? Sry, I'm still new with all the superuser lingos atm =D
stan2 said:
Thanks for your reply.
So re-rooting is needed after an update? Sry, I'm still new with all the superuser lingos atm =D
Click to expand...
Click to collapse
It's a bit of a misnomer that the device will need to be re-rooted. I say this because the su binary does not get removed, rather the owner and permissions for /system/bin and /system/xbin are set by OTA updates. This leads to a lot of talk about "losing root" after updating.
Technically all that needs to be done is to have the owner and permissions reset on the su binary. Most people find it easier to just re-install the SuperSU apk rather than modify the file permissions.
Pro-tip:
The ownership and permissions should be as follows:
owner: root, group: root (uid:0, gid:0)
permissions: 06755
YES. Mine was rooted on the first day I got it back in September and its been updated twice since then.
Sent from my Nexus 7 using xda app-developers app
You can always use OTA RootKeeper its the tool I always use when updating and has never failed
Sent from my SIII in a Galaxy Far Far Away
*GalaxyDev* said:
You can always use OTA RootKeeper its the tool I always use when updating and has never failed
Sent from my SIII in a Galaxy Far Far Away
Click to expand...
Click to collapse
Absolutely agree that OTA RootKeeper is a must have for OTA updating. Makes it totally painless to reestablish root.
Thanks everyone for replying, super useful! I got my device rooted =)
Rooted or not, if you delete any system apps you may have issues with getting updates.
Related
Hello all
Have searched this forum, but im not really sure what to do.
I've used titanium backup to perm remove a few stock apps, the exchange stock app and amazon app
Now i can't recive any updates OTA, and i get this message..:
assert failed: apply_patch_check("/system/app/Stock.apk"....
E:Error in /sdcard/download/OTA_Ace_HTC_WWE_172_405_3_r2_1_32_405_6_release_1632939lowfu0y78jktpp2.zip
(status 7)
using 2.2 android version number 1.32.405.6
please help
//Cham
You can't accept OTA updates when you are rooted.
I see, but only used temp root with visionary
is that going to affect something?
Or what are my options to get a hold of updates in the future, a costum rom instead? I do kinda like the stock rom, just without stock apps
anyone?
Once again, if you are rooted, it doesnt matter how, you CANNOT accept ota update.
If you deleted something you shouldnt have, then restore the backup to that, or do a factory reset and re-root.
Ok i just figures since it was TEMProot that it didn't matter. Tnx for the reply, tried the factory default option (no luck), is there any place where I can get the Stock firmware to re-flash the phone?
Or would anyone in here recommend another rom ? Tons of custom roms, as I can tell.
Thread moved in Desire HD General.
go here and youll find your rom that you need,
you need the ones that are "RUU_Ace_HTC_WWE" in the file name, as these are what we call World Wide Editions
Thank you very much.
Just to make sure I do not **** something up, what are the steps i should follow, to install the rom?
This is what I did: http://forum.xda-developers.com/showthread.php?t=888109
Got the same problem -- some time ago I removed some "useless" apps from my /system/app folder, and when 1.72 update was released I wasn't able to install it in any way (I was trying to follow this guide). I restored the missing apps, and then everything went fine using the guide mentioned above!
Hope this helps.
sitlet said:
You can't accept OTA updates when you are rooted.
Click to expand...
Click to collapse
Sorry but that ain't correct... You *can* update your phone if you're rooted, the main problem is that root will be gone after update. The best solution is to *always* reject OTA updates provided by HTC and wait until devs here have found a safe way to update your device without losing root privileges.
Thank you
Thank you all, it gave perfectly sense since I'm quite happy with the stock firmware, i'll stick with this. The root is not so necessary for me at least for now
I'm glad it was corrected that visionary did not remove the ability for OTA, that was also what I've read before used it.
I'm intrigued in rooting my Nexus 7, but I also love google's stock android, no extra bloatware and apps makes me a happy camper, and thats why I waited for a Nexus tablet in the first place. Here's my question:
Is it possible to root the Nexus 7, get superuser permissions, change DPI settings, etc.... while retaining stock android (no flashing or different roms) so that whenever an OTA gets released, the device still lets you install the updated without giving any problems?
jakeellis01 said:
I'm intrigued in rooting my Nexus 7, but I also love google's stock android, no extra bloatware and apps makes me a happy camper, and thats why I waited for a Nexus tablet in the first place. Here's my question:
Is it possible to root the Nexus 7, get superuser permissions, change DPI settings, etc.... while retaining stock android (no flashing or different roms) so that whenever an OTA gets released, the device still lets you install the updated without giving any problems?
Click to expand...
Click to collapse
Yeah, you can root and get su permissions without changing stock. You need to use this to get OTA and still keep root: https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
I'm not sure if the DPI would revert back to the original settings when updated, but it's something to try.
Also, if you remove any of the apk's under the system folders, you will not be able to update. The update checks to see if they are all there before it starts installing.
great..... do you think the device would still be rooted after an official OTA?
Don't see why not. You would need to run OTA root keeper again, to re enable root. If you read the description in play, it tells you that it temporarily disables root so that it hides it from the OTA update
Anyone actually try this yet? I had OTA Rootkeeper on my razr and it didn't work sometimes.
Dawg5 said:
Anyone actually try this yet? I had OTA Rootkeeper on my razr and it didn't work sometimes.
Click to expand...
Click to collapse
I haven't tried it yet. I let mine update before I rooted it.
Have head mixed reports on here, most say it works and some say it doesn't. You just have to take the chance.
If it does not save, its very easy to root again using a toolkit so it's not a big problem......
Just a heads up that from looking around it seems there is no root method on the new Jellybean Firmware that does not require a bootloader unlock, so if you are a user that does Not want to unlock their BL and still keep root, don't take the OTA.
The update broke the symlinking method found by Wolf, and I think that was the only working one. Correct me if I am wrong c:
Also, Can someone (Preferably one who doesn't care about bootloader unlocking) please confirm if the OTA rootkeeper works? (Voodoo)
ToD
Also posted in TF201 Prime Fora.
Thing O Doom said:
Also, Can someone (Preferably one who doesn't care about bootloader unlocking) please confirm if the OTA rootkeeper works? (Voodoo)
Click to expand...
Click to collapse
I am running 4.2.1 on a locked TF300T and OTA rootkeeper re-rooted after I updated from 4.1
Worked for me too.
http://forum.xda-developers.com/showthread.php?p=39167713#post39167713
Worked like a champ for me.
Sent from my SCH-I510 using xda app-developers app
bads3ctor said:
I am running 4.2.1 on a locked TF300T and OTA rootkeeper re-rooted after I updated from 4.1
Click to expand...
Click to collapse
OTA Rootkeeper didn't maintain root for me coming from official 4.1.2. I only just put TWRP on the device last night (successfully, I might add ) but no matter what su binary I flash, I just can't get superuser or supersu apps to update the su binary from the market.
The binary is definitely on the device (OTA Root Keeper confirms this) but none of the apps can request elevated privileges from it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
I would like to know also, if I do a Factory Reset alter upgrading to 4.2, I'll be able to restore root with OTARootKeeper. Tks!
luismsm said:
I would like to know also, if I do a Factory Reset alter upgrading to 4.2, I'll be able to restore root with OTARootKeeper. Tks!
Click to expand...
Click to collapse
Matter of luck as far as i understand ..
- i lost root after upgrade .. i dont bother either.. the tablet is smooth is enough for me now
I am still using 4.1 on WW because I don't want to lose root. The ota failed and it it's impossible to restart.
Sent from my SGH-I747M using XDA Premium HD app
ogger151
I lost my root when I upgraded to JB. My problem is I do want to unlock my bootloader and can not. ASUS is useless. I sent my tablet back twice under 2 separate rma's clearly stating it was because there unlock gives me network error. The second time they told me they can not unlock it for me. So why did the Dumb**s"s have me send it back twice. I called there 800 number the so called tech said they do not support third party apps. I told him its not a third party app its on your support website under updates so he has to check. Oh well there it is he says we still can not unlock it for you. You have to do it. And I have read lots of forums with people experiencing the same problem none of the solutions have worked. So here I am I need to root this without unlocking my boatloader because I can not unlock it and neither will Asus. Next time I will by a Nexus or a Samsung. There support is terrible and there techs are clueless no one seems to whats going on. Asus themselves have acknowledged on xda forums of the network error when you use there unlock tool but when you call them there like what that's strange. Never again Asus NEVER.
Humm.. I think I will continue to use 4.1 because I also need root.
Anyway, I would like to do a Factory Reset. This should not change my /system partition and invalidate root restore, right?
Tks
luismsm said:
Humm.. I think I will continue to use 4.1 because I also need root.
Anyway, I would like to do a Factory Reset. This should not change my /system partition and invalidate root restore, right?
Tks
Click to expand...
Click to collapse
I tried system reset to get the OTA again. It did not reset the OTA, but I maintained root. I can't recall if I restored root from Voodo OTA rootkeeper or it survived the system reset on its own.
So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device
You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta
A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade
Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app
u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378
Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.
I am, unfortunately, running on MF3 firmware still and have my phone rooted and "customized" (ie I have Titanium backup blocking a few files). I'd like to be able to take the OTA update so I can update my firmware which is still pretty outdated (Android 4.2.2).
What do I need to do in order to be able to take the OTA update and what is the best way to proceed? Will the most recent FW version allow me to obtain root permissions or do I need to do something "fancy" like use survival mode in SuperUserSU?
Let me know the best way to proceed when you get the chance. Thanks!
jbrookley said:
I am, unfortunately, running on MF3 firmware still and have my phone rooted and "customized" (ie I have Titanium backup blocking a few files). I'd like to be able to take the OTA update so I can update my firmware which is still pretty outdated (Android 4.2.2).
What do I need to do in order to be able to take the OTA update and what is the best way to proceed? Will the most recent FW version allow me to obtain root permissions or do I need to do something "fancy" like use survival mode in SuperUserSU?
Let me know the best way to proceed when you get the chance. Thanks!
Click to expand...
Click to collapse
If you have modified or deleted any system files the ota will not work. The latest version, nl1, is rootable with towelroot. If the ota doesn't work then I'd flash the nb1 tar file in Odin, see the general forum, and then ota from there.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you have modified or deleted any system files the ota will not work. The latest version, nl1, is rootable with towelroot. If the ota doesn't work then I'd flash the nb1 tar file in Odin, see the general forum, and then ota from there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm sure I have at least frozen some of those files using titanium backup . . . What's the best way to handle it? Do a backup of my TB settings, unfreeze everything, then try to get the OTA update? I haven't even been prompted for an OTA in months and I'm assuming it's because I currently have root and have frozen some of those files . . . Do I need to remove root in order to get the OTA prompt or is it likely a result of me freezing files?
Thanks for your help!
jbrookley said:
I'm sure I have at least frozen some of those files using titanium backup . . . What's the best way to handle it? Do a backup of my TB settings, unfreeze everything, then try to get the OTA update? I haven't even been prompted for an OTA in months and I'm assuming it's because I currently have root and have frozen some of those files . . . Do I need to remove root in order to get the OTA prompt or is it likely a result of me freezing files?
Thanks for your help!
Click to expand...
Click to collapse
I'm not sure why you haven't gotten the prompt but it's not because of root. Try unfreezing the apps. Make a backup first
Sent from my Nexus 5 using XDA Free mobile app
jbrookley said:
I'm sure I have at least frozen some of those files using titanium backup . . . What's the best way to handle it? Do a backup of my TB settings, unfreeze everything, then try to get the OTA update? I haven't even been prompted for an OTA in months and I'm assuming it's because I currently have root and have frozen some of those files . . . Do I need to remove root in order to get the OTA prompt or is it likely a result of me freezing files?
Thanks for your help!
Click to expand...
Click to collapse
If you try to OTA with root, it will get to about 30% and then fail because the update checks for root if it's anything like the at&t update. I suggest unrooting and going back to 100% stock before trying any OTA updates.
I have posted a guide here: http://forum.xda-developers.com/galaxy-s3-att/general/how-to-restore-device-status-to-t2832880
I know it's for the GS3, but should also work on the GS4.
You guys are awesome. Sounds like this is plenty of information to get started. Thanks for your help!