• 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 said:
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??
Click to expand...

I'm not sure exactly what you are asking?

So you successfully reflashed the recovery using fastboot flash recovery recovery.img ??

And you got a confirmation in command prompt that it was successful?

Then you used fastboot boot recovery.img and it just puts you back in the bootloader after running that command?


If you want to try another recovery download this:
https://dl.dropbox.com/u/100923173/4ext_1.0.0.5.rc9_recovery.img

Rename the one you already have to twrp_recovery.img and rename this downloaded one to recovery.img

Then do fastboot flash recovery recovery.img

fastboot boot recovery.img

Also is your phone in fastboot usb mode when running the commands? I mean, you haven't gotten any errors or anything?
 
Brian706 said:
I'm not sure exactly what you are asking?

So you successfully reflashed the recovery using fastboot flash recovery recovery.img ??

And you got a confirmation in command prompt that it was successful?

Then you used fastboot boot recovery.img and it just puts you back in the bootloader after running that command?


If you want to try another recovery download this:
https://dl.dropbox.com/u/100923173/4ext_1.0.0.5.rc9_recovery.img

Rename the one you already have to twrp_recovery.img and rename this downloaded one to recovery.img

Then do fastboot flash recovery recovery.img

fastboot boot recovery.img

Also is your phone in fastboot usb mode when running the commands? I mean, you haven't gotten any errors or anything?
Click to expand...

So you successfully reflashed the recovery using fastboot flash recovery recovery.img ??

And you got a confirmation in command prompt that it was successful?

No i explored the file using my card reader...
I think a video will better explain what is happening.
give me a minute.
 
I think if you boot the recovery using the fastboot commands you will be fine. I'm not sure what you are trying to do?

You need recovery to flash the zip and then you will be able to run the Ruu.

You should be able to boot the recovery using the commands I mentioned above.

I'm just confused. I'm giving you instructions to help you out but you aren't doing them? I think you'll need to be more straight forward with me.

If I post instructions and you don't understand or aren't going to do them please let me know. I want to help you get back to where you want to be but if you aren't going to take my advice then I feel like I'm wasting my time.

Maybe I misunderstood what you are saying but i really think you will be able to boot your recovery through fastboot.
 
Brian706 said:
I think if you boot the recovery using the fastboot commands you will be fine. I'm not sure what you are trying to do?

You need recovery to flash the zip and then you will be able to run the Ruu.

You should be able to boot the recovery using the commands I mentioned above.

I'm just confused. I'm giving you instructions to help you out but you aren't doing them? I think you'll need to be more straight forward with me.

If I post instructions and you don't understand or aren't going to do them please let me know. I want to help you get back to where you want to be but if you aren't going to take my advice then I feel like I'm wasting my time.

Maybe I misunderstood what you are saying but i really think you will be able to boot your recovery through fastboot.
Click to expand...
i cannot use the commmands because my device is not found, i have been doing everything you say to a tee.
 
Brian706 said:
I'm just confused. I'm giving you instructions to help you out but you aren't doing them? I think you'll need to be more straight forward with me.

If I post instructions and you don't understand or aren't going to do them please let me know. I want to help you get back to where you want to be but if you aren't going to take my advice then I feel like I'm wasting my time.
Click to expand...
I totally agree with brian706 on this. I've been following this thread to see if I could help but I really don't understand what you are doing either.

When brian706 (or anyone that tries to help you) gives you instructions you need to follow them exactly and report back to them the results. Don't try to adlib or do other things while someone is trying to help as that just gets in the way of solving the problem.

ramjet73
 
taatoken said:
i cannot use the commmands because my device is not found, i have been doing everything you say to a tee.
Click to expand...
That's a perfect example of what we are talking about.

You can't be following the instructions brian706 is giving you if your PC isn't communicating with the phone.

ramjet73
 
Okay thank you. I thought you were just ignoring steps :p let's try to communicate and stay on the same page at each step!

Okay, are you getting the device not found when using the adb reboot bootloader command? If so let try it this way.

Boot into bootloader by holding volume down + power. May need a battery pull first.

Then select fastboot from there bootloader screen. Plug in the phone and you should see fastboot usb in red letters on the phone screen.

If you do then type:
fastboot boot recovery.img

See if that will get you into recovery.

If you hit any errors tell me exactly what they say!
 
Brian706 said:
Okay thank you. I thought you were just ignoring steps :p let's try to communicate and stay on the same page at each step!

Okay, are you getting the device not found when using the adb reboot bootloader command? If so let try it this way.

Boot into bootloader by holding volume down + power. May need a battery pull first.

Then select fastboot from there bootloader screen. Plug in the phone and you should see fastboot usb in red letters on the phone screen.

If you do then type:
fastboot boot recovery.img

See if that will get you into recovery.

If you hit any errors tell me exactly what they say!
Click to expand...
Got an error
FAILED <remote: not allowed>
 
Brian706 said:
Hmm I'm not familiar with that error. That happened with fastboot boot recovery.img?
Click to expand...
yes sir!!
check my work please.:(
C:\sdk-tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.520s]
booting... FAILED (remote: not allowed)
finished. total time: 1.521s

