Related
ok so adb is installed and working however when I do "adb shell" I get $ not # and permission denied on everything I do. Phone is rooted via VISIONary, debug on, adb recognizes device and "ls" command gives proper read/ logcat works, any help would be AWESOME!
please don't be asses I would have posted this in the [SOLVED][ADB] Won't install correctly for my G2 thread but it's locked....
thanks in advance
Did you type "su" after adb_shell?
Yes and it just hangs...
Sent from my T-Mobile G2 using XDA App
Ok so I guess this one falls under the age old "have you tried turning it off and on again" method of dealing with windows... root access achieved.
Thanks for help KShatzkes....
Sent from my T-Mobile G2 using XDA App
So after 7 attempts, i decided i should seek help.
I've been trying to root my g2 using VISIONary r14.
1. I installed visionary r14 [i have usb debugging on] i leave all the check boxes unchecked and hit temp root
2. after temp root is finished, i hit attempt perm root.
phone reboots. i see superuser permission in the app drawer, all seems to be
fine.
3. Now I plug my phone to my PC via usb [i have the androidSDK and all drivers installed properly]
i change directory to C:\AndroidSDK\tools\
check adb devices and my device is listed.
then i shoot the following commands
adb push wpthis-OTA.ko /data/local/wpthis-OTA.ko
adb push hboot_7230_0.84.2000_100908.nb0/data/local/hboot_7230_0.84.2000_100908.nb0
adb shell
su
and this returns permission denied.
Ive searched everywhere and everyone says when the superuser prompt shows up check "Remember" and click yes. However this does not show up for me, at all.
I even go into terminal and try it, terminal also gives me 'Permission Denied'
any help anyone?
I'd just do it using the rage method. You obviously understand how to use some simple commands in adb, it's just that there's a few (read: not many) more. It's stickied in the development section.
Sent from my T-Mobile G2 running Cyanogenmod.
Yes rage way is the way to go. I think its a total of about 4 lines you need to enter
Sent from my HTC Vision using XDA App
yeah i ended up using the rage method, it was a lot easier than i thought it would be.
I did it using visionary r13 and terminal emulator. No pc. Go to youtube look up Blackprince310 he made a video on it. If it it doesn't work try permroot option on r13.
Sent from my T-Mobile G2 using XDA App
I would love to go the rage way, but I cannot get any permissions to do so...
Visionary r14 gives me a parsing error and does not install....
I've spent about 8 hours today trying to get this done!!! sigh!
Crey23 said:
I would love to go the rage way, but I cannot get any permissions to do so...
Visionary r14 gives me a parsing error and does not install....
I've spent about 8 hours today trying to get this done!!! sigh!
Click to expand...
Click to collapse
What steps have you taken? The rage way does not require visionary at all.
Sent from my HTC Vision using XDA App
shortlived said:
What steps have you taken? The rage way does not require visionary at all.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
right!!! I've been sitting at my pc for about 8 or 9 hours trying to root.
I continue to get adb: permission denied message no matter what I try. I follwed the adb for dummies guide that didnt work. I tried the VISONary r14 apk, I can't even open it.....
I'm beggining to wonder if I should run recovery first, get back to stock, and then try to root....how will that affect all my apps? Will it work?
Well you can always back them up with titanium backup. But yea i think you should do a factory reset then try the rage method. Follow the guide word for word. If you still got problems post em here i will try to help as much as i can. The whole process should take around 5min.
Sent from my HTC Vision using XDA App
I dont know how to link to a post with the xda app so here is the guide quoted
trigeek said:
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!
[size=+2]G2 ROOT INSTRUCTIONS[/size]
=================================================
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.
[size=+1]REQUIREMENTS[/size]
=================================================
Visionary disabled at boot or uninstalled completely
Android Terminal Emulator app
ADB
vision-combined-root.zip (Attached to this post, OR these two files: )
G2TempRoot.zip (http://forum.xda-developers.com/showthread.php?t=797042) NOTE: only download the files! Don't follow these instructions yet
vision-perm-root.zip (http://forum.xda-developers.com/showthread.php?t=833965) NOTE: again, just download the files from the thread.
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
[size=+2]VERY IMPORTANT![/size]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.
[size=+1]TEMP ROOT[/size]
=================================================
ON YOUR PC:
Unzip the G2TempRoot 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:
Launch Terminal Emulator
/data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
**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.
[size=+1]PERM ROOT[/size]
=================================================
ON YOUR PC:
unzip the vision-perm-root.zip and navigate to that folder. There will be four files. You will need to push two of these to your phone- hboot-eng.img, and one of the wpthis-[..].ko files.
If you HAVE applied the OTA update, push wpthis-OTA.ko.
If you HAVE NOT applied the OTA update, push wpthis-pre-OTA.ko.
Code:
$ adb push hboot-eng.img /data/local
$ adb push wpthis-OTA.ko /data/local
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Code:
# insmod /data/local/wpthis-OTA.ko
You should see:
Code:
init_module 'wpthis-OTA.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)
Code:
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
You should see some messages indicating that it was written. Next, run:
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!
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
i need help, i perm rooted my phone now it got stuck at the HTC start up! what should i do?? pls reply ASAP!
I apologize if this is already answered somewhere. I searched everywhere and could not find anything, but I might be using the wrong wording.
Anyways I am attempting to root my G2. I have managed to get adb onto the computer and it recognizes my phone. However, the next step in the wiki says to:
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/*
However, it gives me error messages such as 'adb' is not recognized. I'm sure I am missing stupid but I cannot figure it out. Thanks in advance.
Just use visionary, it is much easier. Click temp root and when it is done perm root
http://android.modaco.com/content/h...m/320722/19-nov-r14-visionary-one-click-root/
Sent from my HTC Desire using XDA Premium App
I don't trust visionary. I want to go about this the safest way which is the gfree method.
Sent from my T-Mobile G2 using XDA App
Make sure that the adb (and other stuff tha got installed) is in your PATH environment, or cd to that diectory and work from there.
Sent from my HTC Vision using XDA Premium App
o0olove said:
I don't trust visionary. I want to go about this the safest way which is the gfree method.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I used visionary and it worked just fine, but you do what you feel best with
Sent from my HTC Desire using XDA Premium App
bradley_e_smith said:
Make sure that the adb (and other stuff tha got installed) is in your PATH environment, or cd to that diectory and work from there.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I checked the path a few times because I thought that was the problem. However, it all looks good. I'm going to try on another computer tonight and see if that helps.
Did you make sure that all the necessary drivers were installed?
When you type 'ADB Devices' does it show your phone?
I used visionary and terminal emulator and haven't had any problems at all.
_________________________________
Sent from my CM7 T-Mobile G2 using XDA app
tazz9690 said:
Did you make sure that all the necessary drivers were installed?
When you type 'ADB Devices' does it show your phone?
Click to expand...
Click to collapse
Yes it shows my phone when I type 'ADB Devices' That's what's causing my confusion. I've reinstalled all the drivers that are needed. From what I am seeing it SHOULD work.
I am currently in the process of rooting my G2 and when i have to enter this command, (adb shell chmod 755 /data/local/tmp/* and adb shell /data/local/tmp/psneuter) i get no such file or directory everytime. All other commands enter in without a problem. What is chmod 775 anyway. it is the only thing not previously included in the rooting process. Can anyone please give me some feedback on what is going wrong here
thanks
What ever you are doing stop now.
You're doing that the hard way. Here's what u do goto theunlockr.com and then click how to's, then goto the g2 picture then u want to do the how to get temp root first then once that is completed do the permanent root tutotrial. Everything on theunlockr has a video and text so u can't f up.
My best wishes and if u need help like asap jus send a pm or email me [email protected] gmail
gamestar21 said:
I am currently in the process of rooting my G2 and when i have to enter this command, (adb shell chmod 755 /data/local/tmp/* and adb shell /data/local/tmp/psneuter) i get no such file or directory everytime. All other commands enter in without a problem. What is chmod 775 anyway. it is the only thing not previously included in the rooting process. Can anyone please give me some feedback on what is going wrong here
thanks
Click to expand...
Click to collapse
What guide are you following?
Sent from my T-Mobile G2 using XDA App
I'm stuck in the same place. I get operation denied every time...
Please help
A lot of people say its because you haven't set up the path correctly to the abd folder or haven't put the root files in the right abd folder.
Sent from my HTC Vision using XDA Premium App
Where to find 'chmod' answers
I had to exchange my G2. The one T-Mo sent is running Gingerbread(?) ver 2.3.4
I've been to theunlocker.com and in the procedure to downgrade so that I can root, http://theunlockr.com/2011/07/22/how-to-downgrade-a-gingerbread-t-mobile-g2-so-it-can-be-rooted/ two of the steps are to enter in terminal:
chmod 777 /data/local/tmp/fre3vo
and
chmod 777 /data/local/tmp/misc_version
When I do this I get 'chmod' is not recognized as an internal or external command, operable program or batch file
I have spent several hours in the forums and can't find where I've gone wrong or where to find 'chmod'
Someone please help me
SOLVED, use this link http://forum.xda-developers.com/showthread.php?t=1178912 and also (from one noob to another) it helps to type 'adb shell chmod....' if that is one of the issues you're having
You don't seem to be in the directory that you have adb installed. Change directory to there and you should be good
Sent from my Bulletproof G2
I've searched my entire hard drive, both mac & xp. It's not there. I've downloaded the SDK twice, I can't find it anywhere.
Sent from my T-Mobile G2 using XDA App
noflopscott said:
I've searched my entire hard drive, both mac & xp. It's not there. I've downloaded the SDK twice, I can't find it anywhere.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
On my xp it installed to c:/program files/android/android-sdk/platform-tools/ automatically, maybe try there. If you can't find it try downloading just the adb program and putting it in your adk platform-tools folder. You did also download the android development package right?
Sent from my Bulletproof G2
I went ahead and downloaded the ENTIRE sdk, from 1.5 to 3.3, did a hard drive search, still nowhere to be found :-c. Any other ideas?
Sent from my T-Mobile G2 using XDA App
noflopscott said:
I went ahead and downloaded the ENTIRE sdk, from 1.5 to 3.3, did a hard drive search, still nowhere to be found :-c. Any other ideas?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Are you even installing the SDK? Follow this guide to get ADB up and running: http://forum.xda-developers.com/showthread.php?t=865685
Sent from my HTC Vision using XDA App
This method worked http://forum.xda-developers.com/showthread.php?t=1178912
Followed it letter by letter and I was downgraded from 2.3.4 to 2.2 in just a few minutes :-D
hello all, i rooted my a100 via the guide, and the root checker says its rooted, but i cannot get into shell. When i enable filesystem browsing, it won't allow me. Not even a prompt from su.
Sent from my LG-P999 using Tapatalk
joeyxl said:
hello all, i rooted my a100 via the guide, and the root checker says its rooted, but i cannot get into shell. When i enable filesystem browsing, it won't allow me. Not even a prompt from su.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Did you install superuser from the market?
Im having a similar problem. I can verify that su has been moved to system/xbin/su but busybox nor Superuser detects root... Ive used all guides I can find to work this.
http://www.acertabletforum.com/foru...ssion/1167-rooting-iconia-a100-made-easy.html
Tried with no results
Did you update su binary?
Educate me, If you mean by trying to use superuser and update it through the settings, it was a no go.
I had a similar problem. It was showing as being in the /system/xbin folder, but I didn't have root. In my case, I was failing to move the su file out of the folder after extraction and put it in the /mnt/sdcard directory so the commands were just creating a blank su file in /system/xbin
Sent from my Acer Iconia Tab A100 using Tapatalk
How did you go about fixing the issue?
After extracting the zip I moved the su file (the one with no extension) from the extracted folders and tried the lines in the terminal again and it worked.
Sent from my Acer Iconia Tab A100 using Tapatalk
Ahh, Yea. Ive tried that already with no luck. It shows the file, roughly 25kb in the folder, but it also shows I have no root. Ive tried restarting, uninstalling superuser and reinstalling, etc...
did you ever get your tab rooted?
mvan4310 said:
Ahh, Yea. Ive tried that already with no luck. It shows the file, roughly 25kb in the folder, but it also shows I have no root. Ive tried restarting, uninstalling superuser and reinstalling, etc...
Click to expand...
Click to collapse
Could you post what build number your running, also after you've run the commands for copying over the su and download superuser from the market, if you open terminal emulator up and type su what does it output?
Have you tried this???
http://forum.xda-developers.com/showpost.php?p=21409649&postcount=177
painter_ said:
Did you install superuser from the market?
Click to expand...
Click to collapse
yes, after i did what the guide told me to do. i have the latest version of Honeycomb given out via OTA update. now in superuser, i didnt update it, as it fails evey time. also, when i type "su" into terminal, nothing happens. im trying to put the build.prop that was modded recently, so i can get an app made for gingerbread onto here, as well as getting a PS3 controller to connect, but both need root. i just dont understand why the root checking app says i have it, when i really dont. guess it just checks for the su file in xbin? i really hope someone can point me in the right direction
First, I really need to know the build number "the latest one the ota can give" isnt sufficiant. It can be found under settings -> about tablet toward the bottom.
Second, saying "nothing happens" isnt true.. something always happens... either it just spit out another line with $ or the next line showed up with a #. How long did it take for the next line to show up after you typed su in the terminal?
The more details you can provide, the better I can help... this isnt directed at the above poster but all users in general.
One thing you might want to try is to uninstall the superuser app, then run this command:
/system/bin/cmdclient ec_micswitch '`rm /system/xbin/su`'
and then go back through the root process (or use my quick root script). The above command will get rid of any bad su file that might be in /system/xbin.
Sent from my MB860 using XDA App
Build Acer_A100_2.007.04_COM_GEN1
Upon typing in su in the terminal, is shows another line with $. Ive tried your ten second root yesterday looking for other options, but it says permission denied, even when trying to run from other directories. Ive even opened the root.sh file and copied the whole file and pasted in the term and every command gives a permission denied but the 3 commands that you see everywhere else. when typing in ls -l /system/xbin/su I get around 26000 bytes. So the file is there.
mvan4310 said:
Build Acer_A100_2.007.04_COM_GEN1
Upon typing in su in the terminal, is shows another line with $. Ive tried your ten second root yesterday looking for other options, but it says permission denied, even when trying to run from other directories. Ive even opened the root.sh file and copied the whole file and pasted in the term and every command gives a permission denied but the 3 commands that you see everywhere else. when typing in ls -l /system/xbin/su I get around 26000 bytes. So the file is there.
Click to expand...
Click to collapse
Can you try the attached su binary. I don't recall where I got it from since is been a while but I've had issue with 2.3.2 su binary before and the attached is what I use to root mine.