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

Root Been stuck on bootloader screen for DAYS!!!

taatoken

taatoken

Member
hello,
My Ultimate goal is to run CM 10.1 "wild for the night" on my phone but I have run into a major roadblock and need some help.

On the RUU/unrooting guide step 3 and step 3 ALT have not worked on my phone and my phone keeps rebooting into the bootloader screen after all attempt.

My phone screen reads
***RELOCKED***
***SECURITY WARNING***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.09.00.0706

I have been using RUU_Shooter_ICS_35_S_Sprint_WWE_VM_1.13.652.2_Radio_1.06.00.0426_NV_1.53_144_release_262287_signed
which gives me an error 140
and
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed
which gives me an error 131

Can some please point me in the right direction? I have been patiently waiting within the RUU guide but it seem like the thread is tainted with leprosy and no one whats to touch it.
 
Hey taatoken. Sorry I hadn't seen your post in the other thread. You will be wanting to use the first RUU you listed that you are getting an error 140 on.

Please head to this thread:
http://forum.xda-developers.com/showthread.php?t=1865569
and download the setmainversionLOW.zip

Flash that through recovery just like you would any rom. After it flashes you should be able to run the RUU successfully! Also, if you weren't already, try running the RUU from fastboot usb mode rather than booted into a rom!
 
Brian706 said:
Hey taatoken. Sorry I hadn't seen your post in the other thread. You will be wanting to use the first RUU you listed that you are getting an error 140 on.

Please head to this thread:
http://forum.xda-developers.com/showthread.php?t=1865569
and download the setmainversionLOW.zip

Flash that through recovery just like you would any rom. After it flashes you should be able to run the RUU successfully! Also, if you weren't already, try running the RUU from fastboot usb mode rather than booted into a rom!
Click to expand...
Downloaded and set inside my sdcard, but I can not get to TWRP. Could you please supply a link or steps to confirm I am following proper procedures?

davidmargolin said:
ur using hboot 1.57... u need hboot 1.04/1.4/1.5
Click to expand...
I believe that RUU flashes it to 1.04/1.4/1.5 but correct me if I am wrong.
 
taatoken said:
Downloaded and set inside my sdcard, but I can not get to TWRP. Could you please supply a link or steps to confirm I am following proper procedures?

Can you do a battery pull then hold Volume down+power to get to the bootloader? Then use volume keys to navigate to recovery and power button to select recovery.

Otherwise connect to pc like when you first rooted and use adb reboot bootloader

from there use volume keys to navigate to bootloader and power button to select bootloader. Then from there select recovery as per above.

I believe that RUU flashes it to 1.04/1.4/1.5 but correct me if I am wrong.
Click to expand...

The RUU restores the stock hboot which for the Evo V is 1.57.0000.
To flash any of those other hboots, s-off is requried.
 
