Related
I just got a new laptop with 8.1 loaded on it... tried to flash a rom and it didnt go well.. bootlooping at the bootloader. computer wont recognize the phone, doesnt say fastboot usb. ive downloaded every possible driver i could find for 2 days and nothing...
basically ive narrowed it down to needing the amd usb host drivers for win 8.1 and i cant find em or a solution anywhere.
No i cant use another computer.
please please help, im totally screwed.
You can try this http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
Or use a pc that is not Win 8.1
The good news is if you can get your hboot updated to 1.55 your phone will be recognized in fastboot.
BD619 said:
You can try this http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
Or use a pc that is not Win 8.1
The good news is if you can get your hboot updated to 1.55 your phone will be recognized in fastboot.
Click to expand...
Click to collapse
thanks.. havent checked the link yet... wouldnt i need fastboot to get the hboot? haha catch 22
edit... checked that link.... must have seen it 10 times now... i dont understand, can i somehow use the intel drivers with my amd?
think im gunna dual boot ubuntu and see where that takes me... ugh
Use option 2 a Windows machine that is not running 8.1
BD619 said:
Use option 2 a Windows machine that is not running 8.1
Click to expand...
Click to collapse
thatd be great but i live on a tiny island in the caribbean.. theres no one around me with a computer, honestly... theres not even a sprint store on the island!
Lol I forgot about Ubuntu that should get ya going
blacksantron said:
thatd be great but i live on a tiny island in the caribbean.. theres no one around me with a computer, honestly... theres not even a sprint store on the island!
Click to expand...
Click to collapse
never thought I would feel bad for someone on a Caribbean island, haha. hope you get it running, I just installed 8.1 and used the rumrunner modified 1.55 hboot and everything is fine, good luck!
jblaze10 said:
never thought I would feel bad for someone on a Caribbean island, haha. hope you get it running, I just installed 8.1 and used the rumrunner modified 1.55 hboot and everything is fine, good luck!
Click to expand...
Click to collapse
yeah yeah... paradise and all...except it sucks when i cant communicate with anyone.. OK SO UPDATE
after totally crashing my boot partitions trying to dual boot 8.1 & linux, I atttained dual boot... ugh was rough.. came to me in the middle of the night and i just hit 3 keys and bam, dual boot... ok
YES thanks to linux i was able to push a new recovery on as well as a new ROM!! yayyyyyyy not so much.
NOW.. i have a rom running but i have no firmware, radio, nothing.. In my quest to put a firmware on i have achieved S-OFF.. (I also used rumrunner, but my hboot remains 1.44?) and flashed what looked like working radio stuff, but nope. Should i be trying all this with a Sense ROM? Im on SlimKat atm. Thats my only idea now.. i've flashed firmwares out the wazoo and nothing gives me those lovely service bars... just an empty triangle... Any Thoughts? really dont want to download a 900meg rom.
thanks!!!
U may have to ruu. Also rumrunner is for 1.55 hboot so I really don't know if it would work. Revone and moonshine are for 1.44 check bd19 faq thread or pm him if he isn't busy he will gst u on the right path!:thumbup:
Use OMJ's stock rooted ROM. But if you just need firmware and you have S-off, flash the firmware set from OMJ's RUU thread in fastboot . Instructions are there in the thread.
If you need help, just ask. That should get you going. Also, you can flash the firmware package that does not include hboot, recovery and boot. It's on the thread as well.
OMJ thread:
http://forum.xda-developers.com/showthread.php?t=2576995
tdhite said:
Use OMJ's stock rooted ROM. But if you just need firmware and you have S-off, flash the firmware set from OMJ's RUU thread in fastboot . Instructions are there in the thread.
If you need help, just ask. That should get you going. Also, you can flash the firmware package that does not include hboot, recovery and boot. It's on the thread as well.
OMJ thread:
http://forum.xda-developers.com/showthread.php?t=2576995
Click to expand...
Click to collapse
thanks for the tip...
i tried it, as per the instructions.. it went along as though is was working, but upon reboot, still an empty triangle.... baseband "unknown"
could it be something as mundane as me using an aosp rom and not a sense? looks like im facing the 1 gig RUU download... ugh
The ROM has nothing to do with the firmware. You are not getting flashed if your radio shows unknown.
Are you entering fastboot oem and then flashing the firmware set?
tdhite said:
The ROM has nothing to do with the firmware. You are not getting flashed if your radio shows unknown.
Are you entering fastboot oem and then flashing the firmware set?
Click to expand...
Click to collapse
oh yes, absolutely.
fastboot oem rebootRUU
wait should i still lock the bootloader before trying this?
fastboot oem lock?
No. No need to lock. You should be getting a radio version if you followed the few instructions in the thread for 'flashing modified firmware.' If you are really S-off, that should work.
tdhite said:
No. No need to lock. You should be getting a radio version if you followed the few instructions in the thread for 'flashing modified firmware.' If you are really S-off, that should work.
Click to expand...
Click to collapse
well rumrunner says i am s-off.. but these radio/firmware flashes dont take.... bootloader says, tampered, unlocked, s-off, hboot 1.44.
i just dont get it... well cheers to my impending 2 day download... UGH!
blacksantron said:
well rumrunner says i am s-off.. but these radio/firmware flashes dont take.... bootloader says, tampered, unlocked, s-off, hboot 1.44.
i just dont get it... well cheers to my impending 2 day download... UGH!
Click to expand...
Click to collapse
Which firmware are you trying to flash? Give us a link.
I would suggest flashing the Full Firmware 3.04.651.2 found HERE
It should give you a fresh flash of the firmware as well as update your hboot to 1.55 which in turn will make your device recognized in fastboot with Windows 8.1
ok now im going crazy
i downloaded the RUU from that thread above and ran it... says that usb is not connected. I verified that it is by running adb devices and it lists my phone... fastboot reboot works,,, for some reason the RUU thinks its not connected?!?!?!
im pulling my hair out
I believe you are on Windows 8.x, from previous notes. You need to upgrade hboot as BD noted above, which means flash the full firmware package from the links we gave so you get hboot upgraded. I'd use your Ubuntu install for that, but no matter, your choice if you know Windows is working.
But if that works, I seriously think you can blow off the RUU and load a ROM at that point. I would also look at checking things out with the LTE app from the play store once your radio is up, but be very careful with that app and only change the cdma/gsm/whatever selection option.
tdhite said:
I believe you are on Windows 8.x, from previous notes. You need to upgrade hboot as BD noted above, which means flash the full firmware package from the links we gave so you get hboot upgraded. I'd use your Ubuntu install for that, but no matter, your choice if you know Windows is working.
But if that works, I seriously think you can blow off the RUU and load a ROM at that point. I would also look at checking things out with the LTE app from the play store once your radio is up, but be very careful with that app and only change the cdma/gsm/whatever selection option.
Click to expand...
Click to collapse
right on, thanks... yeah im at hboot 1.55 now. So yeah im gunna grab a sense rom. wish me luck, havent had a phone for 4 days now
NOWWWW the sense rom im installing (Android Revolution 41.0) bootloops during the animation..
tried to reinstall the rom i was on that was working just no radio (SlimBean) and now that almost boots up then bootloops.... I swear this is torture.
Hi All,
I tried to delete my personal data from the HTC One as I was planning on selling it tomorrow. I went into TWRP and wiped everything...which meant I wiped the OS too
I've tried everything, but I cannot find a way to reinstall a ROM.
First, I'm on a Windows 7 laptop. Soon, I'll have to switch to a Mac computer at work.
ADB doesn't work at all because I can't get the driver installed so the phone isn't recognized in ADB. I've installed the drivers from Hasoon2000's AIO kit, as well as install HTC Sync Manager. Neither one helps...so for now ADB is out.
Windows RUU.exe installation files don't work either. I've downloaded all versions from HTCDevs.com, and get an ERROR 155 each time.
Fastboot itself works, but I can't flash a ROM. If I try, I get "remote:not allowed". I'm in RUU mode (fastboot oem rebootRUU) for the RUU.zip files. I've also tried flashing a CWM ROM, but I get the same error.
I just want to sell this phone and get on with my life, but I can't find a way to get it working again. Any help would be greatly appreciated!
awer25 said:
Hi All,
I tried to delete my personal data from the HTC One as I was planning on selling it tomorrow. I went into TWRP and wiped everything...which meant I wiped the OS too
I've tried everything, but I cannot find a way to reinstall a ROM.
First, I'm on a Windows 7 laptop. Soon, I'll have to switch to a Mac computer at work.
ADB doesn't work at all because I can't get the driver installed so the phone isn't recognized in ADB. I've installed the drivers from Hasoon2000's AIO kit, as well as install HTC Sync Manager. Neither one helps...so for now ADB is out.
Windows RUU.exe installation files don't work either. I've downloaded all versions from HTCDevs.com, and get an ERROR 155 each time.
Fastboot itself works, but I can't flash a ROM. If I try, I get "remote:not allowed". I'm in RUU mode (fastboot oem rebootRUU) for the RUU.zip files. I've also tried flashing a CWM ROM, but I get the same error.
I just want to sell this phone and get on with my life, but I can't find a way to get it working again. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Ive read that error 155 is caused mainly because the boot loader is unlocked. YOU HAVE TO LOCK THE BOOTLOADER FOR RUU. Lock the boot loader and retry
Are you S-OFF ??
raghav kapur said:
Ive read that error 155 is caused mainly because the boot loader is unlocked. YOU HAVE TO LOCK THE BOOTLOADER FOR RUU. Lock the boot loader and retry
Are you S-OFF ??
Click to expand...
Click to collapse
Thanks for the reply! I forgot to write it but I did relock the boot loader when trying the RUU.
Also, I have the Developer Edition, which is unlocked but S-On I believe.
awer25 said:
Thanks for the reply! I forgot to write it but I did relock the boot loader when trying the RUU.
Also, I have the Developer Edition, which is unlocked but S-On I believe.
Click to expand...
Click to collapse
1- Even though the Dev Edition is unlocked, when you want to run an RUU, you have to relock it (when S-On), otherwise you'll get error 155
2- post a "fastboot getvar all" (excluding IMEI, and s/n)
3- when you say rom.zip in RUU mode, are you using a decrypted zip, or the original signed (encrypted) zip? (because with s-on, only the signed one will work)
nkk71 said:
1- Even though the Dev Edition is unlocked, when you want to run an RUU, you have to relock it (when S-On), otherwise you'll get error 155
2- post a "fastboot getvar all" (excluding IMEI, and s/n)
3- when you say rom.zip in RUU mode, are you using a decrypted zip, or the original signed (encrypted) zip? (because with s-on, only the signed one will work)
Click to expand...
Click to collapse
Yeah, last time that was the solution (re-locking). This time, even after relocking, I still get the Error 155 (and it does show "RELOCKED" in the boot loader)
Getvar screenshot is attached.
The rom.zip was from HTCDev.com, so I'm guessing it is an original signed zip. It was just renamed to be more user friendly.
EDIT: I'm not sure if this helps, but I was able to get ADB working on my Mac at work. I tried sideloading the official ROM and also a CWM ROM. It copies over fine, but then there are errors when trying to install. It says it can't mount various things. I've attached a pic of that as well.
awer25 said:
Yeah, last time that was the solution (re-locking). This time, even after relocking, I still get the Error 155 (and it does show "RELOCKED" in the boot loader)
Getvar screenshot is attached.
The rom.zip was from HTCDev.com, so I'm guessing it is an original signed zip. It was just renamed to be more user friendly.
Click to expand...
Click to collapse
I can never find anything on HTCdev
Anyway, the .zip you got is probably a kernel source code, not an RUU, I don't think HTC release ruu.zips (as far as i know).
How are you running the EXE, cause looks like your on a Mac, (so you may be using a vm, and maybe that's the problem)?
Long story short, here's what I would do, remember you need an RUU.EXE version 4.19.1540.4 or higher, then run the RUU, once it opens up, it will have created a folder in %Temp% (eg on Win7, that would be usually C:\Users\<username>\AppData\Local\Temp) there you will find a newly created folder (use sort by date modified to find it) within that folder you will find rom.zip (a 1GB+ file) which is the signed ruu.zip.
copy that to your fastboot folder, then you can exit the RUU.EXE which will delete the temporary folder i mentioned above
then on your mac:
./fastboot oem rebootRUU
./fastboot flash zip rom.zip
./fastboot flash zip rom.zip <- yes twice
./fastboot reboot-bootloader
if you want to see what kind of output to expect, to my guide http://forum.xda-developers.com/showthread.php?t=2541082 and check post #7, it has a real life example of the above commands.
nkk71 said:
I can never find anything on HTCdev
Anyway, the .zip you got is probably a kernel source code, not an RUU, I don't think HTC release ruu.zips (as far as i know).
How are you running the EXE, cause looks like your on a Mac, (so you may be using a vm, and maybe that's the problem)?
Long story short, here's what I would do, remember you need an RUU.EXE version 4.19.1540.4 or higher, then run the RUU, once it opens up, it will have created a folder in %Temp% (eg on Win7, that would be usually C:\Users\<username>\AppData\Local\Temp) there you will find a newly created folder (use sort by date modified to find it) within that folder you will find rom.zip (a 1GB+ file) which is the signed ruu.zip.
copy that to your fastboot folder, then you can exit the RUU.EXE which will delete the temporary folder i mentioned above
then on your mac:
./fastboot oem rebootRUU
./fastboot flash zip rom.zip
./fastboot flash zip rom.zip <- yes twice
./fastboot reboot-bootloader
if you want to see what kind of output to expect, to my guide http://forum.xda-developers.com/showthread.php?t=2541082 and check post #7, it has a real life example of the above commands.
Click to expand...
Click to collapse
Thank you so much for the walkthrough! It could be that I have the kernel source code...I've attached a screenshot of what I downloaded (link is circled). One thing though - where do I get the RUU.exe that's 4.19.1540.4 or higher? The highest I see is 3.22.1540.1 on HTC Dev for the Developer Edition. There is a 100MB file that's 4.20.1136.8 (see screenshot) for the WWE region, just says "HTC One" without more detail. Should I use that, even though it's only 100MB?
I was running the RUU on a Windows laptop at home, but then switched to my Mac at work. I can boot into Windows 8.1 on the Mac as well, so I can do the RUU extraction portion there (assuming Win 8.1 isn't an issue).
I'll report back once I've tried these steps.
EDIT: I've found this RUU - will it work?
awer25 said:
Thank you so much for the walkthrough! It could be that I have the kernel source code...I've attached a screenshot of what I downloaded (link is circled). One thing though - where do I get the RUU.exe that's 4.19.1540.4 or higher? The highest I see is 3.22.1540.1 on HTC Dev for the Developer Edition. There is a 100MB file that's 4.20.1136.8 (see screenshot) for the WWE region, just says "HTC One" without more detail. Should I use that, even though it's only 100MB?
I was running the RUU on a Windows laptop at home, but then switched to my Mac at work. I can boot into Windows 8.1 on the Mac as well, so I can do the RUU extraction portion there (assuming Win 8.1 isn't an issue).
I'll report back once I've tried these steps.
Click to expand...
Click to collapse
the first picture could very well be a ruu.zip due to the filesize, all the (at least HTC Sense editions) will be 1GB+ the other ones that are around 100MB are just kernel source codes,
but you can't use the 3.22 version cause that's a downgrade and only possible with S-Off.
just found one at http://www.androidruu.com/?developer=M7 version 4.19.1540.9
http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
this should work fine on even on Win 8.1 (without the need to extract it)
this will only work with a locked/relocked bootloader if you're sticking with S-On.
nkk71 said:
the first picture could very well be a ruu.zip due to the filesize, all the (at least HTC Sense editions) will be 1GB+ the other ones that are around 100MB are just kernel source codes,
but you can't use the 3.22 version cause that's a downgrade and only possible with S-Off.
just found one at http://www.androidruu.com/?developer=M7 version 4.19.1540.9
http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
this should work fine on even on Win 8.1 (without the need to extract it)
this will only work with a locked/relocked bootloader if you're sticking with S-On.
Click to expand...
Click to collapse
Thanks! I edited my previous post with a link to one that I found. Is it the same one? It has the exact same file name as what you just posted. I'm 50% done downloading it, and would rather not start again lol.
awer25 said:
Thanks! I edited my previous post with a link to one that I found. Is it the same one? It has the exact same file name as what you just posted. I'm 50% done downloading it, and would rather not start again lol.
Click to expand...
Click to collapse
HTCGuru site is good too.
Good luck
It worked! I verified that fastboot was working and that the drivers were installed, relocked the bootloader, then ran the RUU.exe - and it finished without issue. I then unlocked the bootloader, and it doesn't say Tampered anymore
I can't thank you enough for the help. I wouldn't have guessed that you can't downgrade without being on S-OFF.
awer25 said:
It worked! I verified that fastboot was working and that the drivers were installed, relocked the bootloader, then ran the RUU.exe - and it finished without issue. I then unlocked the bootloader, and it doesn't say Tampered anymore
I can't thank you enough for the help. I wouldn't have guessed that you can't downgrade without being on S-OFF.
Click to expand...
Click to collapse
you're most welcome, feel free to hit the thanks buttons if you found a useful post
and no you can't downgrade (with S-On), but you can upgrade :good:
have a good one
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
So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.
jwalters1123 said:
So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.
Click to expand...
Click to collapse
You say the RUU failed...
Any error message?
As much info as you can give would be better.
Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."
jwalters1123 said:
Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."
Click to expand...
Click to collapse
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173
BD619 said:
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.
jwalters1123 said:
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.
Click to expand...
Click to collapse
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.
BD619 said:
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.
Click to expand...
Click to collapse
ok so hboot version says 3.19.0.0000, i am on a usb 2.0 port, i am not sure how to paste my copied text from the cmd prompt into this box so i just pasted it to a .txt file and attached that and it has all the getvar all info. thanks for the help.
Everything is current according to the getvar...go ahead and remove it as it contains the imei #
The latest RUU should work.
Maybe try downloading Sync Manager to update the drivers or try a different PC/usb port.
Low and behold i was in a 3.0 port lmao... smh... so you just saved me beating my head against the wall for god knows how much longer, thanks for the help, the ruu is working fine now:fingers-crossed:
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.