Database Users

How to know if your phone is rooted or not?

I was rooting my nexus one last night on a guide from theunlockr.com and got through every step except the last one where you have to install ''install-superboot-windows.bat'' when i clicked on it it showed a little blackbox with something in it for about half a second and nothing else showed up so i assumed it was finished. When i go into bootloader it says unlocked at the top and on the start up screen it shows a little unlocked sign at the bottom but i went into the market to download the torch application, the whole reason i rooted it and it told me that i was not rooted and it would not work.

You have root just don't have superuser permission. I say flash the cyanogen add-on if you don't to flash a rom that has su built in.

Reboot your phone. If you have a pic of a unlocked lock, then your phone has been unlocked, and you can flash the amon_ra recovery, then flash a custom rom with superuser permission.
Also, you can go to a terminal emulator and type in su.

david1171 said:
Reboot your phone. If you have a pic of a unlocked lock, then your phone has been unlocked, and you can flash the amon_ra recovery, then flash a custom rom with superuser permission.
Also, you can go to a terminal emulator and type in su.
Click to expand...
Click to collapse
Where can i get a terminal emulator?

Hi mate, I had the same problem... I think you have unlocked your bootloader but failed to root your phone.
Im pretty sure the bit when you ''install-superboot-windows.bat'' doesn't work sometimes.
I had to manually re-do that bit ...
---------------Manual Rooting---------------
open a command window in that folder by holding down your shift key and right clicking anywhere in the window. and selecting open command prompt here
type this command in your command prompt "fastboot-windows flash boot nexusone.superboot.1.1.img"
then enjoy your rooted phone.

viperman78 said:
Hi mate, I had the same problem... I think you have unlocked your bootloader but failed to root your phone.
Im pretty sure the bit when you ''install-superboot-windows.bat'' doesn't work sometimes.
I had to manually re-do that bit ...
---------------Manual Rooting---------------
open a command window in that folder by holding down your shift key and right clicking anywhere in the window. and selecting open command prompt here
type this command in your command prompt "fastboot-windows flash boot nexusone.superboot.1.1.img"
then enjoy your rooted phone.
Click to expand...
Click to collapse
Thanks Do i have to put the phone into bootloader or do anything else on the phone?

No... just follow the last bit of this.
http://www.android-devs.com/?p=100
For some reason the batch file didn't do its magic, so I had to do it manually... Pretty sure you have the same issue .
And really??... the whole reason you voided your warranty was for the torch app???? You are not installing Cyanogen mod or anything?

viperman78 said:
No... just follow the last bit of this.
http://www.android-devs.com/?p=100
For some reason the batch file didn't do its magic, so I had to do it manually... Pretty sure you have the same issue .
And really??... the whole reason you voided your warranty was for the torch app???? You are not installing Cyanogen mod or anything?
Click to expand...
Click to collapse
haha no but thats how i found out about rooting. Also you said just follow the last bit of the steps do you mean just do step 7, Sorry for all the questions im new to most of this and dont want to mess up my nexus.

Thanks, I got it to work but now wifi does not work

Install all the latest Cyanogen stuff and you should have no problems. Also you will have a lot more mem for apps!
Voiding your warranty just for a flashlight is a bit silly IMO.
GL

I installed the cyanogenmod 5.0 rom and everything was installed correctly and when i reset the phone it just shows the firework things coming together over and over again.

Losing root when nandroid restore.

Ok guys, i think this is the best place to post this up as this post will get more appropriate replies.
In the last few days i've lost root 3 times for what i see as no apparent reason. I am running CM 5.0.2 with some morphs and nothing else different. I've heard over at IRC that some people on CM are experiencing the losing root problem as I have and only just now, have i pinpointed the problem.
Just now i did a fresh nandroid backup of my current config, and im not sure if anyone else does this - but i instantly do a restore with the 'new' backup just to verify that it backed up correctly and is not corrupt. If it is corrupt then it will not complete the restore and i can backup again. I do this because in the past I have gotten bad backups that dont restore and leave me with no backup at all. Anyways, after this restore I instantly checked my root and *drum roll* no root access.
Not sure if something is wrong with the Recovery (a bug), but i never had this problem in the past and not sure to the reason why. Im 100% sure i have root before the Nand Backup, so why would it lose root after a restore?
Thanks

I experienced this, I had made a backup, and wiped (to get protected apps working in market)... I then restored my backup, and noted that all attempts to access SU were given permission denied (without prompt). All you have to do is re-flash your current rom. I believe this has happened with Nandroid restores in the past, maybe Amon_Ra's thread is the right place for this conversation?

