Develop Bugs

[Q] Desire Bricked?

Hey Guys,
Right I've been up all night trying to fix this but now I'm at the stage where I need your wisdom!
Problem:
Got a rooted, s-off'd HTC desire (originally on 3 UK running a 3 branded rom, rooted via goldcard method)
It was running Redux and the hboot I was using was CM7. I decided to change back to Oxygen, and proceeded to flash the Oxygen Hboot. I also flashed the latest version of Clockwork Mod Recovery. All was done through terminal in ubuntu using fastboot. I also erased cache, system and boot, before rebooting into recovery and flashing Oxygen. Seemed to install fine so I rebooted into Oxygen and it loaded up. During the setup process my phone informed me that it couldn't find a SIM card. Rebooted into recovery and wiped everything (including dalvik) and still the same problem persisted.
It was at this time I found out that I couldn't mount my SD card either (either in Oxygen or in recovery).
Followed the usb-brick-rickrolled-b0rked-fixed method to resolve the SD card problem.
I used the OP's zip file attached, missed out step 1 and carried on from step 2 (used my Blackberry to get the update file on the SD card).
Anyway it all seemed fixed and Oxygen was booting up fine, sim card was being read, but I found that most of the time my laptop would not discover my phone when attached in storage mode.
Then I decided to start from scratch and restore my desire to a stock htc rom. After preparing my goldcard and getting the RUU I ran the update. The ROM I installed was: RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.0 6.00.02_2_release_127568_signed.exe
(I tried installing a stock froyo RUU before that one and I couldn't. It came up with an error that said invalid vendor ID or something similar)
The restore seemed to go fine until the update utility told me everything was done and rebooted my phone. End result was that the phone's LCD is now not working at all. I've checked the back of my phone's box and all that is written in there is:
Display - 3.7-inch touch-sensitive screen.
The phone boots (it's making all the noises etc). I can get it into fastboot as well and get fastboot oem bootloader info etc. But ADB is not working and I've got a feeling the wrong RUU has been flashed hence screen death.
To make things worse, when I plug the desire into my laptop (with a fresh install of htc sync to flash new rom etc) device manager sees it as: qualcomm cdma technologies msm.
It won't recogize it as a htc desire at all. Tried a different laptop with new htc sync install etc but still the same issue.
Spent like 5/6 hours last night trying to figure this out but now I'm stuck.
Seems like the only access I have to the phone is via fastboot. Is there anything I can do to recover this phone?
Any help would be appreciated.

http://forum.xda-developers.com/showthread.php?t=768256
Try this.. in that thread go to post 2 .. their is section Recovery from broken screen

jhonybravo4u said:
http://forum.xda-developers.com/showthread.php?t=768256
Try this.. in that thread go to post 2 .. their is section Recovery from broken screen
Click to expand...
Click to collapse
had a look at that, however thing is I can't access adb at all..and i got a feeling my goldcard didn't work so I can't create a new one as i cannot find out the CID..
The only thing I can do is use fastboot to reboot into rebootRUU and try to flash the ROM manually. It keeps failing and giving the following error:
c:\android-sdk-windows\tools>fastboot flash zip rom.zip
sending 'zip' (164913 KB)...
OKAY [ 29.190s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 58.717s
Tried flashing a h3G rom and it flashes but still no screen...I can only find two h3g roms. anyone come across any other [uk] three network RUU?

Fixed!!!!
After much google searching/reading over here at XDA and modaco I finally figured it out
1) Made a new gold card, flashed a froyo RUU via fastboot which brought the SLCD back to life and gave me a working froyo unrooted rom (still with no adb/usb access)
2) Created a new misc partition img file using various guides available.
3) Used quanchi's guide to use rageagainstthecage exploit, to allow the misc partition to be flashed.
Laptop is correctly recognizing the desire now

Quitly Brilliant .. ;-) I guess 1st thing you need to do is create a goldcard while your mobile is working