Can you do a battery pull then hold Volume down+power to get to the bootloader? Then use volume keys to navigate to recovery and power button to select recovery. Otherwise connect to pc like when you first rooted and use adb reboot bootloader from there use volume keys to navigate to bootloader and power button to select bootloader. Then from there select recovery as per above. I believe that RUU flashes it to 1.04/1.4/1.5 but correct me if I am wrong.[/QUOTE said:
so though a miracle of the lord (IDK what I did) I got the PG86IMG.zip to run but now I am getting a CID incorrect.
Brian706 said:
Ok. I just downloaded it to look at it. It was only specified for evo 3d. I edited it to work with evo v as well. Try this: http://db.tt/5w5fc7y8 (

Just put the file as is on the root of your sd card not in any folders. No need to rename or anything.
Click to expand...
(yea I did do alot of searching before I posted)
I should be running this RUU .zip fill correct?
RUU_Shooter_ICS_35_S_Sprint_WWE_VM_1.13.652.2_Radio_1.06.00.0426_NV_1.53_144_release_262287_signed
Click to expand...
 
Just did it with RUU_Shooter_ICS_35_S_Sprint_WWE_VM_1.13.652.2_Radi o_1.06.00.0426_NV_1.53_144_release_262287_signed

Main Version is older
Update Fail!
Press <POWER> TO REBOOT

adb reboot recovery method

C:\sdk-tools>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

C:\sdk-tools>
 
Sorry I'm off the pc now and may be a little slower to respond. The main version error happens because you are on the latest update and there is no ruu for that version. You need to first flash that zip I posted a couple posts up SetMainVersionLOW. That will lower the main version and allow you to run the Ruu.


This is the correct ruu : RUU_Shooter_ICS_35_S_Sprint_WWE_VM_1.13.652.2_Radi o_1.06.00.0426_NV_1.53_144_release_262287_signed

The cid error sounds like maybe it was for a sprint ruu. After lowering the main version, the ruu exe should work for you.
 
Brian706 said:
Sorry I'm off the pc now and may be a little slower to respond. The main version error happens because you are on the latest update and there is no ruu for that version. You need to first flash that zip I posted a couple posts up SetMainVersionLOW. That will lower the main version and allow you to run the Ruu.


This is the correct ruu : RUU_Shooter_ICS_35_S_Sprint_WWE_VM_1.13.652.2_Radi o_1.06.00.0426_NV_1.53_144_release_262287_signed

The cid error sounds like maybe it was for a sprint ruu. After lowering the main version, the ruu exe should work for you.
Click to expand...
Thank you soo much. I am still having trouble getting into recovery and adb reboot recovery did not work because "error: device not found" If your wondering I have been transferring PG86img files via card reader.
suggestions?
 
The command is adb reboot bootloader

But device not found seems like a driver issue or an issue with the usb cable. Possibly usb/adb debugging isn't enabled?

Did you try accessing recovery by doing a battery pull and holding volume down +power?

You can't really use PG86IMG files while s-on. Unless it's that version of the ruu. Also having a PG86IMG zip on your sd card will prevent you from accessing recovery. So delete it if you gave one on there and see if you can access recovery then.
 
Took of PG86 and still keeps rebooting into bootloader, did the battery pull and the screen flashes then goes to the green HTC screen with a gold bar filling up on the top right and once it fill the bootloader appears.
 
Brian706 said:
But device not found seems like a driver issue or an issue with the usb cable. Possibly usb/adb debugging isn't enabled?
Click to expand...

Let's go back to this. How did you go about getting the drivers on your PC? Is it a PC? Which OS? Does your computer have USB3 ports? Is HTC Sync on there?

Does the OP have any other physical connectivity things to confirm?
 
You should try going S-Off man. After that I don't think you'll need to run the RUU. You just download the correct hboot for CM10.1, and whatever Radio you want. (One at a time as PG86IMG.zip files. You place one on the sdcard. Reboot boot loader. Install update. Then remove the zip and do the other one. Then remove that. Then boot to recovery, and install your ROM.) Sounds a lot easier then screwing with the RUU. You don't need to return to stock to get CM10.1 you actually need to be the exact opposite of stock. You need S-Off to install a lower hboot anyways in order to use CM10.1 so you might as well get started. Takes time but it will work as long as you don't give up. Why exactly did you decide to indoor and run the RUU anyways???
 
@hatred

ControlBear software for s-off has actually been updated and now requires to be on the ruu with unlocked bootloader and unrooted.


@taatoken

I'll be on the pc in a bit and can help you some more.
 
taatoken, I think maybe you need to flash your recovery again so that you can boot into and flash the SetMainVersionLOW.zip.

Then you should be able to run the RUU.

Make sure you still have a recovery.img in your adb/fastboot folder on the PC.

Get into fastboot with adb reboot bootloader

Then use fastboot flash recovery recovery.img

Then fastboot boot recovery.img

You should be able to boot recovery this way and flash that zip. Once the zip is flashed, the RUU should be good to go.
 
Palmetto Fellow said:
Let's go back to this. How did you go about getting the drivers on your PC? Is it a PC? Which OS? Does your computer have USB3 ports? Is HTC Sync on there?

Does the OP have any other physical connectivity things to confirm?
Click to expand...

How did you go about getting the drivers on your PC?
Downloaded them from HTC support site.
Is it a PC?
PC running windows 7 sp1 and has a pc score of 5.9
Which OS?
Windows 7
Does your computer have USB3 ports?
No none of my ports are USB 3.0
Is HTC Sync on there?
yes the latest version

Does the OP have any other physical connectivity things to confirm?
my layer one is (oh my net+/A+ days) is a usb wireless card, usb mouse and keyboard, and lastly cheap headphones.
 
Brian706 said:
taatoken, I think maybe you need to flash your recovery again so that you can boot into and flash the SetMainVersionLOW.zip.

Then you should be able to run the RUU.

Make sure you still have a recovery.img in your adb/fastboot folder on the PC.

Get into fastboot with adb reboot bootloader

Then use fastboot flash recovery recovery.img

Then fastboot boot recovery.img

You should be able to boot recovery this way and flash that zip. Once the zip is flashed, the RUU should be good to go.
Click to expand...

So just to clarify erase the recovery.img i have in the root of my SDcard and copy the one i have in the sdk-tools in its place?
 
taatoken said:
So just to clarify erase the recovery.img i have in the root of my SDcard and copy the one i have in the sdk-tools in its place?
Click to expand...

No. You need the recovery.img on your computer. In the same folder that adb and fastboot are in. If you rooted with the complete newbies guide, the recovery.img is probably still in that folder! But if you do not have it in there, you need to put it there.
 
ok it is there, my phone still goes start to bootloader after every recovery time, I explored my twrp folder and only the 0000000000000000 no the htc...... has stuff inside of it, is this normal??
 
You must log in or register to reply here.
Back
Top Bottom