daveid said:
I experienced this, I had made a backup, and wiped (to get protected apps working in market)... I then restored my backup, and noted that all attempts to access SU were given permission denied (without prompt). All you have to do is re-flash your current rom. I believe this has happened with Nandroid restores in the past, maybe Amon_Ra's thread is the right place for this conversation?
Click to expand...
Click to collapse
Hi thanks for the reply,
I guess this does belong to Amons thread, but in a way im trying to inform those who are confused about the 'random' lost of root access. This was seriously baffling me before as it seemed really random at times, I wouldnt even know i lost root until i used certain apps. Therefore I couldnt pin point the actual cause. It is easily fixed with reflashing ROM/Gapps etc but i still do a superboot (not sure if this is necessary, although I dont see why not.), and for obvious reasons superboot you would need a computer.

m00moo said:
Hi thanks for the reply,
I guess this does belong to Amons thread, but in a way im trying to inform those who are confused about the 'random' lost of root access. This was seriously baffling me before as it seemed really random at times, I wouldnt even know i lost root until i used certain apps. Therefore I couldnt pin point the actual cause. It is easily fixed with reflashing ROM/Gapps etc but i still do a superboot (not sure if this is necessary, although I dont see why not.), and for obvious reasons superboot you would need a computer.
Click to expand...
Click to collapse
We appreciate the effort, but its just going to make people more confused when the information is all over the place and not in one clear, easy to find location.
Since it occurred when you performed the nandroid restore, then logically it belongs in that forum.

Fictionles said:
We appreciate the effort, but its just going to make people more confused when the information is all over the place and not in one clear, easy to find location.
Since it occurred when you performed the nandroid restore, then logically it belongs in that forum.
Click to expand...
Click to collapse
Sorry if thats the case then I should post in there and ask that a mod closes this thread. Although i think your post slightly contradicts itself lol The information is all over the place and by making this thread, I think it clears the mess up as people can see it clearly.
Like i mentioned before I was personally told over at IRC that people appeared to be getting this issue with CM roms, but to my finding seems to be Nandroid for me. Maybe even a combo of the both together? but whatever it is I hope both of the talented guys can look into it, although its not a huge huge matter to us (unless your an dev and nand frequently and lose root - now that would be annoying).
Regards
(if a mod does see this thread unfit please feel free to close )

i can also confirm when restoring cyan's latest stable rom with nandroid that i loose root. i can also confirm that re-flashing the rom and gapps restores root.

there's a problem with the restore currently.
the permissions of /system/xbin/su get lost.
fix it with:
Code:
adb remount
adb shell chmod 6755 /system/xbin/su
no need to reflash anything. besides if you rather reflash, no need for gapps then.

xkonni said:
there's a problem with the restore currently.
the permissions of /system/xbin/su get lost.
fix it with:
Code:
adb remount
adb shell chmod 6755 /system/xbin/su
no need to reflash anything. besides if you rather reflash, no need for gapps then.
Click to expand...
Click to collapse
solved the issue for me, thanks

xkonni said:
there's a problem with the restore currently.
the permissions of /system/xbin/su get lost.
fix it with:
Code:
adb remount
adb shell chmod 6755 /system/xbin/su
no need to reflash anything. besides if you rather reflash, no need for gapps then.
Click to expand...
Click to collapse
Thank you, sir! You just saved me a lot of time and aggravation!

Having the same issue as others in the thread although when i type in:
"adb remount" i get
"remount failed: invalid argument" thus i cannot get to the next step to restore root!
Cheers,
Vonapets

I've also been unsuccessful with this. Im on windows 64

I have attempted the same thing on XP 32bit as opposed to Win7 64bit. Still the same issue. Can someone post the su file for me to push onto my system via fastboot? I imagine you could probably pull it with root explorer?
Cheers,
Vonapets

The problem is fixed in my RA 1.6.2 recovery, just update and you'll not lose root again.

Amon_RA said:
The problem is fixed in my RA 1.6.2 recovery, just update and you'll not lose root again.
Click to expand...
Click to collapse
I understand completely, i have already done so pretty much the minute i saw there was an update, although as i still dont have root and the commands dont work im guessing that i have to reflash? I have tried commands on 3 diff pc's and still no luck. Do i flash superuser then Cyanogen or?
Cheers

vonapets said:
I understand completely, i have already done so pretty much the minute i saw there was an update, although as i still dont have root and the commands dont work im guessing that i have to reflash? I have tried commands on 3 diff pc's and still no luck. Do i flash superuser then Cyanogen or?
Cheers
Click to expand...
Click to collapse
Did you make a new nandroid backup AFTER flashing the new recovery? Using a corrupted backup will still make you lose root.

vonapets said:
I understand completely, i have already done so pretty much the minute i saw there was an update, although as i still dont have root and the commands dont work im guessing that i have to reflash? I have tried commands on 3 diff pc's and still no luck. Do i flash superuser then Cyanogen or?
Cheers
Click to expand...
Click to collapse
Yes, flash superuser again to gain root.