Desire frozen on htc screen

Hello everyone,
I have a problem with my HTC desire.
I was running Leedroid for more than 6 months and everything was fine.
Yesterday morning, my phone went battery-dead and then when I started it plugin-in to the power socket it turned on and got stuck at the HTC screen.
I can enter bootloader (I guess ?) by pressing power + back but then I don't know what to do (I have a white screen with several menus I can browse with vol up/down) ?
I also tried going with a RUU (RUU MoDaCo Version: 1.15.405.4) and it does detect my phone but won't finish.
Is there anything I can do ?
Geeum

Geeum said:
Hello everyone,
I have a problem with my HTC desire.
I was running Leedroid for more than 6 months and everything was fine.
Yesterday morning, my phone went battery-dead and then when I started it plugin-in to the power socket it turned on and got stuck at the HTC screen.
I can enter bootloader (I guess ?) by pressing power + back but then I don't know what to do (I have a white screen with several menus I can browse with vol up/down) ?
I also tried going with a RUU (RUU MoDaCo Version: 1.15.405.4) and it does detect my phone but won't finish.
Is there anything I can do ?
Geeum
Click to expand...
Click to collapse
Why won't it finish?

No idea, it doesn't say.
I believe my phone is soft bricked, I can access hboot and fastbood so i'm pretty sure I can do something about it.
I read something about a unbrick thing you could launch from fastboot ? But can't find it.
Geeum

Try to flash this ruu:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
Boot phone in fastboot mode and follow instructions on the screen. Does it give you any errors?

Everything goes well, it does the sending part then gets stuck at signature update:
ERROR [132]: SIGNATURE ERROR
The ROM Update Utility cannot update your Android Phone.
Please get the correct ROM Update Utility and try again.
Click 'Exit' to quit.
Geeum

FYI I tried to create a gold card but adb devices doesn't return anything so I don't know if I can create a goldcard.
fastbood devices does return something though.

Geeum said:
FYI I tried to create a gold card but adb devices doesn't return anything so I don't know if I can create a goldcard.
fastbood devices does return something though.
Click to expand...
Click to collapse
Adb will run only if adb debugging is allowed, so Booted state or recovery state. In fastboot mode, only Fastboot will run. Have you overwritten recovery yet? If not, you flash another rom. If yes, are you S-Off? If so, you can flash an Hboot/recovery in Fastboot mode

