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

Root I screwed up really bad. :(

FoxyDrew

Android Enthusiast
I was on the mobsterz 1.4.1 for a while and wanted to switch ROMs, so I booted into 4-ext recovery made a backup, wiped everything and flashe d the Negalite-Blue ROM. It got stuck in a bootloop at the htc screen, so I just booted into recovery wiped and flashed my backup, still had the same problem, so i wiped again and flashed the mobsterz ROM by itself. Still same problem. So i wiped and tried to flash the stock rooted ROM and it still had the problem. So i thought mabye its a problem with the recovery. So i went to the "complete noobies guide" and flahed the recovery.img from there. So when i tried to reboot into recovery i had the same problem an recovery didnt even boot, and still wont boot at all. So now all i can do is boot into Hboot. and thats it, im not sure what to do, and i considered relocking my bootloader and flashing the stock RUU but the link for the RUU.exe is down. OHH and i should mention i have hboot 1.57

edit: So i got the RUU updater and it said "error cannot update your phone, please get the correct version of updater to update your phone" I thought this would happen because when the updator opened it said i had version 1.14.xx.xx.xx and i was about to UPGRADE to version 1.13.xx.xx.xx
 
Flash this recovery while the bootloader is in fastboot USB:
[HIGH]fastboot flash recovery recovery.img[/HIGH]
Just make sure the recovery file is in the same folder as fastboot.

Once you're done with that, follow this guide, beginning with the preliminary steps. You'll be fine.
 
I was on the mobsterz 1.4.1 for a while and wanted to switch ROMs, so I booted into 4-ext recovery made a backup, wiped everything and flashe d the Negalite-Blue ROM. It got stuck in a bootloop at the htc screen, so I just booted into recovery wiped and flashed my backup, still had the same problem, so i wiped again and flashed the mobsterz ROM by itself. Still same problem. So i wiped and tried to flash the stock rooted ROM and it still had the problem. So i thought mabye its a problem with the recovery. So i went to the "complete noobies guide" and flahed the recovery.img from there. So when i tried to reboot into recovery i had the same problem an recovery didnt even boot, and still wont boot at all. So now all i can do is boot into Hboot. and thats it, im not sure what to do, and i considered relocking my bootloader and flashing the stock RUU but the link for the RUU.exe is down. OHH and i should mention i have hboot 1.57

You didnt screw up really bad. Its very hard to break these phones.

I would try to flash the recovery.img through fastboot on a PC with your phone hooked up through USB, And see if you can get TWRP back. If you can, You may need to reflash the boot.img from your installed rom through fastboot the same way as recovery, To get it to work right.

Edit: I reply too slow. :( Someone beat me to it.
 
I was on the mobsterz 1.4.1 for a while and wanted to switch ROMs, so I booted into 4-ext recovery made a backup, wiped everything and flashe d the Negalite-Blue ROM. It got stuck in a bootloop at the htc screen, so I just booted into recovery wiped and flashed my backup, still had the same problem, so i wiped again and flashed the mobsterz ROM by itself. Still same problem. So i wiped and tried to flash the stock rooted ROM and it still had the problem. So i thought mabye its a problem with the recovery. So i went to the "complete noobies guide" and flahed the recovery.img from there. So when i tried to reboot into recovery i had the same problem an recovery didnt even boot, and still wont boot at all. So now all i can do is boot into Hboot. and thats it, im not sure what to do, and i considered relocking my bootloader and flashing the stock RUU but the link for the RUU.exe is down. OHH and i should mention i have hboot 1.57

edit: So i got the RUU updater and it said "error cannot update your phone, please get the correct version of updater to update your phone" I thought this would happen because when the updator opened it said i had version 1.14.xx.xx.xx and i was about to UPGRADE to version 1.13.xx.xx.xx


I used to have similar issues with my phone and I believe that it's because I flashed bits and pieces such as Radios, hboots, etc and over time, it has created fragments/clutter up my partitions and that would cause problems when flashing roms. My advice is to not change radios, PRI, etc and as so to keep them in sync. Only thing to change is the hboot to jbear 1.50.50 to allow you to flash different roms including GB and Jellybean roms.

The solution is to run the RUU, but you would have re-lock your bootloader before running it and if you have taken the November OTA, you would have to flash the mainsetversionlow.zip. If you're S-on and took the latest March OTA (which I hope you did not take while being S-on), then you're pretty much out of luck.
 
No, but if you don't want S-OFF, you need to severely limit your expectations with what you can do with the phone. S-OFF is (very) low risk and high reward.

Well of course I know all the benefits of S-OFF but I cant do it with windows and what I meant is I really don't want to dual boot Ubuntu because it seems like too much work. :(
 
Well of course I know all the benefits of S-OFF but I cant do it with windows and what I meant is I really don't want to dual boot Ubuntu because it seems like too much work. :(

You can download a live CD of ubuntu and boot through there or make a bootable USB and have a fully working ubuntu desktop without having to install or partition anything. But there is a way to s-off through windows.

http://androidforums.com/evo-v-4g-all-things-root/695161-s-off-root-fix-everything-all-in-one.html
 
Well of course I know all the benefits of S-OFF but I cant do it with windows and what I meant is I really don't want to dual boot Ubuntu because it seems like too much work. :(

I think they offer a live cd...

I would offer you my old windows copy but it's for Evo 3d/GB.

I think Ramjet has the Virgin Mobile 1.57 hboot windows version in an all in one file somewhere. I'll see if I can dig it up.
 
You can download a live CD of ubuntu and boot through there or make a bootable USB and have a fully working ubuntu desktop without having to install or partition anything. But there is a way to s-off through windows.

Well it said you cant use LiveUSB and how can I S-OFF with Windows and if I can why isn't it mentioned somewhere on Unlimited.io Also i have no clue how too run Ubuntu off a CD. So i dont even know where to begin.

And i dont have a ubuntu/linux disc or whatever it is??
 
Well it said you cant use LiveUSB and how can I S-OFF with Windows and if I can why isn't it mentioned somewhere on Unlimited.io Also i have no clue how too run Ubuntu off a CD. So i dont even know where to begin.

And i dont have a ubuntu/linux disc or whatever it is??

Because they used to support windows so some people still have the windows versions of the software they they used to host on their site. As long as you haven't taken the March OTA update, you should still be okay to use the windows software for s-off, like everyone else has until just very recently.
 
I didn't know the unlimited.IO site updated their controlbear to only run on LInux now. That sucks.

But no worries, I still have their older windows build that I downloaded last month and used to get S-off on my replacement phone. :D

If you guys want it, I will provide it on dropbox tonight.
 
I didn't know the unlimited.IO site updated their controlbear to only run on LInux now. That sucks.

But no worries, I still have their older windows build that I downloaded last month and used to get S-off on my replacement phone. :D

If you guys want it, I will provide it on dropbox tonight.

Is it the ICS version? If so I want it. I have the GB version but would like to have a copy of the other just for safe keeping!
 
http://androidforums.com/evo-v-4g-all-things-root/695161-s-off-root-fix-everything-all-in-one.html

Look there. A whole tutorial that I just followed 2 days ago myself through windows.

If you need help, just ask away. We are here to help! :D


Some steps don't sound right in the guide, At the end of step two, it says to restore your backup. My understanding it, if you just done S-0ff, you're still on the stock rom and stock rom won't boot or will bootloop if you have jbear 1.50.50? So wouldn't restoring the stock rom backup cause the phone to bootloop?
 
I guess it doesn't matter anyways, I have Windows 8 and I keep getting an "error device not found" when trying to use any adb commands. :(. But I'd also like to mention that when I did flash the RUU I did do an OTA update (and it was just yesterday) but almost immediately unlocked my bootloader and restored from a backup that didn't have the March OTA update, so am I still screwed?
 
Is it the ICS version? If so I want it. I have the GB version but would like to have a copy of the other just for safe keeping!

Yes, it is for the ICS VM version, but I think it should work for the ICS Sprint as well.

I'm about to head off to work so I won't be able to put it up until tonight. Link will be up when as soon as I get it on dropbox.
 
I guess it doesn't matter anyways, I have Windows 8 and I keep getting an "error device not found" when trying to use any adb commands. :(. But I'd also like to mention that when I did flash the RUU I did do an OTA update (and it was just yesterday) but almost immediately unlocked my bootloader and restored from a backup that didn't have the March OTA update, so am I still screwed?

Have you installed the correct drivers for the phone? Ill have to get a link.. But that could be the reason why it isnt finding your device.

It doesnt hurt in trying to get s-off after taking the OTA. Many people are wondering if this will work with the new Hboot or not. Reboot into your bootloader and see what version Hboot you have.
 
Have you installed the correct drivers for the phone? Ill have to get a link.. But that could be the reason why it isnt finding your device.

It doesnt hurt in trying to get s-off after taking the OTA. Many people are wondering if this will work with the new Hboot or not. Reboot into your bootloader and see what version Hboot you have.

Yes I've tried using the HTC sync drivers and the drivers from the thread listed above, they both give the same error. And I am on Hboot 1.57.

Also while I'm in hboot it says FASTBOOT USB highlited in red so i know thats not the problem.
 
Yes I've tried using the HTC sync drivers and the drivers from the thread listed above, they both give the same error. And I am on Hboot 1.57

If you are still on Hboot 1.57 your good to go about s-offing, As long as you can get your PC to read your phone. You dont have the dreaded Hboot 1.58, Which is a good thing. :p

My laptop has windows 8 on it, And I managed to get it to work with it. I cant remember if there was other steps involved, But it seems to work for me. Try reinstalling HTC sync. You will have to uninstall it for the s-off procedure anyway, But the drivers will stay intact.
 
I guess it doesn't matter anyways, I have Windows 8 and I keep getting an "error device not found" when trying to use any adb commands. :(. But I'd also like to mention that when I did flash the RUU I did do an OTA update (and it was just yesterday) but almost immediately unlocked my bootloader and restored from a backup that didn't have the March OTA update, so am I still screwed?
You might want to read though this XDA thread. I helped a VM user with Windows 8 get S-OFF recently and the link to my root/S-OFF guide and the guide to install drivers in Windows 8 are linked in post #7. The version of the JuopunutBear utility included in my-all-one file is an older release that still requires rooting before S-OFF.

ramjet73
 
Some steps don't sound right in the guide, At the end of step two, it says to restore your backup. My understanding it, if you just done S-0ff, you're still on the stock rom and stock rom won't boot or will bootloop if you have jbear 1.50.50? So wouldn't restoring the stock rom backup cause the phone to bootloop?
Thank you for pointing that out. While nowhere in the guide has you rebooting into that restore, it has been removed as erroneous and unnecessary.

What other steps did you notice to be incorrect?
 
Back
Top Bottom