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.

[Q] HELP! My Desire doesn't boot

PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!

AndrewMe said:
PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!
Click to expand...
Click to collapse
My guess is that they've tried to install stock ROM and it failed because I suspect you have custom hboot partitions.
The safest way would be to bring your phone to stock and then try re-rooting, custom Hboot and Rom.
Good luck !

AndrewMe said:
PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!
Click to expand...
Click to collapse
Bring your phone back to stock rom:
1.) Create goldcard: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
2.) Put this in your desire
3.) Download latest stock ruu: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
4.) Boot your phone into fastboot mode and run exe on your computer
5.) If this does not work, extract pb99img from the ruu:
http://forum.xda-developers.com/showpost.php?p=9036922&postcount=2
6.) Put this on your goldcard and boot your desire into bootloader
7.) Follow the instructions

paul.c said:
My guess is that they've tried to install stock ROM and it failed because I suspect you have custom hboot partitions.
The safest way would be to bring your phone to stock and then try re-rooting, custom Hboot and Rom.
Good luck !
Click to expand...
Click to collapse
Thank you for reply, I tried it as well - device not found...

MatDrOiD said:
Bring your phone back to stock rom:
1.) Create goldcard: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
2.) Put this in your desire
3.) Download latest stock ruu: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
4.) Boot your phone into fastboot mode and run exe on your computer
5.) If this does not work, extract pb99img from the ruu:
http://forum.xda-developers.com/showpost.php?p=9036922&postcount=2
6.) Put this on your goldcard and boot your desire into bootloader
7.) Follow the instructions
Click to expand...
Click to collapse
Thanks for your reply, start to try the 2nd variant..

MatDrOiD said:
Bring your phone back to stock rom:
1.) Create goldcard: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
2.) Put this in your desire
3.) Download latest stock ruu: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
4.) Boot your phone into fastboot mode and run exe on your computer
5.) If this does not work, extract pb99img from the ruu:
http://forum.xda-developers.com/showpost.php?p=9036922&postcount=2
6.) Put this on your goldcard and boot your desire into bootloader
7.) Follow the instructions
Click to expand...
Click to collapse
It worked.. a bit by the other way - first placed stock hboot from AlphaRev's site, then booted into bootloader, then normal flashing of stock RUU went well.
Thanks once again!

It worked.. a bit by the other way - first placed stock hboot from AlphaRev's site, then booted into bootloader Can you explain please!! I am not as expert as you are...

it worked actually!! the phone's has been ROMed but I still have the same original problem!! it goes off by itself and the camera doesn't work??
Any Ideas??

HTC_DeSiRe_83 said:
it worked actually!! the phone's has been ROMed but I still have the same original problem!! it goes off by itself and the camera doesn't work??
Any Ideas??
Click to expand...
Click to collapse
Sounds like an hardware issue. You are back on stock ruu, so you can give htc a ring.

Bad flashing caused big problems

Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid

When you flash a new kernel, all you have to do is place modules zip in phone storage, put phone in bootloader, connect to computer, flash boot.img, go into recovery and flash modules. If you don't flash boot.img, the phone won't boot. Try going into bootloader by pressing volume down and power at the same time and holding it, flash viper boot.img via fastboot kit, full wipe and reflash rom. I've messed up a few times but this has always worked for me.

Beyazid said:
Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid
Click to expand...
Click to collapse
there are infinite posts about how to fix this and tutorials too if you use the search button, anyways
1- why using faux 7m when there is already 10m ?
2- hold power+vol dwn
3- go to recovery (hboot not fastboot)
4- go to mounts and storage, mount storage usb
5- copy to your sd all the files excluding the boot.img from faux
6- flash rom then modules then type in cmd "adb reboot-bootloader" (without quotes),
7- choose fastboot in bootloader then flash boot.img and erase cache

@VCek: I flashed this before the Versions 10 and 11 came out
Thanks for the infos. I´ll use them the next time. But now I can´t reach the bootloader anymore because I locked the phone with "fastboot oem lock" and because of that I can´t do anything but go to the fastboot mode. The recovery is locked or in other words: I can´t use the CWM Recovery anymore.
If I click the recovery mode this happens: vvvvvv(dot)vidup(dot)de/v/l1vVH/ (make a dot instead of the word "dot" and change the V´s to W´s, I´m not allowed to post outside links right now)
The next step should be the unlocking I guess. Right? But how can I do that?
Edit: I was able to unlock the phone again so it should be easier from now on but your steps didn´t work for me. I reflashed the Viper X Rom and reflahed the Kernel without the boot.img in it. But I didn´t get the point which boot.img I should flash. Both of them or just the Rom boot.img?
Edit2: After a long day I was able to solve the Problem with the right RUU. After all it was easier than I thought and I should have done that at the beginning