droidzone said:
Have you overwritten recovery yet?
Click to expand...
Click to collapse
I think I did. I downloaded ClockworkMod Recovery and put it in my tools folder then typed 'fastboot flash recovery /path/to/<recovery>.img':
C:\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork-2.5.1.8-bravo.img
sending 'recovery' (3412 KB)...
OKAY [ 0.563s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.922s
droidzone said:
If not, you flash another rom.
Click to expand...
Click to collapse
How ? I tried to put another ROM at the root of my sdcard but not sure how to go from then on. Here is whet I tried, with leedroid v2.5:
C:\android-sdk-windows\tools>fastboot update leedroid.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
droidzone said:
If yes, are you S-On?
Click to expand...
Click to collapse
Don't know what S-On means ?
droidzone said:
If so, you can flash an Hboot/recovery in Fastboot mode
Click to expand...
Click to collapse
Can you tell me more ?
Thanks for your help it's greatly appreciated.
Geeum

Geeum said:
I think I did. I downloaded ClockworkMod Recovery and put it in my tools folder then typed 'fastboot flash recovery /path/to/<recovery>.img':
C:\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork-2.5.1.8-bravo.img
sending 'recovery' (3412 KB)...
OKAY [ 0.563s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.922s
How ? I tried to put another ROM at the root of my sdcard but not sure how to go from then on. Here is whet I tried, with leedroid v2.5:
C:\android-sdk-windows\tools>fastboot update leedroid.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Don't know what S-On means ?
Can you tell me more ?
Thanks for your help it's greatly appreciated.
Geeum
Click to expand...
Click to collapse
You cant flash custom roms from fastboot
You can flash recovery, and each of the .img files included in the Clockworkmod backup folder, but only if you're S-off. Apparently you're S-On (Security on. For S-off, Alpharev should have been used)..
Were you foresighted enough to make a gold card? If you hadnt, you have to find the RUU you successfully flashed last, or the RUU corresponding to the region of your device and brand.
You can read more on two of the threads I started. Click on my userid, and choose "Threads started by DZ". Look for "How to unbrick an SLCD Desire (which works for AMOLED too)" and "How to unroot" both of which should give you a comprehensive idea of how to approach your problem. Any queries pertaining to those threads can be asked there, or after reading it, here.

droidzone said:
You can read more on two of the threads I started. Click on my userid, and choose "Threads started by DZ". Look for "How to unbrick an SLCD Desire (which works for AMOLED too)" and "How to unroot" both of which should give you a comprehensive idea of how to approach your problem. Any queries pertaining to those threads can be asked there, or after reading it, here.
Click to expand...
Click to collapse
I tried, but when I click on your name I can only click on "Find all posts by droidzone" and there are 40 pages of them
Can you maybe send me the link to the posts you mention ?
Geeum
[edit] found the how to unroot one, reading it now. (http://forum.xda-developers.com/showthread.php?t=880268)
[edit 2] found the 2nd one: http://forum.xda-developers.com/showthread.php?t=831734

Geeum said:
I tried, but when I click on your name I can only click on "Find all posts by droidzone" and there are 40 pages of them
Can you maybe send me the link to the posts you mention ?
Geeum
[edit] found the how to unroot one, reading it now. (http://forum.xda-developers.com/showthread.php?t=880268)
Click to expand...
Click to collapse
Hmm.. You should learn your way around the forum!
But here they are:
http://forum.xda-developers.com/showthread.php?t=831734
http://forum.xda-developers.com/showthread.php?t=880268

I did find them in the end
I extracted the PB99IMG.zip and put in on my SDCARD but after loading and checking I get:
CID incorrect!
Update Fail !
I don't have a goldcard
I read on your posts that I can take my sdcard to another DESIRE phone and make it a goldcard so I'll try that tomorrow.
Any other idea ?
Geeum

Geeum said:
I did find them in the end
I extracted the PB99IMG.zip and put in on my SDCARD but after loading and checking I get:
CID incorrect!
Update Fail !
I don't have a goldcard
I read on your posts that I can take my sdcard to another DESIRE phone and make it a goldcard so I'll try that tomorrow.
Any other idea ?
Geeum
Click to expand...
Click to collapse
Making a goldcard is the solution. And you can get the CID from any Android phone.

You definitely need to create a gold card. To create a goldcard see this: http://www.nazriawang.com/2010/04/ho...th-ubuntu.html
It is in unbutu, but maybe you can sort it out. Have a look.

OK I now have a goldcard: took a friends phone (same phone, same carrier) and put my sdcard in there and used modaco's tool.
Now the next step is to install a valid RUU for my region, right ?
If I do so it seems to go past the last error but gets stuck at
ERROR [140]: BOOTLOADER VERSION ERROR
Thanks

Hello ! I tried using a different RUU (the one suggested bu MatDroid: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed) and it has -almost- worked !
The update went until the end but now my phone boots and reboots after a couple of seconds (not fixed: sometimes I can go to unlock my simcard, sometimes a bit longer ...)
I'm getting desperate everytime I think I'm making advance there something new.

Now what ? I'm gone back to the original state: frozen on HTC screen
I tried re-running the RUU (this time the latest I could find: RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe)
Everything goes well, it says it is successful but then it reboots and gets stuck with HTC screen

Hey guys, went to the bootloader and erased all data. This time for some reason it rebooted fine and now the phone seems to be working.
Now I would like to have some advice:
- What can I do so in the future I have all I need for recovering ?
- I already have a goldcard
- what about the recovery ? Should I install something ?
- I liked leedroid, so thinking of going back to 2.5 what do you think?
Thanks for your help you re the best !
EDIT: well I thought it was working but here I am again. Reboot after reboot. This time the first one happened after 15 solid minutes and now it reboots every 30 seconds I barely have the time to enter my pincode ...

Anyone has an idea ?
I've found a way to stabilize my phone, which is by not putting my SIMcard in, but not sure how long it's gonna take before the next reboot.
I don't know what to do. Was thinking in downgrading using teppic74 tool but everytime I download it I get an error: corrupted file.
Can't see the end of it.

Guys, in the end I re-did the whole process: use RUU then delite data in the recovery and it seems to work.
I guess those RUU don't always work fine the first time.
Thanks to you all for your help

[Q] Stuck on S-Off Screen

Hi, i've been using LeeDroid for a few months now and all has been well, however yesterday my Desire turned itself off and now won't come back on. Each time i try and power it up it freezes at the Alpharev S-Off screen. I went into the menu's with volume down + power, but i can't get into my recovery - it takes me to the same frozen screen as does trying to reboot etc. And i don't think it's being recognized by usb either. So i really don't know what to do now.. is my phone bricked? I was a complete noob before rooting and flashing a custom rom before, so now that i've hit a problem i'm clueless all over again. Any help would be greatly appreciated

can you use fastboot? If so just flash a new recovery and all should be fine... chill out it can be fixed

What would i need for that? That's going into new territory

j3nni said:
What would i need for that? That's going into new territory
Click to expand...
Click to collapse
Can you access recovery? If no can you access bootloader (vol down + power on)

I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use

j3nni said:
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
Click to expand...
Click to collapse
Use amon_RA ... Download and flash onto ur phone and ur phone should be fixed
Plenty of guides around man, good way of learning fastboot

to use fastboot you need to download several things. Instead of using fastboot with cmd, I'd just recommend using fastboot commander, which does the job for you. In order to use that however, you will need the adb drivers, and Java SDK.
Once you've got all that, simply boot into fastboot, run "fastboot commander.exe", go into the "misc" tab, wipe Recovery, system, cache, boot, and userdata. Once you've done that download recovery, navigate to the "Hboot, radio & Rec" tab on fastboot commander, select recovery, find the recovery.img you just downloaded, and flash it. Once you've done that just boot into recovery and install any ROM you want.

Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again

j3nni said:
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
Click to expand...
Click to collapse
try do a full wipe of everything like I've mentioned before and then a different HBOOT

Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93

j3nni said:
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
Click to expand...
Click to collapse
www.alpharev.nl download a HBOOT and flash it through fastboot. Just make sure to check MD5 (you need a MD5 utility AFAIK)

I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!

j3nni said:
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
Click to expand...
Click to collapse
For any sense UI ROMs you would use the Sense HBOOT, remember to nandroid backup before you do so! because you might find that you get a bootloop after flashing the HBOOT.
And don't worry about asking questions! it's what we're all here for.
By the way if you don't know what different HBOOTs do: they change the partition sizes for /system /cache and /data. So by using a different HBOOT instead of the stock one you may get more storage for apps etc. if you choose one with a larger /data partition.... if that makes sense

Ok the sense one it is =)
Ah i see! Thanks for explaining cos underneath the nerd in me would have been wondering what it did lol.
Not sure how to get a nandroid done when i can't get into recovery though

I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further

j3nni said:
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
Click to expand...
Click to collapse
Hi.
As I can see the only way to restore is using a RUU to go back to stock then root and S-Off the phone again.
First: Preparation.
1. If you have a custom HBOOT (e.g.: 6.93.0001) you need first to flash the HBOOT Downgrader (found on alpharev site), then flash the RUU.
2. You will gonna need a Gold Card if your phone was branded.
Second: Starting
1. Make your Gold Card using someone's else phone (it has to be running Android) - the Gold Card is unique per SD Card, not per phone.
2. Use this tool to make the Gold Card: HERE
3. Guide how to make a Gold Card in Linux: HERE
4. get the latest RUU WWE 2.29.405.5. Extract the PB99IMG.zip file from the RUU: here it is how: http://forum.xda-developers.com/showthread.php?t=880268 -2nd post.
5. Reboot in bootloader (Volume-Down + Power)
7. Select fastboot
8. Flash the HBOOT Downgrader (don't forget to check the MD5 of the file you have downloaded from alpharev)
9. Extract the PB99IMG.zip and put it on root of SD Card.
10. Reboot in bootloader (scroll to REBOOT and select)
11. It will automatically load the img and ask you if you want to install
12. Check Yes and follow onscreen progress.
13. Wait untill it finnishes
14. I think it will reboot itself, if not scroll down to the Reboot obtion and press Power button to select.
IMPORTANT WARNING!!!
droidzone said:
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
Click to expand...
Click to collapse

Or if you want to go to stock and it is an unbranded phone you can just run ur ruu when the phone is in fastboot
Sent from my HTC Desire using XDA App

Think i may be the happiest girl in the world today lol i finally got it all fixed. I had a bit of trouble making the goldcard as at first my sd card kept saying it needed to be reformatted after, but after formatting it with SD Formatter program rather than Vista's own, it worked. All the rest went without a hitch. Now just gotta root, s-off and grab my new ROM and this past week can all get forgotten about =)
Thankyou so much to everyone that helped!
Incase anyone does read this far, is the procedure still the same as when i first used it back in April.. from here? http://forum.xda-developers.com/showthread.php?t=1016084

It is still the same.

If you like sense -
http://forum.xda-developers.com/showthread.php?t=1054435
░█░ [ROM][28/06] ✰.Reflex S v2.1.7 Gingerbread 2.3.3· ░█░ · |SenseGingerB 2.1+3.0|
You might like it...

[Q] Flashed EU HOX with AT&T stuff and BRICKED! Please help

I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)

If you have CWM did you made a nondroid backup?

Bright.Light said:
I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)
Click to expand...
Click to collapse
THIS will help you

@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)

Bright.Light said:
@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)
Click to expand...
Click to collapse
Yup.It is actualy quite simple,i always do a backup before i flash something or update my ROM and other stuff.You keep the volume down + power button.After that you enter recovery mode (you will need to have CWM) and you have an option there "backup and restore",enter there and make a backup.Next time if you have any problems just enter again in the CWM,go to "backup and restore" and restore the backup you've made.It saves everything you have (i mean the ROM setting and such.Apps and other stuff must be backed up with Titanium Backup).
The backups you made are saved in the SD card in the nandroid directory if i remember corectly,so if you update you're ROM to...1.29 for example and have a 1.28 backup just enter there and delete it and make a new backup of the 1.29 so you don't get confused in so many backups and if you ever have problems and restore a 1.28 backup on you'r 1.29..well...you realize that the phone isn't going to work anymore.So,be carefoul.

