Develop Bugs

[solved] unable to access recovery

hi all.
s-off with alpharev, i'm only able to boot into bootloader and use fastboot, no recovery, no system, that's all.
i'm able to flash recoveries but when i try to enter them, my desire reboots and freezes on the alpharev splash screen.
never did the golden card...
what are my choises... just ruu? anything else?
my info:
SPL/hboot version: 0.93.1000.
Radio version: 5.17.05.23.
Main software version: 2.29.405.5.
cid: htc__405.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
thanks everyone...

have you tried booting into recovery using thru some rom, like oxygen or so? hold down the power button, select reboot->reboot into recovery. If it is not working than I think something is with your recovery. try flashing another one using ADB... fastboot flash recovery xxxx.img.
or try reboot recovery from adb

wings400 said:
have you tried booting into recovery using thru some rom, like oxygen or so?
Click to expand...
Click to collapse
pardon?
wings400 said:
hold down the power button, select reboot->reboot into recovery.
Click to expand...
Click to collapse
cannot access the system...
wings400 said:
If it is not working than I think something is with your recovery. try flashing another one using ADB... fastboot flash recovery xxxx.img.
or try reboot recovery from adb
Click to expand...
Click to collapse
i'm not able to list the device with adb anymore while with fastboot i already tried:
recovery-clockwork-2.5.0.7-bravo.img
recovery-clockwork-3.0.0.5-bravo.img
recovery-RA-desire-v2.0.0-CM.img
recovery-RA-desire-v2.0.0.img

Had the same prob...till i find this recovery: 4extRecovery
look here:
http://forum.xda-developers.com/showthread.php?t=1154221&highlight=4extrecovery
greez VA

i got some bad update.
i decided to revert it through a ruu but i probably got the wrong one and now i'm stuck at the htc logo with the four triangles in the corners.
i now run this RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe but i got:
Code:
ERROR [152]: IMAGE UPDATE ERROR
and the phone says:
Code:
Parsing...[downloaded ZIP]
[1] BOOTLOADER - OK
[2] RADIO_V2 - Fail-PU
[3] RADIO_CUST - OK
[4] BOOT - OK
[5] RECOVERY - OK
[6] SYSTEM - OK
[7] USERDATA - OK
[8] SPLASH1 - OK
[9] SPLASH2 - OK
Partition updtate fail!
Updtate fail!
can anyone suggest something else than send to htc?
thanks...

other update:
i made a goldcard and then i was able to successfully run the ruu!
now i'm s-on and i can access again to hboot and fastboot normally but i'm not able to boot into recovery neither the system...
options?
thanks...

final update.
after a day of cooling, it boots nomally into the stock rom.

your Recovery probably was corrupted somehow. As you've gone back to stock, my advice has come late: you could've erased the old recovery and reflashed a new one from fastboot. You could do this either Fastboot Commander, Android Flasher or by renaming your recovery zip file as PB99IMB.zip and letting fastboot find it and flash it.

HBOOT Message

Hi, just a little advice guys, I have 3 HTC Desires' in the house. The latest one, which I just SIM-Unlocked using "sieempi" Unlock utility (awesome btw)
Basically when I got to the HBOOT on the latest HTC Desire I got the following message which I didn't receive on any of my other Desires:
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
When I boot in to HBOOT I get:
"SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nbh]
No image or wrong image!
This phone was second hand, is this normal? Thanks

yes it's perfectly normal, AFAIK every Desire does this... it does a scan for files with those particular names, that's how you flash through bootloader.
e.g. If I put a .zip named PB99IMG.zip into the root of my SD-Card, containing boot, system, data (etc.) IMG's, it would automatically flash them (after asking you if you want to)
This method is commonly used to flash the extracted rom.zip from a RUU, instead of using a PC

