Hello,
This is a new root method.
This is a linux / OSX version only for now.
When you untar the file. Please make sure to edit the runme.sh it has a path for adb that you need to fix. Other then that it will work.
You just chmod 755 runme.sh and run it
[COLOR="Red"]Mod Edit: removed link[/COLOR]
EDIT: This has been confirmed working on the TF201 and TF101 so its a Universal root for all transformers
EDIT: Adding a step by step guide here.
A) Install an app from market any app. (I choose rootchecker)
B) Open the app-draw and select the asus backup utility and backup rootchecker
C) follow the scripts instructions
D) When it asks you to do another backup. Go into the backup utility from the TF101/TF201 (from the app-draw) go to back and RE-BACKUP the SAME app (Rootchecker in my case)
E) The system will reboot and you will have root. Do this all while the script is running. It will pause and ask you do the above items.
Thanks!
Reserved for later
well adapted it to windows in case anyone needs it
Just extract the zip file, execute the run.bat and follow the onscreen instructions.
chan32167 said:
well adapted it to windows in case anyone needs it
Just extract the zip file, execute the run.bat and follow the onscreen instructions.
Click to expand...
Click to collapse
Both you and the OP are legends. worked like a charm.
THANK YOU
bungknees said:
Both you and the OP are legends. worked like a charm.
THANK YOU
Click to expand...
Click to collapse
Thanks............
I'm already rooted, but I like the technique- it's quite clever and a wonderful hack.
I don't recall there ever being so many root exploits for a single device. It's like a tablet with a free puzzle that keeps giving. People are going to start buying the TF just to root it.
I tried another way to root but when i rebooted i have cwm 3101 and su which updated but not the binaries. When i try anything its telling me i don't have root access.
Now when i try to rerun it or this it hangs right at waiting for device in the beginning. Any thoughts?
Windows 7 x64 machine
B50
frankwhite8536 said:
I tried another way to root but when i rebooted i have cwm 3101 and su which updated but not the binaries. When i try anything its telling me i don't have root access.
Now when i try to rerun it or this it hangs right at waiting for device in the beginning. Any thoughts?
Windows 7 x64 machine
B50
Click to expand...
Click to collapse
Dont know much about windows sorry. I used my method here to root on ICS. Started from stock -> Ota X 3 or 4 then root.
so this will root the official update? if so, i may be interested, but i need to know what kernel version is included in the official FOTA package. if it's still 2.6, i won't bother
sarreq said:
so this will root the official update? if so, i may be interested, but i need to know what kernel version is included in the official FOTA package. if it's still 2.6, i won't bother
Click to expand...
Click to collapse
Yes, This roots the current OTA as stated in the OP / Thread Topic
but what kernel version is in the FOTA?
sarreq said:
but what kernel version is in the FOTA?
Click to expand...
Click to collapse
2.6.39.4-00002
Neptune #1
sarreq said:
but what kernel version is in the FOTA?
Click to expand...
Click to collapse
Kernel is 2.6.39
rhcp0112345 said:
Dont know much about windows sorry. I used my method here to root on ICS. Started from stock -> Ota X 3 or 4 then root.
Click to expand...
Click to collapse
Thanks. I was able to flash this
http://forum.xda-developers.com/showthread.php?t=1334673
And I'm working as god intended.
frankwhite8536 said:
Thanks. I was able to flash this
http://forum.xda-developers.com/showthread.php?t=1334673
And I'm working as god intended.
Click to expand...
Click to collapse
Nice, Good
frankwhite8536 said:
2.6.39.4-00002
Neptune #1
Click to expand...
Click to collapse
rhcp0112345 said:
Kernel is 2.6.39
Click to expand...
Click to collapse
thank you both.
you'd think they would've updated that, since ICS proper is supposed to run on a 3.x kernel.
so, will a honeycomb CIFS.KO work with the FOTA? or is there an ICS specific CIFS module somewhere out there? / nevermind, found it here nope, wrong again, that's for the tfprime, and causes a bootloop when it loads. i guess we have to wait for one to be ported, then?
update: resolved. Didn't know about the App Backup Utility
Worked as promised. Remember you must run the Asus Backup Utility twice!
rhcp0112345 said:
This is a linux / OSX version only for now.
When you untar the file. Please make sure to edit the runme.sh it has a path for adb that you need to fix. Other then that it will work.
You just chmod 755 runme.sh and run it
http://www.mrcellphoneunlocker.com/V2/tf101_ics_root.tar.gz
Click to expand...
Click to collapse
Great job! thanks
tomdot said:
update: resolved. Didn't know about the App Backup Utility
Worked as promised. Remember you must run the Asus Backup Utility twice!
Click to expand...
Click to collapse
what's this utility? never seen it before
WOrks!
Working Perfectly.
Related
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
is busy box installed?
is SU working?
feefeeboomboom said:
is busy box installed?
is SU working?
Click to expand...
Click to collapse
I haven't done anything since flashing the 2.1 RUU. What steps do I need to do to get busybox and su working?
if you installed the RUU that was just 'leaked' (from what i understood our 2.1 builds are based off this ruu already). The build does not include busy box or anything for that matter that is required for wireless tether-
damageless said:
Here is a link to the latest RUU from Sprint.
You cannot simply extract it. This still has root since it is a test release. I recommend just doing an adb pull of your system directory after you flash it. Don't do this when the final one comes out or else you might be stuck without root.
You will need to add busybox, patch sh and su, and make sure that you do another recovery image and such. I also recommend adding Superuser.apk and stuff. If you use the Desire build.prop, you can get most of the protected apps working.
Enjoy.
http://dl.damagedroms.com/2.0/RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe
Leak, I know who you are.
Click to expand...
Click to collapse
http://benno.id.au/blog/2007/11/14/android-busybox
Busy Box link for you, I'm not really sure how to get it working but it's a start, alot of results come up if you google "busybox for android", so I hope that helps ya out bud
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
dwertz said:
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
Click to expand...
Click to collapse
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root
Click to expand...
Click to collapse
Who told you that the RUU was rooted already? It's not. Why would it be? Sprint has no interest in you being root.
As for why do you have to install busybox? Because the application requires it.
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
mobilehavoc said:
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
Click to expand...
Click to collapse
Here is the superuser.apk You have to have root.
Put superuser.apk in your C:\AndroidSDK\Tools\
adb remount
adb push superuser.apk /system/app/
mobilehavoc said:
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
Click to expand...
Click to collapse
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
Not sure what you mean but I was able to push a new build prop onto the phone using adb with no issues.
posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
The leak actually is rooted. It's an engineering leak, so root can work his magic- but only from the adb shell.
why do you need superuser?
superuser requires root, if you had root, you wouldnt need it.
you can just dl the wifi tether for root from the market
program and it would work right?
10 chars and a poke
The Samsung Transform has the same vulnerability as the Epic (joeykrim-root.sh works to get root).
So how would I go about rooting? Would I use the same process as the EPIC 4g?
if you're good with linux, you can follow the directions in this link forum.sdx-developers.com/epic-development/adb-root-exploit-test
(The mount command is slightly different in step 4.)
I'm running a mac. I tried several guides on the sph-m910 rooting for mac osx but it won't let me push any files to the phone with adb.
Sent from my SPH-M920 using XDA App
Have any of you successfully rooted it using this method?
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
aliendude5300 said:
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
Click to expand...
Click to collapse
Here's a link to the zip file containing the exploit that worked: http://www.filedropper.com/ocr
drivers?
What drivers are you guys using? i cant get any drivers to install...
mark920 said:
What drivers are you guys using? i cant get any drivers to install...
Click to expand...
Click to collapse
From what I am told and understand it must be mounted and run in linux. I will find out as soon as my local store gets one in, I'm first in line.
aliendude5300 said:
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
Click to expand...
Click to collapse
Any link to the method you used?
aliendude5300 said:
Here's a link to the zip file containing the exploit that worked:
I've tried 8 times, cannot get it rooted. Suppose I'll wait just like the rest of us
Click to expand...
Click to collapse
berger1980 said:
aliendude5300 said:
Here's a link to the zip file containing the exploit that worked:
I've tried 8 times, cannot get it rooted. Suppose I'll wait just like the rest of us
Click to expand...
Click to collapse
I tried it as well. I couldn't get it to work either.
Click to expand...
Click to collapse
I got it to work. I tried it under my computer with Windows 7. I had to right click the run.bat and click properties, Click compatibility, Run this program in compatibility mode for Windows XP Service Pack 3. Thanks.
cachorropedorro said:
I got it to work. I tried it under my computer with Windows 7. I had to right click the run.bat and click properties, Click compatibility, Run this program in compatibility mode for Windows XP Service Pack 3. Thanks.
Click to expand...
Click to collapse
I don't mean to be a ****, but what app have you installed that requires root access? I have a specific one, roam manager, that will not run. I believe you may have seen visually that it was rooting it, but it does not do squat.
berger1980 said:
I don't mean to be a ****, but what app have you installed that requires root access? I have a specific one, roam manager, that will not run. I believe you may have seen visually that it was rooting it, but it does not do squat.
Click to expand...
Click to collapse
apps2sd, I need a new kernel for wifi tethering which is the main thing that I want
Rooting Help
Can someone give some detailed instructions on rooting the Samsung Transform???
I agree with cachorropedorro, I'm looking to root for wifi teathering also..... Tried a few methods also.... No luck.
Guys, I've never rooted a phone before and this is my first android. I looked a the Joeyconway version of root.... I'm having a hard time following the command prompts??? Any suggestions?
Is there going to be a transform category? Are there other pages about rooting this new phone??
I was able to root my transform using the ocr joey krimm root method, the drivers for the epic finally worked after restarting the phone, one thing i noticed about the transform was that the ratc script takes longer to work and does not always work. I modified the bat file to have a longer wait after running the ratc file, however that doesnt even work all the time, if you manually run the ratc script and then run the bat it should work thats what i had to do. I also updated the su bin and the busybox version from the current version of the one click root because the files in the ocr.zip have an older su bin that doesnt use superuser.apk and the busybox is not compatible with ti backup.
Mark920,
Can you give some more detailed directions for all of us that are newbees? Like I said in a earlier post, I've never rooted a phone so some of the things you were talking about like ratc script confuses me. Any detailed steps would be awsome.
Earlier today I decided I wanted to try Gingerbread through the Android Emulator. It required several updates and the SDK was update to v8. It seems that v8 does not contain adb.exe. For anyone who will be working on their phone using adb, this is obviously a problem.
I've provided v7 below for those that need it.
Android SDK v7
xDragod said:
Earlier today I decided I wanted to try Gingerbread through the Android Emulator. It required several updates and the SDK was update to v8. It seems that v8 does not contain adb.exe. For anyone who will be working on their phone using adb, this is obviously a problem.
I've provided v7 below for those that need it.
Android SDK v7
Click to expand...
Click to collapse
It does have it, but moved to a new folder. Please read the documentation provided with it.
They changed the location of adb. It's now under /platform-tools
I see... Well, nevermind then.
xDragod said:
I see... Well, nevermind then.
Click to expand...
Click to collapse
Good looking out none the less.
Sent from my HERO200 using XDA App
MrSpradlen said:
Good looking out none the less.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yeah.. I was kinda scared. I messed with Gingerbread, then started messing with my phone. Had to pull build.prop through android commander and it said ADB wasn't working. I redirected the path and it said not found. ADB wouldn't work in cmd. I was worried others might have the same problem.
that's fresh hero 2.4.....also can u put up sdk 7?
Sparticuz said:
that's fresh hero 2.4.....also can u put up sdk 7?
Click to expand...
Click to collapse
Sorry. Link fixed.
I can't find platform tools
BlaqkAudio said:
They changed the location of adb. It's now under /platform-tools
Click to expand...
Click to collapse
I don't have that folder in the sdk I downloaded from the website. What am I doing wrong??
lngwstx said:
I don't have that folder in the sdk I downloaded from the website. What am I doing wrong??
Click to expand...
Click to collapse
You need to finish installing. Follow step 4: http://developer.android.com/sdk/installing.html
lngwstx said:
I don't have that folder in the sdk I downloaded from the website. What am I doing wrong??
Click to expand...
Click to collapse
you didnt watch my video tutorials
if youre going to use draw9patch download swing worker HERE
you wont be able to run draw9patch without it.
Anyone have a link for one? Just want to get root access without swiping my data if possible. I did a search but came up with links and files only for 3.2. I'm sure someone is working on one. Thanks guys
http://forum.xda-developers.com/showthread.php?t=1185104
baseballfanz said:
http://forum.xda-developers.com/showthread.php?t=1185104
Click to expand...
Click to collapse
Confirmed working.
Download the v5 Beta and run it and select option "9".
Don't forget to install su, Superuser.apk and busybox afterwards!
jhanford said:
Confirmed working.
Download the v5 Beta and run it and select option "9".
Don't forget to install su, Superuser.apk and busybox afterwards!
Click to expand...
Click to collapse
Worked for me as well. Pretty straightforward, too.
awesome, thanks guys, his 3.1 guide popped up in search but not that one.
jhanford said:
Confirmed working.
Download the v5 Beta and run it and select option "9".
Don't forget to install su, Superuser.apk and busybox afterwards!
Click to expand...
Click to collapse
Sorry to ask a stupid question, but why do I need busybox? I know what it does, but since I don't run unix commands on my tablet, why do I need it?
Hi,
I am looking at that thread too, the batch thread for 3.2 root. I am very very new to this, never rooted anything and wanting to. the thing I am worried about is the faq seem to have not been updated in the bat file, at least it looks lke that to me. it just makes it more confusing
Is this the order I should do this (I have a stock unrooted 3.2 (ota did the 3.2 upgrade) and I am curious about the steps after drivers installed, adb is talking to my tf, and I am in APX mode
1. press 6 Check if ADB is working
2. Press 3 to back up my stock boot.img and recover.img ?
3. press 9 to install "Install root US and/or Recovery 8.6.5.6 (HC3.2) beta"
4. press 7 to install superuser
5. press 8 to install busy box via ADB
6. then reboot?
Please confirm this is correct for me?
thank you for any help,
John
Xerravon said:
Hi,
I am looking at that thread too, the batch thread for 3.2 root. I am very very new to this, never rooted anything and wanting to. the thing I am worried about is the faq seem to have not been updated in the bat file, at least it looks lke that to me. it just makes it more confusing
Is this the order I should do this (I have a stock unrooted 3.2 (ota did the 3.2 upgrade) and I am curious about the steps after drivers installed, adb is talking to my tf, and I am in APX mode
1. press 6 Check if ADB is working
2. Press 3 to back up my stock boot.img and recover.img ?
3. press 9 to install "Install root US and/or Recovery 8.6.5.6 (HC3.2) beta"
4. press 7 to install superuser
5. press 8 to install busy box via ADB
6. then reboot?
Please confirm this is correct for me?
thank you for any help,
John
Click to expand...
Click to collapse
That should work.
slipshft said:
That should work.
Click to expand...
Click to collapse
thank you!! I will try
Xerravon said:
thank you!! I will try
Click to expand...
Click to collapse
I believe you will have to reboot before you install superuser and busybox. They won't install while you are in APX mode. At least that was the case for me. I let everything finish in APX mode, rebooted, pushed SU and BB via ADB, and rebooted again.
You may have already known this but I got stuck for a bit because it never said to reboot before you push SU & BB.
Will not let me Unzip the file. redownloaded, reset my computer. I can unzip other files. not this one. Any ideas?
thank you,
Hitmanthe3rd said:
Will not let me Unzip the file. redownloaded, reset my computer. I can unzip other files. not this one. Any ideas?
Click to expand...
Click to collapse
You need to use 7zip to unzio it
Rooted my stock 3.2 TW using that method, worked flawlessly
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.