Related
There is allegedly a new OTA update on the way, enabling 720p video, among other things.
Will rooting or rooting+recovery reflash prevent the phone from updating? If it doesn't, would I have to re-root the phone after the update?
pieter3d said:
There is allegedly a new OTA update on the way, enabling 720p video, among other things.
Will rooting or rooting+recovery reflash prevent the phone from updating? If it doesn't, would I have to re-root the phone after the update?
Click to expand...
Click to collapse
If I was you, I would simply wait for the OTA to come out and let our AMAZING DEVS get a crack at it and download the rooted version.
I would love to have the 720p and new boot animation and mobile hotspot. But i would rather have root than any of those. Already have wireless tether. But love the new boot animation....hmm. what to do.... can't wait i have a feeling once the DInc gets stocked back up and they can advertise it we will get alot of devs behind it bc the droid x supposedly has a encrypted bootloader. Not looking so good for those who were ready to drop the DInc.
Sent from my ADR6300 using XDA App
This update is supposed to include wireless N, 720p video, wireless tethering, and the droid eye boot animation. Since I already have the wireless tether app for my rooted Inc, I'm wondering what would happen if I accepted to receive this OTA update? Anyway, I agree that having root supersedes all of these features, so I will wait for the download. My question is, about how long does it usually take from the time the OTA update is released until the dev's have it ripped and ready for us to download? Thanks!
Droid Eye Boot Animation
Here is a link to directions on applying the boot animation to a rooted phone.
forum.xda-developers.com/showpost.php?p=6943967&postcount=1
It has something to do with a file called otacerts.zip in etc/security
I think the Certinstaller.odex in system/app has something to do with it do...
I'm not sure what needs to be done with them, but when modified it will block OTA
dont rename the otacerts.zip. it will kill your battery life constantly checking itself over and over.
OK I've been told to just wait for the official ota froyo update before I root. And that if I root before that I wont get the update sent to me. But I've also been told that if I wait for the official ota update I wont be able to use unrevoked forever.
please help me!!! I'm so confused. and I've looked everywhere else and I keep getting different answers.
BigNate said:
OK I've been told to just wait for the official ota froyo update before I root. And that if I root before that I wont get the update sent to me. But I've also been told that if I wait for the official ota update I wont be able to use unrevoked forever.
please help me!!! I'm so confused. and I've looked everywhere else and I keep getting different answers.
Click to expand...
Click to collapse
It's not that you won't be able to use unrevoked-forever, it's that you won't have a way to flash a custom recovery system to the phone to actually FLASH the forever file.
I recommend the following since it seems you want an official update as opposed to the RUU.
1. Perform the unrEVOked root
2. Flash unrEVOked forever
3. Flash the Stock Recovery back to the phone.
4. Hurry up and wait for the OTA.
5. Upon receiving the OTA, install. You will lose your root privileges. No worries!
6. After installing the OTA, flash ClockworkMod back to your phone
7. Use ClockworkMod to flash a root payload file (contains su and Superuser.apk)
8. Bask in Rooted/Official 2.2 Froyo goodness.
From my research, the OTA MUST have the stock recovery to install. What you will have done here is provided an "Official" platform for the OTA to download, check signatures, and install all while having S-OFF. As long as S-OFF is invoked, you can continue to replace the recovery from ClockworkMod to Stock Recovery (Android 2e) whenever you need to.
S-OFF is what makes this all possible, God Bless the bastards at unrEVOked, would like to take 'em to Peter Luger's one day!
Ok thanks man haha. I've only had this phone for two day and I rooted as soon as I got it. But then unrooted because I was that I wouldn't get froyo.
And yes thank you UNREVOKED FOREVER and, also thank rdmerck for telling me I was completely lost.
Sent from my ADR6300 using XDA App
Will there be a rooted ota for people who didn't install it or never got it. I rooted my phone and would like the better radio in hopes I will get more cell bars
There's already the option to root if you already applied the OTA update or are planning to.
Sent from my T-Mobile G2 using XDA App
Sv3nt3k said:
There's already the option to root if you already applied the OTA update or are planning to.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
i dont understand what u mean i have perm root without the ota. If i install the ota it will break root. Will i have to go thru the whole process again if i do this? I know on the mytouchslide when they came out with an ota they just rooted it so it wouldnt break the current root
i havent tried perm root yet. however search this site for 'visionary' root, which is all u really need for now. i had visionary root installed along with several root only apps (titanium backup, cachemate, setcpu, several others) and the OTA installed while my phone was rooted with absolutely no problems.
I installed the ota over the perm root and now I have no superuser permissions. When I try to run visionary it says my phone is already rooted yet I cannot run apps that require root or get the # in termal can anyone help with this
lol
the "#" denotes root access lol...... (coming from a marginal linux background..)
richierich118 said:
I installed the ota over the perm root and now I have no superuser permissions. When I try to run visionary it says my phone is already rooted yet I cannot run apps that require root or get the # in termal can anyone help with this
Click to expand...
Click to collapse
Have you tried reapplying s-off?
I am also interested in getting a solution because right before I rooted my phone I started getting ota update notifications for my phone and now I cant upgrade my phone but the notifications continue to persist. So I figure if I can get a rooted update or delete something, I can get rid of notifications.
ok i got it working what i did was do what somesaid in the begining and that was to follow the guide that doesnt use visionary for perm root. I think its call temp to perm root. I always had the s-off just not the perm root. everything is fine now
At least you were able to apply the update. I tried doing that and Clockworks Recovery halted it because some signature was verified or something.
Sv3nt3k said:
At least you were able to apply the update. I tried doing that and Clockworks Recovery halted it because some signature was verified or something.
Click to expand...
Click to collapse
I didnt use clockworks recover i used the orginal. It just made me loose root and not s-off so i used the temp-too-perm root to get it back because visionary was saying my phone was already rooted. I believe I was getting this cause i had rooted without the ota the first time. The second time i used the ota.ko Instead of the preota.ko because i used this when i didnt update to the ota on the first run.
Oh, okay. Thanks for that. I'm currently in the same boat you were in. I applied the OTA and it's reporting S-OFF, Visionary is saying I'm rooted, but certain things aren't working.
In the process of getting it fixed.
EDIT: Went through the same process you did and I'm all good to go. I was able to apply the OTA update after rooting it and then re-rooted it.
so how exactly did you root you perma root your phone again after ota.
i have perma root right now, its pre-ota, i do want to install ota though.. would i have to go back and do the manual perma-root with the "ota" files now instead of the other ones. im just confused and want to clear this up before i do anything stupid. thanks!
I recently rooted my atrix with superoneclick then i accidently updated then i belive i still had my root until i went to install a 3d theme then my phone crashed and wouldnt get past the at&t screen so i had to erase everything now on my phone i still have "super user" in my app draw but i cannot side load apps did i lose my root? what do i have to do to sideload apps again ? and i guess re root my phone
Yes i am a newb i am comming from IOS and an iPhone 4 please dont flame
If you updated, you mean 4.1.57, this is what I did to re-root when I lost mine after updating and SuperOneClick wouldn't work.
http://forum.xda-developers.com/showthread.php?t=1013931
Ok so i read that so basically i have to flash my phone back to default then root again?
Yeap, that's exactly what I did, but in that same thread, I think someone else outlined using aRoot to go over SuperOneClick.
Originally Posted by donbar85
I'm pretty new to Android (two weeks now), and want to ensure I don't end up with a bricked device, so I apologize for the 'noob' question here. I rooted with SuperOneClick. Has anyone else used this script successfully with that root method, or will it only be successful with aRoot?
Also, if I need aRoot, can I run it over top SuperOneClick, or would it be best to unroot, run aRoot (or let the script root) and then run the script?
I appreciate all the hard work I've seen done in these forums and appreciate any help anyone can offer.
---
Yes you may safely run aroot over superoneclick. Aroot is the recommended method because it cleans up a lot of things Superroneclick does.
----
Originally Posted by DJQ1212
Yes you may safely run aroot over superoneclick. Aroot is the recommended method because it cleans up a lot of things Superroneclick does.
Thank you both. I believe I will try running aRoot over my SuperOneClick root and then try out the script. Thanks again!
Click to expand...
Click to collapse
Yup the aRoot script is used in the GladiAtrix and possibly the GingerBlur rom as well. Either way. SOC is crap, not meant for atrix anyway. aRoot was written specifically for the Atrix. If you want to update to 4.1.57 read through the retain root thread over in atrix development.
after update, i can still see "su" installed in /system/bin/
I am unable to use it, getting permissioned denied message, any solutions ?
sam_t610 said:
after update, i can still see "su" installed in /system/bin/
I am unable to use it, getting permissioned denied message, any solutions ?
Click to expand...
Click to collapse
This has been explained many times. updating kills root, even though you still have superuser installed. to retain root you need to use the script in the development section when updating from 1.26 to 1.57. flash back to 1.26 and try again.
Hey everyone,
Back when it first came out, I did the Visionary temp root. The only thing I did was disable a bunch of the packages that can't be uninstalled like Facebook and such.
I read the thread about doing permanent root with Visionary causing bricks. I'd like to get clarification as to whether or not my phone is potentially at risk.
I verified that I only did temporary root, as opening a terminal and typing 'su' just yields permission denied.
Thanks in advance!
Just did the manual update and everything is fine for what it's worth
I would love to know if you have any luck with Temp Root now that you have the OTA. I don't want to install the OTA until I know VISIONary can give me Temp Root so I can tether...
temp root with visionary doesnt brick your device so dont worry, its perm root that bricks it
But does it still work? I have Visionary r10 and I don't want to accept the OTA until I know I can still tether... (but of course, I can deal with getting a newer Visionary if it's confirmed to still work with the OTA)
r14 I haven't had luck with
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.