prettyboy85712 said:
Yes, flash superuser again to gain root.
Click to expand...
Click to collapse
Attempted this morning, when i flashed the superuser over the top of cyanogen, launcher and phone constantly force close! Maybe should just start again haha. Just hate downloading all the apps again and market db, cant backup because i dont have root!

thank you adb shell chmod 6755 /system/xbin/su saved me some reflash
thank you for your post save me some headaches

I entered the game starting with the 1.6.2.
First thing i did was make a nandroid backup of the stock rom, with root.
then went on flashing random roms , with nandroids.
as i switched from modoco to stock rom, i lost root.
when i try the adb stuff, i get
'Unable to chmod /system/xbin/su: No such file or directory'
I understand that.. but what do I do now then?
Superuser permissions doesnt do much for me here.. but ill be honest and say i dont know how to work it. I highlight the 1 item that was there, and it deletes itself.
-resets phone. opens ti backup-
it gave me the allow stuff, and i said Allow Always,
but it still says no root, I tried Metamorph, always gave me allow questions, and i approved, and no go.
-
---
restoring to a CM nandroid gave me root back.
I wonder if i wipe and format will i still have root, but i can start fresh?

Main Version Is Older! Update Fail! Message

Hi,
Thanks in advance for anyone who tries to help me.
A few weeks ago I tried to gain root access to HTC Eris. I followed the prereq and part one of the guide but stopped there. Rebooted my phone, checked the version (2.1) and went about reinstalling apps and such.
Now I want to install a different ROM so I went back and tried to start from the beginning and put PB00IMG.zip on my phone, went to hboot, let run but then I get the message "Main Version is older! Update Fail! Do you want to reboot device?"
So when I move onto III in the walk through, I get an error on the command
adb push flash_image /system/bin
It would seem like I've lost root right? Is there anyway I can check to see if I accidentally installed the leak w/o root?
Thanks,
Nate

Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.

I am anticipating the next question, so here is your answer. If you did indeed root your phone, you should have loaded a recovery image as jcase mentioned.
First, load the new ROM onto the root of your sd card. Next, power off your phone. Then, hold down the vol up button and turn on your phone. It should boot into the recovery console. From here to load another ROM, you need to perform a wipe and then load your new ROM by flashing. You should see a Wipe and Flash from Zip menu option in recovery.
In the Wipe menu, choose the first two options in order (factory reset and cache). Wait for each to complete. Next, pressing vol down should get you back to the main menu. From here choose Flash from Zip and then select the ROM zip file you loaded onto your sd card and wait for the update to complete. Last, reboot your phone from the menu.

jcase said:
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
Click to expand...
Click to collapse
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?

xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?

try su
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.

jcase said:
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
Click to expand...
Click to collapse
I followed a guide a few weeks ago that must have been for the leaked version of 2.1.
thisismyanonymousaccount said:
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
Click to expand...
Click to collapse
I get
su: permission denied
Click to expand...
Click to collapse
I guess that means my phone I'm stuck with it...FML!

xnatex21 said:
I guess that means my phone I'm stuck with it...FML!
Click to expand...
Click to collapse
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.

g00gl3 said:
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
Click to expand...
Click to collapse
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?

xnatex21 said:
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
Click to expand...
Click to collapse
Technically, modifying your device would void warranties. Even if they could "restore" the device, it would still have the newer bootloader that is causing the rooting issue. Some people have "lost" or "broken" the device bad enough that they could get a replacement from Verizon. However, there is mixed results as to what bootloader the refurbished devices come back with.

I posted before about the safety of re-rooting my eris from 1.5 to a rooted 2.2 rom, and due to lack of responses on any forums over the web, I jumped the gun today. First off my Eris after un-rooting it, wouldn't take the OTA update for 2.1, it downloaded and verified that, but after it rebooted, it was still at 1.5 saying no new updates are available. I cannot download the eris 1 click root app as it's only for 2.1 I'm assuming because it says it's not compatible with 1.5 firmware when I download it. I tried to follow this guide [Walkthrough] From stock (1.5) to rooted 2.1 (update - new link) - xda-developers and when I installed the PB00IMG.zip it downloaded but failed to flash and the screen read "Main version is older". I tried this guide All-In-One Auto-Root Script - Page 4 - xda-developers and when it says it's flashing the root image, it goes straight to a screen with only two options "recovery" something and "fastboot". None of which are listed as options in the guides. I am just trying to root my 1.5 eris and flash the KaosFroyo V3 eris rom with Amon Ra's recovery image. Thanks if anyone can help my problem, or shed light on the situation! Sorry if there's been a fix to this problem already stated, I've desperately been browsing many forums and hundreds of replies to no avail. Thanks again.

It looks to me like you got a pretty reasonable answer to the same question over on Android Forums
bftb0

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.