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

Root Help!!!

I

iamse7en

Lurker
OMG, when I tried to use the unrevoked s-on .zip for my Evo, I kept getting an error. So I thought I could just go around this step. HUGE mistake. I ran the RUU and set my system back to stock, but now I have all of these errors on my phone and the S is still set to off. I wanted to take the phone back to Sprint to see if they could fix a shut-down issue I keep having, now I don't know what to do. Can you guys help me?

Here are some stats:
HBOOT - 2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO - 2.15.00.12.19

So much for thinking I knew enough... smh...:confused:
 
iamse7en said:
OMG, when I tried to use the unrevoked s-on .zip for my Evo, I kept getting an error. So I thought I could just go around this step. HUGE mistake. I ran the RUU and set my system back to stock, but now I have all of these errors on my phone and the S is still set to off. I wanted to take the phone back to Sprint to see if they could fix a shut-down issue I keep having, now I don't know what to do. Can you guys help me?

Here are some stats:
HBOOT - 2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO - 2.15.00.12.19

So much for thinking I knew it all... smh...:confused:
Click to expand...
welcome to the forums!!!!!!
is your bootloader locked now? if you have s-off you can just put a custom recovery back on, but you have to have your bootloader unlocked first.
 
ocnbrze said:
welcome to the forums!!!!!!
is your bootloader locked now? if you have s-off you can just put a custom recovery back on, but you have to have your bootloader unlocked first.
Click to expand...

Well, yeah, it's locked in the bootloader screen. What's the fix? Also, I have this error .67 and one for the voicemail as well. :(
 
iamse7en said:
I used Unrevoked about 1.5yrs ago. Yes, I can get to bootloader, but not to recovery...
Click to expand...

ok first you will need a recovery. go here:http://androidforums.com/evo-4g-all...ooting-dummies-guide-gingerbread-edition.html and go to the switching recovery section for instructions on how to get recovery.

once that is done then go to the unrooting part of the guide. skip to the part where it says in red "if for some reason you can't get s-on after flashing the hboot 6.17 file then here is the instructions:"

hopefully this should work.
 
Rxpert83 said:
You shouldnt have H-boot 2.18....

Did you accept the OTA while rooted? Or did you run the newest RUU?
Click to expand...

yeah i believe it was the ruu that locked the bootloader with s-off still. as long as there is a custom recovery, unrevoked's s-on tool should be able to fix the problem.
 
ocnbrze said:
ok first you will need a recovery. go here:http://androidforums.com/evo-4g-all...ooting-dummies-guide-gingerbread-edition.html and go to the switching recovery section for instructions on how to get recovery.

once that is done then go to the unrooting part of the guide. skip to the part where it says in red "if for some reason you can't get s-on after flashing the hboot 6.17 file then here is the instructions:"

hopefully this should work.
Click to expand...

Sweet! I'll get on that now! I'll let you know how it goes. :o
 
ocnbrze said:
ok first you will need a recovery. go here:http://androidforums.com/evo-4g-all...ooting-dummies-guide-gingerbread-edition.html and go to the switching recovery section for instructions on how to get recovery.

once that is done then go to the unrooting part of the guide. skip to the part where it says in red "if for some reason you can't get s-on after flashing the hboot 6.17 file then here is the instructions:"

hopefully this should work.
Click to expand...

It took some cajoling, but so far, everything is working well. Since I already did the stock rom before all this mess happened, do I need to do it again? Or do I just need to install another stock rom? Also, when I went back into bootloader and saw S-on, I saw that it said "locked oow" at the top of the page. Is that a good thing? Lastly (and trust, I appreciate all of the great help I've received), what should I do about the error 67 I keep getting?
 
iamse7en said:
It took some cajoling, but so far, everything is working well. Since I already did the stock rom before all this mess happened, do I need to do it again? Or do I just need to install another stock rom? Also, when I went back into bootloader and saw S-on, I saw that it said "locked oow" at the top of the page. Is that a good thing? Lastly (and trust, I appreciate all of the great help I've received), what should I do about the error 67 I keep getting?
Click to expand...

ERROR 67
http://androidforums.com/sprint-her.../13197-data-call-failure-error-code-67-a.html

hopefully this can help. its an old thread but same issue with the error

from the looks of the rest of this post you have locked to the bootloader back down to S-ON which is Securities ON this is a Readable state only. You cannot write to the boot loader you will need to obtain S-off or S-on via HTC method see your Hboot is 2.18 so you need the HTC method found here
 
iamse7en said:
It took some cajoling, but so far, everything is working well. Since I already did the stock rom before all this mess happened, do I need to do it again? Or do I just need to install another stock rom? Also, when I went back into bootloader and saw S-on, I saw that it said "locked oow" at the top of the page. Is that a good thing? Lastly (and trust, I appreciate all of the great help I've received), what should I do about the error 67 I keep getting?
Click to expand...

ok so you have s-on now and a locked bootloader. there is not much else you can do at this point. you can try and do a factory reset, but that is the problem on unrooted phones. there is not much troubleshooting you can do, at this point all you can do other then a factory reset is to take it in.
 
argedion said:
ERROR 67
http://androidforums.com/sprint-her.../13197-data-call-failure-error-code-67-a.html

hopefully this can help. its an old thread but same issue with the error

from the looks of the rest of this post you have locked to the bootloader back down to S-ON which is Securities ON this is a Readable state only. You cannot write to the boot loader you will need to obtain S-off or S-on via HTC method see your Hboot is 2.18 so you need the HTC method found here
Click to expand...

Thanks for your help. I'm checking out the Error 67 stuff now. As for the bootloader lock, since I never saw it before rooting it, I just wanted to make sure it looks ok and everything is ok with it before I take it to Sprint.

All you guys are awesome!:cool:
 
You must log in or register to reply here.
Back
Top Bottom