Develop Bugs

Most likely bricked EVO 4g

I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)

The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.

http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.

LaloHigh said:
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
Click to expand...
Click to collapse
What do you mean record what software I started with? I had 2.02, now have 0.76 (But my screen says 2.10). I've tried both the exe and the PC36IMG.zip that you've linked.
Using .exe gives me a Error 170 (Not recognizing my phone is plugged in)
Putting PC36IMG.zip on sd and using hboot gives me Failed-PU, Partition Update Fail! for every category but Radio_V2. BTW I'm supposed to use the first two files from that link
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36*****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04

Greenfieldan said:
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
Click to expand...
Click to collapse
Well what I did was messup the way it sees my partition. I have a nwer partition scheme i believe but the 0.76 software thinks I have the older partition settup.
If you mean unroot method from this post http://forum.xda-developers.com/showthread.php?t=829045 the one I rooted with then I can't do it cause I have no recovery. I can't get to it cause bad partition settup.

I know I can run fastboot erase commands, do you guys think I should run
Code:
fastboot erase boot
to create an unbootable system. One that doesn't even have the screen turn on?
*Which if any partition can I delete in order to never have the phone even turn the screen on?
Here's the choices (wimax, misc, recovery, boot, system, cache, userdata)

if your getting error 170, the RUU can't communicate with the phone.\
Can you get Hboot USb on? IF so, the RUU may run with it.
Drivers installed on computer?
Otherwise, you mave have blown out USB port, like I did.
Try putting the RUU, rom.zip (rename rom.zip to PC36IMG.zip) to your sd card, and see if that saves your a$$.
If that don't work, better run it over with a car or something and take it back.

The good news is you are still in your 30 day warranty. The solution I would suggest is try to flash the bootloader back to hboot 2.10. I would find a pc36 with 2.10 and flash away. Maybe even fastboot erase every partition except boot and hboot first. Don't do radio or wimax either or it will brick your radio and wimax. Then flash a full pc36. Other than that, manually brick. I would erase hboot and boot to brick.
Good luck

If you erase boot.img, it will still go to hboot. Erase the touchpanel image. That way they cant see it. By the time your phone gets to its repair destination, "they" wont be looking for that type of thing. They will just repartition. Also, it wont let you erase hboot

What error are you seeing when you select recovery from the bootloader menu?
The RUU that you tried, what version was it? You MUST use the 3.70.651.1 RUU because your phone thinks you are on hboot 2.10. Do not try an older RUU.
--------------------------------
Try the following
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
4) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
-----------------------------------------------
If that does not work then try the following:
1) Download the img file for the modified Amon_Ra Recovery
2) Put evo-test.img on the root of your sdcard
3) Put the phone in fastboot mode
4) fastboot boot evo-test.img
5) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1

Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks

josh4trunks said:
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
Click to expand...
Click to collapse
But if you can't flash a RUU.exe, then you can probably flash a zip file of a ROM.
This can or be or is not correct, I am just curious how this well happened to you.

nope tried flashing ROM through hboot, fastboot... Tried 'fastboot erase boot' didn't do anything. I'm gonna update the OP on the current situation, giving up...

Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.

i think he said multiple times that he was totally screwed and his partitions were messed up so he either needs a total memory reflash or god's private java code

illogos said:
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
Click to expand...
Click to collapse
Can't flash through bootloader. Get Fail-PU
Which is a Partition Update Error

[Q] Recovery missing ?

