Database Users

rooting problems

hey. i have no clue why but my g1 isnt get rooted. ive did everything in the unlockrs step if you go to theunlockr.com. everything went successful and exactly what his did but when i go to terminal and type su it says permission denied.when i power on using camera and end it goes to android on skateboards(i doont not that matters). anyone have any ideas

mr.johnsexydavis911 said:
hey. i have no clue why but my g1 isnt get rooted. ive did everything in the unlockrs step if you go to theunlockr.com. everything went successful and exactly what his did but when i go to terminal and type su it says permission denied.when i power on using camera and end it goes to android on skateboards(i doont not that matters). anyone have any ideas
Click to expand...
Click to collapse
I followed the unlockr's steps to help David test out his new guides, and I never had a problem. If your going into terminal and typing "su" and getting the permission denied message, that means everything DIDN'T go successfully. The skating androids when in bootloader means that you have an SPL that allows you to upload custom ROMs but says nothing about whether you have root. Follow the steps again paying particular attention to each one.

If you really want to root your phone easily and without problems or confusion, follow this guy's instructions:
http://www.youtube.com/watch?v=xOo2V9qCauc

[Q] Is my Wildifire really rooted?

Hi guys,
I used unrevoked2 to root my phone.
I have the Superuser app and everything seems fine.
I wanted to use the patch to see all the app in the market, but when using the terminal from my mac I try to mount, it says permission denied.
I read somewhere that it could be the Superuser app that doesn't work properly. So I tried to update it, but when I download it from the market is says "Package file was not signed correctly ". I tried to follow the instruction in the thread of Superuser but again I can't mount or delete the previous application.
On another forum I read that when the phone is rooted, when rebooting in HBOOT it should say S-OFF, but mine is S-ON.
So the question is, is there something wrong in my rooting? Is there something wrong elsewhere?

im not a big pro but...
isnt unreovked3 is the oldest version that can root a wildfire? Oo

I'm pretty sure that only unrevoked3 works on the wildfire, not unrevoked 2 as they updated it for the wildfire.

Thanks for your reply.
I used unrevoked2 because on their website they say that they are working on same bugs on the 3rd and that is possible to use unrevoked2. Unrevoked3 is not available for download.
I'm looking for the mac version on the internet but I still haven't found. If you have a source it would be helpful.

Looking carefully it seems that I actually used unrevoked3 since I downloaded from here ->unrevoked.com/rootwiki/doku.php/public/unrevoked2
The page says 2 (and there is and advice in a previous page that says that they "have taken the tool down for a short while until we're satisfied") but the source of the download says 3.14. I'm a little bit confused.
Anyway, if I have the Superuser app should be rooted. Or not?
EDIT: I found the unrevoked3 and tried again all the procedure but it doesn't work. I can't patch, I can't delete the old Superuser app, it still says S-ON.

Frak! Fat fingered permaroot - root is now an unknown user

Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.

vettejock99 said:
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
Try the alternative method in my guide with rage instead of visionary and see if that helps. One thing is does is reinstall su and busybox. Also, make sure that you have deleted the PD15IMG.zip from your sdcard so that this doesn't happen again.

Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!

just either use the stock rom in the downgrading post, or flash one of the new ones i.e. icedglacier or Gorillas's. iceglaciers seems to be pretty functional right now gorillas is awesome just has a few kinks he's working on

vettejock99 said:
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
try this (you should be s-off) and assuming you have busybox already installed.
run rage to get su in your terminal then run the following command in the terminal
busybox mount -o remount,rw /system
busybox chown 0 /system/bin/su
busybox chmod 4755 /system/su
install the superuser.apk if it's not already installed
make sure everything is working by opening a adb shell and typing "su" to verify.
use your phone normally and try rebooting after a few hours. hopefully the fs cache flushed and root is fixed permanently.

mrpanic7 said:
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
Click to expand...
Click to collapse
Okay, first things first - guess I have to try to see if I can even get S-OFF again or if I've completely screwed myself.
Going to try the alt root method, but I think I have been and it wasn't working. So unless me being tired at 1am was the cause, I may need some more help. Thanks.

Okay, followed the s-off guide, and ran the busybox commands posted above, and I am back to S-OFF and now I get "permission denied" instead of "unknown user root". I think this is progress, but still can't flash because I don't have root. I noticed opening Superuser keeps FC'ing...

Please post questions in Q&A section.

just follow this guide here, which you are already familiar with. it's for temp root using rage. but since your phone has the eng hboot with s-off it should become permanent once the FS flushes out to disk (flash)
http://forum.xda-developers.com/showthread.php?t=797042
follow the guide for root and mainly to get the su files installed just in case your's didn't instal properly prior. when you are done just type "sync" multiple times in your terminal
wait a while an hour or so. then reboot to verify that it's permanent.

Same thing happened to me with the unknown root user. What finally fixed it for me, was redoing the adb commands that put those files on your device so you could use rage. Once it re put the files on my phone, I did the rage commands again and it worked
Sent from my HTC Glacier using XDA App

