root keeper andfactory default - Thinkpad Tablet General

HI
don't know if anyone cares or has tried it or not, but i just rooted our spare tpt and then got root keeper to do a backup, i then did a foctory restore with ota2 installed.
quick reinstall of super user and rootkeepr got me my root access back
i didn't know if a factory reset would keep root or not, but since sometimes a factory reset is the only way it's handy to know you want loose root.
cheers
Tom

factory reset didn't delete root, I do it always (but I don't have OTA2 yet)

factory reset won't delete root, because it will only delete data, cache and i think sdcard partition. root is on system partition, so why should it dissapear?
OTA2 deletes /system/app/superuser.apk and /system/xbin. that's the reason why you lose root when updating. rootkeeper protects su file from /system/xbin by making a backup copy to /system named su-backup. superuser.apk can also be downloaded in the market. so you can restore root

Anyone try this on the K1? As far as using the app to regain root after updating to say the 14_14 update?

I only put this up because I know there are people out there like me that would not be sure if you could do this or not and are much happier when they find someone that has already done it.
Just hope that this will put someones mind at ease.
Tom
Sent from my ThinkPad Tablet using Tapatalk

Dueces99 said:
Anyone try this on the K1? As far as using the app to regain root after updating to say the 14_14 update?
Click to expand...
Click to collapse
It should work for all Honeycomb Tablets with update.zip-style OTA's

camou23 said:
It should work for all Honeycomb Tablets with update.zip-style OTA's
Click to expand...
Click to collapse
Any possible confirmation on this? Just having issues atm with recognizing my K1 through ADB, otherwise I would be using timmyDean's approach with a backdoor. If this app will keep root successfully, I'm surprised it isnt getting more attention.
Robert

If RootKeeper fails after OTA2, you still have root - only a little cp, chmod etc and all is done.

JA.de said:
If RootKeeper fails after OTA2, you still have root - only a little cp, chmod etc and all is done.
Click to expand...
Click to collapse
Care to elaborate? RootKeeper failed for me:
http://forum.xda-developers.com/showpost.php?p=22640567&postcount=7

Related

Gearing up for some Gingerbread cookies...