I am totally new to custom Rom's so please be kind!
I purchased a used Desire with Cyanogenmod-7.0.3 already in place. I wanted to use the ROM manager to install the new version, so i took the option to 'Flash Clockworkmod recovery 2.5.0.7' from ROM manager.
From ROM manager again it did a Backup of current ROM.. When i try view the 'Manage and restore backups' i can see nothing.
If i try access recovery from ROM manager, i get phone image with question mark and it reboots straight away.
If i use manual method using volume down - power and select 'recovery', i get screen with phone and exclamation mark? It have to select 'volume up' and power to reboot ok.(Android System recovery menu 2e) There is also a warning in yellow 'E:Cant open /cache/recovery/command'
Is this the recovery menu for me ? I noticed there is an option to ' Apply Sd card:update.zip' but no back up option
Everything works ok at the moment, so i am reluctant to flash the update from ROM manager as i suspect the Clockworkmod recovery is either not accessible or missing??
Details of phone are:
Bravo Unknown Ship S-ON
HBOOT- 0.75.0000
MI Crop-031d
Touch Panel--Synt0101
Radio-5.17.05.23
Mar 5 2010,21;12:15
Current software details are:
Cyanogen Mod 7.0.3
Baseband version 32.56.00.32U_5.17.05.23
Kernel version 2.6.37.4-cyanogenmod-82245-g7f230e8
Some help would be appreciated. I've tried searching but find the various responses a little confusing.
Also, i realise that modding may be more than i need/want. Is it easy enough to restore back to Stock (was T-Mobile originally)
All I want a nice stable daily use phone.
Thanks in advance for replies.

All you need to do is flash a new recovery since yours is non-existent or ill-functioning.
The best way of flashing recovery is through fastboot. In order for this to work your device needs to be S-OFF. You can do this by using the new Alpharev/Unrevoked tool.
Once you have S-OFF, you can use fastboot commander, to flash the recovery.
If you get into any trouble or need any further help just holla
EDIT: Sorry that won't work, I just noticed that you HBOOT Version is really old. You'd have to run a RUU to update it.. but for an inexperienced user I'd leave it for now, unless you really want to - PM me if you want help with it.

That's fantastic. I'll have a try this evening. Thanks

