Database Develop

[Q] cannot root: hboot 2.0 ver. 2.3.5

Hello community!!
I'm new to the HTC/Incredible S world, I have a rooted/cfw LG P500 and now I bought this great phone. Problem is that I updated it to the last official version before this try.
So I went to the official site and I followed successfully the HTC site steps to unlock the bootloader (golden card?) and now I'm trying to follow the guide
http://forum.xda-developers.com/showthread.php?t=1385084
But I have some problems.
First of all clearly the revolutionary program doesn't work (HBOOT 2.0).
I booted to the bootloader (power+volume down) and I had the error "main version is older" then I copied on the SD card the file for the recovery PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip, I renamed it PG32IMG.zip, it loads it but when I press recovery it gives me an allert icon (the phone with a red triangle + red "!" ) and it does nothing.
I installed the SuperUser app like it is written in the post but when I type SU under the adb shell and it gives me "permission denied".
What could I do?
Is it even possible to downgrade it to a rootable/customable version?

If someone write a guide for rooting with the last update installed from original s-on step to step will be very util and a lot of people will be gratefull!
Inviato dal mio HTC Desire usando Tapatalk

Bootloader unlock and goldcard are 2 seperate things. Bootloader unlock is required at the moment for flashing recovery and superuser for rooting the phone.
Gold card is required for flashing another carriers rom.
Read this thread about recovery http://forum.xda-developers.com/showthread.php?t=1104765
After that you can enter recovery mode and flash a superuser zip file http://goo-inside.me/superuser/
My guide should be able to downgrade your rom and get s-off after that (if after researching you decide you require it) http://forum.xda-developers.com/showthread.php?t=1373697
Hope this helps

Thanks, I'm going to try this as soon as I can, I'll write back the results
edit:
It seems like I can't even pass the first step, the 4EXT Recovery Updater doesn't work, it crushes at EVERY menu item....
(I waited 5+minutes and I had the internet connection on).
I checked and the boot loader says "unlocked". Notice that my device is, of course, NOT rooted (at least for what I know for "rooted", it is still unlocked by the HTC official method)....

you need root to use the recovery updater.
download the recovery image and flash it in fastboot

Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...

sariel82 said:
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
Click to expand...
Click to collapse
Could I get a couple of screenshots to help with debugging please?

Sure, ASAP

Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.

edit:
It seems I cannot post the images, too noob ....
Anyway:
I had a photo of the phone in the custom recovery mode, another of the phone with the 4EXT recovery successfully flashing his recovery, another of the script of your post running with this message:
(no errors)
Do you have an unlocked bootloader from htcdev.com (I have)
y OR n:y
<waiting for device>
...
(bootloader) Lock successfully..
FAILED (status read failed (Too many links))
finished. total time: 0.239s
Note: run the RUU in fastboot mode
If all steps etc etc
Now if I try to run RUU NOT in fastboot mode I receive the message:
The Utility of ROM udating can't update the Android device.
Take a valid ROM updating Utility and try again
(I'm translating from Italian)
If I try to go to fastboot after running the script I need to go to hboot using volume down+power since you can go to fastboot only through bootloader and HIS first step is to check the bootloader file (am I right?)
so, since it is again LOCKED the custom boot file I was using PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed
doesn't work anymore and the old one neither so I have to unlock it again and it goes the loop......
So this is the situation, I hope I will be able to post some image soon...

sergiopat said:
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
Click to expand...
Click to collapse
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.

sariel82 said:
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
Click to expand...
Click to collapse
OK, I thought you only wanted to root.

Thank you anyway

You don't need s-off for CFW's, just the unlocked bootloader. I cannot help you any further until I see screenshots as I'm getting lost in your descriptions. Ctrl prtscrn, paste in paint.

Well, I have the screenshots but I can't post web links in the forum (new user).
Let's see if I can flash some cfw in the mean time

Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)

sariel82 said:
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
Click to expand...
Click to collapse
After you flash a custom ROM in recovery, you have one last step to do to prevent the hang. You extract the boot.img file from the ROM's zip file and then manually flash it in FASTBOOT mode on the phone:
FASTBOOT flash boot [path to boot.img]

