gbonato

My problem is similar, but different: when I boot into recovery I simply cannot go past the initial white screen with HTC logo. My phone gets freezed there and I have to remove batery to boot it normally.

gbonato

I am stuck with my HTC Hero and I need help to find my way out of the maze.

I was having trouble with my RCMix v2.2 WWE instalation, as I described here. I decided to flash a new ROM.

What I did:

I tried to boot into recovery but it didn't work. I believe recovery was damaged. I went to installed Rom Manager and tried to reinstall RA Recovery. When it was rebooting, phone got stuck in the first white screen.

Now that's where I am stuck:

Even though I try all the rebooting shortcuts, it doesn't load regular ROM and doesn't load recovery. It keeps showing the white screen with HTC logo and "quietly brilliant" slogan. And it starts it over and over.

If I try to go into recovery with power+home button it freezes in HTC logo on white screen, without looping and without showing "quietly brilliant" slogan.

My two options were:

1) Flash a recovery using ADB (files offered by Slug in post #6). It didn't work. I think that's because phone doesn't really goes to the point where the desktop software can reach it through debug mode. Doesn't know where to go from here. I go to Windows CMD line, in ADB folder and try to run "adb shelll". It shows me "Error: device not found".

2) Install a stock/shipped ROM downloaded from here. My hope was to start from a shipper rom and go from there all the way to rooting and flashing a custom ROM. The installation of a shipped ROM worked until the point where it checks the ID. Since I don't have a goldkey (and there is not way I can create one) it doesn't allow me to finish shipped ROM instalation. Is there an universal shipped ROM file which doesn't demand a specific ID or goldkey?

So... What do I do? Any one can give me a clue?

Thanks!

Xyro

Forgive me if I'm stating the obvious, but have you pulled the battery out for a good 30 seconds before trying to boot into recovery?

I ask because you said it's starting over and over, which I'm interpreting as it seems to be rebooting on it's own. If that's the case, then it's not really shutting down completely and that would explain why holding power + home, or power + back (for the bootloader) doesn't work.

__________________

gbonato

Thanks Xyro for your quick reply.

I had left battery out for more than 30 seconds, but since I'm running out of options, it tried it again.

When I turn phone on regularly, it keeps looping into white screen with logo and slogan.

When I press power + home for recovery, it shows me the same: freezes in the white screen with logo (no loop).

When I press power + back button for bootloader it takes me the Fastboot/Hboot screen. But... What can I do from there?

Xyro

You should be able to connect via ADB whilst using fastboot.

Here are the installation instructions for the amon ra recovery image using that method. (The first step is redundant in your case).

If I recall correctly, that will allow you to boot from the recovery.img file on your PC, rather than the possibly corrupt version on your phone. Then you can re-flash it from there.

Last edited by Xyro; January 29th, 2012 at 12:14 AM.

gbonato

Well, here I am trying to boot RA recovery using ADB + Fastboot as described in XDA post mentioned by Xyro.

The problem is that aparently the phone is not being recognized by ADB. The Windows sounds give me a clue that phone is connected, but when I type "ADB shell" it tells me there are no devices attached.

Fastboot seems to recognize the phone, though. But it still doesn't go through:



What am I doing wrong?

Last edited by gbonato; January 29th, 2012 at 01:14 AM.

Xyro

Does running 'adb remount' first help?

If that doesn't work, do you know your ADB set up is all working? Especially if you've not used it before, windows may have loaded the wrong drivers for you. This guide ought to ensure that you've got the right ones.

gbonato

Xyro, I've tested everything and all the drivers seem to be running correctly.

I've tried "ADB remount" but it still returns the message "Error: device not found".

I've tried all possible commands using Fastboot, but all I get is an error message saying "Remote: not allow".

What can I do?





As you can see from the pictures above, recovery.img is there and everything seems to be working properly, except for the phone which is apparently locked for flashing a new recovery.

(I have tried to erase recovery but it didn't work either)

Xyro

That's unfortunate. You can see in the image you took that your phone is 'S-On'. That, along with the 'remote: not allow' error means it's unlikely we're going to be able to get adb to work in fastboot.

It looks like getting an RUU to work is the only option here. What error + error code, specifically, do you get when you run the RUU? Do you know what version of the official firmware you were using?

gbonato

Let me tell you good and unforseen news. My phone is back to work.

I don't know what happened. I believe I tried to boot it so many times that it decided to break the loop of the initial white screen.

I won't try to discover what happened, but I've learned the lesson: I will create my goldkey and be prepared to install an original RUU in case things go wrong. If I had the goldkey ready from the beginnig, I would have so many problems.

Thanks Xyro once more for all your ideas.

Xyro

Good to hear

yoniroit

Thank you thank you very much!
Removing install-recovery.sh did the magic

BTW, you wanted to know the content:

Sykeo

this worked for me after repeatedly beating my head against the adb approch

now im rockin a pretty quick villainrom v13