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.
Related
Hey guys,
So randomly my phone decided to just turn off (it was just idle on the home screen) and when I booted it back up it was in the Fastboot Menu.
I've tried reboot and even factory reset but neither work they just bring the phone right back to this when I turn it on anyone got any tips for me I'm hoping there's a really simple solution I have naively overlooked.
The screen says
***LOCKED*****
***Security Warning*******
VIVO PVT SHIP S-ON RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
A few months back I used a RUU to manually update to ICS and everything went fine and I had been running it fine for a long time so I'm not sure if that impacted on this in any way at all.
Anyway since this happened I've tried the old turning it off and on, battery out for an hour, sim out/sd out etc
Also the following:
I've tried running the RUU again but I get error 170 as it gets stuck at "waiting for bootloader" after it reboots the phone at the start of the process
(Tried in all my USB ports, reinstalling drivers/HTC Sync, using original cable)
I tried flashing from my SD card, it reads the zip and asks would you like to update but after I click yes it goes for a few seconds and then says "Partition Update Failed" and prompts me to reboot. (Tried multiple sd's)
I tried to unlock the phone using the HTCDev unlock, however once I get my token and use it to get to the unlock screen on the phone I am unable to select yes my phone simply does not acknowledge the option when I press the power button it instead vibrates a few times and then inevitably I end up selecting the No option after much frustration.
I should probably mention that fastboot lists my device under devices but adb does not.
I would have tried making a goldcard but I currently cannot obtain my CID through adb nor by using readcid.exe with my laptop card reader.
So if anyone could help me out that would be much appreciated as I don't have a warranty on this or anything and HTC support were of exceedingly little help.
Nick960 said:
Hey guys,
So randomly my phone decided to just turn off (it was just idle on the home screen) and when I booted it back up it was in the Fastboot Menu.
I've tried reboot and even factory reset but neither work they just bring the phone right back to this when I turn it on anyone got any tips for me I'm hoping there's a really simple solution I have naively overlooked.
The screen says
***LOCKED*****
***Security Warning*******
VIVO PVT SHIP S-ON RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
A few months back I used a RUU to manually update to ICS and everything went fine and I had been running it fine for a long time so I'm not sure if that impacted on this in any way at all.
Anyway since this happened I've tried the old turning it off and on, battery out for an hour, sim out/sd out etc
Also the following:
I've tried running the RUU again but I get error 170 as it gets stuck at "waiting for bootloader" after it reboots the phone at the start of the process
(Tried in all my USB ports, reinstalling drivers/HTC Sync, using original cable)
I tried flashing from my SD card, it reads the zip and asks would you like to update but after I click yes it goes for a few seconds and then says "Partition Update Failed" and prompts me to reboot. (Tried multiple sd's)
I tried to unlock the phone using the HTCDev unlock, however once I get my token and use it to get to the unlock screen on the phone I am unable to select yes my phone simply does not acknowledge the option when I press the power button it instead vibrates a few times and then inevitably I end up selecting the No option after much frustration.
I should probably mention that fastboot lists my device under devices but adb does not.
I would have tried making a goldcard but I currently cannot obtain my CID through adb nor by using readcid.exe with my laptop card reader.
So if anyone could help me out that would be much appreciated as I don't have a warranty on this or anything and HTC support were of exceedingly little help.
Click to expand...
Click to collapse
Try to use search.
For example in this thread were this:
Originally Posted by Addiso View Post
Did you get the HTC token again that you used to unlock the first time? If not, not go back into htcdev.com and follow all of directions. After you have it all in fastboot type in
Fastboot flash unlocktoken unlock_code.bin
http://forum.xda-developers.com/showthread.php?t=2236527
egorlins said:
Try to use search.
For example in this thread were this:
Originally Posted by Addiso View Post
Did you get the HTC token again that you used to unlock the first time? If not, not go back into htcdev.com and follow all of directions. After you have it all in fastboot type in
Fastboot flash unlocktoken unlock_code.bin
http://forum.xda-developers.com/showthread.php?t=2236527
Click to expand...
Click to collapse
Yeah I had a look at that before, I hadn't unlocked my phone before with htcdev but even then when I did try I was able to get my token and run the command and everything perfectly fine and even it takes me to the "Would you like to unlock your phone?" screen on my phone but I am unable to select the yes option and complete the final step which is the frustrating part.
Nick960 said:
Hey guys,
So randomly my phone decided to just turn off (it was just idle on the home screen) and when I booted it back up it was in the Fastboot Menu.
I've tried reboot and even factory reset but neither work they just bring the phone right back to this when I turn it on anyone got any tips for me I'm hoping there's a really simple solution I have naively overlooked.
The screen says
***LOCKED*****
***Security Warning*******
VIVO PVT SHIP S-ON RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
A few months back I used a RUU to manually update to ICS and everything went fine and I had been running it fine for a long time so I'm not sure if that impacted on this in any way at all.
Anyway since this happened I've tried the old turning it off and on, battery out for an hour, sim out/sd out etc
Also the following:
I've tried running the RUU again but I get error 170 as it gets stuck at "waiting for bootloader" after it reboots the phone at the start of the process
(Tried in all my USB ports, reinstalling drivers/HTC Sync, using original cable)
I tried flashing from my SD card, it reads the zip and asks would you like to update but after I click yes it goes for a few seconds and then says "Partition Update Failed" and prompts me to reboot. (Tried multiple sd's)
I tried to unlock the phone using the HTCDev unlock, however once I get my token and use it to get to the unlock screen on the phone I am unable to select yes my phone simply does not acknowledge the option when I press the power button it instead vibrates a few times and then inevitably I end up selecting the No option after much frustration.
I should probably mention that fastboot lists my device under devices but adb does not.
I would have tried making a goldcard but I currently cannot obtain my CID through adb nor by using readcid.exe with my laptop card reader.
So if anyone could help me out that would be much appreciated as I don't have a warranty on this or anything and HTC support were of exceedingly little help.
Click to expand...
Click to collapse
U will need to Downgrade your device from ICS to GB or anything else ...At times it can be Windows 8 ,8.1 issue also ...The driver are still messed up search the forum u will find working way to get driver's work ..Error(170) which means your phone is blank to flash image to boot from or Os for starters..Can u boot in bootloader (Y) then simply working your way via CMD (windows 7 if u can access). It says RELOCKED on your device(Security warning can you paste a screen snap) .
1:- Flash a recovery(if yes skip this)
2:- boot into boot bloader (install any rom via recovery)
3:- flash boot.img manually (fastboot flash boot boot.img)
If it does not work REunlock ur device via htcdev.com
If you were trying to downgrade is HBoot Version (the same issue might happen)
Take stuff's real slow (make sure u do have correct driver installed on your pc )
Okay, first thing first. (INFO ON PHONE) I have a HTC One (M7wls) Sprint 36GB phone. Phone is ROOTED.
bootloader:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.55.0000
OpenDSP-v32.120.274.0909
OS-3.05.651.6
eMMC boot 2048MB
What can I access:
Fastboot
ADB Sideload
Recovery - I am using custom recovery - openrecovery-twrp-2.6.3.0-m7wls
Now the problem is:
When I install a ROM. Every ROM that I use didn't fully complete installing. When it boot up, can't access home screen, like i can't even do nothing, If I'm not making any sense what I'm trying, basically I don't have no OS-install. And when I install a ROM and do the ADB sideload and install em I just can't get to the home screen , farthest I can go is the lockscreen, but then that don't even act right, as in either it don't want to slide up (by the way my screen work and digitizer) or its blank/black and I can even slide it up, or as i should say froze for about few sec, AND when i can slide up the lockscreen it goes to the white HTC logo screen and stays there about 45-60sec and Reboot over and over, until i go into either recovery or bootloader and power it down.
ROMs that I've downloaded and install but don't completely works:
- Android_Revolution_HD-One_51.0
- One_4.19.401.8_odexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Sprint_HTC_One_Stock_Rooted_Odexed_3.05.651.6
- viperROM_One_v1.0.4
What I'm saying is that, for example of What I do to install:
-Boot in Recovery
-Format Data (so i can mount data)
-Erase cache
-Reboot recovery (so the updating partition data can refresh)
-Access ADB Sideload
-Install a ROM (once complete) i reboot the phone
-After all the boot up LOGOs, WHEN I get to the lockscreen it either , 1. don't want to slide up, 2. when do slide up goes to white HTC logo screen get stays about 60sec, then Reboot itself , and 3. Just done want to boot up
Also have Tried RUUs: and Yes I unzip to run the Ruu.exe
- Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
- Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Also and Yes I re-lock my bootloader to run the RUU , still doesn't happen
I'm not sure which one have this problem, but one of em, Do go through the process and once I get to the part to update Image (I realized my phone image is newer than the RUU image) so i proceed anyways, then it comes to a screen where it say ERROR find the latest Update for RUU. THE second one of em , once i run the program and pop-up screen comes where you accept the terms & conditions, once I do accept it; It closes OUT by itself.
I'VE DONE THE BEST I CAN DO , and I'm very frustrated right now. I've look and look and research, But nothing solve my problem, and I APOLOGIZE FOR THIS LONG ARTICLE/QUESTION. But I'm asking for anyone help who can help me get back this phone back on its feet and I will very appreciate for your help !
P.S. I can't get S-OFF , I want to use my AT&T sim card in it.
ilovetechnology123 said:
Okay, first thing first. (INFO ON PHONE) I have a HTC One (M7wls) Sprint 36GB phone. Phone is ROOTED.
bootloader:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.55.0000
OpenDSP-v32.120.274.0909
OS-3.05.651.6
eMMC boot 2048MB
What can I access:
Fastboot
ADB Sideload
Recovery - I am using custom recovery - openrecovery-twrp-2.6.3.0-m7wls
Now the problem is:
When I install a ROM. Every ROM that I use didn't fully complete installing. When it boot up, can't access home screen, like i can't even do nothing, If I'm not making any sense what I'm trying, basically I don't have no OS-install. And when I install a ROM and do the ADB sideload and install em I just can't get to the home screen , farthest I can go is the lockscreen, but then that don't even act right, as in either it don't want to slide up (by the way my screen work and digitizer) or its blank/black and I can even slide it up, or as i should say froze for about few sec, AND when i can slide up the lockscreen it goes to the white HTC logo screen and stays there about 45-60sec and Reboot over and over, until i go into either recovery or bootloader and power it down.
ROMs that I've downloaded and install but don't completely works:
- Android_Revolution_HD-One_51.0
- One_4.19.401.8_odexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Sprint_HTC_One_Stock_Rooted_Odexed_3.05.651.6
- viperROM_One_v1.0.4
What I'm saying is that, for example of What I do to install:
-Boot in Recovery
-Format Data (so i can mount data)
-Erase cache
-Reboot recovery (so the updating partition data can refresh)
-Access ADB Sideload
-Install a ROM (once complete) i reboot the phone
-After all the boot up LOGOs, WHEN I get to the lockscreen it either , 1. don't want to slide up, 2. when do slide up goes to white HTC logo screen get stays about 60sec, then Reboot itself , and 3. Just done want to boot up
Also have Tried RUUs: and Yes I unzip to run the Ruu.exe
- Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
- Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Also and Yes I re-lock my bootloader to run the RUU , still doesn't happen
I'm not sure which one have this problem, but one of em, Do go through the process and once I get to the part to update Image (I realized my phone image is newer than the RUU image) so i proceed anyways, then it comes to a screen where it say ERROR find the latest Update for RUU. THE second one of em , once i run the program and pop-up screen comes where you accept the terms & conditions, once I do accept it; It closes OUT by itself.
I'VE DONE THE BEST I CAN DO , and I'm very frustrated right now. I've look and look and research, But nothing solve my problem, and I APOLOGIZE FOR THIS LONG ARTICLE/QUESTION. But I'm asking for anyone help who can help me get back this phone back on its feet and I will very appreciate for your help !
P.S. I can't get S-OFF , I want to use my AT&T sim card in it.
Click to expand...
Click to collapse
I had a similar problem. Turned out to be a firmware issue.
Boot into fastboot and connect to your computer.
run "fastboot getvar all"
See what firmware you are running.
Pull the firmware from post #3 on Bad Boyz thread
http://forum.xda-developers.com/showthread.php?t=2635051
and run.. the flash is there twice, make sure and do it twice.. it's not a typo.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
If you still have trouble, try flashing an older firmware from here..
http://forum.xda-developers.com/showthread.php?t=2503646
In my situation, I flashed to 3.05.651.6 and it would boot, but once I connected to the PC and tried to access the storage on the phone, it would reboot the phone.
Flashing to 4.06.651.4 fixed everything.
Look HERE for the 3.05.651.6 RUU or you can go thru the steps to fix your phone.
From now on stay in the Sprint section to find roms
Puff1911 said:
I had a similar problem. Turned out to be a firmware issue.
Boot into fastboot and connect to your computer.
run "fastboot getvar all"
See what firmware you are running.
Pull the firmware from post #3 on Bad Boyz thread
http://forum.xda-developers.com/showthread.php?t=2635051
and run.. the flash is there twice, make sure and do it twice.. it's not a typo.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
If you still have trouble, try flashing an older firmware from here..
http://forum.xda-developers.com/showthread.php?t=2503646
In my situation, I flashed to 3.05.651.6 and it would boot, but once I connected to the PC and tried to access the storage on the phone, it would reboot the phone.
Flashing to 4.06.651.4 fixed everything.
Click to expand...
Click to collapse
Do I need a RUU
Puff1911 said:
I had a similar problem. Turned out to be a firmware issue.
Boot into fastboot and connect to your computer.
run "fastboot getvar all"
See what firmware you are running.
Pull the firmware from post #3 on Bad Boyz thread
http://forum.xda-developers.com/showthread.php?t=2635051
and run.. the flash is there twice, make sure and do it twice.. it's not a typo.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
If you still have trouble, try flashing an older firmware from here..
http://forum.xda-developers.com/showthread.php?t=2503646
In my situation, I flashed to 3.05.651.6 and it would boot, but once I connected to the PC and tried to access the storage on the phone, it would reboot the phone.
Flashing to 4.06.651.4 fixed everything.
Click to expand...
Click to collapse
When doing the fastboot commands, it gives me error twice when doing the firmware and YES I renamed it to "firmware.zip"
gives me error message saying "cannot open" and also re-type in command again , same error
hmm.. let me try to duplicate my error later today on one of my test phones and i'll get back to you.
What ROM are you trying to install?
ilovetechnology123 said:
When doing the fastboot commands, it gives me error twice when doing the firmware and YES I renamed it to "firmware.zip"
gives me error message saying "cannot open" and also re-type in command again , same error
Click to expand...
Click to collapse
Make sure it's firmware.zip and not firmware.zip.zip
Window hides extentions as least on my machine it does.
So rename it just firmware and see if that helps
BD619 said:
Make sure it's firmware.zip and not firmware.zip.zip
Window hides extentions as least on my machine it does.
So rename it just firmware and see if that helps
Click to expand...
Click to collapse
That was my mistake, but rename it to "firmware" . now its working. Phone is back up on its feet. lol.
Just want to say thank you for your support and help. Phone is flawless, Thanks you so much again.
HAVE A BLESSED DAY !
I did the same thing by accident. Flashed the old firmware instead of the new by accident and then kept trying to update with the same problems. Since only the first and last digits of the firmware are different and I had them in the same folder I just grabbed the wrong one. All was fixed as with you when I corrected my firmware.
Lately my phone has been rebooting itself quite a bit. It seems to be getting progressively worse to the point where if I open any app for more than a minute or two then my phone will reboot. I've tried uninstalling quite a few third party apps but that didn't do the trick. Whenever I try to do a hard reset (whether it's through settings or the HBOOT menu) the phone will shut down and then instead of getting the picture of a phone with the green thing in the middle and a status bar below that indicating the phone is resetting, I get a picture of a phone with a red symbol similar to a hazard sign that will last for about 30 seconds then the phone just boots back up to my home screen. I had put an incorrect custom ROM on this phone about 5-6 months ago but I was able to get the stock Sprint ROM back on the phone and relock the boot loader and the phone functioned fine ever since up until about a week ago when it started rebooting randomly. I have a feeling this may be part of the reason why the factory reset is not working. Does anyone have any ideas on how to proceed? Can I do a factory reset by pushing a ROM to the phone through my computer?
If u are s-off then I suggest u download the ruu and run it. If s-off all u have to do is go to hboot and select fast boot and run the program it will reset the phone back to whatever software version it is for the ruu. If your not s-off you will need to get the ruu that matches your firmware. That should fix your troubles if not then you have something faulty with the hardware itself
Sent from my iPad using Tapatalk
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
coppertop4646 said:
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
Click to expand...
Click to collapse
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
luigi311 said:
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ok I tried that RUU yesterday and couldn't seem to get anywhere because I kept getting error 170 (tried updating drivers, installing HTC sync, etc). Tried again today and got error 170 again, so then I went in my bootloader, then fastboot, connected USB cable, fastboot usb. I then ran the RUU and it said it was going to update my phone. The status bar then said "Waiting for bootloader" and my phone just rebooted itself to the home screen and then I got like error 171 or something (another USB error). I'm kind of running out of ideas at this point. I believe something is wrong with my recovery or I have some sort of bug because I attempted to flash a custom recovery today (TWRP) but when I unlocked my bootloader, I restarted the phone and entered my bootloader again but it still said relocked (even though the prompt on my phone came up giving me the warnings asking if I was sure I wanted to unlock the bootloader) so when I run the command fastboot flash recovery twrp.img I get something along the lines of can't read twrp.img or can't open twrp.img (yes I made sure the file is in the same folder that I am running the adb out of). Willing to try any recommendations at this point because my phone is pretty useless as of right now because it restarts every couple minutes. HTC wants $150 to fix it which I told them I'm not willing to pay, rather buy a new phone.
Coucou !
I need to put my HTC Desire C back as new, therefore I looked for RUU stuff.
I checked this post: http://forum.xda-developers.com/showthread.php?t=2035480, trying to follow it the more I can. HTC Sync as well as Android SDK (up to date) are present on my laptop using Windows 7 64.
1. I re-lock the phone: fastboot oem lock.
2. I downloaded the RUU from: http://www.androidruu.com/?developer=Golf, file: RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed.exe
3. I ran with administrator rights the RUU til first screen, asking for agreement.
4. I extracted the recovery_signed.img and flashed it. Fine.
5. I followed the instructions on the screen.
6. It says (translation from french, sorry if it's not exactly what you'll have on an english screen): "checking", "rebooting to bootloader", "waiting for bootloader", "erase user's data" and finally "sending". On my phone screen, there is a white HTC on a black screen.
And it is stuck there. I waited for an hour, still there.
When I disconnect the phone, it says:
- On my computer: error 155: error to image update
- On my phone: a white RUU on an orange background, under classical "*** Relocked ***" (and sometimes "*** Security warning ***") and "GolfU PVT SHIP S-ON RL", then "HBOOT-1.31.000", then "RADIO-1.10.98.15", then "eMMC-boot", then "Jul 12 2012, 15:44:30".
I followed the instruction to "recover" (correct ? button at the bottom and righ of the window), nothing good. I restarted the phone, the laptop, nothing changes.
What can I do?
If you want, I can take screen captures to show you.
i think you also need to flash the stock boot.img
Coucou Bogdy,
First of all, I'd like to thank you for your answer. But, sadly, it didn't work.
I flashed the boot.img, extracted from the "temp" directory , like this:
Code:
fastboot flash boot boot.img
I ran the program and the same thing, stuck on HTC logo, then started the repair stuff, and again stuck on HTC logo.
Does somebody have an idea?
you could also try flashing a stock rom+boot+recovery from http://forum.xda-developers.com/showthread.php?t=2220396&page=2
from what i experienced with a stock based custom rom is that when activating data connection the phone restarts(radio versions differ) so this could happen with a stock rom(not sure)
as for the RUU,i've read that if the hboot version on the phone is higher than the RUU's it won't flash. also i think that the RUU you have only works on european CID but i could be wrong.
you should wait for a more "PRO" answer
Thanks again for your answer, Bogdy.
I'm downloading from the link from the post you suggest me. When it's finished, good or bad, I'll come back.
Coucou !
Well done. Now it's OK, I could flash the original ROM and the phone works perfectly.
Thank you for your help.
BBBenj said:
Coucou !
Well done. Now it's OK, I could flash the original ROM and the phone works perfectly.
Thank you for your help.
Click to expand...
Click to collapse
You could also do this: - lock bootloader
- power on device
- enable adb debugging on device
- make sure you have adb and fasboot working corectly
- connect device via usb to PC
- run RUU with administrator rights
- and from there on just follow the instructions given by software
you really need the 2-4 lines i mentioned up for this to work
no need to flash anything recovery or boot if it's an .exe
if it's a .zip you need to :
flash via custom recovery and flash boot and recovery via fastboot
Coucou Makerrr,
More or less, it is what I've done. I haven't check if adb were working, nevertheless. So it may be the cause of all my problems. But I won't know because I followed Bogdy's way and the job is done, the phone is completly configured, and already in my wife's hand.
Next time, I'll try your way. So thanks a lot.
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
PrimalMK said:
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
Click to expand...
Click to collapse
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
clsA said:
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
Click to expand...
Click to collapse
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version of TWRP does not work. I have no preferences when it comes to OS's. A stock OS (is OS and ROM the same thing?) would be fine.
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
PrimalMK said:
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version does not work. I have no preferences. A stock OS (is OS and ROM the same thing?) would be fine.
Click to expand...
Click to collapse
Well your going to need adb / fastboot on your PC
use mine here >> https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip
and install the HTC Drivers here >> http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
unzip that to c:\ so you have c:\fastboot in windows explorer
now inside the folder you shift + right click / command prompt here
now you have a command prompt window type
fastboot getvar all
and post the result here / minus your serial number and IMEI
then i can find you the correct recovery and rom for your phone
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
PrimalMK said:
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
Click to expand...
Click to collapse
yes window 8 will be a problem till you get another hboot above 1.44/1.54
hboot 1.55 has no problem on windows 8 ( I use windows 8.1)
clsA said:
instructions
Click to expand...
Click to collapse
Downloaded fastboot, unzipped in c:
Drivers from that link are classed as malware. Trying to find earlier drivers/other mirror.
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
PrimalMK said:
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
Click to expand...
Click to collapse
this will work fine
just put TWRP and the Rom in the fastboot folder
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
clsA said:
this will work fine
just put TWRP and the Rom in the fastboot folder
Click to expand...
Click to collapse
error: cannot open 'openrecovery.......img'
What to do?
PrimalMK said:
error: cannot open 'openrecovery.......img'
What to do?
Click to expand...
Click to collapse
is it in the fastboot folder ?
clsA said:
is it in the fastboot folder ?
Click to expand...
Click to collapse
Yes, see screenshot.
PrimalMK said:
Yes, see screenshot.
Click to expand...
Click to collapse
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
clsA said:
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
Click to expand...
Click to collapse
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
PrimalMK said:
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
Click to expand...
Click to collapse
fastboot crashes ?
no if fastboot getvar worked it will all work
it's only 4 commands and your phone will be working
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb sideload rom.zip
sideload takes about 8 min
calculation icatkg
clsA said:
fastboot crashes ?
no if fastboot getvar worked it will all work
Click to expand...
Click to collapse
Restarted a couple of times etc. It worked. Will do the ROM thing now.
PrimalMK said:
Restarted a couple of times etc. It worked. Will do the ROM thing now.
Click to expand...
Click to collapse
great your about done ...your phone will be android 4.3 when it finishes
don't take any updates to the OS
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
PrimalMK said:
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
Click to expand...
Click to collapse
no problem, hit the thanks button