So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...any senior members willing to point me in the right direction? I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
HTCFAN0923 said:
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...
Click to expand...
Click to collapse
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
HTCFAN0923 said:
I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Click to expand...
Click to collapse
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
HTCFAN0923 said:
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
Click to expand...
Click to collapse
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
redpoint73 said:
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
Click to expand...
Click to collapse
Thanks for the help and sorry for the confusion.
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
thanks again!
HTCFAN0923 said:
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
Click to expand...
Click to collapse
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
HTCFAN0923 said:
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
Click to expand...
Click to collapse
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
redpoint73 said:
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
Click to expand...
Click to collapse
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
HTCFAN0923 said:
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
Click to expand...
Click to collapse
I gave previous advice to stop using the toolkit, so I don't know why you insist on ignoring that advice.
Older versions of TWRP don't work on newer hboots; and the opposite is true where older hboots don't work with newer TWRP builds. This is the most frequent reason for TWRP not working properly.The toolkit worked fine at the time it was updated. But it hasn't been updated in a very long time, and therefore won't work on many M8 versions now. The issue is more your lack of understanding, and lack of following advice given to you.
Flashing TWRP is just a matter of downloading the proper version, and flashing with a single fastboot command (2 commands, if you want to be thorough and wipe cache before flashing TWRP). You don't need a toolkit for that, and again I advise stopping its use altogether.
Its not clear whether you chose to update before TWRP and root (current device status) and once I know the main version (OS number on bootloader screen) and present hboot number I can probably advice what version TWRP you need to flash.
And you're absolutely right about that. It was my fault for not listening. I was being lazy about it honestly.
I did end up using the lollipop pre rooted RUU and that worked after two atttempts. I think the issue was that the toolkit flashed the recovery without root. Add that to the fact that the toolkit caused the SD card issue to pop up made it a nightmare. Thankfully, I was able to fix it and now I'm running the AT&T lollipop ROM rooted.
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
HTCFAN0923 said:
I think the issue was that the toolkit flashed the recovery without root.
Click to expand...
Click to collapse
I don't follow. Root isn't needed to install custom recovery; nor does flashing custom recovery automatically root the phone (this has to be done as an additional step, usually by flashing SuperSU in TWRP).
I think the main issue was that the toolkit flashed an old TWRP version that was not compatible with the software/firmware that was on your phone.
HTCFAN0923 said:
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
Click to expand...
Click to collapse
I appreciate the thought; but your thanks is all I expect in return. I've benefited plenty from XDA from folks that don't ask for any monetary compensation; so I just like to give back to the community by helping how I can.
Related
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
some_douchebag said:
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
Click to expand...
Click to collapse
Once you unlock the boot loader no update can relock it. HTC offers a lot more freedom than samsung, but at the price of no warranty. So if you unlock it and shatter your screen, don't be upset like other people when htc will not warranty it. As long as you have a custom recovery, your phone cannot even physically take an ota update so nothing to worry about either way.
The Magnuson–Moss Warranty Act is in place for us consumers for this reason. The company has to prove that any modification you did, is the cause of the trouble. So if you unlock your bootloader, root, etc, then crack your screen, as the poster above mentioned, the company can not void your warranty since what you did has nothing to do with cracking your screen.
This was huge for me when I modified my car and I found this here on XDA after doing more searching
http://www.xda-developers.com/xda-tv-2/your-warranty-is-not-void-xda-tv/
Oh and yeah,,if you are outside the US, it wont work lol
some_douchebag said:
if HTC allows downgrading the bootloader
Click to expand...
Click to collapse
That depends on what you mean by "allow". You cannot downgrade the bootloader by any "official" means. You will fail version check when you try to install, as you can "normally" only flash a equal or great version number hboot.
But if you are s-off, version check is bypassed, and any hboot version can be flashed.
Similar to a previous response, my advice would be to unlock the bootloader (required if you want to flash custom ROMs anyway) and S-off the phone soon after you get it. Neither of those can be changed by any OTA.
Also, accepting OTA is not recommended on a modded phone, anyway. Whatever came in the update will usually get posted in a stock rooted form in the Development forum, and/or incorporated into custom ROMs, often within days of the OTA rolling out. And OTA will not install on a modded phone (stock recovery needs to be present). OTAs also may plug existing s-off or other exploit; preventing you from doing them if you haven't already (but as mentioned, can't make the phone s-on again). Moral of the story, I strongly recommend against OTA on any modded phone.
Some of these terms/concepts are HTC specific, so may be a bit confusing for you. I would suggest reading up on these forums, if you aren't familiar with s-off, HTC's bootloader unlock process, etc.
Hello. Thanks in advance for your time and advice.
I've got a brand new HTC One M8, AT&T, firmware says 4.4.2 with no available updates.
I want to create an initial backup. I'm a computer technician, and just dabbling in Android, and it's important for me to make a "clone" of my phone before I proceed to wreck things. (This is a replacement phone, the last one had a hardware issue... I swear... I managed to install ViperOne onto it, for a week before the screen faded to white and died.)
I assume I'll need root access to make a proper backup. I also assume I should use Nandroid. I've not used the app before, but I'm sure I can figure it out. As far as root goes, I previously used Hasoon2000's HTC One 2014 (M8) All-In-One Toolkit, which worked well, as far as I could tell. (It's a visual basic program with scripts to download drivers, register at htcdev, get token id, submit it, unlock bootloader, flash recovery, and lots of nice ADB commands. Is this a good option to use? I hear many people use S-Off, but I don't really see a need... ?
So, I assume I'll need a new token ID from HTC, as the previous one I got corresponds to the old, malfunctioning phone.
After it's unlocked, I'd use the toolkit to grant perm root. That would be a great place to be for now. I plan to wait until the 4.4.4 update is pushed, then worry about installing a new rom.
Am I on the right track?
For the AT&T version (and most the major US carrier versions) we are lucky enough to have RUUs. So really, no need to backup the stock configuration. If you like, grab the RUUs and save them to your computer so you have them ready if and when it is needed.
Nandroid isn't a specific app, its just a generic term for a backup made with recovery. The custom recovery is your choice: TWRP, Clockworkmod, Philz.
Just a personal opinion, I would actually strongly recommend against using the toolkit for a couple reasons: most importantly using the toolkit robs you of an important learning opportunity. Doing the steps "manually" is a key way to learning your way around fastboot/adb. Doing the steps manually isn't that hard, and shortcutting the process with the toolkit really doesn't gain you much. Another key issue, is the toolkit introduces an additional point of failure. In fact, I've seen folks have trouble doing some of the steps with the toolkit; where doing the steps "manually" worked without a hitch. And the toolkit hasn't been updated for a long time, and will install an obsolete version of TWRP recovery, which in itself can cause issues.
If you used the toolkit before, you can certainly use it again. This is likely the path of "least" resistance, the the "easy" way to do things. But I wouldn't necessarily call it the "best" way to do it. If you don't already know your way around adb, I would do the steps manually. Since you have a background in computers, you will probably even find the manual process more enjoyable.
Yes, you would need to unlock the bootloader again via HTCDev.com, as the unlock bin code in based on the phone's unique IMEI.
The process would be as simple as unlocking the bootloader using HTCDev.com (very easy, the website is self-explanatory). Use fastboot to install custom recovery. Then to gain root, just flash SU or SuperSU in recovery. If you need a step-by-step guide, there is an excellent one here: http://forum.xda-developers.com/showthread.php?t=2799796
But also be aware that once the 4.4.4 OTA rolls out, you will need to return to stock recovery, and also restore any system files modifed by root, in order to install the OTA.
Thanks, redpoint73
Exactly the answer I was looking for. The guide looks great. Looks like there's a lot of useful information about reverting to stock, too. I guess I'll have a go at it now, as opposed to waiting for the update. Like you say, it's good to know things. Thanks much.
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
AT&T HTC ONE M8
jball said:
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
Click to expand...
Click to collapse
Absolutely. In fact S-off is not even required to run an RUU intended for your version (AT&T). If s-on, the added step of relocking the bootloader is all that is needed to run the RUU.
HTC seems to have gotten better about releasing the RUUs promptly. In fact, the previous (ill fated) 4.4.3 update saw the RUU and OTA roll out on the same day. Although this hasn't always been the case. On past devices, the RUUs were not released for weeks (sometimes longer) after the OTA started to roll out. And many folks don't want to wait that long.
Also, relocking the bootloader is not required to OTA, only to RUU.
hello guys
please help me here, i got a mobile from a friend and it is AT&T One M8, it has lot of unnecessary apps and its not possible for me to share net via hotspot.
So i went and done root but can not able to get S-off and i really can't pay $25.
please can any one tell me how get at least official Asia or Indian OS.
Mobile condition
Rooted
CID HTC__001
factory unlocked.
Please help me to get another OS. Thanks in Advance.:angel::crying:
Not at this time. Your only option is to pay. Firewater was the last option to s-off and that project was abandoned
If you're looking to delete at&t apps to free up space, ROM toolbox and Titanium Backup in the play store will work just fine to delete those apps
You have a few options:
1) Unlock bootloader, flash custom recovery. Then flash just about any ROM that is not AT&T based, that supports your firmware (hboot, radio, etc.). Basically, any ROM is better than AT&T stock, in my opinion.
2) Unlock bootloader, flash custom recovery and root. Than manually delete what apps you want (as suggested above) and apply WiFi tethering hack.
3) Pay for sunshine s-off, and convert to another CID, such as Developer Edition. Not only will this get you on a clean (no AT&T branding or limitations) stock base (and Lollipop at that), but allow OTA updates as well.
Firewater was discontinued (as mentioned above). Firewater was an online service, so it no longer works now that the dev has stopped supporting it. Sunshine is the only s-off method at this time, so you can stop trying to s-off by some "other" method unless you have some advanced development skills and intend to find you own exploit.
redpoint73 said:
3) Pay for sunshine s-off, and convert to another CID, such as Developer Edition. Not only will this get you on a clean (no AT&T branding or limitations) stock base (and Lollipop at that), but allow OTA updates as well.
Firewater was discontinued (as mentioned above). Firewater was an online service, so it no longer works now that the dev has stopped supporting it. Sunshine is the only s-off method at this time, so you can stop trying to s-off by some "other" method unless you have some advanced development skills and intend to find you own exploit.
Click to expand...
Click to collapse
I would suggest to do this. Converting an AT&T branded phone to Developer Edition is fantastic because of all the benefits that were already mentioned. Believe me, you won't be disappointed. I had to pay $25 to get S-off but I don't regret my decision, since immediately I got Lollipop and had the option to tethering and without bloatware.
neha12347 said:
please help me here, i got a mobile from a friend and it is AT&T One M8
Mobile condition
Rooted
CID HTC__001
factory unlocked.
Click to expand...
Click to collapse
Hold on, that isn't the AT&T CID. So either the CID has been modified (s-off required to do so), its not the AT&T version, or CID listed incorrectly above.
AT&T version of the M8 has the AT&T "globe" logo on the back of the phone.
I have an at&t branded phone. I recently switched to T-Mobile and would like to get T-Mobile ROM installed on it.
I started with a phone which was NOT rooted, had stock AT&T rom.
I have done the following so far:
*
Unlocked my boot loader - worked flawlessly
Installed TWRP - worked flawlessy
Attempted to install Super SU - I think it worked
Attempted to install a T-Mobile ROM - Getting a "Error flashing zip" error
I download official T-Mobile ROM installer from HTC website. I let the installer run until I saw "Rom.zip" in the temp folder.
A website on google told me that i can use this file to flash my phone. I did have some doubts about this file as I am able to unzip only half the file's contents using winrar. But anyways, I went ahead and used this ROM file.
I rebooted my phone in Recovery mode (TWRP). I clicked on Install and selected rom.zip from my SD Card. When I attempt to install rom.zip, I received following messages:
Installing '/external_sd/tmobile_rom.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip 'external_sd/tmobile_rom.zip'
Updating partition details...
....done
I tried a few different ROM's I found on the internet with the same error message.
So now I am stuck with no OS on the phone. I can only go to bootloader or TWRP.
If someone can suggest a more appropriate ROM file, I can give that a try.
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
I have s-on. Yes, I want the full T-Mobile firmware...mixing up my terms as I am new to this.
Since I don't have an OS right now, I will first try to restore to AT&T firmware by using the stock RUU on htc website. If that's successful, I will proceed with rest of the steps.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
So I was able to get back to AT&T firmware using below steps:
booted my phone to boot fastboot mode
I re-locked my bootloader using following command: fastboot oem lock
I download the AT&T HTC One M8 Stock RUU
Ran the installation until my firmware was flashed again
I am just so happy to have a phone that works now. I will continue soon with the rest of your instructions to get T-Mobile firmware.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
After spending few hours, I have successfully installed T-Mobile firmware on my AT&T M8.
I pretty much followed your instructions. For anyone else looking to this this, here are the complete instructions.
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
And now I am enjoying a beer
Thanks redpoint73 for your helpful reply.
deepak528 said:
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
Click to expand...
Click to collapse
I think this is slightly out of sequence. You need to s-off before changing CID and MID. CID and MID cannot be modified with s-on.
wouldnt a simple rom without the firmware provide wifi calling?
PunishedSnake said:
wouldnt a simple rom without the firmware provide wifi calling?
Click to expand...
Click to collapse
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
redpoint73 said:
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
Click to expand...
Click to collapse
Agreed
Hello all, haven't been on this forum for awhile, Ha!
Anyways, my m8 wasn't receiving calls a couple years ago so I of course thought it was my ROM. I flashed several, and most calls didn't come through. I could make calls, just almost all didn't go through (very few did)
So, took it into the att store and the guy said the antenna was probably corroded. I don't think that's the case, as data worked fine and texting did as well. Just recently, it hit me to try and update the modem. I've searched and searched but couldn't find out how. Here's some info:
HBOOT: 3.19.0.0000
RADIO: [email protected]
Unlocked - S-ON
TWRP v3.2.1-0
Any help on updating modem would be great. I'm looking to get rid of my s7 edge (Locked bootloader can kiss it)
*Id like to do this without relocking my bootloader
"Corroded antenna" sounds like hogwash, and the store employee just making up crap, so he didn't have do anything (or didn't know what he was talking about).
Since you mention the AT&T store, I will assume you are using the AT&T network. Is so, I think (pretty sure) you have the problem described in the following thread, and the solution should work for you: https://forum.xda-developers.com/htc-one-m8/help/receive-calls-make-detailed-thread-t3146670
You may need an AT&T Tier 2 tech support to turn off HD Voice. Tier 1 tech support may not know what you are talking about - or may claim incorrectly that it can be done (this has been reported by others).
Craz Basics said:
Any help on updating modem would be great.
*Id like to do this without relocking my bootloader
Click to expand...
Click to collapse
It does appear from your radio number, that it is on the older side (Lollipop). Therefore, it may not be a bad idea to update to Marshmallow firmware (the latest you will be able to get, since HTC doesn't support the device any longer).
You aren't going to see any major differences from updating the firmware (as mentioned, it's probably not the cause of your voice call problem). In fact, I was running MM custom ROMs on the M8 for a long time, with LP firmware; with no negative results observed. But it's typically recommended to have the most updated firmware for maximum compatibility with the current ROMs.
Unfortunately, you can't do this with an unlocked bootloader (since you are s-on). You unfortunately cannot flash firmware with an unlocked bootloader, on this device. For that matter (what you are asking originally) you can't flash the radio separately with s-on, at all. But you can flash the signed firmware (which includes radio) with a relocked bootloader.
You can flash the AT&T Marshmallow firmware using the following guide: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
No need to do the part "Install RUU" if you want to continue using a custom ROM (with HD Voice disabled on your ATT account). So the process would be something like:
1) Backup any data you want to keep, by method of your choice
2) Relock bootloader with command: fastboot oem lock
3) Flash firmware using guide linked above
4) Unlock bootloader again, using the old unlock bin code, or get a new one from HTCDev.com
5) Install TWRP again (flashing firmware replaces TWRP with stock recovery)
6) Flash the custom ROM of your choice again
redpoint73 said:
"Corroded antenna" sounds like hogwash, and the store employee just making up crap, so he didn't have do anything (or didn't know what he was talking about).
Since you mention the AT&T store, I will assume you are using the AT&T network. Is so, I think (pretty sure) you have the problem described in the following thread, and the solution should work for you: https://forum.xda-developers.com/htc-one-m8/help/receive-calls-make-detailed-thread-t3146670
You may need an AT&T Tier 2 tech support to turn off HD Voice. Tier 1 tech support may not know what you are talking about - or may claim incorrectly that it can be done (this has been reported by others).
It does appear from your radio number, that it is on the older side (Lollipop). Therefore, it may not be a bad idea to update to Marshmallow firmware (the latest you will be able to get, since HTC doesn't support the device any longer).
You aren't going to see any major differences from updating the firmware (as mentioned, it's probably not the cause of your voice call problem). In fact, I was running MM custom ROMs on the M8 for a long time, with LP firmware; with no negative results observed. But it's typically recommended to have the most updated firmware for maximum compatibility with the current ROMs.
Unfortunately, you can't do this with an unlocked bootloader (since you are s-on). You unfortunately cannot flash firmware with an unlocked bootloader, on this device. For that matter (what you are asking originally) you can't flash the radio separately with s-on, at all. But you can flash the signed firmware (which includes radio with a relocked bootloader).
You can flash the AT&T Marshmallow firmware using the following guide: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
No need to do the part "Install RUU" if you want to continue using a custom ROM (with HD Voice disabled on your ATT account). So the process would be something like:
1) Backup any data you want to keep, by method of your choice
2) Relock bootloader with command: fastboot oem lock
3) Flash firmware using guide linked above
4) Unlock bootloader again, using the old unlock bin code, or get a new one from HTCDev.com
5) Install TWRP again (flashing firmware replaces TWRP with stock recovery)
6) Flash the custom ROM of your choice again
Click to expand...
Click to collapse
Thanks a ton! I really appreciate this!