That totally solved the problem
Thank you ALL!!!

sariel82 said:
That totally solved the problem
Thank you ALL!!!
Click to expand...
Click to collapse
Hi,
Please list the methods you use from the start. I have also 2.3.5 and hboot 2.0. cant manage to downgrade, i always getting an error.
Thanks

htc developer site -> unlock bootloader
find and download this file:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio _20.2810.30.085AU_3805.06.03.16_M_release_199684_s igned.zip
copy it on the sd card and renamto to pg32IMG.zip
reboot in power+volume down mode
go in fastboot
from your pc use fastboot to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1104765
copy to sd card the superuser file:
http://goo-inside.me/superuser/
enter recovery mode and flash the zip
Then if u want to flash a custom rom you dont need to downgrade, just copy the zip into the sd card, flash it, copy on the sd card the boot.img you find inside the rom zip file and reboot in fastboot (power+volume down)
FASTBOOT flash boot [path to boot.img]
and reboot and the job is done!

[Q] Need help with a ROM

Hi,
So I decided to flash a ROM for the first time. Followed the steps from this:
http://forum.xda-developers.com/showthread.php?t=1337105
and got everything working with Cyanogenmod 7.1.
Whilst browsing I came across this interesting ROM:
http://forum.xda-developers.com/showthread.php?t=1312021&page=7
Copied it to SD card and flashed it. Everything went well. However, my phone is stuck in the loading screen. This already happened once. It's actually the second time I'm trying to flash this ROM. The first time I removed the battery after I spent an hour waiting in the loading screen; but that didn't help.
Anyone can help or give suggestions pls? Any help is appreciated.
Thanks in advance.

Incredible2011 said:
Hi,
So I decided to flash a ROM for the first time. Followed the steps from this:
http://forum.xda-developers.com/showthread.php?t=1337105
and got everything working with Cyanogenmod 7.1.
Whilst browsing I came across this interesting ROM:
http://forum.xda-developers.com/showthread.php?t=1312021&page=7
Copied it to SD card and flashed it. Everything went well. However, my phone is stuck in the loading screen. This already happened once. It's actually the second time I'm trying to flash this ROM. The first time I removed the battery after I spent an hour waiting in the loading screen; but that didn't help.
Anyone can help or give suggestions pls? Any help is appreciated.
Thanks in advance.
Click to expand...
Click to collapse
You may need to manually flash the boot.img from the ROM's zip file If you unlocked HBOOT 2.00.
You need to flash it in FASTBOOT USB mode using the command:
fastboot flash boot boot.img

Oh y forgot about that! Thing is I'm now stuck in the HTC loading screen instead of the ROM loading screen...

Press and hold the volume down key while starting the phone.
Then you are in boot menu you go to "fastboot". Connect the phone to the computer and you can work with adb and fastboot.
How his work you see in the developer forum.
Success...

Don't quite get what you mean...sry I'm kinda new at this. Thing is the ROM has been flashed; checking the SD card the files have been copied.
However, every time I try to boot the new ROM I get stuck at the HTC loading screen with no way out but to remove the battery.

So I flashed the boot.img and now I'm stuck in the HTC loading screen instead of the ROM loading screen. Any possible solution pls?

