Develop Bugs

[Q] Desire stuck in bootloader loop after hboot downgrade - HELP!!

I have serious problems with my phone that I could really use some help with as at the moment I'm completely screwed - I've already spent hours reading forums but have yet to find advice that will help. Here's whats happened:
I have an A8181 HTC Desire, and I took an OTA update yesterday that bricked my wifi. At this point I thought it would be easiest to root my phone, and after checking that my hboot version was 0.93, I read advice that said to downgrade this to 0.83, which I duly did.
Now, my phone is stuck in a bootloader loop - I get the 3 androids on skatebooards with FASTBOOT in red, and I can choose from:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I select bootloader I then get:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
I can access recovery and apply update.zip roms successfully (I've only tried official HTC 2.2 roms as the phone isnt rooted), but after doing so it just goes back to the bootloader loop.
If I select FASTBOOT then I'm just back at the first screen.
I've tried clearing cache and factory reset aswell, but I still can't get past this 2 screen loop.
It's like the bootloader just can't load whatever rom is installed.
Because the phone isn't booting up, I can't use adb or any other pc tools as the device is not detected on my pc - although it does show up in device manager on windows.
I'm close to sending this back to try a warrantly claim, although I'm worried that by trying to fix this I may have invalidated this.
I'd really appreciate any help or advice as to how I can get out of this and get my stock 2.2 back.
Cheers

If your computer using windows, have you installed hboot drivers?
If you have those installed your pc should detect the phone.
unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

You shouldn't have had to downgrade your bootloader. If you can, go back to the newer.
The wifi issue, was widespread on desires, I had it also after a "pushed" update from HTC (european model, unlocked). I downloaded a stock 2.29 froyo. Had to make a gold card also. Took several tries, wipe cache, but eventually successful.
Then, I rooted, and went to CyanogenMod7 rom with clockwork recovery.

Phone is looping the Evo Splash Screen

I have searched and I can't get this too boot up.
I installed a fresh RUU and it updated it successfully but it still keeps looping.
I can get into HBOOT but not into recovery.
I was rooted running Decks 2.3.4 ROM with the Godmode kernal.
Any help would be appreciated.

deception88 said:
I have searched and I can't get this too boot up.
I installed a fresh RUU and it updated it successfully but it still keeps looping.
I can get into HBOOT but not into recovery.
I was rooted running Decks 2.3.4 ROM with the Godmode kernal.
Any help would be appreciated.
Click to expand...
Click to collapse
Was everything working properly before you tried to run the RUU, or were you already having looping problems? Perhaps try clearing storage from your bootloader menu, then try to boot up again. If that still fails, then I'd try running the RUU again.
Some more info would be great, such as the following:
what RUU version did you flash?
what is your current hboot version?
what is your current radio/baseband version?
That information will determine which RUU you need to run.
If your looping at the splash screen (HTC Evo 4G screen) and NOT the actual boot animation, then it sounds like it could be a problem with your bootloader, possibly.
It does sound like you'll need to try running the RUU again, or running a different RUU.

Thanks for your reply.
Everything was working fine before this happened. I took it off the charger and booted it up and it started to loop.
Hboot is 2.10 and I flashed the latest RUU available from HTC/Sprint

deception88 said:
Thanks for your reply.
Everything was working fine before this happened. I took it off the charger and booted it up and it started to loop.
Hboot is 2.10 and I flashed the latest RUU available from HTC/Sprint
Click to expand...
Click to collapse
So everything was working good, then you decided you were going to unroot? Do you mind if I ask why (out of curiosity).
So basically, you decided to unroot it. You ran the RUU, it completed successfully, you unplugged from your USB cable, turned it on, and the result was looping at the splash. Is that accurate? If so, I would try running the RUU again.
I'd probably even download a new copy of the RUU, just to be sure you don't have a bad download. Then try running it again and see if that makes any difference for you. I'll attatch a link to the RUU i keep in my dropbox.
http://dl.dropbox.com/u/16599118/RU...15.00.11.19_NV_1.90_release_161482_signed.exe
EDIT: I forgot to mention, that in order for you to run the RUU now, you'll most likely need to be in fastboot mode. So, boot to the bootloader, and select 'fastboot usb' from the menu. Once your in fastboot usb mode, try running the RUU. It should detect the phone and run just fine.

I wasn't trying to unroot. I flashed the ruu to see if I could get my phone working again after I saw it was looping the splash screen. I did the fastboot usb the ruu found the phone and flashed the new software and still loops.

Same thing is happening to me. I was on Deck's ROM except I wasn't trying to unroot. I put it on the charge then I noticed the White HTC Splash screen was on and off.
Now it won't get past it. I can get into the loader but not recovery.

deception88 said:
I wasn't trying to unroot. I flashed the ruu to see if I could get my phone working again after I saw it was looping the splash screen. I did the fastboot usb the ruu found the phone and flashed the new software and still loops.
Click to expand...
Click to collapse
Damn man, I'm sorry to hear that. The RUU is pretty much a last resort of restoring your phone back to stock when things go wrong. Since that is failing, there isn't too much else you can do. You can try running a different RUU, but I would most likely expect the same results you've been getting. There was a bunch of people with this same problem a month or two back, and there was never a fix found for it. The name of the thread was "boot looping and no recovery access" or something like that. Author of the thread was something like westibone. I'll see if I can dig it up for you, so you can read through that. There were a ton of suggestions in there. Good luck.

Stuck in non funtioning RUU Froyo with S-ON

Hello. I'm in a bit of a bind which I cannot get myself out of, so I am posting here. I've been around for over a year lingering, updating, trying new things, etc. I came across a free Incredible, which I attempted to root, and install a ROM onto. I rooted the phone with Unrevoked 3, booted into Clockwork mod recovery, made a nandroid, and installed the ROM. The installation was successful, however, on boot after the HTC splash screen the phone vibrates 5 times and the led flashes green constantly. The same thing happened when I tried to boot into recovery.
I found that the phone booted to the Set Up, which crashed, if it was plugged into a computer. I ADB saw the device but I could not push files or execute commands. Unrevoked S-OFF would not work also.
After Googling, I found a 2.2 RUU, which installed successfully, but I get the same boot problems. If the USB is plugged into a computer before the phone is turned on I actually get to Android and can play around. The phone will not recognize any memory, SD or internal; only phone memory is recognized. I tried ADB again with no luck, most likely has to do with the phone not recognizing memory. So I flashed the RUU from HBOOT which flashed fine, but the same problems still persist.
I am out of ideas, which I hope someone has anything I can try.
S-ON
HBOOT 0.92
MICROP-0417
TOUCH PANEL - ATMELC03_16AC
RADIO 2.15.00.07.28
Edit: I tried to be as detailed as possible, so ask any questions if I did not make since.

Check this out
http://pvillecomp.com/?page_id=33

Thank you, trying it now.

cmlusco said:
Check this out
http://pvillecomp.com/?page_id=33
Click to expand...
Click to collapse
I cannot thank you enough.
Edit: Unrevoked gave me s-off. I want to be clear this time before I install any ROM. Do I need to run unrevoked-forever.zip? I am 99.999% positive I do not since I already have s-off. I want to get a new ROM on tonight.

Unrevoked 3 now contains the forever patch, as previous versions did not. So you are good to go flash away, after making a nandroid of course

No need for unrevoked forever if you are s-off

Thanks! On my way to a new ROM.

Desire stuck in fastboot RUU mode

First of all, hello to all forum members!
I had not been particularly active here in the forum,
but I read a lot here and build some knowledge.
so far I have solved all my problems due to browse and read.
But now I am facing a problem, where I need help.
I got a desire from a friend with wrong nexus one blackrose hboot.
I managed to install alpharev hboot on it, but its not booting the rom, neither the recovery.
I decided to get a ruu on it, to reflash boot, system, recovery, etc.
After i did:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <rom.zip>
the phone is stuck in fastboot RUU mode. No matter if I pull the battery and power on with vol-, vol+ or back, the fastboot RUU mode starts (Black screen with htc logo in the middle and 4 exclamation marks in the corners).
What Ive done so far:
Tried different RUUs(Europe, WWE) via fastboot. Most of them fail while writing radio image.
Tried to flash the radio image via fastboot. Most of them stuck while writing.
Asked a friend with exactly matching hardware to send me his working nand backup, his hboot is CM7 r2, so I flashed it
to match his nand backup.
I flashed his boot/recovery/system/cache and the latest radio, matching the nand backup.
The latest radio was flashed successfully.
The recovery in his nand backup was 4EXT Touch 1.0.0.3
So, after flashing boot, recovery, system, cache and even misc and userdata (AND erasing them prior on second try), the behaviour stays the same, the phone wont boot the rom or recovery and no matter what buttons I press on power on, it boots at fastboot RUU mode.
I tried
Code:
fastboot oem boot
, but that keeps stucking in the white htc splash1
If I plug in the usb cable and pull it out again, I see the hboot infos:
AlphaRev CM7 r2
BRAVO PVT1 SHIP S-OFF
HBOOT-6.92.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
<date>
RUU
After a lot of research, Ive found several opinions:
-its a brick (sure it is ;D)
-its a radio brick (ive sucessfully flashed the newest radio, so I doubt it)
Almost all users wo tried it hardly, and havent given up after the second try,
recovered their phone from this fastboot RUU mode.
I can run all fastboot extended commands, and flash RUUs over it.
So: what have I done wrong? Is there anything missing?
Can someone who knows what he says please take a look over it?
Thank you really much
criestr

After "a lot" of research you still haven't looked at my guide, well done.

Sure Ive looked at your guide,
I work with linux, and I hate flashing tools.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
Click to expand...
Click to collapse
Is it any difference to use
Code:
fastboot flash hboot bravo_alphaspl.img
instead of using Android Flasher?
I dont think so, and Ive already done the steps in your guide, except using Android Flasher to flash the AlphaRev stock version.
Or is there another point in your guide that Im missing?
If so, then I am sorry for wasting your time.
I know, I am "new" here, so thats the standard answer for all newbs from you.
Thats ok. But Ive fixed a lot of phones without open even one thread, just with hours of research. But after google search for about 8 hours, several tries and following several guides and tips I didnt find an answer yet.
New update: Ive managed to push and boot the 4EXT Recovery image.

Fair enough, but the guide was meant to be made as easy to use as possible.
All you had to do was flash the stock hboot, or the downgrader, and then try a RUU.
The reason for it being stuck, is because alpharev hboots have write protection (meaning they won't be overwritten until you use the downgrader), and since you had the cm7r2 partition flashed, there was not enough space in /system for the stock ROM.

Hi again,
thanks for your answer.
I had the right stock hboot whilst flashing the RUU, so that wasnt the problem.
The RUU always failed to write the radio. A few hours ago i figured out that
the problem was because of a faulty battery. I changed the battery, loaded it
half an hour, and voila! the RUU was running quite fine.
The stock rom wasnt booting yet, but from then it was possible to go into the HBOOT/Fastboot, so it was making progress ;D
After another research I found out that my misc partition was screwed, maybe because the blackrose hboot, maybe because of the pre-owner.
Fixed the misc partition with cid, kernel commandlines & rom version.
After that I wiped cache and data, and did fastboot oem boot.
The rom was booting, but did random reboots/crashes after about 3-5 mins.
After 3 or 4 reboots the phone is now stuck at htc splash1, and isnt booting anymore.
For now I will try to flash the nand backup again, see if that works out.
Anyone has an better idea?
Thanks alot
criestr

New update:
The phone switched randomly between bootable and non-bootable bootloop/stuck in splash1.
I tried different radios, different boot & system.img from RUUs.
I can flash a new recovery, tried 4 different ones, none of them is booting,
not over hboot->recovery and also not over
Code:
fastboot oem gencheckpt
.
The only thing that worked was to erase cache and immediatly do
Code:
fastboot boot recovery.img
,
so after the stock rom randomly reboots, I decided to install a custom rom for CM7 r2 hboot. So I flashed the CM7 r2 hboot again, erased cache, booted the recovery and flashed rom.
The rom was booting! But again, after fiddling with flashing a new recovery with 4EXT Updater, the rom rebooted into splash1 and stuck there.
After this first time, it has yet never rebooted again. So I twist my fingers that it was a custom rom bug on first boot.
Flashing the recovery via 4EXT Updater worked for me, despite of none of the recoverys flashed via fastboot had booted before.
Anyway, thanks for the help.
Hopefully it helps someone with the same problem,
but I doubt there are many people dumb enough to flash blackrose hboot on a desire
Cheers
criestr

I had a similar problem with my old Magic. I have Desire now but never had that problem. I hope not.
Anyways, the way I solved it was to flash the right radio.img. I supposed you can try to fastboot flash radio radio.img. Make sure you use the right radio.img. That is what I did if I recall correctly and it worked for me on Magic. I don't know if it is will work on Desire that way.
The other thing is when Ruu failed at radio, I think it is because the lower version of radio.
I hope this helps.
Try it and let me know.

bortak said:
After "a lot" of research you still haven't looked at my guide, well done.
Click to expand...
Click to collapse
link please

[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!