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

Root stuck on bootloop s-on hboot 1.40?

fplives

Newbie
I have a phone I bought on ebay that i'm trying to bring back to life?I'm kinda a newb but tried using fastboot to flash a new or the stock rom kept getting errors.Tried running RUU_Shooter_ICS_35_S_Sprint_WWE_VM nothing said it was the wrong update?Almost done thought someone here could help?Thanks for anything anyone could do.I already have a Motorola triumph that I run miui on.Was thinking of changing phones but this one has a bad esn.I just want to see this running again.I know it's not bricked.Thanks:D
 
It's because your phone probably took the OTA update and there is no RUU for that update. And being s-on, it won't allow you to run an earlier RUU.

Go here: http://forum.xda-developers.com/showthread.php?t=1865569 and get the SetMainVersionLOW.zip

Flash that through recovery, then you should be able to run the RUU!

I can't even get recovery to flash through fastboot?What do I do with that?Do I extract into the same folder as fastboot?Thanks
 
No that zip needs to go on your sd card so that once you are in recovery you can flash it.

So you can't access recovery at all?? If you have a recovery.img in your fastboot folder, try using this command: fastboot boot recovery.img
(recovery.img being the exact name of the file)

See if that will get you into recovery. If you don't have a recovery.img I can get you one.
 
It said failed remote not allowed.Maybe I have the wrong recovery?Thanks for the help.I'm still trying haven't gave up yet......
 
Oh! Sounds like the bootloader is locked... Crap, you probably don't have the unlock token as you got it second hand.

Just to let you know, I am going to be busy for the next few hours but I will try to pop in and answer quick questions when possible.

First boot into the bootloader: do a battery pull then hold volume down+power. Type out what it says there. If it is locked or relocked go to this guide:
http://androidforums.com/evo-v-4g-a...ing-evo-v-4g-roms-kernels-using-fastboot.html
and follow step 4 to unlock the bootloader through htc dev. Once that is done, follow the steps in my last post to get into recovery and flash the SetMainVersionLOW.zip.

Then after that flashes, you will need to lock the bootloader again: fastboot oem lock and then run the RUU with a locked bootloader. That should get you booted back up and stock again.

I will check in and try to answer when I can over the next few hours. Normally I would try to get more detailed but I'm in a hurry and you seem to know your way around a bit so I hope you understand all those instructions. Just let me know if you don't understand something.
 
Ugh. I just had an after thought. I'm sorry it's been a really hectic day so I've been kind of distracted on my replies. If you are on hboot 1.4 that means that the phone is s-off. I think you can't run the Ruu because you aren't on a stock hboot. Give me a minute and I will post another link and copy/paste instructions.

I don't know how you could be s-on and on hboot 1.4.... You have to be s-off to change hboots and if you turned s back on while on a non stock hboot it would hard brick the phone... Please post the info from your bootloader screen!!
 
Thanks Brian. when I enable fastboot this is what it says above FASTBOOT USB (red)
(green)SHOOTER XC SHIP S-ON RL
HBOOT-1.40.0000 eMMC-boot June 8, 2011 17:20:22 .It doesn't however say Locked or Unlocked....Hope that helps..Not giving up.
 
If you are indeed s-off then download this hboot: https://dl.dropbox.com/u/100923173/Hboot/Hboot_1.57_PG86IMG.zip

I am going to copy/paste my instructions for how to use that file:
First let me start by stressing something important! Verify the integrity of the download by checking the file against its md5 checksum that I provided for each file. You can use a free software such as MD5 Checker to do the job. Or if you'd like to check on your phone without a pc, download MD5 Checker for android from the play store. If for whatever reason your download gets corrupted, using a corrupted file can brick your phone! So use an md5 checker to verify the integrity of the file, it's quick and easy and can keep your phone safe!

1. Download File. Check md5 for a match ;)

2. Place the file on the root of your sd card (not in any folders).

3. Rename the file to PG86IMG.zip

