Related
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
Hi All
My htc all of the sudden is showing white screen, Please have a look at the picture
Unlocked
RUNNYMEDE XA SHIP S-ON
HBOOT-1.25.0004
RADIO-3822.10.10.12_M
eMMC-boot
Oct 20 2011,00:20:30
I Have been looking on youtube, at videos, also I have been reading on this great forum, but I still can't get it to work, any idea why is this giving me this, i also done factory reset and it comes up with the same screen again.
after reading on google youtube i tried to install a program called RUU which has europe and it's 3822, but for some reason this file ( ruu exe ) does not install, I don't understand what to do.
could some one please assist me with this as this was a small present for someone. how do i fix this problem
regards
Hello.
You need to be more precise on the informations you provide.
What the "does not install" means ? Is your computer returning a special error message, does the installer crash ?
Did you try to install any custom ROM ?
Did you try to install any custom recovery ? I see your bootloader is unlocked.
Try to access the recovery by selecting the RECOVERY entry on the bootloader. If it goes to a black screen or a warning sign, it means that your recovery is the stock one.
If you installed CWM or TWRP, you could try to wipe everything (after doing an eventual backup) and flash a new ROM.
Siphoné said:
Hello.
You need to be more precise on the informations you provide.
What the "does not install" means ? Is your computer returning a special error message, does the installer crash ?
Did you try to install any custom ROM ?
Did you try to install any custom recovery ? I see your bootloader is unlocked.
Try to access the recovery by selecting the RECOVERY entry on the bootloader. If it goes to a black screen or a warning sign, it means that your recovery is the stock one.
If you installed CWM or TWRP, you could try to wipe everything (after doing an eventual backup) and flash a new ROM.
Click to expand...
Click to collapse
When I try to install this ruu file on windows xp sp3 RUU_PRIMO_U_ICS_40A_HTC_Europe_1.41.401.1_Radio_20.62.30.0830U_3822.15.00.03_M_release_247272_signed.exe
this will not install, I also tried, this on windows 7 again this will not install, after diagnosing this on windows 7, it says that this is made for windows xp sp2.
I haven't tried to install anything at all, all I have done is unlocked the bootloader but that's all I could do, i don't know where to go from here, i tried cwm but no result with this
jim102 said:
Hi All
My htc all of the sudden is showing white screen, Please have a look at the picture
Unlocked
RUNNYMEDE XA SHIP S-ON
HBOOT-1.25.0004
RADIO-3822.10.10.12_M
eMMC-boot
Oct 20 2011,00:20:30
I Have been looking on youtube, at videos, also I have been reading on this great forum, but I still can't get it to work, any idea why is this giving me this, i also done factory reset and it comes up with the same screen again.
after reading on google youtube i tried to install a program called RUU which has europe and it's 3822, but for some reason this file ( ruu exe ) does not install, I don't understand what to do.
could some one please assist me with this as this was a small present for someone. how do i fix this problem
regards
Click to expand...
Click to collapse
Crazy man, you must Relocked your phone before install RUU.
plug with USB and go to fastboot:
run fastboot oem lock
then try with RUU file, there is no different which ver. of windows using XP and/or SEVEN.
if received any error write down.
marco1962 said:
Crazy man, you must Relocked your phone before install RUU.
plug with USB and go to fastboot:
run fastboot oem lock
then try with RUU file, there is no different which ver. of windows using XP and/or SEVEN.
if received any error write down.
Click to expand...
Click to collapse
hi there
I did as you advised, it does say relocked now, but when I try to install RUU_PRIMO_U_ICS_40A_HTC_Europe_1.41.401.1_Radio_20.62.30.0830U_3822.15.00.03_M_release_247272_signed.exe this will not install
my windows xp sp3 has no drivers and it's all up to date, here is a small video up to where it goes. y o u t u . b e/7TwtU_1rJZU or search on youtube my video titled: htc ruu rom not installing on windows xp sp3
Please read and understand the guide and accompanying links in their entirety before beginning.XDA and I am not responsible for anything you do to your phone.
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
While trying to run an RUU to reset my phone, I kept running into an issue: "htc_fastboot.exe has stopped working". I could get my phone to restart, but the RUU would not run successfully. I searched this site and the internet for an answer, but could not find anything that worked for me. Also, a lot of people in Q&A tend to have issues getting the RUU to work. That's why I'm writing this guide. Hopefully someone who is having trouble will search and stumble across it. I tried everything I could find - 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 so the guide is written from that perspective.
Steps:
1. Make sure that your computer can see your phone when you boot into fastboot. It should say Fastboot in red that changes to Fastboot USB when plugged into your computer. There are guides that help with this, so I'm not going to go into much detail. Basically you install HTC Sync to your computer and then uninstall it but leave the drivers.
2. Get a copy of fastboot and ADB. The easiest way is to get the SDK from Google (tools only) as it also includes drivers, but you can get just fastboot and adb from here (I did not use this tool personally).
3. To verify that your phone and computer are talking, open a command prompt window (I always open as administrator) and go to the folder that contains fastboot. Type "fastboot devices" (no quotes) and it should list your phone. If it does not, something did not work right with steps 1 and 2.
4. 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 by typing "fastboot oem lock" (again, no quotes).
5. Download the Full Firmware from RUU here. While you're there, get the RUU as well. Make sure to get the one that is not decrypted (first link). Copy both into the folder with fastboot.
6. Flash the firmware file using fastboot following the directions in the OP from where you got it. To summarize, rename the firmware zip file to firmware.zip. Then at a command prompt, type "fastboot oem rebootRUU". When the phone shows a black screen that says HTC, type "fastboot flash zip firmware.zip". The command prompt window will show a bunch of stuff as it does its thing. When you get back to the command prompt, it's finished. At this point, type "fastboot reboot-bootloader" to restart back into the (hopefully now stock) bootloader. Personally, I had to repeat the last command again because it failed the first time.
7. At this point, you should be in the stock hboot. It should say fastboot USB in red. Now time to RUU.
8. The current RUU is an exe so run the RUU you download before (if you have a zip file, unzip the RUU and run ARUWizard.exe). I personally ran it as an administrator just to make sure limited privileges didn't cause an issue. Read each screen and keep clicking next. Eventually it will do its thing. It takes about ten minutes and sometimes seems to be frozen. Have patience grasshopper.
And that's it. I'm now running pure stock (not for long I'm sure), still s-off. If you are s-on, you will have to unlock your bootloader again.
Good luck!
I'll be the first to troll post in this guide
Nice work brother.
I've noticed the newer RUU's (M7 and M8) require you to have the matching hboot to run correctly even if your device is s-off.
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
kushanson said:
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
Click to expand...
Click to collapse
You're welcome. Glad it helped. Also, thank you for the heads up about the RUU being an exe now. It was a zip file when I wrote the guide. I've fixed the guide to reflect the change.
Dude...
I was soft bricked for about an hour until I found this. It seems fairly obvious to me now, but for some reason I had thought that only flashing the full_firmware zip in fastboot would suffice. I guess the tiny file size (80MB unzipped???) should have tipped me off.
Regardless, I'm back up and running. Thanks, coal.
i am getting error bootloader signature failed how to fix please
rajnshubham said:
i am getting error bootloader signature failed how to fix please
Click to expand...
Click to collapse
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
coal686 said:
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
Good luck!
Click to expand...
Click to collapse
Thanks for your guided I was able to fix an old One that I had laying around, thanks again
coal686 said:
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
Click to expand...
Click to collapse
i think the problem was due to same hboot error. i get to know this thing few days back. anyway thanks coal686. now i updated with the ruu having hboot 1.56 and now i m on kitkat 4.4.2 stock. i can update now to higher ones. thanks buddy
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for using my guide!
The first step is to flash the "full firmware from RUU" (it's actually labelled that way in the OP of the linked post). It's only the firmware, not the full RUU. Then, follow that up with the .exe file which is the entire RUU. For some reason, the RUU wouldn't run for me without flashing the firmware first.
Since you are already on hboot 1.6, you probably don't have to flash the firmware first, but I'd do it just to be safe.
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Just run it. Fastboot flash the firmware then just run the RUU exe.
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
cowboysgz said:
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
Click to expand...
Click to collapse
.
Thanks
Device not recognized
Whenever I plug in my device and go to fastboot, my computer tells me "USB Device not recognized". I've installed the drivers from HTC, I even went to Decide manager on my PC to see if the device appears at all. It shows on the top under "Android USB Device" and it's labeled "My HTC" but it has the error symbol on it, so o deviced to unistall the driver and install it manually. It said that I already had the correct driver.
The reason I'm trying to do all this is, back in 2013 I had put Viper ROM on my device, it worked great, I also installed cyanogen mod as well and that worked great, at the time I wanted to have the double tap to wake feature, so I installed a custom Kernel to allow that. When I had booted up my phone the HTC logo didn t go away, then the lock screen showed up, I unlocked my phone, the HTC logo was still there, then my home screen finally opened and some apps wouldn't open. Then it would restart, so I rebooted it and it would do the same thing, turn on, show the HTC, start then restart. I could go into recovery fine, Install updated version of rom, and the same problem persists
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
krakora said:
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
Click to expand...
Click to collapse
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
coal686 said:
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
Click to expand...
Click to collapse
Thanks so much Coal, that absolutely worked. The RUU exe runs for me, but getting 155 unknown error. Evidently its not the right RUU for my device. My bootloader is "relocked" already, S-on. So confusing. When I was following the directions on the guide, when flashing the firmware, I was getting the 12 missing signatures error also, I'm assuming its not reading it as an HTC signed firmware. Any ideas on my next direction? Best, Rich
in short, I have a playstore M7_UL that just won't switch to LTE after flashing a couple of lolipop based roms, I already tried messing around with the APN settings. stock roms such as this one (http://forum.xda-developers.com/showthread.php?t=2499452) will work properly with every single feature the phone should have if it was originally from T-Mobile, however I would Ideally like to update my phone to 12.
do you have any suggestions for this problem? or am I stuck with this 4.3 rom? I would like to thank you in advance for your time and consideration, and I wait eagerly for your response.
BNMotive said:
I've tried updating to several Lolipop roms, flashed 2 different radios as well as double checked APN settings and confirmed that my Sim card does support LTE however no luck, I've been having the issue of not being able to retain LTE support. only rom that worked completely was this one http://forum.xda-developers.com/showthread.php?t=2499452 the help would be greatly appreciated to resolve this nightmare.
my carrier is T-Mobile.
Click to expand...
Click to collapse
That is a very old ROM, have you updated your system to the latest Sense 6 firmware? If not, then you might want to run the latest TMOUS RUU. When completed, check to see if you have LTE. My guess you will, then if you want you can try one of the Lollipop ROM.
majmoz said:
That is a very old ROM, have you updated your system to the latest Sense 6 firmware? If not, then you might want to run the latest TMOUS RUU. When completed, check to see if you have LTE. My guess you will, then if you want you can try one of the Lollipop ROM.
Click to expand...
Click to collapse
this makes a ton of sense to me, so I decided to downloaded this RUU http://forum.xda-developers.com/htc-one-tmobile/general/ruu-t-mobile-htc-one-android-4-4-3-t2995420
I tried flashing it through my PC but I get this "Error [170] USB connection error" I read briefly over the code and there are some mentions of re-locking my phone, before I get deeper into this, do you have any suggestions for flashing the right RUU?
I really appreciate the help
BNMotive said:
this makes a ton of sense to me, so I decided to downloaded this RUU http://forum.xda-developers.com/htc-one-tmobile/general/ruu-t-mobile-htc-one-android-4-4-3-t2995420
I tried flashing it through my PC but I get this "Error [170] USB connection error" I read briefly over the code and there are some mentions of re-locking my phone, before I get deeper into this, do you have any suggestions for flashing the right RUU?
I really appreciate the help
Click to expand...
Click to collapse
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Utterly Clueless
majmoz said:
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Click to expand...
Click to collapse
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
BNMotive said:
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
Click to expand...
Click to collapse
I think you have a gross firmware - ROM mismatch. You are running version 1.XX firmware with a version 6.XX or 7.XX rom. You need to update your phone to at least version 6.XX and then see if CM12 will give you 4G. If you still have troubles with it in CM12 but not in the stock then it is CM12 that is the issue! These need to be done in order so that you don't brick your phone!!!
RUU 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.1
RUU 6.10.531.10
BNMotive said:
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
Click to expand...
Click to collapse
if you have a read through the CM12 thread or use the search feature within the thread itself, you will find that 4G / LTE is currently a problem for most users and in all not working, seem's to be a problem with 11 and 12 at the moment.
tried installing the first one, I get Error [155] "The ROM update utility cannot update your android phone. please get the correct ROM update utility and try again."
is there a way to give detailed information of my phone's firmware status? would that help? I thank you for the help.
BNMotive said:
tried installing the first one, I get Error [155] "The ROM update utility cannot update your android phone. please get the correct ROM update utility and try again."
is there a way to give detailed information of my phone's firmware status? would that help? I thank you for the help.
Click to expand...
Click to collapse
as you are s-on you will need to do the updates in order, therefore your next one you'll need will either be a 1.28.531.xx or 1.29.531.xx or even 2.24.531.xx, you need to do them in the correct order otherwise you'll just keep erroring out, easier to just s-off on your current firmware.
you cant jump from 1xxxxxx to 3xxxxxxx
Windows 8.1 proved to be a very bad choice to begin flashing old RUUs. USB drivers went rogue on me, so I decided to switch to an old beat up windows 7 system. worked like a charm, I was able to flash 1.2 and 3.2 things were looking up till tried 4.2, both windows 8.1 and 7 killed the installer, 7 says it is a USB error [171] while 8.1 says it is the wrong RUU. apparently I am not the only one with this issue, I'll see what I can find. I feel that thanks to your help guys I am getting real close, I can almost smell the sweet scent of fresh 4G lolipop brewing.
BNMotive said:
Windows 8.1 proved to be a very bad choice to begin flashing old RUUs. USB drivers went rogue on me, so I decided to switch to an old beat up windows 7 system. worked like a charm, I was able to flash 1.2 and 3.2 things were looking up till tried 4.2, both windows 8.1 and 7 killed the installer, 7 says it is a USB error [171] while 8.1 says it is the wrong RUU. apparently I am not the only one with this issue, I'll see what I can find. I feel that thanks to your help guys I am getting real close, I can almost smell the sweet scent of fresh 4G lolipop brewing.
Click to expand...
Click to collapse
Error 171 is a connection error, meaning the RUU can't connect to/find your phone, recheck your drivers with the phone booted and plugged into the computer and also recheck your drivers with the phone in the bootloader and plugged into your PC, I think you might find when its in the bootloader you have "One" with a yellow exclamation mark in device manager, you will have to manually force the driver, right click and select update driver, you the manual installation instructions, don't let windows search anything itself, it will fail.
have you also tried to just run the updates from your phone, ie settings - about - software updates ?
majmoz said:
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Click to expand...
Click to collapse
majmoz said:
I think you have a gross firmware - ROM mismatch. You are running version 1.XX firmware with a version 6.XX or 7.XX rom. You need to update your phone to at least version 6.XX and then see if CM12 will give you 4G. If you still have troubles with it in CM12 but not in the stock then it is CM12 that is the issue! These need to be done in order so that you don't brick your phone!!!
RUU 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.1
RUU 6.10.531.10
Click to expand...
Click to collapse
Seanie280672 said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone, recheck your drivers with the phone booted and plugged into the computer and also recheck your drivers with the phone in the bootloader and plugged into your PC, I think you might find when its in the bootloader you have "One" with a yellow exclamation mark in device manager, you will have to manually force the driver, right click and select update driver, you the manual installation instructions, don't let windows search anything itself, it will fail.
have you also tried to just run the updates from your phone, ie settings - about - software updates ?
Click to expand...
Click to collapse
after the first comment in this post yeah, I had installed a very early TMOUS RUU, from there it asked to be updated to Sense 6.0, I let it update and from there I flashed CM12 and I had no 4G. would something different happen if i try this again now that I flashed 1.2 and 3.2?
more info though, both computers do "update" the phone but get interrupted. regarding the "wrong" RUU error message from windows 8.1, it says "ERROR[158]: Image Error"
BNMotive said:
after the first comment in this post yeah, I had installed a very early TMOUS RUU, from there it asked to be updated to Sense 6.0, I let it update and from there I flashed CM12 and I had no 4G. would something different happen if i try this again now that I flashed 1.2 and 3.2?
more info though, both computers do "update" the phone but get interrupted. regarding the "wrong" RUU error message from windows 8.1, it says "ERROR[158]: Image Error"
Click to expand...
Click to collapse
Im sure I read through here somewhere ages ago about users having problems with the 4xxxxx update, have a search through this forum for T-Mobile RUU, it was in the main RUU thread, and im sure someone fixed it too.
http://forum.xda-developers.com/htc-one-tmobile
ok so I'm not even gonna explain what brought me here to this point with this phone lol, here is the deal right now...first off the phone works, I just relocked the bootloader, TWRP is installed and I have a stable running rom, the phone boots up normally...the rom I'm using is the one created by a member for VM/Sprint that is debloated, now I guess I could just ask the simple question, wich is why the hell no matter what I do why cant I sign into the HTC theme thing (this is btw why I am reverting back to factory everything) idk if its a problem with the rom, but me and my non patient self decided to just say F it and go back to factory (after that I will Unlock BL again, flash TWRP and flash SU) now I did see on this page for the debloated rom, that there is a full stock rooted img, but every time I tried that one, it returned a error saying something about not finding the meta inf something, so again this brings me back to scratch...so I DL the RUU and ran it, well first time it failed with a 155 error, ok I get it, BL was unlocked, ok I fixed that, BL is now relocked, confirmed in BL
Software Status Official
Relocked
S-On
now re running the RUU from normal bootup, it does its thing, restarts goes into RUU mode, and then when its tying to push, it fails again with a 155 error, I'm at a loss, please help me
or if possible, help me fix the original problems I stated first, either way is fine
Thanks
Michael
UPDATE!!!!
ok after doing some reading...I just kept re running the RUU over and over again, about the 5th time it took, now phone is fully back to stock...however
how do I unlock my BL since I relocked it?
WOW I'm on a roll today!!!!
I just unlocked it like normal, I still had the Unlock_code.bin and I just simply reflashed it, VOILA!!
Deimos_Phobos said:
ok so I'm not even gonna explain what brought me here to this point with this phone lol, here is the deal right now...first off the phone works, I just relocked the bootloader, TWRP is installed and I have a stable running rom, the phone boots up normally...the rom I'm using is the one created by a member for VM/Sprint that is debloated, now I guess I could just ask the simple question, wich is why the hell no matter what I do why cant I sign into the HTC theme thing (this is btw why I am reverting back to factory everything) idk if its a problem with the rom, but me and my non patient self decided to just say F it and go back to factory (after that I will Unlock BL again, flash TWRP and flash SU) now I did see on this page for the debloated rom, that there is a full stock rooted img, but every time I tried that one, it returned a error saying something about not finding the meta inf something, so again this brings me back to scratch...so I DL the RUU and ran it, well first time it failed with a 155 error, ok I get it, BL was unlocked, ok I fixed that, BL is now relocked, confirmed in BL
Software Status Official
Relocked
S-On
now re running the RUU from normal bootup, it does its thing, restarts goes into RUU mode, and then when its tying to push, it fails again with a 155 error, I'm at a loss, please help me
or if possible, help me fix the original problems I stated first, either way is fine
Thanks
Michael
Click to expand...
Click to collapse
If sounds to me like your original problem was uninstalling the stock Sense home launcher. The Sense 7 theme stuff won't work without it
Sent from my HTC Desire 626s using Tapatalk
RUU troubles?
I had a problem with the RUU running and found that (I'm running vista) I needed to download and install from Microsoft the Microsoft Visual C++ 2008 Redistributable Package (X86) onto my laptop and presto...it worked.
Maybe the same problem? Hope I helped you.