[Q] Desire stuck in bootloader loop after hboot downgrade - HELP!! - Desire Q&A, Help & Troubleshooting

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.

Related

[Q] Rooting phone that won't go past white screen

A few days ago, my dad called me about a HTC Evo 4G he just got. It's a replacement that someone got for him b/c his old one was broken. The issue is that the phone won't go past the "HTC" white screen. I told him to check the HBOOT and he says it's 2.10. The weird thing about it is that it says "S-ON".
I told him to "Clear Storage" from the bootloader... No success.
The only way I figured that this issue could be fixed was to root a custom ROM onto it.
PS: Steps commonly say to make sure that USB Debugging is on... If I'm unable to get the phone to load the stock ROM that's already on it... How could I do that? (If rooting is even possible)
I would go to the bootloader, mount it ad fastboot, then try to manually push a new boot partition extracted from a rom and use adb to do so.
If it's HBoot 2.10 and it's S-On, use the old Unrevoked to root, and that will also push Recovery on the phone.
Then, flash the pc36img of Amon Ra, get into recovery, wipe everything, every single thing ,except the SD Card and try to boot up, or flash a new ROM

[Q] Is it possible to Recover my DInc?

I hope someone in this community is able to help. I've already been scouring Google this morning for people with a similar issue and haven't been successful in getting my phone to come back so I suspect there may be a hardware issue.
Here's a summary of the problem:
My phone shutdown this morning while I was listening to a podcast. It got stuck in a boot loop at the splash screen, constantly rebooting itself. A battery pull would not solve the problem. I was able to get it into HBOOT (version 0.92) but when I tried going into recovery from there, It got stuck on the splash screen (no looping). Before all this I had been running Nils Business Gingersense for quite a while and things were working fine, in case anyone needs that detail.
After failing to boot to recovery, here are some of the things I have tried to fix this issue:
1. Factory reset in HBOOT
2. Flashed RUU 2.2 and then tried RUU 2.3.4 through HBOOT. Though neither of these would get the phone to come up, the splash screen reboots stopped and the phone just freezes in splash screen now (over 30 minutes with no change).
3. Tried to reflash CWM 5.0.2.0 through Fastboot. Although the phone is recognized by 'fastboot device', it says 'remote: not allowed' when try to flash the .IMG file.
4. Tried to flash an older CWM recovery from when I originally rooted my phone --same 'not allowed' error
5. Ran the official RUU for Froyo on my PC and it looked promising but I never got past the splash screen afterward a reboot.
6. I don't know a ton about ADB but ADB does not recognize my device even though Fastboot does.
At this point I'm not sure what else to try. It seems promising that I can get into HBOOT and that Fastboot will recognize my phone but what can I do with that now?
Thanks for any ideas you might have.
Have you tried flashing cwm thru hboot as a PB31IMG.zip? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. If that dosent work you could try to update hboot to 1.02 and htcdev unlock it. This will allow extended fastboot commands. You can do this on the htcdev website. Or you could downgrade hboot to the 0.77 engineering bootloader http://dinc.does-it.net/Hboots/ENG_Hboot_0.77/PB31IMG.zip which basicly does the same thing, and might be a better option than upgrading. You are s-off right?
Yes, I still have S-OFF. I did try flashing several recoveries through hboot and they all acted like they updated fine but I wasn't able to boot into any of them because I kept getting frozen at the white screen after choosing recovery from hboot. I will try another hboot and see if that makes any difference. Thanks.
Cmlusco, I tried the CWM version you posted with hboot .92 and .77 but had no luck. I also tried walking through the hboot upgrade steps on the htcdev site but I couldn't get the RUU exe to find my phone. This is odd because an older RUU found the phone just fine earlier today.

Emergency help: Possible brick?