saw some articles about this but they weren't this specific...
so I have a Nexus One 2.2.1 stock, rooted with rageagainstthecage thing...
will my phone update to 2.3 as-is, or will I have to unroot the rageagainstthecage method first?
from 2.2 to 2.2.1 I had to uninstall Universal Androot (useless anyways) and reinstall some missing APKs that I had deleted (Amazon MP3 and GenieWidget)
Don't quote me on that, but I'm pretty sure that you will not get OTA automatically. However, as soon as it's out, it will be posted here and you can flash it manually. You will loose root though.
thanks, I hope you're right. Losing root is no biggie (hopefully a nice easy root method will come up shortly)
If anything it will be here before you get the OTA anyway.
Atleast that's what happened with Froyo.
Someone will logcat the address then DL it, then it will get mirrored all over XDA
Once it's here on XDA the flashing will begin long before the OTA arrives
question
I had CM6.1 Nightlies on my N1 with Clockwork, now I went back to stock recovery, stock FRG83 and I have my bootloader unlocked.
I'm wondering if the OTA will come automaticaly (probably gonna install the "XDA" version before OTA even starts going around)?
And I'm wondering if anybody knows what is supposed to be the criteria for the OTA to come automaticaly?
I was rooted with 2.2 and got the OTA for 2.2.1.
As far as I know you need a stock rom (rooted or otherwise) with a locked bootloader.
Sent from my Nexus One using XDA App
are you certain about the locked bootloader?
Its kinda pointless to go back to stock and such if you like the CM nightlies, its what I run, because the first phones to receive the OTA will be the "Holiday" Nexus one, based on imei. It will be up on xda with many mirorrs and versions shortly after! If you remener froyo it will be like that. So just look here for the update.zip
Just my two cents
Sent from my Nexus One using XDA App
Yeah I know I was just wondering about the update process, requirements, etc.
I love CM6.1, I'll probably go back to it when I'm fed up with Ginger there was another reason to go back to stock and that's that I still had ere27 stock backup and it was time to update the stock ROM to frg83 and back that up for the future
It doesn't matter if you have an unlocked bootloader or not, nor does it matter if you have rooted. You must have a stock recovery as the ota will use it to install, if it doesn't find it the installation will fail. Previous updates were available here for rooted users before the update went ota
i also was rooted but had a stock bootloader and recovery... got the 2.2.1 OTA. lost root though.
now for my question... i dont care if i lose root for gingerbread but since i rooted.. SU is in my rom and i cant delete it. i just dont want something on my phone that i cant use.
will the gingerbread update bring me to full stock gingerbread? or would SU be still stuck there. just asking since i rooted after i got froyo so im not sure.
If memory serves, with an OTA su will be removed, but Superuser.apk will remain.
Anyways, if you try this app, you should be able to regain root with ease, even if it's only to bin the files you don't want.
Rusty! said:
If memory serves, with an OTA su will be removed, but Superuser.apk will remain.
Anyways, if you try this app, you should be able to regain root with ease, even if it's only to bin the files you don't want.
Click to expand...
Click to collapse
yeah i got root back because of that app! my main grip was superuser.apk was still in the phone without SU access. now im back to rooted i just left it there.
so basically if i get gingerbread and lose root superuser.apk will still be left in the phone? any thoughts? if so ill just delete it then install it back somewhere i could delete it if i lose root again.
I believe so, yes.
Bin it before updating to be 'safe', I guess.
Rusty! said:
I believe so, yes.
Bin it before updating to be 'safe', I guess.
Click to expand...
Click to collapse
is there an easy way to do it... say just delete it via astro file manager? this is the tutorial i used to root in the first place..
http://forum.xda-developers.com/showthread.php?t=736271
.. lost root then i used the "one click root" that first appeared in the market, then lost root again after 2.2.1 then used visionary.
theres a lot more in the phone that was put in there by rooting (like busybox right?)... but i guess superuser.apk is the visible one since it shows on the app drawer so i wanna remove it from the phone and just install it via the market.
ASTRO can't do it as far as I'm aware, but it's easy from ADB shell or a terminal:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
rm /system/bin/su
rm /system/app/Superuser.apk
rm /system/bin/busybox
and it's goodbye root (and busybox since you mentioned it).
Rusty! said:
ASTRO can't do it as far as I'm aware, but it's easy from ADB shell or a terminal:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
rm /system/bin/su
rm /system/app/Superuser.apk
rm /system/bin/busybox
and it's goodbye root (and busybox since you mentioned it).
Click to expand...
Click to collapse
thanks will give it some thought
krabman said:
It doesn't matter if you have an unlocked bootloader or not, nor does it matter if you have rooted. You must have a stock recovery as the ota will use it to install, if it doesn't find it the installation will fail. Previous updates were available here for rooted users before the update went ota
Click to expand...
Click to collapse
I think that the latest Amon RA will flash an update, regardless of signature verification.
GldRush98 said:
I think that the latest Amon RA will flash an update, regardless of signature verification.
Click to expand...
Click to collapse
You're right, same as the latest ClockworkMod recovery...they disable signature check

Lost root on as I updated to 2.3.4 on my Nexus S

After getting assert_failed errors since forever on 2.3.2, I finally downgraded my radio to fix them and without even thinking installed 2.3.4 OTA. The install went fine but I lost my root.
Now, I haven't unlocked my bootloader. To root, I have to unlock the bootloader which will wipe my phone clean. To take a nandroid/full backup of phone I need root. So, kinda stuck in a catch-22 here.
I still have ROM Manager installed and when I used backup feature in it, it created a new backup. However I am not sure if its a full phone backup or just the ROM. Is there anyway to verify?
Also, any solution to gain my root back with all my data? I am fine with unlocking the bootloader as long as my data is safe.
Edit:
This just struck my mind. If I modify the update file and put in su binaries repackage it and reinstall it on my phone, would it work? Can I even reinstall an update?
Edit2:
Can I just create my own update.zip containing su binaries, sign it and install it?
dpacmittal said:
Edit2:
Can I just create my own update.zip containing su binaries, sign it and install it?
Click to expand...
Click to collapse
You can create it, of course, but I doubt you could install it with a locked bootloader, since you are unlikely to have the private key google uses to sign its updates.
How much can I back-up without rooting my phone? I'll backup the SD partition. I just want all my application settings (eg; Angry birds data) with all the applications, messages and contacts. Is it possible to back all these up without root?
I have titanium installed, if its any good?
[Guide] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).
I hope this will able to help you
http://forum.xda-developers.com/showthread.php?p=13800735#post13800735
My bootloader is locked, mate. Your method won't work for me. Thanks, anyways