4. Reboot into bootloader.

5. When asked to update, say yes by hitting volume up.

6. When it's all finished, hit power button to reboot.

7. *Important! After booting up, immediately rename or delete the file.

*The presence of the file on your sd card will prevent you from entering recovery in an emergency situation. It's nothing to panic about, but if you get caught in a bootloop, you will have to manually remove the file using a pc and card reader or another phone. That said, to avoid bootloops and being stuck with no way to boot up and no way to enter recovery, plan ahead. If you are on a rom that requires hboot 1.58 and you flash hboot 1.5, you will hit a bootloop and not be able to access recovery. You would then need to remove the file or flash a compatible rom through fastboot connected to a pc.

Okay. Now with instructions and warnings out of the way, I will give you my personal preference on how to flash a different hboot that will be incompatible with your current rom without getting a bootloop and having to use a pc to fix the situation.

Follow steps 1-3 above. Stop! Now, instead of rebooting into the bootloader, we are going to bypass the bootloader by rebooting directly into recovery. Some roms have this feature built in. I recommend downloading something like ROM TOOLBOX from the play store. It's a great app to have if you are rooted. Rom Toolbox has a built in rebooter menu (with widgets) that allows this function. Alternatively go get QUICK REBOOTER from the play store. So once in recovery, wipe and flash the rom normally. Once finished, continue to steps 4-7.

This will allow you to do everything completely from your phone and avoid getting stuck. Remember, this is just for when you are changing hboots that will be incompatible with the rom you are already using (ie: ICS to GB). Just following steps 1-7 normally is fine for just flashing radios or switching between different GB hboots etc.


So then if you are s-off, and flash the stock hboot, you should be able to run the ruu without locking the bootloader or flashing the setmainversionlow.zip.
 
Thanks Brian. when I enable fastboot this is what it says above FASTBOOT USB (red)
(green)SHOOTER XC SHIP S-ON RL
HBOOT-1.40.0000 eMMC-boot June 8, 2011 17:20:22 .It doesn't however say Locked or Unlocked....Hope that helps..Not giving up.


Ahhhhhhhhhh!!! The reason it doesn't say locked or unlocked is because it is a custom hboot and it doesn't display that information. I'm pretty sure it's locked though with the error you got running the fastboot command.

I'm starting to worry you got ripped off. It sounds like the previous owner turned s-on while on a custom hboot.... This leaves you stuck... You can't change the hboot because the phone is s-on. You can't get s-off without unlocking the bootloader through htc dev. I don't know that you can unlock it while on a custom hboot....

I am stumped at the moment and really have to get going. I need to think about this a little more with a clearer head. I am going to ask a couple guys to check this thread. If there is a way out of this, they will be able to help. I really hope you didn't get screwed here but that custom hboot with s-on really has me worried for you....
 
I cant even see my sd card .I'm running fastboot through my desktop.will that work?What commands or command do I use do update load the hboot update?Fastboot does see my phone.
 
if someone had turned s on with a custom hboot,then youd have a device that does not boot to anything :eek:

1.40.0000 is a stock sprint GB hboot. as evidenced by this,and your main version(1.13.651.7) id say you have a sprint evo on oooooold firmware,not an evo v. youre getting the error because your trying to flash the virgin mobile RUU

try this RUU:
Shipped ROMs

then afterward,IMMEDIATELY download and run Revolutionary to get s off,as it is a much easier process than the jpbear tool needed for 1.50+ hboots :)
 
Scotty's instructions sound correct from my research too -- give Revolutionary a try, and then report back on results/problems -- we will help you get the phone working, because it's definitely not a lost cause, as you have power to the phone (not bricked).
 
I'll try this and get back to you guys.Thanks everyone.I can't seem to get revolutionary to see my phone.I unzipped the folder, opened it and it says waiting for device.Should I have moved the unzipped folder to the same one that has fastboot. because I still have fastboot usb on?
 
You need a working phone to run revolutionary. As I said above,run the ruu I linked FIRST ;)

