So I've scoured the internet/Google for HOURS trying to find a solution to my issue. I left my office with my phone charging on a charger plugged into the wall, then came back about 40 minutes later to find my phone black-screened. No charging light on my charger, so I tried a different outlet, a different charger, and still no power. Then I plugged it into my desktop computer and it booted up!! Great!...except, all it DID was boot up to the white HTC screen...and repeated it over and over and over...
After a lot of research and learning a bit about bootloop, I discovered the HBOOT menu, pressing the POWER and VOL DOWN keys at the same time. Luckily, this worked. I managed to find the HBOOT menu, and this is what I was greeted with:
*** LOCKED ***
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.02.01.0818
OpenDSP-v12.120.274.0909
OS-4.09.605.5
eMMC-boot 2048MB
Aug 27 2014, 13:22:15.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Well, the last two options work, and FASTBOOT brings me to another menu screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
And of those, the 2nd and 3rd bring me into bootloop again, and the 4th actually powers it down and sometimes shows me a battery-icon (as my phone would NORMALLY show when powered down and charging, but no charging animation is shown) and a lit charging light, but only briefly before going into bootloop.
Trying RECOVERY brings me into bootloop, and as a last-ditch effort, I tried FACTORY RESET, but that also brought me into bootloop (would trying that have already erased my memory? I haven't backed up my photos and other files in awhile...).
Anyways, if ANYONE can give me ANY help with this, it would be greatly appreciated! THANKS!
-Marc.
You can get into fastboot, good. See if the below can get your phone up and running. If it doesn't work, I don't know if the special commands @dottat knows would work on a locked and s-on device to try and manually repartition. Hopefully he can verify in his free time.
http://forum.xda-developers.com/showthread.php?t=2935556
Sent from my HTC6500LVW using XDA Free mobile app
MarkyMarc413 said:
So I've scoured the internet/Google for HOURS trying to find a solution to my issue. I left my office with my phone charging on a charger plugged into the wall, then came back about 40 minutes later to find my phone black-screened. No charging light on my charger, so I tried a different outlet, a different charger, and still no power. Then I plugged it into my desktop computer and it booted up!! Great!...except, all it DID was boot up to the white HTC screen...and repeated it over and over and over...
After a lot of research and learning a bit about bootloop, I discovered the HBOOT menu, pressing the POWER and VOL DOWN keys at the same time. Luckily, this worked. I managed to find the HBOOT menu, and this is what I was greeted with:
*** LOCKED ***
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.02.01.0818
OpenDSP-v12.120.274.0909
OS-4.09.605.5
eMMC-boot 2048MB
Aug 27 2014, 13:22:15.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Well, the last two options work, and FASTBOOT brings me to another menu screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
And of those, the 2nd and 3rd bring me into bootloop again, and the 4th actually powers it down and sometimes shows me a battery-icon (as my phone would NORMALLY show when powered down and charging, but no charging animation is shown) and a lit charging light, but only briefly before going into bootloop.
Trying RECOVERY brings me into bootloop, and as a last-ditch effort, I tried FACTORY RESET, but that also brought me into bootloop (would trying that have already erased my memory? I haven't backed up my photos and other files in awhile...).
Anyways, if ANYONE can give me ANY help with this, it would be greatly appreciated! THANKS!
-Marc.
Click to expand...
Click to collapse
Figure this out yet?
Uzephi said:
You can get into fastboot, good. See if the below can get your phone up and running. If it doesn't work, I don't know if the special commands @dottat knows would work on a locked and s-on device to try and manually repartition. Hopefully he can verify in his free time.
http://forum.xda-developers.com/showthread.php?t=2935556
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I downloaded the 4.09.605.5 wizard and everytime I try to run it while my phone is connected to my computer, it keeps giving me the ERROR [107]: USB CONNECTION ERROR, even though my FASTBOOT menu says FASTBOOT USB, which I guess means it is connected, but for some reason, the program isn't reading the phone as such.
I also tried downloading the third link in the thread you linked me to, but the folder isn't unzipping for some reason on my computer. Am I doing something wrong or am I missing something?
MarkyMarc413 said:
I downloaded the 4.09.605.5 wizard and everytime I try to run it while my phone is connected to my computer, it keeps giving me the ERROR [107]: USB CONNECTION ERROR, even though my FASTBOOT menu says FASTBOOT USB, which I guess means it is connected, but for some reason, the program isn't reading the phone as such.
I also tried downloading the third link in the thread you linked me to, but the folder isn't unzipping for some reason on my computer. Am I doing something wrong or am I missing something?
Click to expand...
Click to collapse
Connection error could be driver issues. What drivers and OS are on your PC?
That third zip is a flashable firmware for s-off.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
You can get into fastboot, good. See if the below can get your phone up and running. If it doesn't work, I don't know if the special commands @dottat knows would work on a locked and s-on device to try and manually repartition. Hopefully he can verify in his free time.
http://forum.xda-developers.com/showthread.php?t=2935556
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Uzephi said:
Connection error could be driver issues. What drivers and OS are on your PC?
That third zip is a flashable firmware for s-off.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I'm using my office computer at work since my HP Pavilion died on me early last month (Yeah, I've been having bad luck with my tech lately...). I'm running Windows 7 on this Dell desktop, but I'm not sure I have the proper drivers on it for my phone. Unfortunately, I don't have the required ADMIN credentials to run any .exe's to install the proper drivers for my phone (as I just tried that with this link - http://www.theandroidsoul.com/?files_box=d56b9fc4b0f1be8 )
MarkyMarc413 said:
I'm using my office computer at work since my HP Pavilion died on me early last month (Yeah, I've been having bad luck with my tech lately...). I'm running Windows 7 on this Dell desktop, but I'm not sure I have the proper drivers on it for my phone. Unfortunately, I don't have the required ADMIN credentials to run any .exe's to install the proper drivers for my phone (as I just tried that with this link - http://www.theandroidsoul.com/?files_box=d56b9fc4b0f1be8 )
Click to expand...
Click to collapse
Yeah, to have fastboot commands or ruu working, you would need to install drivers and a work PC would not have the correct ones.
Sent from my HTC6500LVW using XDA Free mobile app
Related
//Header information
***UNLOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
eMMC-boot
Hey guys, I recently acquired an EVO 3D in a trade deal and even though I don't want it (I plan on selling it but the cash deal + EVO 3D was worthy), I ended up being hellbent on rooting it last night. Success. Great, I threw Cyanogenmod7 on there and realized I'll have to undo the root/ROM to sell it later. I used what I believe is referred to as the REVOLUTIONARY method (using HTCDev.com, some terminal commands on my Mac, etc.)
Anyhow, didn't think it would be hard to undo what I did and I guess I was wrong. Let me tell you what I've tried so far.
I've tried using the PG86IMG.zip flash and nothing. No option (VOL UP or VOL DOWN) to even TRY installing it. Just quickly flashes the green text "No Image!" under each category (it goes too fast for me to read it) and I'm back at the boot menu. I've tried using different copies of the PG86IMG.zip with the same results (latest site acquired from: Goo-inside me, or something like that).
I've also tried using the RUU*.exe method on a Windows 7 machine. I've installed the drivers, everything checks out just fine until it actually tried to update the ROM. What happens here is that the phone reboots (as expected) and though the splash screen is different (black background with silver/gray hTc logo, semi-reflected) from the usual splash screen (white background with hTc in green), nothing happens. The software on the Windows 7 machine says "Waiting for bootloader" - which never shows up. Then it quickly gives me an error stating that the USB cable between the PC and the phone needs to be checked. Of course, there's no disconnect anywhere in the cables.
Please help! I planned on selling this device but if it's stuck in Cyanogenmod7, especially with no Google apps (couldn't get Gapps*.zip to work but whatever, not really concerned about that right now), there's no way I could sell this thing. I'm fairly knowledgeable in the basics of these matters as I have a rooted EVO 4G as well.
Anyone wanna buy an EVO 3D? HAHA
you could always flash a stock rooted rom .
You've gotta relock through adb before running the RUU.exe; then it'll work.
Hit the thanks if I helped
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
zer0xity said:
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
Click to expand...
Click to collapse
It's because of the pg86img.zip you can delete/move it away from the root of your sd card and get back into recovery... but you shouldn't need to, follow these steps:
1) Turn off phone
2) Hold power+vol down
3) Choose fastboot
4) Plug into your PC if you're not already
5) When you see FASTBOOT USB on the phone screen go back to your command prompt where you have your adb.exe, fastboot.exe, etc.
6) Type: " fastboot oem lock "
7) Aaaand you're done w/ the relocking go crazy and run your RUU.exe, don't reboot the phone or anything just run your RUU while your phone's still in HBOOT.
Edit: Oh, the adb I was talking about would kind of make everything easier; in command prompt: adb reboot bootloader AND THEN fastboot oem lock
Two steps, mhm.
I'm on it! Standby...
Okay, the adb stuff - can I do that from terminal in Mac? I tried doing it while in the appropriate folder where all that adb stuff is and I typed: adb reboot bootloader (ERROR: command not found), then I tried just: reboot bootloader (not permitted). I did try: ./fastboot-mac oem lock (successful. header now says *** RELOCKED ***).
Tried the RUU*.exe stuff on the Windows machine while in that state and again an alleged problem with the USB connection...
Sounds like we're close?
BAM! Got it. You put me on the right track with that last post. RUU still wouldn't do the reversion even though I had some drivers installed on Windows so I had to find some other drivers (some HTC3*.exe file, 13MB) and ended up running those for it to recognize the phone.
+1 to you, sir. Thank you so much!
Glad it all turned out well.
After attempting to S-Off the phone yesterday afternoon and failing (it is unlocked), I'm now stuck at the infamous JPbear screen with the green arrow. I've read pretty much every post I can find on recovering from it and still cannot get the phone to boot correctly.
I flashed the boot img for the rom I was running, I created my own PH98 file with the boot image and AmonRa, I've tried to flash a complete rooted Global stock rom, as well as attempting a full flash of the rom I was running. The PH files seem to process correctly but when done I get a messaging it is parsing the file but nothing happens afterwards. On reboot I get the white HTC screen then straight to the black JPBear screen. The phone also does not recognize that it is plugged into my laptop or a wall charger, there are no LED's lit. Without the USB I cannot relock the phone so I cannot flash back to a stock RUU. Fastboot\Min-ADB\Controlbear all fail as the phone is not recognized.
Are there any other things I can try before I give up. I'm not sure if the S-Off attempt may have damaged the USB or not but it definitely does not respond. I do have the extended warranty on the phone but returning it would be a last resort.
I apologize for asking the same questions as many others but I have not been able to find an answer despite searching for most of the night.
controlbear - r
Straight from the troubleshooting page: http://unlimited.io/jbtroubleshooting.htm
shrike1978 said:
controlbear - r
Does not work. I've read the troubleshooting page and tried everything I could find before posting. Controlbear returns an error it cannot find the phone and prompts me to install the drivers and reboot. Fastboot and mini-adb return similar results (phone is not detected).
Thanks for the input.
Click to expand...
Click to collapse
Did you try placing a rom on your sdcard and flashing it in recovery, or just simply placing a signed PH98IMG.zip on your sdcard (meaning the official update)?
brando56894 said:
Did you try placing a rom on your sdcard and flashing it in recovery, or just simply placing a signed PH98IMG.zip on your sdcard (meaning the official update)?
Click to expand...
Click to collapse
I did try a ROM but have no access to recovery. When I select it fro the hboot menu, the screen flashes for a second and then goes back to hboot. I cannot load the stock RUU because the bootloader is unlocked and I have read there is no way to relock it without working USB.
Thanks for the suggestions, I appreciate the imput.
control bear makes a back up before doing the wire trick. just restore the back up?
synisterwolf said:
control bear makes a back up before doing the wire trick. just restore the back up?
Click to expand...
Click to collapse
I tried that but no go. The main issue comes down to not getting the phone recognized by the laptop. The USB port on the phone does not recognize when it is plugged in (either to a PC or the wall charger). Controlbear or other utilities cannot find the phone so I cannot execute any commands. I've been searching for a strictly SD based solution but I am SOL.
Thanks though.
gskuse said:
I tried that but no go. The main issue comes down to not getting the phone recognized by the laptop. The USB port on the phone does not recognize when it is plugged in (either to a PC or the wall charger). Controlbear or other utilities cannot find the phone so I cannot execute any commands. I've been searching for a strictly SD based solution but I am SOL.
Thanks though.
Click to expand...
Click to collapse
Can you see hboot at all?
Sent from my iPhone...
synisterwolf said:
Can you see hboot at all?
Sent from my iPhone...
Click to expand...
Click to collapse
I can boot to hboot by using power and volume keys, but I have no recovery when I select that choice. If I choose Fastboot, it will try to load a PH image if present but when it completes it says "parsing file" and then goes back to the hboot menu.
gskuse said:
I can boot to hboot by using power and volume keys, but I have no recovery when I select that choice. If I choose Fastboot, it will try to load a PH image if present but when it completes it says "parsing file" and then goes back to the hboot menu.
Click to expand...
Click to collapse
if you can get to hboot then you should ruu. it will get your phone back to working order. just make sure you oem lock before doing it if you are s-on
synisterwolf said:
if you can get to hboot then you should ruu. it will get your phone back to working order. just make sure you oem lock before doing it if you are s-on
Click to expand...
Click to collapse
I cannot relock the bootloader without access to to the phone. The laptop does not see the phone when connected to it. I cannot run the relock tool. I think the port actually died. No LED when plugged in to a wall charger or laptop USB cable. I have not been able to locate a way to relock the bootloader using the SD card.
Thanks again.
gskuse said:
I cannot relock the bootloader without access to to the phone. The laptop does not see the phone when connected to it. I cannot run the relock tool. I think the port actually died. No LED when plugged in to a wall charger or laptop USB cable. I have not been able to locate a way to relock the bootloader using the SD card.
Thanks again.
Click to expand...
Click to collapse
idk how to help then. Im sorry. can you charge the phone in any way? if not then i would let it die and send it in as a warranty replacement.
synisterwolf said:
idk how to help then. Im sorry. can you charge the phone in any way? if not then i would let it die and send it in as a warranty replacement.
Click to expand...
Click to collapse
Nah no way to charge the battery. I have a VZW store near me and will take it there for a swap.
I really appreciate your help though.:good:
The only way to recover with the control bear program is to place all the files in its own folder and then CD to that folder and run from there.I had to recover my phone once. Took me a few minutes to wrap my mind around it. Just keep reading until it makes sense.
I pretty much screwed my phone so bad, and I can't seem to the find any solution anywhere...
Here's what I did in order:
-tried rooting it with this guy's guide [link taken down since im a new member, but it's on htconeroot dot com//htc-one-root/how-to-root-htc-one-windowsmaclinux/]
[keep in mind it's S-On with HBoot 1.55]
-found out TWRP wasn't updated so I replaced it with a newer one (2.6.3)
-now rooted device
-wanted to restore to normal stock settings so I downloaded the Guru Reset M7 1.26.502.15 and put it in my root folder
-went to recovery to install the guru reset ZIP
-things install, but touch screen doesn't work
problems now:
-can't turn off phone on main screen (tried holding down power, but doesn't restart phone past the 3 second mark)
-can't boot into bootloader from restart
-ruu doesn't work
can anyone provide me with help? please and thank you
EDIT: few things to keep in mind
-everytime i use RUU 3.17.502.3, it loads up black screen with HTC logo int he middle, then I can turn off the phone.
-when loading up, i can load into bootloader
-when choosing recovery/factory reset, it brings up the software update screen, but then goes to red triangle
-at red triangle screen, i can reboot system through android recovery system.
-back at square 1, touch screen doesn't work, etc.
All I can say is that I am in the same waters, phone stuck in bootloop, or goes to triangle of death, and PC WILL NOT recognize phone at all so without driver support, I am screwed too.
Added: All I did was unlock through HTCDev, and all hell broke loose, loaded up AIO, and phone freaked upon flashing TWRP. 1.55 HBoot, 4.3 ATT update.
hack14u said:
All I can say is that I am in the same waters, phone stuck in bootloop, or goes to triangle of death, and PC WILL NOT recognize phone at all so without driver support, I am screwed too.
Added: All I did was unlock through HTCDev, and all hell broke loose, loaded up AIO, and phone freaked upon flashing TWRP. 1.55 HBoot, 4.3 ATT update.
Click to expand...
Click to collapse
Here's a solution:
-get into bootloader mode
-fastboot
-plug usb in
-open cmd, then get to where your HTC One rooting stuff is (for example, everything was in a folder on my desktop)
-type "fastboot oem lock"
-your phone should say "relocked"
-open the latest RUU you have
-run things normally
that's how i fixed mine, lemme know if you have any more questions.
i also don't know why your phone has to be "relocked" in order to update it's software.
pztrixwsup said:
Here's a solution:
-get into bootloader mode
-fastboot
-plug usb in
-open cmd, then get to where your HTC One rooting stuff is (for example, everything was in a folder on my desktop)
-type "fastboot oem lock"
-your phone should say "relocked"
-open the latest RUU you have
-run things normally
that's how i fixed mine, lemme know if you have any more questions.
i also don't know why your phone has to be "relocked" in order to update it's software.
Click to expand...
Click to collapse
A thousand thanks, you are my new hero! And if you run the RUU, then go back and re-unlock the bootloader, it only says "unlocked" not tampered.
That's why we need to wait for the issue with Rumrunner S-off for our phones to get squared away. So we can flash other carrier or older software.
---------- Post added at 06:51 PM ---------- Previous post was at 06:40 PM ----------
Has anybody had success with Rumrunner for 3.17.502.3 yet? I have been hitting a wall and am not the only one. The phone is freezing on adb at test 2.1. We have tried flashing the RUU and doing it again, but it fails every time in the same way.
Here's what I get:
Code:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
Specifically looking for somebody with 3.17.502.3 to chime in if they've tried it, or one of the most awesome devs that work tirelessly so we common folk may find new ways to nearly-brick our phones :silly:
hack14u said:
A thousand thanks, you are my new hero! And if you run the RUU, then go back and re-unlock the bootloader, it only says "unlocked" not tampered.
Click to expand...
Click to collapse
Yea no problem bro, i was in your position for the whole day and i stumbled upon a billion sites and eventually trial and error'd the whole way through
Check the discussion in other thread about 4.3 and s-off. We have tried quite a few different things with no luck so far. I even posted in HTC one forums in the support thread. Hoping they will release something soon for our hboot 155.
Sent from my HTC One using xda app-developers app
I have been following all the posts about rooting and I managed to soft-brick my phone. I was able to temp root the phone, but I could never get superCID because the modified CID would never take. I didn't get errors, it just didn't stick. Anyway, I flashed the recovery for 2.17, but my phone took an OTA update to 2.19 a few days ago, and now I am stuck on the main screen but without the sense unlock ring. The screen works, and I can access the phone's drive and sd card, and I can adb. The bootloader shows ****TAMPERED***** (been that way for a while), and Bootloader is LOCKED. FIREBALL PVT SHIP S-ON RL, HBOOT is 1.15.0000.
Any ideas to recover to a fully booted phone?
yes had the same thing happen to me. download the ruu exe. from here http://www.androidruu.com/?developer=Fireball i used 217.605.2 ruu. put phone in fastboot connect it to computer and run ruu exe. on ur computer
I followed your reply but am not having any success . . . yet.
I go through the RUU.exe screens where I verify that I want to "upgrade" from image version 2.19.605.2 to image version 2.17.605.2.
Then RUU.exe runs to the point where it tells me the process will take 10 minutes. It then gets to "waiting for bootloader........" and the phone looks like it is rebooting and a black "HTC" screen appears. Bootloader never appears. A Windows 8 Systray error message then appears saying "USB Device Not Recognized - The last USB device connected has lost communication with the computer [or something like that]" The RUU.exe program then states: "ERROR [171] USB Connection Error. Check the following: (1) phone is connected to USB cable; (2) PC is connected to USB cable" There is no further option than to EXIT the RUU.exe. (Yes, my cable is connected to a USB 2 port).
I tried to do this twice with the same error message and the same disappointing results. The phone stays locked on the black HTC screen and I need to pull the battery to change this locked state.
I have no trouble communicating with the phone with ADB and I have root (#) at ADB Shell. I JUST loose USB communications with the phone as soon as it goes tries to load bootloader. I originally tried to run RUU.exe the way you stated by putting the phone into fastboot and then running RUU.exe, but then the program would not find the phone. What am I missing here? I have HTC drivers loaded, but I keep getting the comm error. Any more ideas?
Maybe I need to flash a recovery for 2.19.605.2? Any idea where I might find that?
OK, not sure why I didn't do this sooner, but I did a factory reset from Bootloader and it seems I am back again running the 2.19.605.2. Not sure if I can root this new OTA version using the 2.17.605.2 procedures or not, but I may give this a break for a bit.
Yeah u can't downgrade to 2.17 if ur on 2.19
Sent from my XT1060 using xda app-developers app
Hello,
I was trying to convert my T-Mobile HTC One to a Developer Edition so I could receive OTA updates by following the instructions here. I made it to step 11 where I changed the CID to BS_US001 (from T-MOB010), but encountered an error trying to change the MID to PN0712000 (from PN0713000). I also tried to change the CID to 11111111 which also worked, but I was still unable to change the MID. At this point I searched around for alternate ways to change the MID and found this post which I was able to follow until step 5. When I rebooted to bootloader at step 5, the phone never turned back on and I got a message in Windows saying "USB device not recognized".
The phone doesn't turn on at all, I have tried to hold power and power + vol down for around 30 seconds and nothing happens aside from a few vibrations every 20-30 seconds. I've tried holding power + both volume buttons for over 2 minutes to no avail. The PC I'm using is Win 8.1 using the USB 2.0 ports. I left it connected to the wall charger overnight and it only gave me a flashing red light.
Am I permanently bricked? No matter what I've tried, the phone just will not turn on at all. I tried running the RUU but of course it didn't work because the phone wasn't recognized as being plugged into the PC. Any help would be greatly appreciated. I've also attached a screenshot of the command window up until the point where I tried to reboot and it never turned back on.
When you get the "unrecognized device" the phone is on. Chances are, it's running a badly modified HBOOT that is trying and failing to get into RUU. LAst tiome that happened to me, holding the power button for *exactly* 16 seconds brought it into RUU mode (did not display the HTC RUU logo). From there I was able to run the RUU.
If you can get to that point, the RUU should install so long as you are SuperCID. If it does not;
Make sure you have the latest adb/fastboot - (or search google for "Minimal ADB and Fastboot" which has always worked for me)
fastboot reboot-bootloader
Install the modified tmous hboot following the instructions here:
http://rumrunner.us/hboots/
This will enable the use of the fastboot oem writemid command allowing you to change your MID.
I use this HBOOT when doing any conversions on my device. It allows all of the commands and has yet to fail me getting RUU's to run.
I have converted from T-Mobile to Dev, GPe and Int'l (and back to T-Mobile) several times and haven't bricked.
Keep working at it. These things are hard to brick!
Thank you for the reply! I'll try what you mentioned and report back on the results. I probably should have waited until I had a windows 7 PC to work on, but mine is currently in shipment. Hopefully with those tools you mentioned I can resurrect it.
Sent from my Galaxy Nexus using xda app-developers app
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
dg32 said:
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Try flashing a bright light into the proximity sensor while holding the power button + vol down buttons together.
:good: