Related
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!!!
Hello All,
So I decided to try rooting after doing all this research. I chose to use the "rage" method shown here: http://forum.xda-developers.com/showthread.php?t=834228
I download all the files and everything needed, I get adb to work, and I type in the displayed commands. My problem comes in when I move over to the phone and use Terminal Emulator. I type in /data/local/tmp/rage just as the directions specified but emulator then spits back: /data/local/tmp/rage:not found.
I have scoured the internet to find a solution to this problem and I can't seem to find any postings of someone else having the same problem. How do I get past this. Is there something I am missing? Please help!
in terminal or in adb shell... go to that directory to tmp
then do ls to check if rage is in there
so you would go
cd /data
cd /local
cd tmp
then
ls
and hopefully you should see rage in there if you do then try it again if you dont push it back in there
I tried your suggestion using terminal on my phone and it keeps telling me Is: permission denied. So I tried cd /data\local\tmp and it let me get to that point. then i tried the dir command and I get dir: permission denied.
hey, i recently rooted my desire z and i had that problem too
i found that if you don't do run this
Code:
$ adb shell chmod 0755 /data/local/tmp/*
make sure you run that before you type /data/local/tmp/rage in your terminal
I got it to work!! I am rooted. I finally realized that I had missed a space. I am about to flash my first rom!! YAAAAYYY. Thanks to all the hard work of others and their wonderful directions lol
I am going to root using the [GUIDE][30/06/2011]Root AND Downgrade Desire Z/G2(S-OFF/ClockWorkMod) -No Gingerbread topic to root. I have a question though regarding ADB as i dont want to brick my phone.
when it says :
Now you are ready to begin:
1. Open a CMD prompt window
2. Navigate your way to the folder with psneuter & misc_version IN CMD PROMPT. (So the cmd prompt window should be something like this C:\RootVision> )
3. Now we will use the following 5 commands one after the other
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
do i need to mount the phone or just do this:
Plug phone in
turn on usb debugging
navigate to folder
type in 5 commands or do i need to "register" or "identify" the phone that I want to move the psneuter for example to ? or do I just type in the commands without doing anything ?
so basically I dont need to connect to my phone it does it automatically.
in other words if I just plug my phone in and open up cmd and the first 2 commands are this:
cd C:/RootVision
adb push psneuter /data/local/tmp
Then psneuter will be 'pushed' to my phones /data/local/tmp directory ?
Sorry for the confusing post but trying to get my confusion across.
bump..................
As long as you are in the adb folder it will work by just entering the commands. If you feel more comfortable knowing adb properly sees your phone just type 'adb devices' in command prompt while in your adb folder. It should return something like 'HTC0098755432' or something with a lot of numbers, as long as it doesn't say "No Devices Found" then you're good
Edit: Also I seriously recommend the wiki here on xda for rooting, it's much more concise and provides links to everything you could need
Sent from my Bulletproof G2
PaganAng3l said:
As long as you are in the adb folder it will work by just entering the commands. If you feel more comfortable knowing adb properly sees your phone just type 'adb devices' in command prompt while in your adb folder. It should return something like 'HTC0098755432' or something with a lot of numbers, as long as it doesn't say "No Devices Found" then you're good
Edit: Also I seriously recommend the wiki here on xda for rooting, it's much more concise and provides links to everything you could need
Sent from my Bulletproof G2
Click to expand...
Click to collapse
I find the layout too hard on the eye. Would the topic I referred to work safely to root the desire z ?
If you find it hard on the eye, use the cyanogenmod guide
It's just a stripped down version of the xda wiki.
-Nipqer
trippinz said:
I find the layout too hard on the eye. Would the topic I referred to work safely to root the desire z ?
Click to expand...
Click to collapse
It would most likely work, although being a guide already 4 months out of date, I can't say for sure. What I am absolutely sure of is that the xda wiki or the cyanogen wiki pointed out by the post above me will work and work safely with little to no chance of brick as long as you follow the instructions. Ultimately it's your device to do with as you wish, we simply were pointing out guides that are tested and known to be good
Sent from my Bulletproof G2
[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)
Edit: This does not works on anything newer than ICL53F (i.e., 4.0.2). It works fine on ITL41D (4.0.1), ITL41F (4.0.1) and ICL53F (4.0.2)
Once you have got root, you can now use segv11's BootUnlocker app to unlock your bootloader without wiping anything. Easy as pie!
Disclaimer: I take no credit for this exploit or the implementation of it (but I will take credit for the step-by step ). Thanks to kendong2 for pointing it out to me here.
So, it looks like zx2c4 has found a local privilege escalation exploit. See source here, and saurik has managed to package it together for Android. See here. Although this may be old news to some, I hadn't seen it before.
So what does this all mean:
If you are running a 2.6.39 kernel (or above), which all Galaxy Nexus' are, you can now root your device without having to unlock your bootloader (and without losing your data).
Moreover, you should now be able to root your device even if your hardware buttons are not working.
Additionally, this allows those who have not received an OTA update and want to apply it without having an unlocked bootloader or root to do so by copying the OTA update to /cache from /sdcard.
Notes:
1) This assumes that you have USB Debugging enable on your device (Settings > Developer Options > Enable USB Debugging) and the drivers for your device installed on your computer. For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
2) This needs to be done over ADB, as a terminal emulator on-device does not have the appropriate access. If you do not have ADB, I've attached it in the zip. Unzip all files.
3) Some users indicate that, once finished the procedure, they needed to open the Superuser app.
Step-by-step:
1) Download the attached files to your computer and unzip them in the same directory as your adb.exe file;
2) Open a command prompt in the same directory;
3) Copy the files to your device:
adb push mempodroid /data/local/tmp/mempodroid
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
4) Open a shell: adb shell
5) Change permission on mempodroid to allow it to run: chmod 777 /data/local/tmp/mempodroid
6) Run the exploit: ./data/local/tmp/mempodroid 0xd7f4 0xad4b sh
Note: Once you do step 6, your prompt should change from $ to #. If not, it did not work.
7) Mount the system partition as rw: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
8) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
9) Change permissions on su: chmod 06755 /system/bin/su
10) Copy Superuser.apk: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
11) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
12) Mount the system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
13) Rescind root: exit
14) Exit the ADB shell: exit
15) Done. You now should have root without having to unlock your bootloader.
Reserved
Reserved
This is the same as https://github.com/saurik/mempodroid
saurik ftw.
times_infinity said:
This is the same as https://github.com/saurik/mempodroid
saurik ftw.
Click to expand...
Click to collapse
Not sure what you are getting at? I mentioned saurik in the first post, and the link you posted is in the first post. And I mentioned that this may be old news, but I haven't seen it anywhere before today in the GN forums.
Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!
Sleuth255 said:
Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!
Click to expand...
Click to collapse
You need ics to have a vulnerable kernel version, so given the number of devices which currently have ics officially, I doubt it will be common. I'd also expect Google and vendors to correct this in next release.
Also many custom kernels don't have this flaw as they are at or over 3.0.18 or have patched it. This prevents gaining unnoticed root.
Sent from my Galaxy Nexus
Hmmm I thought 2.6.39 was found in GB builds. This exploit is almost a root fix for the Moto DX 4.5.621 fiasco. Unfortunately the kernel for that build is 2.6.32.9.
Sent from my Galaxy Nexus using xda premium
This was huge in the headlines a few weeks back. It's nice to see someone putting it to a good use!
Sent from my Galaxy Nexus using xda premium
Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.
Huxleysäl said:
Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.
Click to expand...
Click to collapse
I think you are mistaken. In a terminal emulator type: cd /data/local/tmp
Edit: Fixed a mistake made by auto correct...
Sent from my Galaxy Nexus using Tapatalk
efrant said:
I think you are mistaken. In a terminal emulator type: cd /data/local/temp
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links
try /data/local/tmp
Huxleysäl said:
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links
Click to expand...
Click to collapse
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk
efrant said:
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb
Huxleysäl said:
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb
Click to expand...
Click to collapse
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk
OK, this is exactly what I did:
I downloaded the files, extracted them into the ./sdcard folder of my android. I opened the console, wrote exactly as stated. Reaction? Cannot create /data/local/tmp/mempodroid: Permission denied
So, what I'm thinking is this: I tried the cd ./sdcard/mempodroid, found it. So, logically, that should mean that since the permission is dennied, the problem lies not in where I put the mempodroid, but with my authority over my phone. So, here we are again. Could anybody smarter then me clarify?
efrant said:
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
****, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.
Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.
convolution said:
Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.
Click to expand...
Click to collapse
I hade my initial problems with that too. But as if this moment it doesn't really matter. Read above posts. Anyhow, to answer your question: you need to download a console emulator
Just search for it in the market. Also the commands go in this console
For example: cat /directory/filename > /newdirectory/samefilename means to copy or move from one place. To change permission you just write that line of code ending with 777 instead of cat and then the filename etc and etc.
I didn't know any of this 'till yesterday, so it is quite understandable.
cheers
Huxleysäl said:
F***, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.
Click to expand...
Click to collapse
I've updated the first post. Give that a go and let me know how it turns out. (The guide may need some minor tweaking, but I am here to help you through it.)
It seems that ADB has rw access to /data/local/tmp but a terminal emulator on-device does not. So for now, you need to be plugged into your computer.
It may be possible to do this with ADB-over-Wi-Fi, but I haven't gotten there yet.
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)