Didn't work... I downloaded this rom: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
did everything this page told us: http://forum.xda-developers.com/showthread.php?t=1609190
But I do not see anything change... It's still stuck in the boot process.
I don't know what I am doing wrong...
I also didn't find a clear guide for how to do things - it's all pieces which everyone has to put together, making it hard when there is a real problem.
If this can be solved, I will investigate the nand backup for certain!
For now I need my phone, but it does not work...
Oh - how does the charging with the new clockwork work? I don't see anything happen, so I am afraid the battery will be down soon.
edit: It was on power all night and when I looked it had the screen on. Unplugging and replugging and the gren light went on. Does that mean the battery is filled?
One important fact: the adb command cannot find the device and I don't know why!

How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system

EddyOS said:
How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system
Click to expand...
Click to collapse
with a LOCKED bootloader?
Mine is unlocked...
I will try to relock the boorloader (saw somewhere a snippet)

Tried with a locked one:
Code:
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot oem lock
... INFOLock successfully...
OKAY [ 0.143s]
finished. total time: 0.143s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash boot boot_signed.img
sending 'boot' (4288 KB)... OKAY [ 0.667s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.874s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash system system.img
sending 'system' (963584 KB)... FAILED (remote: (00000008))
finished. total time: -0.000s
The bootloader loocks relocked ok (as it shows on top of that screen)
But flashing is impossible and, of cause, I don't know why

Adb will work in recovery but only if you boot the recovery from fastboot.
Fastboot boot recovery recovery.img

ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?

Run .11 RUU, wait until load all completely, now go to %temp% in your pc and find a folder that contain a ROM.ZIP file... Unzip the files and flash the boot_signed.img and the recovery_signed.img, then relock your phone fastboot oem lock) do a factory reset (with the new recovery) and then try to run the .11 RUU.
THAT SHOULD WORK
pd: sorry for my poor english.
Sent from my HTC One X using XDA

