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
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
Hey guys, I've been using the HTC One and I've run into some troubles, someone else had this phone previously so I'm not very aware on what this phone is running.
The phone is unable to do any software updates which I believe it is because it is running a different/custom rom?
On the bootloader screen the phone is tampered and unlocked with S-on.
I don't really need for it to be COMPLETELY reverted back to factory settings, I just want the phone to be updatable and have the ability to install custom roms like Cyanogen.
How would I go about doing this?
Also want to add that I am very very new to this and have looked at a lot of things without really getting it all...
Thanks
Jakuzure said:
Hey guys, I've been using the HTC One and I've run into some troubles, someone else had this phone previously so I'm not very aware on what this phone is running.
The phone is unable to do any software updates which I believe it is because it is running a different/custom rom?
On the bootloader screen the phone is tampered and unlocked with S-on.
I don't really need for it to be COMPLETELY reverted back to factory settings, I just want the phone to be updatable and have the ability to install custom roms like Cyanogen.
How would I go about doing this?
Also want to add that I am very very new to this and have looked at a lot of things without really getting it all...
Thanks
Click to expand...
Click to collapse
Well as the saying goes "You can't have your cake and eat it too"
If you want the stock phone that will do OTA updates you can't flash custom roms. If you want to flash custom Roms you can't take OTA updates ... so which do you choose ?
Revert
clsA said:
Well as the saying goes "You can't have your cake and eat it too"
If you want the stock phone that will do OTA updates you can't flash custom roms. If you want to flash custom Roms you can't take OTA updates ... so which do you choose ?
Click to expand...
Click to collapse
I want the phone to be stock as it's on some altered stock rom that I'm not aware of...
Jakuzure said:
I want the phone to be stock as it's on some altered stock rom that I'm not aware of...
Click to expand...
Click to collapse
OK then we need more information do you have fastboot and adb setup on your PC ? If yes please post the results from fastboot getvar all - minus your serial no and IMEI. From their we can locate you a RUU to return the phone to Stock.
clsA said:
OK then we need more information do you have fastboot and adb setup on your PC ? If yes please post the results from fastboot getvar all - minus your serial no and IMEI. From their we can locate you a RUU to return the phone to Stock.
Click to expand...
Click to collapse
I have them both set up from this, running that command just gives me a "< waiting for device >" message that doesn't appear to change.
Jakuzure said:
I have them both set up from this, running that command just gives me a "< waiting for device >" message that doesn't appear to change.
Click to expand...
Click to collapse
Let me guess: You're on Windows 8.1 and you've never installed any OTA's after 4.2.2
If that's the issue, you have two solutions:
1) Use a Windows 7 PC
2) Update your HBOOT to 1.55/1.56
raghav kapur said:
Let me guess: You're on Windows 8.1 and you've never installed any OTA's after 4.2.2
If that's the issue, you have two solutions:
1) Use a Windows 7 PC
2) Update your HBOOT to 1.55/1.56
Click to expand...
Click to collapse
Nope...? I'm on Windows 7 Home Premium, 64-bit
The Rom I'm running, while solid, is no longer being developed so I'm beginning the process of changing to another Rom. My issue is that I've since switched to Windows 8.1 and I can't get it to fully recognize my m7. I'm pretty sure I'm going to need full drivers/etc to upgrade my TWRP from 2.6.3.0 to 2.whatever it is now. I also read somewhere that hboot 1.44 (I have it and s-off) that it doesn't agree with 8.1. I'm somewhat familiar with flashing Roms/themes/etc but little out of my depth when taking on the hboot area. Could someone please direct me as to how to update that and also how to get my 8.1 to completely see my m7? Thanks in advance for your time.
You will have to use a PC that is not 8.1 to update your hboot then you will be golden with 8.1
BD619 said:
You will have to use a PC that is not 8.1 to update your hboot then you will be golden with 8.1
Click to expand...
Click to collapse
Thanks. I've got a windows 7 laptop I can use. I must be missing something though as I'm not finding a thread that can walk me through updating the hboot. Would someone please direct me to that? Thansk again.
Treadstone06 said:
Thanks. I've got a windows 7 laptop I can use. I must be missing something though as I'm not finding a thread that can walk me through updating the hboot. Would someone please direct me to that? Thansk again.
Click to expand...
Click to collapse
You can flash the Firewater hboot follow the directions there and make sure you choose the one for Sprint M7
BD619 said:
You can flash the Firewater hboot follow the directions there and make sure you choose the one for Sprint M7
Click to expand...
Click to collapse
Thanks again. I've got that done and updated twrp. I just have 1 more thing if you'd be so kind. I'm wanting to update to the latest prl/firmware/radio but when I try to update them through setting, it fails. After looking around I found this thread: http://forum.xda-developers.com/showpost.php?p=53007098&postcount=2. Since I'm on a custom Rom, should I just flash the modified firmware and does that one zip include radio/prl/etc?
Thanks again.
Treadstone06 said:
Thanks again. I've got that done and updated twrp. I just have 1 more thing if you'd be so kind. I'm wanting to update to the latest prl/firmware/radio but when I try to update them through setting, it fails. After looking around I found this thread: http://forum.xda-developers.com/showpost.php?p=53007098&postcount=2. Since I'm on a custom Rom, should I just flash the modified firmware and does that one zip include radio/prl/etc?
Thanks again.
Click to expand...
Click to collapse
PRL is not included in the firmware if PRL and Profile are failing in settings then it's most likely a network problem.
You can flash the modified firmware it will update your radio and some other bits.
I flashed a gsm rom on my sprint m7, which put it into a bootloop....
I tried the firmware fix , but ended up with signature failures.
I haven't been able to get the RUU.exe to run on my windows 8 machine.
Wondering if anyone can supply me with 5.05.651.02RUU flashable zip?
I've searched, and see a bunch of flashable firmwares, but non for 5.05.651.02.
Or maybe a solution to my ruu.exe problem? I've tried the guides supplied in this forum, but still can't get passed the installation screen.
Thank you !
Can u open the ruu at least to the first menu
phonegeekjr said:
Can u open the ruu at least to the first menu
Click to expand...
Click to collapse
No, just install wizard "loading" . when its done it either freezes the computer , or does nothing.
I have tried to open it using "compatibility" which tells me to use win 7. But no luck.
Looking for a way to just push it too the phone. Seems easiest.
Supertacomonkeyexplosion said:
No, just install wizard "loading" . when its done it either freezes the computer , or does nothing.
I have tried to open it using "compatibility" which tells me to use win 7. But no luck.
Looking for a way to just push it too the phone. Seems easiest.
Click to expand...
Click to collapse
Hmm can I have the link to where you got it. And out of curiosity why not upgrade to 6.16.651.2 which is lollipop
phonegeekjr said:
Hmm can I have the link to where you got it. And out of curiosity why not upgrade to 6.16.651.2 which is lollipop
Click to expand...
Click to collapse
I can use 6.16.651.2 flashableRUU ?
The phone is unusable right now, bootloops. I thought I had to be s-off to flash anything but the firmware that's present. Am I wrong?
My end game was to use the phone on at&t. I thought I could flash a gsm ROM to accomplish that.
Can I still s-off and sim unlock lollipop? Or at least s-off and downgrade?
Thanks for the help
I tried downloads from here:
[RUU][Firmware]Sprint HTC One | 6.16.651.2 | *Updated 2.10.15*
And I also tried the RUU from the official HTC website.
And I also tried the ripped "firmware only" from http://forum.xda-developers.com/showthread.php?t=2503646
There is an ruu in that thread that has a fastboot flashable zip. You might want to read through how to run it on your device. You shouldn't ever flash a gsm Rom to a Sprint phone. The mount points are different.
Solution: get a new computer.
Not sure what was going on but I could not get the ruu to run on windows 8.1. Drivers, adb,fastboot all working on the computer. I couldn't find the problem.
Dug up an old windows XP machine I have , worked in an instant.
No knowledge gained.
The RUU exe take a lot of RAM to run. please make sure you have no other programs running when running the exe. If you device is stuck in a boot loop try power the device down and into recovery mode. Then connect to terminal when the RUU ask to connect to the device. My guess is the the RUU is corrupt and try re-downloading the file. If all else fails relock the boot loader and try returning to stock.
Huge amount of frustration with trying to deal with my phone
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
F0rZ3r0 said:
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
Click to expand...
Click to collapse
Flashing RUU requires locked bootloader.
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
F0rZ3r0 said:
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
Click to expand...
Click to collapse
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Alright, doing this now. I'm a lot calmer today, so I can do this.
dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
F0rZ3r0 said:
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
Click to expand...
Click to collapse
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Sloth said:
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Click to expand...
Click to collapse
My apologies for the swearing, was angry at the time.
Also, my hboot version seems to be 3.18. Not sure what to do in order to be able to flash firmware. My OS version seems to be 2.16.651.4 as well if that helps.
What would I have to do in order to install a ROM and how?
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
dopy25 said:
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
Click to expand...
Click to collapse
I believe I'm S-OFF.
F0rZ3r0 said:
I believe I'm S-OFF.
Click to expand...
Click to collapse
look in bootloader it will tell you if you are s-off or s-on.
Sloth said:
look in bootloader it will tell you if you are s-off or s-on.
Click to expand...
Click to collapse
Never mind, S-ON.
F0rZ3r0 said:
Never mind, S-ON.
Click to expand...
Click to collapse
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Sloth said:
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Click to expand...
Click to collapse
Umm...I don't have anything called SDK :/
What do I do then?
F0rZ3r0 said:
Umm...I don't have anything called SDK :/
What do I do then?
Click to expand...
Click to collapse
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Sloth said:
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Click to expand...
Click to collapse
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
F0rZ3r0 said:
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
Click to expand...
Click to collapse
Should only be a few seconds.
Sloth said:
Should only be a few seconds.
Click to expand...
Click to collapse
Not sure what the issue here is then. As I write this, it is still sending. I'm not sure what the issue is...
Check PM.