Develop Bugs

Stuck in Hboot, pc36 & recov not working

Hello,
I've been rooted for over a year now. Have flashed back and forth roms around hundreds of times now. Unfortunately an hour after flashing synergy godmode and some of the godmode tweaks, my phone rebooted while idling and bootloops.
Now i am stuck in hboot and can not enter recovery. I am using hboot 0.76.2000 (pc3610000) and s-off. I have tried flashing seperate clockwork and amon-ra embedded pc36img.zip, these say that they will complete updating but then will bootloop after i try to enter recovery. I have tried these updates with a different sd card (as my current sd card w/godmode may be an ext2 partition?) but that has not changed anything either.
As i understand, I can only push files with adb through recovery; which i can not get into.
If anyone can please help it would be very much appreciated.
Thank you in advance

try this way? its how i flash my recoveries when im switching or testing...
remove any pc36img.zip files from your sd and boot to your bootloader...
when you bootloader boots up let it scan for the pc36img whatever thing and let it say not found...
now highlight fastboot and click the power button and wait for FASTBOOT USB to show up...
then type in these codes...
Code:
fastboot devices
it should output some info, if you get some serial number then your good
then type in...
Code:
fastboot flash recovery *whatever the name of the recovery your using is*
so like for amon_ra 2.3 (which is what i use is)
Code:
fastboot flash recovery recovery-RA-supersonic-v2.3.img
just make sure that the recovery img file is in the same directory as the fastboot.exe file on your comp (its should be with all your other sdk stuff like adb.exe and such)
if all goes well then itll say
pushing recovery OKAY
writing recovery OKAY
and the amount of time it took...
then click back into your bootloader and go to the newly written recovery
(i apologize in advance if you already tried this with no avail)

I've set up fastboot usb and done this. Everything wrote ok and finished, however i still bootloop when trying to access recovery. I have tried multiple recoveries including clockwork 3, recovery-RA-supersonic-v2.3.img, and doing entire nandroid restores using nandroid recovery batch script. In both cases everything passes and nothing seems to be functional afterwards.
Any other ideas?

dunno man.. im just trying to visualize how it bootloops going to recovery.. it should be the white htc screen (or any other splash you may have set on there) and then boink recovery... does it like just sit there on the splash and thats it?
try letting it boot normal and then when it goes to the rom loading screen type in
Code:
adb reboot recovery
other than that something is totally askew bro

When booting, i'll get the white htc screen for 4-5 seconds, then it'll power off and reboot, unless i boot to hboot. When i hit recovery, it goes black for a second, then reboots to htc screen and repeats.
I've also tried complete wiping recovery and reloading using fastboot commander, and doing full pc36img.zip that include hboot, radio wiimax updates etc http://forum.xda-developers.com/showthread.php?t=830153&highlight=wimax
I may just go into a sprint store today. Was trying to avoid it as I really don't want to be stock again.

This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again

the only hboot that allows fastboot commands is 0.76 unfortunately
try running an ruu maybe? other than that i havent the slightest idea

I used this RUU - http://forum.xda-developers.com/showthread.php?p=7529500
It passed every step, but still bootloops when booting to ROM and Recovery.
I'm out of ideas....

I'm going to go with hardware problem.
Sent from my PC36100 using XDA Premium App

bad sector on the internal flash memory ?

My brother has the same problem and i have been trying to fix it with no luck. When i boot the phone up its beeps/vibrate 5 times, then sits on a black screen. I can get into hboot and load pc.....whatever files, it says they work but still reboot, 5 beep, ect. I was going to try an RUU next i see that didnt work for op.

i just ran into this problem today. I was at work when it randomly rebooted and now is stuck in a bootloop. i have tried everything even using the latest RUU. it finished but still bootloops. I am also not able to get into recovery. Sucks because im out of warranty.

So let me get this straight...you can't go into recovery because there's no recovery? You've installed drivers and ran RUU and still nothing? That seems weird because i had the same issue when i first rooted my phone with unrevoked, all i did was run the RUU and it restored my phone back to "stock" and i re-rooted again but this time using z4 root. You might just have to take the phone back to Sprint

