Related
This thread is copied and modified from the G2 thread by trigeek for the Desire Z:
http://forum.xda-developers.com/showthread.php?t=834228
Apart from the changed hboot and wpthis-Z kernel module for the Desire Z instead of the G2, I have also updated the su-binary and SuperUser.apk to the latest version by ChainsDD
In no way I can be held responsible for any bricks to your phone. You are using this guide at your own risk!! I did test this guide on my own, and also on a friend's Desire Z.
As there was no manual rooting guide for the Desire Z, I posted it myself in order to help others that do not like visionary and like to do it 'the clean way'.
[GUIDE] Temp to permanent root on Desire Z, using rage instead of visionary
=================================================
There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-
None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. His paypal is:
[email protected]
Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!
DESIRE Z ROOT INSTRUCTIONS
=================================================
These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.
REQUIREMENTS
=================================================
•Visionary disabled at boot or uninstalled completely
•Android Terminal Emulator app
•ADB
•desirez-combined-root.zip (Attached to this post)
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
VERY IMPORTANT!
Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.
TEMP ROOT
=================================================
ON YOUR PC:
Unzip the z-temp-root files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
Code:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
ON YOUR PHONE:
1.Launch Terminal Emulator
2.
Code:
/data/local/tmp/rage
3.Wait for the message: "Forked #### childs."
4.Menu > Reset Term - Terminal Emulator will exit.
5.Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
6.**NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this just yet. Leave the terminal window open.
PERM ROOT
=================================================
ON YOUR PC:
unzip z-perm-root and navigate to that folder. There will be four files. You will need to push two of these to your phone: hboot_7230_0.84.2000_100908.nb0 and wpthis-Z.ko. The other two files are optional for checksum verification.
Code:
$ adb push hboot_7230_0.84.2000_100908.nb0 /data/local
$ adb push wpthis-Z.ko /data/local
Optional but might came in handy:
Code:
$ adb push md5checksum /sdcard/md5checksum
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Optional but recommended:
Code:
# /data/local/tmp/busybox md5sum /data/local/*
You should see:
hboot_7230_0.84.2000_100908.nb0 2ce1bdd5e4c1119ccfcecb938710d742
wpthis-Z.ko c73c5e77c91d306c418983c002b60b93
In case your hboot or wpthis-Z.ko file do not have the same md5hash as shown above, DO NOT CONTINUE. This means your file is corrupt or you are using a different file, for example the one for the G2 instead of Desire Z.
Now, let's turn off security for permanent flashing:
Code:
# insmod /data/local/wpthis-Z.ko
init_module 'wpthis-Z.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
# dd if=/data/local/hboot_7230_0.84.2000_100908.nb0 of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
You should see some messages indicating that it was written.
Code:
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code:
# sync
Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!
Nice guide, thanks
Thank you Mr Q. works like a charm!
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
when I just ignore it and type sync after that I have no root acces after a reboot.
Does anybody have a solution for it? I have already done a hardreset with the same results.
thanks in advance...
So this only roots your phone? Or does it s-off as well? From what I understand this s-offs as well because you're pushing the hboot as well.
EDIT: Nevermind. I read the thread again and it does indeed s-off as well.
MarDor said:
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
when I just ignore it and type sync after that I have no root acces after a reboot.
Does anybody have a solution for it? I have already done a hardreset with the same results.
thanks in advance...
Click to expand...
Click to collapse
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
ssyed said:
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
Click to expand...
Click to collapse
having the same issue here
So I'm looking into these S-OFF and rooting threads and here is two bricks too. Does anyone have an answer for these two or should I skip this? Did the hboot do this or was it due to some problem in inserted kernel module? (I.E. the reboot of the emmc controller resulted in a ****ed up file system?)
yelti said:
having the same issue here
Click to expand...
Click to collapse
AnyDone said:
So I'm looking into these S-OFF and rooting threads and here is two bricks too. Does anyone have an answer for these two or should I skip this? Did the hboot do this or was it due to some problem in inserted kernel module? (I.E. the reboot of the emmc controller resulted in a ****ed up file system?)
Click to expand...
Click to collapse
Ok, so I have figured out how to get out of this "quietly brilliant" loop.
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
ssyed said:
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
Click to expand...
Click to collapse
Ok, so does any one have an explanation why this happened?
1. It wasn't wrong or screwed hboot, otherwise we would be facing a real brick?
Was it the root method? Was it the wpthis-Z.ko?
It might have been the kernel module, but I can't be sure about that with so little knowledge I have. (sure not the module itself but the kick to the emmc?) Just that it seems to be more likely option than a rooting attempt on a cached r-o file system?
I'm not complaining about the guide, it is specific and easy to follow but I would really love to have these semi bricks etc inspected more closely. It is not really helping to encourage ppl to root and try safe-off when we have unexplained bricks and semi-bricks around
MarDor said:
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
Click to expand...
Click to collapse
ssyed said:
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
Click to expand...
Click to collapse
yelti said:
having the same issue here
Click to expand...
Click to collapse
Did you guys run Visionary before trying this "rage" method of rooting ?
steviewevie said:
Did you guys run Visionary before trying this "rage" method of rooting ?
Click to expand...
Click to collapse
I don't know about others, but I didn't on mine. I was rooting it for the first time. Also, I don't know if this has anything to do with it, but I have the Bell version from Canada.
The root script threw an error for me too, so just to be safe I opened the script and typed in the commands manually. If you have problems with the script, just run these commands from the root terminal on your phone:
Code:
/data/local/tmp/busybox killall rage
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
mkdir /system/xbin
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
sync
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Hope this helps someone.. Thanks to the OP for the scripts.
Have a quick look, /system/xbin already seems to exist on my phone too.
So is there an error in the script ? e.g. needs to ignore if the directory already exists ? Or am I (we ?) missing something ?
goldenarmZ said:
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Click to expand...
Click to collapse
Good info, thanks. Perhaps just comment out that line of the script, to save running it all by hand (and therefore be prone to more error ?) ?
steviewevie said:
Good info, thanks. Perhaps just comment out that line of the script, to save running it all by hand (and therefore be prone to more error ?) ?
Click to expand...
Click to collapse
I did that first.. it threw more errors with the mount commands because I'd already run the script once, so some of the commands were repated. If it's your first run through, commenting it out would be fine.
I only did it line by line so I could see any more errors for myself and decide if they were important. As it turns out the script is very simple and only involves moving files around and changing their permissions.. anything that goes wrong should be immediately apparent even if you have no experience with shell commands.
goldenarmZ said:
I only did it line by line so I could see any more errors for myself and decide if they were important. As it turns out the script is very simple and only involves moving files around and changing their permissions.. anything that goes wrong should be immediately apparent even if you have no experience with shell commands.
Click to expand...
Click to collapse
Thanks, I was starting to worry about the bad experiences outlined above, given that this method appeared to be a more reliable one than VISIONary, and a route I was going to go down. But I'm pretty comfortable with shell scripts, so your input makes me feel a whole lot better !
goldenarmZ said:
The root script threw an error for me too, so just to be safe I opened the script and typed in the commands manually. If you have problems with the script, just run these commands from the root terminal on your phone:
-code-
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Hope this helps someone.. Thanks to the OP for the scripts.
Click to expand...
Click to collapse
thanks for this... I will give it a try
Yay, I just perma-rooted my phone using this method, many thanks to those who came up with the method in the first place, plus this handy guide too.
I got the message about /system/xbin already existing, but you can just ignore that message, it runs the rest of the script anyway.
ssyed said:
Ok, so I have figured out how to get out of this "quietly brilliant" loop.
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
Click to expand...
Click to collapse
So after doing the guide you simply reeboot your phone into bootloader and select factory reset?
And then will the device be perm root and s-off???
I'm trying the rage root method after reading up on all the stuff. I managed to get adb installed and connected, but i can't use adb actions.
I type in c\androidsdk\tools\adb shell
$ su
$ SUermission denied
even without su, if i try to type "adb push su /sdcard/su" it says adb permission denied.
I have kept my phone screen on as per another thread, but i do not get a prompt that asks for adb permissions. Am i missing an app or something? I do have debugging and screen awke both on.
I have placed the g2 root folder in the androidsdk\tools\ folder, both just the files and the entire folder just to be sure.
Obviously I'm new to adb, so If i'm doing something completely wrong just let me know.
as long as you're not rooted (temp or perma) you can't use "su" in adb-commands... If you tell a little more about what you're trying to push, then I can help some more
Im just trying to root the phone with rage since visionary seems unreliable.
Im trying to adb push the su/ sdcard/su as per the first line of instruction in the rage temp root guide
hehe... I used the visionary root, and it have worked good for me btw, I think you should've posted in the rage-thread instead of opening a new topic, but now it's already opened so here it goes
firstly... are you sure you're in the right folder, and have the folder "su" in there?
If so, don't go into "adb shell"... use the lines exactly as stated in the OP. adb inside an adb shell won't give the results you want... Post back if it doesn't work
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Click to expand...
Click to collapse
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Ok, my adb stuff is in c:\tools .. so when I first open command prompt, I have to type this:
cd c:\tools
That puts me into the correct folder. If yours is in C, then you'd probably have to do this:
cd c:\androidsdk\tools
Then type:
adb devices
It should at least give you SOME sort of output, either with your device number (if it's connected, and adb is working properly), or just say devices, with no numbers (incorrectly)
dwang93 said:
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Click to expand...
Click to collapse
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
FYI you will not see the $ symbol. that just indicated the next line you have to enter in commnad prompt. Each time you see $ just mean you type that line then press enter. Wait to see a result of transfer from prompt then enter next line and so on.
rsxtypes72 said:
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
This!! I'll be kind though.
Make your life easy. Unzip the contents of g2TempRoot, to your tools folder, in sdk. So, unzip the g2temproot to your desktop. Go into that folder. Copy all, and move them to c:\androidsdk\tools. Now, once that's done, go into command prompt. cd c:\androidsdk\tools. Then, do as follows, as per that link
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
(Sorry I couldn't be of more help, as I used VisionaryR12 and it worked fine for me.)
One more word of advise...
I would recommend you try temp root first.
Become used to using adb then try to get full root.
When you use temp root everything you do is temporary only.
Rebooting will reset everything back to stock so its good practice.
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
any tips on going onto the perm root?
Click to expand...
Click to collapse
Read .. research .. double check .. triple check .. and right before you do it .. check again. As you're doing it, go over every letter, space, and character to make sure it's as it should be.
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Daughain said:
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Click to expand...
Click to collapse
Upload a screen shot of your command window
with the error
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
Click to expand...
Click to collapse
dude..I think I am doing something like you...could you please post what you did....I think is an issue of directories..but I'm not that familiar with adb and i have not been able to figure this out.....
Thanks!!!
[Q] Help me root my OTA upgraded G2 Visionary R14 Don't Work "Visionary R7 needed"
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......
Is temp root working?
Sent from my HTC Vision using XDA App
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks
My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks
Nonentity018 said:
Is temp root working?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
+1
Like he said, use that, don't waste your time with visionary
sammd301 said:
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......
Click to expand...
Click to collapse
I'd stay away from visionary if I were you! Its messing up just as many phones as it is rooting them!
part of the problem is that a visionary method is stickied in one of these subforums... that needs to be taken down desperately and replaced with gfree/rage.
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
I am in the process of using this method....I'll let you all know how it turns out. by the thanks for pointing me to it...
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
Yes I am in the process of using ADB / RAGE method....I run in problem and I could use someone help please...
TEMP ROOT
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
===========
All the commands are working except
$ adb push rage /data/local/tmp/rage
the reply I get after input the command is
Cannot open 'rage': No such file or directory
I have search the web for help...but I could find help on that issue
SO please if anyone knows what I am doing wrong could you please help....
thanks
unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.
yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it
Cobra281 said:
yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it
Click to expand...
Click to collapse
Yes the "Rage" file is there, all the other command work fine...except the one dealing with the "Rage" file
ratchetrizzo said:
unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.
Click to expand...
Click to collapse
Thanks so much for your input....when I gfree_temp-root.zip file I can see that the "RAGE" file is present but after 20 to 30 minutes the "RAGE" file disappear from the folder but all the other files remains....Is an alternative gfree_temp-root download link that anyone might know of....thanks again
Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App
ratchetrizzo said:
Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...
sammd301 said:
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...
Click to expand...
Click to collapse
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.
ratchetrizzo said:
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.
Click to expand...
Click to collapse
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system
sammd301 said:
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system
Click to expand...
Click to collapse
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.
ratchetrizzo said:
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.
Click to expand...
Click to collapse
Yes, I did what you suggested, but now I am getting
"rm failed for -rt, no such file or directory" after inputting ""rm -rf /system/xbin" command...by the way thanks so much for helping me out on this...
I am attempted to root my phone as the new guide on the wiki.
Once I get to this secion:
In this shell:
Remark: When you run su for the first time in the adb shell make sure the the screen of the phone is unlocked. Because when you enter the command the Superuser app will show up and ask you if you want to grant superuser access to app Unknown (2000).
Check the Remember check box and click allow.
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
I am unable to get SU to enable, it'll immidetly say permision denied and does not prompt anything on my phone and does not allow me to gain access so I am unable to verify Gfree
Thanks in advance for the help
What's the exact commands you're typing in the command prompt?
I have shell, so I type
$ su *$ is not typed, already shows in the command prompt*
but I think I know what I di dwrong and I am trying it again
Did you manage to get the root access?
Care to tell how it's done for you? Because I am having the same problem
I pretty much just followed the steps as stated in the wiki.
Just make sure you do all the steps required and more importantly that you type properly, thats what messed me up, I went like most of the way in to find out I forgot to do something properly @ the start.
You can also copy and paste the commands into your command line window which I did the second time round and that pretty much solved all problems for me , its fairly simple to be honest
These instructions are not solely my own and are adapted from miloj’s Windows based instructions found here:
http://developer.android.com/sdk/installing.html
Thank you miloj for the instructions!
This guide is intended to help noobs with rooting their TF300T device with a Mac. I am probably a half step above noob, so please don’t expect perfection.
Read this these instructions straight through, maybe even a couple of times before you begin to make sure you fully understand what you are doing.
I am not responsible for any bricked devices, malfunctions, etc. and most likely will not be able to problem solve much for you. Hopefully, the real geniuses here on XDA will jump in should you need extra help.
First off, make sure you have Android SDK and ADB installed. Follow these instructions skipping the Eclipse installation step (unless you plan on developing apps and such):
http://developer.android.com/sdk/installing.html
Save these files wherever makes sense to you and once done open up the folder containing adb in file explorer and leave open. This should be in the SDK>platform-tools folder.
Now for miloj’s instructions with some Mac specific extras and for sake of ease:
Download the debugfs and su binary files provided by miloj first from here:
http://db.tt/FBUNeVmo
Again, save these files where it makes sense to you and then open up the containing folder in file explorer and leave open.
Make sure “usb debugging” is turned on on your Asus TF300T by going to Settings>Developer options and check the USB debugging options.
Make sure you device is plugged into your Mac via usb cable. Now find out if our Mac recognizes your device.
Open up terminal from your utilities.
Organize your Terminal and folder containing adb on your workspace so you can easily access both. Click, hold, and drag the adp icon and drop it into the Terminal window. This will allow you to you immediately move into the adb command without having to type in the complete destination. Your line should end with “…/adb” now type in the command devices and hit return/enter.
NOTE – from here on out assume after every command you hit “return” or “enter”
It will look something like this:
Code:
…adb devices
the response should read:
List of devices attached
{serial number} devices
If nothing is listed, then you either didn’t activate USB debugging or your adb isn’t up to date, start again from the top.
If it showed your device, then lets move forward.
Now we have to push over the debugfs file and the su file (superuser). Make sure you can see Terminal and both open file explorer windows listed above all visible on your workspace.
Again, click, hold, drag the adb into Terminal and then complete the following commands by typing the command (in this case “push”) in between adb and the proper file and then typing in the location you want it pushed to on the device: (*note: dragging and dropping the “debugfs”file where it says “debugfs” – your file destination path name will be shown, not just debugfs)
Code:
adb push debugfs /data/local/
In the command above you would drag into Terminal the adb file then type push, drag in the debugfs file then type in “/data/local/” all with spaces in between. Every time you read in a “Code” section “adb” you are going to follow this procedure with the adb icon/file. Now, rinse and repeat moving forward.
Then this command (dragging and dropping the “su”file where it says “su” – your file destination path name will be shown, not just su)
Code:
adb push su /data/local/
now you have debugfs and su on your device.
You now have to have Terminal take control and run commands in your device by using this command:
Code:
adb shell
once in you will have a line starting with a “$” and you type in the following commands to gain root access: (type them exactly as written)
Code:
cd /data/local/
mv tmp tmp.back
ln -s /dev/block/mmcblk0p1 tmp
exit
The “exit” takes you back into your Mac, now reboot your device through adb:
Code:
adb reboot
WAIT UNTIL THE TF300T HAS BOOTED UP AGAIN!
Now get back into the device:
Code:
adb shell
Continue with the following commands after the “$” symbol:
Code:
cd /data/local
toolbox chmod 755 /data/local/debugfs
/data/local/debugfs -w /data/local/tmp
Now you’re going to run the debugfs files. Make sure you are writing these all in EXACTLY as written. All lines preceeded by “debugfs:” you will type in the following:
Code:
cd xbin
rm su
write /data/local/su su
set_inode_field su mode 0106755
set_inode_field su uid 0
set_inode_field su gid 0
quit
Now, back in to lines starting with “$” and run these:
Code:
rm /data/local/tmp
mv /data/local/tmp.back /data/local/tmp
exit
Now reboot:
Code:
adb reboot
WAIT UNTIL THE TF300T HAS BOOTED UP AGAIN
You are rooted! Congratulations!
Let’s double check and do some clean up:
Code:
adb shell
From the line “$” type these commands for double check:
Code:
/system/xbin/su
Now the line is a hash tag “#” and type
Code:
id
The Terminal response should read something like this:
id=0 (root) gid=0 (root) … and so forth
Clean up:
Code:
rm /data/local/su
rm /data/local/debugfs
Done with Terminal.
Now, open up the Play store and download the Superuser app immediately. Once it is installed, open the app and go into the settings. Under the heading “GENERAL” Tap the “Su binary v…” to check for updates and update the app.
You are now rooted, you have Superuser control.
Let me know how this works for you!!!
Credits: wolf849 for exploit, and miloj for commands.
Good stuf, just wait firsts feedbacks about this process :good:
Inserted in the Index for TF 300t
Guess i'm the only person who either owns a Mac here or has tried this but...
First time Terminal user and first time ASUS owner. Was a bit iffy doing it. Read through the TF300 board for weeks and was scared as sh#t to mess with this but...
it works!! Thank you so much. :good:
ngocdao said:
Guess i'm the only person who either owns a Mac here or has tried this but...
First time Terminal user and first time ASUS owner. Was a bit iffy doing it. Read through the TF300 board for weeks and was scared as sh#t to mess with this but...
it works!! Thank you so much. :good:
Click to expand...
Click to collapse
I'm glad it was easy for you! I am not a pro Terminal user by any stretch of the imagination! I am a first time ASUS owner as well, and have only rooted 2 phones and worked on rooting another (the phone ended up being software updated via Verizon to the point of unrootable that I could find or figure out). I am a Mac user and do not have easy access to a Windows PC and figured there were plenty of other Mac users noob to rooting. Apparently, that lists is you and me!!!
Thanks for the feedback, though! Congrats on your root!!
...too dificult for me,
Thanks.
Enviado desde mi ASUS Transformer Pad TF300T usando Tapatalk 2
dirator said:
...too dificult for me,
Thanks.
Enviado desde mi ASUS Transformer Pad TF300T usando Tapatalk 2
Click to expand...
Click to collapse
It sounds intimidating, I know, trust me when I say this is rather easy! The first time I rooted my phone I was quite worried! I read the instructions a few times and took my time though and it was really quite easy! Read the instructions a few times and you'll be alright. If you start to have trouble come back here or to this thread http://forum.xda-developers.com/showthread.php?t=1704209 and ask for answers.
not working as expected
Sorry to bother you with noob's problems.
I think I unlocked my TF300T ww Jelly Bean 4.2.1 allright.
I moved debugfs and su and other files to /data/local/ through bluetooth 'cause I wasn't able to do it in any other way.
The process worked fine up to here:
mv tmp tmp.back
Then I got this message:
[email protected]:/data/local $ mv tmp tmp.back
failed on 'tmp' - Permission denied
also, when pressing Power + Vol Down and then Vol Up to choose RCK it just dies (lying android with red triangle)