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

Root ROOTING For Dummies Guide.....the Gingerbread Edition

Ok I did it and updated the pc36img but now what do i do to get superuser on my phone? Clockwork still won't work so I still can't do it that way.

So are you using amon ra or clockwork recovery? Or are you talking about clockwork rom manager? Don't use that, it's buggy.

Just go to recovery, and "Flash zip" or whatever your recovery says. Then point to the su file you downloaded.
 
Ok I got it. Thankyou so much. I'm so excited. Now two more questions. If I want to clear the system because im running out of space can I do a factory reset or will that unroot my phone? And i want cm7 can I use that Rom with this root method?
 
OK Folks, having a weird problem here and would appreciate any help!

I ran Revolutionary, checked Debug, uninstalled Sync and EasyTether from my PC. When I run Revolutionary I get the message 'zerging for root' and then the following error message a few minutes later:

Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partition.
Errors <if any>:-
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
Press <almost> any key to exit.

I'm running GB 2.3.3, but haven't done the most recent update. Any advice??

Thanks in advance.
 
Ok I got it. Thankyou so much. I'm so excited. Now two more questions. If I want to clear the system because im running out of space can I do a factory reset or will that unroot my phone? And i want cm7 can I use that Rom with this root method?

You won't unroot your phone with a factory reset, but if you're running low on space, you pretty much have too many apps (look into the sd card partitioning - it allows you to run apps from the sd card)

You can use CM7 (and any Evo rom) with this root method. And CM7 is a good AOSP rom to start with.
 
OK Folks, having a weird problem here and would appreciate any help!

I ran Revolutionary, checked Debug, uninstalled Sync and EasyTether from my PC. When I run Revolutionary I get the message 'zerging for root' and then the following error message a few minutes later:

Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partition.
Errors <if any>:-
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
Press <almost> any key to exit.

I'm running GB 2.3.3, but haven't done the most recent update. Any advice??

Thanks in advance.

Hmm... What's your HBOOT. Power down, then hold down Vol Down and Power together for a few seconds. This will show your hboot and if you s-off

If you have S-Off, then you're fine (probably)
 
2.16.0001

Says S-On still :confused:

Hmm... okay

I'd try going through Revolutionary again. Also, remember this is the Dev release (at least it was last night ;) ), so it might be a bit buggy..

Try it again though, I remember some had to use unrevoked (last root method) several times before it stuck.
 
Hmm... okay

I'd try going through Revolutionary again. Also, remember this is the Dev release (at least it was last night ;) ), so it might be a bit buggy..

Try it again though, I remember some had to use unrevoked (last root method) several times before it stuck.

Have tried running it a few times, still same result :(

Should I run the most recent HTC update? Any chance that may help?
 
Have tried running it a few times, still same result :(

Should I run the most recent HTC update? Any chance that may help?
hmm.. I wouldn't update (if you are talking about the software update). Who knows, it might bump you up to HBOOT 2.20 and then you'd be SOL.

Do you have the drivers right? No AV running? Have you tried rebooting your comp?
 
hmm.. I wouldn't update (if you are talking about the software update). Who knows, it might bump you up to HBOOT 2.20 and then you'd be SOL.

Do you have the drivers right? No AV running? Have you tried rebooting your comp?

For the drivers I downloaded the driver file and ran it, I assume that's all there was to do there? Yep, no AV and have rebooted comp.

Ahhh!! Any ideas? :confused:
 
For the drivers I downloaded the driver file and ran it, I assume that's all there was to do there? Yep, no AV and have rebooted comp.

Ahhh!! Any ideas? :confused:

Hmm... not really. Just going through Ocn's OP...

Do you have debugging on?
3.make sure your phone has usb debugging on go to phone settings/applications/development/check usb debugging

What about HTC Sync?

And it ends in step six right? That's where you get your error?
 
ok went and re did everything now my phone is stuck in a loop rebooting. IDK what is going wrong never had any problems when doing my old evo

Okay, were are you on this process? Do you have S-Off? Did you flash a recovery? Where does it reboot? sometimes it reboots while booting, other times you can get to the Fastboot menu (Vol Down + Power while off)
 
it wants to keep updating bootloader then rebooting and if i dont update it I can get to ra and load the rom even but then when i restart it just goes back and does the same thing
 
Hmm... not really. Just going through Ocn's OP...

Do you have debugging on?
3.make sure your phone has usb debugging on go to phone settings/applications/development/check usb debugging

What about HTC Sync?

And it ends in step six right? That's where you get your error?

Yep, have debugging on, got rid of Sync and get stuck on step 6. Should I try resetting the phone?
 
Idk -- doing so would get rid of your apps, sms and anything else (contacts should be safe with google though)

Try the web IRC someone there might help you..

freenode Web IRC (qwebirc)

channel : #revolutionary

[22:52] <@NikonElite> !badblock
[22:52] <@Revolutionary`> badblock is If you get "Not writing bad block at 0xXXXXXXX" errors while running Revolutionary, you have a hardware error on your NAND. We have no workaround for that at the moment, sorry.

Looks like nothing for me to do? :(
 
that made the bootloader stop updating but no mater what ra starts up and wont let me past it. At least I know my sprint guy so worse comes to worse I can get a new one
 
[22:52] <@NikonElite> !badblock
[22:52] <@Revolutionary`> badblock is If you get "Not writing bad block at 0xXXXXXXX" errors while running Revolutionary, you have a hardware error on your NAND. We have no workaround for that at the moment, sorry.

Looks like nothing for me to do? :(
yup, total bummer. Can you boot back into the Stock version though?


that made the bootloader stop updating but no mater what ra starts up and wont let me past it. At least I know my sprint guy so worse comes to worse I can get a new one

What do you mean, you can't flash anything in ra?
 
Now I need help with this. I tried installing cm7 using recovery but when i rwboot it goes to the cyanogen load screen and then freezes and reloads over and over. I had to restore my phone.
 
Now I need help with this. I tried installing cm7 using recovery but when i rwboot it goes to the cyanogen load screen and then freezes and reloads over and over. I had to restore my phone.
are you wiping everything? Try to re-flash the cm7 file. I'd use the superwipe zip that ocn posted in the OP. It wipes everything you need to wipe three times. That should be all you need to do.


Sorry, still new to this, what does that mean? (And not sure I understand what the actual problem is :confused:)
Yeah me neither. And the IRC people of the world are a bit short. Got a thorough bashing with that copy and paste business eh (posting your error message)?

Well, the stock rom is what you have from sprint. I actually mis-spoke with stock rooted. You have s-on and are not rooted. Sorry. Just wanted to make sure this thing hadn't bricked ya. Your phone is still working?
 
Back
Top Bottom