It's the same version you are on,and will not update hboot.

Once the phone boots and is working,THEN run revolutionary :)
 
Along with what Scotty said above,

Make sure you have the correct drivers installed on your computer -- what operating system are you using? If it's Windows 7, these drivers will set you straight. I also have this package which contains adb and fastboot in the S-OFF folder.

Just open it in a terminal and run "fastboot devices" to see if it'll give you a serial number. In order for fastboot to work, you should be in the bootloader (pull the battery out, then replace it. Hold the volume down button, and press the power button. Your phone will boot into the bootloader, and you can run fastboot from there.
 
Ran several ruu's now have hboot version 1.50 Also phone says locked .Still no boot though after running ruu.I still get boot loop screen white with htc for 30 sec or so powers off same thing Also now phone main ver is 2.08.651.3......Sorry if I'm in the wrong forum.I was told it was the vm version.Thanks for all the help your giving me?I fell like were close to getting it going!!
 
Ran several ruu's now have hboot version 1.50 Also phone says locked .Still no boot though after running ruu.I still get boot loop screen white with htc for 30 sec or so powers off same thing Also now phone main ver is 2.08.651.3......Sorry if I'm in the wrong forum.I was told it was the vm version.Thanks for all the help your giving me?I fell like were close to getting it going!!

That's odd after running the Ruu it should boot up. It changed your hboot and main version... Looks like you were successful. It should just boot right up as the ruu contains everything you need... You see locked now because the ruu returned you to the stock bootloader. It was already locked before but the custom bootloader hid that. Seriously I'm baffled on this one. I've helped a lot of people with this device and am very comfortable with it but I have never seen anything like your problem. Obviously the ruu worked. It makes no sense that it still won't boot.... :confused:
 
Ran several ruu's now have hboot version 1.50 Also phone says locked .Still no boot though after running ruu.I still get boot loop screen white with htc for 30 sec or so powers off same thing Also now phone main ver is 2.08.651.3......Sorry if I'm in the wrong forum.I was told it was the vm version.Thanks for all the help your giving me?I fell like were close to getting it going!!
It's definitely an Evo 3D if you were able to flash the 2.08.651.3 version of the GB RUU. I don't know why the phone is powering off instead of booting.

You are not going to be able to use Revolutionary with hboot 1.5 so I suggest that you bring it up to the Sprint ICS level by flashing the 2.89.651.2 RUU that you can find here and see what happens after that. If all goes well you can still get S-OFF using the JuopunutBear wire trick.

ramjet73
 
Now i'm having a problem?I can get to fastboot.But now my pc doesn't recognize the phone.Calling it an unknown device?Tried installing HTCDriver_4.0.1.001_20121107 then went back to 3.0 still nothing.When I run the ruu it says a usb not recognized?Any takers on that one?So it doesn't go to fastboot usb mode.
 
Now i'm having a problem?I can get to fastboot.But now my pc doesn't recognize the phone.Calling it an unknown device?Tried installing HTCDriver_4.0.1.001_20121107 then went back to 3.0 still nothing.When I run the ruu it says a usb not recognized?Any takers on that one?So it doesn't go to fastboot usb mode.
Try rebooting your PC and see if that resolves it. Sometimes the USB connection gets hung and a reboot will clear that.

ramjet73
 
It's impossible to be s on and on a custom hboot. The stock 1.40 hboot simply does not have htcdev compatibility. Before running any more RUUs I would try the factory reset and clear storage options in hboot. It could something lurking somewhere the ruu doesn't update,but the stock recovery can clear.

Failing that,you prolly have some sort of hardware failure,as prolly 99.9% of software issues are always resolved by factory reset/ruu. :(

As a last resort,you could try unlocing the bootloader and installing a recovery. This would give the option to use adb commands,and you could try flashing a Rom. Based on the ineffectiveness of multiple RUUs I don't want to get your hopes up too high,unfortunately :(
 
Back
Top Bottom