[Q] ADB "Permission Denied" - myTouch 4G Q&A, Help & Troubleshooting

hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks

mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
You may have to run visionary and reboot a few more times to make root privileges stick.
My MyGlacier 4G MINE!!!

Try this:
: adb shell (this should give $)
:$ su (next line type su, this should give you prompt on Super user to allow permission)
:# ( once you get this your good)
Sent from my HTC Glacier using Tapatalk

Try to install visionary and then re install open click temp root then permoot super user should ask to approve click yes. After that restart
Sent from my HTC Glacier using XDA App

Please post questions in Q&A forum. Thank you

ok everytime i try adb shell in terminal emulator it says the permission denied, im gonna try the first reply again and then see....any other ideas?

also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.

mrpanic7 said:
also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.
Click to expand...
Click to collapse
Ok, go into adb shell and type su + enter. Watch your phone when you do this. Superuser should ask if you want to allow "unknown" root privileges. "unknown" is adb. Click allow and your problems should go away.
My MyGlacier 4G MINE!!!

So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G

Whats a test command I could try?
Sent via MyTouch 4G

mrpanic7 said:
So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G
Click to expand...
Click to collapse
I ran into this same issue and it drove me crazy. I would not get prompted by the phone to allow su permissions when going through ADB- kept getting "permission denied"
I did finally get SU permissions through ADB, but I dont recall exactly what I did to get prompted to allow access.
I will try to retrace what I did... believe I had ADB shell running (without su permissions "$"), but I also had terminal emulator running on my phone. I entered the su command on my phone, then I did the same from ADB shell.
Finally the phone prompted me to allow access - accepted - and no problems from that point.
Basically, I just had to keep f'n with it.

Yeah thats my problem exactly. Yeah I appreciate any assistance you can provide. I mean my pc reads my device when I adb devices command, but it wont allow nothing past that. Please keep me informed on anything I can try, also im not thag most fluent with using sdk/adb stuff so any additional info with using that is much appreciated thanks again fellow enthusiasts!
Sent via MyTouch 4G

Have you tried to bacup su, then uninstall su. Reinstall su, Then try it again. MIGHT work
Sent from my HTC Glacier using XDA App

yeah i re-installed su and didnt help, @dbiggs-what can i do thru adb to initiate the su permissions to the device like you did?

I wish I could help more specifically, but I dont remember exactly what I did that allowed me access- just kept trying
Maybe try this...(dont be offended if any of these steps are ones that you already know or have tried, I am just trying to be as thorough as I can from memory)
Open up super user, then go back to the terminal emulator and enter the "su" command to gain superuser permissions.
Plug the phone into the computer, select charge only, enter ADB through tools (probably "C:\Android\tools" if your Android folder is in the root of your harddrive).
from the prompt C:\Android\Tools, enter:
adb shell
then you will get the "$" that you mentioned.
enter the "su" command, and hopefully you will get prompted to allow superuser permissions for ADB.
I am pretty sure these are the steps that I took, just had to keep trying.
Lemme know how it works out.

I see some people here asking about getting su privileges in adb, however I do have SU and I can run su in adb shell. My problem is that I am trying to push some files and use Android Commander. I can't run "adb remount" (remount failed: Operation not permitted), I can't copy files in Android Commander (it's says that I do not have ROOT)
How can I get Read-Write in ADB ??
Edit: Oh, now I got it, I don't have root in ADB, when i type "adb root" it says "adbd cannot run as root in production builds"

Did anyone figure this out? I'm being denied on TE and PC also.

I have managed to be able to get around this issue by going into recovery mode on my phone.
If the end result that you are looking for is to adb push files, then the easier way to do this is to flash clockwork recovery to your phone, then start your phone into recovery mode, mount system and you should be able to push files no problem.
Lemke know if this helps.
Sent from my HTC Glacier using XDA App

mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
I'm pretty sure your issue has nothing to do with SU access. Most likely, your phone is simply mounting as r/o (read only) when it boots up, so ADB is unable to change anything to the system folder. The easiest way to mount as r/w (Read/Write) is to go into Root Explorer and click the r/w button in the top right corner, and then go to ADB and see if it will allow you to do the same commands that it previously denied.
I have the same issue with my phone mounting as r/o by default, but I haven't been able to figure out how to automount as r/w on the MT4G. If anyone knows how, please share.

I had this same issue, on several android phones including MT4G. Here is how I fixed it.
1. Connect phone via usb (I was in "charge only" mode, not disk drive mode)
2. Open command prompt and navigate to the android tools folder
3. type "adb shell"
4. MAKE SURE YOUR PHONE SCREEN IS ON AND UNLOCKED
- The above step is very important otherwise you will not get the SU prompt
5. At the "$" prompt type "su"
6. Your phone should now display the SU screen asking you to allow the connection root access.
7. Once you allow it, you are golden.
I did this on a windows pc. Hope it helps.

Related

[Q] Rooted but adb says I am not?

I searched around several threads and saw a few people with the same issue but no fixes.
I rooted my phone using this and it worked great.
I then installed clockwork manager from here and then installed the clockwork recovery and made my nandroid.
So far so good.
I booted up and then checked the terminal emulator app i had installed and did:
Code:
$su
and got
Code:
#
So, all good.
I then went to remove some of the bloatware by using adb.
When I do adb shell I get the $ prompt.
I type in "su" without quotes and after a few seconds i get "Permission denied".
Seems like i fudged something somewhere but I am not sure what.
Anyone able to offer some constructive help?
Make sure your phone is unlocked when you type su in adb shell, and a superuser permission should pop up.
many thanks for that!
i have been on a rooted G1 with CM for so long that i forgot to even look at my phone when i "adb shell...su" into it =)
did it just now and looked at the phone and the superuser permissions window came up. all set.
thanks again!

