Develop Bugs

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

Android noob needs help! Universal good karma for anyone who can help find a fix!

Fairly noobed to android so need a little help (teething) haha,
I've tried to install a custom rom for my one x unlocked boot loader and installed clockwork mod touch recovery, downloaded android revolution hd and moved wipe script and android revolution zip to sd card, flashed the boot.img and run wipe script no problem.
But when I go to install the zip file I get greeted with
finding update package>opening update package>installing update>installation aborted... then nothing. If I reboot the phone the phone stays in the htc quietly brilliant screen.
Please anyone! Help a fella out, crack this and I'll be forever in everyone debt. Thanks.
Con

ConorL said:
Fairly noobed to android so need a little help (teething) haha,
I've tried to install a custom rom for my one x unlocked boot loader and installed clockwork mod touch recovery, downloaded android revolution hd and moved wipe script and android revolution zip to sd card, flashed the boot.img and run wipe script no problem.
But when I go to install the zip file I get greeted with
finding update package>opening update package>installing update>installation aborted... then nothing. If I reboot the phone the phone stays in the htc quietly brilliant screen.
Please anyone! Help a fella out, crack this and I'll be forever in everyone debt. Thanks.
Con
Click to expand...
Click to collapse
Try to disable the signature check and see if you're able to install it.

Your Rom zip files is corrupted. You have to verify md5 value and then you have to flash.
Goto fastboot and just flash the stock kernel.
Sent from my HTC One X using Tapatalk 2

Tried disabling the signature check with no luck same thing happens..Do you know where could I get the stock kernel from? Thanks again for your patience it is greatly appreciated!

When i try to Flash the stock rom i get this message
sending 'flash' (9792 KB)... OKAY
writing 'flash'... FAILED (remote: not allowed)
xx-xxx-xx-22:bootloader connor$
anyone know what I'm doing wrong?? Thanks..

ConorL said:
When i try to Flash the stock rom i get this message
sending 'flash' (9792 KB)... OKAY
writing 'flash'... FAILED (remote: not allowed)
xx-xxx-xx-22:bootloader connor$
anyone know what I'm doing wrong?? Thanks..
Click to expand...
Click to collapse
Use the automated batch file in ARHD Thread. Like he said it might be a bad download. Re-downloaded it and test it again.

Tried downloading the stock kernel again and same story... How do I use the automated batch file you mentioned? thanks..

Are you trying to flash a .zip in fastboot? What file have you renamed 'flash'?

I haven't renamed any files flash I've just been trying to flash the .zip file...Its been a major fail so far, thanks for everyone patience..

ConorL said:
I haven't renamed any files flash I've just been trying to flash the .zip file...Its been a major fail so far, thanks for everyone patience..
Click to expand...
Click to collapse
Re-download the file to PC
Send file to sdcard
Remove usb cable from HOX
Try again
Hope it helps

I can't get back into the os to move the files over to the sd card, every time i reboot I get the htc quietly brilliant screen...

after i download the file should i rename anything to get it to flash properly from fastboot? I can't get back into the os so i'm in bootloader trying to fix it..Cheers

Go to Bootloader select Fastboot
Download http://www.androidrevolution.nl/downloader/download.php?file=Flash_boot_6.0.0.rar and extract it. Then run the batch file.
Then go into Recovery and your SD card will be automatically mounted to your PC in Recovery mode
So copy the ROM and flash it again.
Make sure you don't select any custom settings on the first boot.

It still looks like your trying to flash a .zip in fastboot.
---------- Post added at 01:05 PM ---------- Previous post was at 01:02 PM ----------
ConorL said:
When i try to Flash the stock rom i get this message
sending 'flash' (9792 KB)... OKAY
writing 'flash'... FAILED (remote: not allowed)
xx-xxx-xx-22:bootloader connor$
anyone know what I'm doing wrong?? Thanks..
Click to expand...
Click to collapse
This. ^^^
Sending 'flash'.
What command did you write to get this error. And what was the filename and extension. It would really help to know what you tried to flash.

I had the same issue on Wednesday where I ran the wipe script then tried to flash the rom and it turned out to be a corrupt download (failed to follow instructions to my peril).
To resolve all that was needed was to re-download the rom, mount the sdcard and copy it over and reattempt the flash. In my case I couldn't mount the sdcard at first, so if you are having issues here I solved it by updating recovery as per this thread "[RECOVERY] TeamWin Recovery Project (twrp) 2.1.7 [2012-06-04]"
under the "One X Android Development section"

To send files to your sd with no os, either install the new recovery that has usb support or use
Fastboot boot name.IMG (this is recovery IMG)
While booting from fastboot like that it allows adb to be used then Just push
adb push Rom.zip /sdcard
That will push the Rom to sd then just install as normal.
You will need the adb files easy enough to find on google.
Sent from my HTC One X using xda premium

i made a compilation thread about this, have a check... might help you out..
http://forum.xda-developers.com/showthread.php?t=1692681

