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

Root Stuck in boot-up screen.

kloroformkandi said:
Also, since we are doing this step by step, I have been powering down my phone so the battery stays charged.
Do I need to be starting from the very first step in doing so?
Click to expand...

I missed this part. I'll keep that in mind as we go forward. I have generally been assuming that you were powering down, though, (I think...)
 
kloroformkandi said:
When I copy the Token into the text and click submit, it gives me 404 error.
Click to expand...

ive had that happen once or twice. the site is prolly just having some prollems,unless your internet has coincidently just crashed :eek:

if you paste your unlock token onto a text document,or somewhere you can copy it again later,you can pick back up at that step when the site is working.

sounds like your moving right along. doogald is doing a great job with the instructions but ill keep watching in case he becomes busy with his family activities so hopefully youll have as little down time as possible :)
 
kloroformkandi said:
My command window is telling me 'waiting for device' after typing to unlock it.
Do I have to redo any of these steps if I powered down?
Click to expand...

No on redo-ing steps - you have fastboot that works, you have the 1.51.0000 bootloader - these do not go away.

Since I have never unlocked the bootloader on the 1.51.0000 method, I'm actually going to do so now, just so I know the steps, etc.
 
kloroformkandi said:
My command window is telling me 'waiting for device' after typing to unlock it.
Do I have to redo any of these steps if I powered down?
Click to expand...

powering down shouldnt have any affect on the steps youve allready done. since you had everything working to get the identifier token,well assume its not a driver issue.

-try a reboot of the PC
-try different ports and usb cables
-make sure your phone is in "fastboot" mode and not hboot
-uninstall or stop htc sync,pda net,or any other program capable of comunicating with your phone.

hopefully one of those will get you recognized again :)
 
kloroformkandi said:
My command window is telling me 'waiting for device' after typing to unlock it.
Do I have to redo any of these steps if I powered down?
Click to expand...

doogald said:
No on redo-ing steps - you have fastboot that works, you have the 1.51.0000 bootloader - these do not go away.

Since I have never unlocked the bootloader on the 1.51.0000 method, I'm actually going to do so now, just so I know the steps, etc.
Click to expand...

Ok, I just went through the process. (A bit of a pain on the Mac, as it turns out - you cannot copy a rectangular block of text as you can in the Windows CMD window - unless I am missing something - so I had to cut and paste into textedit, search and replace "INFO" with nothing, and then paste that back into the token window on the HTCDev web site.) Anyway, I now have an unlocked 1.51.0000 bootloader.

When you successfully unlock it will restart the phone as if it was trying to start the phone normally, so, since you don't have a working system, you will probably still see the skating Droids. You can just pull battery at that point.


scotty85 said:
powering down shouldnt have any affect on the steps youve allready done. since you had everything working to get the identifier token,well assume its not a driver issue.

-try a reboot of the PC
-try different ports and usb cables
-make sure your phone is in "fastboot" mode and not hboot
-uninstall or stop htc sync,pda net,or any other program capable of comunicating with your phone.

hopefully one of those will get you recognized again :)
Click to expand...

It may be this - in order for the fastboot flash unlocktoken Unlock_code.bin command to work, you need the phone to be in fastboot mode again. So, start the phone in HBOOT by holding VolDn when you start the phone, then press "Send" when prompted to enter fastboot. You should see "FASTBOOT USB" in red if you have the cable connected. It won't hurt to run

fastboot devices

