My prime came with 9.4.2.15.
Viper's tool work great. Rooted.
Installed OTA Rootkeeper from the market.
Let the OTA 9.4.2.21 update run.
Restored root with great success.
So those who are still locked(with warranty) should know that 9.4.2.21 update and rootkeeper seem to work.
Now... I have to give this tablet back to my girlfriend and I'm worried about loosing root with a wipe. How should I go about wiping or switching the main user account? Or should superuser and root be immune to wipe? Could I just download rootkeeper again and restore?
thanks in advance... long time android tinker-er but new to rootkeeper and locked bootloaders.
junglizste said:
My prime came with 9.4.2.15.
Viper's tool work great. Rooted.
Installed OTA Rootkeeper from the market.
Let the OTA 9.4.2.21 update run.
Restored root with great success.
So those who are still locked(with warranty) should know that 9.4.2.21 update and rootkeeper seem to work.
Now... I have to give this tablet back to my girlfriend and I'm worried about loosing root with a wipe. How should I go about wiping or switching the main user account? Or should superuser and root be immune to wipe? Could I just download rootkeeper again and restore?
thanks in advance... long time android tinker-er but new to rootkeeper and locked bootloaders.
Click to expand...
Click to collapse
I wish Rootkeeper would include the option of choosing where you put your backup..
Anyway, the wipe will eradicate any and all data on the Prime, including the SU backup that Rootkeeper creates. *Root stays intact, just not the backup.*
But, lucky for you, sparkym3 has graced us with a root app that you can keep ready to go in your ASUS WebStorage or DropBox or external mSD card, whatever you want.
But again, everything on the internal SD card will be lost when you wipe so be sure to back up your apps and their data (don't do system apps and data, restoring these usually just causes problems) to a location other than /sdcard along with any movies, music, and other personal files.
*EDIT:
Actually, no root methods currently work on .21, ASUS patched the exploit (badly I may add)
Factory reset should not touch root and you have root keeper so your good.
Blackwidowman said:
Factory reset should not touch root and you have root keeper so your good.
Click to expand...
Click to collapse
this is true as I had trouble trying to unroot on. 21 after using root keeper, as a factory data reset does not remove root
JSale said:
this is true as I had trouble trying to unroot on. 21 after using root keeper, as a factory data reset does not remove root
Click to expand...
Click to collapse
This is true. But it does remove the backup and all other files, so you need to be sure and back up as well as run Rootkeeper again after the wipe.
Why trying to unroot? You could try reverting to .15 either through an "emergency update" or with the .blob method, both of which are in my signature, then remove root and upgrade again to .21.
At this point however, you'll be at the mercy of time for the next root method; you won't be able to revert again I don't think since you won't have root.
I installed .21 and my root access was intact. I did not use OTA rootkeeper. Do I need to use it?
---
Sorry . I mixed up with HTC sensation upgrade. I used OTA rootkeeper to restore root.
Related
Hi,
I used to root the tablet successfully. But I found I did not have the root access grant this morning after consuming the power.
So I tried to root it again, but I got remount failed when executing NookandZergy.bat.
remount failed: Operation not permitted
Is there anyone could help me?
Thanks,
Kevin
its weird that you loosed root , first check if you are still on version 1.4.0, if so then try first using the unrooting script method and then root again, if not and you got the 1.4.1 upgrade silently then you will have restore stock(Go back to 1.4.0) and start from scratch, if you previously had a titanium backup of your apps then you good if not do it now and copy your titanium backup folder in to your pc.
Veronica
Thank you for your reply.
It was upgraded to 1.4.1 automatically.
Do you know how to go back to 1.4.0?
And how to prevent it upgrading?
Thanks,
Kevin
Kevin_Lu said:
Thank you for your reply.
It was upgraded to 1.4.1 automatically.
Do you know how to go back to 1.4.0?
And how to prevent it upgrading?
Thanks,
Kevin
Click to expand...
Click to collapse
Yes use this method to go back to stock, after that you probably want to use this to get 1.4.1 with root and android market (You must go back to stock to use this method is why i put it as second option) then use this method to block OTA, Indirect just released an update! as some users have reported that they are getting the upgrade with the 999 method. If you want to be even safer then freeze device manager but you will have issues with some B&N bloat apps i think, you can unfreeze anytime.
Apparently my indecisiveness with unlocking my bootloader caught up with me.
I accepted the OTA when it was announced, but at the time had no root and had not unlocked my bootloader. As of the update, I cannot get temp root by any of the cookie-cutter methods (CleanTool, ZergRush, One Click, etc). I've tried to regain temp root post-OTA, but always fails at
Code:
adb remount
remount failed: Operation not permitted
The question is - does anyone have any ideas on how I can backup my apps/settings prior to unlocking my bootloader NOW? Bettery yet - is there a modified zergRush file that will work with the 2.01.601.11 firmware?
I'm thinking I may be SOL but it never hurts to ask.
You can use MyBackup to back all that up and you don't need root. Free version is a 30 day trial.
Sorry, it is likely HTC patched the security vulnerability. It is good that they did. Those exploit based roots are bad because they are based on security holes that could be exploited maliciously. My backup would probably work well.
Okay, I'll take a look at MyBackup. Interesting that they can do the backup w/o root, must admit I'm a little skeptical.
I've only used it since having root but I like it. I use TiBU as well and AppMonster so I'm covered for sure.
The only weird thing is that I had a MyBackup backup on my ext sd card. It then had problems so I had to recover the data and then copied it back onto my card once I reformatted it and now MyBackup says it can't find my backup.
Not a big deal since I restored a nand and don't need the messages I received since that nand, but just thought I'd report that since I just recommended the app.
Unlocked, restoring everything back now.
Does this happen to backup user settings (background, widgets, WiFi, bluetooth, etc)? Always such a pain reconnecting to all the wireless networks and getting it back to the way I like it to feel.
MyBackup did a great job. Got all my apps back, all app icons but no widgets. Most system settings were not saved (WiFi and bluetooth included), so I'll have to live with that. At least it made it a 1-2 hour restore instead of starting from scratch.
We still can perm root though right?
-Sent from my Droid 2-
I'm trying that now. Supposedly those who had root but wanted to update had to re-lock, update, unlock, re-root....so I'm guessing it works.
Root achieved.
Final procedure:
Backup anything you can/want (MyBackup works for this)
Unlock bootloader using HTCDev.com (this will wipe to factory defaults)
Restore any backups
Flash AmonRa Recovery using CleanFLASH
Reboot to recovery
Install SU through "Developer Menu"
Reboot
Open Superuser app -> Preferences -> SU Binary update
Verify SU privileges through an app (Titanium Backup, Root Explorer, etc)
spitzaf said:
Root achieved.
Final procedure:
Backup anything you can/want (MyBackup works for this)
Unlock bootloader using HTCDev.com (this will wipe to factory defaults)
Restore any backups
Flash AmonRa Recovery using CleanFLASH
Reboot to recovery
Install SU through "Developer Menu"
Reboot
Open Superuser app -> Preferences -> SU Binary update
Verify SU privileges through an app (Titanium Backup, Root Explorer, etc)
Click to expand...
Click to collapse
Step 1.5 : Do the update?
If you weren't updated, yes. In my case I was starting the whole process after receiving the update, and was trying to figure out how to get root without the exploit so I could keep my data and settings.
Sent from my ADR6425LVW using XDA App
We just got the Prime and I want to root it so Titanium Backup and MyBackup Pro will work with it fully. Question is what is the best method to root it with? I prefer to avoid the Asus Tool for unlocking as that will probably void the warranty. I don't want to have to worry about other ROMS or that just the capability to run apps that require root for this Tablet.
Here ya go.. The unlock tool is also built into this as an option so make sure you just do root.
Then get voodoo root keeper from market, and have it create a backup. That way you can easily gain root access back after the OTA updates.
http://forum.xda-developers.com/showthread.php?t=1427125
regalpimpin said:
Here ya go.. The unlock tool is also built into this as an option so make sure you just do root.
Then get voodoo root keeper from market, and have it create a backup. That way you can easily gain root access back after the OTA updates.
http://forum.xda-developers.com/showthread.php?t=1427125
Click to expand...
Click to collapse
Excellent thanks.. Just what I needed especially the tip about voodoo root keeper.
With the coming update to .28 dont make the same mistake many of us did with .21. Use rootkeeper, takes a minute and saves a hassle. I've read that .28 fixed the workaround to downgrade so you really dont want to forget to use rootkeeper unless you want to go without root or unlock for a while.
nyijedi said:
Another important reminder before applying the update: If you manually removed or renamed any stock .apks to disable them, be sure to put them back before doing the update, or your Prime could be screwed up
Click to expand...
Click to collapse
Thanks, forgot that!
Just a general shoutout, dont say you werent warned!
(If you have experiences with the .28 update why not keep it in this thread? no use having a dozen threads about the same thing like we do most updates )
EDIT
felisen said:
So I have been meaning to factory reset my prime to get rid of some of the bugs from the HC to ICS update. My plan was to do it after this next update, but your post just reminded me that I would lose root when I reset. Is that correct? Any way to keep it?
Can we root the current update? I'm wondering if I should reset now and root before this upcoming update?
Any info is welcome, thanks!
Click to expand...
Click to collapse
If you want to revert to stock and KEEP ROOT do the following (worked for me, ymmv)
Download the firmware you are CURRENTLY ON (for me its .21)
Put that firmware in the ROOT DIRECTORY of your prime (not the removable SD card)
Restart your prime, it should detect that there is an update available and update you to .21 (the same FW you are on)
NOW that you are stock (all stock apps are there) you can go about reverting back to .15 (or your favorite pre-.21 update), use wolf's guide:
http://forum.xda-developers.com/showthread.php?t=1622628
Get blob file for firmware (download firmware, extract, find blob file. I used .15) MAKE SURE ITS FOR YOUR AREA (Mine is WW)
copy blob file to root dir of the prime
In shell execute: ADB Reboot
let it reboot, dont touch anything
In shell execute: dd if=/sdcard/blob of=/dev/block/mmcblk0p4
it will appear nothing is happening for 3 to 10 minutes. Mine took closer to 15 minutes. BE PATIENT THIS BIT TAKES A WHILE
when you see records in/out in how many seconds you know its done.
in shell execute: ADB Reboot
you should now have a clean, freshly installed prime on .15 Root with your flavor of root tools, use OTA rootkeeper and OTA to .21, then when the OTA to .28 is ready in your area your good to go!
Credit to wolf, go to his thread, hit the thanks button.
Hit my thanks button if i helped! Good luck and i will try to bring forward important info as it happens.
Unless of course Asus do a **** move and completely overwrite /system or rm the voodoo rootkeeper backup specifically in the update script.
Thanks for the reminder.
Maybe Demandarin tells us how he lost his root. Clumbsyness or override by Asus?
Tell us the story bro.
131313 said:
Thanks for the reminder.
Maybe Demandarin tells us how he lost his root. Clumbsyness or override by Asus?
Tell us the story bro.
Click to expand...
Click to collapse
If I had to guess it would be because he had to manually install the update from his micro-SD card. OTA Rootkeeper won't work that way.
Hi everyone
I rooted .15 and use OTA Rootkeeper and then OTA to .21.
When the .28 will be released do I have to do something with Rootkeeper or I just OTA to .28...then open Rootkeeper and recover root from .15?
Thx for answer and sorry for my english
phree1 said:
If I had to guess it would be because he had to manually install the update from his micro-SD card. OTA Rootkeeper won't work that way.
Click to expand...
Click to collapse
ouch !!
Edit:
Let's see; I am on my forth prime since early april now. Three of them on .21 and I had to update all the three via an update.zip from the micro-sd. Do I remember this? Or is it wishful thinking??
... Yeah, I did it from the micro-sd card.... Pure speculation: otarootkeeper will work... Also Demandarin mentioned that GK asked him to do whatever test on his formerly rooted device, so this implies it should still work...but then GK probably doesn't even know how to power on the prime..........................................hell.................
@
lukcinek said:
Hi everyone
I rooted .15 and use OTA Rootkeeper and then OTA to .21.
When the .28 will be released do I have to do something with Rootkeeper or I just OTA to .28...then open Rootkeeper and recover root from .15?
Thx for answer and sorry for my english
Click to expand...
Click to collapse
You shouldn't have to do anything, but to be safe, open the app and ensure that it says something along the lines of "Root backed up/protected."
Another important reminder before applying the update: If you manually removed or renamed any stock .apks to disable them, be sure to put them back before doing the update, or your Prime could be screwed up
nyijedi said:
Another important reminder before applying the update: If you manually removed or renamed any stock .apks to disable them, be sure to put them back before doing the update, or your Prime could be screwed up
Click to expand...
Click to collapse
Say what? This is true?
cam30era said:
Say what? This is true?
Click to expand...
Click to collapse
Your prime won't be screwed up, but you will be unable to load the update.
I speak from personal experience.
I have heard it looks at the 'preinstall' folder.
Where else I do not know? Help
razr maxx - stock rom
cam30era said:
Say what? This is true?
Click to expand...
Click to collapse
phree1 said:
Your prime won't be screwed up, but you will be unable to load the update.
I speak from personal experience.
Click to expand...
Click to collapse
I never made this mistake, so I can't speak from personal experience, but I thought I remember people having problems as a result of this. However, I very well may have just been thinking of being unable to load the latest update.
Regardless, you don't want to experience either of these issues
phree1 said:
Your prime won't be screwed up, but you will be unable to load the update.
I speak from personal experience.
Click to expand...
Click to collapse
Which .apk's have to be "in place" for the update load? All of the Google and Asus ones?
So I have been meaning to factory reset my prime to get rid of some of the bugs from the HC to ICS update. My plan was to do it after this next update, but your post just reminded me that I would lose root when I reset. Is that correct? Any way to keep it?
Can we root the current update? I'm wondering if I should reset now and root before this upcoming update?
Any info is welcome, thanks!
cam30era said:
Which .apk's have to be "in place" for the update load? All of the Google and Asus ones?
Click to expand...
Click to collapse
I think the simple rule of thumb is that anything that cannot be uninstalled the normal way (e.g., through the settings menu without rooting and deleting/renaming .apks) must be present.
Where is the backup file made by Root Keeper saved?
Mine is rooted and su file is saved, but will the OTA delete the restore file when installing the new fw?
Should the Ota RK file be saved on the SD Card instead?
bimbobo said:
Where is the backup file made by Root Keeper saved?
Mine is rooted and su file is saved, but will the OTA delete the restore file when installing the new fw?
Should the Ota RK file be saved on the SD Card instead?
Click to expand...
Click to collapse
You will be fine unless you choose to factory data wipe.
I saved a copy on the SD, just in case.
Appreciate the reminder. Rootkeeper looks to be in order and I think all I changed was the build.prop mod and the gps mod. I just put them back to stock so hopefully I'll be okay. Now comes the wait.
For those who forget how to revert to stock i wrote up a quick guide and posted it to OP.
Basically:
Download current FW
Install current FW
Use Wolf's guide to revert
Root
Use OTA rootkeeper
OTA to current version.
Good luck!
If I disabled some apps in app info will that be OK when updating
Or do I have to enable them all again
Sent from my Transformer Prime TF201 using Tapatalk 2
Hi,
My prime is rooted, now I want to know something about OTA Rootkeeper. I know you use it to backup your Root access, but do I use Backup root or Protect Root option. And when a new OTA update is released how do I proceeed to get my root back. Is it as simple as restore root or is thre some other stuff needed to do ?
Thanks in advance
Greamlive said:
Hi,
My prime is rooted, now I want to know something about OTA Rootkeeper. I know you use it to backup your Root access, but do I use Backup root or Protect Root option. And when a new OTA update is released how do I proceeed to get my root back. Is it as simple as restore root or is thre some other stuff needed to do ?
Thanks in advance
Click to expand...
Click to collapse
thats the way you would do it
just simply go back onto the app and press restore root
i would suggest using protect root option tho
Thanks