• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Root problem, Please help

An UrgeTo Dance

An UrgeTo Dance

The Hero of the Winds
Okay so I ran unrevoked it said root was a triumph then came up with an error (validation error: backup CID is missing) I then went on to manually root the phone by installing Amon-Ra from hboot. I successfully got it to install but then when I went to install SU from recovery it said installation failed signature not verified, or something like that. I then tried to install it from the market and it installed then I went into terminal emulator and typed in "su" (without ") and it did not change the prompt. I have hboot 2.10 and the newest software on my phone and s-off. Can someone please help.
 
Did you try what I suggested in your first thread? Rerun unrevoked. It should finish the rest of the process cleanly (Root your current ROM). If it still doesn't run, you can continue with what you're doing, but you'll have to flash a custom ROM, wiping all your data in the process.
 
I tried downloading SU from the market and tried the prompt you gave me in the terminal emulator and it did not change from a $ to #. right now I have no idea what to do, and if my phone is already rooted will running unrevoked again mess anything up. Right now I currently have Amon_RA recovery and s-off but I can't get superuser.
 
Unrevoked basically does three things:

1) Gives you s-off
2) Gives you a custom recovery (Clockwork)
3) Roots your custom ROM

It used to be that it would flash Clockwork, then flash unrevoked-forever (to get s-off) from recovery. I don't know if the process has changed, but somehow, you got the s-off part, and the rest failed. Flashing a custom recovery (RA in your case) isn't difficult, as you found out. Technically, all you ever need is s-off and a custom recovery. That will enable you to flash custom ROMs. That is one route you could take. The thing is, if you want to back up all your apps with titanium, or just wanted to stick with stock, you can't because unrevoked failed that part. That's why I'm saying the easiest thing to do is rerun unrevoked. It should complete what it's supposed to do.

It will not break anything. What will happen is, it will overwrite RA with Clockwork, root your ROM (what you need now), and when it gets to flashing unrevoked-forever, it just won't have anything to do, since it's already done. Flashing unrevoked-forever when you already have s-off doesn't break anything. It just doesn't do anything. So, go ahead and rerun unrevoked. That should get you where you need to be.
 
You don't need to unroot first. If you still get errors, I would suggest you do a factory reset, then try again. You'll still have s-off, but it eliminates any potential software conflicts. If that still gives you problems, then unroot, but you should be able to rerun unrevoked now without doing that.
 
What are they telling you to do? If they have better advice, take it. There are several ways out of your predicament. I happen to think rerunning unrevoked will work the best.
 
They are telling me to just flash clockwork manually then trying to flash SU again, I'm going to try that and if it doesn't work I may just give up on rooting or try again on a later day.
 
Hm, well if you do that, make sure you don't have it installed from the market, and make sure it doesn't exist in /system/app. Let me know what you decide and how it turns out.
 
Did you at any point try to flash superuser? If so, and it was successful, you'll have superuser.apk in /system/app. Open the terminal emulator and type:

ls /system/app/Superuser.apk

If it returns an error, it's not there. If the output is the file name, it's there. Presumably, if it's already there, though, reflashing it isn't going to make a difference. It's either there or it's not.
 
Ok, then it's not there. You can try flashing it again, but I still think you're better off rerunning unrevoked.
 
I am going to try unrevoked again, hopefully it will work this time. I actually thought about flashing it back to stock but then decided I want root to much to do that.
 
You must log in or register to reply here.
Back
Top Bottom