to make sure that the computer sees the phone from the CMD window. (That's what I did before I ran fastboot flash unlocktoken Unlock_code.bin). When you do finally run the command to unlock the bootloader, it will change to a graphical display - you can press VolUp to answer that, yes, you want to unlock the bootloader, then power to confirm. (Your phone will almost immediately restart, as I described above.)

After you pull battery and replace it, you can start to HBOOT again (hold VolDn). It should say "*** UNLOCKED ***" with a pink background at the very top. If that's all set, we are ready for the next step.
 
Ok, the next couple of steps say:

- create a zip file with a custom recovery image in it (named "recovery.img"), and an "android-info.txt" file with MainVer set to 2.42.0000 (see step #3 of this XDA post).

- using fastboot and the phone in RUU mode, flash this zip file ("fastboot flash zip zipfilename.zip") Again, see step #3 of the link above.
Click to expand...

So, to make this easier, and flesh it out a bit:

[update: do not do this step!]- download this file PB00IMG-rescue-recovery.zip


[update: do this instead] - download the attached file recovery.zip

Copy that file into your c:\android folder

Then, you are going to run a few commands that you have run before:

- start the phone in HBOOT and put it in fastboot mode, with the phone cabled to the PC (I trust that this is old hat by now).

- back at the CMD prompt, run these commands (you have done one of these before):

fastboot oem rebootRUU

fastboot flash zip PB00IMG-rescue-recovery.zip

fastboot flash zip recovery.zip

fastboot reboot

Pull the battery and then restart the phone by holding VolUp.

This should look much like this:

Code: 
C:\android>fastboot devices
HTblahblah    fastboot

C:\Android>fastboot oem rebootRUU
...
OKAY [  0.024s]
finished. total time: 0.025s


c:\Android>fastboot flash zip recovery.zip
       sending 'zip' (2523 KB)... OKAY [  0.592s]
                 writing 'zip'... INFOzip header checking
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,42
INFO[RUU]UZ,boot,94
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,40
INFO[RUU]WP,boot,80
INFO[RUU]WP,boot,100
OKAY [  2.738s]
finished. total time: 3.331s

c:\Android>fastboot reboot
                     rebooting...
finished. total time: 0.024s

c:\Android>

This should reboot the phone to a different looking screen, with green text on a black background, which looks like this:


13309d1289352290-amon_ra-1-6-2-custom-recovery-trackball-not-required-recovery-ra-eris-v1.6.2-trackball-not-required.jpg
 

Attachments

Excellent. You are doing great.

The next step is

- power off the phone and boot into the custom recovery and flash the ErisMiscReset_v0.9.zip file (watch for any errors - stop if you see errors!).
Click to expand...

You are already in recovery, so you don't need to power off.

What you are going to do is (with the phone still cabled to the PC) go down to the USB-MS Toggle and press the trackball. This will connect your SD card as a drive letter on your PC.

Drag the following files that you downloaded earlier to the SD card:

ErisMiscReset_v0.9.zip
MTD_Inspect_v0.9.zip
ErisMTDNuke_v0.9.zip

When those files are copied over (which should not take too long), disconnect the drive safely from the taskbar notification on your Windows PC and then press the trackball on the phone to return to the menu.

Then go to "Flash zip from sdcard" and press the trackball.

Go down to ErisMiscReset_v0.9.zip and press the trackball.
Press the trackball to confirm.

There will be a series of messages:

Code: 
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying files...
Deleting files...

Report back if there are any error messages.
 
I believe that error is simply the battery needs charged.

Failing that, you may need to transfer the files via a card reader mounted in the pc.

Try and charge or change the battery. You do not want it to die mid flash with one of those files :eek:
 
kloroformkandi said:
On my phone, right after selecting USB-MS Toggle
Click to expand...

scotty85 said:
I believe that error is simply the battery needs charged.

Failing that, you may need to transfer the files via a card reader mounted in the pc.

Try and charge or change the battery. You do not want it to die mid flash with one of those files :eek:
Click to expand...

No, that's not it. I should have tested this sooner - I made a mistake. There is a better way, I think.

Let's try this: download the attached file recovery.zip (in the next post - sorry!)

Copy recovery.zip to c:\android if you did not do this already

We will do the same thing that we did a few steps ago:

- restart the phone to HBOOT, with the phone connected to the PC
- (make sure that it still says "Unlocked" at the top - if not, let me know.)
- press Send to start fastboot
- fastboot oem rebootRUU
- fastboot flash zip recovery.zip
- (notice that last step is a little shorter - just recovery.zip)
- (also, report if there is an error message)
- fastboot reboot

This should start the Amon_RA recovery again. We are still not there

- pull battery
- restart the phone holding VolUp
- (if you did that last step holding VolDn and started HBOOT, no worries - there should be a prompt to press VolUp to start Recovery. Go ahead and do that.)

Now USB-MS toggle should work. Proceed with the step to copy ErisMiscReset_v0.9.zip, MTD_Inspect_v0.9.zip, and ErisMTDNuke_v0.9.zip, and then flash ErisMiscReset_v0.9.zip, from a few posts ago.

(Note: in my experience, this ended up re-locking the bootloader. That's not a big deal - it will just save a step later.)

Again, report any error messages.
 
Okay I ended up having to use a card reader.
I just drag it onto the SD card, not in any particular folder, correct?

Oh wait I just saw your last post. [I haven't dragged anything in yet]
 
You must log in or register to reply here.
Back
Top Bottom