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
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.
Hey guys, I've messed up my phone and I'm trying to RUU it back to stock. The problem is that it isn't working for me. I keep getting the error message "htc_fastboot.exe has stopped working" and it's driving me nuts. Im using the latest RUU and my firmware is up to date.
I relocked my bootloader even though Im S-OFF in a deperate attempt but nothing is working. THis isn't my first RUU and I don't know what Im doing wrong
EmSeeMAC said:
Hey guys, I've messed up my phone and I'm trying to RUU it back to stock. The problem is that it isn't working for me. I keep getting the error message "htc_fastboot.exe has stopped working" and it's driving me nuts. Im using the latest RUU and my firmware is up to date.
I relocked my bootloader even though Im S-OFF in a deperate attempt but nothing is working. THis isn't my first RUU and I don't know what Im doing wrong
Click to expand...
Click to collapse
Try using a computer that's running Windows 7.
Had same problem - how I fixed it.
I was having the exact same problem last night when trying to run my yearly RUU cleanup. I tried Windows 7, 8.1, different RUUs, etc and this is how I finally fixed it. I am s-off by the way and did this in Windows 8.1 Update. I'm suspecting that the rumrunner hboot I used was causing the issue, but I'm not sure. I'm assuming that you already have the drivers installed in Windows and that the PC can see your phone when you connect it.
0. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader. Since I'm s-off, I am not including how here.
1. Download the Full Firmware from RUU here. While you're there, get the RUU as well.
2. Flash the firmware file using fastboot following the directions in the OP. It failed for me the first time so I had to run it twice. The only thing I did differently was fastboot reboot-bootloader instead of just fastboot reboot at the end. The strange thing is that I ran it last night and it didn't work, but maybe I did something incorrectly.
3. While in (hopefully stock from step 2) bootloader, run the RUU as stated in the OP. I ran the RUU as an administrator and this time htc_fastboot.exe did not crash.
I'm now running pure stock (not for long I'm sure), still s-off. Good luck!
coal686 said:
I was having the exact same problem last night when trying to run my yearly RUU cleanup. I tried Windows 7, 8.1, different RUUs, etc and this is how I finally fixed it. I am s-off by the way and did this in Windows 8.1 Update. I'm suspecting that the rumrunner hboot I used was causing the issue, but I'm not sure. I'm assuming that you already have the drivers installed in Windows and that the PC can see your phone when you connect it.
0. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader. Since I'm s-off, I am not including how here.
1. Download the Full Firmware from RUU here. While you're there, get the RUU as well.
2. Flash the firmware file using fastboot following the directions in the OP. It failed for me the first time so I had to run it twice. The only thing I did differently was fastboot reboot-bootloader instead of just fastboot reboot at the end. The strange thing is that I ran it last night and it didn't work, but maybe I did something incorrectly.
3. While in (hopefully stock from step 2) bootloader, run the RUU as stated in the OP. I ran the RUU as an administrator and this time htc_fastboot.exe did not crash.
I'm now running pure stock (not for long I'm sure), still s-off. Good luck!
Click to expand...
Click to collapse
Haha, I just saw this after I fixed the problem using this exact solution!
thanks for the reply though!
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.
Hi, I have a thoug one, So i had an att htc one m7, i changed its os to the GPE and the hboot was 1.54, i was having problems with battery overheating and losing signal so i decided to get it back to stock, so first error: i used TWRP to flash an old nandroid of the firs OS it had, and it worked except that the touch screen didnt work, so i tried to downgrade the hboot to 1,44 and succedeed, but it didnt help to the touch problem, i tried to flash a RUU exe of att but when the RUU tries to connect to bootloader the phone disconnects, i read somewhere that if i relock the bootloader it can help but it didnt, now I am stucked I cant flash anything because of the bootloader and I cant give permission to unlock it again since the touch doesn work. Please help, im truly desperate.
ivandaterrible said:
Hi, I have a thoug one, So i had an att htc one m7, i changed its os to the GPE and the hboot was 1.54, i was having problems with battery overheating and losing signal so i decided to get it back to stock, so first error: i used TWRP to flash an old nandroid of the firs OS it had, and it worked except that the touch screen didnt work, so i tried to downgrade the hboot to 1,44 and succedeed, but it didnt help to the touch problem, i tried to flash a RUU exe of att but when the RUU tries to connect to bootloader the phone disconnects, i read somewhere that if i relock the bootloader it can help but it didnt, now I am stucked I cant flash anything because of the bootloader and I cant give permission to unlock it again since the touch doesn work. Please help, im truly desperate.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" and don't forget that since you downgraded to hboot 1.44, only win7/Linux/Mac will detect the phone in bootloader mode (not win8 / win10).
alray said:
Post the output of "fastboot getvar all" and don't forget that since you downgraded to hboot 1.44, only win7/Linux/Mac will detect the phone in bootloader mode (not win8 / win10).
Click to expand...
Click to collapse
Hi thanks for the reply, but I already solved it, it turns out I didnt knew obout the driver and Im running w10 so that was the problem, anyway I deactivated the windows signature enforment drivers function and get registry archive from this thread http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 and then the fastboot was recognized by windows.
I was trying to change the cid of my m7 but after flashing some files it just stuck on this Grey screen.. the tutorial i was following said that i can use adb commands on this screen but i cant because this phone is recognised as malfunctioning now (after that adb command) in my pc with windows 10.. i don't know much abt these stuff but it would be really helpful if i can revive this phone.
If u need any info just le me know..ill post it asap.
RIPhones said:
I was trying to change the cid of my m7 but after flashing some files it just stuck on this Grey screen.. the tutorial i was following said that i can use adb commands on this screen but i cant because this phone is recognised as malfunctioning now (after that adb command) in my pc with windows 10.. i don't know much abt these stuff but it would be really helpful if i can revive this phone.
If u need any info just le me know..ill post it asap.
Click to expand...
Click to collapse
Flashing files to change CID? CID can be changed using "fastboot oem writecid <your_desired_cid>", no file flashing required.
Are you talking about MID change? Hope you did not followed the crappy guide making users flash an eng bootloader?
And why are you trying to change your CID (or MID) on a Sprint phone?
alray said:
Flashing files to change CID? CID can be changed using "fastboot oem writecid <your_desired_cid>", no file flashing required.
Are you talking about MID change? Hope you did not followed the crappy guide making users flash an eng bootloader?
And why are you trying to change your CID (or MID) on a Sprint phone?
Click to expand...
Click to collapse
yes i was following that "crappy guide" as i was trying to change mid because i was unable to flash Stock RUU using adb ..it was showing some error.
PS. i don't have any recovery installed.
RIPhones said:
yes i was following that "crappy guide" as i was trying to change mid because i was unable to flash Stock RUU using adb ..it was showing some error.
PS. i don't have any recovery installed.
Click to expand...
Click to collapse
There are much more up-to-date and safer guides to change your MID. Did you read to moderator comment (in red) before reading the guide? The last pages of the thread? The guide you just followed made you flash an engineering bootloader made for the Droid DNA, not even designed for the M7 (hence the gray screen). This bootloader version is 1.39 which mean it will not allow you to connect (use fastboot) with any Windows 8 or 10 computer. So from now you must use a Win 7, XP, Linux or Mac machine to be able to use fastboot commands.
If your goal was to restore the original Sprint MID and CID on your phone that's ok. If you are trying to change your MID/CID to something else than Sprint, this is totally useless since only Sprint RUU will flash correctly on a Sprint phone (no conversion possible for this variant).
What was the error when flashing the RUU?
The first step out of this will be to flash twrp recovery (the wls version) so you can revert your MID back to Sprint and flash an old sprint RUU or firmware.zip.
alray said:
There are much more up-to-date and safer guides to change your MID. Did you read to moderator comment (in red) before reading the guide? The last pages of the thread? The guide you just followed made you flash an engineering bootloader made for the Droid DNA, not even designed for the M7 (hence the gray screen). This bootloader version is 1.39 which mean it will not allow you to connect (use fastboot) with any Windows 8 or 10 computer. So from now you must use a Win 7, XP, Linux or Mac machine to be able to use fastboot commands.
If your goal was to restore the original Sprint MID and CID on your phone that's ok. If you are trying to change your MID/CID to something else than Sprint, this is totally useless since only Sprint RUU will flash correctly on a Sprint phone (no conversion possible for this variant).
What was the error when flashing the RUU?
The first step out of this will be to flash twrp recovery (the wls version) so you can revert your MID back to Sprint and flash an old sprint RUU or firmware.zip.
Click to expand...
Click to collapse
i can't remember that error as it was done a week ago but when i was trying to flash twrp it was just was failing. ill get back to u once i install ubuntu on my system and try with that.. but what should i do first after connecting it to a linux machine? should i try to install recovery ?? please help me out here.
RIPhones said:
i can't remember that error as it was done a week ago but when i was trying to flash twrp it was just was failing. ill get back to u once i install ubuntu on my system and try with that.. but what should i do first after connecting it to a linux machine? should i try to install recovery ?? please help me out here.
Click to expand...
Click to collapse
you'll first need to flash back a Sprint bootloader. Then flash twrp and revert your MID and CID back to sprint using twrp's terminal and finally flash a sprint RUU.