Database Users

Missing SU!

So here's an odd one i can't put my finger on.
So i used the RUU to go back to stock unrooted, to install the leaked OTA for the radio update. It all worked properly.
I used unrevoked3 to root the phone again. Also worked perfectly.
When using a terminal emulator on the phone i can issue the "su" command and all is well, however when i reboot into recovery and try to issue the "su" command it wonderfully tells me that it cannot find the "su" command.
What step did i miss guys, i've been over this a few times, now trying to get things pinned down, but i just can't figure this one out.

obsidianblackhawk said:
So here's an odd one i can't put my finger on.
So i used the RUU to go back to stock unrooted, to install the leaked OTA for the radio update. It all worked properly.
I used unrevoked3 to root the phone again. Also worked perfectly.
When using a terminal emulator on the phone i can issue the "su" command and all is well, however when i reboot into recovery and try to issue the "su" command it wonderfully tells me that it cannot find the "su" command.
What step did i miss guys, i've been over this a few times, now trying to get things pinned down, but i just can't figure this one out.
Click to expand...
Click to collapse
You are fine. By default, you are already SU in an adb recovery shell, if booted into CWM. If you want to actually do things with SU, you want to mount your system partition.
Oh, and BTW, this belongs in general.

ah ha that's what i was missing. Thanks!!!!
MODS: Can someone please move this to general.
Edit: Interestingly enough, i have mounted the system partition in recovery, and am still getting the same error. /sbin/sh: su: not found.