Alright,
So I had several issues caused by the latest INC 2 OTA. After the OTA messed up my phone I followed several threads online to downgrade to 2.3.3. After I did this, I updated back to 2.3.4 and then did the new OTA. It worked.
When I did this, "recovery" disappeared in the bootloader.
I eventually unlocked my phone again and was able to flash a custom recovery.img to get clockwork mod recovery back on. Everything was going smoothly!
I then entered recovery and accidentally restored a previous backup (version 5.xxxxx which would power off due to the OTA messing it up). So I immediately did a factory reset.
After this, the Radio is 1.09.01.0312. Every time I boot up it gets stuck on the white HTC screen. I've tried clearing cache, formatting system and then doing a factory reset. It still is the same.
To my knowledge this current radio is the radio for the new OTA (6.xxxxxx). My phone thinks it's software is still 5.xxxxxx due to the accidental restore.
I guess the radio I need ends in .1111. Would not having this radio cause this issue? I downloaded the radio but it says I have to be S-OFF to install it.
I am currently unlocked and S-ON.
Am I screwed or is there anything I can do to fix this?
I can only Fastboot and use CMD prompts. I don't even care if it's a custom rom at this point. Anything I can do to restore the phone.
Please and thank you.
EDIT: Also, PG32IMG files will not work. If I go to manually install it says E: Can't open sdcard/PG32IMG.zip (BAD)
Nor will it go through when I boot it up in the bootloader. I tried this for the version 5.xxxxxx. Do I need to wait for a 6.xxxxxx officiall RUU PG32IMG to come out? I haven't seen one yet.
Only one thread needed

[Q] Help Please with possible bricked phone after upgrade to 4.0.4

Hello
This is my last ditch attempt to fix my HTC ONE X, before I resign and send it to HTC for a repair. The phone was rooted and locked to T-mobile UK when the update for 4.0.4 came through 2 days ago. I downloaded it OTA and installed the update. After the update had installed the phone was in a bootloop. It kept loading the home screen and rebooting.
I have tried the following with no success!
Initially couldn't get access to recovery, but when I reflashed recovery I have no access to the sd card. The drive shows up on my computer when connected via usb but it says there is no drive connected and all my files appeared to have been deleted, although the reset folders are visible! So can't transfer a custom ROM and flash.
I have reflashed a boot.img and now the ONE X doesn't even get to the home screen it just hangs at the htc splash screen.
I have also relocked the bootloader to flash a RUU. This hasn't worked either. It appears to be working and the phone screen turns black with an install icon, but the RUU stops after approx 1 min, says it's completed, but nothing has changed on the phone.
This has been a nightmare and am just about to package it up and send to HTC and accept any charges for rooting!
Please help!!!
Can you get the phone in hboot/fastboot ?
What do you see when you enter
Fastboot devices or adb devices ?
If it works unlock your bootloader again with the unlock token.google the exact fastboot command, don't know it for sure now i'm on my phone.
Reflash custom cwm recovery (5.8.0.4 if i'm guessing it right) you can mount sd card within recovery
From there flash a custom rom again.
Flash kernel from the rom and install it with a full wipe.
Think it's your best option as far as I can see now
If your bootloader is locked and you have a stock recovery you can not flash anything
Verstuurd van mijn HTC One X
Thank you for your reply.
I managed to finally get access to the SD card and transfer a custom ROM. Which I flashed and the phone is working again!!
Thank you for your help!! So relieved!

M8 appears bricked no rom or recovery menu

Tried to remove cynagenmod from my htc and return to stock android settings and messed up somewhere along the line, on powering on my phone it loads straight into the boot loader, navigating to >HBOOT then pressing >RECOVERY makes the HTC logo appear for a moment before returning to the first bootloader screen.
[software status modified, re locked, security warning, M8-UL PVT SHIP S-ON]
The rom has been deleted along with recovery, I am not an expert in using fastboot tried using it for a bit and had no success also tried installing htc sync manager to see if it would help but the installer for the sync manager would crash my computer every time (windows 10). Looking for some help as what to do not sure if it can be fixed or should I bin it thanks.
I would RUU if it was me in your position.
bigmacattack said:
Tried to remove cynagenmod from my htc and return to stock android settings and messed up somewhere along the line
Click to expand...
Click to collapse
To properly troubleshoot where you went wrong, and how to solve it, you will need to describe the exact steps of how you tried to return to stock.
It seems you wiped things in recovery, expecting that to return you to stock? If so, that isn't the case as you now know, without flashing a ROM, TWRP backup, etc.
Similarly, relocking the bootloader renders the phone unable to boot, and wipes the phone; as it expects RUU to be run. But you haven't explained if you were trying to run an RUU, which one, details of your phone version, etc.

Categories

Resources