bortak said:
yes it's perfectly normal, AFAIK every Desire does this... it does a scan for files with those particular names, that's how you flash through bootloader.
e.g. If I put a .zip named PB99IMG.zip into the root of my SD-Card, containing boot, system, data (etc.) IMG's, it would automatically flash them (after asking you if you want to)
This method is commonly used to flash the extracted rom.zip from a RUU, instead of using a PC
Click to expand...
Click to collapse
Yep, every desire does this 7 seconds after booting into Hboot.

[Q] Help Me and my desire hd

Hello everyone,
six months I have the ROM Miui but then the phone is switched off
my htc desire hd will not start
when I start the ext4 recovery touch: the error recovery in safe mode
and I can not install a new ROM or do a wipe
Here is what hboot says:
*******AAHK**********
ACE PVT ENG S-OFF RL
HBOOT-0.85.2425
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011,00:55:45
I also see "HBOOT USB PLUG" when plugged in, and the computer does beep though no connection can be established. HTC Sync doesnt work (on a different computer), adb cannot connect and AAHK doesnt find a device.
The RUU from HTCDEV doesnt find the phone either....
What can I do? I tried to flash many PD98IMG.zip for example that of the stock and PD98IMG_cwmrecovery nothing but the result is always:
sd checking ....
loading .... [PD98DIAG.zip]
No Image
Loading .... [PD98DIAG.nbh]
No Image or Wrong Image
Loading .... [PD98img.zip]
No Image
Loading ...... [PD98img.nbh]
No Image or wrong image.
aspect of your answers and sorry for my english stupid

first method.. you can try flashing recovery from FASTBOOT mode..
download 4EXT recovery.img from here then extracted file and placed it to your adb/ sdk folder on your pc...then flash it through FASTBOOT mode with command "fastboot flash recovery recovery.img"
second method...you can firstly flash RUU that already rooted by phiber2000 download from here.. through bootloader with PD98IMG.zip name of file..to fix your bootloader and at once replaced your hboot to the newest of ENG hboot..after that...you can continued with the first step for flashing recovery.img through FASTBOOT
hope this help..

thanks friend!
I flashed the recovery via fastboot commander but into recovery the ext4 partition is sometimes mounted and sometimes error mounting
the phone works via fastboot commander 1:51 :
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 0.85.2425.
Radio version: 26.10.04.03_m.
Main software version: 2.47.502.7.
cid: 11111111.
cpld: none.
product: ace.
mid: pd9810000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
I tried to erase the system cache and data but it makes me always the same problem later
What do you advise me to do?

Zueg92 said:
thanks friend!
I flashed the recovery via fastboot commander but into recovery the ext4 partition is sometimes mounted and sometimes error mounting
the phone works via fastboot commander 1:51 :
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 0.85.2425.
Radio version: 26.10.04.03_m.
Main software version: 2.47.502.7.
cid: 11111111.
cpld: none.
product: ace.
mid: pd9810000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
I tried to erase the system cache and data but it makes me always the same problem later
What do you advise me to do?
Click to expand...
Click to collapse
did you already tried flashing RUU PD98IMG.zip (rooted RUU by phiber2000) that i give it the link to you before..?
just make sure to placed that RUU PD98IMG under the root of your sd card..then flashing it through loading from your phone bootloader..

JJeamy said:
did you already tried flashing RUU PD98IMG.zip (rooted RUU by phiber2000) that i give it the link to you before..?
just make sure to placed that RUU PD98IMG under the root of your sd card..then flashing it through loading from your phone bootloader..
Click to expand...
Click to collapse
thanks friend,
Yesterday I solved and the phone started
but I was wrong to flshare the recovery and did the erase of the system and the phone is dead
when I connect the power supply does not turn on no led
it is fried the motherboard?

Zueg92 said:
thanks friend,
Yesterday I solved and the phone started
but I was wrong to flshare the recovery and did the erase of the system and the phone is dead
when I connect the power supply does not turn on no led
it is fried the motherboard?
Click to expand...
Click to collapse
when I connect it to my pc makes the sound of the new device but not red led power