Thanks, everyone! I am working again, and I cannot tell you how much I appreciate the help. I was THIS CLOSE to giving up on this phone.
Thanks again.
Mark

Help! Rooting issues

Hey guys, so first I rooted my phone using this method:
Ugh it won't let me use the outside link. basically its the doroot batch file for sdk/adb
Basically installed the android sdk stuff and drivers and then used the doroot batch file. That came back as okay, and I have the superuser permissions app on my phone now.
But then I tried to deodex the phone to start putting themes on there. When i get to the part where i go into the adb shell and try to use 'su' it says permission denied. So I figured the root had failed, or something was messed up. Then I tried to use this method to root:
(DroidX root. the one click program with root me and unroot me.)
That hasn't been successful. The phone disconnects from the computer for some reason (the laptop gives me the disconnected hardware sound during the install, and the install never finishes.)
So I tried Z4root. I downloaded it online, and put it on the phone, and installed it. It gives me the 'unroot' option, so it thinks my phone is rooted, but then it says usb debugging must be enabled. It says it must be enabled for every option i can choose (temp or permanant root.) The thing is, it is enabled!
I've tried to run titanium backup to check if I have root access on the phone, and that app says I don't.
What do I do? I'm totally stumped, and I have no idea if i've screwed this thing up or what. Is there any way to get my phone back to its original state so I can try this whole thing over again?
Help!

lunchbox2 said:
Hey guys, so first I rooted my phone using this method:
Ugh it won't let me use the outside link. basically its the doroot batch file for sdk/adb
Basically installed the android sdk stuff and drivers and then used the doroot batch file. That came back as okay, and I have the superuser permissions app on my phone now.
But then I tried to deodex the phone to start putting themes on there. When i get to the part where i go into the adb shell and try to use 'su' it says permission denied. So I figured the root had failed, or something was messed up. Then I tried to use this method to root:
(DroidX root. the one click program with root me and unroot me.)
That hasn't been successful. The phone disconnects from the computer for some reason (the laptop gives me the disconnected hardware sound during the install, and the install never finishes.)
So I tried Z4root. I downloaded it online, and put it on the phone, and installed it. It gives me the 'unroot' option, so it thinks my phone is rooted, but then it says usb debugging must be enabled. It says it must be enabled for every option i can choose (temp or permanant root.) The thing is, it is enabled!
I've tried to run titanium backup to check if I have root access on the phone, and that app says I don't.
What do I do? I'm totally stumped, and I have no idea if i've screwed this thing up or what. Is there any way to get my phone back to its original state so I can try this whole thing over again?
Help!
Click to expand...
Click to collapse
have you tried unrooting it since you got the "unroot" option you said when you open up z4?...if you can sucessfully unroot keep debug on and reboot then run z4 again..worth a shot...if it was sucessful you should see the temp root or permenant root option chose permemnet and let it do its magic. hope it helps its worth a shot..

Weird...
Thanks paul. I ended up turning the phone off and pulling the battery, and then upon restart z4 let me unroot, and then let me root! I had probably ****ed something up by trying to root it 2 different ways and 20 different times. Thanks for the advice!

Wait a sec -
So I'm trying to use adb to finish de-odexing, and I'm getting permission denied on the following command:
su mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
Does this mean I'm not rooted? Titanium backup works on the phone, and a notification popped up on the phone asking me if I wanted to give it superuser permissions or something...So I feel like I must be rooted. Any ideas?
If I leave out the su in the front of that command, it says Operation not permitted.
But If I type SU the cursor does switch to the dollar sign, so I think I have su privileges.