I'm just guessing here as I have never had this problem.
It's always went well for me, takes a while to boot first time but never an hour!
Did you do an MD5 check on the ROM you downloaded?
Try this.
Boot into recovery (Hold volume down and power)
Format all partitions apart from SDCard (I think it's System, Data and Cache)
Clear Cache
Clear Davlik-Cache
Re-flash rom.
Also would be wise to update your recovery first. (You will need to use fastboot to do this probably)
Not sure if this will work, but it definatly won't hurt you.
If it doesn't work, get a different ROM in a zip, flash through recovery see if you can boot phone.

I'm going to sound like a total noob now but I'm kinda new at this...what is an MD5 check?

MD5 checksum is to verify the file you have on your computer is exactly the same as the uploader. The uploader will generate an MD5 checksum, you generate an MD5 checksum using any program (google or some ROM manager apps) and if they match you're fine, but if they dont then it means your file has an error/is incomplete and flashing it will cause an error.
It sounds like the stuff you've done already is probably fudged so I would start over by clearing/formatting all the cache (dalvik is important), doing a complete wipe of the system (not including the SD card of course), re-download the ROM you tried and flash it in recovery, and immediately flash the boot.img file (extract it from your new ROM) from fastboot.

Wow gee thanks so much info! Will try everything from scratch and see how that works out. Thanks once again.

Could it be that I need to S-OFF my phone? It's still S-ON.

How did you flash the boot.img?
Being s-on it has to be done through your pc using fastboot commands. If you just copied it to sd card it won't work.
Try flashing rom again, then boot phone into fastboot usb mode. Flash boot.img with the command written above.
What version of hboot are you on?

Y I used my PC to flash the boot.img. HBoot 2.00 here.

If you're set on flashing other ROMs (if you don't want to restore the CM backup) it will be easier in the long run to just downgrade to HBOOT v1.13 so you can S-OFF and have no further problems flashing ROMs due to the locked bootloader.
Guide with many thanks to Nonverbose: http://forum.xda-developers.com/showthread.php?t=1373697
Remember to carefully read everything if you do that!

Incredible2011 said:
Y I used my PC to flash the boot.img. HBoot 2.00 here.
Click to expand...
Click to collapse
best thing is to flash boot img as i see from your postings that you don't know that much (earlier i was the same)
but if you do go for downgrade i suggest these things
read the full guide as soothsayer suggested.
with me and i think many of us an error appeared on the bootloader saying relocked security warning when you lock the bootloader again
don't worry
reboot your bootloader, connect your phone and start the ruu exe named ruu needed for downgrade and voila your hboot will be downgraded!

[Q] How to fix Sensation XL from GUIDE

Hello,
I've been following this guide: http://forum.xda-developers.com/showthread.php?t=1466436
When I came to the part where I had to fastboot the Chinese ROM my phone stopped working. I followed it straight out, and when I chose "Recovery" as the guide told me to choose, my phone only boots with a black lit screen and then turns black completely (no backlight), but the touch buttons still work and the phone vibrates.
The part it failed at was this:
1. You cant just flash a custom rom on this phone, firstly you will need the 'Chinese rom' which is here http://hotfile.com/dl/148413075/8990...01713.zip.html and make sure it is on the SDcard part of your phones memory. Make sure it on the root of the SDcard because it will be easier to find later. Then you will need this rom RCMix3d Runny XL rom from here http://dl.dropbox.com/u/56143145/RCM...ny_XL_v1.2.zip (thanks to benjamin.j.goodwin) and make sure that is on the SDcard too with the other rom
2. Then you will need to download this file from here http://forum.xda-developers.com/show...7&postcount=18 it is the 'Chinese boot.img' and will need flashing from fastboot again. So put the phone in fastboot and extract the 'boot.img' from the 'boot.rar' file and put it in the fastboot folder on the PC. Open the command prompt again and type this... fastboot flash boot boot.img ... This should only need doing once if you're coming from a stock rom.
3. Once you've done that you will need to get into recovery. From fastboot select bootloader and then look for recovery, it should be under fastboot if its worked correctly. Select that and the phone should then reboot and go into 'CWM' (recovery). Once there you will need to use the volume keys and power button just like when you were in bootloader. Go down and select 'Factory Reset/Data Wipe' and select that, the select yes on following screen. This will take a few mins (don't worry if it looks like its not doing anything). After that go down to 'Wipe Cache' and select that. and then go down to 'Advanced' select that and on the following screen select 'Wipe Dalvik Cache'.
Click to expand...
Click to collapse
The bolded text is what I have done, whatever comes after I never got a chance to do. Nothing I have tried so far have worked.
I'm very new to doing this kind of stuff and I thought I'd try the three musketeers ROM out, so far I haven't gotten this far. I need help in getting my phone to work again so I can continue the guide.
I'm sorry if this is in the wrong section of the forums. Like I said, I'm new, and please move this to the correct area (If any mods around). Sorry for any troubles, and appreciate any help.
Thanks! <3