There should be no need to execute su in recovery as you are already su when in recovery (as shown by the hash sign at the prompt, #).
What is it you're trying to accomplish? Try doing it without explicitly using su as a command?
Sent from my ADR6300 using XDA App

bcgaynor82 said:
There should be no need to execute su in recovery as you are already su when in recovery (as shown by the hash sign at the prompt, #).
What is it you're trying to accomplish? Try doing it without explicitly using su as a command?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
lolol, linux on a desktop i can handle. Linux on a phone for some reason though is confusing me. I did end up trying to do what i was after without issuing a su command and whoa it worked. Thanks for the advise.

S=ON but still can't stock unroot

hi i recently rooted my mytouch4g but know i want it back to stock OFTB
s=on in hboot but the pd15img.zip said no image
i have repeat tons of time but nothing
root phone by:
visonary temp root then i did perm root gfree for s=off steps was
gfree moving files to data/local/ with root explorer
then i did the commands for gfree and s=off
now thats what i did for root s=off
CWM = 3.0.0.5
now am running ice glacier (newest)
i did the unroot Automated way to unroot your myTouch 4G (difficulty level 1) method by jjjackson56 and got s=on
1. To use this simply download the zip and extract the two items to the root of your sdcard (ones a folder and ones the PD15IMG)
2. Open terminal and type
su (press enter)
cd /sdcard/unroot (press enter)
sh unroot.sh (press enter
3. Let it work.
after it did its thing and try to reboot itself it couldn't said that reboot: no such tool
so i reboot myself to hboot by vol+power
but the phone doesn't flash hboot did not find it said no image and i have the pd15img in my sdcard root
can anybody help

Can you verify that your PD15IMG is named exactly "PD15IMG.zip" and not "PD15IMG.zip.zip" or something similar? If it is, possibly try a different sdcard if hboot still won't detect the file.

Yes the file name is correct no double zip and I trade with a different card didn't work

What error are you getting in hboot? Does it display the messages of searching for an image then that it can't find one, or what?

Be sure that the file is on the root of the card, and not in another folder.

Yes its on the root of my sdcard not in any folder just like glacier Rom am using right now and when it search in hoot it says no image to all 4 search

is it my hboot version is 86

ok i found the problem i know its noob
but for noobs make sure u make sure your sdcard is fat32 format
or it will not work THX BYE!

[Q] Problems getting perm root s=off on MT4G HELP!!!

I have been trying to perm root (s=off) my MT4G using the visionary method on the xda perm root procedure (s=off) threads and I can't for the life of me get it to work? I have a MT4G with 2.2.1 and HBOOT -0.86.0000.
I have run visionary r14 and run the su commands outlined in the procedure and the root.sh script runs fine and when I power down and reboot into hboot, I keep getting s=on??
I have rooted a couple of MT4G phones in the past and I am stumped. I have tried running visionary 3 times then running the su commands and root.sh script and still get s=off.
Any help would be greatly appreciated please. I almost at the point of tossing it in the toilet.

Have you rebooted and then run visionary again to gain temp root and then ran visionary to gain perm root?? Once you do temp root in visionary, go into terminal and run the root.sh command and reboot, it was only temp rooted so you have to run temp root and then perm root in visionary again and it should stick...

I have tried the following procedures with no success:
Run visionary r14 to get temp root
Goto terminal and run change directory commands to run root.sh script
Script runs fine and tells me to power down and check for s=off
I power down and boot into HBOOT S=ON
Phase two:
Run visionary r14 to get temp root
Run root.sh script in terminal
Run visionary r14 and run get perm root
Visonary tells me superuser was granted, screen goes black and reboots
I run terminal and try su command and "access denied"
I try and boot into hboot and S=ON
Phase Three:
Run visonary r14 to get temp root
Run root.sh script in terminal, tells me to reboot into hboot and check for s=off
I reboot
I run visionary again to get temp root
I run visonary again to get prem root, visionary runs and phone reboots
I run terminal and try su command "access denied"
At this point I am fustrated, I have rooted a couple of MT4G phones in the past and never had this hassle before.
I have followed the procedures to the letter, double check the files I downloaded, What am I doing wrong?

http://forum.xda-developers.com/showthread.php?t=858996
try this one....worked for me on hboot 0.86.0000

Are you checking "set system r/w after root?"
Is usb debugging enabled?
Is fast boot disabled under apps settings?
If you're doing everything right and it fails, use the gfree method linked in the post above mine.

This might help you out its what i did and im on hboot 86,
Follow that gfree method, and afterwards go into visionary r14 and go for a temproot And then a permaroot and your phone should reboot and you should be good... I did this because even with s=off i still had permission issues.

Same issue, with HBoot 86. So going through the gfree method is the only way to obtain S-Off then?
I thought I was losing my mind, using the tried-and-true Visionary+ and Terminal route. I tried it seven times: "S-ON"...
Thanks for the tips. Please update this thread with any new info.

Hboot 0.86.0000 has nothing to do with it. All MT4Gs ship with this bootloader. You get Hboot 0.85.2007 either by flashing manually (as per the instructions in the gfree thread) or if you used the root.sh script (such as by following theunlockr.com's video walkthrough).
If VISIONary is giving you temproot, you should be able to do either the gfree script or the root.sh script (your choice, I say use gfree), and then you can permroot with VISIONary. If that's not working, wither you haven't followed the directions properly or something else is interfering, in which case more information is needed to help you.

The gfree way is the way to go. With the walk through under the development thread, it is pretty much dummy proof. I just rooted my buddy and his wifes phone last night using that method.

did i loose my permaroot?

when i install roms, and i have to do all the wiping of the data, devlik and so on, does this mean i have to reroot my phone? ive done the TRUE PermaRoot and the ULTIMATE S=Off!!!

gd6noob said:
when i install roms, and i have to do all the wiping of the data, devlik and so on, does this mean i have to reroot my phone? ive done the TRUE PermaRoot and the ULTIMATE S=Off!!!
Click to expand...
Click to collapse
untill you turn s-on you will not lose the SU access. once you do that you need to reroot.
But rooting takes all of five mins so you shouldn't really fret about it anyways.

when i hold the volume down + power, i cant go into the mode...
when i try to reroot, in terminal it failed on me...
i have SU access, but just wundering if i need to go back into the mode where you hold the volume down+power...

gd6noob said:
when i hold the volume down + power, i cant go into the mode...
when i try to reroot, in terminal it failed on me...
i have SU access, but just wundering if i need to go back into the mode where you hold the volume down+power...
Click to expand...
Click to collapse
Step by step what did you do to root your phone, and get to where you are now.

when i first did it, i followed the Truperma root and it was successful..
after i wiped all data and what not, to install a rom, i cant get back into that mode..
so i followed that guide again,
used SDK and pushed gfree to /data/local
then i open visionaryplus and did the temproot (tried 2 times, once without temproot and once with.. the guide said i can skip this step...)
then open terminal
su
cd /data/local
chmod 777 gfree
./gfree -f
showed some stuff and the last few lines read fail something and unable to make folder or something....

Ok neidlinger..you win...some people should not root their phone.
Now back to the matter at hand. It would be really sweet if you could get into that volume down power down screen thingy.

[Q] recovery flasher doesn't work

Hi All,
I installed Androot and recovery flasher and tried to update/backup the recovery.
But i can't. I only got message "backup failure".
As I understand i have to give root permissions to recovery flasher but androot don't ask me when recovery flasher start.
I'm sure, androot works because I give "root" to terminal and adb.
Can I give root manually? Or is any other options?

paganelle said:
Hi All,
I installed Androot and recovery flasher and tried to update/backup the recovery.
But i can't. I only got message "backup failure".
As I understand i have to give root permissions to recovery flasher but androot don't ask me when recovery flasher start.
I'm sure, androot works because I give "root" to terminal and adb.
Can I give root manually? Or is any other options?
Click to expand...
Click to collapse
Hi.
There are a few things we should check, and a few things to try.
1) Try running Androot again and see what happens. Does it say "already rooted" or anything else?
2) When you look at the list of installed apps, do you see the "Superuser" app? If you don't, you'll have to root the phone again and install Superuser.apk before you reboot. If you do see Superuser, open it and check the history and the settings. See if your backup app is listed in the logs.
3) Connect the phone to your PC and open a Command Prompt. Run "adb shell", then try to run "su". If you get "Permission denied", you aren't rooted, or Superuser hasn't been granted root privileges; look at the phone's screen to see if it asks you to "Allow" or "Deny" granting privileges.
4) Try SuperOneClick. I'm not positive, but I think they stopped development of Universal Androot (let me know if I'm wrong about this). SuperOneClick works through adb, so make sure "adb devices" lists your phone when connected to your PC. Download and install SuperOneClick, run it (as Administrator if you use Windows 7 or whatever), and click the Root button.
Once you've tried these steps, we'll have a better idea what's going on. It's possible that you were only given temporary root and it disappeared after a reboot. *shrug*
Let us know what happens. Cheers.

