I have a functioning but not up to date setup:
Apollo Nexus v2.0.1 which is unfortunately in the stock slot of Safestrap v3.75, no other ROM slots and previous FireOS backup leaves screen blank (boots and ADB accessible).
(The backstory to this: some update had gone wrong at the end of last year I this status is all I could manage to get to a functioning state.)
Now I would like to move to unlocked bootloader, TWRP and CM12.1
I tried to unlock the bootloader using the method with cuberHDX posted in other threads but in fastboot after
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
I am getting
FAILED (remote: Unlock code is NOT correct)
I don't know what seems to be the problem. After the messy "fixes" from the end of last year I cannot quite remember which was the last version of the FireOS (and hence the bootloader that came along with it) that was installed.
--> Can anyone tell me how to find out the version of the bootloader?
Any other suggestions how to get out of my non-upgradeable situation? Any help greatly appreciated.
scaftogy said:
I have a functioning but not up to date setup:
Apollo Nexus v2.0.1 which is unfortunately in the stock slot of Safestrap v3.75, no other ROM slots and previous FireOS backup leaves screen blank (boots and ADB accessible).
(The backstory to this: some update had gone wrong at the end of last year I this status is all I could manage to get to a functioning state.)
Now I would like to move to unlocked bootloader, TWRP and CM12.1
I tried to unlock the bootloader using the method with cuberHDX posted in other threads but in fastboot after
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
I am getting
FAILED (remote: Unlock code is NOT correct)
I don't know what seems to be the problem. After the messy "fixes" from the end of last year I cannot quite remember which was the last version of the FireOS (and hence the bootloader that came along with it) that was installed.
--> Can anyone tell me how to find out the version of the bootloader?
Any other suggestions how to get out of my non-upgradeable situation? Any help greatly appreciated.
Click to expand...
Click to collapse
Unfortunately, there is no reliable method to determine bootloader version. If you are confident in the steps you are taking to unlock the bootloader the your system may have upgraded past 3.2.3.2 which is the last version that contains the vulnerability that the unlock exploit leverages. You could try one of the Safestrap Flashable HDX Stock Images (suggest v3.2.6 for greatest compatibility) in the stock slot but this could result in a brick if everything doesn't line up properly. Not sure it is worth the risk given your device may have other lingering issues from the previous update attempt gone bad. Nexus v2 is still highly functional; you can safely update that to v2.05 and add a few Xposed modules to acheive a near KitKat experience.
OK, I was afraid that there wasn't any way to determine the bootloader version. Thanks for the clear answer.
Given that the state of my kindle HDX is somewhat complicated I agree that trying something like flashing a stock rom seems rather risky. I just needed someone else to confirm that.
I am fairly confident about the steps I took with cuber and the bootloader unlocking procedure (on linux VM which I use regularly). I am also 98% sure I never let FireOS update. Doing a bit more digging, I found that I have kept all files that I used for flashing last year. There are the following (relevant) files in that folder:
update-kindle-14.3.1.0_user_310079820.bin
update-kindle-14.3.2.4_user_324002120.bin
prerooted14.3.1.0.zip
Safestrap-Apollo-3.75-os3.2.4-B02.apk
apollo-nexus-rom-v2.0.1.zip
That leads me to believe that the bootloader should be version .3.2.4
Now I am a bit confused whether the version .3.2.4 should be unlockable. @Davey126, you wrote that the last one was .3.2.3.2. However the original thread by @dpeddi states in first post:
dpeddi said:
- Bootloader shipped with firmwareversion 1[34].3.1.0 <= x <= 1[34].3.2.4 (as we use the rsa bug)
Click to expand...
Click to collapse
Could anyone please confirm which one is actually the last version of the bootloader that can be unlocked?
scaftogy said:
OK, I was afraid that there wasn't any way to determine the bootloader version. Thanks for the clear answer.
Given that the state of my kindle HDX is somewhat complicated I agree that trying something like flashing a stock rom seems rather risky. I just needed someone else to confirm that.
I am fairly confident about the steps I took with cuber and the bootloader unlocking procedure (on linux VM which I use regularly). I am also 98% sure I never let FireOS update. Doing a bit more digging, I found that I have kept all files that I used for flashing last year. There are the following (relevant) files in that folder:
update-kindle-14.3.1.0_user_310079820.bin
update-kindle-14.3.2.4_user_324002120.bin
prerooted14.3.1.0.zip
Safestrap-Apollo-3.75-os3.2.4-B02.apk
apollo-nexus-rom-v2.0.1.zip
That leads me to believe that the bootloader should be version .3.2.4
Now I am a bit confused whether the version .3.2.4 should be unlockable. @Davey126, you wrote that the last one was .3.2.3.2. However the original thread by @dpeddi states in first post:
Could anyone please confirm which one is actually the last version of the bootloader that can be unlocked?
Click to expand...
Click to collapse
You need a version below 3.2.4, i.e. 3.2.3.2 or lower.
But the good news is, if you are on 3.2.4 you can use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Cl4ncy said:
You need a version below 3.2.4, i.e. 3.2.3.2 or lower.
But the good news is, if you are on 3.2.4 you can use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Click to expand...
Click to collapse
I am on @ggow's CM12.1 now! :victory:
Rolled back with this to .3.0.9, upgraded to stock .3.1.0, rooted, unlocked bootloader, flashed TWRP, and finally flashed CM12.1. Thanks so much for the hint to roll back!
To come full circle to the original question: Determining the version of the bootloader is not possible from adb or fastboot. If you don't know which version of the bootloader you have, it can help to try to find out which roms / updates you flashed before. In my case I had a folder on my PC that showed I must have had .3.2.4.
Related
Hi
help me how to install .bin file
Standin.Weed said:
Hi
help me how to install .bin file
Click to expand...
Click to collapse
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Davey126 said:
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Click to expand...
Click to collapse
I have the kindle fire hdx 7 13.3.2.4 and I also have file:
mod-update-kindle-thor-13.3.2.8_user_713328020.bin
I do not know how to manually install this file
these words are translated by google because I have bad english
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Cl4ncy said:
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Click to expand...
Click to collapse
teach me how to install 13.3.1.0 install TWRP, update the bootloader to 3.2.3.2
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelihood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Cl4ncy said:
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelyhood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade Images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Click to expand...
Click to collapse
I do not know to do this step:
cuberHDX from here: http://forum.xda-developers.com/showpost.php?p=58864282&postcount=46
then open another DOS box, change dir to your Python Directory with the .py script (enter cd\python27 or whatever the path of your Python directory is), then
python.exe cuberHDX.py 0xmmssssssss
with mm being the last two digits of your ID, and the ssssssss being your serial, the script should create the .unlock file then.
So assuming the numbers you mentioned are correct the python command would be
python.exe cuberHDX.py 0x45f0bf7e1d
Copy/move the .unlock file to your ADB directory then, open another DOS box for the adb reboot-bootloader command, and yet another DOS box for the fastboot commands (change dir cd\adb both times before you enter the adb & fastboot commands):
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot
this is not have to be?
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Cl4ncy said:
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Click to expand...
Click to collapse
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Standin.Weed said:
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Click to expand...
Click to collapse
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Cl4ncy said:
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Click to expand...
Click to collapse
tks you so much.
I did all :laugh:
Standin.Weed said:
tks you so much.
I did all :laugh:
Click to expand...
Click to collapse
You're welcome - enjoy your "free" HDX.
I saw someone mention bootloader unlock was only possible on .3.2.8 and earlier, but to my knowledge it was only .3.2.4 and earlier because it accepted the forged signatures. Is it possible from 13.3.2.5?
Good news is you can downgrade to unlock, bad news is, it's a bit tricky.
Check this thread, scroll down to the procedure for 3.2.5/3.2.6 users!
Make sure you understand all points of the procedure, if in doubt ask first, i.e. before you brick your HDX.
After you downgraded to 3.1.0 be sure to re-root (if required, HDX Toolkit here, also good to disable OTA updates), then you can unlock (try the one click solution first - might require the PDANet drivers), install TWRP 3.0.0-1, and use the ROM of your choice, create a backup of your current system before you flash anything though. It is recommended to update the bootloader to 3.2.3.2.
"Unfortunately, AT&T Ready2Go has stopped." Is stuck looping on my phone.
About a year ago I rooted my phone, following these directions. (I can't yet post a link, but the first option on google when searching "how to root m8" is the site, htconeroot.com, that I used.)
This morning I noticed that my phone was not vibrating anymore no matter if I restarted the phone or what settings were applied. So I checked online to see if there was a fix, and a factory reset was recommended.
So when I got back from work today, I thought I had successfully uninstalled the root using SuperSU. Then I performed a factory reset. My phone then went into TWRP recovery which was alarming. So I rebooted the system from TWRP , then the message in the title kept popping up over and over again, so I am in a bit of a pickle. I can message and call at the moment but that is about it.
I'm thinking the problem is similar to this one someone had on a note 3, except I was trying to factory reset rather than update. http://forum.xda-developers.com/showthread.php?t=2663120
Has this happened to anyone else, and do you have any suggested fixes for resetting this phone???
Thanks in advance.
I've seen a number of cases on the M8 forums of various processes stopping with message "XXX has stopped" after a factory reset. Not sure what is causing this. But there are a variety of ways to recover.
Since you have TWRP, you can try to restore a TWRP backup of your own (if you made one) or install a stockish ROM. Those methods may be helpful if you want to retain or retrieve any personal data.
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
redpoint73 said:
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
Click to expand...
Click to collapse
Honestly I'd be fine returning to full stock, at least for the time being, to see if the vibration problem would fix itself. But do I need to be S-OFF for RUU?
eaflook said:
But do I need to be S-OFF for RUU?
Click to expand...
Click to collapse
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
redpoint73 said:
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
Click to expand...
Click to collapse
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
eaflook said:
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Click to expand...
Click to collapse
No, you're looking in the right place. Its somewhat common for OS number to be blank, its a known bug in older TWRP versions that it deletes the OS number.
What does it say for hboot number and radio number?
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
eaflook said:
U
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
Click to expand...
Click to collapse
You can do that. All that "guide" describes is one way to get a ROM on an SD and flash it, which is one of the options I already suggested in Post #2 above.
But what ROM will work, somewhat depends on the info I requested above.
redpoint73 said:
What does it say for hboot number and radio number?
Click to expand...
Click to collapse
hboot number-3.19.0.0000
radio [email protected]
redpoint73 said:
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
Click to expand...
Click to collapse
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
eaflook said:
hboot number-3.19.0.0000
radio [email protected]
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
Click to expand...
Click to collapse
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
redpoint73 said:
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
eaflook said:
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
Click to expand...
Click to collapse
Good practice is to post what you did (or going to do) for the benefit of others that may have the same question; or so we can verify you are on the right track.
In case others may have the same question (or you get stuck again), all TWRP versions, and instructions (recommend install with fastboot method) are here: https://twrp.me/devices/htconem8gsm.html
There is a master list of stock recovery versions for the HTC One. How do I determine which version I should be using?
None of those. That is hardly a "master" list. It's over 3 years old, never updated past the original Kitkat (M8 release) recoveries, and woefully obsolete. You'll want your recovery number to match your OS number (main version on bootloader screen or getvar all). Also, none of those are valid for AT&T version M8 (which is what I assume you have, since this section is specifically for the AT&T M8). It would need to have "502" in the version number x.xx.502.x which specifically denotes AT&T.
Why exactly do you want stock recovery? Most folks want this, in order to get OTA updates. But you will also need a stock, never rooted ROM (unrooting doesn't work), and also must be connected to the AT&T network. It's probably easier to relock the bootloader, and update by RUU. Note that RUU will wipe all data from the phone. See RUU section in my Index thread: https://forum.xda-developers.com/showthread.php?t=2751432
If you really want stock recovery, you should be able to extract it from the firmware.zip. Find the right firmware version number from the firmware collection, and extract recovery.img from the "Stock, Full Wipe" firmware zip:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
That is definitely helpful. Thank you. I didn't realize that I could pull the bootloader out of the firmware.zip. The phone was AT&T and later unlocked and made in to a rooted Cyanogenmod phone. I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
mortifyxda said:
I didn't realize that I could pull the bootloader out of the firmware.zip.
Click to expand...
Click to collapse
Recovery and bootloader are two completely different things! You can pull recovery.img from firmware.zip, and flash with fastboot. I would not do this with bootloader, which would require s-off (to flash manually) and it would still be risky. Better to flash the whole firmware.zip or RUU, if you want to update bootloader. But I don't think that is what you meant.
mortifyxda said:
I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
Click to expand...
Click to collapse
Your description is confusing, and I think you're mixing the terms up again. 6.12.1540.4 is the version number for the US Developer's Edition, which is Sense, and not the same as Google Play Edition (GPE) which is not Sense.
To OTA, the version number of the current stock ROM needs to match your firmware number (in bootloader and getar all), and you also need matching stock recovery.
To be clear, what is the current ROM (and version number) as shown in Settings? And also do fastboot getvar all, and post the result (delete IMEI and serial number). Need those pieces of info, before I can properly advise what stock recovery to use.
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!