I've tried to get back to stock version, but it's not working.
My phone only boots to FASTBOOT and BOOTLOADER right now. It says on the top:
***RELOCKED***
RUNNYMEDE PVT SHIP S-ON
RADIO-3831.16.00.16_M
eMMC-BOOT
When trying to do anything within the CMD it says:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3424 KB)...
OKAY [ 2.594s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.031s
:/

Phrebbie said:
I've tried to get back to stock version, but it's not working.
My phone only boots to FASTBOOT and BOOTLOADER right now. It says on the top:
***RELOCKED***
RUNNYMEDE PVT SHIP S-ON
RADIO-3831.16.00.16_M
eMMC-BOOT
When trying to do anything within the CMD it says:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3424 KB)...
OKAY [ 2.594s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.031s
:/
Click to expand...
Click to collapse
Unlock bootloader and flash recovery. Måske device s-off then run the ruu.exe . do not relock bootloader.
Sent from my Sensation XL using XDA Premium HD app

anders3408 said:
Unlock bootloader and flash recovery. Måske device s-off then run the ruu.exe . do not relock bootloader.
Sent from my Sensation XL using XDA Premium HD app
Click to expand...
Click to collapse
I'm really sorry, but how should I do this? :/
It keeps telling me it failed and remote: signature failed.

I think I did it now.
I unlocked bootlader again.
I flashed the recovery "Clockwork" OK.
Now I have no idea what to do next? I tried putting in the Chinese ROM again and then hit "Recover", but I only come to black screen and nothing happens.
RUU.EXE doesn't work either, tried it, it says security/update fail or something and it just stops.

Phrebbie said:
I think I did it now.
I unlocked bootlader again.
I flashed the recovery "Clockwork" OK.
Now I have no idea what to do next? I tried putting in the Chinese ROM again and then hit "Recover", but I only come to black screen and nothing happens.
RUU.EXE doesn't work either, tried it, it says security/update fail or something and it just stops.
Click to expand...
Click to collapse
From boot loader go to recovery.
From recovery mount SD card for PC/USB
Copy the ROM over to sdcard.
Unmount for USB/PC
Wipe data/factory reset
Wipe cache and dalvik cache
Flash the ROM
Boot up the new ROM
S-off the device
Then install the ruu.exe.
Sent from my Sensation XL using XDA Premium HD app

Thank you for reply Anders,
The problem is I can't go into "recovery" on my phone. It just goes black and nothing happens.
I did both version of Clockwork recovery flash and it succeeded - no idea if it's related, but I just can't go into recovery.

Phrebbie said:
Thank you for reply Anders,
The problem is I can't go into "recovery" on my phone. It just goes black and nothing happens.
I did both version of Clockwork recovery flash and it succeeded - no idea if it's related, but I just can't go into recovery.
Click to expand...
Click to collapse
Try from fastboot and flash twrp.
Fastboot flash recovery recovery.img
Sent from my Sensation XL using XDA Premium HD app

Thank you,
TWRP worked much better.
I put rom on USB storage (i had to format it first to be able to open it, so it was completely empty and i just put file in there)
I did wipe/reset and cache/dalvik wipe.
I flashed the ROM succesfully.
I tried booting it up, the HTC logo comes up as well as the BEATS animation, then HTC logo with "Quietly Brilliant" beneath, and it stops there, nothing happens. Also, it starts making the startup HTC signal for less than a second, then it's quiet.
The ROM I put in storage and flashed with was "Total_Senseless_SXL-v4.1.1".
No idea if I did it right but I will try the Chinese ROM as well. As said, I'm new to this.

I get a problem when trying to flash the runnymede_ax918 .zip file.
It tells me this:
Installing '/sdcard/runnymede_ax918_11511_10171
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E:Error in /sdcard/runnymede_ax918_11511_101713
(Status 1)
Error flashing zip '/sdcard/runnymede_ax918_1115
Updating partition details...
And a red text "Failed".
According to the guide I have to install the Chinese ROM first which is what I'm trying to do here.
I flashed the boot.img first, entered TWRP, factory reset/wipe cache/dalvik
Find the Chinese .zip file (runnymede_ax918) and press install and this problem occurs.

That guide is old, you do not need any other chinese ROM's and suc, just unlock bootloader, flash recovery, root, S-OFF and after that you can have whatever you want on your phone. The thing with cbinese ROM and.such was before S-OFF was available.for the device...
Sent from my Nexus S using xda app-developers app

Well that's fun. Thanks for pointing that out though.
I can't stress it enough, I'm new to this, what should I do next? How do I root and how do I S-OFF? Guides?
Sorry for troubles.

Phrebbie said:
I get a problem when trying to flash the runnymede_ax918 .zip file.
It tells me this:
Installing '/sdcard/runnymede_ax918_11511_10171
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E:Error in /sdcard/runnymede_ax918_11511_101713
(Status 1)
Error flashing zip '/sdcard/runnymede_ax918_1115
Updating partition details...
And a red text "Failed".
According to the guide I have to install the Chinese ROM first which is what I'm trying to do here.
I flashed the boot.img first, entered TWRP, factory reset/wipe cache/dalvik
Find the Chinese .zip file (runnymede_ax918) and press install and this problem occurs.
Click to expand...
Click to collapse
Delete ROM from zip and put it over again. And ofc try and open the zip on the computer first. If you can't open it on computer download the ROM again.
BTW. That is just how I did it, since no one really knows what its so special in that ROM and no one knows for sure that it makes Amy difference at all when using it or not, you can do as lexmazter wrote and don't use it.
The reason for me to flash that ROM is that I had read in here that when that ROM has been flashed hard brick was almost impossible with some common sense
No matter what, if you delete or has wrong vold.fstab and formats the sdcard from PC you only luck will be jtag.
Sent from my Sensation XL using XDA Premium HD app

anders3408 said:
Delete ROM from zip and put it over again. And ofc try and open the zip on the computer first. If you can't open it on computer download the ROM again.
BTW. That is just how I did it, since no one really knows what its so special in that ROM and no one knows for sure that it makes Amy difference at all when using it or not, you can do as lexmazter wrote and don't use it.
The reason for me to flash that ROM is that I had read in here that when that ROM has been flashed hard brick was almost impossible with some common sense
No matter what, if you delete or has wrong vold.fstab and formats the sdcard from PC you only luck will be jtag.
Sent from my Sensation XL using XDA Premium HD app
Click to expand...
Click to collapse
From what i know, that Chinese ROM was supposed to have unsecured boot, don't know how that helps and i don't get the ideea behind it anyways, so the right way to do it is to Unlock Bootloader -> Flash Recovery -> Root -> S-OFF -> Free to try whatever custom ROM out there you want, hard bricking is pretty hard even without common sense, i personally tried to do it and i failed, i think you need to know how to brick it in order to brick it, but to avoid that, make sure you do things the right way, read things before you try and so on.

Lexmazter said:
From what i know, that Chinese ROM was supposed to have unsecured boot, don't know how that helps and i don't get the ideea behind it anyways, so the right way to do it is to Unlock Bootloader -> Flash Recovery -> Root -> S-OFF -> Free to try whatever custom ROM out there you want, hard bricking is pretty hard even without common sense, i personally tried to do it and i failed, i think you need to know how to brick it in order to brick it, but to avoid that, make sure you do things the right way, read things before you try and so on.
Click to expand...
Click to collapse
a simple way to do a hard brick:
flash a rom with only has the vold.fstab for hboot 1.25 and device is 1.28 , then mount sdcard for pc and format sdcard (pc says you need to do it before it can read the sdcard) - the result = BRICKED

No OS on phone, can't install a rom

I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab. Then when he tried to flash Cyanogenmod 10.2 it keeps failing. I asked him why he did this and he said his friend told him how cool Cyanogenmod is so naturally he want it to! (By the way my son is 13).
I know very little about this phone but I would like to get the phone back to the way it was before he messed with it as it cost me $650 to buy it. I started reading about RUU files but from what I can tell the RUU will not work with S-ON. And I can't seem to flash any ROM as it keeps failing. Any suggestions would be a big help!

Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck

Then make him use a flip phone for a week as punishment lol

I had the same. In my case I started ruu for another version (international), of course ruu failed to install but it did fix partitions, after that I was able to sideload rom. I will try to find my topic and provide You with my solution.
This is my BLS/ALS with HTC One, patient is alive and well now, only camera has pink tint...
http://forum.xda-developers.com/showthread.php?t=2322851
Try with CWM instead of TWRP... and finally pass some information about progress.

Thealshear said:
Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck
Click to expand...
Click to collapse
Will the ruu method work if the phone is S-ON? All of the XDA posts I read state that you need to be S-OFF?

Give it a shot the phone is already bricked what you got to lose

crixley said:
Then make him use a flip phone for a week as punishment lol
Click to expand...
Click to collapse
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk

woody970 said:
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can run an ruu but it has to be newer..
See here:
http://forum.gsmhosting.com/vbb/f485/understanding-s-off-super-cid-s-read-b4-u-run-ruu-1505916/

crixley said:
You can run an ruu but it has to be newer..
Any idea where to download the RUU? The build number that was on the phone before all this started was KRT16S.H5 release-keys
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

woody970 said:
I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab.
Click to expand...
Click to collapse
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk

Delgra said:
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
when your son was flashing CM mod was he using the correct version? I don't recall but I tried flashing my ATT HTC one but I am running a WWE firmware so that made me have to flash the GSM version of CM mod. http://www.cmxlog.com/11/m7ul/ Try downloading the latest zip file there and than try mounting to his phone with the USB mount or if you have a USB OTG you can install it from a USB. It shouldn't matter if your S-ON or S-OFF for installing some roms it just helps you avoid taking extra steps to get the ROM to install.
When your flashing with TWRP make sure to do a advanced wipe and check everything that is on there. After you do a advanced wipe do a regular factory reset. I'm hoping that the new CM11 rom will flash for his phone. You can also use ADB sideload to send the zip files over to your phone if you cannot mount the phone. What ADB sideload does is open up a connection from your phones USB and lets you transfer zips over onto the internal SD card basically in DOS command.

I want to thank everyone for there guidance in this. After googling for a couple of days and a few failed attempts with the RUU command I was finally able to restore the phone. I was able to flash a nandroid backup using TWRp from another google edition HTC which brought the phone back to life. Then I flashed a stock recovery and OTA's became available to the phone. The once dead HTC is now back up and running stock 4.4 android. The only issue I with the phone now is that there is a popping sound after a notification comes in that I can't get rid of... Anyone have any ideas?
Sent from my Nexus 5 using Tapatalk

The popping noises seem to come after I updated to kit Kat I don't know but a lot of people might have that issue too.
Sent from my HTC One using Tapatalk

[Q] Chronic phone problems. Want to nuke the whole thing and start again.

I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931

gothmog1114 said:
I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931
Click to expand...
Click to collapse
Follow this guide.

StormyNight said:
Follow this guide.
Click to expand...
Click to collapse
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)

gothmog1114 said:
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)
Click to expand...
Click to collapse
Could you screenshot the bootloader for me?

Maybe you've got a whacked recovery. Reflash from fastboot from an md5 verified .img (make sure its m7wls version of TWRP). You should have no problems wiping any partition from within.

StormyNight said:
Could you screenshot the bootloader for me?
Click to expand...
Click to collapse
http://imgur.com/GwCBmpe

gothmog1114 said:
http://imgur.com/GwCBmpe
Click to expand...
Click to collapse
Are you using a Windows 8 computer? If so, try it with Windows 7. If you're using Windows 7, try a different port (preferably a USB 2.0 port).