Same issue but worse
I'm having the same issue as the OP except that my buttons (power and volume up/down) will not respond. I have scoured these and other forums for a situation like mine and have found none.
I have tried flashing recoveries, RUU's and jsut about anything someone says.
First screen says:
supersonic evt3 ship s-off
hboot-2.10.0001
touch panel atmelc03_16ac
oct 15 2010 12:01:00
hboot
fastboot
recovery
clear storage
simlock
hboot usb
then it scans the sd card for the pc36img zip. It will load but will freeze on the next screen:
parsing...... [sd zip]
1. boot loader
2. radio
3. boot
4. recovery
5. system
6. user data
7. splash
8. wimax
it will stick here and I am completely lost. My old Palm Pre will only suffice for a day.... max.
If anyone has come across a situation like this that might help me, would you please point me in the right direction. Thanks!

kdbrown5 said:
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
Click to expand...
Click to collapse
If you look in autoroot thread in my sig the "tools" zip has something that will let you flash different partitions from fastboot. If you use that to flash the PC36IMG from here it will give you the eng hboot back and possibly reflash whatever got corrupted.
Keep in mind, that will only work properly if you are not using one of the 2.xx hboots. Only phones with a 0.9x hboot will let you use it.

[Q] Bricked T-Mobile G2?

My mom brought me her phone last night because it's stuck in HBOOT. It refuses to boot into anything except HBOOT, and the keys are unresponsive in HBOOT.
I can't seem to find an uncorrupt PC10IMG.zip file to try flashing it, and any commands I send it through fastboot say completed or failed <status malformed>.
EG, fastboot reboot says it finished, but the phone doesn't reboot. Fastboot reboot-bootloader gives me the status malformed error.
Any ideas?
edit: the Shipped ROMs website zip is corrupted. Windows won't open it, and when I tried it in fastboot, it said "failed to access zipdata in <random ascii string>". I'd appreciate it if somebody could link me to a PC10IMG.zip of the official 2.3 rom.
edit2: Never mind. This thing's fragged, I give up.

The PC10IMG.zips will always say corrupt in windows as they are signed, and windows explorer does not handle signed zips at all.
You can use a program like 7zip or winrar to open them up.
You should probably check the md5 of the zip before flashing, to make sure it isn't corrupt.
-Nipqer

The MD5 matches, but the phone won't flash them for some reason. It pauses on the PC10IMG.zip when it goes through the list, but it won't flash and just goes right back into HBOOT.

Maybe try flash it via RUU mode.
Check the 'fastboot downgrade' method in this guide for instructions on how to do it.
-Nipqer

Nipqer said:
Maybe try flash it via RUU mode.
Check the 'fastboot downgrade' method in this guide for instructions on how to do it.
-Nipqer
Click to expand...
Click to collapse
Unpossible; ADB doesn't see the device when it's in HBOOT and it won't boot into anything else.
I think the eMMC is fragged.
Stupid refurbs. Also, all fastboot commands return "Failed (status malformed)". I tried updating the HBOOT using the file from htcdev.com, but it just says the battery isn't charged enough even if I charge it while off till the green light comes on.

