Related
So I was really dumb and tried to factory reset my phone while I was on a custom rom and now am stuck in a boot loop. I have been googling around to try and figure out what to do but nothing seems to work. When I try and Hboot an RUU stock file it gets stuck at UserData. I also cannot get into recovery only Hboot.
I am relocked and S-On. Don't know what else to do. Is it beyond repair?
Ok when you run the ruu are you selecting fastboot in the hboot screen ? Does it say USB after fastboot when connected ?
Bigtjmc said:
Ok when you run the ruu are you selecting fastboot in the hboot screen ? Does it say USB after fastboot when connected ?
Click to expand...
Click to collapse
When i hold down power and volume down it goes to the Hboot screen and it automatically looks for the PH39IMG.zip file so no I am not running fastboot but when I do select fastboot it only says fastboot no USB (i do not have it plugged into PC btw).
When you select fastboot , then plug it in the pc and it should go USB , if not you need to install the drivers
If you need the drivers you dl htc sync manager , or dl the toolkit in the dev forum and install them that way .
Fastboot USB is showing up but HTC Sync is saying there are no devices connected, not sure if thats a problem.
Ok did you do this when you ran the ruu ?
brandork said:
Fastboot USB is showing up but HTC Sync is saying there are no devices connected, not sure if thats a problem.
Click to expand...
Click to collapse
HTC sync looks for devices that are powered on...just try and run the ruu..listen to bigtjmc
AND DON'T UNPLUG ONCE IT'S GOING, THE PROCESS TAKES A WHILE...
Sent from my HTC PH39100 using Tapatalk 2
Well I was actually extracting the RUU image from my PC's temp folder then placing it on my phone to allow Hboot to find it. I am now running the actual RUU software on my PC and it seems to be working. I will update when its finished. Thanks so much for your help.
Right on ,
Let us know what happens .
The ruu is stuck at 34%...I have it plugged in still not sure what to do from here
How long has it been stuck?
Don't unplug it...just let it sit...
Sent from my HTC PH39100 using Tapatalk 2
sorry guys I was in class and couldnt respond. so right now i went through the RUU recovery steps and it allowed me to re-do the RUU setup. I just redid it thinking my PC may have messed up but I am stuck at 34% again. Any suggestions for what I should do after I recover it again?
edit: forgot to mention that I left it for a few hours while in class and it took me to the recovery setup
Can you get into recovery when it sends you there ?
no I cannot get into recovery. All i can do is get into fastboot.
Right but what recovery setup you mentioned earlier ? Maybe you got a bad ruu download try and re dl it or try a different version.
Sorry the recovery I mentioned was a recovery process the RUU takes you through when an update fails. I also have tried about 4 different downloads to no avail. I have been using this file here
Ok , what Rom did you have on the phone ?
I couldnt tell you for sure I installed it pretty quickly after the ICS update was available. I want to say I installed one of the HTC Holiday or Raider ICS roms because that was available before the Vivid one. Once that was installed I rooted.
Ok one last thing and I will see what I can come up with , the ruu screen when it stopped at 34% what was it trying or waiting on ?
Seeking some help here.
I am from Singapore and using the HTC international version.
It is (was?) rooted but the camera was giving problems and I sent it in for servicing. Even though the hardware fault has nothing to do with the rooting, I was asked to unroot it into stock and they will service it for me.
Ok, fair enough. So this is what I did.
1. I relocked the bootloader using Fastboot
2. Tried to run the RUU which and it didn't run. I used
RUU_M7_UL_JB_50_hTC_Asia_WWE_1.26.707.5_Radio_4A.13.3231.20_10.30.1131.05_release_309365_signed_2_4.exe
3. Realised that I need to turn S-off before the RUU may work, I tried running the Rumrunner but couldn't get it to work.
4. Rumrunner says I need to check USBdebugging but since I couldn't get the phone running, I couldn't have checked that.
5. I decided to just unlock the bootloader and install a custom rom (was using CM11). Tried to push the Zip by ADB but it fails. The computer recognises the device but after pushing the file, the TWRP screen reads ADB Sideload Complete Failed
6. Possibly unrelated, but I tried to do a wipe on TWRP, it reads Factory Reset Complete Failed
So now I can stuck with a bootloop and can't seem to get anything installed or restored.
Would love to know what should I do in such a situation. Thanks guys.
Hey guys need some help
My HTC M7 was playing up, restarting by itself, etc etc, so i decided to wipe the whole thing and start again, so i have no OS atm, also is s-off
Running TWRM atm as recovery.
Now heres the problem
Sideload hangs at 1%
Push hangs and displays nothing
RUU hangs, wont complete sending
flashing a different recovery hangs (cant anymore as i relocked bootloader as an attempt to use RUU)
cant do anything
Have tried all USB ports, 3 different sets of drivers and tools, and even a toolkit and i am stumped
the tools detect the phone in adb and fastboot, but cant do anything with it
Any adivce?
Make sure your using the proper cable. Alot of these cheap cables have been found to lower the data transfer speed to a point that it hangs. Only thing I can think of
DSX2 said:
Hey guys need some help
My HTC M7 was playing up, restarting by itself, etc etc, so i decided to wipe the whole thing and start again, so i have no OS atm, also is s-off
Running TWRM atm as recovery.
Now heres the problem
Sideload hangs at 1%
Push hangs and displays nothing
RUU hangs, wont complete sending
flashing a different recovery hangs (cant anymore as i relocked bootloader as an attempt to use RUU)
cant do anything
Have tried all USB ports, 3 different sets of drivers and tools, and even a toolkit and i am stumped
the tools detect the phone in adb and fastboot, but cant do anything with it
Any adivce?
Click to expand...
Click to collapse
Do you have HTC sync installed on your pc. its well known for causing these types of problems. If you do try uninstalling HTC sync but leave drivers installed.
Also check your sdk (adb/fastboot) is up to date.
Danny201281 said:
Do you have HTC sync installed on your pc. its well known for causing these types of problems. If you do try uninstalling HTC sync but leave drivers installed.
Also check your sdk (adb/fastboot) is up to date.
Click to expand...
Click to collapse
End up being my cable, which annoyed the crap out of me because i had already tried 3 before posting this
DSX2 said:
End up being my cable, which annoyed the crap out of me because i had already tried 3 before posting this
Click to expand...
Click to collapse
Thats the issue with cables. Most generic cables are not great or useful for data transfering.
DSX2 said:
(...)
is s-off
(...)
i relocked bootloader as an attempt to use RUU
Click to expand...
Click to collapse
Btw you don't need to relock the bootloader to flash a ruu if your phone is s-off.
alray said:
Btw you don't need to relock the bootloader to flash a ruu if your phone is s-off.
Click to expand...
Click to collapse
haha i didnt think i had too, but the guide said too and i was desperate
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.
I got an M9. Wanted to root it to remove bloatware. Everything was going fine until I flashed supersu zip through TWRP. I didn't let TWRP install supersu as per instructions but I ran into the bootloop issue and decided to just go back to stock. Well I made a noob mistake and relocked the bootloader. Now the phone fails to enter recovery and when I reboot, it boots directly into the bootloader. I've been researching for hours and hours trying to find a resolution to just flash the stock RUU but when I run the file it comes up with the error no device is attached. The phone shows up in my device manager just fine but won't connect to ADB or when I tried running the RUU exe even that said there were no devices attached Also my phone is now not able to be found in adb or fastboot. If you could lend any assistance as to what I might be able to do just to even get it back to stock I would greatly appreciate it.
It's a T-Mobile HTC M9
bootloader is showing relocked.
S-On
Thanks for any help.
Update. I tried using Squabbi M9 toolkit but again the same issue with no devices attached. I'm guessing it has to do with usb debugging not being enabled? I'm not sure. It was enabled when I started the whole process but now that I can't boot into the phone itself I can't check anything. If anyone could offer at least a little assistance I would greatly appreciate it.