Related
Does anyone know any way to get the One S back to as close to stock as possible? I'm returning my phone to T-mobile for service and I can't get 'TAMPERED' to disappear from HBoot without the RUU. Also, now having an issue with every time I turn on the phone it has the developer text on the splash screen even though it isn't entering hboot or recovery.
Does anyone have any ideas on either issue? The only threads I can find are people with pretty much the same issue and no solution or pre 2.35 updates.
fbihawk said:
Does anyone know any way to get the One S back to as close to stock as possible? I'm returning my phone to T-mobile for service and I can't get 'TAMPERED' to disappear from HBoot without the RUU. Also, now having an issue with every time I turn on the phone it has the developer text on the splash screen even though it isn't entering hboot or recovery.
Does anyone have any ideas on either issue? The only threads I can find are people with pretty much the same issue and no solution or pre 2.35 updates.
Click to expand...
Click to collapse
Sorry, I should also mention I've loaded a nandroid backup of the stock rom without root and attempted to flash the "stock" recovery. I'm not sure about the recovery because I don't believe it came from the 2.35 software and that's when I started to have issues with the splash screen. Loaded TWRP back on and still same issue.
Also, was having issues after with the device not loading to anything but bootloader until I re-unlocked it then it started fine.
I don't think you're gonna be able to do anything without ruu
mbernusg said:
I don't think you're gonna be able to do anything without ruu
Click to expand...
Click to collapse
That's kind of what I was afraid of. Any ideas on when that could be? Or if HTC would have that file?
from personal experience, dont worry about it, t-mobile wont care.
I had a sidekick that I bricked, and there was no way to even power it on, went to tmobile with custom sw and recovery...
also I had a sensation that i sent back with custom rom and a custom recovery because the phone would not get power, never heard anything about.
I read somewhere online that tmobile returns the phones to stock even before they check them.
if you send it back as is, you SHOULD be fine... ive done it twice.
jahnbodah said:
from personal experience, dont worry about it, t-mobile wont care.
I had a sidekick that I bricked, and there was no way to even power it on, went to tmobile with customer sw and recovery...
also I had a sensation that i sent back with custom rom and a custom recovery because the phone would not get power, never heard anything about.
I read somewhere online that tmobile returns the phones to stock even before they check them.
if you send it back as is, you SHOULD be fine... ive done it twice.
Click to expand...
Click to collapse
That definitely relieves a little stress. Thanks!
fbihawk said:
Sorry, I should also mention I've loaded a nandroid backup of the stock rom without root and attempted to flash the "stock" recovery. I'm not sure about the recovery because I don't believe it came from the 2.35 software and that's when I started to have issues with the splash screen. Loaded TWRP back on and still same issue.
Also, was having issues after with the device not loading to anything but bootloader until I re-unlocked it then it started fine.
Click to expand...
Click to collapse
Could you provide a link for the stock nandroid? It would be much appreciated! I am on CM 10 but can't get back to stock. The stock nandroid I downloaded the other day fails upon restoring everytime.
jaker.the.skater said:
Could you provide a link for the stock nandroid? It would be much appreciated! I am on CM 10 but can't get back to stock. The stock nandroid I downloaded the other day fails upon restoring everytime.
Click to expand...
Click to collapse
I just used the one in the dev section.
Alright here's the issue...
Ok so my brother had my rooted HTC SENSATION S-ON with CM9, and he was longboarding and txting (bad combination...). As it results, obviously, he fell and desintegrated the screen, but the phone was fully functional before. Couple of months after the incident, before fixing it, i took it out of the drawer i had it put away and turned it on, and earlier that day i had found a very stable cm10.1 rom for it so i went ahead and installed it because wifi and bluetooth was functional on it. After i do so, i try to turn my wifi on in the innitial Google log on and on the screen it said "Turning WiFi on." and i waited about half an hour and nothing, so i skipped it. When i went into the settings app i tried turning bluetooth on and the switch went back to off instantly. And i went online and did research and saw a guy that just pulled the bluetooth and wifi connectors for the antenna up so they would actually work, and i tried it, but no luck... I also tried flashing the boot.img for the current rom, but also didnt work. So i thought it might have been the rom since it wasnt fully stable yet, so i did a full wipe and re-flashed the currnet rom and re-flashed the boot.img but no luck. So i downloaded a stable release of cm9 and did full wipe and installed the boot.img for that version of cm9, but yet again no luck... So i re-installed the cm10.1 Albinoman build and lived on 4G so far... i need help on re-enabling bluetooth and wifi....plz help im desperate
P.S. I think this might have to do with the incident of the screen, but i dont think its hardware related...anyways im going to have the screen replaced this monday, so wish me luck
Try formatting all the partitions except for SD card and then reflash the ROM.
Look here for general solutions: http://forum.xda-developers.com/showthread.php?t=2085025
Sent from my HTC Sensation
AndroidSupporter318 said:
Try formatting all the partitions except for SD card and then reflash the ROM.
Look here for general solutions: http://forum.xda-developers.com/showthread.php?t=2085025
Sent from my HTC Sensation
Click to expand...
Click to collapse
tried that already
Which recovery do you have? If you don't have 4EXT, you need to get flash it, otherwise, you need to s-off your phone
Sent from my HTC Sensation
AndroidSupporter318 said:
Which recovery do you have? If you don't have 4EXT, you need to get flash it, otherwise, you need to s-off your phone
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea i got 4EXT and i always use smartflash when flashing anything at all
Hmmm... what is your radio version and hboot version number? Try to obtain s-off, and then flash firmware 3.33(i think it has a different radio that might fix your problem)
Also, make sure that you s-off before flashing 3.33 from bootloader.
Here's s-off guide: http://forum.xda-developers.com/showthread.php?p=25202517
Here's firmware 3.33: http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation
AndroidSupporter318 said:
Hmmm... what is your radio version and hboot version number? Try to obtain s-off, and then flash firmware 3.33(i think it has a different radio that might fix your problem)
Also, make sure that you s-off before flashing 3.33 from bootloader.
Here's s-off guide: http://forum.xda-developers.com/showthread.php?p=25202517
Here's firmware 3.33: http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation
Click to expand...
Click to collapse
I cant read the version due to the dead chunks on the screen but i should have it fixed in a couple of days. I preffer not trying to s-off since i find that too complicated, but in case i had to do so, would i have to do a full wipe?
No, a full wipe is not required for s-off.
You can go to "about phone" in the settings to find out about your radio version. It should be the baseband numbers/letters.
Also, which kernel do you have? Flashing another kernel might solve the problem.
Try flashing this kernel: http://forum.xda-developers.com/showthread.php?p=36216263
Or this one: http://forum.xda-developers.com/showthread.php?p=16608447
Sent from my HTC Sensation
i took it to get fixed and they fixed the screen and tried to fix this issue but couldnt and told me
it was a motherboard issue and that it was broken, but i highly doubt it because everything else works
perfectly fine, although i tried the kernel (Sultan) and it didnt work...still got that same issue
Well, did you get s-off on your phone? I think the only way is to fix your radio (flash 3.33) but you need s-off for that... Other than that, I have no idea.
BTW, did you try stock ICS before? If yes, how did it go?
Here's some quick fixes to WiFi: http://forum.xda-developers.com/showthread.php?t=1469428
Sent from my HTC Sensation
dosnoventa said:
i took it to get fixed and they fixed the screen and tried to fix this issue but couldnt and told me
it was a motherboard issue and that it was broken, but i highly doubt it because everything else works
perfectly fine, although i tried the kernel (Sultan) and it didnt work...still got that same issue
Click to expand...
Click to collapse
hi, didn't see anywhere that you mention your android version, if it is 4.2.X, don't try to turn the WiFi on, rather go to advanced WiFi settings and select a region code in there, whatever you liked. but in case it is 4.1.X then Install WiFix Manager while WiFi is off, and reboot your phone.
good luck. :good:
AndroidSupporter318 said:
Well, did you get s-off on your phone? I think the only way is to fix your radio (flash 3.33) but you need s-off for that... Other than that, I have no idea.
BTW, did you try stock ICS before? If yes, how did it go?
Here's some quick fixes to WiFi: http://forum.xda-developers.com/showthread.php?t=1469428
Sent from my HTC Sensation
Click to expand...
Click to collapse
as a matter of fact i did try the stock ics and it had the same issue, unafortunately i havent s-off yet, but im not quite sure i want to do that
A friend of mine haf the same problem about a year back. Tried softwarefix but no luck. Restocked it and got the board replaced by htc.
Sent from my GT-N7105 using xda app-developers app
AndroidSupporter318 said:
Well, did you get s-off on your phone? I think the only way is to fix your radio (flash 3.33) but you need s-off for that... Other than that, I have no idea.
BTW, did you try stock ICS before? If yes, how did it go?
Here's some quick fixes to WiFi: http://forum.xda-developers.com/showthread.php?t=1469428
Sent from my HTC Sensation
Click to expand...
Click to collapse
I did try stock ics, even resetting the phone to stock but no luck. Though i might not want to s-off, finding
that the process is pretty complicated, i yet do not have the knowledge to understand.
help
Hey guys I need help with my galaxy note 2 t0ltetmo, if anyone is interested and is willing to help me with this one I'd appreciate it, cause no one seems to help me. Please help if you can, I'm in desperate need here. Anyways here's the link to the forum: http:// http://forum.xda-developers.com/showthread.php?p=48442689&nocache=1
So I have used TMOUS rom for ALONG time and recently decided to switch to use Cyanogen being a fan of it form other platforms.
While on the TMOUS rom I had 4g connectivity in my area about 90% of the time with the occasional drop into 3g here and there. It always displayed a 4g image in the top.
When I switched to Cyanogen that pretty much stoped. It always says 3g and is slow as hell. every once in awhile it will say H+ but not for long. MOST of the time it is constantly switching between 3g/4g/edge then shutting off.
Now im not sure if its a rom problem or not, but its making me want to switch back to a TMOUS rom.
Any suggestions would be great!
Edit: Just for clairification, I am S-On
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
cp101 said:
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
Click to expand...
Click to collapse
Damn, this scares me.... any solution anyone?
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
cp101 said:
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
Click to expand...
Click to collapse
Unfortunately, it doesn't seem to be a hardware problem
I have been trolling the net for weeks but have not found a solution yet.
I've posted in threads here but no solution.....
My issues started when I went to CM ROM - I used to have great 4g all the time before I went to custom rom (I was on stock TMO US) .. Now no matter what I do, I am not able to get 4G again.... it's really irritating...
I've tried a bunch of custom ROMS.. I am on 1.13 HBOOT and S-ON .. .. CID = HTC__001 (originally my CID was stock TMO US CID whatever that is but now its not that.. I don't wan to run RUU because I don't have TMO US CID and dont want to brick my phone)
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
cp101 said:
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
Click to expand...
Click to collapse
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
bnd10706 said:
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
Click to expand...
Click to collapse
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
cp101 said:
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
Click to expand...
Click to collapse
my phone is still under warrenty. Im wondering if i am able to revert back to stock without them knowing if I can get a phone replacement.
From what I've read, it's doable; even with an unlocked phone. But I'd really like to know what in the dev's source code made this happen... it's a bit ridiculous.
jenenser83 said:
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
Click to expand...
Click to collapse
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
bnd10706 said:
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
Click to expand...
Click to collapse
Can you take me through the steps you took to achieve all of this? Thanks.
cp101 said:
Can you take me through the steps you took to achieve all of this? Thanks.
Click to expand...
Click to collapse
So what I did first was go into TWRP and selected wipe. Inside wipe i selected EVERYTHING, every little box. Then Wiped it.
This left nothing on the phone but the recovery. I then loaded on SuperSU from TWRP. I download the stock TMOUS rom that was posted earlier in this post.
In TWRP I mounted it and hooked it to computer and transfered the rom over.
Once the rom was on I did the install of the rom.
I rebooted the rom into bootloader.
Once in bootloader i put it into fastboot.
I had previous extracted the boot.img from the rom.
I sent the boot.img over via fastboot which restarted the phone.
Once it got all started up. No issues. I am on 4g 99% of the time now.
Im thinking the issue was definatly based in the CM rom.
Since this worked I wanted to test things out since my phone was pretty much stripped of everything.
I tried out Viper rom and a couple of other non CM based roms, and I have had no issues.
IM back on teh TMOUS rom though. Wifi calling will win over when i go overseas.
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
cp101 said:
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
Click to expand...
Click to collapse
Must be.
I did find something out though doing all my research. Did you ever at any point update the radio? TMobile uses some frequencies that some companies dont use.
It is my understanding that some of these roms are packed with radios that are generic and thus ment for multi carriers.
Not sure if thats your issue, but might want to look into.
Its nice being back on 4g though.
I was experimenting my M8 with T-Mobile sim card. I flashed 5.0.1 GPE ROM and everything worked fine. I also changed its CID to T-MOB010 and flashed ViperOneM8 3.2.1. It worked fine as well. But after I reverted everything back (by loading 3.28.605.4 0P6BIMG and firmware, and restoring a TWRP backup), I discovered I can no longer get 4G/LTE signal. I can only get 3G. I tried flashing to RUU M8_VZW 4.4.3 (firmware &0P6BIMG). But it doesn't help. I dialed *#*#4636#*#* but didn't see any option/menu. When I use 4G Switcher app to select band, 1900MHz band isn't available. The network type is set to "CDMA/EvDo/GSM/WCDMA/LTE auto". I am using CleanROM 3.0. Any advise will be greatly appreciated.
HBOOT-3.19.0.000
RADIO-1.09.20.0926
OpenDSP-v38.2.2-00542-M8974_F0.0811
OS-3.28.605.4
2ndLeaf said:
I was experimenting my M8 with T-Mobile sim card. I flashed 5.0.1 GPE ROM and everything worked fine. I also changed its CID to T-MOB010 and flashed ViperOneM8 3.2.1. It worked fine as well. But after I reverted everything back (by loading 3.28.605.4 0P6BIMG and firmware, and restoring a TWRP backup), I discovered I can no longer get 4G/LTE signal. I can only get 3G. I tried flashing to RUU M8_VZW 4.4.3 (firmware &0P6BIMG). But it doesn't help. I dialed *#*#4636#*#* but didn't see any option/menu. When I use 4G Switcher app to select band, 1900MHz band isn't available. The network type is set to "CDMA/EvDo/GSM/WCDMA/LTE auto". I am using CleanROM 3.0. Any advise will be greatly appreciated.
HBOOT-3.19.0.000
RADIO-1.09.20.0926
OpenDSP-v38.2.2-00542-M8974_F0.0811
OS-3.28.605.4
Click to expand...
Click to collapse
Try a factory reset using stock recovery. Not twrp or any custom recovery. Has to be stock recovery.
Sent from my HTC6525LVW using Tapatalk
I understand completely where you are coming from. I flashed the same rom and my phone stop connecting to LTE when in global mode. I have flashed the 4.4.2, 4.4.3, and 4.4.4 RUU and went into the stock recovery and did a factory reset and it still does not work.
Right now I am running cleanrom 3.0 also. The only time I can get LTE is when I go into settings and switch it to LTE only.
The only thing I think it can be is when I do the factory reset on the RUU, the says restoring Verizon NV flash rather than formatting it. I want to try and flash a T-MOBILE RUU to see if it will format it and clear it out then switch back to Verizon but I don't know if that will brick my phone. If I can't find a way to wipe the NV the only thing else to do is run the phone over with my car a couple times then claim warranty.
Not trying to knock digital high's rom because he and several others put a lot of work into the stock 5.0 rom and I really appreciate the effort, but I wish I didn't flash it because I think there is an underlying issue with the rom that is affecting a small portion of our phones. And it is so small that there is no support to fix it. I have scoured the forum to find a fix and nothing has worked so far. But these are the problems we accept when we hack our phones and flash non factory software.
I hope you find a fix and if you do please let me know. Good luck.
Sent from my HTC6525LVW using XDA Free mobile app
dottat said:
Try a factory reset using stock recovery. Not twrp or any custom recovery. Has to be stock recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Factory reset using stock recovery does the trick. 4G/LTE is back. Thanks a lot for the suggestion. Much appreciate it.
2ndLeaf said:
Factory reset using stock recovery does the trick. 4G/LTE is back. Thanks a lot for the suggestion. Much appreciate it.
Click to expand...
Click to collapse
No problem.
Sent from my HTC6525LVW using Tapatalk
Ruffroc02 said:
I understand completely where you are coming from. I flashed the same rom and my phone stop connecting to LTE when in global mode. I have flashed the 4.4.2, 4.4.3, and 4.4.4 RUU and went into the stock recovery and did a factory reset and it still does not work.
Right now I am running cleanrom 3.0 also. The only time I can get LTE is when I go into settings and switch it to LTE only.
The only thing I think it can be is when I do the factory reset on the RUU, the says restoring Verizon NV flash rather than formatting it. I want to try and flash a T-MOBILE RUU to see if it will format it and clear it out then switch back to Verizon but I don't know if that will brick my phone. If I can't find a way to wipe the NV the only thing else to do is run the phone over with my car a couple times then claim warranty.
Not trying to knock digital high's rom because he and several others put a lot of work into the stock 5.0 rom and I really appreciate the effort, but I wish I didn't flash it because I think there is an underlying issue with the rom that is affecting a small portion of our phones. And it is so small that there is no support to fix it. I have scoured the forum to find a fix and nothing has worked so far. But these are the problems we accept when we hack our phones and flash non factory software.
I hope you find a fix and if you do please let me know. Good luck.
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
Please try dottat's suggestion and follow the instruction below to reset:
http://www.htc.com/us/support/htc-one-m8/howto/465049.html
It should work.
Ruffroc02 said:
Not trying to knock digital high's rom because he and several others put a lot of work into the stock 5.0 rom and I really appreciate the effort, but I wish I didn't flash it because I think there is an underlying issue with the rom that is affecting a small portion of our phones. And it is so small that there is no support to fix it. I have scoured the forum to find a fix and nothing has worked so far. But these are the problems we accept when we hack our phones and flash non factory software.
Click to expand...
Click to collapse
I'm having the LTE issue as well. I'm currently running DigtalHigh's GPE 12/18 release with the updated firmware. LTE works on first boot until I connect to my Wi-Fi network, after that I never see LTE again. I tried everything, and I mean everything. I tried the RUU back to 4.4.4 and doing a factory reset from that... I get the same result, LTE on 1st boot until the WiFi connects and then it's gone for good again until the next complete reset.
The most recent thing I tried was replacing the SIM card (while on the GPE rom)... this worked flawlessly. I had LTE again for a few days... until I made a phone call from my car using Bluetooth, at which point the phone geeked out, switching from speaker to line-out to bluetooth audio and eventually dropping my call (not sure if that is somehow related to the LTE issue), but now I'm back to no LTE again.
But I get full bars of 3G, so I've got that going for me... which is nice.
Is it possible for you to put in a new SIM while on another Rom like clean rom to see if LTE will stay?
Sent from my HTC6525LVW using XDA Free mobile app
Ruffroc02 said:
Is it possible for you to put in a new SIM while on another Rom like clean rom to see if LTE will stay?
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
DH GPE with custom firmware has hooped the VZW LTE radio settings, it has overwritten them...no amount of custom rom re-installations will fix this.
As stated above, the easiest way to fix this is to simply flash a stock Verizon RUU, and THEN do a factory reset from the stock recovery. I used http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914 with the SD card method and it worked fine.
After you do the stock factory reset you can then install DH GPE again, without using custom firmware.
Croak said:
DH GPE with custom firmware has hooped the VZW LTE radio settings, it has overwritten them...no amount of custom rom re-installations will fix this.
As stated above, the easiest way to fix this is to simply flash a stock Verizon RUU, and THEN do a factory reset from the stock recovery. I used http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914 with the SD card method and it worked fine.
After you do the stock factory reset you can then install DH GPE again, without using custom firmware.
Click to expand...
Click to collapse
I tried installing the stock ruu and using the stock recovery to fix it. It hasn't worked. Did you use the method of installing through the phone or the computer?
Sent from my HTC6525LVW using XDA Free mobile app
Ruffroc02 said:
I tried installing the stock ruu and using the stock recovery to fix it. It hasn't worked. Did you use the method of installing through the phone or the computer?
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
I put 0P6BIMG.zip in ext SD card and booted from HBOOT.
My LTE just automagically kicked back on after I reset it three weeks. Glad it doesn't have to meet the tire of my car. I pray it stays on
Sent from my HTC6525LVW using XDA Free mobile app
dottat said:
No problem.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I posed this question on another thread, but I'm trying to understand what you mean when you say "stock recovery". I know what it is, but what I don't know is what stock are you referring to; do I have to downgrade to 4.4.4 or when you mean stock it doesn't matter if it's Lollipop 5.0.1.? Thank you sir!
berrywr said:
I posed this question on another thread, but I'm trying to understand what you mean when you say "stock recovery". I know what it is, but what I don't know is what stock are you referring to; do I have to downgrade to 4.4.4 or when you mean stock it doesn't matter if it's Lollipop 5.0.1.? Thank you sir!
Click to expand...
Click to collapse
I mean the matching HTC provided recovery img for the firmware version you are on.
Sent from my Nexus 6 using Tapatalk
Boy this horse is getting beat to death. Go to Dottat's RUU posts where he explains it all. I used the 5.0.1 S-Off one. Once it's installed, boot, and then reboot to it's stock/factory recovery and do a factory reset. That will fix your 4G/LTE problem. Then you get root back and flash a "custom" recovery like TWRP. I followed the Sunshine instructions. If you don't want/need root or TWRP skip it and you'll have an S-off stock not rooted phone.
dottat said:
I mean the matching HTC provided recovery img for the firmware version you are on.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It's been a few years since I wore my horse, the HD2 to death and I didn't stumble on to the cure until the wee hours this morning. It eventually comes back and like the wife hitting your head with the iron skillet...ding, ding, ding....external micros SD card and RUU; I remember how to do that. I'm S-Off, this will work. What I didn't know is what is "stock"; factory state you walked out the store with or matching the ROM to the firmware and if I'm going to downgrade to reset the NV configuration, what all that entails. It's the jargon, I need to learn and that takes time. I sincerely appreciate what the OPs do and where they direct me to; thanks!
berrywr said:
It's been a few years since I wore my horse, the HD2 to death and I didn't stumble on to the cure until the wee hours this morning. It eventually comes back and like the wife hitting your head with the iron skillet...ding, ding, ding....external micros SD card and RUU; I remember how to do that. I'm S-Off, this will work. What I didn't know is what is "stock"; factory state you walked out the store with or matching the ROM to the firmware and if I'm going to downgrade to reset the NV configuration, what all that entails. It's the jargon, I need to learn and that takes time. I sincerely appreciate what the OPs do and where they direct me to; thanks!
Click to expand...
Click to collapse
Answered this once already in the last 24 hours and this will be the last time.
Stock recovery is the matching HTC provided recovery img that is from the matching firmware version you are currently on. If you are on 1.X firmware it's best to find stock recovery from the 1.X ruu or firmware zip file.
Stock recovery is only provided by HTC.
Why is this so dang difficult to understand folks and why does the question need to be repeatedly posed?
Sent from my Nexus 6 using Tapatalk
dottat said:
Answered this once already in the last 24 hours and this will be the last time.
Stock recovery is the matching HTC provided recovery img that is from the matching firmware version you are currently on. If you are on 1.X firmware it's best to find stock recovery from the 1.X ruu or firmware zip file.
Stock recovery is only provided by HTC.
Why is this so dang difficult to understand folks and why does the question need to be repeatedly posed?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
1droidmod said:
Well, not all brains are wired the same. I do understand providing a direct link again or now would be like defeating the purpose. Although sometimes some words in some directions or answers are misleading to One and very confusing.
Sent from my HTC6525LVW using Tapatalk 2
Click to expand...
Click to collapse
Point is the information is already out there. Nothing misleading about it.
There are some basic premises that better be understood first lest he avoid failure by leaving that boot loader locked and s on.
Capiche?
Sent from my Nexus 6 using Tapatalk
dottat said:
Answered this once already in the last 24 hours and this will be the last time.
Stock recovery is the matching HTC provided recovery img that is from the matching firmware version you are currently on. If you are on 1.X firmware it's best to find stock recovery from the 1.X ruu or firmware zip file.
Stock recovery is only provided by HTC.
Why is this so dang difficult to understand folks and why does the question need to be repeatedly posed?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Because, those of us doing the asking while we truly and sincerely appreciate the work all of you do, and believe me "I" do, some of you, not all of you completely fail at the teaching aspect of the knowledge you possess. That said, thank you very much; it worked. I can't tell you whether it was the factory reset or performing the edit inside ##778; the moment I put the wife's Straight Talk (Verizon) SIM card in; 4G LTE returned. I did not have access to the dial code until now. Again, thank you!
There are very few posts found on any site about this issue so I wanted to post a success.
Symptom: M8 that either from a ROM install or OTA is 'stuck' on 3G. This persists across radio revisions and OS.
In my case, I had a M8 with S-off arrive from Swappa but it was 3g only on 4.4.4 so I took the OTA... No change. Following, I tried 3 different SIM and opened a support case with Verizon. As with the other 2 cases I found reference to in a search, the determination was a fault with the phone and it would be factory replaced under warranty. BUT this phone is S-OFF!... so I kept digging. After trying various RUU from 4.4.3, 4.4.4. and 5.01 NONE of them worked, still trapped in 3G land even with factory reset wiped cache and clean install of 4.4.4 with the Verizon OTA update to 5.01 full path.
Solution: Roll farther back! I found a very early RUU from 4.4.2 and flashed the baseband. Immediately 4g worked. Rolling forward, every firmware version I flashed after (any baseband) also worked. SO if you have a M8 that does only 3G just roll all the way back to release baseband and then back forward to 5.01.. should fix! Verizon also indicated they know of this phone sometimes not 'taking' a SIM so try a 2nd one too.
Regards and good luck,
TekGnosis said:
There are very few posts found on any site about this issue so I wanted to post a success.
Symptom: M8 that either from a ROM install or OTA is 'stuck' on 3G. This persists across radio revisions and OS.
In my case, I had a M8 with S-off arrive from Swappa but it was 3g only on 4.4.4 so I took the OTA... No change. Following, I tried 3 different SIM and opened a support case with Verizon. As with the other 2 cases I found reference to in a search, the determination was a fault with the phone and it would be factory replaced under warranty. BUT this phone is S-OFF!... so I kept digging. After trying various RUU from 4.4.3, 4.4.4. and 5.01 NONE of them worked, still trapped in 3G land even with factory reset wiped cache and clean install of 4.4.4 with the Verizon OTA update to 5.01 full path.
Solution: Roll farther back! I found a very early RUU from 4.4.2 and flashed the baseband. Immediately 4g worked. Rolling forward, every firmware version I flashed after (any baseband) also worked. SO if you have a M8 that does only 3G just roll all the way back to release baseband and then back forward to 5.01.. should fix! Verizon also indicated they know of this phone sometimes not 'taking' a SIM so try a 2nd one too.
Regards and good luck,
Click to expand...
Click to collapse
Thanks for this share. I am having an issue that may or may not be related. I have a feeling that my sim card reader is broken but my phone was actually having a similar symptoms before its radio stopped working altogether. I came back from international roaming today (and a non vzw sim) and when I arrived stateside, my phone would only pick up CDMA evdo 3g. After much fiddling in the *#*#4636#*#* menu, I did not have any luck. Then all of the sudden my phone read "no service" and wouldn't even connect to vzw at all. I tried a new sim from a vzw store, no dice. My plan was to ruu tomorrow as a last resort. I am s-off. Would you mind sharing the 4.2.2 ruu link? I'd like to try.
bacon612 said:
Thanks for this share. I am having an issue that may or may not be related. I have a feeling that my sim card reader is broken but my phone was actually having a similar symptoms before its radio stopped working altogether. I came back from international roaming today (and a non vzw sim) and when I arrived stateside, my phone would only pick up CDMA evdo 3g. After much fiddling in the *#*#4636#*#* menu, I did not have any luck. Then all of the sudden my phone read "no service" and wouldn't even connect to vzw at all. I tried a new sim from a vzw store, no dice. My plan was to ruu tomorrow as a last resort. I am s-off. Would you mind sharing the 4.2.2 ruu link? I'd like to try.
Click to expand...
Click to collapse
I have all of the ruu in one thread which is stickied in the general section.
dottat said:
I have all of the ruu in one thread which is stickied in the general section.
Click to expand...
Click to collapse
Thanks man. U think I can just reflash radio for a fix instead? Hoping for a quicker fix rather than backup> ruu >flash twrp>restore nandroid...
bacon612 said:
Thanks man. U think I can just reflash radio for a fix instead? Hoping for a quicker fix rather than backup> ruu >flash twrp>restore nandroid...
Click to expand...
Click to collapse
The s-on ruu will not wipe. They will not affect s status or unlock status. Flash ruu. Flash twrp. Flash supersu. Ten mins or less.
dottat said:
The s-on ruu will not wipe. They will not affect s status or unlock status. Flash ruu. Flash twrp. Flash supersu. Ten mins or less.
Click to expand...
Click to collapse
But I am s-off running an aosp rom. That matter? I am under the impression that flashing that ruu will take my phone back to the way it came out of a box
bacon612 said:
But I am s-off running an aosp rom. That matter? I am under the impression that flashing that ruu will take my phone back to the way it came out of a box
Click to expand...
Click to collapse
Yes that could be a problem. If you were on a sense rom it would not be. Because it does not wipe. Those ruu are unique in that they don't. The s-off ones and every other carriers ruu do wipe.
Sent from my HTC6535LVW using Tapatalk
dottat said:
Yes that could be a problem. If you were on a sense rom it would not be. Because it does not wipe. Those ruu are unique in that they don't. The s-off ones and every other carriers ruu do wipe.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Im going to attempt to reflash the latest verizon radios in Hboot and see if it clears the whatever band settings i changed that killed my radio? Perhaps this is the same as what a full RUU would be but radio only.
Edit: that didnt work. Still "no service"
bacon612 said:
Im going to attempt to reflash the latest verizon radios in Hboot and see if it clears the whatever band settings i changed that killed my radio? Perhaps this is the same as what a full RUU would be but radio only.
Edit: that didnt work. Still "no service"
Click to expand...
Click to collapse
Factory reset on stock recovery now?
Sent from my HTC6535LVW using Tapatalk
dottat said:
Factory reset on stock recovery now?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Did a full RUU. That didnt work. Factory reset worked!!!!! Thanks so much!
bacon612 said:
Did a full RUU. That didnt work. Factory reset worked!!!!! Thanks so much!
Click to expand...
Click to collapse
Yeah. That's always been the old standby as it sets the nv golden config back.
Sent from my HTC6535LVW using Tapatalk
So while that did reset my radio. My SIM card reader is also broken. My LTE comes in and out. Its my fault.
I have been sent a warranty replacement from VZW but its running the 5.0.1 firmware. I have come to learn that there is no way to RUU downgrade to a 4.4.4 firmware so I can run sunshine to S-Off.
Does this mean I am SOL installing TWRP and roms since im stuck S-ON? ive actually never been S-On on an HTC device before.
bacon612 said:
So while that did reset my radio. My SIM card reader is also broken. My LTE comes in and out. Its my fault.
I have been sent a warranty replacement from VZW but its running the 5.0.1 firmware. I have come to learn that there is no way to RUU downgrade to a 4.4.4 firmware so I can run sunshine to S-Off.
Does this mean I am SOL installing TWRP and roms since im stuck S-ON? ive actually never been S-On on an HTC device before.
Click to expand...
Click to collapse
You can use a Java Card to S-OFF your M8 - check out the Verizon M9 Java Card thread.
(@dottat has one, he is my recommendation - but all are very trustworthy and if someone is closer it may be easier on you to go with them)
Been having this issue myself. Tried RUU, flashing all radios from 4.4.2 on up, factory reset, etc. I'm only getting 3G-- not LTE whatsoever. Any ideas?
Edit: Got a new SIM-- no cigar. Unless there are some network settings that I don't know about, the 4G antenna might just be broken or something
dottat said:
Factory reset on stock recovery now?
Click to expand...
Click to collapse
Thank you! This saved me from having to get a new M8 from Verizon (after the new SIM didn't work) and losing S-OFF.
meskibob said:
Thank you! This saved me from having to get a new M8 from Verizon (after the new SIM didn't work) and losing S-OFF.
Click to expand...
Click to collapse
It's not possible to lose s-off? Did you turn it on yourself?
Sent from my Nexus 6 using Tapatalk
dottat said:
It's not possible to lose s-off? Did you turn it on yourself?
Click to expand...
Click to collapse
I meant that I can keep my current M8 (still S-OFF) and have working LTE, instead of having to swap it with the new M8 that Verizon is sending to me (which I can now return).
meskibob said:
I meant that I can keep my current M8 (still S-OFF) and have working LTE, instead of having to swap it with the new M8 that Verizon is sending to me (which I can now return).
Click to expand...
Click to collapse
Thank you for the clarification. Gotta keep the folks from spinning rumors you can lose s-off
Sent from my Nexus 6 using Tapatalk
dottat said:
Thank you for the clarification. Gotta keep the folks from spinning rumors you can lose s-off
Click to expand...
Click to collapse
Sorry for the confusion, and thanks again!
No dice. On any of these fixes. I've gone through all the RUUs that dottat has posted, full back to stock (with root /s-off). I'm at a complete loss. Does anyone have any other suggestions to try and get this fixed?
After I flashed on of the RUUs I have 4G for about 10 mins, then it bumps back down to 3G. I've checked this in three different cities (Home, Work, Friends) so its not the network in my area. I was thinking of stopping at Verizon, maybe get a new SIM, but I'm not sure if that would work.