Develop Bugs

[Q] S-ON, non-rooted Z won't boot or go into recovery.

Hi All.
Not my phone, but a friends:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011.23:36:27
If you go into recovery, the phone just vibrates a few times and turns off. If you go Factory Reset, the phone just freezes.
I've tried:
RUU with no luck (get's stuck on Rebooting into Bootloader)
tried putting the .ZIP onto the SD but got "ModelID Incorrect" (can't create a GoldCard as phone won't boot, therefor no ADB)
flashing a recovery through fastboot but got "FAILED (remote: signature verify fail)"
booting into recovery using fastboot boot (FAILED (remote: signature verify fail))
I assume all my issues have been due to S-ON.
I'm stumped - any ideas?

There have been a few folks on here with the same issue in the last few weeks. Not that the phone is terribly old, but I wonder if it can be that some hardware component (eMMC or other) is failing over time?

expza said:
Hi All.
*snip*
RUU with no luck (get's stuck on Rebooting into Bootloader)
tried putting the .ZIP onto the SD but got "ModelID Incorrect" (can't create a GoldCard as phone won't boot, therefor no ADB)
flashing a recovery through fastboot but got "FAILED (remote: signature verify fail)"
booting into recovery using fastboot boot (FAILED (remote: signature verify fail))
?
Click to expand...
Click to collapse
IIRC there is a way to create a GoldCard manually without the phone ... but i'm highly unsure :-s
The last two sounds like an error due to s-on

oelly said:
IIRC there is a way to create a GoldCard manually without the phone ... but i'm highly unsure :-s
The last two sounds like an error due to s-on
Click to expand...
Click to collapse
I was able to create a working GoldCard using my phone, it no longer gives Model-ID Incorrect. HOWEVER, new problem. It's now moaning about Main Version being older, update failed.
I see android-info.txt in the ZIP is:
modelid: PC1010000
cidnum: T-MOB010
mainver: 2.15.531.3
hbootpreupdate:12
However, this phones info is:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011.23:36:27
I assume it's the Radio Version number that is not matching up - however, the one RUU's in Shipped-Roms with that Radio Number are EXE's and not ZIPs.
Does anyone know how I can get a ZIP RUU that would work with this phones current versions?
edit: p.s. ZIP I'm currently using is PC10IMG_Vision_TMOUS_2.15.531.3_Radio_12.52.60.25U_26.08.04.30_M3.zip (renamed when on SDcard to PC10IMG.zip)
double edit: Have found a way to extract zip from EXE. Loaded it to Gold Card and update is currently flashing via HBOOT. Still on Bootloader. Assume this takes a while (10 - 15 minutes), so I'll be patient.
combo edit: should state the the RUU ZIP I extracted was RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe

Phone honors the PC10IMG.zip, but gets stuck on BOOTLOADER - Updating.
Any suggestions? Is it safe to delete items out of the RUU .zip? Want to try flash recovery.img only.
edit: looks the the rom.zip I extract is always corrupt (when trying to edit it using WinRAR or something)

You can't edit the zips, they are signed, so anything you do to them will cause them to not flash.
Winrar might be complaining because of the signing.
-Nipqer

Given up on trying to flash the RUU via HBOOT - it just freezes on "Bootloader - Updating" - pulling battery causes no issues so I assume it doesn't even attempt to flash anything.
Next step, using HTCDev to unlock the bootloader? Safe? I worry that the Bootloader not flashing via RUU means that HTCDev Bootloader Unlock won't work, or could possibly break it.

same problem
hi mate, im having the exact same problem as you...did you manage to fix it?
i have found the same ruu for my radio version but it gets stuck on the bootloader as the bar moves but the fone stays on the same screen.
do u think i need to make that goldchip card? how do i make one please?

i had that same problem just 2 days ago so in order to get the ruu to flash right it has to be a radio thats higher than the one you already have ... but if that dosnt work you will have to change it manualy using adb in recovery mode so wat you do is power offf the phone comptley and plug it in your computer via usb then open up adb and type adb devices the phone has to be off and it should show your device id then the word recvery next to it then your gunna wanna pull the misc.img from the phone and edit it with a hex editor i did this method to downgrade my g2 kus my sdcard dosnt read but after you change the misc the ruu shuld flash fine 1.power off phone Connect phone to computer,
2.Open adb cmd and type : adb shell
3.Type su
4. if you get # symbol continue
5.Type : dd if=/dev/block/mmcblk0p24 of=/sdcard/misc.img (YOU CAN COPY THE IMG TO EITHER sdcard, which is internal memory, or sdcard2, which is removal card)
6. Switch to USB mode
7.copy misc.img from the root of the sdcard to your computer
8.Open misc.img with HeX Editor XVI32
9.Find the version and change it. it will be the first area in the the upper right in the screen of the app
10.change the number in whatever you want. (has to be in the form of.. 1.00.000.0
11.Save it and upload it to the root of the sdcard with miscnew.img name
12. Switch to charge mode
13.Type adb shell, su dd if=/sdcard/misc.img of=/dev/block/mmcblk0p24
14.Reboot to fastboot then fastboot reboot to RUU then fastboot flash PC10IMG.zip and it shuld flash fine
---------- Post added at 11:42 PM ---------- Previous post was at 11:37 PM ----------
or yu can try this http://forum.xda-developers.com/showthread.php?t=1526316 and should work its alot easier than the adb method

Never managed to fix this (tried the exact same thing ari3z suggested, but ages ago) - just kept freezing when trying to write anything to flash.
Phone was eventually swapped out in warranty.

[Q] HTC Wildfire Buzz: stuck and doesnt accept custom roms or RUUs

Hi,
I have HTC Wildfire Buzz which had a problem getting stucking at HTC logo and kept rebooting. I decided to unlock the bootloader and flash a custom rom, I downloaded CWM recovery and tried flashing a custom rom but got an error and then I tried flashing different variations of CM roms such as update-cm-7.1.0.1-buzz-signed.zip and cm_buzz_full-256.zip but I got different types of errors including Err 7.
The other custom rom I tried to install was Android_Freedom_Wildfire_By_MONI69_a2sd but I kept getting the following error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
I tried running different relevant RUUs based on my phone region but always ended up with error due to the fact that the firmware version currently installed is 2.46.0.0 and all the RUUs have versions lower than it.
I would appreciate providing me with your guidance and advice, my phone info is provided below.
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: SH13TPY12305
INFOimei: xxxxxxxxxxxxxx
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4211mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0

yabdali said:
Hi,
I have HTC Wildfire Buzz which had a problem getting stucking at HTC logo and kept rebooting. I decided to unlock the bootloader and flash a custom rom, I downloaded CWM recovery and tried flashing a custom rom but got an error and then I tried flashing different variations of CM roms such as update-cm-7.1.0.1-buzz-signed.zip and cm_buzz_full-256.zip but I got different types of errors including Err 7.
The other custom rom I tried to install was Android_Freedom_Wildfire_By_MONI69_a2sd but I kept getting the following error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
I tried running different relevant RUUs based on my phone region but always ended up with error due to the fact that the firmware version currently installed is 2.46.0.0 and all the RUUs have versions lower than it.
I would appreciate providing me with your guidance and advice, my phone info is provided below.
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: SH13TPY12305
INFOimei: xxxxxxxxxxxxxx
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4211mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Click to expand...
Click to collapse
Hello dude...i have the same phone with exactly same specs n had d same prob
go to fastboot,connect usb
now u have a .img file in ur rom's zip.
extract it to fastboot folder
via cmd go to fastboot folder with ur ph connected.. type
fastboot flash boot xxx.img
it will take some time
nxt flash cwm if u dont hv it
then get a micro sd wid ur rom(unedited) and flash it via cwm...disable signature verification if needed
press d thanks button n voila u have ur nw rom

ontheflames said:
Hello dude...i have the same phone with exactly same specs n had d same prob
go to fastboot,connect usb
now u have a .img file in ur rom's zip.
extract it to fastboot folder
via cmd go to fastboot folder with ur ph connected.. type
fastboot flash boot xxx.img
it will take some time
nxt flash cwm if u dont hv it
then get a micro sd wid ur rom(unedited) and flash it via cwm...disable signature verification if needed
press d thanks button n voila u have ur nw rom
Click to expand...
Click to collapse
Hi, Thanks for your advice, unfortunately it didnt work! I tried the following:
Extracting the rom zip and flashing boot.img via fastboot then using CWM flashing the rom xxxx.zip.
update-cm-7.1.0.1-buzz-signed.zip error:
assert failedackage_extract_file("boot.img","/tmp/boot.img")
E:error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 7)
Installation aborted
Android_Freedom_Wildfire_By_MONI69 error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
Hope this gives further insights about the problem, any suggestion advise would be highly appreciated.

hey man, silly question but are you sure you are doing a full factory wipe, data wipe cache wipe and dalvick cache wipe?
you should do the wipes every time you try to flash a new rom.

heavy_metal_man said:
hey man, silly question but are you sure you are doing a full factory wipe, data wipe cache wipe and dalvick cache wipe?
you should do the wipes every time you try to flash a new rom.
Click to expand...
Click to collapse
Yes, I use CWM to do factory reset, cache, dalvick wipes everytime I flash a rom!

yabdali said:
Hi, Thanks for your advice, unfortunately it didnt work! I tried the following:
Extracting the rom zip and flashing boot.img via fastboot then using CWM flashing the rom xxxx.zip.
update-cm-7.1.0.1-buzz-signed.zip error:
assert failedackage_extract_file("boot.img","/tmp/boot.img")
E:error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 7)
Installation aborted
Android_Freedom_Wildfire_By_MONI69 error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
Hope this gives further insights about the problem, any suggestion advise would be highly appreciated.
Click to expand...
Click to collapse
Another alternative is formating all partitions before flashing..
and btw did u extract the whole zip for boot.img?
what is ur cwm version?
did u try disabling signature check and script asserts??

ontheflames said:
Another alternative is formating all partitions before flashing..
and btw did u extract the whole zip for boot.img?
what is ur cwm version?
did u try disabling signature check and string asserts??
Click to expand...
Click to collapse
Hi, thanks for your continous support, I tried the following but not matter what rom I flashed I still get some sort of an error. As for your question regarding the boot.img, yes I extracted the xxxx.zip flashed boot.img via fastboot pulled the batter started CWM and installed the original xxxx.zip. I tried the partiations formatting, below are the details.
ClockworkMod Recovery v2.5.0.7
Green color
wipe data/factory
wip cache
wipe delivak (E: can't mount /dev/block.mmcblk0p2)
format system
format boot
format data
format cache
toggle script asserts/signature (disabled)
Rom: cm-buzz_full-256.zip
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/cm-buzz_full-256.zip
(Status 7)
Installation aborted.
Rom: update-cm-7.1.0.1-buzz-signed.zip
E:Error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 0)
Installation aborted
I also get package_extract_file("boot.img","/tmp/boot.img") error in some other roms.

yabdali said:
Hi, thanks for your continous support, I tried the following but not matter what rom I flashed I still get some sort of an error. As for your question regarding the boot.img, yes I extracted the xxxx.zip flashed boot.img via fastboot pulled the batter started CWM and installed the original xxxx.zip. I tried the partiations formatting, below are the details.
ClockworkMod Recovery v2.5.0.7
Green color
wipe data/factory
wip cache
wipe delivak (E: can't mount /dev/block.mmcblk0p2)
format system
format boot
format data
format cache
toggle script asserts/signature (disabled)
Rom: cm-buzz_full-256.zip
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/cm-buzz_full-256.zip
(Status 7)
Installation aborted.
Rom: update-cm-7.1.0.1-buzz-signed.zip
E:Error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 0)
Installation aborted
I also get package_extract_file("boot.img","/tmp/boot.img") error in some other roms.
Click to expand...
Click to collapse
Strange...btw how did ur wf stop booting all of a sudden? I think u have failed to get proper root and unlocked bootloader
pl verify it in hboot..on top it must display 'UNLOCKED'
more when u comment
Hit thanks if i helped u

ontheflames said:
Strange...btw how did ur wf stop booting all of a sudden? I think u have failed to get proper root and unlocked bootloader
pl verify it in hboot..on top it must display 'UNLOCKED'
more when u comment
Hit thanks if i helped u
Click to expand...
Click to collapse
Its my wife's phone. Out of the blue started getting stuck in HTC logo and kept rebooting. Yes, its unlocked using HTCDEV and it shows that in hboot "UNLOCKED".
Appreciate your further feedback..

I'd first try a different sd card, it looks to me like it's not reading properly with some of those errors, mount /system from Cwm mounts and storage option before wiping and flashing the new rom too, if that fails try fastboot flashing Cwm 5.0.2.0, then try again. I've never seen this problem before so my apologies if I'm way off the mark.
Sent from my HTC Wildfire using xda premium

i have the same problem here.
hboot 1.02.0000 - won't downgrade for anything in the world
s-on
in cwm i cannot install any rom. says "status 0 installation aborted" or "bad"
the ruu's are not working either.
i don't have a backup or a rom installed. if there's anyone who can provide me a buzz backup so i can restore into my phone, i would much appreciate it. i think is the single thing i didn't try.

seagerfreak said:
i have the same problem here.
hboot 1.02.0000 - won't downgrade for anything in the world
s-on
in cwm i cannot install any rom. says "status 0 installation aborted" or "bad"
the ruu's are not working either.
i don't have a backup or a rom installed. if there's anyone who can provide me a buzz backup so i can restore into my phone, i would much appreciate it. i think is the single thing i didn't try.
Click to expand...
Click to collapse
It already has been mentioned a few times here in the forum: htcdev won't give you s-off and it's not absolutely clear (= not confirmed) that can get s-off after the htcdev unlock (because you can't downgrade the HBOOT).
I have no idea if there's a possibility but it doesn't look good - there are 2 other threads regarding this issue here in Q&A or General section - you might want to have a look.
For the install problem I'm pretty sure that's something different as you usually should be able to install a ROM...

i have looked into othet threads. nothing works

seagerfreak said:
i have looked into othet threads. nothing works
Click to expand...
Click to collapse
You need to relock your boot loader for an ruu to work. relock the bootloader and remove the rom.zip from the htcdev bootloader unlock ruu. Remember an ruu with a lower hboot will not run. Rename it to pc49img.zip and put it on the root of your sdcard. Boot to hboot and allow the bootloader to flash the rom. but if I was you I would just try to get access to an xtc clip and fully s-off the phone. Then it will run any ruu and custom rom.
Sent from my HTC Sensation using xda premium

heavy_metal_man said:
You need to relock your boot loader for an ruu to work. relock the bootloader and remove the rom.zip from the htcdev bootloader unlock ruu. Remember an ruu with a lower hboot will not run. Rename it to pc49img.zip and put it on the root of your sdcard. Boot to hboot and allow the bootloader to flash the rom. but if I was you I would just try to get access to an xtc clip and fully s-off the phone. Then it will run any ruu and custom rom.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
thanx for the answer. i have relocked my bootloader. renamed the rom and put it on the root of the sdcard. the hboot shows a loading bar, but after loading, nothing happens. the part with the removing the rom.zip from the htcdev bootloader unlock ruu i didn't understand. can you be more specific? thanx
quick edit: when running a ruu, it gives me usb connection error

Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(i faintly remember what this was, sorry )
Type fastboot flash 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
Edit: Hey sorry didnt read my earlier posts, after all wf is slow on internet.
However this is the problem where u you are flashing incorrect boot.img
Make sure its from your rom, or try using the one in cm7, try both as Im not exactly certain. If u have cwm it asserts that u have root and you can flash roms.

ontheflames said:
Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(i faintly remember what this was, sorry )
Type fastboot flash 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
Edit: Hey sorry didnt read my earlier posts, after all wf is slow on internet.
However this is the problem where u you are flashing incorrect boot.img
Make sure its from your rom, or try using the one in cm7, try both as Im not exactly certain. If u have cwm it asserts that u have root and you can flash roms.
Click to expand...
Click to collapse
i made every step you told me to. this is what i get.
the only way i can make the phone visible in adb, is in recovery. being unable to boot a rom, i cannot set the usb debugging mode. so, everything that i will make, is via fastboot or ruu. but ruu gives me usb connection error or error [155] in fastboot, and baterry < 30% in adb mode.

What if you unlock your bootloader again and flash a recovery.img from fastboot? Maybe there is problem with your cwm recovery. I guess you have already tried formatting you sd card, tried a different sd card and tried different custom roms.
I would definitely try to get some more charge in your phone first because if you loose power while flashing it could end up really bad. An RUU won't install on low battery (i thought you needed >70%) what if you charge up and run ruu from adb again?

Rename your CID to HTC_001 (fastboot writecid HTC__001). Relock your bootloader using fastboot oem lock. Run a WWE RUU. Use the rooting link in my sig.
Done, and don't ever root with HTCDev again.

hans moleman said:
What if you unlock your bootloader again and flash a recovery.img from fastboot? Maybe there is problem with your cwm recovery. I guess you have already tried formatting you sd card, tried a different sd card and tried different custom roms.
I would definitely try to get some more charge in your phone first because if you loose power while flashing it could end up really bad. An RUU won't install on low battery (i thought you needed >70%) what if you charge up and run ruu from adb again?
Click to expand...
Click to collapse
i tried every possible combination of cwms and roms.
usaff22 said:
Rename your CID to HTC_001 (fastboot writecid HTC__001). Relock your bootloader using fastboot oem lock. Run a WWE RUU. Use the rooting link in my sig.
Done, and don't ever root with HTCDev again.
Click to expand...
Click to collapse
i get this error
C:\android sdk\platform-tools>fastboot oem writecid HTC__001
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
C:\android sdk\platform-tools>
Click to expand...
Click to collapse
just to be clear, the phone was in this state, it's not mine. i am only trying to put whatever rom i can so i can make it work

Bricked phone after rooting with AAHK? Stuck at white HTC screen

Here is my phone detail:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Here is what I did:
Root with AAHK after that it reboot and stuck at white HTC screen
I boot the phone into booloader and make a factory reset, but it still stuck
I format my sdcard by a Nokia N8
Retried the first 2 steps, but still the same
Here is what I tried to do
I boot the phone into bootloader and go into fastboot, then run the correct RUU version (I see the same software version). However, it said customer error id #131. I use the this file RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed
I boot the phone into bootloader and go into fastboot, and do these step below, but it said something about "signature verification fail".
1) Download recovery above and place it in your fastboot directory
2) Boot into Hboot
3) Connect your phone to your PC
4) Select fastboot
5) Open up command prompt and CD to your Fastboot directory
6) Run the command fastboot erase cache
7) After the OK run fastboot oem rebootRUU
8) You'll see a new screen with HTC logo and a progress bar. here you need to run fastboot flash zip PD98IMG.zip
9) Once it completes (should say ok,finished, or complete) run fastboot reboot bootloader
10) Go into Recovery and flash a rom
Click to expand...
Click to collapse
Any suggestion to help me unbrick? I read somewhere about customer error id and it is related to goldcard. I am trying to borrow a card reader to do that.