1. It says "already rooted"
2. Yes I see "Superuser' and 2 "rooted" applications "Terminal emulator" and "Unknown". "Unknown" appeared after I connected to the phone by adb shell su bla-bla.
3. See above. It was as you described.
4.Ok. I'll try!
DasBub said:
Hi.
There are a few things we should check, and a few things to try.
1) Try running Androot again and see what happens. Does it say "already rooted" or anything else?
2) When you look at the list of installed apps, do you see the "Superuser" app? If you don't, you'll have to root the phone again and install Superuser.apk before you reboot. If you do see Superuser, open it and check the history and the settings. See if your backup app is listed in the logs.
3) Connect the phone to your PC and open a Command Prompt. Run "adb shell", then try to run "su". If you get "Permission denied", you aren't rooted, or Superuser hasn't been granted root privileges; look at the phone's screen to see if it asks you to "Allow" or "Deny" granting privileges.
4) Try SuperOneClick. I'm not positive, but I think they stopped development of Universal Androot (let me know if I'm wrong about this). SuperOneClick works through adb, so make sure "adb devices" lists your phone when connected to your PC. Download and install SuperOneClick, run it (as Administrator if you use Windows 7 or whatever), and click the Root button.
Once you've tried these steps, we'll have a better idea what's going on. It's possible that you were only given temporary root and it disappeared after a reboot. *shrug*
Let us know what happens. Cheers.
Click to expand...
Click to collapse