Hello guys! the instructions are very easy if you do the steps correctly.
This is my first post in the development section.
First, go to market and download OTA Rootkeeper
Second, open the app, Select Create SU Backup.
Third, Select Temp UnRoot(with backup)
Fourth, uninstall Superuser, if you have superuser elite uninstall it also! and uninstall OTA Rootkeeper(dont worry it will not delete UR Backup!)
Fifth, Download and install the OTA.
After it is done and reboot, do a power cycle.
and the last step, go to market, install superuser and ota rootkeeper.
Launch OTA Rootkeeper and Select RestoreRoot, accept the superuser permission, and reboot!
AND ur back with rooted 2.3.6!
Michael
Alternate method! This is Jim's method(Thanks jim for this other way)
To do the 4ever root hack do the following:
1) open root explorer or ew file manager etc...
go to /system/bin
find the file named mount_ext3.sh
touch and hold the file name until the menu appears, go to open in text editor.
Add the following line to the VERY bottom of the file, after the fi
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
2) SAVE!!!! the file.
3) Do the OTA update.
4) You should still have root after the update, now.
Jim
Enjoy, Hope this helps!
I missed step 3 and 4 this is why it did not work for me
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
I don't know but as soon as I get home I'm going to check and see... Just got another A2 today, its going to be a good lil Guinea Pig... (insert evil grin here)
Sent from my MB865 using XDA App
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 644 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root. but if you did not do the update maually, and you used the one-click you might need to add the following line as well....
chmod 4755 /system/xbin/su
Jim
Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
cant tell you, i didnt had a custom rom on it while i tried but if i am correct the update will work with stock only. wait till Iggis Pop do the test before attempting.
I just used OTA Rootkeeper normally and it worked fine for me. Backed up root, temp un-rooted, downloaded and applied the update, then restored root from OTA Rootkeeper after the update finished. I have root back just fine...
Did this not work for others?
I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.
tmease1 said:
I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
can you tell me step by step what ou did so i can help you!
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
Michael443 said:
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root
Click to expand...
Click to collapse
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.
09CarreraS said:
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.
Click to expand...
Click to collapse
I'm not Jim but I do have the answers to your questions!
You should flash the fkz's (sbf) files before you update, just a good idea to remove any oddities or potential problems. Also most modifications do relay on a deodexed ROM , so my guess is that it won't work with the new update yet. My personal recommendation would be to wait until lfaber06 incorperates this update into a nice little cwm flashable zip (around this weekend, or next), that will already contain root, as well as the 1 percent mod and the updated theming!
Thanks for the answer! Hey I'm from Ma as well.
well that's what i get for not reading here first. My coworker was demo-ing an app to our CEO and the update notification came in. A few minutes later he comes back and says he hit download then install when it came up. When i got it it was flashing in recovery already
extide said:
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.
Click to expand...
Click to collapse
Well, this definitely bricked my phone.
toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
Are you sure you followed the instructions and put the files in the right directory? I havn't had any problems using this exact method as for a few others.
No way if it was done correctly that it bricked your phone.correctly can be accomplished by navigating to the proper file then copy pasting the code in order.the only thing you are modifying is superuser.
toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.
extide said:
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.
Click to expand...
Click to collapse
Not sure, I just pasted those two lines under "fi" or whatever was on the last line. Checked it. Saved it. Rebooted. Boot loop.
Related
Update: I'd recommend using the full update found here instead - it's less likely to fail than this one based on the patch update.
I've managed to build a working RC30 update that retains root via adb shell. Much of the credit goes to the people in this thread. All I did was build an updated boot.img with ro.secure set to 0, and reinsert it into the RC30 update.
Installing it will require the modded RC29 recovery image found in that thread.
A warning: if you've modified any files that are patched in the RC30 update, bad things will happen. Also, I had to disable the version check, so if you attempt to apply the update to anything but RC29, bad things will happen. I'm not responsible if your phone is bricked, bursts into flames, or even starts walking around on it's own and attacks you.
Modified RC30 update
did you have any trouble installing it? I will give it a try later today.
1 question, so theres no root on the phone Only by adb?
Edit:2 questions have you try to put busybox on?
It worked fine for me. Just follow the manual firmware update procedure, and it should work, as long as you're already running the modified RC29.
humble said:
1 question, so theres no root on the phone Only by adb?
Click to expand...
Click to collapse
Yeah, it closes the root console bug. However, once you have root via adb, you can do pretty much anything you want, including create a new suid root shell.
yes thats all i need to know disregard my edit
it dose not work I'm stuck! i got some sort of error
It won't let me mount the SD card... gonna ask in the other thread
What was the error exactly? Did it come at the recovery screen when you first tried to update, or later? Is your phone still working?
rale00 said:
What was the error exactly? Did it come at the recovery screen when you first tried to update, or later? Is your phone still working?
Click to expand...
Click to collapse
Thanks for asking the error was 105, yes later, and yes
and this is what i did
THANK GOD!! for JesusFreke Restore Original RC29 Boot Image.zip. if what happened to me happens to anyone just rename that file up above to update and your golden.
Note: i used it and now i have
kila-user 1.0 TC4-RC30 116143
ota-rel-keys,release-keys
i dont understand... and i sill have root on my phone and busybox, and telnetd exploit still works
maybe i should try it again?
It sounds like the update partially completed for you, since it claims to be RC30, but it failed either sometime before or during the flash of the updated boot.img. boot.img has the fix for the telnetd exploit, which is why it's still working for you after restoring the RC29 version.
If you try to run the RC30 update again, it will probably fail, since some or all of your other files are already updated.
The bad news is, you probably won't be able to install any future updates with the state you're in now. What you probably want to do now is try to figure out how far along in the update script it failed.
If you can download the following files off your phone, and post them somewhere, I'll compare them to the versions in a completely updated RC30 and should be able to get a better idea of where you are.
/system/framework/android.awt.jar
/system/app/GoogleSearch.apk
/system/app/Bugreport.apk
What good thing i made a backup of my flash i am going to see if i can restore it using this methodhttp://forum.xda-developers.com/showthread.php?t=442831
but witch partitions should i flash? and is it a good idea
rale00 said:
/system/framework/android.awt.jar
/system/app/GoogleSearch.apk
/system/app/Bugreport.apk
Click to expand...
Click to collapse
how do i get them to the sdcard? i will post them
I can get root through adb shell after this, which is fantastic!
So I try this from adb shell:
cd /system/bin
echo sh > su
chmod 4755 su
But when I run su from the phone's terminal, I don't get a root shell. (reboot gives me a reboot: Operation not permitted.
Any ideas?
humble said:
What good thing i made a backup of my flash i am going to see if i can restore it using this methodhttp://forum.xda-developers.com/showthread.php?t=442831
but witch partitions should i flash? and is it a good idea
Click to expand...
Click to collapse
Oh, that's good news. If you have a backup of mtd3 / "system", then you should be able to just restore that and be in good shape.
rale00 said:
Oh, that's good news. If you have a backup of mtd3 / "system", then you should be able to just restore that and be in good shape.
Click to expand...
Click to collapse
thanks, but i wanna help out with those files. and do you know the exact commands to copy(i know cp and"???? ") and to restore mtd3
SORRY........
to restore is this right....
cat /dev/zero >> /dev/mtd/mtd3
flash_system /sdcard/mtd3.img
To copy them to sd card:
cat /system/framework/android.awt.jar > /sdcard/android.awt.jar
cat /system/app/GoogleSearch.apk > /sdcard/GoogleSearch.apk
cat /system/app/Bugreport.apk > /sdcard/Bugreport.apk
I haven't tried this, so I don't know if it works, but to restore system, if you backed it up using the directions in the other thread, should just be:
flash_image system /sdcard/mtd3.img
I wouldn't recommend cat /dev/zero to it first, because flash_image is actually on the system partition.
rale00 said:
To copy them to sd card:
cat /system/framework/android.awt.jar > /sdcard/android.awt.jar
cat /system/app/GoogleSearch.apk > /sdcard/GoogleSearch.apk
cat /system/app/Bugreport.apk > /sdcard/Bugreport.apk
I haven't tried this, so I don't know if it works, but to restore system, if you backed it up using the directions in the other thread, should just be:
flash_image system /sdcard/mtd3.img
Click to expand...
Click to collapse
Thanks rale00, when im finish if it works i'l post
but where the fugg is "su".
I pushed superuser.apk no prblem but were is this extensionless su app??
Reason:
I rooted my gf's hero and need to run titanium to backup all her apps before I flash Fresh 2.1.2 to it. After lots of searching I se I need to put SU on it. Can soeone shed some light...?
scirio said:
but where the fugg is "su".
I pushed superuser.apk no prblem but were is this extensionless su app??
Reason:
I rooted my gf's hero and need to run titanium to backup all her apps before I flash Fresh 2.1.2 to it. After lots of searching I se I need to put SU on it. Can soeone shed some light...?
Click to expand...
Click to collapse
hmm.. you could just use another backup program that doesnt need root. i personally use astro to back up my apps.
assuming that just pushing superuser.apk works, then you should get a prompt when you try to use titanium back up that asks for root access.
su should be in /system/bin and I believe /system/xbin. I had to cp su /system/xbin for Metamorph to work a while ago...
Code:
adb shell
cd /system/bin
ls
see if su is in this folder. if it is then
Code:
cp su /system/xbin
But wait till someone else confirms this...
Also, if you are getting the black super user request screen make sure that you have USB Debugging turned on. Settings>Applications>Development>USB Debugging Mode
"su" is not an app.. "su" is command for "super user"..
"su" is root access.. If the rom you are using is not rooted it will never have "su".. Because the rom will not allow sudo access
*search for appsaver to get the apps from an unrooted rom..
azyouthinkeyeiz said:
"su" is not an app..
"su" is root access.. If the rom you are using is not rooted it will never have "su"..
Click to expand...
Click to collapse
Have to kind of disagree with you here.
he is refering to the SU file that lives in //bin/
Which is technically "executable" when setting suid bits.
But you are correct in that the rom should have that. And if it doesn't...she's not rooted...and you'll need more than just SU eventually...you should go ahead and get busy box installed for TIbackup to use.
Kcarpenter said:
Have to kind of disagree with you here.
he is refering to the SU file that lives in //bin/
Which is technically "executable" when setting suid bits.
But you are correct in that the rom should have that. And if it doesn't...she's not rooted...and you'll need more than just SU eventually...you should go ahead and get busy box installed for TIbackup to use.
Click to expand...
Click to collapse
The su file that lives in //bin/ allows the rom to interact with busybox and supermissions.. It is not an APP just a directory file.. That's like saying on a PC that the DLL files for each program is a program.. It does "execute" but there is not a single file on your computer that isn't "executable" in someway.. I was just saying in layman's terms that he can't do what he wants..
You can't just install that on a Sprint Rom.. He cannot just push busybox into his rom because it is lacking the su file.. And it cannot interact with the Sprint Rom even if you did get it installed somehow...
Yes he rooted the phone, but the ROM is still locked in by sprint until you flash a custom rom.. You have to repackage the rom and reflash it to get those parts into the rom.. Which would not help this guy with what he wants..
*again.. Search for appsaver.. it is the easiest solution for you OP
azyouthinkeyeiz said:
The su file that lives in //bin/ allows the rom to interact with busybox and supermissions.. It is not an APP just a directory file.. That's like saying on a PC that the DLL files for each program is a program.. It does "execute" but there is not a single file on your computer that isn't "executable" in someway.. I was just saying in layman's terms that he can't do what he wants..
You can't just install that on a Sprint Rom.. He cannot just push busybox into his rom because it is lacking the su file.. And it cannot interact with the Sprint Rom even if you did get it installed somehow...
Yes he rooted the phone, but the ROM is still locked in by sprint until you flash a custom rom.. You have to repackage the rom and reflash it to get those parts into the rom.. Which would not help this guy with what he wants..
*again.. Search for appsaver.. it is the easiest solution for you OP
Click to expand...
Click to collapse
I knew it wasn't an "app" but I also figured you guys were smart enough not to hassle me about symantics
Ended up just flashing Fresh 2.1.2 and to hell with her apps.
scirio said:
to hell with her apps.
Click to expand...
Click to collapse
I tell ya what, every time I wipe my wifes phone and wipe out that "My Days" app. She wants to kill me. You'd think she has that schedule memorized...lord knows I do.
I rooted my Htc nexus one, droid, droid X, and the htc evo. I just bought the mt4g. Im good at procedures. I cant unlock the S off. Ive done every single. way visonary, gfree, emulator, and adb. and even tired some guyz zip. for some reason. I cant now root this freaking phone. Ive tired multiple times and nada. Is there anything out there that works. I even tired the root explorer. nothing. did they put a different lock on this phone. i got it a week ago and nothing. HELP any one ?
My wife's MT4G arrived last weekend, and I rooted it with s-off in a few minutes. This is the method I followed:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Go to Settings >> About Phone and look for the Baseband Version. What do you see there?
jdkoren said:
Go to Settings >> About Phone and look for the Baseband Version. What do you see there?
Click to expand...
Click to collapse
HTC has yet to push out the OS that will prevent the Rage method from working. Even if they did the ./gfree method should still work.
Im gonna try
baseband version12.28b.60.140eU_26.03.02.26_m
Thats what it says. Im gonna keep trying this method. thanks guyz for the help. Im just baffled.
Sir0 said:
baseband version12.28b.60.140eU_26.03.02.26_m
Thats what it says. Im gonna keep trying this method. thanks guyz for the help. Im just baffled.
Click to expand...
Click to collapse
if you are doing the "ultimate guide" look at the screen, the phone and the ADB Shell commands, and see if anything says about a fail or error between each step.
neidlinger said:
HTC has yet to push out the OS that will prevent the Rage method from working. Even if they did the ./gfree method should still work.
Click to expand...
Click to collapse
Reading my mind. I guess that was only for the G2 then.
I'm guessing temproot works with Visionary?
Does the ./gfree -f say anything about errors at the end? It seems to be kind of particular about when you reboot. I also found that I had some files from my previous phone (warranty replaced mt4g) on my sd card. It was not until i removed those files that the ./gfree -f worked.
Here is what I did.
Temproot via visionary.
ADB push the gfree files to /data/local
terminal emulator
su
cd /data/local
chmod 777 gfree
./gfree -f
reboot
temproot with system r/w
permroot, should cause a reboot.
jdkoren said:
Reading my mind. I guess that was only for the G2 then.
Click to expand...
Click to collapse
well no not really. from the blogs that i've been reading HTC will be pushing out a ROM update that will prevent all "Rage against the cage" style of rooters from working on their ROMs. So the HTC Glacier is included. but the ./gfree method i don' "think" uses Rage to work.
Another thing to watch is that when a guide says to power off, you pretty much have to pull the battery, because the MT4G typically just goes into hibernation, and doesn't do a true power cycle...
Sent from my Nexus One using XDA App
Ive giving up
Ive tired and ive tired and nothing, Im about to send this phone back. NOT. but wait and see it out. Try the next method. If anything comes out. Thank you guyz for the support. Im gonna wait it out stock or now.
I was having a hard time just like you. I ended up doing it all on the phone (no pc)
Temp root & r/w in visionary
Copied gfree to /data/local with root explorer
terminal emulator
su
cd /data/local
chmod 777 gfree
./gfree -f
reboot
temproot with system r/w
permroot, should cause a reboot.
Just read & follow all steps in the True s-off guide right after step 4 where it says "optional"
Sent from my HTC Glacier using XDA App
lincoln131 said:
I'm guessing temproot works with Visionary?
Does the ./gfree -f say anything about errors at the end? It seems to be kind of particular about when you reboot. I also found that I had some files from my previous phone (warranty replaced mt4g) on my sd card. It was not until i removed those files that the ./gfree -f worked.
Here is what I did.
Temproot via visionary.
ADB push the gfree files to /data/local
terminal emulator
su
cd /data/local
chmod 777 gfree
./gfree -f
reboot
temproot with system r/w
permroot, should cause a reboot.
Click to expand...
Click to collapse
Perm root never wanted to run for me, so after making system r/w I used ROM manager to flash clockwork recovery and then flashed Iced Glacier.
My wife's phone was impossible to S-OFF. It would even flash the eng hboot successfully and still show S-ON. Grankin suggested it was a faulty eMMC controller; swapped it and the phone rooted first try. I was at my wit's end after my phone was so simple.
This was all pre-gfree, FYI, so I don't know if that would have worked on her original phone or not. Seriously consider a swap if nothing else works.
I was the same way. I was about to pull my hair out. Then I did the gfree method and got s-off in one try and in less than ten minutes. Definitely the way to go.
Sent from my HTC Glacier using XDA App
I followed this method: http://forum.xda-developers.com/showthread.php?t=858021
Make sure that you leave the option "temproot on boot" unchecked.
Works like a charm.
Hours later
I got it.SERiously everyone thank you so much. cost me 2 bucks. I ended getting root explorer. ANd i Copied gfree andro zip to my sd card. Then i Moved the file gfree. To DATA/local AND put it In there. Ta da
su
#cd data/local hit enter
#chmod 777 gfree Hit enter
#./gfree -f
THen u get all these commands. says DOne turn of the device.
HOLD volume down. POWER button and S off. thank you i just got home and did this method thanks guyz your all awesome. wow the support. just when i was about to give up. Ive done other phones but this one was a lil ticky. THank U
Sir0 said:
I got it.SERiously everyone thank you so much. cost me 2 bucks. I ended getting root explorer. ANd i Copied gfree andro zip to my sd card. Then i Moved the file gfree. To DATA/local AND put it In there. Ta da
su
#cd data/local hit enter
#chmod 777 gfree Hit enter
#./gfree -f
THen u get all these commands. says DOne turn of the device.
HOLD volume down. POWER button and S off. thank you i just got home and did this method thanks guyz your all awesome. wow the support. just when i was about to give up. Ive done other phones but this one was a lil ticky. THank U
Click to expand...
Click to collapse
Super Manager is a free Root explorer, and would of done the same thing. So if your phone moved the file to the correct spot then there is something wrong with your ADB.
kenrippy said:
I was having a hard time just like you. I ended up doing it all on the phone (no pc)
Temp root & r/w in visionary
Copied gfree to /data/local with root explorer
terminal emulator
su
cd /data/local
chmod 777 gfree
./gfree -f
reboot
temproot with system r/w
permroot, should cause a reboot.
Just read & follow all steps in the True s-off guide right after step 4 where it says "optional"
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Where did you get the gfree file for this method?
idelgado782 said:
Where did you get the gfree file for this method?
Click to expand...
Click to collapse
Should be the first download in this thread
http://forum.xda-developers.com/showthread.php?t=858996
Alright guys....Need help. How do I unroot from Super OneClick. I have the official TMobile 2.2 ROM as OTA..however it's failing because its checking to see if its rooted. Pleasant. So If someone could point me in the right direction it would be appreciated.
you sure its 2.2? OTA?
Yup. 100% Sure. 112MB file download. File is called Blur_Version.3.6.360.MB525.T-Mobile.en.US.zip with a Blur_Version.3.6.360.MB525.T-Mobile.en.US.crc file as well. Build.prop indicates that it is 2.2.1 /3.4.2-107-JDN-9/34.4.9. Getting completely hung up on this Status 7 error though. It is picky as hell, and I don't have a out of the box backup I can use to try as stock. It is definitely checking files though. It's like christmas and staring at your presents knowing what it is, but you can't unwrap it. Uggh!!
Root can't be your problem. I've updated to that release; Android 2.2.1, Blur 34.4.9, Build # 3.4.2.107_IDN-9, while my system was rooted. My phone was quite customized (Go Launcher with some "foreign" widgets and no Blur apps/widgets except for the Email app to get at my work e-mail) and everything came up OK. I was rather surprized how smoothly it all went. All my data (seemed to be mostly e-mail) had to be re-synched (this happened automatically), and it took one reboot to clear a message about non-Moto battery that was displayed after the first boot. Basically it all is where it was, except, of course, for root (I tried the latest, 1.7, SuperOneClick but it's looping no matter what I do).
Good luck.
[Added]
Well, well. It turned out that even though it seemed that SuperOneClick was failing (looping at trying to mount a partition R/O) it actually it did it's job! I just fired up RootExplorer and lo and behold a confirmation from Superuser for root popped up, got accepted, and I can start renaming the bloatware again. Woo hoo!
For me it ended up being the root. I was able to unroot with Z4root, and as soon as I did no more issues. I ended up saying screw it and wiped my phone all the way back to factory. Figure it's just better to rebuild it all cleanly and be done with it. I'm just happy its an official rom now.
mind posting a nandroid back up please?
It's really insane to sanction against rooting a phone. I can't image a computer denying me administrator's rights.
runeblade said:
How do I unroot from Super OneClick.
Click to expand...
Click to collapse
You can simply do it manually using Root Explorer. delete followings AS ROOT USER and reboot. that's all!
1. /data/data/com.noshufou.android.su
2. /system/app/superuser.apk
3. /system/bin/su & busybox
Also, it can be done via adb connection.
adb shell
$ su
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# rm -r /data/data/com.noshufou.android.su
# rm /system/app/superuser.apk
# rm /system/bin/su
# rm /system/bin/busybox
# reboot
I second this.
jboogie3 said:
mind posting a nandroid back up please?
Click to expand...
Click to collapse
Is there already a method on the root 9.2.2.3 ?
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
Perhaps downgrade your ROM to an earlier version. Someone has done it with HC.
http://forum.xda-developers.com/showthread.php?t=1400532
[Edit] Ignore me. Apparently you cannot go back to a lower version number.
Bump
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470
TNS201 said:
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470
Click to expand...
Click to collapse
It has been patched up with this update
wolf849 said:
It has been patched up with this update
Click to expand...
Click to collapse
confirmed
if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302
chadster214 said:
if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302
Click to expand...
Click to collapse
Problem is that 9.2.2.3 update came for tf101g and that means SBK3 device, therefore root by nvflash will not make the trick...
P.S. As far as we are talking about 3g devices
Is it possible to flash recovery.img on device via adb ? (Fastboot) Then boot into CWM and flash a rooted rom ?
Sent from my GT-I9100 using XDA
Nick502 said:
Is it possible to flash recovery.img on device via adb ? (Fastboot)
Click to expand...
Click to collapse
The bootloader does support the fastboot protocol (and some obscure methods of booting a kernel via JTAG), but it's locked down to the point that you can't even get fastboot to recognize the device.
So no luck there
ViperMod is your answer I believe
I've not had to root since any version of ICS, but many are have success with ViperMod: http://forum.xda-developers.com/showthread.php?p=21009605
You might have to drop back to a 9.2.2.17 or 19 but there are lots of roms out there that are still on that version. I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.
chadcspencer said:
I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.
Click to expand...
Click to collapse
It doesn't work
I tried with my TFT101G build 9.2.2.3 but didn't work!
OK, so to sum it up:
1. SUID /proc/<pid>/mem write has been patched in this release (aka 9.2.2.3) therefore mempodroid exploit and basing on it viperMod is useless
2. qEmu vulnerability in /data/local.prop is also patched up so TPsparkyroot will also fail.
3. The location of backed up files and temp storage have been shifted out from data therefore all rooting tools connected with ASUS backup app will not do the trick.
4. Jumping back to previous software is unachievable without root.
So I ask you to post ONLY methods that are not listed above.
(However I think that we have to wait for next linux Local Privilage Escalation bug to be discovered in order to get rooted)
Cheers
P.S. Sorry for any mistakes English is not my native.
ICS 9.9.23G
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?
thunderman98 said:
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?
Click to expand...
Click to collapse
OTA is only for TF101G. You can install firmware pack from ASUS website through custom recovery, but I do not see any point of doing that.
Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance
hearts king101 said:
Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance
Click to expand...
Click to collapse
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.
wolf849 said:
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.
Click to expand...
Click to collapse
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits
sbiriguda said:
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits
Click to expand...
Click to collapse
Unfortunately I've tried that and than I came to a conclusion that 'ro.kernel.qemu=' has been shifted... Try read build.prop on /system and you will find it there, so /data write does nothing for now
EDIT:
Nonetheless, I have rw access to /cache where dlpkgfile is held, so maybe it is possible to do a downgrade of firmware through that hole.
EDIT2:
BTW, I did it by flashing TW 9.2.2.3 firmware on to WW 9.2.2.3 through EP101_SDUPDATE (or similar).
Than:
adb mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /cache /data/local/tmp
adb rebbot
After that /data becomes readwrite
EDIT3:
There is also one more question: where is held /tmp partition needed to repack the blob maybe by accessing it and pushing blob we can manually force its update.