Database Develop

Stuck G1 - but Not your typical

Okay.
I dont think my problem is typical, and Ive searched google and xda for answers. Some situations seem similar, but none exact.
Here is the story:
G1 was running wifi tether and on charge. No bumps or bruises, just sitting by itself. The tether stopped working, so I went over to look at the G1 and the phone was frozen. Display was lit up and working, just frozen. Had to pop the battery out to shut it down.
After powering back up, the sits at the splash screen indefinitely.
I can go into fastboot but I can NOT get into recovery.
I have going into fastboot usb mode and:
1) flash a recovery image (works)
2) flash a nandroid backup (works)
3) flash rc29 (see below)
4) flash hboot (always fails)
What I mean by works is the flash indicates it was good, but there is no change in functionality of the phone. Hboot gives me device errors.
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
Radio-2.22.19.26I
Apr 20 2009,15:30:43
I have also flashed a different splash image - and even though it says it succeeded the image doesnt change.
When I attempt to flash the original RC29 using the SD card mode or fastboot mode it indicated I need HBOOT 1.33.2004. 2004 *will not install* --- it gives an error (I think something to the effect of wrong device.)
I know my way around fastboot and adb, but I dont know what "hboot mode" is used for. For grins, I tried flashing the recovery in hboot mode and it says "waiting on device" forever.
It seems almost like this is a hardware problem that is presenting itself as a software issue.
Also - *sometime* when I hold home/power to try to boot into recover the phone will connect to ADB (listed in adb devices) but no commands seem to work.
Im an a loss. 10+ hours trying to fix this thing...
Any ideas?
Thanks.
Blade

Blade10 said:
When I attempt to flash the original RC29 using the SD card mode or fastboot mode it indicated I need HBOOT 1.33.2004. 2004 *will not install* --- it gives an error (I think something to the effect of wrong device.)
Click to expand...
Click to collapse
Tried with a goldcard?

No. Maybe I didnt read enough, but I thought the goldcard required a WM Device? All my machines are win xp, obvously I can use a live cd to boot linux.
BTW, the SDcard method of installing dream.nbh (RC29) gives me a checksum error, while fastboot finishes but doesnt make a difference. Yes, tried different SD cards and ran checksum after coipying to the card - checksum is correct.
Any other ideas, or maybe some links that make a goldcard easy?
Thanks,
Blade

[Q] HTC Dream update to Android2 (wow this is hard)