cruel91 said:
Here is my phone detail:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Here is what I did:
Root with AAHK after that it reboot and stuck at white HTC screen
I boot the phone into booloader and make a factory reset, but it still stuck
I format my sdcard by a Nokia N8
Retried the first 2 steps, but still the same
Here is what I tried to do
I boot the phone into bootloader and go into fastboot, then run the correct RUU version (I see the same software version). However, it said customer error id #131. I use the this file RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed
I boot the phone into bootloader and go into fastboot, and do these step below, but it said something about "signature verification fail".
Any suggestion to help me unbrick? I read somewhere about customer error id and it is related to goldcard. I am trying to borrow a card reader to do that.
Click to expand...
Click to collapse
AAHK would have created your goldcard for you its one of the options when running, also AAHK needs to run twice, and during said runs attend to any errors or requests it makes.

[Q] HTC One X bricked!

Hi there,
So I decided to be a moron and go ahead and "UNROOT" my HTC One X. What ended up happening is I got my phone stuck in a bootloader loop.
now I can't even flash the bootloader, when I type "adb shell" I get: "error: device not found".
What the bootloader looks like:
*** RELOCKED ***
ENDEAVORU PVTSHIP S-ON RL
HBOOT-1.39.0000
CPLD-NONE
MICROP-NONE
RADIO-5.1204.162A.29
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot: enabled
MODEM PATH: OFF
Dec 17 2012, 13:59:37
Thanks in advance.

Saw in another thread he asked for the outcome of this:
fastboot getvar version-main
version-main: 3.20.401.1
finished. total time: 0.066s

Unlock the bootloader and restore the nandroid backup, wich is mandatory before rooting and tinkering

Mr Hofs said:
Unlock the bootloader and restore the nandroid backup, wich is mandatory before rooting and tinkering
Click to expand...
Click to collapse
Thanks for your time to reply but that's the problem, I can't unlock the bootloader / restore the nandroid backup because I have literally no OS on it, when I try to do anything fastboot it just tells me that the device is not found. I've been trying to figure this out for some hours

Rogueaholic said:
Thanks for your time to reply but that's the problem, I can't unlock the bootloader / restore the nandroid backup because I have literally no OS on it, when I try to do anything fastboot it just tells me that the device is not found. I've been trying to figure this out for some hours
Click to expand...
Click to collapse
Well, alright. So I've unlocked it again but I have absolutely no data on it, (When I go into "Install zip from sdcard" it says "No files found."
Anyone got an idea what to do?
Oh and I'm using CWM, Recovery v5.8.3.1

Flash a new recovery first. Yours doesn't support usb mass storage to copy a rom to the sdcard in the recovery
http://db.tt/SPXdFfPw
This one does.

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