Just a heads up for anyone who has been waiting, the newest OTA has been rooted!
http://forum.xda-developers.com/showthread.php?t=1461736
All credit goes to these guys, just letting people who dont normally check the DEV section know. I tried it and worked perfect
MAYBE PEOPLE WILL BE SMART ENOUGH TO USE VOODOO OTA ROOTKEEPER NOW..LMFAO if we get another update n they lose root, that's on them then. Can't tell you how many times it's been stressed to use that app to save root.
We can expect another update any day now, according to Gary's last statement of a new fix being in approval process.
demandarin said:
MAYBE PEOPLE WILL BE SMART ENOUGH TO USE VOODOO OTA ROOTKEEPER NOW..LMFAO if we get another update n they lose root, that's on them then. Can't tell you how many times it's been stressed to use that app to save root.
We can expect another update any day now, according to Gary's last statement of a new fix being in approval process.
Click to expand...
Click to collapse
I used that for the first time and apparently did it wrong as I lost root, so this is for the dumb people like me, lol
Also, people, like a friend of mine, who got their prime recently aren't aware of the OTA when first upgrading to ICS out of the box and are screwed
DroidHam said:
I used that for the first time and apparently did it wrong as I lost root, so this is for the dumb people like me, lol
Also, people, like a friend of mine, who got their prime recently aren't aware of the OTA when first upgrading to ICS out of the box and are screwed
Click to expand...
Click to collapse
What were the steps you took? Run app, hit save root or whatever, update, then the run app and hit restore root? That's what I did and it worked flawlessly.
Sent from my ADR6425LVW using XDA Premium.
I wish people would use it too. They are burning through root exploits on every update. Would be nice if some of these root methods could be held onto for a couple months until all the updates slow down because it gets harder each time.
demandarin said:
We can expect another update any day now, according to Gary's last statement of a new fix being in approval process.
Click to expand...
Click to collapse
Did he mention what the fix(s) was for?
BongoBong said:
Did he mention what the fix(s) was for?
Click to expand...
Click to collapse
Yes.
Changelog:
1) Closing the 9.4.2.11 root exploit.
Does rooting invalidate your warranty?
I guess "officially" it does, but you could always factory reset it if you needed to send it to Asus?
Docaroo said:
Does rooting invalidate your warranty?
I guess "officially" it does, but you could always factory reset it if you needed to send it to Asus?
Click to expand...
Click to collapse
Nope, a rooted device; when factory reset, the root still exist.
However, another option could be to unroot then factory reset.
If on a custom rom, flash back the stock rom and follow the same process as above.
I know unlocking the bootloading voids warranty but I was wondering if you could lock the bootloader as to regain your warranty?
Evo_Shift said:
I wish people would use it too. They are burning through root exploits on every update. Would be nice if some of these root methods could be held onto for a couple months until all the updates slow down because it gets harder each time.
Click to expand...
Click to collapse
Here's the issue though -- Rootkeeper will not work to restore root if you have trouble with the OTA version and need to do an update manually. We need to keep saying this so people know that they may be stuck even with Rootkeeper if they do a manual update.
I'm sorry for asking a dumb question, but this will be my first time rooting my tablet. Will all my apps and data be lost like if rooted my phone, or is the Asus back up app sufficient to not lose anything? Thank you for the help.
pudge12 said:
I'm sorry for asking a dumb question, but this will be my first time rooting my tablet. Will all my apps and data be lost like if rooted my phone, or is the Asus back up app sufficient to not lose anything? Thank you for the help.
Click to expand...
Click to collapse
All the apps and data are still there intact cause rooting has nothing to these areas. It is like building a back door in your house won't affect the storage room in your basement.
sounds good, thanks
Problem, and workaround
Folks, I had a problem with this method. I followed all the steps until this:
cat /data/local/su > /system/xbin/su
This command, and all other interactive commands attempted from the cracked root shell session, just hung indefinitely. I don't know why.
I was able to workaround the problem using this procedure on my linux machine:
echo "cat /data/local/su > /system/xbin/su" > foo.sh
echo "chown 0.0 /system/xbin/su" >> foo.sh
echo "chmod 06755 /system/xbin/su" >> foo.sh
adb push foo.sh /data/local/foo.sh
adb shell
/data/local/mempodroid 0xd9ec 0xaf47 sh /data/local/foo.sh
I would post this to the dev thread, but I don't have a high enough post count.
Moothead2 said:
I know unlocking the bootloading voids warranty but I was wondering if you could lock the bootloader as to regain your warranty?
Click to expand...
Click to collapse
We aren't able to unlock the boot loader until ASUS releases the tool next month
Sent from my Galaxy Nexus using xda premium
Related
So, I am new to this site and to the android community. I apologize if I sound stupid to any of you but if you aren't going to help I'd appreciate it if you just ignored me.
Anyway, I got my Atrix a couple days ago on AT&T and started learning about rooting and such. Everything on it is still stock, last night I upgraded to Gingerbread from Froyo and I'd just like to know if there's any specific rooting program, method I can use right now for 4.5.91 Also, when I upgraded I lost my music player widget, is there I can get it back without going back to Froyo?
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
will there be any severe consequences if I screw up?
Use gingerbreak.
Sent from my MB860 using XDA App
TheToiletSpaula said:
Use gingerbreak.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I've read that gingerbreak doesn't work with this version. I'll look it up though.
phobos512 said:
follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my mb860 using xda app
Click to expand...
Click to collapse
^^^^^ only way to root gb and probably the best way if there are other methods
savier420 said:
^^^^^ only way to root gb and probably the best way if there are other methods
Click to expand...
Click to collapse
cool, just one question. Am I supposed to have the device connected to my computer the whole time? and if not between which steps should I connect/ disconnect it? also, when I put the root.img in the C: folder, do I put the zip file or just the .img inside of it?
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
PSY0NIC said:
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
Click to expand...
Click to collapse
Since this is the 1st time I've seen some one say it this way....
If you are just trying to "root" your phone only, YES, this is the best method.
Brand new phone, all stock... just want root.... use gingerbreak?
Sent from my MB860 using XDA Premium App
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
hambone123 said:
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
Click to expand...
Click to collapse
I'm about to try it but I'm still confused about a few things like when exactly to connect or disconnect my phone and what to do after I've entered all the commands on my computer, will it install by itself? This is my first time rooting a phone, and my first time even owning an android so I want to make sure I know exactly what I'm doing
I hear you man, it's nerve wracking to worry that you're going to brick your phone. I did the gingerbreak on the last release and it worked perfectly. I'm sure this method will work fine as well, as you said I just want to be sure I'm doing the right thing for my goal: stock phone/downloaded updates/rooted. Best of luck, and thanks to anyone who gives us noobs some more reassurance.
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got, before i updated to the OTA GB i had BL unlocked and rooted, just flashed back to 1.2.6 to be rid of root and unlocked BL, then just went throught the OTA updates to get to GB and im loving it, dont really care to flash any other custom roms, BUT BEWARE DOING THE OTA TO GB AND UNLOCKING THE BL THEN TRYIN TO FLASH BACK TO A STOCK ROM WILL HARD BRICK SO DO YOUR RESEARCH so if u dont want a hard bricked phone dont do the ota stick to custom roms and ignore all OTA'S
so I got through the fastboot reboot command, phone booted back up automatically, then put the phone into debug. Then typed in the adb shell code and said the specified path could not be found.
Now I was still in the command prompt that said the c:/root
What did I do wrong?
So, adb says it is a bad path?? Do this instead..it is easier and it works -- I did it this way last night!
After "moto-fastboot reboot", once your phone has completely rebooted, go to the Android Market and download and install "Terminal Emulator." Once it is instslled and you have opened it, enter the EXACT SAME commands that you were going to type into the Adb Shell..once again, type in the commands VERBATIM. After the last command, there should be a message saying (in terminal emulator) that it was successful! Congrats, you have achieved root access on the AT&T issued stock Gingerbread 2.3.4 build! I hope it works for you!
~Eric
savier420 said:
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got.
Click to expand...
Click to collapse
I'm very vanilla. I root pretty much entirely for free wireless tethering and being able to delete bloatware.
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
aroca1978 said:
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
Click to expand...
Click to collapse
Updating to GB won't brick your phone. After updating to GB you can't down grade to older OS (like the one your on right now) that would brick your phone. So as long as you don't plan on going back to a past OS version (and I don't know why anyone would) you'll have no problems at all. As for Rooting >follow this link< and follow the instructions there after you update to GB. It works perfectly, you don't have to unlock your BL or anything else like that to just have Root on GB. Hope this helps.
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
For Questions about BL Unlocking
aroca1978 said:
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
Click to expand...
Click to collapse
Click on the link below, that thread will give you the answers and files your looking for.
> Click Here <
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
redpoint13 said:
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
Click to expand...
Click to collapse
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Don't you love those Asus emails telling you to flash things without any indication of consequences? That's why I didn't flash the one I was pmed.
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Seems to be a firmware update today just got it
Commodore 64
buxtahuda said:
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Click to expand...
Click to collapse
So it sounds like we are guaranteed to lose root then?
GreginNH said:
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Click to expand...
Click to collapse
The biggest thing for rooting to me was being able to install/use an ad-block program.
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Does it not work downloading and flashing 9.4.2.11 from asus' site and aquiring the .13 OTA that way?
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
*EDIT: Also, sorry, didn't meant to sound like a d'bag lol just trying to make sure some poor soul doesn't do a manual update thinking rootkeeper will work for them
buxtahuda said:
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
Click to expand...
Click to collapse
Good point..lmfao wasn't really thinkn of that. Exit stage right. Lol
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
AFAIK when you manually install "OTA" root keeper does not work, and seems like others are confirming this.
I just hope someone is able to quickly find another root exploit as fast as they did for .11.
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
I noticed that as well. 1st few times I hit it twice due to the delay which would end up turning it on and then back to standby/sleep
Moothead2 said:
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
Click to expand...
Click to collapse
Yes, also noticed it. We'll see if the .13 goes back to the quicker.
Duh!
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
What are the risks of this? I want to do this myself but I'm worried.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Trying now.
*RETARDED found both
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Even if this seems to work, I would be very worried about messing up the system. The OTAs are basically a patch file, and they only contain the changed bits of system files, not the whole files. (It's using bsdiff, if anyone cares.)
What this means is, if it's patching the wrong file because you lied about your version, it will very likely mess up your system - maybe even make it unbootable until you fix it with a full update.
Now, it's possible this update doesn't touch any files which changed between .11 and. 11.1, so it would be safe. But I wouldn't assume that.
buxtahuda said:
Trying now.
Click to expand...
Click to collapse
Any news? I.e. does it work or not?
It may have been put clearly somewhere else but I can't seem to locate it. Apologies if I am asking an answered question.
If I root this phone (don't intend to unlock bootloader), however:
Will OTA stop working? (because of modification)
Will doing an OTA update on rooted phone remove root?
If so, is it possible to preserve root while doing an OTA?
Will removing all traces of root be as easy as SU uninstall?
With some phones, the OTA will be broken after rooting and some it will not. This is my first Sony and I wanted to confirm if this was also the case.
jcspecs said:
It may have been put clearly somewhere else but I can't seem to locate it. Apologies if I am asking an answered question.
If I root this phone (don't intend to unlock bootloader), however:
Will OTA stop working? (because of modification)
Will doing an OTA update on rooted phone remove root?
If so, is it possible to preserve root while doing an OTA?
Will removing all traces of root be as easy as SU uninstall?
With some phones, the OTA will be broken after rooting and some it will not. This is my first Sony and I wanted to confirm if this was also the case.
Click to expand...
Click to collapse
Will OTA stop working? (because of modification) No, it would not stop working if you just root
Will doing an OTA update on rooted phone remove root? It may or may not. Nobody has tried it yet. But normally we dont recommend doing OTA after rooting
If so, is it possible to preserve root while doing an OTA? No way till now.
Will removing all traces of root be as easy as SU uninstall? Yes, there is an option in SU to unroot the phone.
manu44 said:
Will OTA stop working? (because of modification) No, it would not stop working if you just root
Will doing an OTA update on rooted phone remove root? It may or may not. Nobody has tried it yet. But normally we dont recommend doing OTA after rooting
If so, is it possible to preserve root while doing an OTA? No way till now.
Will removing all traces of root be as easy as SU uninstall? Yes, there is an option in SU to unroot the phone.
Click to expand...
Click to collapse
Hello,
Thanks so much for your clear and concise responses. Previously I've never been concerned about the unrooting of a phone or access to OTA. I just got so comfortable working with Samsung that I feel a bit out of my depth at the moment with the Z2.
jcspecs said:
It may have been put clearly somewhere else but I can't seem to locate it. Apologies if I am asking an answered question.
If I root this phone (don't intend to unlock bootloader), however:
Will OTA stop working? (because of modification)
Will doing an OTA update on rooted phone remove root?
If so, is it possible to preserve root while doing an OTA?
Will removing all traces of root be as easy as SU uninstall?
With some phones, the OTA will be broken after rooting and some it will not. This is my first Sony and I wanted to confirm if this was also the case.
Click to expand...
Click to collapse
On my phone OTA won't work on rooted device. Firmware downloads fine but it fails verification when trying to install.
jcspecs said:
Hello,
Thanks so much for your clear and concise responses. Previously I've never been concerned about the unrooting of a phone or access to OTA. I just got so comfortable working with Samsung that I feel a bit out of my depth at the moment with the Z2.
Click to expand...
Click to collapse
I can understand, I am also coming from SamsungS4. this is my first sony phone.But trust me sony has lot less hassles compared to Samsung Knox Bull****
kamalaggi said:
On my phone OTA won't work on rooted device. Firmware downloads fine but it fails verification when trying to install.
Click to expand...
Click to collapse
Interesting. Could it be something that varies across providers?
manu44 said:
I can understand, I am also coming from SamsungS4. this is my first sony phone.But trust me sony has lot less hassles compared to Samsung Knox Bull****
Click to expand...
Click to collapse
Yes. Happy to have avoided Knox.
manu44 said:
Will OTA stop working? (because of modification) No, it would not stop working if you just root
Will doing an OTA update on rooted phone remove root? It may or may not. Nobody has tried it yet. But normally we dont recommend doing OTA after rooting
If so, is it possible to preserve root while doing an OTA? No way till now.
Will removing all traces of root be as easy as SU uninstall? Yes, there is an option in SU to unroot the phone.
Click to expand...
Click to collapse
So, we can just click unroot in supersu, not have to flash FTF using FlashTool ? After this method of unroot can we safely do ota ?
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
I rooted mine specifically to disable updates. I'm not so much afraid of root exploits getting patched as I am any potential bootloader exploits being patched. I came from the galaxy s3, which got a bootloader update mid way through that was never cracked, so I'm little worried about that if I wait to long I can never unlock the bootloader. So far I've installed titanium backup, root explorer, and the kit kat sd card fix (no need for hotspot hack since I don't have unlimited data). I'm holding off on anything too major until the bootloader is unlocked and I can do a nandroid first.
I rooted the day I got my g3. I rooted and installed custom roms on my g2 and can't wait to do the same on my g3
Sent from my LG G3
I actually got a demo model from VZW, rooted that one, just to see how hard it was going to be, When I got my permanent one a few days later I rooted it out of the box, before installing anything else.
rooted and uninstalled what I could installed xposed tweaked to my liking and waiting for bootloader recovery and roms
Sent from my VS985 4G using Tapatalk
I rooted mine before I even set it up.
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
As with most of my phones, my G3 was rooted as soon as the battery was charged, and usually before being activated. Now if we could just get a bootloader unlock. :fingers-crossed:
bkhorn said:
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
Click to expand...
Click to collapse
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
tu3218 said:
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
Click to expand...
Click to collapse
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
tu3218 said:
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
Click to expand...
Click to collapse
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
tech_head said:
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
Click to expand...
Click to collapse
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
bkhorn said:
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
Click to expand...
Click to collapse
Great thanks! If I root, I'll be sure to follow your instructions.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I used "ioroot". Stump root did not exist when I got my phone.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I also used IORoot and it's very easy, Stump wasn't out when I rooted mine but from what I've read Stump is super easy and reliable.
I walked out of Best But, phone activated and Battery at like 70% and hopped on my laptop which I had with me and rooted the phone right there in the parking lot so that I could freeze System Updates right away.
Although Verizon is so slow with OTA updates anyways I really could have waited lol
Root that thing then remove all the Verizon junk and use Greenify... You'll be even more happy with how your G3 runs after doing that and it's quite easy to do.
- Tapatalked from the G3
nrage23 said:
I rooted mine before I even set it up.
Click to expand...
Click to collapse
yup me too
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
bobcat987 said:
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
Click to expand...
Click to collapse
Yeah I've seen some remarkable things done my fellow members.
spotmark said:
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
Click to expand...
Click to collapse
Very true. Thanks for that link. I'm just afraid of my screwing up my brand new toy haha Not sure why though, it seems stump root is really straight foward. I just know once I do it, I'll start messing with xposed a lot. I know when I had my S3, I was flashing roms like once a day. My gf thought I was crazy.
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.