Bright.Light said:
ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?
Click to expand...
Click to collapse
You haven't a clue have you?
You don't flash an RUU from CWM, it's a Windows application!
1. Boot phone into FASTBOOT
2. Connect to the PC
3. Lock the bootloader
4. Run the RUU
Job done

@wolfraim: Yes, the factory reset was the one culprit, it seems!
EddyOS: Tried that so many times, but finally wolfraim added a crucial point: Factory reset!
Now the RUU install from the PC is working... (Have to wait for some time ...)
* I have to go for now, right after the flash is done.
When I've got the time, I will try to make some more notes and maybe another step-by-step story on how to make the device work again.
Thank you very much for your patience and help!
This is why I love the xda-developers site so much!
(and all possible ways included on XDA to brick my device is the reason why I hate xda sometimes... )
edit: Flashing has succeeded! Software number: 1.29.401.11, so it seems I also have the latest ROM update now.
I'll make a recovery backup asap and will try the titanium backup too.
Oh, this one is SU-locked of cause, so I will have to install the SU zip file again... Much work is to be done yet. Maybe I should look for a good ROM in the Android development area.

[Q] [Help] Can't mount SD card, flash stock recovery, no RUU

Hey all, I'm looking for some help.
Here's the thing:
The problem started with what I think was a dying battery (2 yr old device) because I started to have some battery drain, screen frozen at short intervals at random times, insane heat... I was running AOSP at that time so I decided to go back to Sense to see if I could make it last a bit longer. Here's when things get strange: I flashed CWM 6.0.3.2 and then ViperX4.1.1 wuth Alex V 2 pa3 kernel. I did everything the same way I've done in the past two years, except this time after flashing the phone started to reboot itself out of the blue which made me think it was definitely the battery, but sometimes when it rebooted it wouldn't load everything, gave FC on some core apps (dialer, settings, etc) so I decided to wipe everything and reflash ROM and kernel. Stupid idea because things got worse and worse (gave FC on pretty much everything on first run, after reboot it wouldn't let me go past lockscreen, etc) and here I am today, a week later, still trying to fix this thing with no luck. I can boot to fastboot and go to recovery; I can't flash a ROM or restore a nandroid because CWM can't mount SD card I can't flash another recovery because it gives me an error and I can't flash a RUU because there's no RUU for 3.14.720.24, I cant' put anything in SD card from PC because large files keep on getting corrupted....
Really, I'm lost. Does anyone have any idea?

