Titanium Backup says "error could not acquire root", yet I "am" rooted???
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Be weary. I used unrevoked3 for mac on a froyo Evo. I'm having some issues currently. Be careful before you proceed. You should download ROM manager as well. Once you download busybox perform your backup. A friend recommended Appbrain over Titanium Backup. Once your done with your back up, reboot into the bootloader and try to go into recovery to perform a nandroid backup. If you select recovery and it takes you to the htcevo 4g white screen and nothing happens, you're having the same issue as i am. I wouldn't recommend flashing any radios or roms yet. I'm working with some other members to try to figure this issue out. Apparently this is why other experts don't like unrevoked3.
There might be a missing pc36img or unrevoked forever might need to be install, but I don't want to lock my phone into root with unrevoked. From my understanding, if you use unrevoked forever, you wont be able to unroot.
jontorres said:
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
Click to expand...
Click to collapse
[highlight]Mod Edit: If you have nothing useful to say, say nothing at all. The question in the correct section this time.[/highlight]
jontorres said:
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
Click to expand...
Click to collapse
What about any other app requesting root? Like setCPU or ShootMe? I'd install one of those to confirm root. If it works then you might you need to reinstall TB if not well then root was not properly achieved.
TruSlide said:
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Click to expand...
Click to collapse
Thanks for the suggestions, will try those out and report back what happened.
Sporkman said:
take the time to read the info it tales you have to fix said issue
Click to expand...
Click to collapse
MOD PM'd, apparently you are following my threads now to post the same "ignorant" response, your sanction from the mod will follow, enjoy.
Everyone else, thanks for actually offering helpful suggestions.
TruSlide said:
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Click to expand...
Click to collapse
Ok, so I did update BusyBox, and now Titanium Backup doesnt show the error, also installed Terminal Emulator when you launch it the 1st line of text says"
$ export PATH=/data/local/bin:$PATH
$
On the 2nd line where the $ i typed SU and hit enter and it goes to the next line and displays # is this what its suppose to do?
Thanks
Ok, here is some things for you to try.
1. Make sure you are using the latest version of TB.
2. Make sure you hit Problems? and download Busybox 1.60 (whether or not the ROM you have is using 1.60 or not, do it anyhow.)
I assume you did those two based on what I read. So here is what else to try.
Upgrade Superuser to the latest version, then update the binary. Make sure Titanium backup is not blocked by going to Superuser and there should be a green circle next to TB, if it is red that means it is blocked. If it still doesn't work, remove it from Superuser and then have it ask for permissions again.
If STILL not working, take out your battery for around 10 seconds, plug it back in and try again. Lastly, uninstall and reinstall TB then do these steps all over again.
That is a bunch of stuff to try, see what happens and hope this helps
jontorres said:
Ok, so I did update BusyBox, and now Titanium Backup doesnt show the error, also installed Terminal Emulator when you launch it the 1st line of text says"
$ export PATH=/data/local/bin:$PATH
$
On the 2nd line where the $ i typed SU and hit enter and it goes to the next line and displays # is this what its suppose to do?
Thanks
Click to expand...
Click to collapse
That's exactly what it's supposed to do. $ is the prompt you get when you are a regular user. You get # when you are root.
If you type 'id' (without the quotes) now, you should get:
uid=0(root) gid=0(root)
ricsim78 said:
Upgrade Superuser to the latest version, then update the binary. Make sure
Click to expand...
Click to collapse
I launched Superuser, the one with the little niña guy, and it showed TB and the emulator both with green on the right side, but no idea how to "update" superuser, seeing as all appears to be ok should I still update it? If so, hoe would I do that? If not then I guess now my next step s finding the best 2.2 ROM that still keeps HTC Sense, any recommendations?
timdsmith72 said:
That's exactly what it's supposed to do. $ is the prompt you get when you are a regular user. You get # when you are root.
If you type 'id' (without the quotes) now, you should get:
uid=0(root) gid=0(root)
Click to expand...
Click to collapse
the prompt b4 I typed anything was $, after typing SU and enter it went to #
jontorres said:
the prompt b4 I typed anything was $, after typing SU and enter it went to #
Click to expand...
Click to collapse
Yep. That's what is supposed to happen. You are root when you have the # prompt.
Problem
I just flashed CM 7.1 stable version, i cant launched TB couldt aquire root privileges i read this post and typed SU in the terminal emulator and it came up with a $ sign. So that means im not rooted?
Any cure to get my phone rooted again but i want to keep CM 7.1 what should i do?
aks1081 said:
I just flashed CM 7.1 stable version, i cant launched TB couldt aquire root privileges i read this post and typed SU in the terminal emulator and it came up with a $ sign. So that means im not rooted?
Any cure to get my phone rooted again but i want to keep CM 7.1 what should i do?
Click to expand...
Click to collapse
Flash the super user zip from http://androidsu.com/superuser/
Should fix you up, not sure how you lost it, but this souls fix it nevertheless.
Related
I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?
Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.
AzN1337c0d3r said:
I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?
Click to expand...
Click to collapse
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?
xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?
Click to expand...
Click to collapse
My leetspeak is a little rusty, but I think 1337 is 'leet' as in "elite"....and I'm guessing the young man is of Asian descent.
drmacinyasha said:
Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.
Click to expand...
Click to collapse
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
Click to expand...
Click to collapse
I thought Unrevoked Forever took care of the NAND not getting unlocked. It says on their website that it unlocks NAND.
Anyways, the whole reason why I went with unrevoked is because I could keep PRI 1.40_003. I had lost it when I manually rooted and had to go back to stock and then unrevoked to get it back.
I am having the same issues. I am unrevoked3 and unrevoked forever. It is always telling me either device not found or remote not allowed. As far as I can tell all of my drivers are up to date, I am fully rooted with nand unlocked, and the problem didn't start until just recently. Everything worked fine before. I will try to download an updated Superuser app and give some feedback on that when I get off work.
On a side note, does Busybox have anything to do with this sort of matter?
Sent from my regaw rooted EVO.
My problem appears to be a software/OS issue. When I wipe everything and install a stock 2.2 system, I am able to "adb remount".
My guess is that something is continually accessing the /system partition and holding a lock on it.
Does anyone know how I might check for this?
Just to clarify: yes, Unrevoked Forever does unlock NAND.
The issue must be with the rom? Try a different superuser/su...
AzN1337c0d3r said:
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
Click to expand...
Click to collapse
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Thank you so much for the info. I have been searching high and low for a straight answer on this. Even though its not fixed I am much happier knowing what the issue is. Again thank you.
When I ran your test I got a $ which as you said means it is a conflict with my current ROM. So, if I flash a different ROM than I should be squared away yes? Again many thanks.
Sent from my regaw rooted EVO.
drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
Click to expand...
Click to collapse
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.
AzN1337c0d3r said:
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.
Click to expand...
Click to collapse
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.
drmacinyasha said:
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.
Click to expand...
Click to collapse
Yup I did exactly that.
It's some app I installed that is doing this. I nandroided my current config, reflashed the netarchy 2.2 rooted rom and was able to get access.
Then when I installed all the rest of my apps, I suddenly lost access.
Tommorow I will start fresh again and try apps one by one.
now i got # what else
I cannot enter any SU commands in TE since I updated to 3.29. Ex. Reboot and reboot recovery - get "Not Permitted" error message. Anyone else?
Thanks!
I just rooted using the latest Unrevoked (3.21).
The process indicated success.
But attempting "su" in an effort to manipulate "perms" results in "Permission denied".
Does this mean I am not actually "rooted"?
Or do I need a something in addition to being "rooted".
I seem to remember something called "Super User application".
Is this a requirement? If so, where might I find it?
Thank you for all your time and consideration.
--Chris
You can download Superuser from the market. Skull and crossbones icon.
bender1077 said:
You can download Superuser from the market. Skull and crossbones icon.
Click to expand...
Click to collapse
Thank you for your reply bender1077.
Is this app required in order to make changes like deleting apps and stuff on a "rooted" stock ROM?
Thanks again.
--Chris
If you are using an app that requires Superuser permissions yes. Depends on how you are removing the apps. I always delete through ADB.
bender1077 said:
If you are using an app that requires Superuser permissions yes. Depends on how you are removing the apps. I always delete through ADB.
Click to expand...
Click to collapse
Thank you again bender1077.
I used Unrevoked 3.21 to root it. When it had completed, I found that SuperUser was/is
now installed, and available on my HTC-EVO-supersonic.
On the downside, when prompted by SuperUser when I launch Terminal Emulator to allow
su (root), I answer YES. But when attempting (like you) to delete apps, or what-not,
I'm told "read only file system". So the attempt fails.
Seems we're having the same issue - no?
Thanks again.
--Chris
CTH-EVO said:
Thank you again bender1077.
I used Unrevoked 3.21 to root it. When it had completed, I found that SuperUser was/is
now installed, and available on my HTC-EVO-supersonic.
On the downside, when prompted by SuperUser when I launch Terminal Emulator to allow
su (root), I answer YES. But when attempting (like you) to delete apps, or what-not,
I'm told "read only file system". So the attempt fails.
Seems we're having the same issue - no?
Thanks again.
--Chris
Click to expand...
Click to collapse
You have to remount in -rw in order to delete apps iirc.
I'm not trying to delete apps through TE, I do that through ADB.
BUUUUUTTTTTT.... Please just go into TE, and see if you are able to enter a simple command like reboot, and confirm if it works on 3.29.
I still get "not permited!" error.
It is funny that TE has permitted mispelled by the way!
THANKS!
bender1077 said:
I'm not trying to delete apps through TE, I do that through ADB.
BUUUUUTTTTTT.... Please just go into TE, and see if you are able to enter a simple command like reboot, and confirm if it works on 3.29.
I still get "not permited!" error.
It is funny that TE has permitted mispelled by the way!
THANKS!
Click to expand...
Click to collapse
Greetings bender1077,
Code:
% su
message from SuperUser:
permission granted to Terminal Emulator for su
# _
# reboot
permission denied!
# _
I hope that made sense. Superuser granted permission to me
to su. I got the hash in the upper left hand corner (#), indicating
I was root. But as you can see, I was not granted permission to "reboot".
HTH
--Chris
Oh boyzie!
OK... I will run Quick Boot for reboots, and reboot recovery for the time being!
Thanks,
Hey bender are you nand unlocked? I don't know if that would make a difference.
Sent from my GiRLiE Evo
princessakiki said:
Hey bender are you nand unlocked? I don't know if that would make a difference.
Sent from my GiRLiE Evo
Click to expand...
Click to collapse
Yes.
Worked fine on 3.26... there has to be an issue somewhere ..... /system/bin/toolbox?
I followed all the steps from the Wiki: (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD).
Now the problem is when I go to verify the root. On the Wiki, where it says run "su' in computer ADB shell, I get access denied. When I run "./gfree_verify" in computer ADB shell, I get
Error: Could not open modem device; /dev/****
Error: Verify could not initialize device
But in my apps on the G2 I see an icon for superuser permissions. So did the root take or not?
Thanks for any help, new to Android.
Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root
MacaronyMax said:
Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root
Click to expand...
Click to collapse
After typing Su in the terminal on the phone, I get a message pop that says either allow or deny. I click allow and it gives me root permission.
Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".
Ganii said:
Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".
Click to expand...
Click to collapse
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.
boost3d23 said:
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.
Click to expand...
Click to collapse
# sign means your rooted or have su access.
Go under manage and restore backups in rom manager, you should have a copy of the rom you just backed up. Unless you renamed the back up its probably a date.
Its ok to delete the files you pushed to data/local use a file manager like root explorer.
Sent from my HTC Vision using XDA App
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again. Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
Click to expand...
Click to collapse
You get "#" then it`s right,the app don`t ask you again about allow or deny!
About gfree-verify,I don`t know.Maybe something wrong with Script
or you have done something wrong with the commands!
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Click to expand...
Click to collapse
If you choose "Backup ROM" you phone boot into Recovery,then you have
to choose "backup/restore option to backup you current ROM.
Otherwise you don`t have a backup
Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
boost3d23 said:
Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
I use Root Explorer or SUFBS (Super User File Manager and Terminal).
boost3d23 said:
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
You should really have posted up in the existing thread about gfree on this, or otherwise in the Q&A forum
But anyway, yes, those file managers don't handle root. Well, ES does have an option to do so, but it doesn't work on the Vision. So you'll need a root-capable file manager, as joemm said.
On the backup, that sounds a bit odd, but you'll know that it's doing a backup because it'll take a while. You'll get a different screen where it shows you it's backup up the main phone partitions, and even which file is being backed up. When it's done, make sure you copy this backup somewhere else, like your PC (i.e. so you don't just have a single copy, in case something happens to it - e.g. corrupt SD card).
Thanks to everyone who provided insight. I had the same problem and was worried about bricking my phone, but this worked and I'm happily rooted!
If on Recovery, it says S-ON, is that a Problem?
triumphantpower said:
If on Recovery, it says S-ON, is that a Problem?
Click to expand...
Click to collapse
If it says S-ON, you don't have permaroot. Did you follow the guide in the wiki?
Sent from my T-Mobile G2 using XDA App
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
triumphantpower said:
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
Click to expand...
Click to collapse
YouTube *really* shouldn't be the go to for things like this, unless you like bricks. This guide is by the folks who actually engineered the hack: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App
oh alright, Thank You OriginalGabriel.
But is rage an adb command or an app from the Market?
and where would the HTC G2 Drivers have to be installed?
triumphantpower said:
and where would the HTC G2 Drivers have to be installed?
Click to expand...
Click to collapse
If you've used adb (eg. you have the SDK installed on your computer), then you have the drivers already installed. Otherwise, unzip the file and when you plug your computer into your phone, point the hardware wizard to the folder that you unzipped
Rage is an included binary in gfree_temp-root.zip
Got it Thank You.
I got to where I have to use ADB, and while trying to $ adb push su /sdcard/su
It won't let allow me, it'll say access denied. (I've even put adb shell before that command)
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
triumphantpower said:
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
Click to expand...
Click to collapse
on your phone be sure you have menu>settings>applications>development>usb debugging checked (on)
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
triumphantpower said:
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
Click to expand...
Click to collapse
After you do the temp root, shut down adb (I am using a windows machine so I ctrl alt del and find it in task manager and shut it down that way) It should restart by itself when you do the perm root commands. ( you probably know this, but don't enter the # sign, it should be there by itself)
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
triumphantpower said:
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
Click to expand...
Click to collapse
Download ROM manager from the market, spend the few bucks for the upgrade and then install clockworkmod recovery through ROM Manager (if you haven't done this already). Then, do some more reading about doing a Nandroid backup and you're ready to go! Now, the fun begins....lol!
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
triumphantpower said:
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
Click to expand...
Click to collapse
do you have the superuser app now in your applications drawer?
edit: Also, disconnect the phone from the USB. That might give ROM manager a problem accessing your sd card if you're still connected.
yeah I have Superuser Permissions but it FC's when you try to open it
triumphantpower said:
yeah I have Superuser Permissions but it FC's when you try to open it
Click to expand...
Click to collapse
Try uninstalling ROM Manager and after that see if you still get a force close when you try to open Superuser.
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
triumphantpower said:
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
Click to expand...
Click to collapse
what happens when, in ROM Manager, you select "fix permissions"?
Hi everyone, I`m getting the "Main Version is older! Update Fail!" message and have run into a brick wall. Can anybody help? Hopefully the screen grab of the cmd has attached correctly so one of you clever people may be able to see it and know what is wrong.... I have not got a clue!
Too bad you didn't scroll down before you took the screen shot.
Agoattamer said:
Too bad you didn't scroll down before you took the screen shot.
Click to expand...
Click to collapse
That was it dude! Below Exploiting Device, it just went back to the start C:Users...ect. There was nothing else of interest.
Anybody know what went wrong?
Dazblink said:
That was it dude! Below Exploiting Device, it just went back to the start C:Users...ect. There was nothing else of interest.
Anybody know what went wrong?
Click to expand...
Click to collapse
If i remember correctly fre3vo exploits and then exits the shell.
If you use "adb shell" again, you should have root on your phone.
I followed the guide in the cyanogenmod wiki and it worked, so maybe have a look at that:
http://wiki.cyanogenmod.com/wiki/HTC_Desire_HD:_Firmware_Downgrade_(Gingerbread)
Your error sound like you didn't use misc_version.
Dlog said:
If i remember correctly fre3vo exploits and then exits the shell.
If you use "adb shell" again, you should have root on your phone.
I followed the guide in the cyanogenmod wiki and it worked, so maybe have a look at that:
http://wiki.cyanogenmod.com/wiki/HTC_Desire_HD:_Firmware_Downgrade_(Gingerbread)
Your error sound like you didn't use misc_version.
Click to expand...
Click to collapse
yeah i think that's right, i think you will exit shell after the exploit. if you type adb shell and you get a # you're root. if you get a $, try typing su then hit enter and if you get a # you're root
i followed the guide that Dlog linked to and it worked well so i would definitely do that. but i guess that's what you're doing anyway?
it is because the update package in your sdcard is older than your device running right now,
that's why after fre3vo and got root in adb shell (the # sign), you run this command
./misc_version -s 1.31.405.6 , to make your DHD think the update package is newer, and do the update from the IMG file in your sdcard
after update complete (downgrade), you can now use visionary+ to root .
BTW, what's your build number ?
Sorted it cheers! Typed in abd shell again and got the #
Thanks for the replies!