I've been trying for a long time reading all the guides following all instructions and I think I finally see how all the pieces work together, but for some reason, I get completely stuck by fastboot.
Here's what it says when I hold back and power:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Sep 2 2008
Serial 0
this guide: http://wiki.cyanogenmod.com/index.php?title=Dream:DangerSPL
Says to root the G1 (based on the radio version, I think that's been done).
Next I'm supposed to install Amon Ra recovery
From this guide: http://forum.xda-developers.com/showthread.php?t=566669
It says that if I have the engineering SPL (which I seem to based on the numbers), I should be able to follow these directions:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
I've copied the img to somewhere on the phone (I forget where) and I've done the second and third steps, but fastboot never sees the device even though ADB can. What now?
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img

Something must have happened at some point because now the phone won't boot unless I do it into safe mode. This is pretty frustrating. All these guides and none work for me.

What is the status at this point? Are you able to get into Recovery, fastboot, etc...?

When you boot normally and you plug your phone in fastbooted, do you hear a sound/any indication from Windows that it's detected in any way at all? Have you checked device manager?
You need not bother with the further commands unless 'fastboot devices' picks up the phone in command prompt. Fastboot didn't find mine straight away either. I had to change to HTC Bootloader driver when connected to USB in bootloader -which shouldn't effect ADB or anything else as the phone is booted differently and loads as a different device to have ADB operational, hence why I believe you generally can't mix fastboot/adb ccommands.

BeenAndroidized said:
What is the status at this point? Are you able to get into Recovery, fastboot, etc...?
Click to expand...
Click to collapse
Sorry for the late reply. I don't often get a chance to work on the phone. I can boot to the four color boot screen that shows the hboot and radio information as follows:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Sep 2 2008
Serial 0
For a second it flashes to a different screen and then says "no image" or something then goes back to the multi-color screen. When I plug the device into the computer during the multi-color screen, nothing happens. The computer makes no noises to indicate it knows a USB device is there.
If I exit colored screen mode (whatever it's called), and leave the cable plugged in, Windows says there's something attached but it malfunctioned. Both the phone and Windows respond when I plug in USB at any time other than the multicolor mode.

I'm trying to solve the "g1 looks like usb mass storage" issue and it's not working. If I follow directions to boot to fasboot mode first, it only goes to the four color screen and the USB isn't recognized. If I do it while it's on normally, Windows sees it, but won't let me update the drivers.
I tried picking them manually, but that's not working. Wait... all of a sudden I see HTC Android listed under "Disk Drives" I don't know what happened, but it seems to have worked (I just updated the GOOGLE USB drivers using the SDK third party installer so maybe that was it). Let me try from scratch again.

Still nothing. By the way, I've never been able to boot to Fastboot mode. I've never seen skateboarders. Do you install that?

Ok, I've tried a series of other guides online. I've spent the last 4 or 5 hours on this trying to root and then install various other things. Using three different rooting techniques, I still can't get super user access when using terminal emulator.
What is this? Some kind of practical joke?

Making progress... I think
I followed the directions here:
http://wiki.cyanogenmod.com/index.php?title=HTC_Dream:_Rooting
Which didn't use to make sense, but now are helping. I downgraded the Firmware per instructions, but used the SuperOneClickv1.7-ShortFuse to root the phone instead (which worked splendidly). Now I FINALLY can get root using ADB though installing Amon Ra recovery isn't going too smoothly yet.
Edit, spoke too soon: I didn't see anything in the SDCARD folder until I disconnected the cable and reconnected it. I was able to use the flash_image recovery recovery.img file now (recovery.img is a renamed amon ra cyan image).

After installing Amon Ra, upgrading the SPL to Danger was easy to do in recovery mode as was installing Cyanogen. I also installed a different mod (biffmod), but didn't like it.
Now everything seems to work other than clockwordmod still won't install (but I don't really care since I can do everything fine with Amon Ra if I move downloads into the root folder).
I hope this thread helps others!

One S - Stuck In Loop After Maximus HD Install

I browsed a few other threads, and tried to update the recovery with the latest version per the advice of a member, and prior to this, it was just stuck at the green HTC screen with the red disclaimer under it. And after flashing the newest recovery TWRP it has begun to loop.
I also cannot boot into recovery now. Only fastboot is working,.
Phone info is:
***UNLOCKED****
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT- 1.14.0005
RADIO - 1.13.50.05.25
OPENDSP-V29.1.0.45.0622
EMMC-BOOT
NOV 21, 2012, 12:17:41
I believe everything is set for the Maximus ROM to work, but if I am missing something I would appreciate the feedback and help.
Thanks
Tancred

Tancred213 said:
I browsed a few other threads, and tried to update the recovery with the latest version per the advice of a member, and prior to this, it was just stuck at the green HTC screen with the red disclaimer under it. And after flashing the newest recovery TWRP it has begun to loop.
I also cannot boot into recovery now. Only fastboot is working,.
Phone info is:
***UNLOCKED****
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT- 1.14.0005
RADIO - 1.13.50.05.25
OPENDSP-V29.1.0.45.0622
EMMC-BOOT
NOV 21, 2012, 12:17:41
I believe everything is set for the Maximus ROM to work, but if I am missing something I would appreciate the feedback and help.
Thanks
Tancred
Click to expand...
Click to collapse
This is HTC ONE forum not ONE S , you can try with RUU.exe while you're in bootloader or " fastboot oem rebootRUU "

Vixa said:
This is HTC ONE forum not ONE S , you can try with RUU.exe while you're in bootloader or " fastboot oem rebootRUU "
Click to expand...
Click to collapse
My bad, I was following posts about this ROM and assumed they were discussing the same phone. But it appears that there isn't a S thread, only an X for this model..
This takes me to a silver HTC logo and hangs there... I have fastboot access, but i cant get ADB to talk to the phone. But with fastboot I can push a new recovery img but still not allowing me into any recovery.

If you cant get into recovery donwload a RUU and get your phone flashed with it from FASTBOOT.

Vixa said:
If you cant get into recovery donwload a RUU and get your phone flashed with it from FASTBOOT.
Click to expand...
Click to collapse
Able to get into Philz recovery and adb sideload zips, but it cant find my sdcard...what a headache this is turning into, and no closer to knowing what the problem was / is.

Tell me can you mount system or get in twrp or something to hold on?
Sent from my HTC One using Tapatalk

Vixa said:
Tell me can you mount system or get in twrp or something to hold on?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Changed TWRP to CWM which is at least allowing me into recovery mode.
Thinking I will have to transfer the files with another android phone onto the memory and try to install the rom again?
Mounting USB fails, it just makes a sound like I have added a drive to my PC non stop every few seconds, and I cant mount anything. formatted it and it seems to have settled it a bit. But I cant do anything with the storage via USB in Windows. Just updated to the latest clockwork for my model and still no success...
With latest version I cant even sideload at the moment.

Tancred213 said:
Changed TWRP to CWM which is at least allowing me into recovery mode.
Thinking I will have to transfer the files with another android phone onto the memory and try to install the rom again?
Mounting USB fails, it just makes a sound like I have added a drive to my PC non stop every few seconds, and I cant mount anything. formatted it and it seems to have settled it a bit. But I cant do anything with the storage via USB in Windows. Just updated to the latest clockwork for my model and still no success...
With latest version I cant even sideload at the moment.
Click to expand...
Click to collapse
Ok, sorted that out, apparently the drivers were having issues, and when I manually picked them I became able to communicate with the phone again like normal. This is like hour 8 of the upgrade so far...
Assuming my firmware is also outdated, and from my searching I havent found an easy way to update my hboot and others without flashing a RUU Rom from T-Mobile, any alternatives to doing that?

Pretty sure I killed it. Downloaded the latest RUU from T-Mobile, after relocking the bootloader and turning S-on, it ran fine, completed, rebooted the phone and now its totally dead. No charge light, doesnt turn on at all. And I was just thinking to myself how hard it is to brick a phone since I have yet to kill one with all of my misadventures....oops. We'll see what happens..

Had you read the HTC One S forum, you would have found out that this particular phone can get hard bricked up S-OFF with SuperCID and then a RUU update is ran.

[Q] Can't get past white HTC logo screen, stock rom(?) details within

EDIT FOR DETAIL: I CAN GET TO AND USE FASTBOOT, THAT SEEMS TO BE IT (Well, I could before it went into an infinite bootloop, but once the battery runs down I can probably get back in)
Hi All,
I received a HTC ONE today (Model on back: PNO7140) - got it for cheap from an op shop but sold as-is :/
When I plugged it in there was a red flashing light so I held power + vol+/- and it booted to the white HTC logo and then turned off but showed a solid red LED, so i left it to charge for a couple hours.
Now I'm having a look at it and it always turns off after the HTC logo.. I can get into the setup screen with vol- but factory reset seems to just freeze as soon as I press it (left for maybe five minutes?) - fastboot activates OK and the device shows up on my win7 pc.
I've attached a getvar all from fastboot and I'll type out the first few lines shown in fastboot on the device, let me know if you need anything else:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.23.3263.28
etc..
Going to bootloader just reboots the phone, shows the HTC logo, then turns off and device QHUSB_DLOAD shows up without drivers in device manager (same thing that happens when device is powered down from fastboot).
I have ADB and fastboot installed on this PC, I've done rom updates in the past but got quickly lost when trying to figure my way through this one so thought I"d ask for help before messing anything up.
Thanks anyone and everyone
e: oh one other thing sometimes it will show the Battery with lightning bolt symbol too - although fastboot says battery status is good.. also it seems to take awhile to turn on, like I have to hold the power button for about 10 seconds.. don't know if that's normal? I'm not covering the light sensor.

defroster said:
Hi All,
I received a HTC ONE today (Model on back: PNO7140) - got it for cheap from an op shop but sold as-is :/
When I plugged it in there was a red flashing light so I held power + vol+/- and it booted to the white HTC logo and then turned off but showed a solid red LED, so i left it to charge for a couple hours.
Now I'm having a look at it and it always turns off after the HTC logo.. I can get into the setup screen with vol- but factory reset seems to just freeze as soon as I press it (left for maybe five minutes?) - fastboot activates OK and the device shows up on my win7 pc.
I've attached a getvar all from fastboot and I'll type out the first few lines shown in fastboot on the device, let me know if you need anything else:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.23.3263.28
etc..
Going to bootloader just reboots the phone, shows the HTC logo, then turns off and device QHUSB_DLOAD shows up without drivers in device manager (same thing that happens when device is powered down from fastboot).
I have ADB and fastboot installed on this PC, I've done rom updates in the past but got quickly lost when trying to figure my way through this one so thought I"d ask for help before messing anything up.
Thanks anyone and everyone
e: oh one other thing sometimes it will show the Battery with lightning bolt symbol too - although fastboot says battery status is good.. also it seems to take awhile to turn on, like I have to hold the power button for about 10 seconds.. don't know if that's normal? I'm not covering the light sensor.
Click to expand...
Click to collapse
Try the solution from this thread: http://forum.xda-developers.com/showthread.php?t=2770684
Good luck!

That seems pretty full on. I have a Linux live CD somewhere but should I not try something simpler first?
Keeping in mind fastboot seems to work?

So far I've tried running revive.sh - device not found, tried unlocking via htcdev - it shows the unlock notification request on the phone but after i push yes it reboots and bootloader still reports locked i think? tried rumrunner but it won't run from bootloader.
Heeeeelp!

tried:
chmod 755 PblClear
sudo modprobe qcserial
sudo ./PblClear
and it actually got past the HTC screen to the next HTC screen with beats logo and made a noise... sat there for a minute, then turned itself off...
progress of sorts?
E: unable to repeat that so it may have been unrelated

Is it possible to push a ROM via fastboot? Given that I'm s-on etc?

If I"m not mistaken I can't really do anything from fastboot unless the bootloader is unlocked?
I've tried the HTCdev method a bunch of times, after I click yes it just freezes for a second, reboots and is the same as before (locked).

and now it's in an infinite bootloop !
I can't stop the damn thing power cycling!

Escaped the bootloop but it goes into one whenever turned on or plugged in now :/

anyone?
No one has any ideas?

defroster said:
If I"m not mistaken I can't really do anything from fastboot unless the bootloader is unlocked?
I've tried the HTCdev method a bunch of times, after I click yes it just freezes for a second, reboots and is the same as before (locked).
Click to expand...
Click to collapse
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/707/4.20.707.7.zip
Download this and flash it with fastboot. This is signed firmware and requires a locked bootloader so that's not a problem.
As I said in the unbrick thread know one has confirmed this did or didn't work. Try it and please let me know the result.
Download the firmware and rename the file firmware.zip and put it in your fastboot folder.
Reboot the phone into the bootloader and connect fastbootusb.
In the fastboot command line type.
Code:
fastboot erase cache
Code:
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Once that's done (be sure to delete any old Unlock_code.bin you already have from htcdev) then go and complete the full unlock procedure to get a new Unlock_code.bin and try to unlock it again.
:fingers-crossed:
The idea is by flashing firmware your reinstalling hboot, do with new hboot and unlock code hopefully it will work but as I say I can't confirm it. Worth a try though.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

[Q] I screwed up big time and now my M7 is bricked.

So, I took a look around the forums thinking that maybe another newbie such myself did this thing but apparently I am one of a kind. So here is my story:
I have my HTC One M7 since the summer of 2014, I rooted it without any problems and unrooted it when the Lollipop update came out. After two or three days of the update, I had a problem where my phone would lose all sounds and would be unable to play any media that involved music. I thought it might be a software problem so I rooted it again and I installed the ViperOne ROM from the forums. Despite the fact that I really loved the ROM, the problem insisted and once/twice a day I needed to clear cache, restart the phone and if I was lucky it would go away on the first trial.
P.S. The problem only occurred when a call started.
This past Friday however, the problem wouldn't go away no matter what I did. My phone had lost all sounds and I couldn't do anything about it. Ringtones, alarms, videos, youtube, calls, even the bootup sound, nothing.
So I decided to redo everything from the beginning, in case I did something wrong and with the hope that it will just get fixed. Thinking that my software was the problem, I decided not to do a backup (please don't kill me I know it was a stupid decision) and to just wipe everything off, and do it from scratch. I re-installed viper as a first step but it didn't fix. I wiped the whole system and data partitions and installed the ROM again, nothing. Then I tried to install a clean HTC RUU and I found that the latest was this one
Code:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3
but it needed to be installed through HTC Sync and it just wouldn't work. I was getting a message that the phone was not connected.
Uninstalled HTC Sync, Re-installed HTCDriver_4.1.0.001 and downloaded a KitKat ROM from HTC1Guru site but when I tried to install it, I was getting an error message from the TWRP recovery.
Next, I downloaded Guru_Reset_M7_2.24.401.8, installed it, opened it, sound still wouldn't work no matter what. Also, while I installed the Guru Reset, I was asked if I wanted to also install stock recovery and I said yes. Since this ROM was able to be installed, I started doing the OTA updates with the hope that one of them might fix the sound problem. On the third update, the phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
TL;DR
phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
Please help me I don't know what to do and I cannot send it to service to fix it because the Bootloader has the "Tampered" message on top.
This is what my bootloader has:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4A.17.3250.14
OpenDSP-v35.120.274.0718
OS-7.19.401.2
eMMC-boot 2048MB

skypse said:
So, I took a look around the forums thinking that maybe another newbie such myself did this thing but apparently I am one of a kind. So here is my story:
I have my HTC One M7 since the summer of 2014, I rooted it without any problems and unrooted it when the Lollipop update came out. After two or three days of the update, I had a problem where my phone would lose all sounds and would be unable to play any media that involved music. I thought it might be a software problem so I rooted it again and I installed the ViperOne ROM from the forums. Despite the fact that I really loved the ROM, the problem insisted and once/twice a day I needed to clear cache, restart the phone and if I was lucky it would go away on the first trial.
P.S. The problem only occurred when a call started.
This past Friday however, the problem wouldn't go away no matter what I did. My phone had lost all sounds and I couldn't do anything about it. Ringtones, alarms, videos, youtube, calls, even the bootup sound, nothing.
So I decided to redo everything from the beginning, in case I did something wrong and with the hope that it will just get fixed. Thinking that my software was the problem, I decided not to do a backup (please don't kill me I know it was a stupid decision) and to just wipe everything off, and do it from scratch. I re-installed viper as a first step but it didn't fix. I wiped the whole system and data partitions and installed the ROM again, nothing. Then I tried to install a clean HTC RUU and I found that the latest was this one
Code:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3
but it needed to be installed through HTC Sync and it just wouldn't work. I was getting a message that the phone was not connected.
Uninstalled HTC Sync, Re-installed HTCDriver_4.1.0.001 and downloaded a KitKat ROM from HTC1Guru site but when I tried to install it, I was getting an error message from the TWRP recovery.
Next, I downloaded Guru_Reset_M7_2.24.401.8, installed it, opened it, sound still wouldn't work no matter what. Also, while I installed the Guru Reset, I was asked if I wanted to also install stock recovery and I said yes. Since this ROM was able to be installed, I started doing the OTA updates with the hope that one of them might fix the sound problem. On the third update, the phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
TL;DR
phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
Please help me I don't know what to do and I cannot send it to service to fix it because the Bootloader has the "Tampered" message on top.
This is what my bootloader has:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4A.17.3250.14
OpenDSP-v35.120.274.0718
OS-7.19.401.2
eMMC-boot 2048MB
Click to expand...
Click to collapse
oops, that's the wrong RUU for you phone, I would also hazard a guess that the guru reset is just too old, the key for you is in the numbers, your current os is 7.19.401.2 its the 401 part which matters the most, the 7 part is also android revision, as your on 7, I would say 2 is very too old for your phone., the RUU you tried to use if you look at the numbers is android revision 4 developer edition 1540 (4.19.1540.9) hope that explains that a little for you.
The red exclamation mark is stock recovery, when you see that symbol, press volume up and power a few times and you'll get the menu.
well the first thing you need to do is get your drivers sorted, so uninstall HTC sync manager and the drivers now restart your computer, then re-download it, install it, and then go into add/remove programs and remove HTC sync, just above it you will see HTC driver package, leave that alone.
now boot your phone into the bootloader, fastboot USB mode and plug it into the computer, leave it alone to detect your phone ands install the fastboot drivers.
your going to need to download 2 files: your RUU zip and HTC's fastboot to flash it: https://www.androidfilehost.com/?fid=95916177934554130 rename this file to RUU for ease, and also download this: https://www.androidfilehost.com/?fid=96042739161891970, put both files on your computer in the same folder as your current adb and fastboot files, then just issue these commands, this will wipe your entire phone by the way, but I think you've probably already done that anyway.
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
your phone should now say tampered and relocked at the top
fastboot oem rebootRUU black screen silver HTC logo
htc_fastboot flash zip RUU.zip notice your now using the HTC fastboot, the normal one wont work for this flash
it take about 10 mins to flash, at the end make sure it says successful and OKAY, final commands are:
fastboot reboot-bootloader
fastboot reboot
phone should now boot, it will be a first time boot so may take a while

Seanie280672 said:
oops, that's the wrong RUU for you phone, I would also hazard a guess that the guru reset is just too old, the key for you is in the numbers, your current os is 7.19.401.2 its the 401 part which matters the most, the 7 part is also android revision, as your on 7, I would say 2 is very too old for your phone., the RUU you tried to use if you look at the numbers is android revision 4 developer edition 1540 (4.19.1540.9) hope that explains that a little for you.
The red exclamation mark is stock recovery, when you see that symbol, press volume up and power a few times and you'll get the menu.
well the first thing you need to do is get your drivers sorted, so uninstall HTC sync manager and the drivers now restart your computer, then re-download it, install it, and then go into add/remove programs and remove HTC sync, just above it you will see HTC driver package, leave that alone.
now boot your phone into the bootloader, fastboot USB mode and plug it into the computer, leave it alone to detect your phone ands install the fastboot drivers.
your going to need to download 2 files: your RUU zip and HTC's fastboot to flash it: https://www.androidfilehost.com/?fid=95916177934554130 rename this file to RUU for ease, and also download this: https://www.androidfilehost.com/?fid=96042739161891970, put both files on your computer in the same folder as your current adb and fastboot files, then just issue these commands, this will wipe your entire phone by the way, but I think you've probably already done that anyway.
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
your phone should now say tampered and relocked at the top
fastboot oem rebootRUU black screen silver HTC logo
htc_fastboot flash zip RUU.zip notice your now using the HTC fastboot, the normal one wont work for this flash
it take about 10 mins to flash, at the end make sure it says successful and OKAY, final commands are:
fastboot reboot-bootloader
fastboot reboot
phone should now boot, it will be a first time boot so may take a while
Click to expand...
Click to collapse
Thank you very much for your help Seanie. I followed all the steps as you described but I still get "waiting for device" message in the command prompt. How can I overcome this? Is it supposed to be a problem with the drivers?

skypse said:
Thank you very much for your help Seanie. I followed all the steps as you described but I still get "waiting for device" message in the command prompt. How can I overcome this? Is it supposed to be a problem with the drivers?
Click to expand...
Click to collapse
yes it's a driver issue
see nkk71 guide post 2 faq 2 / to get fastboot working with your phone
http://forum.xda-developers.com/showthread.php?t=2541082

Thank you for your reply! I downloaded the drivers from the guide and it works. I'm on step 5 now and waiting for flash to end.
EDIT: So everything worked perfectly and I finally was able to turn my phone on again. Thank you very much for your assistance!
Bad news is that the sound problem is still here. I really have no idea on what would be the problem. Maybe it has something to do with the hardware and the whole Lollipop upgrade was an unfortunate moment. I guess I'll start another thread in the following days to see if anyone can help with that.