JuanArg said:
Hey all, I'm looking for some help.
Here's the thing:
The problem started with what I think was a dying battery (2 yr old device) because I started to have some battery drain, screen frozen at short intervals at random times, insane heat... I was running AOSP at that time so I decided to go back to Sense to see if I could make it last a bit longer. Here's when things get strange: I flashed CWM 6.0.3.2 and then ViperX4.1.1 wuth Alex V 2 pa3 kernel. I did everything the same way I've done in the past two years, except this time after flashing the phone started to reboot itself out of the blue which made me think it was definitely the battery, but sometimes when it rebooted it wouldn't load everything, gave FC on some core apps (dialer, settings, etc) so I decided to wipe everything and reflash ROM and kernel. Stupid idea because things got worse and worse (gave FC on pretty much everything on first run, after reboot it wouldn't let me go past lockscreen, etc) and here I am today, a week later, still trying to fix this thing with no luck. I can boot to fastboot and go to recovery; I can't flash a ROM or restore a nandroid because CWM can't mount SD card I can't flash another recovery because it gives me an error and I can't flash a RUU because there's no RUU for 3.14.720.24, I cant' put anything in SD card from PC because large files keep on getting corrupted....
Really, I'm lost. Does anyone have any idea?
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery and mount sd card only in this recovery this function work

