I am having an issue with my phone in fastboot mode. After changing my CID to GOOGL001 from CWS_001, I was in the process of flashing the GPE RUU, but it got interrupted and it was stuck on the HTC logo for a while. I ended up rebooting the device and now it is unrecognized in fastboot, yet it still works in normal mode. In fastboot mode, it is a black screen instead of the normal white screen. I don't think anything is wrong with my drivers because everything was working alright before. Phone is still fully functional and I would like to either change my CID back to normal or continue with the GPE RUU. Any help would be much appreciated. Thanks!
I have tried using USBDeview to uninstall all drivers and reinstalled all HTC drivers, but I still cant get it to connect on fastboot. Has anyone had a similar issue with their phone or know what I can do?
jacky1017 said:
I have tried using USBDeview to uninstall all drivers and reinstalled all HTC drivers, but I still cant get it to connect on fastboot. Has anyone had a similar issue with their phone or know what I can do?
Click to expand...
Click to collapse
my guess is that you are using windows 8 or above and your phone is on hboot 1.44.
try with windows 7, linux or mac.
alray said:
my guess is that you are using windows 8 or above and your phone is on hboot 1.44.
try with windows 7, linux or mac.
Click to expand...
Click to collapse
Yeah I am on Windows 8.1, but my phone is on hboot 1.54 if that makes a difference. I will try to get on a computer with windows 7 next weekend when I get home. Really hoping that it works out because this has been stressing me out these past two days.
Related
After a lot of reading and some trial and error I was finally able to get S-OFF on my Bell (Canada) unlocked HTC One using the universal 0.45 rumrunner. I wanted to change my phone into the Google Edition so I followed the guide and everything went well but I missed the part about flashing the RUU twice and once I got that failed error I assumed it hadn't worked and I manually rebooted the phone. When I booted back into bootloader my phone was on 1.54.0000 instead of 1.55.0000 which it had been on before. The problem is that my computer won't recognize the phone in 1.54 bootloader so i can run my adb commands. I know the drivers are installed properly because it recognizes it when the phone is booted up normally and my adb commands work and I can reboot the bootloader from there but once it goes into the bootloader I can't get it to recognize the device. For reference this is on a windows 8.1 laptop, I also tried on a windows 7 desktop and an older windows 7 laptop with the same results. Is the issue with the HTC drivers not compatible with newer versions of windows? Or do I need to try to find an older version of the drivers that are compatible with the 1.54 bootloader? Or is it something else? Any help to steer me in the right direction would be greatly appreciated. Once I can get the bootloader recognized I can flash the RUU again and everything should be good to go.
I tried to update to 4.4, but it gave me a blue screen. I can get into TWRP and Fastboot works.
However, it won't read it as USB on my Windows 8.1, but it sees it on my Windows 7 and OSX. I'm trying everything to get some from of OS running on my HTC One.
Please help me. I'm new to this and I'm scared out of my mind!
If you are soff then connect the phone in fastboot mode and run the google edition ruu.
If not Soff, then post your fastboot getvar all output
SaHiLzZ said:
If you are soff then connect the phone in fastboot mode and run the google edition ruu.
If not Soff, then post your fastboot getvar all output
Click to expand...
Click to collapse
How could I check if S-off, and if it is S-off how would I run the google edition Ruu? I have no way to transfer the zip to my phone.
Yes you do. Start searching the guides littered in this forum.
SaHiLzZ said:
Yes you do. Start searching the guides littered in this forum.
Click to expand...
Click to collapse
I have S-Off, so would I have to sideload the ROM from OSX to my phone?
If you have S-off then either run ruu or do fastboot flash ruu.zip.. Look up nik71 guide how to do that.
BobFaggot said:
I tried to update to 4.4, but it gave me a blue screen. I can get into TWRP and Fastboot works.
However, it won't read it as USB on my Windows 8.1, but it sees it on my Windows 7 and OSX. I'm trying everything to get some from of OS running on my HTC One.
Please help me. I'm new to this and I'm scared out of my mind!
Click to expand...
Click to collapse
im having the same problem
i managed to get into twrp, and install 4.3, but its not 4.4
Bascially we are screwed
I too have the problem with blue screen on upgrade.
I got the OTA upgrade and when installing it, reboots, dropping me to a blue screen.
I have had TWRP with no issues
I have the Bigxie ROM installed.
When I try and get S-OFF and try moonshine, I can not find a version to match my HTC One
My phone was bought from Wind Mobile, and ROM IS is GLOBA001
Is there anyone who can assist us who are stuck in this way?
Thank you!
i'm trying to install a stock Europe ROM from a RUU.zip because the RUU.exe wont run on my laptop for some reason (Windows 8.1 64bit)
i am S-off and have changed my CID to Super-CID and MID to the required one.
I have the latest HTC drivers installed and have uninstalled HTC Sync. my HBOOT version was 1.57 before, but i used firewater to obtain s-off and it brought my HOBOOT back to 1.44 (i don't know how) *i couldn't get s-off with 1.57*
i'm trying to follow this guide to install the ruu.zip
but i can only get as far as adb reboot-bootloaderon htcguru site
after it boots to bootloader mode the USB device becomes unrecognized and i cant fastboot any commands (waiting for device) shows up.
i restart my phone and i can mount to my laptop just fine and everything but when i get into fastboot mode it becomes unrecognized (Code 43), i've been up all night trying to find a solution but nothing. im lost for ideas.
ive tried different ports and restarted my laptop several times
any ideas. only reason i wanted the European ROM was to get rid of the o2 UK bootanimation and now its become a much bigger problem
i cant even run the ruu.exe file now that im s-off so im pretty much stumped
Windows 8 and 8.1 has trouble recognizing hboot 1.44, Update hboot to 1.54 and Windows will now recognize fastboot.
Sent from my HTC One using XDA Premium HD app
bored_stupid said:
Windows 8 and 8.1 has trouble recognizing hboot 1.44, Update hboot to 1.54 and Windows will now recognize fastboot.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
but i cant do that without flashing can i? will 1.44 be fine on windows 7?
jewwiid said:
but i cant do that without flashing can i? will 1.44 be fine on windows 7?
Click to expand...
Click to collapse
Hboot 1.44 is fine with Windows 7
Take a look at FAQ 1, and 5, from here
http://forum.xda-developers.com/showthread.php?p=47794181
This should get fastboot working again
Sent from my Nexus 7 using XDA Premium HD app
Hey guys, so I tried to unlock my phone to switch over to T-mobile and in the process, I believe I bricked my phone. I followed some very misleading guide, and due to this, my phone is stuck on the RUU screen with the four triangles. To make things worse, my computer (running win 8.1) stopped being able to recognize my phone, so adb and fastboot won't recognize it either (I feel like this happened due to me trying to flash a RUU). I tried several times to re-install drivers to no avail. I don't think I can get to the recovery screen either. Is there any hope in saving this or is it a goner? Thanks.
What I've done so far before this state:
S-OFF
Rooted
changed the CID and MID to T-mobile relevant IDs
kiweewee said:
Hey guys, so I tried to unlock my phone to switch over to T-mobile and in the process, I believe I bricked my phone. I followed some very misleading guide, and due to this, my phone is stuck on the RUU screen with the four triangles. To make things worse, my computer (running win 8.1) stopped being able to recognize my phone, so adb and fastboot won't recognize it either (I feel like this happened due to me trying to flash a RUU). I tried several times to re-install drivers to no avail. I don't think I can get to the recovery screen either. Is there any hope in saving this or is it a goner? Thanks.
What I've done so far before this state:
S-OFF
Rooted
changed the CID and MID to T-mobile relevant IDs
Click to expand...
Click to collapse
if you have used a 1.xx.xxx.x RUU with windows 8.1, thats the problem. When flashing a 1.xx.xxx.x ruu, your bootloader will downgrade to version 1.44. This bootloader version isn't compatible with windows 8.1 (fastboot won't work).
The ruu screen with 4 triangles = incomplete ruu flash. Most likely caused by the computer not being able to flash the entire RUU after hboot 1.44 was flashed.
If using a ruu.exe, you'll need to find a winXP or 7 pc. If using a ruu.zip, you can either use winXP, win7, Linux (recommand ubuntu 12.04 32 bits version) or MacOS.
Btw why did you flashed a ruu to unlock your phone? You know that sim-unlock can be done simply by using a paid code? Or if you have s-off you can sim-unlock for free using the sieempi method.
can you post all the information you can see on the bootloader screen here?
Uh I don't think I can get to the bootloader screen as it is stuck on the RUU screen. Would connecting my phone on linux get some response?
kiweewee said:
Uh I don't think I can get to the bootloader screen as it is stuck on the RUU screen. Would connecting my phone on linux get some response?
Click to expand...
Click to collapse
hold volume down and power until the phone reboot in bootloader mode. can you confirm the ruu version used?
I've done that and the screen just turns off and on with the RUU screen with the four triangles still there.
I've also tried connecting my phone on linux, after installing adb and fastboot, but it has given me a "HTC unknown usb device( device failed enumeration) " warning.
I used this ruu after hearing my phone should be using this ruu, I changed the cid to 11111111 and mid to tmobile on the android.info file so it would work
RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted
After flashing this once it gave me the hboot error thing to boot again, but that is when my phone stopped responding to fastboot.
kiweewee said:
I used this ruu after hearing my phone should be using this ruu, I changed the cid to 11111111 and mid to tmobile on the android.info file so it would work
RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted
After flashing this once it gave me the hboot error thing to boot again, but that is when my phone stopped responding to fastboot.
Click to expand...
Click to collapse
I'm pretty sure your totally wasting your time you can't turn a CDMA Verizon phone into a GSM t-mobile phone by flashing a RUU
your going to end up with a bunch of screwed up partitions
this is how you get fastboot working on windows 8.1 hboot 1.44
http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
Just looking for this rom, I understand no one wants to develop an old rom, but there would be a good reason, and it seems all the downloads have been deleted. I can't find a 4.2 ROM anywayere. Anyone got an idea for me where I can get a Custom 4.2,,,like a CM 10 or something?
Found this.
S off disables fastboot in windows 7 and up. Vista worked.
kruc Ire said:
Found this.
S off disables fastboot in windows 7 and up. Vista worked.
Click to expand...
Click to collapse
S-OFF does not disable fastboot on win 7 and up
the only problem with fastboot and windows is when your hboot version is 1.44, it will not work with Windows 8.1 and 10 but its not an s-on/s-off thing...
alray said:
S-OFF does not disable fastboot on win 7 and up
the only problem with fastboot and windows is when your hboot version is 1.44, it will not work with Windows 8.1 and 10 but its not an s-on/s-off thing...
Click to expand...
Click to collapse
when I got my phone back from jtag it was s on, tampered /unlocked. i unlocked it myself 6 hours before bricking it. that was 1 month ago.
I never looked what the original hboot was but I unlocked it, so Im guessing it didnt change, but after jtag the splash screen said quietly brilliant where it did not previously.
it returned to me with cm on it, the repairer put the nandroid I had stored. no stock nandroid was available to repair. however, the orig. pbone was clearly a 5.0.2 lollipop updated phone.
So if it had 1.44 when I got it back, and the original quietly brilliant type splash screen would you say it was otherwise when I sent it in?
were 1.44 phones unable to fastboot in windows 8 at their inception? I'm a month only owner of a m7.
so I heard someplace that only windows 8.1 and up are programmed not to recognize the 1.44 hboot.
my experience is my 7 machine would not do a fastboot. either. vista did it, and now I oem flashed a 1.54 hboot, and still cant fastboot connect in win7.
kruc Ire said:
when I got my phone back from jtag it was s on, tampered /unlocked. i unlocked it myself 6 hours before bricking it. that was 1 month ago.
I never looked what the original hboot was but I unlocked it, so Im guessing it didnt change, but after jtag the splash screen said quietly brilliant where it did not previously.
it returned to me with cm on it, the repairer put the nandroid I had stored. no stock nandroid was available to repair. however, the orig. pbone was clearly a 5.0.2 lollipop updated phone.
So if it had 1.44 when I got it back, and the original quietly brilliant type splash screen would you say it was otherwise when I sent it in?
were 1.44 phones unable to fastboot in windows 8 at their inception? I'm a month only owner of a m7.
so I heard someplace that only windows 8.1 and up are programmed not to recognize the 1.44 hboot.
my experience is my 7 machine would not do a fastboot. either. vista did it, and now I oem flashed a 1.54 hboot, and still cant fastboot connect in win7.
Click to expand...
Click to collapse
I can confirm that hboot 1.44 was working fine for Windows XP to Windows 8.0. When Windows 8.1 was released (August 2013) fastboot were not working anymore and HTC released hboot 1.54 in October 2013 to fix the problem.
Many of us (including me) were still using Win 7 back in these days since we hated Win 8/8.1 and it was working fine. I unlocked my bootloader, flashed a custom recovery, achieved s-off. changed CID and MID and converted my phone to another version, all this when my phone was on 1.44 and my computer running Win 7.
I believe you when you say its not working on your side with Win7, but its most likely another problem like a driver issue or something with your config but it should work, its not an hboot or S-on/S-off problem.
read faq #1:http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2