because your hboot is too old for revolutionary to work:
create a goldcard (THIS WILL FORMAT YOUR SDCARD), then put the attatched PB99IMG.zip in the root of your sd-card, and boot into Bootloader (power off, then hold volume down & power), it will prompt you if you'd like to update, press volume up, and it should go.
This *should* work, I tried it and it did.. might give it a go again to confirm it 100% lol.
If it doesn't work for some reason because you're S-ON, although it should since this is an official HTC Hboot (if it doesn't work because of a CID error, your goldcard doesn't work, and you need to try the goldcard process again just in case [some SD-cards don't work as a goldcard]) then you will need to run a RUU, either the correct one for your phone, or the latest WWE RUU (if your goldcard works)
Once you've done that just follow the process I posted above

booting loop

My htc evo all of the sudden it doesnt want to start it just staying on the htc white screen and then vibrates and it restarts itself I tried installing a ruu rom and sitll the same, tried to install a recovery app and it wont take it I get a message saying that the image is invalid. Plz someone help me I havent slep and been looking and looking and I havent found something that can help me with my problem
Heres some info from the Hboot screen
Supersonic EVT2-3 Ship S-on
Hboot-2.16.0001
Microp-041f
Touch Panel-Atmelc03_16ac
Radio-2.15.00.0808
any ideas will help

Same prob
Have you had any luck? I'm in the same boat, I've tried just about everything... I sold my phone to someone and they tried installing muiu rom and it quit working for them and they sent it back to me... And now I just want to get it working so I can use it and sell my iPhone and get a new android!! I hate the iPhone.

What exactly were you trying to achieve switching RUU's?
did you make sure it was for phones that were not rooted?

I havent had any luck and well I tried the Ruu that it wasnt rooted and it went all the way but the same thing keeps on happening

I am having this issue as well, about 12 hours after switching roms to cm9 nightly (unofficial) from the roms section, everything was working just fine, all was well. I had spent some time getting the rom set back up the way i like it, and had finished, while waiting in line at a restaurant I opened a bookmark from ics browser plus app and the phone rebooted itself. it just loops through the white screen, goes black, and then back to the white screen. I can get to hboot, but not to recovery, selecting recovery just goes back to the loop. I tried clearing user data via hboot, I tried reinstalling recovery (both amon-ra and twrp). the recovery installs ok according to the screen, but then trying to go back to recovery causes the loop to return. I do not know what else to try. (in my case, the phone does still show s-off and always has throughout the problems)
Any ideas or help would be greatly appreciated.....

is there a way to try and flash a rom thru ABD since im not able to go into recovery and i have S ON??? but my bootloader is unlocked already

areskorn said:
is there a way to try and flash a rom thru ABD since im not able to go into recovery and i have S ON??? but my bootloader is unlocked already
Click to expand...
Click to collapse
You're gona ned to get to s-off sot hat adb and mount the system if needed. Since you have the 2.16 bootloader, head over to revolutionary.io to get to rooting tools.

UPDATE
After trying different things now my HBOOT says 2.18.0001
Radio 2.15.00.12.19 and at the top it says unlocked, how can I S-off if i cant go inside the phone?

Now you're S-Off, flash a recovery and see if you can into Recovery and flash a ROM.
BTW, what ROM were you using when this started?

areskorn said:
UPDATE
After trying different things now my HBOOT says 2.18.0001
Radio 2.15.00.12.19 and at the top it says unlocked, how can I S-off if i cant go inside the phone?
Click to expand...
Click to collapse
If the top of the screen says S-Off, stop right there. Go to the dev section > download and flash a recovrey via PC36IMG.zip > then flash a rom.

for S+G's try pulling battery and removing sd card before rebooting without it

sorry but I havent had time to get online but now it says
S-ON
HBOOT-2.18.0001
MICROP-041f
RADIO-2.15.00.12.19
Dec 21 2011,
I still cant get the s-off tried different times, the recovery still doesnt work i try to select recovery sometimes it stays on a black screen sometmes it just starts rebooting itself

I tried installing a recovery thru fastboot and it says that it was finished and everything but when I select recovery it stays on the htc evo 4g white screen and it doesnt do anything after that

try to get S-Off useing revolutionary, once you get it ,Get smelkus-mod-4.3 recovery. Flash it through H-Boot, If you can get it to flash then your good to go. Just a note, Twerp is a badass recovery but twerp anc CWM dont really play well with the Evo 4g,,,Later,,,

areskorn said:
I tried installing a recovery thru fastboot and it says that it was finished and everything but when I select recovery it stays on the htc evo 4g white screen and it doesnt do anything after that
Click to expand...
Click to collapse
Try flashing it through the bootloader using the file attached here.

I tried flashing the image and it did detect it, but it wont go into it after I select recovery it restarts once by itself then goes into a black screen and I cant see anything there

i appreciate all the help that has been provided to me, has anyone else been thru the same thing if so what is the fix to this nightmare

areskorn said:
I tried flashing the image and it did detect it, but it wont go into it after I select recovery it restarts once by itself then goes into a black screen and I cant see anything there
Click to expand...
Click to collapse
So it detected it, but did you actually tell it to flash?

This happened to me after a dead battery. I was worried but a Phillip charge and then it booted up
Sent from my PC36100 using xda premium

It did flash it and everything but when I select recovery it restarts itself over and over again

[Q] Stuck on cyanogenmod boot loop and no clockwork recovery...

Ok so here's the deal I have been working on this STUPID Incredible for a buddy of mine for like the last 4 hours trying to fix his boot loop issue. I have scoured the internet looking for a way to fix this problem and downloaded countless *.img and *.zip files and who knows what else...
[EDIT] Also if I reboot to bootloader (either through adb fastboot or through the phone (VOL (-) + POWER) adb can't find the phone I can only access the phone when it's actually trying to boot up
[THE ISSUE]​
The phone boots up shows the white htc incredible screen than proceeds to boot into cyanogenmod 7.blah.blah.blah (don't know the exact version it's from a couple months ago) and than just continuously shows the skateboard dude and doesn't proceed past that point.
When I reboot the phone and load up the bootloader it runs fine and than when I try to do the recovery option it will vibrate for a second show the htc incredible screen and than show the fastboot usb options (bootloader, reboot, reboot bootloader, power down) and if I select reboot it just reboots to the same problem.
If I choose Factory Reset it goes to the fastboot usb menu but I can't choose any of the options and it just sits there, I actually have to do a battery pull in order to do anything.
I know that clockword mod was installed on this phone but I can't access it by any means.
I hooked the phone up to my computer and loaded up adb (which is installed correctly as I've used it on my phone and the htc drivers are installed correctly) if I try to access my internal sd card through an adb shell it doesn't list anything and I have root in the shell (#) and if I try to cd to sd-ext it says "can't cd to sd-ext) so I can put something on the cards and load them up (as far as I know) to get the recovery working or anything...
adb does see the phone sees the files on the phone I can do a adb reboot it and that works fine.
Here's some info from the bootloader:
incrediblec xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.15.00.07.28
Jul 23 2010, 18:06:51
Ok so that got longer than I thought it would be (whoops) I hope I explained this well enough for everyone and didn't make it to confusing. I don't care if I have to go back to stock or what I just need to get this phone up and running again...
Thanks for reading this horribly long thread and for any feedback you have!

Sounds like something is borked with your install, and your recovery has vamooshed. Yes, those are the technical terms for it. Try an RUU.
http://pvillecomp.com/?page_id=22
That will give you stock everything, including recovery, you just have to flash CWM, then in CWM wipe everything (wipe data/factory reset, wipe boot, wipe system), then flash a ROM.

Edit: try Pons' method first.
First, the phone isn't stupid...it's Incredible. I mean seriously /s
Can you reformat the sd card, download CWM to the root of your sd card, then install CWM through hboot that way?
CWM is available from pvillecomp.com, download the file under the heading "Recoveries" and rename it to: PB31IMG.zip
Couple questions:
What started the bootloop issue? What steps have you taken to try resolving this issue?

G33kman said:
Ok so here's the deal I have been working on this STUPID Incredible for a buddy of mine for like the last 4 hours trying to fix his boot loop issue. I have scoured the internet looking for a way to fix this problem and downloaded countless *.img and *.zip files and who knows what else...
[EDIT] Also if I reboot to bootloader (either through adb fastboot or through the phone (VOL (-) + POWER) adb can't find the phone I can only access the phone when it's actually trying to boot up
[THE ISSUE]​
The phone boots up shows the white htc incredible screen than proceeds to boot into cyanogenmod 7.blah.blah.blah (don't know the exact version it's from a couple months ago) and than just continuously shows the skateboard dude and doesn't proceed past that point.
When I reboot the phone and load up the bootloader it runs fine and than when I try to do the recovery option it will vibrate for a second show the htc incredible screen and than show the fastboot usb options (bootloader, reboot, reboot bootloader, power down) and if I select reboot it just reboots to the same problem.
If I choose Factory Reset it goes to the fastboot usb menu but I can't choose any of the options and it just sits there, I actually have to do a battery pull in order to do anything.
I know that clockword mod was installed on this phone but I can't access it by any means.
I hooked the phone up to my computer and loaded up adb (which is installed correctly as I've used it on my phone and the htc drivers are installed correctly) if I try to access my internal sd card through an adb shell it doesn't list anything and I have root in the shell (#) and if I try to cd to sd-ext it says "can't cd to sd-ext) so I can put something on the cards and load them up (as far as I know) to get the recovery working or anything...
adb does see the phone sees the files on the phone I can do a adb reboot it and that works fine.
Here's some info from the bootloader:
incrediblec xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.15.00.07.28
Jul 23 2010, 18:06:51
Ok so that got longer than I thought it would be (whoops) I hope I explained this well enough for everyone and didn't make it to confusing. I don't care if I have to go back to stock or what I just need to get this phone up and running again...
Thanks for reading this horribly long thread and for any feedback you have!
Click to expand...
Click to collapse
Have you tried to reflash cwm recovery thru hboot? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip Then ser if you can access it. If you can wipe everything and flash a rom of your choosing. If that dosent work try an ruu thru hboot. http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip

WIN!
cmlusco said:
Have you tried to reflash cwm recovery thru hboot? Then ser if you can access it. If you can wipe everything and flash a rom of your choosing. If that dosent work try an ruu thru hboot.
Click to expand...
Click to collapse
Oh man thanks guys for the feedback I thought it would be something easy enough. I officially have cwm recovery working and am currently install cyanogenmod 9 as we speak! You guys are lifesavers seriously thank you!

CWM Boot Loop - Unable to access via Odin/ADB
I have the boot loader problem too... Last night, for no apparent reason, my phone turned off and didn't want to come back on again. I didn't change anything, plug it into anything, or do anything fancy, it just turned itself off and now it's stuck in a boot loop.
It boots into download mode okay, but I can't get it into recovery.

Win here too!
i bricked my phone running cm7 also and had the exact same problems right down to the T. ...SO!, that program that i installed on my computer took complete control of the phone and reset the rom. this is a wonderful piece of software. if you have an incredible download this program and dont worry about bricking your phone again.

how to obtain s-on now?
After I used the program from the website in the previous post, it brought me back to stock Rom and everything. Now it's still s-off, but I can't get into cwm, just hboot. My main goal is just to get this back to stock (unrooted and s-on). Can someone please explain how I go about doing this? I can get.any info needed ie. Radio etc.
Problem right now is in order to get into the phone I have to do the entire setup which includes activating it,which I cannot do.
Thank you guys much for this useful info.

brandonb0013 said:
After I used the program from the website in the previous post, it brought me back to stock Rom and everything. Now it's still s-off, but I can't get into cwm, just hboot. My main goal is just to get this back to stock (unrooted and s-on). Can someone please explain how I go about doing this? I can get.any info needed ie. Radio etc.
Problem right now is in order to get into the phone I have to do the entire setup which includes activating it,which I cannot do.
Thank you guys much for this useful info.
Click to expand...
Click to collapse
Why do you want it unrooted and s-on? All you need to do is flash cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot. From there you can flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip and be rooted if so desired. If you really want s-on and stock you need to flash cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, flash the 2.15.00.07.28 radio http://dinc.does-it.net/Radios/2.15.00.07.28/PB31IMG.zip thru hboot, and then flash the unrevoked s-on patch http://dinc.does-it.net/Unrevoked/unrevoked-forever-son.zip thru recovery. Once s-on flash a official ruu http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip thru hboot and you will be stock s-on. Also if you want to bypass the activation just cancel it 3 or 4 times and it will let you skip it.

cmlusco said:
Also if you want to bypass the activation just cancel it 3 or 4 times and it will let you skip it.
Click to expand...
Click to collapse
Tapping each corner going clockwise, starting in the top left, is an easier way to skip the setup.

thanks
Thanks guys. I ended up calling customer service and they got me past the activate screen. From there I re rooted the phone so I could use cwm recovery again and flash s-on then unrooted it and all is good now. Thanks

[SOLVED] Bootloop with no access to recovery (S-OFF)

SOLVED. THE PHONE IS BROKEN AKA HARDWARE FAILURE
Hi,
My old Desire had been sitting in my desk for about a year since i bought myself a Galaxy S2. Today, I decided to try it out. Charged the battery first and then tried to boot it. Well, I got stuck in the splash screen. The phone had been working normally the last time i used it (maybe 6 months ago?) so i thought it was weird. Then I tried to boot it into recovery, and got again stuck in the splash screen. HBOOT came up normally but after pressing the recovery button the phone just made the boot vibration multiple times and then was stuck in the splash screen.
What I have:
- Alpharev S-OFF HBOOT: bravo_alphaspl-oxygenr2.img
- Oxygen rom (don't remember the version but i have the zip on my computer): update-oxygen-2.1.6-signed.zip
- My current HBOOT screen shows the following:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
- AFAIK the phone is the older AMOLED version (if that matters)
- I have a working ADB
- I dont have a goldcard
What I did after noticing the problem:
1. Read the sticky which told me to reflash my recovery.
2. Flashed the CWM 2.5.0.7 recovery via Android flasher. The program said it was successful but my phone was in a bootloop again without access to recovery.
3. Flashed the Amon Ra recovery via Android flasher. The program again said it was successful but the bootloop persisted.
4. Flashed both of the recoveries (one at time of course) via the adb fastboot command. Again, it was supposed to be successful, but the phone STILL was in the bootloop.
I thought the sticky explained my situation perfectly but apparently this is not the case
I have also a RUU lying around:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
But I was hesitant to use it as I have the custom Alpharev HBOOT which might cause problems.
So what should I do now? I appreciate all advice.

Re: Bootloop with no access to recovery (S-OFF)
In my sig you'll find a thread with how to install 4ext recovery through pb99img. Check it out.

I DL'd the PB99IMG.zip file for the recovery and put it on my SD by moving the SD to my other phone and connecting it to my PC.
However, when the HBOOT searches for the PB99IMG.zip, it only says "No Image!".

Re: Bootloop with no access to recovery (S-OFF)
Are you sure you didn't put it in any folder?
Then, again in my sig, you'll find a partitioning guide. The first part of the guide will help you install a recovery. Try it.

Yes, I put it right in the root of the sd card.
The partitioning thread in your sig has a few methods of installing the recovery. But i have already tried them and for some reason they fail. I have now tried the Android flasher method, the ADB + Fastboot method and the PB99IMG.zip method. I have no clue why these should fail like i have described.
EDIT: Looks like I cannot run the RUU either. It says it failed to detect the device. What on earth could be going on when EVERY possible way of reinstalling the recovery fails? I was starting to think that maybe there was something wrong with my USB connection/drivers or ADB so I made a test and flashed another alpharev HBOOT (their bravo stock one: bravo_alphaspl.img) and the flashing procedure worked. So at least my ADB is working. Still no idea why the PB99IMG.zip just won't work... looks like my phone defies all these guides available here.

Update:
I downloaded the 2.3 GB RUU from the sticky topic. Suprisingly enough I could run it, it detected my device and went throught the whole RUU process without a single error. I booted the phone - and was again stuck in a bootloop. Went to HBOOT, chose recovery (the RUU should have flashed the stock recovery) but no, I could not get into the recovery. Instead the phone was again stuck in a bootloop. So I still cannot get into the recovery. The only thing that changed was the splash screen I was stuck on... (I had a custom splash, now it's the stock one)
I then formatted my SD, put the 4ext recovery PB99IMG.zip there and booted into HBOOT. This time It found the PB99IMG.zip. It asked if I wanted to update, I pressed yes and it went through it without any error. When it asked if i wanted to reboot, i pressed no, navigated into recovery and pressed the power button. This should have taken me to the 4ext recovery i just flashed successfully. And guess what? Bootloop again...
So after all this, I still do not have access to the recovery. I just get the bootloop every time. I've whacked around with android phones (mostly Galaxy S2 though) quite a lot but this far have never seen such a persistent problem which just evades all (for other people) working attempts to fix it. The procedures work exactly as described and give me no errors, but in the end the issue still persists: I cannot access the recovery because of the bootloop.
I was starting to wonder if it could be hardware failure causing this? Just a wild guess but the phone has been sitting in my desk for almost a year... I didn't change anything in the software. The only thing that comes to my mind is that the memory where the recovery and rom are stored is somehow corrupt. This would explain why I cannot get into the recovery even though i have reflashed it successfully multiple times. I also can change my HBOOT and splash screen.
Does anyone have any ideas left?

Re: Bootloop with no access to recovery (S-OFF)
Are you s-on now?

Yep,
At the moment i'm S-ON with the 2.3 RUU from your sig. Bootloader is 1.02.0001. I flashed the RUU from the PB99IMG. No errors. Still cannot get to recovery.
I then opened the phone and removed the mainboard but i could not see any damage at all. No burns, marks of water damage etc.

Re: Bootloop with no access to recovery (S-OFF)
As weird as it sounds, try putting the phone in the freezer without the battery for 10 minutes, then try to boot.

You are pretty good, man.
CASE CLOSED
Explanation: after putting the phone into the freezer for some time, I tried to boot. It booted normally to the ROM. Wifi worked, I could use internet, setup my settings etc. After 10 minutes the phone rebooted into a bootloop. This proves that the problem always was a hardware one, and this is why any software fixes couldn't solve the issue. Because i don't have a freezer in my pocket I can safely say the phone is broken and I can throw it away.
Thank you!