[Q]Desire HD perpetual reboot

Hi everybody,
a few weeks ago, my HTC Desire HD under custom rom ( MIUI ) which was working just fine, decided to brutally reboot, and keep doing it again and again.
I checked the Bootloader. Got the classic unable to load PG58IMG.zip, then, going on recovery mod just makes the phone rebooting again and again, the fastboot is recognized by the computer, but not the sdcard.
I read some tutorials, and i used an official RUU, it worked, but put back my phone in S-ON mode.
So actually there is (are) the problem(s) :
Classic boot keeps rebooting ( green htc logo ).
I can go to the bootloader interface but Recovery makes my phone reboot again and again.
S-ON is back.
When i plug my phone fastboot is not recognized anymore ( since i used the ruu install ), and it doesnt mount my sdcard.
I thought using RUU Rom, which was an official one could be helpful, it seems it just turn the S-ON back and forbid every fastboot commands.
What can i do ?

graphomaniac said:
Hi everybody,
a few weeks ago, my HTC Desire HD under custom rom ( MIUI ) which was working just fine, decided to brutally reboot, and keep doing it again and again.
I checked the Bootloader. Got the classic unable to load PG58IMG.zip, then, going on recovery mod just makes the phone rebooting again and again, the fastboot is recognized by the computer, but not the sdcard.
I read some tutorials, and i used an official RUU, it worked, but put back my phone in S-ON mode.
So actually there is (are) the problem(s) :
Classic boot keeps rebooting ( green htc logo ).
I can go to the bootloader interface but Recovery makes my phone reboot again and again.
S-ON is back.
When i plug my phone fastboot is not recognized anymore ( since i used the ruu install ), and it doesnt mount my sdcard.
I thought using RUU Rom, which was an official one could be helpful, it seems it just turn the S-ON back and forbid every fastboot commands.
What can i do ?
Click to expand...
Click to collapse
Do you have custom recovery with S-ON? Flashing a RUU from S-OFF shouldn't have reverted to S-ON...and doint it was a mistake...it is much harder to sort issues when you are S-ON
Try wiping cache and factory reset...

Problem in Recovery boot, while rooting

I decided to root my phone. I have an htc one M8 with android version 4.4.2. I followed a detailed guide step by step found on htconeroot site (sorry cant post link im a new user but its the same rooting process i found everywhere). Everything went perfect until the final stage ''step 25: choose “RECOVERY” and hit the Power button'' well i did that and instead get access to TWRP Recovery, the HBOOT RECOVERY option just show me for about 1-2 seconds the screen with HTC logo and letters ''entering recovery ...'' but almost immediately jumps back to fastboot menu ! never get into TWRP so i can finish rooting process. My phone, if i select reboot, works fine (unrooted).
Details of the device:
MEM_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1102.19.1017
OpenDSP-v28.2.2-00546.0311
OS-2.19.401.2
Emmc-BOOT 1024MB
Aug 13 2015,
Also on the top displays ''TAMPERED'' ''UNLOCKED''
What i tried
Tried several TWRP recovery images, no luck, (actually i tried almost every TWRP file i found out there)
Tried fastboot erase cache, no luck
(no verizon or sprint im on international carrier)
Been stuck here for many hours, any ideas ?
Thank you
(sorry for my bad english)

First....I suggest updating your firmware to the latest version.
Second, When you flash TWRP which version are you trying to flash, and what command are you using?

firmware updated, still no luck
command i used: fastboot flash recovery
versions i tried: twrp-2.7.0.1-m8 till 2.8.6.0
Still got this annoying bootloop

Use correct twrp version on correct device variant.
You can't use a M8 twrp on a HTC ONE MINI 2 device
MEM_UL = HTC ONE MINI 2
M8_UL = HTC ONE M8

im a blind idiot ! for many hours flashed wrong device twrp versions ! stupid stupid stupid
so i tried all the m4 twrp versions i found, i used 11 versions from twrp-2.6.0.0-m4 till twrp-2.8.7.0-m4
and the problem still exists, no recovery mode-jump back to fastboot menu.
But the last moment i found on a forum (can't remember which one) that: twrp-2.7.1.0-20140802-memul.img
and finally yes ... i was able to enter the recovery and finish rooting process easily !
If anyone encounters similar problem just use the above twrp, well, it worked for me !
Thank you Kyuubi10 and ckpv5 for your help !