s-off but not super user acces!? help please :)

hey well i got to this point :
# # /data/local/tmp/root
Click to expand...
Click to collapse
anyhow when i run this it says:
cp: can't stat '/sdcard/superuser.apk': no such file or directory
then is the same but with su
Click to expand...
Click to collapse
i went ahead and put sync anyhow and when i restart and run 'su' but is says: unknown user root
any ideas what i did wrong? :/
oh and btw somehow i have S-off...
i followed each step, but i just notices this... for some reason it wont let me push superuser.apk or su, all of the other files can be pushed... any ideas?
no one?
http://www.youtube.com/watch?v=tU9zn_BEth4 i did that way and it works for me.
but i have s-off i supposed to be rooted already but i do not have super user powers... what do i do
Did you copy the Superuser.apk file to the root of your SDcard?
yes i did, and su too and now when i put su on my phone it says unknown user root :/
i can get temporal rooting tough.
Use visionary r13 ... had same issue... worked for me
Get it from pauls visionary thread on Modaco.
Sent from my HTC Vision using XDA App
i had the same situation with u few days ago. just follow http://forum.xda-developers.com/showthread.php?t=834228 and u only need do the temp root part.
Delete visionary and superuser first, install terminal emulator from market.
on you pc:
$ 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/*
Then on you G2, open a terminal emulator
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----- run the /data/local/tmp/root script here.---sync.
In the last step, u can find the origin thread dose not let u do this. but, if you've got s-off, trust me, just do the last step "/data/local/tmp/root", and when u see a feedback "****files exist",then "sync",
I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions
u can also do what i suggested in the 8th floor.
o>c said:
I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions
Click to expand...
Click to collapse
r u rspt in Gfan? since u can read chinese, just look at here. http://www.hiapk.com/thread-631413-1-3.html
I made this thread to help solve such problem.
After I got S-off, I didn't have root either. I just jumped on visionary (made sure run on boot wasn't checked), clicked root now. And boom, that was it. Then I deleted visionary and I've had root ever since...

Having trouble rooting on Windows 7 64bit

I am having a bit of difficulty rooting my g2. I am not sure if its related to my os or not but i can not get it to work.
I have followed this and tried it all kinds of different ways.
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/[/url]
I can get to my run command after doing all of that and it shows my serial number after typing adb devices but after that i can't enter any info in the sdk run command promt.
I have not been able to gain temp root yet because it won't let me enter the commands. I went to try to re-install java/sdk manager yet again and now it says java is not in the right path.
Any help?
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
martonikaj said:
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
Click to expand...
Click to collapse
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
901-Memphis said:
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
Click to expand...
Click to collapse
Yep let me grab a link for you (theres actually a video tutorial I wanna try and find). But basically instead of using ADB to push the files to the correct location, you just have to manually put the files in the right locations on the SDcard, which is where ADB pushes them anyways.
K so I followed this method: http://www.youtube.com/watch?v=tU9zn_BEth4
The files he refers to are in this thread: http://forum.xda-developers.com/showthread.php?t=833965
Now different people have had different issues with this. I personally had some issues where it tells you to run #sync, because my perm root wouldn't stick properly after reboot. If this doesn't work properly, I'm sure someone can help you with your drivers to get ADB working.
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
If you got the adb devices command to work you are actually in good shape. You are supposed to enter all of the commands from what you are calling the "run command" prompt anyway (the one you used for adb devices).
martonikaj said:
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
Click to expand...
Click to collapse
Unfortunately this won't work (if you don't want to use ADB, Visionary must be used to get temp root). ADB is needed in order to push the files directly to the phone. If you try copying the files to the SD card first, you won't have the correct permissions to copy the files to the phone in Terminal. You are also not allowed to execute programs directly from the SD card (mounted as noexec), so you can't try to obtain temp root from there. If you want to use the gfree method of rooting without using ADB, I made a guide using Visionary for the temp root here: http://forum.xda-developers.com/showthread.php?t=928160.
But the OP actually has ADB working, so he should be able to use any of the guides.
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Uploaded with ImageShack.us
901-Memphis said:
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Click to expand...
Click to collapse
You are supposed to be using the regular command prompt (I think you referred to it as the "run command prompt" earlier). It is the prompt in which you successfully ran the "adb devices" command. That is the only prompt you need to use.
Do i enter commands 1 at a time or all at once?
901-Memphis said:
Do i enter commands 1 at a time or all at once?
Click to expand...
Click to collapse
First off, Yes you enter each line as you see it.
Second just to make sure you are in the right area to enter these commands, to get to command prompt you can either search for it from the start menu or hold the "windows button + R".
That opens your run command from there type in "cmd" and that opens command prompt.
Next make sure your current directory is the one you installed adb into. To get to that you can type "cd C:/...... whatever folder you installed it to."
To make sure my adb is working I usually type "adb devices" and see if my phone shows up.
Good luck
Glad to see someone else from the good ole 901 around here =)
Sent from my HTC Vision using XDA App
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
901-Memphis said:
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
Click to expand...
Click to collapse
try pushing the file to that folder again
Re-Tried everything at least 3 times, including pushing the files that didn't go.
I give up Ive spent so much time on this only to have it fail at the most unlikely times.
Will wait for another method to root come available
You could try downloading and installing Droid Explorer. It installs adb and fastboot files in its install folder.
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
ianmcquinn said:
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
Click to expand...
Click to collapse
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
901-Memphis said:
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
Click to expand...
Click to collapse
You are supposed to do that command from your computer. (The instructions state "On the computer, open terminal and type the following commands".) Here, terminal means the command prompt that you've been running all of you other ADB commands from.
If you wanted to run the command from terminal on your phone, you would just type "chmod 777 /data/local/gfree".
You don't need ADB for G2s.
trance2315 said:
You don't need ADB for G2s.
Click to expand...
Click to collapse
Can someone link me a better guide for my G2 so that i can try this 1 more time ?
Maybe a link to the top choices for versions of android to run once i get it rooted?

[Q] Command Prompt Issue When Trying To Exit ADB Shell?

Hi this is my first post on the site and i would appreciate it if anyone could help me with this problem. (I know your probably fed up of hearing about rooting problems but anyway!)
I have succesfully installed ADB and as far as i know it seems to be working properley as i can access the ADB shell on my device.
However when i get to a certain stage of the rooting process it all seems to go wrong.
wiki.cyanogenmod.com/index.php?title=HTC_Tattoo:_Full_Update_Guide
I have been using the above rooting guide (can't hyperlink first post!) and i cannot get past stage 7 of the process because the 'exit' command doesnt seem to work in Command Prompt (Windows 7) and it is stopping me from being able to exit the ADB Shell. I have tried other ways of exiting the shell such as ctrl+C but this kills ADB completely and i think that it is undoing the previous steps of the guide.
I do get the message:
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
so i think that i have successfully rooted the device but i cannot proceed to push the 'su' file to the device as i can't exit the adb shell, i just keep getting lists of text saying reboot (-n) (-p) and everytime i use the exit command nothing seems to happen and the flashing # symbol keeps coming back.
Has anybody else had this problem? or have any idea of how to stop the ADB Shell with any other commands other than 'exi't or Ctrl+C?
Cheers.
If device is rooted, by writing in command prompt the command "adb shell", must appear the symbol #, if the symbol $ appears the device isn't rooted.
If you cannot use adb from pc, run on device a terminal emulator(you can find one on market) the above command to see if you're rooted. Then you can give the next commands from terminal emulator(maybe you need to copy the nessecary files on sd card and change the related paths to point to sd card)
I'm having the exact same problem while rooting my HTC Tattoo (on Windows 7).
I have Android 1.6 (Donut), the baseband is 13.29a.55.13H_3.35.07.33, kernel is 2.6.29-gf922713 and build is 1.67.173.37.
Please help and thanks in advance . I really want to install CyanogenMod 7...
more info
When i say i have rooted the device i mean temporarily by pushing and changing the 'm7' file, the problem is pushing the 'su' file to the device to make the root permanent.
I do get the # symbol when in ADB Shell but only after changing m7 on the device. As i cannot complete the whole rooting process the # is not there permanently and it returns to the $ symbol.
Thanks for the reply, i will try and do it using a terminal on the device. Do you not need root access to use a terminal app?
I'm having the same issue. When I input exit it stucks into that loop and then I got to ctrl+c, and of course the root does not stick
From that point forward I can't do anything else...
If someone overcome the problem please post.
I just used this app to root a zte blade with a new greek stock rom:
http://forum.xda-developers.com/showthread.php?t=803682
Seems to work for almost all devices and in first post have some info about root levels and links to a workaround for devices that have some lock which prevents the full rooting.
I didn't tried anythink cause the rooting process was successful, but you can try this app and if still have problems try to follow the instructions given.
Good luck.
If you have your mobile rooted can you just use this commands:
cd /data/local/bin/
chmod 755 flash_image
flash_image recovery /sdcard/recovery-clockwork-x.x.x.x-click.img
to perform a recovery flash? Without using the su command?
I don't remember if I tried it, but, if it works I recommend using Androot for rooting the device, it worked for me(checked by Root Checker ).
I'm mentioning this just because you recommended the SuperOneClick app.
Update:
For all trying to get thing done, follow the instructions on 1Click modified by tenis and flash the latest cyanogenmod.
It worked!!!
I got it to work using androot. Cm7 is awesome
Sent from my HTC click using XDA App
exit command in adb seems to lock up
like omgsufc, I also reach this stage and can see the message:
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(a db),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt ),3003(inet)
Again, like omgsufc, when I issue the command:
# exit
ADB shell seems to go into some kind of loop. Pressing ctrl-c or ctrl-d also give the same results. I thus can't go to the next stage. Any help or clues would be greatly appreciated.
I'm on Ubuntu 11.04.
TIA for any help.
Finally got it to work
No matter what I did, rooting using m7 just didn't work for me (Ubuntu 11.04). Running 'while ./m7 ; do : ; done' got me temporarily rooted as issuing 'id' shows me at 'uid=0(root)'. However, issuing 'exit' just left me in a long loop in the terminal from which it never recovers, and hence I could not complete the root process this way.
So I tried androot, which appeared to root me right away. Issuing 'su' in Android Terminal worked, and doing the same in ADB Shell also gets me to the # prompt. However, issuing the 'flash_image recovery' failed no matter what I did. I tried ROM Manager after this initial androot root: it gives me a success message after flashing ClockworkMod recovery, but when I reboot into recovery it just fails. Fastboot also failed consistently.
Finally, when I tried Terminal Emulator to get root access by issuing the command 'su', it says permission denied, even though Terminal Emulator gave me root access.
So... I unrooted Androot. Again trying to root using m7 I got the same problems as before.
I didn't bother trying flash_image or fastboot and instead tried rooting with androot. After doing so, this time Terminal Emulator allowed root access, which gave me some hope.
So I pulled out ROM Manager again, and woot! My Tattoo is on CyanogenMod 7 and am I a happy camper! I like what Cyanogen has given us: ADW Launcher is as good for me as Sense ever was... actually it's better. And finally I get to use all the new apps I've been wanting to use but wouldn't run on Android 1.6.
So thank you Cyanogen, thank you xda-developers, particularly KalimochoAz, thank you Koushik Dutta for ROM Manager, and thank you, whorever developed androot!

[Q] Questions galore on rooting MT4G!

Hi everyone,
I have a MT4G, 2.2.1, kernel 2.6.32.21-g899d047. I am using Windows 7 Ultimate 32-bit.
I want to root the phone but I am meeting a lot of permission issues.
I have been following this guide: http://wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide
At the very beginning, I had problems with su and Superuser.apk.
I have used 'adb devices' to check that my phone is indeed detected.
I put su and Superuser.apk into the same directory as
When I use 'adb push su /sdcard/su', I receive an error saying 'Failed to copy 'su' to '/sdcard/su': Permission denied. Same error for Superuser.apk.
I looked further down the guide and noticed that I would not actually be using the su and Superuser.apk at all and simply copied it over to the SD card itself when I plug the phone into my computer.
I then go into terminal emulator on the phone and I run rage and received the 'Forked #### childs' message, after which I reset term.
I assume I have root shell at this point because I am no longer on $, but instead on #.
At this point, I am able to adb push gfree (the one file gfree) into /data/local. I am able chmod 777 from adb.
When I go into terminal emulator again, I run '/data/local/gfree -f' but it gives me the error message of '/data/local/gfree: permission denied'
What am I doing wrong? I used 'ls -l' inside the directory of /data/local and I have complete rights for gfree (drwxrwxrwx).
----
I have also attempted to use VISIONary+ (R14) but all it does is flash a couple of times then go back to the app page where you choose to temproot. I check my app drawer and Superuser is indeed there, but if I tried to go into terminal, I am met with $. I tried entering 'su' but it would say unknown user root.
----
PLEASE HELP! THANKS!
Use this method. It's pretty much fool proof.
http://forum.xda-developers.com/showthread.php?t=858996
Are you temp rooting with visionary before entering the commands in terminal?
lowandbehold said:
Are you temp rooting with visionary before entering the commands in terminal?
Click to expand...
Click to collapse
i can haz 10 char
neidlinger said:
Use this method. It's pretty much fool proof.
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
lowandbehold said:
Are you temp rooting with visionary before entering the commands in terminal?
Click to expand...
Click to collapse
As mentioned in OP, I am using the rage file to give me temporary root. I am currently not using VISIONary because (also included in OP) I am not getting root shell at all with VISIONary. I click temproot in VISIONary and the superuser app shows up but I am unable to su in Terminal.
Try to find visionary 11, people have alot of problems with 14.
neidlinger said:
Use this method. It's pretty much fool proof.
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
Having trouble at step 1..
'adb push gfree /data/local'
Met with the error 'Failed to copy 'gfree' to '/data/local/gfree': Is a directory'
I extracted the files into platform-tools.
Didn't you already put gfree on your phone from the first attempt?
lowandbehold said:
Didn't you already put gfree on your phone from the first attempt?
Click to expand...
Click to collapse
Yes but I was attempting to follow a whole new guide. Regardless, I have shell root but I am still unable to run gfree. It still shows permission denied (again, using ls -l, I can see that gfree is drwxrwxrwx).
Use visionary 11. I have rooted 4 MT4G's with that guide and visionary 11...It works.
before you attempt a new rooting method please pull the battery and let the phone sit for a few moments. Since your s-on it will delete any unwanted files that you may of tried to push to the phone.
and type in
Code:
adb kill-server
adb start-server
That will refresh the adb server on your computer.
you'll also need to change the directory to the folder where you stored the gfree files.
double post...sorry
lowandbehold said:
Use visionary 11. I have rooted 4 MT4G's with that guide and visionary 11...It works.
Click to expand...
Click to collapse
Yeah, I'm using visionary 11. Still no good.
Are you checking the boxes in visionary and clicking temproot? I don't know what the issue could be...you must be missing something.
lowandbehold said:
Are you checking the boxes in visionary and clicking temproot? I don't know what the issue could be...you must be missing something.
Click to expand...
Click to collapse
I have 'Set system r/w after root' checked. I don't need to check 'Run visionary.sh' and 'Root on boot', do I?
itzbilly said:
I have 'Set system r/w after root' checked. I don't need to check 'Run visionary.sh' and 'Root on boot', do I?
Click to expand...
Click to collapse
RUN VISIONARY.SH : Yes
root on boot : no
neidlinger said:
RUN VISIONARY.SH : Yes
root on boot : no
Click to expand...
Click to collapse
Tried with those settings and now I've lost root shell. I'm on $ and entering su gives me unknown user root.
VISIONary says device is rooted when I try to run it again.
I would check the root on boot, reboot, uncheck it, go into terminal and put in the su command and see what happens...your phone will be really laggy when you boot it up, so give it a minute, it is normal.
lowandbehold said:
I would check the root on boot, reboot, uncheck it, go into terminal and put in the su command and see what happens...your phone will be really laggy when you boot it up, so give it a minute, it is normal.
Click to expand...
Click to collapse
Do i uncheck and then reboot or just uncheck and go straight into terminal?
check everything including the root on boot. Reboot the phone. Then you can go straight into terminal or uncheck it and go into terminal..doesn't matter. Just make sure before you reboot a second time that root on boot is not checked.

Categories

Resources