Related
I have done a lot of reading her about rooting and updating my TF300. After getting a headspinning amount of information, I'd like someone to verify what I think I know.
I have a TF300, stock ROM, no root, running US .17. I have not received any updates after going to Settings/about tab/update and pressing the update button (I get "no updates found') I have cleared DM and CM client and rebooted several times, but no updates are found. I have tried on several WiFI networks I have access to.
1. I should be able to root using one of several one click methods I have found here, correct?
2. Once rooted and root keeper is installed, I should be able to update to .29 and keep root, correct?
3. A manual update to US .29, once rooted, will cause me to lose root, correct?
4. Will I receive Over The Air update once rooted? If not, how can I update to US .29 without losing root?
5. Is this the best path to take, or is there another path that would be easier for a newb like me (I know just enough about Android to be dangerous)? What I mean by another path is, should I manually update to US .29 and wait for a one click solution to come out later, all the while enjoying the new update.
6. All this is to fix some lag issues I have with all browsers....Tried Stock, Dolphin, Firefox, Opera...all the same. Some FC and others just hang for up to 30 seconds, even in Performance mode (With only one tab open!) So this will "FIX" those lag issues, correct?
Thank you for your time
If you're still on .17, root with sparkyroot, save it with ota rootkeeper, update to .29 (if it isn't there, they've been posted in many places on the forums), and restore root. As for fixing lag issues, it depends on what you do, rooting alone won't change anything, but you can try out the different tweaks available.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Missed a couple of your questions, yes, you will still receive ota updates if you're rooted, as long as you don't unlock the bootloader. This is the easiest way to root too, all you need to do is follow sparkyroot's instructions and back up your root.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
One question always leads to another
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Throb1231 said:
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Click to expand...
Click to collapse
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Oh, and after you've updated to .29 and rooted; don't forget to use OTA rootkeeper to backup root.
If Asus releases a new update it may save your root.
EndlessDissent said:
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Click to expand...
Click to collapse
He's still on the .17 software, so no need to do that. Just use the sparkyroot method, backup with rootkeeper and then update.
Edit to add that no, rooting will not void the warranty, just unroot before you need to send it back.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Throb1231 said:
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Click to expand...
Click to collapse
No, you need to go to:
h tt p://forum.xda-developers.c om/showthread.php?t=1704209 (sorry for the chopped up link. I can't post links yet)
and root again.
EndlessDissent said:
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Click to expand...
Click to collapse
Ah, ok. Didn't realize you couldn't restore if you updated manually.
Yes, it is as I thought. Tried Sparkys and miloj's root program and I can not get root. I ran the program twice from my lap top. Driver's for TF300 show installed in Device manager (Windows 7). ASUS sync was installed in laptop and recognized TF300 but the program was not running during root attempt.
When I run Superuser and attempt to update SU binaries, I get "Failed" when it attempts pathway to write update.
Attempted to restore using OTA rootkeeper but all I get is "SU Restored". Check boxes indicate no root.
Any other ideas?
Confirmed I am on .29 from a MANUAL update.
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Throb1231 said:
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Click to expand...
Click to collapse
Can you just install Superuser from the market? The su binaries might be there and the app just isn't installing. I may be wrong, not sure how the automated program works, but it can't hurt.
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Try manually doing the code from miloj's thread?
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Throb1231 said:
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Click to expand...
Click to collapse
Well, I can't think of anything else, you could just use the downgrade method, that's easy enough. The code really is just copy/paste though.
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Your problem is not with the superuser apk.
The actual root is when you write an "su" binary to system and makes it executable (there is some access control stuff in between, but it's what's happening in essence).
So - your trouble is not with the installation nor the messages from superuser.apk - it's with the actual rooting method.
Make absolutely sure your adb drivers are working and that you've got the files "debugfs", "su" and the other debugfs file on top of the .bat file, which is the installation script, in the same directory whilst running the .bat file.
Agreed. I posted this in development.
It was surprisingly more difficult to install the drivers correctly than anticipated.
For those noobs like me, here's a step-by-step for installing the drivers before running the root method.
http://transformerprimeroot.com/tra...all-transformer-prime-usb-drivers-on-windows/
Please note that before using the step-by-step guide above, I also had to put the tf300 in Camera Mount to even get the "“ASUS Android Composite ADB Interface" option to show up in Device Manager.
Once you get this far, you can manually update the driver (found in the sparkym3 "Drivers" folder from the download) via the step-by-step.
Sent from my ASUS Transformer Pad TF300T using XDA
I am a new member on xda, however i have read posts and forums to resolve issues with my gt-p1000n. I now own a Motorola Razr (XT910), on 2.3.5 rooted. I want to play the new 9 innings from Com2us and Inotia4. As you may all know this is not possible if your device is rooted. I have played them both on my wifes SGS2 with shell root, and sure enough...they run perfectly fine. My phone is full in root, is there any way around this? Someone please help!!!!
il0v3kush said:
I am a new member on xda, however i have read posts and forums to resolve issues with my gt-p1000n. I now own a Motorola Razr (XT910), on 2.3.5 rooted. I want to play the new 9 innings from Com2us and Inotia4. As you may all know this is not possible if your device is rooted. I have played them both on my wifes SGS2 with shell root, and sure enough...they run perfectly fine. My phone is full in root, is there any way around this? Someone please help!!!!
Click to expand...
Click to collapse
did you use a one click root? if so most of them can unroot, so you could just unroot for a bit to get your gaming on.
Good to know, I'm new to XDA and hacking my devices. I had know idea that some games or apps wouldn't work on rooted devices. Now I know
Sent from my Galaxy Nexus using xda premium
I actually did...i used super one click. Yeah it's fast once you've attained the Motorola drivers for your device. I was looking for a work around with much less hassle. In my opinion the Motorola Razr beats Samsungs Galaxy I & II in performance and video/audio quality (haven't compared against an SIII yet). Only if the Motorola Razr is rooted though. Motorola has so much more bloatware compared to Samsung, so battery life is just terrible on such an amazing device. I do appreciate the reply though, thanks! Way to make a new member feel welcomed. Looking for a full on work around, that won't require me to temoprarily unroot then reroot. Thanks though @ loosedupon!
Yup, there are quite a few actually. Don't let that stop you from rooting though, i don't know how to flash and **** like that. Personally, I'd prefer not to though. Due to all the different outcomes if you load the incorrect files. However, rooting my device has made me truly enjoy my devices (gt-p1000n & razr xt910). My Galaxy Tablet is one of the first batches out in the Latin American versions (the original 7in. with a ****ty 400 ram availability). I played Blood Brothers and Quest and Sorcery on it with little to no lags or hangs opposed to my razr. @wannahit
Try Voodoo OTA rootkeeper. It will protect root, but also allow you to temporarily unroot with the " push of a button" I use it for google movies. Works good.
Thanks chrism.brunner! I will try that. I actually tried Hide My Root, it worked. For that to work, you must set a password first. That password is needed to hide/uninstall the su apk, and su binary. I was super baked when i set mine! About 45 minutes later tried to restore my binary files. I forgot the ****ing password, [email protected]! What upset me was, there was no recovery process to have my password reset. I had to re-root my device. I will give OTA a try though. Thanks!
Just so you know, OTA Rootkeeper's latest version will not save an SU binary in /system/xbin.
So when you re-root your device, you will have to go into /system/bin and scroll down and copy SU. Then go into /system/xbin and paste it in there and set your permissions. Not having it in xbin sometimes causes some Root applications to not run.
I've use OTA on my Transformer for 6 updates now and restored each and every time. Granted that is for a Asus product. If worse come to worse, you could always just SBF back to stock using RSDlite (I'm an ex-Motorola user btw).
Thanks for the help! @ Woodrube
I actually just finished using OTA Rootkeeper. It restored my su back up fine. I tested it on 9 innings 2013, and i still ended up with the same results. I also tried the temp. unroot and ota survival options on superuser. Same as OTA Rootkeeper, i do intend on keeping the app for further uses. Hopefully i won't get the same result as 9 innings!
I am a better hands on learner than a read and study. I am also not ashamed of my ignorance. With that being said, what the f*ck is a SBF and RSDlite?
No need to be ashamed. Every one of us was new at one time.
An sbf file, is the Motorola file for reflashing the stock operating system to the phone. It returns the phone to the way it was brand new.
Rsd lite is the program used to flash the sbf file. It is installed to your computer, and and " installs" the software on your phone. It can be dangerous if you flash previous versions of android. Many have bricked their devices with this.
Once again, thanks! I was completely lost with Woodrube's reply. I am also fully aware of the possibilities of bricking while flashing. So flashing is something I refuse as a resolve. So all of that are things I won't attempt, to simply avoid that from occurring.
How about if I uninstalled root and replaced it with shell root. My wife has a GT-i9100 on 4.0.3, with shell root...I know the pro and con of shell root vs root. Surprisingly, she hasn't lost her root access! However, with shell root your device only has temporary root access. Will I still be able to grant su access, for apps such as lucky patcher, TB, and the many other apps used to tweak performance and settings?
Man this is burning out my mind!!!! Maybe, I'll just give it a try...won't know until I try right? On SuperOneClick, which exploit should I use though? Should I use motofail, zergrush, or gingerbreak? I am currently running 2.3.5 (on a Razr XT910, of course) which is a gingerbread, if I am correct. I used zergRush on my GT-P1000N running 2.3.4 which I'm assuming is a gingerbread too.
Also, what are ideal min. - max. values for over/underclocking my device? Where I won't sacrifice too much performance for battery life.
I used the automatic script for unlocking the bootloader, rooting, and installing cwm. I used unlock_ version 4.2.
As to overclocking, I don't anymore. The phone I am using now is a new one from Motorola to replace the one with constant reboots. I am told it was a hardware issue, but I'm not sure of it wasn't related to constant changing kernels and overclocking. I am actually satisfied with the atrix on the stock kernel and clock speed.
I haven't used the root that you are talking about, but it might be an option. Try it on your wifes phone, if you can.
Let me know, if you will. I'm interested now.
As to sbf files, no need to worry about it. I have found it to be totally safe. If you Need to get back to stock, it works. I have done it many times. Just flash the same or newer version.
Superuser
Could this not be worked around by denying root access to the game using superuser?
thanks, thanks! i bricked my xt910 changing the boot logo. at least i know not to change that from now on.
What app were you using to change the boot logo?
Rom Manager Pro....and no you can't work around by denying root access. The games are granted permission to see all apps running in background. I have tried denying such permissions with Permission Denied, whatever the name is. All it did was automatically close the game. Didn't even launch at all, immediately closed.
Sent from my XT910 using xda app-developers app
Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!
CoinCoin88 said:
Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!
Click to expand...
Click to collapse
Just to make sure you do have SuperUser, SuperSU, and I generally prefer to include BusyBox all into the mix. Also, if you would download Root Checker by Joey Krim in the Play store. Just to confirm and we know you are missing root click the verify should indicate the appropriate SU's are red and not engaged, slide to the right verify BusyBox, chances are it is green, if so you are in good condition. With Busybox in green, exit go into SuperUser and update the binaries, once that is completed go into SuperSU and click the update. Go back to Root Checker and double check, click verify root on SuperUser/SuperSU and should be green = rooted. :good:
Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)
CoinCoin88 said:
Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)
Click to expand...
Click to collapse
If the color is Red all around then yes, there is little you can do. However, there are ways to get out of this and gain root without waiting even if they have Jelly Bean 4.1.1. For instance those on JB that own the XT926 can use the Droid Razr HD Utility 1.10 > go back to ICS 4.0.4 > apply the 1st update > Root > Voodoo OTA, SU Backup > apply the JB 4.1.1 update. I have done this twice and have been quite successful on my XT926 with Verizon.
But, in general going back to the discussion. If after the update the Supers are not showing, as long as Busy Box is Green and in place, Root can be restored by updating the binaries.
If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.
tech_head said:
If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.
Click to expand...
Click to collapse
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )
CoinCoin88 said:
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )
Click to expand...
Click to collapse
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.
tech_head said:
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.
Click to expand...
Click to collapse
edit the XML ?? I'm new to RSD lite, but from what I've understood so far, edit the xml is only neededn when flashing via RSDLite/fastboot so that you don't end-up with the "unknown fastboot command" or something like that (by removing 2 lines in the fw xml file, indeed).
How is this related to going back from JB to ICS ? I'm not sure that's possible with a locked bootloader (which I'm probably not going to unlock). Also, how is my carrier related to this operation ? (the phone was SFR simlocked, but I bought an unlock code online and I'm no using it on Free Mobile)
Or did I miss something ? (btw, no mention of a JB root for the Razr HD, only for the Razr M, and it is assumed it won't work on HD because for reasons I am yet to find)
I was rooted with 4.1.2 and haven't rerooted since taking 4.3 which I had to do for work. I know the bootloader is locked forever. I'm okay with touchwiz. But, after taking NC1, I tried saferoot for the first time on 4.3 and I got hung up at "sending files to device". I looked under the covers a bit and tried to just execute the commands manually. I can shell to the phone and do stuff, but if I try the install, it just hangs. And when I looked in /data (the bat file pushes stuff to /data/local/tmp) I see nothing. I tried simply pushing the files somewhere else and that was fine, but when I tried to change the permissions, I got "Operation not permitted".
Needless to say, I'm not rooted. But it seems others get farther than this before failing, even on NC1. So my big question is whether there is something funky with my setup or with adb which is preventing these commands from working properly. My phone initially connects as an installer but then flips to a media device shortly thereafter, even though I have usb debugging enabled, etc, since I can obviously run adb and all.
Any help/insight would be greatly appreciated.
Well, it looks like, despite my different behavior, saferoot doesn't work on NC1 anyway. From what I've read, some kept root after the update and some didn't. At this point, it appears my path would be to odin back to ML1, root there, and then try the update to see if root is maintained (or ignore it).
I noticed on AT&T someone managed to come up with a modified update that could be applied using safestrap that would maintain root for sure, but I don't think that will work here and haven't seem the same for Verizon yet.
doncaruana said:
Well, it looks like, despite my different behavior, saferoot doesn't work on NC1 anyway. From what I've read, some kept root after the update and some didn't. At this point, it appears my path would be to odin back to ML1, root there, and then try the update to see if root is maintained (or ignore it).
I noticed on AT&T someone managed to come up with a modified update that could be applied using safestrap that would maintain root for sure, but I don't think that will work here and haven't seem the same for Verizon yet.
Click to expand...
Click to collapse
You should probably just ignore it unless your going to Canada any time soon. Otherwise you will most likely loose root and need to do it all over again.
People have had luck keeping root by checking the survival mode in the paid version of super su. Just thought I would let you know in case you really want to be on the update. I will be making a pre rooted odin file sometime soon. I gave my main pc to my fiance and am currently on her old crappy laptop. It wouldn't be a problem but I need to install linux before I can do it. You probably don't care but ill be buying a Clevo P150SM-A in a few months so that should fix all my computer problems for the next 6+ years (just in time to upgrade to a graphene processor!).
saferoot on NC1
doncaruana said:
Well, it looks like, despite my different behavior, saferoot doesn't work on NC1 anyway. From what I've read, some kept root after the update and some didn't. At this point, it appears my path would be to odin back to ML1, root there, and then try the update to see if root is maintained (or ignore it).
I noticed on AT&T someone managed to come up with a modified update that could be applied using safestrap that would maintain root for sure, but I don't think that will work here and haven't seem the same for Verizon yet.
Click to expand...
Click to collapse
Do you think there will ever be an update to Saferoot that will allow it to work on NC1 or is that not really possible? I have used Saferoot on earlier firmware versions and it was great how easy it worked.....??
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
If she is rooted it will break root, If she has a custom recovery (twrp) than it will cause a boot loop.
advice: if she wants lollipop she's gonna have to follow these steps.
http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
Going to pass the link on to her now.
There is no custom recovery. She used Stump Root originally to get her phone route, if that makes any difference.
martinezma99 said:
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
Click to expand...
Click to collapse
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
SGE_DEW said:
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
Click to expand...
Click to collapse
You would still lose root
2SHAYNEZ
Yep.. I went through the whole process of going completely back to stock and then rooted before updating to Lollipop hoping it would stay. It didn't and Stump Root says it's already rooted.
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Rayvin56 said:
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Click to expand...
Click to collapse
I read somewhere the LG Flashtool had to be modified at installation to avoid what you are going through.
You're right, it's just a matter of overwriting the megalock.dll file after you install the tool. It was a step I didn't miss. But good news for me, I used another pc and when I installed the flashtool it again gave me the three choices (not sure, but the title bar of the window was something like 'DMB').
This time I chose the 'global' selection and ran the tool as before and it completed for me. I'm currently DL'ing the lollipop update right now. Thanks for the quick reply, netomel.
partylikeaninjastar said:
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
Click to expand...
Click to collapse
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
hitekredneck said:
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
Click to expand...
Click to collapse
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update.
Click to expand...
Click to collapse
+1
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
Click to expand...
Click to collapse
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Lolipop upgrade
Hi iam very new on this forum . I got LGg3 AT&t version D85010f and i cannot upgrade to LOLIPOP always i have com that i have latest soft and need to wait 48h to next check ......plz help me
hitekredneck said:
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Click to expand...
Click to collapse
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Vess69 said:
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Click to expand...
Click to collapse
Call Bull**** all you want, I don't lie. To be honest, I can't even remember what method I used to root when on KitKat. Then I used TiBu to freeze a bunch of apps that I didn't want or need. Shortly thereafter the update hit me so I went ahead and let it do its thing. As stated, I did lose root afterwards but the apps I had frozen with TiBu remained frozen and everything still worked as it should. I waited patiently for a few weeks until the one click root script became available and used it to root lollipop, then installed TWRP and flashed Cloudy G3 stock ROM which is where I am happily at at this moment.
It could possibly have successfully updated due to the fact that I had not installed a custom recovery, that's the only thing I can think of that would have allowed it to happen on mine, yet not on others that were rooted.
EDIT: After reading back through this thread it jogged my memory. I used the Stump Root method to root while on KitKat.
You'd be the first person reported to be able to do this.
It would be a boon to the AT&T G3 community if you could remember the precise details of how you pulled this off as it would save loads of time and hassle for everyone else who has to restore to KK (which means a full wipe), then take the OTA to L, then root there.
Thanks in advance.
*edit
I think you're L is version 20f, not the latest 21l, based on the date of your posts above.
Further, I'd suppose that what may have happened to you, is that the deivce had already downloaded the L update (from 10f to 20f) before you pulled off the root on KitKat. Then you simply acknowledged the install, which perhaps KK would allow to continue through.
Reports are the L will not allow this. So, going forward, someone rooted on L would not be allowed to complete the install even if the package is already downloaded on the device.
Still, it is, interesting.