Bootloop, Recovery loop!!! ADB/FASTBOOT/HBOOT HELP!

Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message <bootrom> [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51

ragus15 said:
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
Click to expand...
Click to collapse
Try this ruu its the newest officially signed ruu, so it will work with s-on. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.

I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?

Trygon said:
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Click to expand...
Click to collapse
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?

cmlusco said:
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
Click to expand...
Click to collapse
Holy cow, props on the quick reply. You're pretty much confirming my fears. I've tried a few combinations of battery and usb connections, but there's no vibration nor ADB signal.
I can't say I've ever seen a stock utility behave this way, so user beware. It's also worth noting that I have no history on this phone's modifications - Just that it was S-ON and locked when I got it, in bootloops between kernel and ROM, and attempting to access recovery looped it too.

cmlusco said:
Try this ruu its the newest officially signed ruu, so it will work with s-on. Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
Click to expand...
Click to collapse
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.

ragus15 said:
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
Click to expand...
Click to collapse
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?

cmlusco said:
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
Click to expand...
Click to collapse
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.

ragus15 said:
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
Click to expand...
Click to collapse
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?

cmlusco said:
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
Click to expand...
Click to collapse
I have tried fastboot erase recovery followed by the flash and still get the white HTC image. I am not able to boot the os... i get white HTC splash image over and over, and the USB driver that tries to mount to my desktop in the bootloop is not Android 1.0, it is CMDA technologies. I have no idea what that is or if that has to do with the previous frawg/straight talk flash attempts.

[Q] Wildfire stuck on HTC logo after restoring stock rom

Hi guys,
I'm going crazy with this Wildfire. I had Cyanogenmod on this unlocked device. I tried to restore a stock Marvel ROM. After that I could not start the phone anymore, it's just stuck at white screen with HTC logo. I booted in boot mode and could not get to recovery. I managed to install via fastboot USB a clockwork recovery, from there I could install some ROMs I found (including Marvel and Cyano) but after rebooting my phone just reached the HTC logo and stays stuck there. I can't RUU because for some reason the process fails during upgrade.
Any idea?
BUZZ PVT SHIP S-OFF
HBOOT-6.01.0002
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.15.31
Nov 17 2010, 12:08:53

petnas said:
Hi guys,
I'm going crazy with this Wildfire. I had Cyanogenmod on this unlocked device. I tried to restore a stock Marvel ROM. After that I could not start the phone anymore, it's just stuck at white screen with HTC logo. I booted in boot mode and could not get to recovery. I managed to install via fastboot USB a clockwork recovery, from there I could install some ROMs I found (including Marvel and Cyano) but after rebooting my phone just reached the HTC logo and stays stuck there. I can't RUU because for some reason the process fails during upgrade.
Any idea?
BUZZ PVT SHIP S-OFF
HBOOT-6.01.0002
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.15.31
Nov 17 2010, 12:08:53
Click to expand...
Click to collapse
Can you link to the ROM your trying to install?
Sent from my HTC Desire S using Tapatalk

petnas said:
Hi guys,
I'm going crazy with this Wildfire. I had Cyanogenmod on this unlocked device. I tried to restore a stock Marvel ROM. After that I could not start the phone anymore, it's just stuck at white screen with HTC logo. I booted in boot mode and could not get to recovery. I managed to install via fastboot USB a clockwork recovery, from there I could install some ROMs I found (including Marvel and Cyano) but after rebooting my phone just reached the HTC logo and stays stuck there. I can't RUU because for some reason the process fails during upgrade.
Any idea?
BUZZ PVT SHIP S-OFF
HBOOT-6.01.0002
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.15.31
Nov 17 2010, 12:08:53
Click to expand...
Click to collapse
DON'T RESTORE A STOCK MARVEL ROM!!! Our device is "buzz", "marvel" is Wildfire S.

Same for me
KoolKid98189 said:
DON'T RESTORE A STOCK MARVEL ROM!!! Our device is "buzz", "marvel" is Wildfire S.
Click to expand...
Click to collapse
I'm stuck on it aswell but I can go into Recovery.
However when I try and install the stock rom:
RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.zip
I get the error message:
Amend scripting (update script) is no longer supported. Amend scripting was deprecated by Google in android 1.5. It was necessary to remove it when upgrading to the clockworkmod 3.0 gingerbread based recovery . Please switch to edify scripting ( update - script and update binary) to create working update zip packages. Installation aborted.
and when I try the safe flash zip:
Buzz_Froyo_hTC_WWE_2.22.405.1_SAFE_FLASH_ZIP
it always says its bad.
Also when I download the .exe instead of zip and it runs through the program it finds the phone but says it has less than 30% battery even though I have been charging my phone from the socket for 2 days.
Any ideas on what to do?
Thanks, Aadil

Answer
aadil10 said:
I'm stuck on it aswell but I can go into Recovery.
However when I try and install the stock rom:
RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.zip
I get the error message:
Amend scripting (update script) is no longer supported. Amend scripting was deprecated by Google in android 1.5. It was necessary to remove it when upgrading to the clockworkmod 3.0 gingerbread based recovery . Please switch to edify scripting ( update - script and update binary) to create working update zip packages. Installation aborted.
and when I try the safe flash zip:
Buzz_Froyo_hTC_WWE_2.22.405.1_SAFE_FLASH_ZIP
it always says its bad.
Also when I download the .exe instead of zip and it runs through the program it finds the phone but says it has less than 30% battery even though I have been charging my phone from the socket for 2 days.
Any ideas on what to do?
Thanks, Aadil
Click to expand...
Click to collapse
try this file
shipped-roms(dot)com/download.php? category=android&model=Buzz&file=RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe
use . instead of (dot)
follow these instructions if it doesn't work
forum(dot)xda-developers(dot)com/showthread.php?t=1132028
use . instead of (dot)
hope that helps

digijedi007 said:
try this file
shipped-roms(dot)com/download.php? category=android&model=Buzz&file=RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe
use . instead of (dot)
follow these instructions if it doesn't work
forum(dot)xda-developers(dot)com/showthread.php?t=1132028
use . instead of (dot)
hope that helps
Click to expand...
Click to collapse
No, didn't work.
And the guide is for downgrading hboot which I've done.
I have clockwork Recovery mod v4.0.1.4 and I think I need 5
but whenever I try to flash a zip I get the error:
Finding update package...
Opening update package...
Installing update...
Instalation aborted.

aadil10 said:
No, didn't work.
And the guide is for downgrading hboot which I've done.
I have clockwork Recovery mod v4.0.1.4 and I think I need 5
but whenever I try to flash a zip I get the error:
Finding update package...
Opening update package...
Installing update...
Instalation aborted.
Click to expand...
Click to collapse
So do you want to go back to official (albeit old sense software?)
---------- Post added at 09:43 PM ---------- Previous post was at 09:34 PM ----------
If you don't i'd recommend this rom it does run quite a bit faster than sense http://download.cyanogenmod.org/get/jenkins/2808/cm-7.2.0-buzz.zip
it's what i use on my buzz

digijedi007 said:
So do you want to go back to official (albeit old sense software?)
---------- Post added at 09:43 PM ---------- Previous post was at 09:34 PM ----------
If you don't i'd recommend this rom it does run quite a bit faster than sense http://download.cyanogenmod.org/get/jenkins/2808/cm-7.2.0-buzz.zip
it's what i use on my buzz
Click to expand...
Click to collapse
thats the problem, I get that error message whenever I try to flash a zip

before you try flashing anything did you format everything but ext_sd card?
recovery 5 http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip
also try seeing if there is a adb/fastboot option somewhere in your recovery when you find it open it
then from your pc / run from your adb/fastboot dir
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
fastboot reboot-bootloader

digijedi007 said:
before you try flashing anything did you format everything but ext_sd card?
recovery 5 http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip
also try seeing if there is a adb/fastboot option somewhere in your recovery when you find it open it
then from your pc / run from your adb/fastboot dir
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
yeah I formatted it all
And how can I find adb/fastboot on the recovery zip? when I click it it just shows:
android-info.txt
recovery.img
and where is my adb dir?

aadil10 said:
yeah I formatted it all
And how can I find adb/fastboot on the recovery zip? when I click it it just shows:
android-info.txt
recovery.img
and where is my adb dir?
Click to expand...
Click to collapse
you will need these http://adbdriver.com/upload/AdbDriverInstaller.exe (adb drivers) also make sure to uninstall any htc desktop software you have installed, you will need to install this http://forum.xda-developers.com/showthread.php?t=2317790 (adb+fastboot tools) and afterwards put that downloaded recovery zip into that folder it would be C:\Program Files (x86)\Minimal ADB and Fastboot if you have a x64bit operating system otherwise it would be at C:\Program Files\Minimal ADB and Fastboot\
then you would need to use your fastboot mode > when you hold your vol buttons+pwr button during startup select fastboot there and then from your pc using the commands i speciefied you would overwrite the recovery with a newer one so to do that the easiest would be to use the shortcut on your desktop that the minimal adb installer creates ,
so open minimal adb shortcut on your desktop
then excecute these commands
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
fastboot reboot-bootloader

digijedi007 said:
before you try flashing anything did you format everything but ext_sd card?
recovery 5 http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip
also try seeing if there is a adb/fastboot option somewhere in your recovery when you find it open it
then from your pc / run from your adb/fastboot dir
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
Clockworkmod 5 worked when I flash it but when I restart my phone it goes back to version 4

You have to flash recoveries with pc's , just flashing it with your existing recovery won't help at all, so you need to use the software i provided links for and use that adb commands to overwrite your existing recovery so do>take out the battery from the phone and unplug it>then>put battery back >
then run the adb shortcut on your desktop>
then just hold pwr+vol btns simultaneously>then
at the very top - select "Fastboot",and connect your phone with the USB Cable to your PC.Then it should say "Fastboot USB" on your phone's screen.>
Type:
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
afterwards reboot your phone and then try flashing another zip and see if it works

digijedi007 said:
You have to flash recoveries with pc's , just flashing it with your existing recovery won't help at all, so you need to use the software i provided links for and use that adb commands to overwrite your existing recovery so do>take out the battery from the phone and unplug it>then>put battery back >
then run the adb shortcut on your desktop>
then just hold pwr+vol btns simultaneously>then
at the very top - select "Fastboot",and connect your phone with the USB Cable to your PC.Then it should say "Fastboot USB" on your phone's screen.>
Type:
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
afterwards reboot your phone and then try flashing another zip and see if it works
Click to expand...
Click to collapse
Nevermind, somehow when I booted my phone it went onto cyanogenmod 7 so its working!

Ok, was it the 7.2 one

digijedi007 said:
Ok, was it the 7.2 one
Click to expand...
Click to collapse
yeah, back to how it was after I flashed cyanogen mod

[Q] Having trouble flashing new recovery

Really hope that I am in the right section.
I have been running the blisspop rom for a little while now. Wanted to give a new rom a shot. Went into recovery and wiped as usual and went to flash and got a "this package supports bootloader....." Realized that the new rom recommenced TWRP or Clockwork. So I went into fastboot and tried flashing both Clockwork and TWRP and after flashing and rebooting it hangs on the boot screen with "entering recovery" at the top.
Suggestions? Help?

harrishabitat said:
Really hope that I am in the right section.
I have been running the blisspop rom for a little while now. Wanted to give a new rom a shot. Went into recovery and wiped as usual and went to flash and got a "this package supports bootloader....." Realized that the new rom recommenced TWRP or Clockwork. So I went into fastboot and tried flashing both Clockwork and TWRP and after flashing and rebooting it hangs on the boot screen with "entering recovery" at the top.
Suggestions? Help?
Click to expand...
Click to collapse
Are you flashing the right recovery that's made specifically for your device?

djpabz23 said:
Are you flashing the right recovery that's made specifically for your device?
Click to expand...
Click to collapse
Yes I am, I have a At&t Htc one M8 and for clockwork I flashed 6.0.4.3 and twrp is the correct one via their selection menu

harrishabitat said:
Yes I am, I have a At&t Htc one M8 and for clockwork I flashed 6.0.4.3 and twrp is the correct one via their selection menu
Click to expand...
Click to collapse
Here download this one: Click Here
Boot your phone into bootloader,
Choose Fastboot and hook it up to the computer
Wait until it says Fastboot-USB
Open CMD in the window where you downloaded the file and copy this without the quotation marks: "fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img"
Wait until it finishes, then just try going back into recovery

djpabz23 said:
Here download this one: Click Here
Boot your phone into bootloader,
Choose Fastboot and hook it up to the computer
Wait until it says Fastboot-USB
Open CMD in the window where you downloaded the file and copy this without the quotation marks: "fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img"
Wait until it finishes, then just try going back into recovery
Click to expand...
Click to collapse
Yep same thing...just hangs on the white HTC boot screen with Entering Recovery at the top. The weird thing is even though it hangs there I still get a message on my computer that says the phone is connected through USB

harrishabitat said:
Yep same thing...just hangs on the white HTC boot screen with Entering Recovery at the top. The weird thing is even though it hangs there I still get a message on my computer that says the phone is connected through USB
Click to expand...
Click to collapse
hmm.. Odd. Have you ever tried RUU back to stock and retrying all over again?

harrishabitat said:
Yep same thing...just hangs on the white HTC boot screen with Entering Recovery at the top. The weird thing is even though it hangs there I still get a message on my computer that says the phone is connected through USB
Click to expand...
Click to collapse
Try this:
fastboot erase cache
Then flash again twrp recovery
Fastboot flash recovery twrp_recovery_name.img
Send with my M8 from Tuttoandroid

That didn't work either. Has anyone else tried to go from the philz recovery back to the other ones and had any issues?

Still trying to figure this out...maybe someone else has a suggestion. I can't RUU since I don't have S-Off, but there should't be an issue flashing a new recovery, I've never had this issue before.

harrishabitat said:
Still trying to figure this out...maybe someone else has a suggestion. I can't RUU since I don't have S-Off, but there should't be an issue flashing a new recovery, I've never had this issue before.
Click to expand...
Click to collapse
Okay. Let's start over from the beginning.
Go here and download this. on your PC.
rename it to "recovery.img" (no quotes) and put it into your fastboot folder on your PC. (either fastboot or platform-tools depending on the ADB version you have)
Hook up to ADB/fastboot and enter the command fastboot flash recovery recovery.img.
The img you are trying to flash has to be in your fastboot folder.
Also, make sure you have the proper drivers installed. You can confirm this by going to Device Manager on you PC (enter device manager into the search box in your start menu. If you see a yellow exclamation point over "My HTC" or "Android" you don't have the proper drivers).
If you get the yellow "!", and don't have the drivers, then you can get them by clicking this link.
Also, make sure that HTC Sync Manager is uninstalled from your computer. It does not play nice with ADB.

xunholyx said:
Okay. Let's start over from the beginning.
Go here and download this. on your PC.
rename it to "recovery.img" (no quotes) and put it into your fastboot folder on your PC. (either fastboot or platform-tools depending on the ADB version you have)
Hook up to ADB/fastboot and enter the command fastboot flash recovery recovery.img.
The img you are trying to flash has to be in your fastboot folder.
Also, make sure you have the proper drivers installed. You can confirm this by going to Device Manager on you PC (enter device manager into the search box in your start menu. If you see a yellow exclamation point over "My HTC" or "Android" you don't have the proper drivers).
If you get the yellow "!", and don't have the drivers, then you can get them by clicking this link.
Also, make sure that HTC Sync Manager is uninstalled from your computer. It does not play nice with ADB.
Click to expand...
Click to collapse
I appreciate the detailed instructions, and I went through and did it exactly like you suggested and I ended up with the same issue. I am able to flash the recovery, the issue is afterwards when I reboot the bootloader then try to go into the recovery it freezes on the htc logo screen with "entering recovery" at the top of the screen. I have been able to flash roms and everything with no issue, just for some reason I can't switch recoveries.

harrishabitat said:
I appreciate the detailed instructions, and I went through and did it exactly like you suggested and I ended up with the same issue. I am able to flash the recovery, the issue is afterwards when I reboot the bootloader then try to go into the recovery it freezes on the htc logo screen with "entering recovery" at the top of the screen. I have been able to flash roms and everything with no issue, just for some reason I can't switch recoveries.
Click to expand...
Click to collapse
Having the same issue, a few things a I see on Hboot:
*** TAMPERED ***
*** UNLOCKED ****
S-ON
Is that ok?
Thanks in advance