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 ?
I have a Sprint HTC One running 4.2.2 (3.05.651.6) stock rom and TWRP recovery. It is unlocked and unrooted at the moment. It randomly took a nose dive the other day and has been stuck in either boot loop or bootloader/ fastboot usb. If I try to reboot, reboot-bootloader, factory reset, lock the bootloader, etc it boot loops on the white htc screen.
I have tried to flash the recovery again and erase cache with no luck. I've tried to flash a stock rooted rom using RUU and fastboot with no luck, it just boot loops.
I have had extensive help from @benny3 and we can't figure this out.
I found these links to be insightful and possibly a fix but to repair the EMMC if that is the issue, I first need to get my recovery up and running.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
http://forum.xda-developers.com/showthread.php?p=49965919
Any ideas on how to do this since it seems that my recovery is corrupt because I can't get into despite flashing CWR and TWRP (I can't overwrite TWRP).
Any input is helpful as I has exhausted everything I can think of and nothing works.
Does your computer see the One when it's in fastboot mode?
And if I understand properly..
fastboot oem lock
won't 'Relocked' your phone? When it white screen bootloops does it go to bootloader mode, or back into fastboot mode?
Whenever I've mucked something up beyond repair (you'll lose data)
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format sdcard
*fastboot format recovery* never tried this one, but if you have a botched recovery partition this could cause a problem
fastboot reboot-bootloader
fastboot oem lock
have been my failsafes for getting things back to order (ie: reRUUing).
Probably unrelated and unnecessary (but for info completeness sake) what hboot are you on? If you are on Windows 8/8.1, 1.44/1.54 hboots don't work (1.55 does) and you'll need Windows 7 (or linux) to be able to talk in fastboot.
If you happen to be s-off,
fastboot oem rebootRUU
will let you bypass everything and go straight into RUU reflash mode.
Haven't heard of any irrecoverable emmc errors with the One yet, but I may just not have looked hard enough. First time I legit hardbricked my Sprint GS2 I ebay'd a jtag debugger to get things back.
pbassjunk said:
Does your computer see the One when it's in fastboot mode?
And if I understand properly..
fastboot oem lock
won't 'Relocked' your phone? When it white screen bootloops does it go to bootloader mode, or back into fastboot mode?
Whenever I've mucked something up beyond repair (you'll lose data)
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format sdcard
*fastboot format recovery* never tried this one, but if you have a botched recovery partition this could cause a problem
fastboot reboot-bootloader
fastboot oem lock
have been my failsafes for getting things back to order (ie: reRUUing).
Probably unrelated and unnecessary (but for info completeness sake) what hboot are you on? If you are on Windows 8/8.1, 1.44/1.54 hboots don't work (1.55 does) and you'll need Windows 7 (or linux) to be able to talk in fastboot.
If you happen to be s-off,
fastboot oem rebootRUU
will let you bypass everything and go straight into RUU reflash mode.
Haven't heard of any irrecoverable emmc errors with the One yet, but I may just not have looked hard enough. First time I legit hardbricked my Sprint GS2 I ebay'd a jtag debugger to get things back.
Click to expand...
Click to collapse
fastboot oem lock reboots my phone and goes into a boot loop. I have to manually get it back into bootloader. From there I can go back into fastboot
I'm running hboot 1.55. I have tried the above commands on Windows XP and Vista and MacOSX with the same results. Do you think Windows 7 will help? I can try my brother's computer.
And I'm s-on so i can't fastboot oem rebootRUU
And for the jtag debugger don't you have to tear the phone apart. HTC One can't be taken apart easily, it damages the casing
If you can get to bootloader you should be able to RUU
pbassjunk said:
Does your computer see the One when it's in fastboot mode?
And if I understand properly..
fastboot oem lock
won't 'Relocked' your phone? When it white screen bootloops does it go to bootloader mode, or back into fastboot mode?
Whenever I've mucked something up beyond repair (you'll lose data)
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format sdcard
*fastboot format recovery* never tried this one, but if you have a botched recovery partition this could cause a problem
fastboot reboot-bootloader
fastboot oem lock
have been my failsafes for getting things back to order (ie: reRUUing).
Probably unrelated and unnecessary (but for info completeness sake) what hboot are you on? If you are on Windows 8/8.1, 1.44/1.54 hboots don't work (1.55 does) and you'll need Windows 7 (or linux) to be able to talk in fastboot.
If you happen to be s-off,
fastboot oem rebootRUU
will let you bypass everything and go straight into RUU reflash mode.
Haven't heard of any irrecoverable emmc errors with the One yet, but I may just not have looked hard enough. First time I legit hardbricked my Sprint GS2 I ebay'd a jtag debugger to get things back.
Click to expand...
Click to collapse
BD619 said:
If you can get to bootloader you should be able to RUU
Click to expand...
Click to collapse
when you say RUU do you mean using fastboot, cuz I actually tried that last night and it failed and went into a boot loop. I also tried using RUU on my computer with my phone initially in fastboot usb. When it rebooted into bootloader it went into a boot loop as well. I had to manually go into bootloader again and then the program failed
BD619 said:
If you can get to bootloader you should be able to RUU
Click to expand...
Click to collapse
I tried these commands and also tried to unlock the bootloader but they all failed when running
I have the same problem just with verizon htc one
can boot only to hboot
any other mode (recovery, factury reset, check crc, reboot RUU) unavailable. Phone just bootloops on white htc logo
can not unlock boot, verizon phones restricted on htc-dev site
I have this problem in ONE M7 S-ON
no solution to restore; ;
thanks
jondon156 said:
I have a Sprint HTC One running 4.2.2 (3.05.651.6) stock rom and TWRP recovery. It is unlocked and unrooted at the moment. It randomly took a nose dive the other day and has been stuck in either boot loop or bootloader/ fastboot usb. If I try to reboot, reboot-bootloader, factory reset, lock the bootloader, etc it boot loops on the white htc screen.
I have tried to flash the recovery again and erase cache with no luck. I've tried to flash a stock rooted rom using RUU and fastboot with no luck, it just boot loops.
I have had extensive help from @benny3 and we can't figure this out.
I found these links to be insightful and possibly a fix but to repair the EMMC if that is the issue, I first need to get my recovery up and running.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
http://forum.xda-developers.com/showthread.php?p=49965919
Any ideas on how to do this since it seems that my recovery is corrupt because I can't get into despite flashing CWR and TWRP (I can't overwrite TWRP).
Any input is helpful as I has exhausted everything I can think of and nothing works.
Click to expand...
Click to collapse
try fastboot boot recovery.img
Same issue
I have the same problem on my Verizon HTC One M8. I was wondering if you were able to get your phone up and running again. If so, what/how did you do it?
I actually can get into recovery - adb sideload will not work any wiping or formatting I does NOT in fact wipe anything. I've tried recovering nandroid(s) and installing ROMs but same boot loop.
No fix??
Has anyone been able to fix their phone.
I'm also having same issue .. Tried everything nothing works ..
http://forum.xda-developers.com/htc-one/help/htc-one-m7-802d-booting-cleaner-killed-t3438530
Hello everyone, I'm also having the same problem with my HTC mini. I'm pretty sure the emmc got corrupted.
I have tried everything that was out there.
Can't unlock, at least it doesn't show unlocked, but send code successfully that I got from htcdev.
Can't twrp, since I'm locked. Can't flash Rom.zip that I extracted from the ruu.
On Windows I get 171 error. I have the correct drivers and fasboot works . I'm s-on , so I tried higher version from stock image.
Has anyone fixed their emmc ? If so, how'd u do it?
Thanks guys and good luck to all
davipaulo9 said:
On Windows I get 171 error. I have the correct drivers and fasboot works . I'm s-on , so I tried higher version from stock image.
Click to expand...
Click to collapse
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.
coal686 said:
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.
Click to expand...
Click to collapse
I tried that before, fasboot sees the phone but adb does not .
I think the emmc might be bad. I got the right ruu. Took from HTC website . Can't unlock either
---------- Post added at 10:13 AM ---------- Previous post was at 10:10 AM ----------
coal686 said:
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.
Click to expand...
Click to collapse
I,tried all that, I got correct ruu from HTC site.
Using usb 2.0 fastboot sees the phone but adb does not .
I might have corrupted emmc
---------- Post added at 10:13 AM ---------- Previous post was at 10:13 AM ----------
coal686 said:
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.
Click to expand...
Click to collapse
I,tried all that, I got correct ruu from HTC site.
Using usb 2.0 fastboot sees the phone but adb does not .
I might have corrupted emmc
davipaulo9 said:
I,tried all that, I got correct ruu from HTC site.
Using usb 2.0 fastboot sees the phone but adb does not .
I might have corrupted emmc
Click to expand...
Click to collapse
Maybe, but I've had that issue (where fastboot sees the phone and adb doesn't) and nothing was corrupt on the phone. It was a driver issue. But the ruu still worked for me.
coal686 said:
Maybe, but I've had that issue (where fastboot sees the phone and adb doesn't) and nothing was corrupt on the phone. It was a driver issue. But the ruu still worked for me.
Click to expand...
Click to collapse
I don't think it's a driver issue, but I'm not sure.
Fastboot sees the devices and in Windows also it's recognized on device manager . How can I check the emmc for errors and is it possible to repair?
---------- Post added at 01:45 PM ---------- Previous post was at 12:47 PM ----------
coal686 said:
Maybe, but I've had that issue (where fastboot sees the phone and adb doesn't) and nothing was corrupt on the phone. It was a driver issue. But the ruu still worked for me.
Click to expand...
Click to collapse
This is what I get running fastboot oem rebootruu
cmd18 polling stattus times out , MCI _status: 0x4C2000
davipaulo9 said:
I don't think it's a driver issue, but I'm not sure.
Fastboot sees the devices and in Windows also it's recognized on device manager . How can I check the emmc for errors and is it possible to repair?
---------- Post added at 01:45 PM ---------- Previous post was at 12:47 PM ----------
This is what I get running fastboot oem rebootruu
cmd18 polling stattus times out , MCI _status: 0x4C2000
Click to expand...
Click to collapse
From what I'm reading, the partitions might be shot. What does "fastboot getvar all" say?
coal686 said:
From what I'm reading, the partitions might be shot. What does "fastboot getvar all" say?
Click to expand...
Click to collapse
It spits out this message
coal686 said:
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.
Click to expand...
Click to collapse
Tried that, didn't work.
I'm using usb 2.0 uninstall HTC sync , got right ruu. Any other thoughts?
I'm on CM11 which has been working for weeks, last night my phone died completely and when I put it in the charger it wouldn’t light up no matter which outlet/cord I used. It reboots itself after a few seconds of being on, and so soon that I cant enter into recovery or select factory reset under recovery from bootloader because it selects recovery for me and then turns off. My Hboot is 1.44, S-on, its rooted as well. I have reached the edge of my competence, I'd really appreciate any and all help.
nicksperception said:
I'm on CM11 which has been working for weeks, last night my phone died completely and when I put it in the charger it wouldn’t light up no matter which outlet/cord I used. It reboots itself after a few seconds of being on, and so soon that I cant enter into recovery or select factory reset under recovery from bootloader because it selects recovery for me and then turns off. My Hboot is 1.44, S-on, its rooted as well. I have reached the edge of my competence, I'd really appreciate any and all help.
Click to expand...
Click to collapse
first try to re-flash your recovery to resolve
if not, you must flash stock ROM :
turn your phone on in bootloader mode or RUU mode (fastboot oem rebootRUU)
find your right RUU.exe from here > flash it
Note : you must flash the correct RUU that meet your CID & MID
if you can't know/find the correct RUU?, post your CID & MID
moha_moha20106 said:
first try to re-flash your recovery to resolve
if not, you must flash stock ROM :
turn your phone on in bootloader mode or RUU mode (fastboot oem rebootRUU)
find your right RUU.exe from> flash it
Note : you must flash the correct RUU that meet your CID & MID
if you can't know/find the correct RUU?, post your CID & MID
Click to expand...
Click to collapse
i dont know how to run adb commands when my phone wont turn on long enough to get registered by adb or the computer its on. it cant stay in bootloader for more than a few seconds, cant go into fastboot nor recovery. my radio is 4A 14.3250.13 and my phone is for AT&T, is that helpful?
it seems that there is nothing left to do with the phone. no fastboot, no recovery, no factory reset, no computer recognition. no adb/fastboot command gets the phone to be recognized. i have the latest htc drivers installed manually but when the computer recognizes there is a usb anything it tries to install the drivers but the phone quickly turns off and the driver installation fails. adb devices comes up empty, getvar cid keeps waiting for device forever, and trying to push files doesn’t work because it cant recognize it's there in the first place. is there anything I can do?
Here is the bootloader page I see if it helps.
nicksperception said:
Here is the bootloader page I see if it helps.
Click to expand...
Click to collapse
first, you must hit THANKS if anyone try to help you, or reply to help you
read this post if you need to learn more about ADB / Fastboot commands
Maybe my topic will help you (it's just one page back) http:// http://forum.xda-developers.com/showthread.php?t=2707187
detovenaar said:
Maybe my topic will help you (it's just one page back) http://forum.xda-developers.com/showthread.php?t=2707187
Click to expand...
Click to collapse
you link was broken
@nicksperception
try the link in my Quote above
detovenaar said:
Maybe my topic will help you (it's just one page back) http:// http://forum.xda-developers.com/showthread.php?t=2707187
Click to expand...
Click to collapse
I appreciate the help but I cant even get my phone to be recognized in fastboot or adb. It said "waiting for device" when i tried to get my cid for hours. It turns off too quickly for the computer to recognize it. Did you have this problem? If so how did you fix it?
Hi, recently I owned my HTC desire 626s but when I was unlocking bootloader and rooting accidentally I broke the system and now sends failure messages all time. could someone make a clean rom stock backup and upload it for flash it?
Could use one too
AlexLeonVader said:
Hi, recently I owned my HTC desire 626s but when I was unlocking bootloader and rooting accidentally I broke the system and now sends failure messages all time. could someone make a clean rom stock backup and upload it for flash it?
Click to expand...
Click to collapse
This would also help me out as i accidentally deleted os while trying to reset with twrp.
Lol... Back up is 5gb.. Not only that, TWRP for this device as of now has bugs and will break root after nandroid restore. Download RUU from HTC website put RUU in adb folder and put phone into download mode. Thru adb type in "fastboot oem rebootRUU". Run RUU on PC (DO NOT UNPLUG USB). Process takes about 10-15mins so be patient and your phone will be back to stock.
I tried it and it finished way to fast. The device is not in adb devices. After accidentaly trying to reset thru twrp now my device wont show up untill i boot into twrp. Any idea of whats wrong. I have the right files in the same location as adb. I have the updates htc drivers for my device.
After typing fastboot oem rebootRUU all i got was a silver htc logo with a security warnig about non htc roms.
f1tzg3r4ld said:
I tried it and it finished way to fast. The device is not in adb devices. After accidentaly trying to reset thru twrp now my device wont show up untill i boot into twrp. Any idea of whats wrong. I have the right files in the same location as adb. I have the updates htc drivers for my device.
After typing fastboot oem rebootRUU all i got was a silver htc logo with a security warnig about non htc roms.
Click to expand...
Click to collapse
Yea ur on the right path. Now open RUU file and let it load and execute on your PC and it should restore stock metro rom. Process takes awhile so be patient
kdayyy said:
Yea ur on the right path. Now open RUU file and let it load and execute on your PC and it should restore stock metro rom. Process takes awhile so be patient
Click to expand...
Click to collapse
After I run ruu.exe for my device nothing happens. I let it sit for an hour. I think I can get this fixed but after accidentally deleting things with twrp tryign to reset now my device is not recognized by adb. I reinstalled the stock recovery thinking that might help and it didnt. I was able to get the rom.zip extracted from the ruu. Do you know what steps I would take to install the rom with the stock recovery. Or do you know how I can reinstall twrp. This phone is about to get thrown against the wall. Its my stupidy for nopt backing up before trying to reset.
f1tzg3r4ld said:
After I run ruu.exe for my device nothing happens. I let it sit for an hour. I think I can get this fixed but after accidentally deleting things with twrp tryign to reset now my device is not recognized by adb. I reinstalled the stock recovery thinking that might help and it didnt. I was able to get the rom.zip extracted from the ruu. Do you know what steps I would take to install the rom with the stock recovery. Or do you know how I can reinstall twrp. This phone is about to get thrown against the wall. Its my stupidy for nopt backing up before trying to reset.
Click to expand...
Click to collapse
Put ur phone in download mode if adb can detect in twrp than it should detect in download mode. It's not gonna show on ur PC that it's detected. Just connected and see if adb work in download mode. Same process download mode and type in "fastboot oem rebootRUU" when it goes to silver HTC logo screen open RUU and run it on your PC make sure you have metropcs RUU
---------- Post added at 09:51 AM ---------- Previous post was at 09:36 AM ----------
Stock recovery doesn't do anything. And why are you extracting RUU? It's not meant to be extracted but to run and execute on adb thru PC
kdayyy said:
Put ur phone in download mode if adb can detect in twrp than it should detect in download mode. It's not gonna show on ur PC that it's detected. Just connected and see if adb work in download mode. Same process download mode and type in "fastboot oem rebootRUU" when it goes to silver HTC logo screen open RUU and run it on your PC make sure you have metropcs RUU
Click to expand...
Click to collapse
I have the stock recovery now and cant figure out how to put twrp back on the phone. Ok put it into download mode and ran
C:\HTC626s>adb devices
List of devices attached
C:\HTC626s>fastboot oem rebootRUU
...
OKAY [ 0.053s]
finished. total time: 0.054s
C:\HTC626s>
as you can see adb doesnt recognize the device. Once the ruu starts the install sheild it loads, I accept terms of the licence and hit next, Then nothing happens. It just sits on ther silver htc logo screen and the ruu installer never shows back up.
https://drive.google.com/file/d/0B7_8Xh6NIsIPOUxFbXNEcnZzTlE/view?usp=sharing
https://drive.google.com/file/d/0B7_8Xh6NIsIPQVkya19vSlBpTmc/view?usp=sharing
When I was trying to reset my phone using TWRP i selected everything and hit wipe. Thats how I got into this mess. Does that tell you anything.
f1tzg3r4ld said:
I have the stock recovery now and cant figure out how to put twrp back on the phone. Ok put it into download mode and ran
C:\HTC626s>adb devices
List of devices attached
C:\HTC626s>fastboot oem rebootRUU
...
OKAY [ 0.053s]
finished. total time: 0.054s
C:\HTC626s>
as you can see adb doesnt recognize the device. Once the ruu starts the install sheild it loads, I accept terms of the licence and hit next, Then nothing happens. It just sits on ther silver htc logo screen and the ruu installer never shows back up.
https://drive.google.com/file/d/0B7_8Xh6NIsIPOUxFbXNEcnZzTlE/view?usp=sharing
https://drive.google.com/file/d/0B7_8Xh6NIsIPQVkya19vSlBpTmc/view?usp=sharing
Click to expand...
Click to collapse
It actually is detected because ur cmd says "<C:\HTC626s>" meaning it's in adb mode and connected. Make sure RUU file is in adb folder. The RUU takes awhile to run. And window will disappear after proceeding, and will run in the PC background and takes approximately 10-20 mins. Took a good 15 mins for me and I don't have the best PC
---------- Post added at 10:17 AM ---------- Previous post was at 10:05 AM ----------
f1tzg3r4ld said:
I have the stock recovery now and cant figure out how to put twrp back on the phone. Ok put it into download mode and ran
C:\HTC626s>adb devices
List of devices attached
C:\HTC626s>fastboot oem rebootRUU
...
OKAY [ 0.053s]
finished. total time: 0.054s
C:\HTC626s>
as you can see adb doesnt recognize the device. Once the ruu starts the install sheild it loads, I accept terms of the licence and hit next, Then nothing happens. It just sits on ther silver htc logo screen and the ruu installer never shows back up.
https://drive.google.com/file/d/0B7_8Xh6NIsIPOUxFbXNEcnZzTlE/view?usp=sharing
https://drive.google.com/file/d/0B7_8Xh6NIsIPQVkya19vSlBpTmc/view?usp=sharing
When I was trying to reset my phone using TWRP i selected everything and hit wipe. Thats how I got into this mess. Does that tell you anything.
Click to expand...
Click to collapse
I've wiped everything before. This is my second HTC device. I had a desire510. Either flash a stable custom ROM which 626s don't have any, or run RUU thru adb is your only option.
I figured it out Thansk for your help I had to run cmd as admin and install this
Microsoft Visual C++ 2008 Redistributable Package (x86)
Because you have the wrong ruu download sprint ruu
:angel::angel:
f1tzg3r4ld said:
After I run ruu.exe for my device nothing happens. I let it sit for an hour. I think I can get this fixed but after accidentally deleting things with twrp tryign to reset now my device is not recognized by adb. I reinstalled the stock recovery thinking that might help and it didnt. I was able to get the rom.zip extracted from the ruu. Do you know what steps I would take to install the rom with the stock recovery. Or do you know how I can reinstall twrp. This phone is about to get thrown against the wall. Its my stupidy for nopt backing up before trying to reset.
Click to expand...
Click to collapse
It Works.
kdayyy said:
Put ur phone in download mode if adb can detect in twrp than it should detect in download mode. It's not gonna show on ur PC that it's detected. Just connected and see if adb work in download mode. Same process download mode and type in "fastboot oem rebootRUU" when it goes to silver HTC logo screen open RUU and run it on your PC make sure you have metropcs RUU
---------- Post added at 09:51 AM ---------- Previous post was at 09:36 AM ----------
Stock recovery doesn't do anything. And why are you extracting RUU? It's not meant to be extracted but to run and execute on adb thru PC
Click to expand...
Click to collapse
I created an account to thank you. Your method worked for me. Thank you so much. My device was soft-bricked from wiping with Cyanogen Recovery. I was stressed out all week looking for a solution and finally found your solution that worked for me. Thank you.
kdayyy said:
Lol... Back up is 5gb.. Not only that, TWRP for this device as of now has bugs and will break root after nandroid restore. Download RUU from HTC website put RUU in adb folder and put phone into download mode. Thru adb type in "fastboot oem rebootRUU". Run RUU on PC (DO NOT UNPLUG USB). Process takes about 10-15mins so be patient and your phone will be back to stock.
Click to expand...
Click to collapse
i know this is an old post but ruu for unlocked 626 is not available on its official website
Good Morning,
I have an HTC One M7 here that no longer works. I found out that I can boot into the HBoot, but I can't really choose anything.
I mean, if I select e.g. Bootloader / Fastboot, then the phone goes into the menu of the bootloader, but after that I can neither select something in the menu nor access the device via Fastboot. (Using Arch Linux with Android Tools)
I also tried going into recovery mode. When I select "Recovery" in HBoot, the phone reboots, gets stuck on the boot logo, and turns off.
I would appreciate any help from you ^^
Cheers,
TheGoliath
Linux have some issues with fastboot drivers.
Try to get an "fastboot getvar all" from windows and post here(remove sn, imei).
lucyr03 said:
Linux have some issues with fastboot drivers.
Try to get an "fastboot getvar all" from windows and post here(remove sn, imei).
Click to expand...
Click to collapse
The same goes for Windows. The phone basically freezes when you select something in HBoot. For example, I'm trying to start from HBoot. When I select Fastboot it brings up the submenu (ok). But I can't move within the entries and it doesn't change from Fastboot to Fastboot USB either when I connect it to a Windows / Linux device with the correct drivers installed. When I try to go into recovery, it vibrates, the HTC logo with the white background appears, and then it turns off.
TheGoliath said:
Same goes for windows. The phone basically freezes when selecting anything in HBoot. For example, I try to fastboot via HBoot, when I select fastboot, it goes to the submenu (all right). But I'm not able to move within the entrys nor it changes from fastboot to fastboot usb when plugging it in to windows/linux device with proper drivers installed. When trying recovery, it vibrates, the htc logo with the white background comes up and then it "turns off".
Click to expand...
Click to collapse
Getting into recovery worked like a few hours ago, but not anymore.
From there I was able to get into the bootloader (still buggy, but I was able to print Vars via Fastboot, for example)
But when trying to RUU (fastboot oem rebootRUU) the phone got stuck with "Verifying: 3". After turning off and restarting the phone, I was greeted by the HTC logo on the black background. Normally I could flash the RUU through Fastboot, but the phone was not recognized by Windows or Linux. Therefore, unfortunately, no success so far.
TheGoliath said:
Getting into the recovery worked like few hours ago, but now it doesn't.
From there I was able to get into bootloader (still buggy but I was able to e.g. print vars via fastboot)
But when trying to RUU the phone (fastboot oem rebootRUU) it got stuck at "verifying: 3". After hard-turning off the phone and starting it again, I was greeted by the htc logo sitting on the black background. Normally I'd be able to flash the RUU through fastboot, but the phone wasn't recognized by windows or linux. Sooo...
Click to expand...
Click to collapse
Yeah, most probably is an hardware issue.
lucyr03 said:
Yeah, most probably is an hardware issue.
Click to expand...
Click to collapse
I agree.
EDIT .: The device was ultimately defective and from then on only served as a paperweight. Nevertheless, thanks for the helpfulness!