Root problem after restore

I restored my Iconia to a previous backup after trying a rom that I decided I didn't like. My root now doesn't work. Superuser is installed but most app say superuser is not available. I tried re-rooting with Iconia Root and it said it worked but nothing changes. What's going on?
antisomnic said:
I restored my Iconia to a previous backup after trying a rom that I decided I didn't like. My root now doesn't work. Superuser is installed but most app say superuser is not available. I tried re-rooting with Iconia Root and it said it worked but nothing changes. What's going on?
Click to expand...
Click to collapse
That is a bug in cwm restore, had the exact same problem. Someone said deleate android secure image from your backup set before you restore, did not work for me. I'm sure someone knows how to do it. I just have not tried lately. But you do want to delete the above file so the restore installs flexrom. Later.
Disclaimer: I'm no expert on root....
My suggestion would be to try to use the root application to unroot first, then try again, failing that, re-install the rom and try again. it is probably getting confused because the SU binary exists even though it doesn't work, so you probably need to get rid of SU before you re-root.
same problem for me after full restore. My solution is reintall orginal custom room without wipe and SU will work fine. Just take some time but it works for me. Tried on hollivian and lightspeed room.

No more Root!!!! eek!!!

Well guys this is what I did... OTA Voodoo did not work to unroot for... me so I started from scratch... At 403 9.x.x17 with NVFlash that I have Lucky me with B50... then took the new OTA update ICS update v9.2.1.21......Butttt Now when pressing the Volume Down and power and then press up it goes into Asus Recovery.. but with the android lying down with an ! over him...ViperMod does not see the the tablet at all...Sooooo Now I guess it's a waiting game to root again..
The Android with ! Is your stock recovery. It doesn't do anything except handle official update file.
I would just nvflash to .17 root it and wait for a cwm version of the new.21. Usually a day or two most till a dev make a cwm version.
Thanks Base I can wait not going back... Just thought I was doing something wrong
really
Yea.. I just killed my DMclient so no Asus update notification harrassing me around..
Will wait for the CWM update for v9.2.1.21 to come.. It's the safer way to update when we have CWM installed and running under v9.2.1.17 at the moment..
what about flashing .17, root it, install ota rootkeeper, update and recover root?
just don't flash a custom recovery before updating via OTA
oifi said:
what about flashing .17, root it, install ota rootkeeper, update and recover root?
just don't flash a custom recovery before updating via OTA
Click to expand...
Click to collapse
Did you try what your saying... and did it work ???
JohnM109R said:
Did you try what your saying... and did it work ???
Click to expand...
Click to collapse
There's a lot of peoples in the "firmware update" thread reporting that it work.
baseballfanz said:
There's a lot of peoples in the "firmware update" thread reporting that it work.
Click to expand...
Click to collapse
Well I got it going as the above said....But after restoring root from Voodoo..that was ok but when I got to install gnufabio one click RecoveryInstaller it says i'm not rooted but I am...Now what LOL ?
Everything is working fine so far the only thing that bugs me is no CWR....
JohnM109R said:
Well I got it going as the above said....But after restoring root from Voodoo..that was ok but when I got to install gnufabio one click RecoveryInstaller it says i'm not rooted but I am...Now what LOL ?
Everything is working fine so far the only thing that bugs me is no CWR....
Click to expand...
Click to collapse
Try this, look in system/xbin to see if you have an su there. If not look in system/bin and copy the su from there and paste it to system/xbin
Yessss thats what was missing.... Thanks So Now I can confirm that this procedure works Great Thanks... Baseballfanz and oifi..
JohnM109R said:
Yessss thats what was missing.... Thanks So Now I can confirm that this procedure works Great Thanks... Baseballfanz and oifi..
Click to expand...
Click to collapse
Ok, would you be able to guide me through the same? I have the same problem. No recovery and no root after .21 update.
I checked my system/xbin and I have su in there. Also in system/bin. I tried using root explorer to copy it over anyways, but can't mount R/W.
Any other ideas?
oifi said:
what about flashing .17, root it, install ota rootkeeper, update and recover root?
just don't flash a custom recovery before updating via OTA
Click to expand...
Click to collapse
The is worked for me! Thanks
Gr8Danes said:
Ok, would you be able to guide me through the same? I have the same problem. No recovery and no root after .21 update.
I checked my system/xbin and I have su in there. Also in system/bin. I tried using root explorer to copy it over anyways, but can't mount R/W.
Any other ideas?
Click to expand...
Click to collapse
Nevermind