Zueg92 said:
when I connect it to my pc makes the sound of the new device but not red led power
Click to expand...
Click to collapse
did the phone still can get into bootloader..?

JJeamy said:
did the phone still can get into bootloader..?
Click to expand...
Click to collapse
no i can't....i have deleted bootloader!! :crying:

Zueg92 said:
no i can't....i have deleted bootloader!! :crying:
Click to expand...
Click to collapse
WHAT !!!!...
are you sure that your bootloader is already gone...?
i mean...did you already trid to pressing and hold volume down+power to turn on your phone..then nothing happen..?
if so...then you must take your phone to the services center to flashing emmc from the beginning..
sorry for can't help you more than this..

JJeamy said:
WHAT !!!!...
are you sure that your bootloader is already gone...?
i mean...did you already trid to pressing and hold volume down+power to turn on your phone..then nothing happen..?
if so...then you must take your phone to the services center to flashing emmc from the beginning..
sorry for can't help you more than this..
Click to expand...
Click to collapse
thank you so much you have been very kind ....
Now I try to flash the bootloader via EPROM

[Q] Stuck in hboot (S-ON)

Details from hboot:
BRAVO PVT1 SHIP S-ON
HBOOT - 0.93.0001
MICROP-031d
RADIO-5.09.05.30_2
Hello
I have an HTC Desire that only boots up hboot (I can also change to fastboot). I have tried downloading the RUU to return the phone to stock but as I am running Windows 8 I can't install the driver for the phone. Windows 8 gives me a USB device not recognised error message when I connect my phone.
Has anyone else experienced this? If so do you have a fix?
(I have searched but am yet to find a solution )
Thanks :good:

Have a look at bortak's troubleshooting guide, stickied to the top of Q&A section, Method [7]
Use the PB99IMG.zip method, extracted from the 2.3.3. GB RUU at the bottom here. All you will need is a card reader to copy it to the root of the sdcard, no driver installation required.

Thanks for the reply.
I have actually tried this method - and just tried again - but I get this message flash up on my phone:
SD checking...
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading...[PB99IMG.zip]
No image!
Loading...[PB99IMG.nbh]
No image or wrong image!
and then it goes back to being stuck on hboot.

I think I may have sorted it!
I formatted the SD card to FAT32 and it seems to be installing ...fingers crossed.

[Q&A] Semi bricked Desire