Droid X probably dead.
Haha hey everyone. So I managed to get root access through adb shell, and was in the middle of de-odexing the files. However, I ran rm /system/framework/*.odex before I ran rm /system/app/*.odex by mistake.
After the first command, the phone restarted and I lost connection to the phone for some reason.
Now when I start the phone up I get all these boxes that say (on a black background) Sorry! the application Voice Commands (process com.nuance.android.vsuite.vsuiteapp) has stopped unexpectedly. Please try again.
It gives me the option to force close, but the box just appears again. I can't get the phone to boot. What do I do!?
Edit: Found sbf. Flashed. Phone is alive.

Help Help Help...SOS..Permissions Issues

Hello,
I am having real problems with my phone. I was trying to root the phone and I am stuck. I have S=off on the HBOOT screen, android version 2.2, software version 1.14.531.1.
I am not able to perform Visionary temp root, can't load clockwork recovery, and can't install Busybox. When I try SU within terminal, I get the error "must be suid to work properly".
When I try to install Busybox, I get the error "The application failed either becasue you device is not NAND unlocked or we were unable to remount".
I cant install ClockWork recovery..I get the error "an error occured while trying to run privilidged commands"
I have tried everything which is probably why I am stuck. I tried to force the update to 2.2.1 but won't work. The phone goes thru the motions of updating boot, radio, etc...However, still the same results are its done. THe phone stays on 2.2.
I have tried doing all of the root methods avail: Using Visonary, rage, etc... None of them will work.
Can anybody offer me advice to get root back so I can 1. install a recovery and then install another rom? I need a way to basically put the phone back to factory installed software and start fresh.

Try this worked perfectly for me. also make sure you have ADB installed and working properly before attempting root.
http://forum.xda-developers.com/showthread.php?t=858996

lancer123 said:
Hello,
I am having real problems with my phone. I was trying to root the phone and I am stuck. I have S=off on the HBOOT screen, android version 2.2, software version 1.14.531.1.
I am not able to perform Visionary temp root, can't load clockwork recovery, and can't install Busybox. When I try SU within terminal, I get the error "must be suid to work properly".
When I try to install Busybox, I get the error "The application failed either becasue you device is not NAND unlocked or we were unable to remount".
I cant install ClockWork recovery..I get the error "an error occured while trying to run privilidged commands"
I have tried everything which is probably why I am stuck. I tried to force the update to 2.2.1 but won't work. The phone goes thru the motions of updating boot, radio, etc...However, still the same results are its done. THe phone stays on 2.2.
I have tried doing all of the root methods avail: Using Visonary, rage, etc... None of them will work.
Can anybody offer me advice to get root back so I can 1. install a recovery and then install another rom? I need a way to basically put the phone back to factory installed software and start fresh.
Click to expand...
Click to collapse
if you want to go back to stock follow the downgrade thread (linked in the thread about forcing the update) then follow the one linked above me here... it's faster than my forcing the update method (once you get radio s-off and the eng boot loader you can actually just flash the update.zip from my thread....)
EDIT: and in the future please post in the proper section or reply in the thread of the guide you're having problems with.

Thank you for trying to quickly help me. I started to follow the instrucions for downgrading and got stuck at the ADB Shell command. Within the Shell, I typed SU and got the following error "must be usid to work properly". Can you please offer any advice to get around this error?
Thanks,
Lance

to be suid you have to have temp or full root access. my sugestion would be to start the process from scratch. have you tried the visionary method?
i cant post the link to the other forum but its readily availible if you google it.
i didnt see the download link in the site i found so if you need the file PM me your email and ill send it back to you

Hello,
Yes, I did try Visonary and will not get SU working. The S=off is already showing. However, no matter what I do, I can't get SU to work. The device appears to be rooted but won't allow any advanced permisson comands to be used such as SU. I have tried re-installing superuser. that didn't help either.

launch the current version of SU you have on your phone and select settings scroll to the bottom of the page and under "superuser Information" you should see "Su binary Vx.x.x-xx) what is the version #?
Click on that and see if it updates the version if it does update try rebooting launch terminal and retry SU

Hello,
I checked the version of SU and did find there is an update. I tried to install and got the followng error 'An error occured and su was not updated. a zip file has been placed on your sdcard. please reboot into recovery and flash it".
The problem is that I can't get into recovery as I get the red exlimation mark. I can't find a way to install a recovery program because of permission issues.
Any further suggestions?

Please post questions in Q&A section.

Aren't you suppose to be on 2.2.1 before you start any rooting. Op=reading fail!
Sent from my HTC Glacier using XDA App

Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?

lancer123 said:
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
Click to expand...
Click to collapse
How in the first place you get the s=off. In order to get s-off you need root! Is also known that to boot into recovery thou need to try several times before its locks! The better way to deal woth it is reading! The root method in the dev section help a lot! Read, read! That's the better way to learn! If you are in eng hboot and s= off there's a possibility that you only need to reboot into recovery several times! Other than that just read with patience!
Sent from my HTC Glacier using XDA App

lancer123 said:
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
Click to expand...
Click to collapse
My advice (without trying to hurt feelings too much) is DON'T ROOT. You obviously don't really know your way around Android too well at this point. I would familiarize yourself with everything before diving in head first.
Despite popular belief, having root does NOT in fact make you cooler.
WAAAY too many new users are trying to root because they think it's cool or heard it's cool. You need to learn your device first.

deviusdragger said:
Aren't you suppose to be on 2.2.1 before you start any rooting. Op=reading fail!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
no... you fail

lancer123 said:
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
Click to expand...
Click to collapse
lancer... get on IRC I will help you
EDIT: or AIM, or yahoo, msn, or gtalk.... my info is in my profile

If you have S=Off on your phone already, your best bet would be to flash Clockwork recovery through FASTBOOT.
If you are unsure of how to do this, refer to this link from the Cyanogen Wiki:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
The page will point you in the right direction for everything that you need.
Have the ROM that you want to install on your SD Card because FASTBOOT will probably not allow you to directly flash all the other partitions, but it will at least allow you to flash recovery, then boot into Clockwork and Install a new ROM.