[ROOT] 23.0.1.A.0.167 [LOCKED BL] No recovery needed

Hello,
I just wanted to share how I have rooted my device today, and it was way easier than the methods I have been reading about so far.
My device: Xperia Z2 , C6543.
How I did it:
1- I updated my flashtool to the latest version, downloaded the 7.1.2.A.0.314 ftf for my region and flashed like instructed in the post. (Note that If you don't have flashtool installed, you have to go inside it's drivers folder and install the Z2 driver so it can communicate to the phone).
http://forum.xda-developers.com/showthread.php?t=2759934
2- After the downgrade to the 7.1.2.A.0.314 version mentioned above, I went to the flashtool menu (My 65XX -> Root -> Force towelroot)
When prompted to, I have choosen the SuperSU option.
Then the towelroot app showed in the phone's screen, I've tapped on "make it rain" and let it run.
After that the phone restarted and it was rooted.
3. Okay, now that the 7.1.2.A.0.314 is rooted, an OTA update notification showed up to update to the same version (lol). Well, I just let it update, and the root was there (I confirmed by restoring some data in titanium backup).
4. After that, another OTA update showed up to update to 23.0.1.A.0.167. Again, I let it download and install.
Well, that's what it took for me to root my z2 in it's latest version with only one downgrade and no manual adb commands, no manual rootkit downloads, pretty similar to the way I've always rooted my ZQ (R.I.P - it drowned lol).
The credits are due to the hard-working people who made all the mentioned tools, I am only doing my part by sharing an easier method than what i've seen around. Feel free to share your toughts.
Laters!
Sorry to be noob! Will it break anything like camera x reality or anything? And for warranty, can I claim it by just unrooting it(it's in the su) ?
Did not break anything for me. Now I can use foldermount and transfer heavy apps to the external sd. Wonderful. As for the warranty, since there is no recovery installed and no bootloader unlocked, it is as easy as doing the step 1 in the procedure described. It will flash the unrooted system back.
But ist same method, if u use this or this tool.
This post doesnt deserve an original development section!
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
But ist same method, if u use this or this tool.
Click to expand...
Click to collapse
I am not sure I understand what you mean, but if you are talking about the xperiarootkit compared to the "force towelroot" from flashtool, I checked the scripts in advance and they seem to be the same thing yes. The only shortcut to what I did was not having to flash recovery, and creating customized ftf, etc.
This post doesnt deserve an original development section!
Click to expand...
Click to collapse
I am sorry you feel that way man, that comment was a great way to add value to the conversation, thank you.
remydlc said:
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
Click to expand...
Click to collapse
Did you tried ota survival in Supersu?
rjshrjndrn said:
Did you tried ota survival in Supersu?
Click to expand...
Click to collapse
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
remydlc said:
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
Click to expand...
Click to collapse
I think you have to do all the stuff one again and root device. Then check the option for its root survival and do ota updates. I think you'll be fine with the updates.
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Moscow Desire said:
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Click to expand...
Click to collapse
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
root achieved and kept
Nice one thanks for the info worked well and updated to .167 ota and kept root.
Going to give this a try. Thanks
Thanks for the info, OP.
I used flashtool to downgrade my D6503 to .55, tried to use towelroot, no luck. used the CVE root exploit and got root, but after that update center failed the verification to .314.
Your method works, so cheers!
Will the Phone be wiped during this root method
ecolupo said:
Will the Phone be wiped during this root method
Click to expand...
Click to collapse
flashtool will wipe your phone unless you unselect data partition (not recommended). The rooting part is non-destructive so no that part won't your phone.
ptmaniac said:
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
Click to expand...
Click to collapse
Tried to install nut's recovery with supersu option but all the apks in the script could not be written into system folder. Also could not install xposed installer. May have to downgrade again and avoid this method
update: no need to downgrade again. sony_ric prevents r/w to system folder even with root, so I just used ric killer by forty two: http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141
afterward I was able to install xposed installer via normal method.
Thank you for the tutorial. It worked fine for me.
What will happen if I do a factory reset via settings-menu? Will root be gone? Do I have to downgrade again or can I install SuperSU to get root back?
Sent from my D6503 using XDA Free mobile app

Categories

Resources