Some assistance is requested

Hello there,
I'm slightly new to the forums, at least posting to them so if I'm in the wrong section or if I'm just not suppose to ask these questions... well... lend some expert advice and help me out!
I'm by no means an expert on rooting and flashing, pretty much every thing i have learned has been on my Optimus V, Nexus 7, and My latest device, HTC One V and i learned it all on these forums!
So my problem is... My HTC One V i have unlocked it and rooted it with a tool kit i found on here called "Hasoon2000's HTC One V All-In-One Kit" and all was well in the world. But now that i have rooted it I've grown bored with the device... after less than 24 hours of running stock rooted. And i've attempted to flash MIUI.us on my device as found on the developers website Now I've flashed many custom roms on my other devices, currently running Paranoid Android Beta 3 on my Nexus and Harmonia 2 (I believe) on my OV. But this phone has become quite the hassle. I'm running TWRP CDMA recovery and i Factory reset, wipe data, cache, dalvic (spelled correctly?) and it boots up to the MIUI boot logo then it goes to the usual Google start screen where you select language and set up your device... but... at that point it fails to do anything then boot loops back out and restarts the phone, and repeats... sometimes it won't even get out of the boot loop and it will just restart the phone... so i have used the RUU and reset the phone multiple times after this has occurred... If anyone could be of assistance or point me towards the correct forum it would be much appreciated!
I'm not totally sure what else could help anyone out there but it says S-OFF and i am unlocked and i have tried multiple roms and none of them have worked yet at all, the AOSP rom actually got to the home screen then restarted... this is getting quite frustrating and slightly irritating so if anyone could lend a helping hand I'd be much appreciative!

If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.

robaho said:
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
Click to expand...
Click to collapse
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV

the last OTA broke the Radio (-> v.0928) firmware
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
mkgarrod said:
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
Click to expand...
Click to collapse

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Okay so I just wanna make sure i understand all this... I'm basically doing the same thing that the RUU does? What does the RUU do outside of this? and i tried what you said and it never notices it and now when i boot up my phone it has no service and doesn't connect to the network....

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not

You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
mkgarrod said:
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
Click to expand...
Click to collapse

master_c said:
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
Click to expand...
Click to collapse
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..

You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
mkgarrod said:
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
Click to expand...
Click to collapse

master_c said:
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
Click to expand...
Click to collapse
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.

I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
mkgarrod said:
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
Click to expand...
Click to collapse

master_c said:
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
Click to expand...
Click to collapse
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?

It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
mkgarrod said:
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
Click to expand...
Click to collapse

master_c said:
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
Click to expand...
Click to collapse
Well as soon as i get back to my house I'm going to try this out and try reflashing the MIUI rom which is JB i believe and hope it works! if not... I'll be using that RUU tool again... I think i've been on that more than i have my new phone!

Why did no one report this thread? Obviously I'll see it eventually, but come on guys/gals!
Moved to Q&A.

HTC One M8s propably bricked HELP GUYS

Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language

Mikkal said:
Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language
Click to expand...
Click to collapse
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably this is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.

root-expert said:
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.
Click to expand...
Click to collapse
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies

Mikkal said:
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies
Click to expand...
Click to collapse
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.

root-expert said:
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.
Click to expand...
Click to collapse
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now

Similar situation
Hi,
I appear to be in a similar situation with my M8 that I tried to convert to GPE. Something went wrong and although the ROM booted, I kept getting told my data was corrupt or encrypted... Tried a few reboots, and refreshed but still got the same...
A thread on here suggested formatting one of the partitions from TWRP which just returned an error, since then the phone appears to be 'hard bricked'.
No display, no charging indication, not recognised in ADB, and I can't force boot into recovery or fast boot.
However, I do still get the notification sound when I plug it into my PC...
It appears in the Device Manager as Qualcomm Mass Storage Device, and Windows shows ~20 drives most of which are unformatted, a few of which seem to contain system info...
I was wondering, would it be possible to re-image the Device? Given that the PC recognises the partitions, would anyway know what -should- be on them?
Alternatively, can anyone provide an image of a stock drive, partitions etc which I could apply?
Apologies if this is nonsense, but I'd imagine the reason it can't boot is the Bootloader partition is 'missing' or corrupted.
The same may be true for your device Mikkal.
Thanks in advance,

Mikkal said:
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now
Click to expand...
Click to collapse
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?

funjai said:
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?
Click to expand...
Click to collapse
What is your CID , software version

No idea mate.. I can't turn on the phone so I can't check that..

For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!

LoneWolfO2Se said:
For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!
Click to expand...
Click to collapse
Oh really? You never noticed that there are no custom roms for M8S ?

funjai said:
Oh really? You never noticed that there are no custom roms for M8S ?
Click to expand...
Click to collapse
You sure about that ?

Hi can you paste info from your phone use this command in fasboot
fastboot getvar all
also tell me what software did you try to flash
Regards