Thanks a lot for you reply, I tried it but I got the following:
C:\fastboot>fastboot flash recovery philz_touch_5.15.9-endeavoru.img
sending 'recovery' (8198 KB)...
OKAY [ 1.109s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 7.896s
--EDIT: Now everytime I try to go to recovery the phone goes back to fastboot menu. What the hell...

JuanArg said:
Thanks a lot for you reply, I tried it but I got the following:
C:\fastboot>fastboot flash recovery philz_touch_5.15.9-endeavoru.img
sending 'recovery' (8198 KB)...
OKAY [ 1.109s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 7.896s
--EDIT: Now everytime I try to go to recovery the phone goes back to fastboot menu. What the hell...
Click to expand...
Click to collapse
are your bootloader is unlocked? And rename the gole name to recovery.img dont use so many symbols
EDIT: Now I read for your problem on other places and the solution is to try again and again to flash the recovery

OK, now this is starting to get pretty insane. I rebooted to bootloader to continue trying to flash a recovery and it shows ***LOCKED*** as if I had never unlocked it.
If I go to fastboot and try to flash it gives me a "not allowed" error when attempting to write recovery.
I'm starting to think that the battery failed and somehow shorted something in the mobo.

JuanArg said:
OK, now this is starting to get pretty insane. I rebooted to bootloader to continue trying to flash a recovery and it shows ***LOCKED*** as if I had never unlocked it.
If I go to fastboot and try to flash it gives me a "not allowed" error when attempting to write recovery.
I'm starting to think that the battery failed and somehow shorted something in the mobo.
Click to expand...
Click to collapse
just unlock your bootloader and flash the recovery

I would, but as soon as I rebooted it went back to UNLOCKED and back to post #3... I'm close to smash this thing against the wall. I'll keep trying to flash the recovery.

Phone got in APX mode. Bye bye HOX, it was fun.

JuanArg said:
Phone got in APX mode. Bye bye HOX, it was fun.
Click to expand...
Click to collapse
Exact same thing happened to me... Didn't even get to try lollipop :l

I had a similar problem last week, what I had to do was to unlock the bootloader, then I flashed TWRP recovery and I mounted the SD with MTP enabled. Nothing happened in the first 2 or 3 minutes, and I was getting insane until TWRP did the magic and the PC recognized my hox as a MTP device, I copied a rom and I flashed it with the recovery and everything is fine right now. I hope this is helpful for you

dario_pet said:
I had a similar problem last week, what I had to do was to unlock the bootloader, then I flashed TWRP recovery and I mounted the SD with MTP enabled. Nothing happened in the first 2 or 3 minutes, and I was getting insane until TWRP did the magic and the PC recognized my hox as a MTP device, I copied a rom and I flashed it with the recovery and everything is fine right now. I hope this is helpful for you
Click to expand...
Click to collapse
my problem is also same............
but in my hox twrp not working.. actually ..touch not working...
what to do......