Long time reader first time poster! I'm not by any means an expert but I can follow directions.
I and a friend of mine bought our primes at the same time. Both of us rooted and unlocked both of us runs Virtuous Prime mod. when the .21 update came I was able to update and keep root with Voodoo OTA Rootkeeper. My friend, do not know what he was thinking , did not have rootkkeeper. He did have CWM but somehow did not have a backup rom.
Apparently He selected backup rom, and thought since it rebooted that he had made the backup, he didn’t go though the rest of the process.
So what I he has tried to do, is flash down to Virtuous .15 install rootkeeper, at which point he does have root, SU, and Su Copy available. All nice and easy.
Then flash up to Virtuous .21. Goes perfect.
After the restore however rootkeeper reports Not rooted, no root permission granted, and no SU copy available, even though he did backup .
Where did the root backup go?
Like I said I'm not an expert but I can flow directions. Why is what we are doing not working as I think it should?
PS: just a quick note of thanks to All the posters here. Like I said I've been a reader of these forums for a long time with several devices. I don’t have the time or honestly the inclination to really delve into the particulars of these devices. But I do like them to work the way I want them to, and with the help of the people here And especially Diamondback for his work on Virtuous Prime (Prime is 10X better than stock!) I've been able to get much more use out of my toys than I would have on my own!
Cheers!
I am not unlocked (yet) and was rooted with .15. Ran rootkeeper, and also lost my su-backup when I OTA upgraded to .21
I did make a copy of my su-backup, but since I'm not rooted now I cannot restore it to the /system folder.
Unlock is next.
George
Related
Okay, so I haven't as of yet seen a thread that appears to spell out this process. Most of you are talking about applying developer-modified patches to get to DI01, using Clockwork recovery, and things like that. For various reasons, some of us prefer to remain a bit closer to stock, and not worry about bricking with custom recovery software and whatnot. I'm one of those people, and I've seen questions here and there on how to go back to stock, and if root can be maintained or redone afterward, etc., so I decided to document here what I did to apply the official update to my rooted and lag-fixed Fascinate. Without further ado, here's the process I followed:
Ran the unlagfixme.bat script from http://forum.xda-developers.com/showthread.php?t=779597, which automatically reboots the phone
Used Root Explorer to remove the ".old" extension I had added to all system .apk files I considered bloatware (I chose to disable them, not delete them)
Rebooted the phone again for good measure
Downloaded the update, and let it install normally, after which root access was gone as expected (Superuser.apk and other apps that required root access were still present, but they wouldn't function)
Rooted my Fascinate again per the instructions in http://forum.xda-developers.com/showthread.php?t=779238, just like I did the first time (only had to do it once, not twice like some here have said); note that I followed all instructions except for the final one, which is installing Superuser.apk, as that application was still installed, and still worked fine after applying the proper permissions to su and busybox
Opened Root Explorer, and once again added .old to all .apk files that I wanted to disable and remove from sight
Rebooted again
Ran the lagfixme.bat from http://forum.xda-developers.com/showthread.php?t=779597 to re-apply the lag fix
Rebooted one final time to make sure everything was in still good working order
So there it is. I'm still running stock ROM, stock recovery, etc. I should be able to easily repeat this process any time there's a new OTA update, with minimal risk of bricking.
Helpful thanks, but I think I screwed up.
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
propylene22 said:
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
Click to expand...
Click to collapse
Just re-root, either through adb or there was a one-click out there.
Yeah, just re-root using the original procedure you used (except no need to reinstall superuser.apk), and you should be good to go.
Sent from my SCH-I500 using XDA App
Thanks for taking the time to write that up Ivorycruncher!
How would this process differ when the Froyo update is released, also having ClockworkMod Recovery installed instead of stock recovery?
I, like you, would like to have legitimate updates installed while keeping root.
I've never installed Clockwork, so I can't comment on that. When Froyo comes out, I imagine the process will be much the same, though at this point there's no way to know if the original rooting method will still work or not after the upgrade. Also, depending on what they do with Froyo, the lag fix may not be necessary anymore, and might not work without some tweaking even if it is still needed.
Sent from my SCH-I500 using XDA App
Okay, here is the situation: I have an Atrix (obviously) that I rooted using the Gingerbreak.exe downloaded from here http://forum.xda-developers.com/showthread.php?t=1046626. I just tried to update my phone to Gingerbread using the OTA update in About Phone and it failed; I’m assuming it is because I have rooted the device (if not please correct me and tell me what I did wrong). So I hopped onto these forums looking for a way to undo the root, or a way to get the update to work, and my eyes have glazed over. Could someone please tell me how to unroot my atrix before i use it as a hockey puck
I posted a thread very similar to this. You should look around.
http://forum.xda-developers.com/showthread.php?t=1184199
Now honestly, I have no idea why it didnt let you update, since I used SuperOneClick with Gingerbreak and it seemed to work after updating, Didn't really test out any SU apps but I still had it. To think of it, It's kinda useless for me to state that, however it states success...
One of the options for you, since you are still on Froyo and apparently rooted are to install Gingerbreak 1.2. I'm not 100% sure if it will work, but i do know it can't harm your device.
After you install Gingerbreak 1.2, you should root again, then after the reboot, reopen the app and unroot. This method should be flawless since you did re-root with the app. But again, Not 100% sure. And right now you can unlock your bootloader and just start loading if you'd like. That is a much easier and safer way to do it. Plenty of tuts on Android Dev forum here.
lol don't worry about unrooting. I'll tell you that much.
It's not so much of a problem with root, but moreso the pre-test that accompanies the OTA. If you fail it because you use Titanium to clear out bloatware and stuff like that. even if you remove root, you still won't be able to upgrade. Instead, just use this method.
Just download the Automated Upgrade for PC Users and let your phone upgrade. All your data should still be there, but backup before just in case. Oh, and if you wanna root again after you upgrade (cause i mean, why WOULDN'T you want root?!), just use the preinstall method (hehe I'll leave this for you to search. it'll be good practice for the future, i promise =])
happy upgrading!
~jojojohnson7410~
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
Regain root access after JB update
weakenfalls said:
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
Click to expand...
Click to collapse
I lost root on my TF201 after flashing Craig Gomez's us-tf201-jro03c-10.4.2.15-stock-deodexed.zip ROM. In addition to losing root access, I still had Superuser installed, and it would not grant superuser permission to anything I was trying to use to fix the problem, such as Voodoo OTA Rootkeeper, GooManager, etc. Also, Superuser did not even have superuser permission, but could not be deleted in the File Manager. Another big problem is that I could not boot into recovery, and I could not downgrade to ICS.
After trying a number of possible solutions that I found on this and other sites, I discovered Urkel's Fresh Start 1.0.zip. Here's the post:
<http://forum.xda-developers.com/showthread.php?p=32677560>
If you are at a dead end, I highly recommend that you give this a try! Your bootloader needs to be unlocked, but I had already done that when I was still using ICS. I'm not sure if the unlock tool available on the Asus site will work with JB. All you have to do is download the Urkel's Fresh Start zip file to your computer, unzip it to the same folder on your computer where you have adb and fastboot, add the JB ROM that you want to use to that folder, and rename the ROM file to system.blob. You'll also need to install the drivers on your computer so that it can send data to your TF201. I used the drivers that are on the Microsoft site, but there is a link to some universal drivers in the post above. Connect the cable from your TF201 to a USB port on your computer, and after deciding which option you want to try, double click Fresh Root.bat or Fresh Start.bat. Fresh Start.bat will first install the TWRP 2.2.2.1 recovery (that's what recovery.blob is). It will then install whatever JB ROM you decided to use. I went with the 10.4.2.15 ROM that's now on the ASUS site. The Urkel batch file may then restore root access, but that didn't work for some reason in my case. I think my problem was not mounting \System. You can do this by booting into TWRP recovery that you now have, select the Mount button, and put an X in the top box. In my case it seems that the box becomes unchecked during reboot. I tried it several times and gave up, but there is another simple way to regain root access if you have made it this far. Download Superuser-3.2-arm-signed.zip and flash that using TWRP, and you will at long last have root access once again. I see that this file has already been mentioned in this thread, and it worked like a charm for me.
So why did I want root access to being with? It's because of that stupid GPS problem. GPS isn't really needed on a pad in my opinion, but things like that bug me (pardon the pun)! When I was still using ICS, I unlocked the bootloader, rooted, and then used GooManager to flash TF201_External_GPS.zip. This file allowed the GPS function in my TF201 to work just as well as the GPS in my Samsung Galaxy S2. Also, I see no change when I attach the GPS dongle. What does that tell you? I think for most people with the GPS problem, it's a FIRMWARE problem, not a hardware problem. I'm not having a wifi problem, but I suspect that this is also a firmware problem. If Asus is smart, they have someone reading these blogs to get some ideas on how to fix their problems. Instead, they've spent money sending people a GPS dongle that, at least in some cases, is just a waste of time and money. So I've reinstalled the GPS zip file, and my GPS works...so now Google Maps can tell me where I am. Thanks, I already know that most of the time. Another thing that seemed to help with the GPS problem...disable the stock browser and use the Dolphin browser instead. I have no idea why that should make a difference.
Since I am a noob (whatever man), I tried to spell this out so that it can be easily understood by other noobs. Good luck, hope this works for you.
weakenfalls said:
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
Click to expand...
Click to collapse
Read this thread : http://forum.xda-developers.com/showthread.php?t=1911261 . It gives you two ways to try and get su/root back and working properly.
Intro: I'm on the official Jelly Bean update, and by updating lost the root I had on ICS. I was one of the unfortunate users that backed up with an older version of Voodoo OTA RootKeeper, before the program updated to account for the JB changes, so my root got wiped even though it was backed up. Well I'm tired of sitting around waiting for exploits, and I treat my tablet with care anyways, so I figure it's finally time to take the plunge and unlock so I can root the thing, right?
Plan: According to this thread, I should run the unlock tool and then flash TWRP, after that I'll be free to flash custom updates and/or replace the whole OS/ROM.
Question: Do I really need to change ROMs in order to root? I've read vague mentions of flashing a zip with the su executable and such, if that works for an unlocked TF201 with the stock JB ROM, that'd save me a lot of trouble of backing up my apps and all that jazz. Does anybody have any info on this?
EDIT: Okay, it seems I can't do it right now. I'm currently getting network access via bluetooth tethering (pdanet app), but the unlock tool seems to explicitly demand wifi, as it tells me there's no network connection available even when I can browse just fine in the browsers and such... so this will have to wait until I can access some wifi.
I got a notice today saying that my nook needs to be updated. Apparently they are forcing TLS 1.2 and a firmware update is needed to do so. Being the update file is 278mb this is the whole ROM not just the TLS update (v1.4.4 now).
Anyone installed this and will the old rooting tools still work? I am 98% certain they won't as B&N has always tried to block such access. Is anyone still around willing to update the tools? Or even have devices to do so?
I personally still like my NT, and it does all I need from a tablet at the moment (once I rooted it and installed a different launcher that is). I *think* I disabled OTA back when I rooted, but I am not 100% certain on that. Is there a easy way to check?
I have thought about doing other ROM's but never got around to it since this still meets my needs (reading, and a couple of simple games, and email/newsfeeds).
Updated, rooted using old tools for 1.4.3, flashed nougat, works fine.
Oh COOL. I guess they didn't bother changing anything more than the TLS. Glad to see. Now I just need to dig up my old microSD and get this done lol.
Probably will do a nandroid backup beforehand just to be safe. I have a lot of customizations I don't want to lose lol.