C:\sdk-tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.757s]
booting... FAILED (remote: not allowed)
finished. total time: 1.758s
 
I think he relocked ramjet73. Thank you because now I don't have to figure out that error :)


Okay so you need to unlock your bootloader again with your unlock token.

fastboot flash unlocktoken Unlock_code.bin

I assume you still have it? It should work to use it again.

So then after unlocking, then try the steps from the last post!
 
taatoken said:
Step 2) Lock the bootloader from RUU
***RELOCKED***
***Seecurity Warning***
I have the htcdev unlock
Click to expand...
I'm not sure which guide you are quoting but I think that relock is to allow flashing the RUU. Once that's installed you need to unlock the bootloader again.

Edit: Sorry to duplicate the info. I think brian706 will take it from here. ;)

ramjet73
 
taatoken said:
yes sir!!
check my work please.:(
C:\sdk-tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.520s]
booting... FAILED (remote: not allowed)
finished. total time: 1.521s

C:\sdk-tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.757s]
booting... FAILED (remote: not allowed)
finished. total time: 1.758s
Click to expand...

Well that's good news. I'm happy to see that you are running the commands right and from the proper directory. Your bootloader just needs to be unlocked to use fastboot commands. I guess I forgot or hadn't realized the bootloader was locked!
 
fastboot flash unlocktoken Unlock_code.bin worked and now it is downloading from the boot.img
Thanks for your patience!
how long should it take?
 
It should pop up on your phone screen and you should have to confirm on your phone that your want to unlock. It's been a long time since I unlocked so I can't remember the exact thing that it says but pretty much immediately after flashing the unlock token something should pop up on the phone.

Ughh please tell me we aren't going to hit another snag!
 
Brian706 said:
It should pop up on your phone screen and you should have to confirm on your phone that your want to unlock. It's been a long time since I unlocked so I can't remember the exact thing that it says but pretty much immediately after flashing the unlock token something should pop up on the phone.

Ughh please tell me we aren't going to hit another snag!
Click to expand...
Sorry to jump in again but I think he said the unlock worked and he was hung up on the boot.img. I'm not sure why he's flashing that since you told him to flash, then boot, recovery.img. :confused:

He really needs to post the commands he is issuing and the responses he is getting.

ramjet73
 
By all means, no need to apologize :)
You're right after reading back the unlock appears to have been successful.

Maybe I wasn't clear enough about what step to jump to after unlocking.

As ramjet73 said, if you are unlocked you should run the command: fastboot boot recovery.img

See if that will get you into recovery.

If so, flash the SetMainVersionLOW zip, then we should be able to run the Ruu! We're making progress and getting closer! :beer:
 
ramjet73 said:
Sorry to jump in again but I think he said the unlock worked and he was hung up on the boot.img. I'm not sure why he's flashing that since you told him to flash, then boot, recovery.img. :confused:

He really needs to post the commands he is issuing and the responses he is getting.

ramjet73
Click to expand...
this is the what i did.

C:\sdk-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s

C:\sdk-tools>fastboot boot recovery.img
downloading 'boot.img'...

I apologize that if I messed up or took brian706 steps out of order but I am learning and trying. If you would like any infomation about EKGs, EEGs or any cardiovascular equipment, this is my area of expertise, htc phones are not.

So should I yes unlock bootloader?
 
Brian706 said:
If so, flash the SetMainVersionLOW zip, then we should be able to run the Ruu! We're making progress and getting closer! :beer:
Click to expand...
Don't forget to relock after successfully flashing the setmainverlow.zip and before flashing the RUU. ;)

Edit1: It doesn't look like the "fastboot boot recovery.img" took. It might help to remove/replace the battery, start the bootloader and try it again.

Edit2: I just noticed your question about responding to the unlock bootloader prompt. Yes, you need to do that or it won't unlock.

ramjet73
 
Hmm it looks as if he ran the right command. Any ideas why it is stuck on downloading boot.img ramjet?

I know the commands but haven't dealt with any problems using them so I'm not familiar with all the errors or terminology that command prompt throws back sometimes.

taatoken you are doing a good job following the steps. Don't worry. And we will make it through this!
Booting the recovery should online take a short time. So I'm not sure why it's hanging... :/ hoping ramjet can elaborate on why it hanging on downloading boot.img
 
ramjet73 said:
Don't forget to relock after successfully flashing the setmainverlow.zip and before flashing the RUU. ;)

Edit: It doesn't look like the "fastboot boot recovery.img" took. It might help to remove/replace the battery, start the bootloader and try it again.

ramjet73
Click to expand...

Yes we definitely won't. But I don't think he has flashed the SetMainVersionLOW zip yet as it go stuck trying to boot recovery
 
Brian706 said:
Yes we definitely won't. But I don't think he has flashed the SetMainVersionLOW zip yet as it go stuck trying to boot recovery
Click to expand...
See the edits to my last post. If he didn't respond to the prompt he may not actually be unlocked.

ramjet73
 
You must log in or register to reply here.
Back
Top Bottom