Hey Folks!
After the dead of my desire (7 buzzes / vibrates -> indicates a broken soc/motherboard) and the new rising (got a motherboard of a desire with a broken screen) the old lady worked again!
I got the s/n and system from the one with the broken screen - this is normal because it's stored on the mainboard. It was a CM v7 as I remember.
Here as a list of things I did and where I stuck now:
flashed an up-to-date recovery TWRP -> worked
tried to install a new rom with a new hboot which -> didn't worked out
Since here I only can access the recovery
All attempts to flash something (via recovery or fastboot) -> doesn't work
also tried to use revolutionary (even it's already unlooked and s-off) -> but the app stucks
I could only flash the boot logo via fastboot the rest results in different errors like:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?

Here is an other error message i get when running this fastboot command
Code:
fastboot getvar all
getvar:all FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm realy appreciate any help!
BTW: I'm not a robot!

Des!re said:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?
Click to expand...
Click to collapse
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.

eddiehk6 said:
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
Click to expand...
Click to collapse
Thanks for your reply. Some things I forgot to mention in the thread above.
I successfully rooted, s-off, and flashed a new hboot & rom to my old desire.... all before she died. I remembered I needed some tries for the hboot... but it worked out fine in the end.
I also need to say that I tried (with the new/repaired one) different clients (hardware and os, win & linux) and different cables. Just to be sure.
I also went sure that fastboot is working (fastboot devices) and there always was my serial -> so it's good for sure
I read something about that the Alpharev hboot (with the repaired phone there was also the bootsplash with 'alpha-rev s-off / why so serious?' before I flashed it away to the stock 'htc') is somehow write-protected itself which can cause issues???
I tried to flash the "Alpha Jelly (250/5/182) hboot" to be able to install CarbonRom 1.0 (4.4.4) by spezi77 (http://forum.xda-developers.com/showthread.php?t=2658853). But I didn't succeeded at all.
eddiehk6 said:
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
Click to expand...
Click to collapse
I think I flashed the recovery via fastboot, it just worked once. When I tried to flash CWM it didn't worked anymore.
eddiehk6 said:
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
Click to expand...
Click to collapse
I did checked the md5sum's and I tested a couple of Roms (more than 3)
eddiehk6 said:
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
Click to expand...
Click to collapse
My old devices was a PVT4 and the repaired one is a PVT1 - there should be no difference for the hboot i guess?
eddiehk6 said:
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
Click to expand...
Click to collapse
This I should have done straight after I repaired the hardware and I was able to boot in CM7.... To late for now but if I have a working state I definitely do this!! :good:
eddiehk6 said:
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
Click to expand...
Click to collapse
I don't have a booting system yet so I need to postpone this. To be able to do the pb99img.zip method i formatted the whole sd-card with one partition as fat32. But when I have (hopefully) soon a working system I need to partion it correctly - easy!
eddiehk6 said:
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.
Click to expand...
Click to collapse
I'm the resarcher! I'm going down to reasearch - I will report!
Thanks for your help so far!

I'm the resarcher! I'm going down to reasearch - I will report!
Click to expand...
Click to collapse
I went down to research!
I tried to flash hboot 'Bravo Stock' by Alpharev.
Code:
fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)...
OKAY [ 0.104s]
writing 'hboot'...
OKAY [ 0.160s]
finished. total time: 0.264s
looks good for me!
the bootscreen changed from
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
to
Code:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
so first and third line changed!
And because it's so nice to flash hboot i also flashed AlphaRev Jelly successfully!!
I try flash a rom now :fingers-crossed:

After I successfully flashed my hboot (twice!)....
I'm not able to wipe or install stuff....
Team Win Recovery Project v2.7.1.0
WIPE -> Factory Reset (Wipe Data, Cache and Dalvik)
Code:
Factory Reset Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
E:Unable to recreate and-sec folder.
Updating partition details...
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup.
Full SELinux support is present.
E:Unabke to mount /sdcard/TWRP/.twrps when trying to read settings file.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Updatting partition details...
E:Unable to mount storage.
### FAILED ###
Team Win Recovery Project v2.7.1.0
Install -> ZIP
Code:
Zip Install Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
Installing '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Could not create file for updater extract in '/tmp/updater'
Error flashing zip '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'
Updatting partition details...
### FAILED ###
Maybe there is something "broken" with the filesystem?
As always I appreciate any help

Did a 'clear userdata' in the boot menu and then a wipe via TWRP.
Now it was successful but with this errors in the console:
Code:
Factory Reset Complete
Successful
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Wiping Android Secure
Formatting SD-Ext using make_ext4fs function.
Updating partition details...
But I wonder where are these errors from
Installing a rom still doesn't work. I think the problem is this line:
Code:
E:Could not create file for updater extract in '/tmp/updater'

There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
You have to do the following steps to flash any files :
- boot into recovery mode
- choose 'Advanced'
- choose 'Terminal Command'
- You're now on the '/' (root of the file system). Choose 'Select'
- Type : 'mkdir tmp' without quotes, then Hit the enter key of your keyboard.
- Return to the main screen (Go back 3 times)
- Choose 'Install' and select the file.
Click to expand...
Click to collapse
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046

Des!re said:
There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046
Click to expand...
Click to collapse
I've personally never used TWRP on the Desire.
I recommend trying with 4EXT Recovery, never had any issues with it.
If you can successfully flash an hboot, you should be able to flash the recovery.img using the same method.