Related
I'm a happy One M8 user since June '14, never had an issue (except for the camera lens scratch, which I was able to reapir thankfully to the XDA community) but there's one thing that always bother me,
I have no 4G support.
I live in Brazil and here we use the 2600MHz (IMT-E) band for LTE, but my model only have LTE 700MHz (Lower SMH Blocks B/C) and LTE 1700MHz (AWS A-F) bands avaliable.
I know that is a way to change the avalible bands using a NV writer and changing some values there, and I did try to change, but my M8 always return to the old values after I disconnect from QPST. *Of course I looked for the proper way to calculate the numbers to put there before try anything*
My device is Unlocked/S-OFF/and w/Super CID.
Now the questions:
1. If I flash a EU RUU, is there a chance to this RUU change the NV partition and modify the values from LTE support? (Since the EU M8 have support for the 2600MHz band)
2. If the answer for the first question is afirmative, do I have to relock my phone to be able to flash the RUU or do something else?
3. If the answer for the first question is not afirmative, I need to know if all boards have LTE support. Mine is 0P6B13000. Maybe not all of them include hardware support for all LTE bands (?)
Could someone with the same board tell me if you have this band avaliable on your phone, please
PS: I do know that I have a US variant, but I don't know what carrier is the owner of the HTC__017 cid (the original from my phone). I know that this board is used by US T-Mobile too, and they also don't include support to 2600MHz LTE on their phones.
Bump
dxzdxz1 said:
I'm a happy One M8 user since June '14, never had an issue (except for the camera lens scratch, which I was able to reapir thankfully to the XDA community) but there's one thing that always bother me,
I have no 4G support.
I live in Brazil and here we use the 2600MHz (IMT-E) band for LTE, but my model only have LTE 700MHz (Lower SMH Blocks B/C) and LTE 1700MHz (AWS A-F) bands avaliable.
I know that is a way to change the avalible bands using a NV writer and changing some values there, and I did try to change, but my M8 always return to the old values after I disconnect from QPST. *Of course I looked for the proper way to calculate the numbers to put there before try anything*
My device is Unlocked/S-OFF/and w/Super CID.
Now the questions:
1. If I flash a EU RUU, is there a chance to this RUU change the NV partition and modify the values from LTE support? (Since the EU M8 have support for the 2600MHz band)
2. If the answer for the first question is afirmative, do I have to relock my phone to be able to flash the RUU or do something else?
3. If the answer for the first question is not afirmative, I need to know if all boards have LTE support. Mine is 0P6B13000. Maybe not all of them include hardware support for all LTE bands (?)
Could someone with the same board tell me if you have this band avaliable on your phone, please
PS: I do know that I have a US variant, but I don't know what carrier is the owner of the HTC__017 cid (the original from my phone). I know that this board is used by US T-Mobile too, and they also don't include support to 2600MHz LTE on their phones.
Click to expand...
Click to collapse
I'm about 99.99% sure it will work just fine. You won't need the whole RUU though. Just flash a 4.16.401.10 firmware package.
My advice below in red font:
dxzdxz1 said:
1. If I flash a EU RUU, is there a chance to this RUU change the NV partition and modify the values from LTE support? (Since the EU M8 have support for the 2600MHz band) Advise to flash the Euro firmware (in agreement with previous response) or RUU.
2. If the answer for the first question is afirmative, do I have to relock my phone to be able to flash the RUU or do something else? Since you are s-off, NO. You can run the RUU with unlocked bootloader. However, you will need to change the MID.
3. If the answer for the first question is not afirmative, I need to know if all boards have LTE support. Mine is 0P6B13000. Maybe not all of them include hardware support for all LTE bands (?) All boards have LTE support; and specific band support is set in radio firmware. All "GSM" versions are the same in hardware to my knowledge, the exceptions being "CDMA" variants (Sprint & Verizon) and dual SIM version.
Could someone with the same board tell me if you have this band avaliable on your phone, please
PS: I do know that I have a US variant, but I don't know what carrier is the owner of the HTC__017 cid (the original from my phone). I know that this board is used by US T-Mobile too, and they also don't include support to 2600MHz LTE on their phones. Not familiar with that CID. But my guess is that its a regional US carrier that uses T-Mobile's network. Google search for "HTC_0017" yields some results for Cincinnati Bell. Although that would make it associated with AT&T, rather than T-Mobile. So probably just confusing the issue more here.
But its somewhat irrelevant. You've already changed the CID, and can change the MID to whatever you like.
Click to expand...
Click to collapse
redpoint73 said:
My advice below in red font:
Click to expand...
Click to collapse
xunholyx said:
I'm about 99.99% sure it will work just fine. You won't need the whole RUU though. Just flash a 4.16.401.10 firmware package.
Click to expand...
Click to collapse
I tried to flash only a EU radio.img = No success.
Then I tried to flash a EU firmware = Still no success.
And then I tried to install a ruu, but again, no success.
Is there anything else that I could try?
dxzdxz1 said:
I tried to flash only a EU radio.img = No success.
Then I tried to flash a EU firmware = Still no success.
And then I tried to install a ruu, but again, no success.
Is there anything else that I could try?
Click to expand...
Click to collapse
Get into ADB/fastboot, and do fastboot getvar all. Post the readout here (delete your IMEI and serial# ~ that is private info you should never post on a public forum) and someone will be able to direct you on how to update properly.
I'm not positive (but I mostly am), but I don't think WWE/EU firmware is compatible with you model.
dxzdxz1 said:
I tried to flash only a EU radio.img = No success.
Then I tried to flash a EU firmware = Still no success.
And then I tried to install a ruu, but again, no success.
Is there anything else that I could try?
Click to expand...
Click to collapse
You need to tell us where the processes failed, and any error messages. And exactly what files you tried to flash. There are quite a few RUUs, firmwares, and radios possible, even if isolated to Euro WWE.
Did you change the MID on the phone, as I mentioned previously?
RUU will absolutely fail with your present MID. Firmware probably, and radio maybe will also fail due to MID. It depends on what exactly you tried to flash, and if the MID check was removed.
redpoint73 said:
You need to tell us where the processes failed, and any error messages. And exactly what files you tried to flash. There are quite a few RUUs, firmwares, and radios possible, even if isolated to Euro WWE.
Did you change the MID on the phone, as I mentioned previously?
RUU will absolutely fail with your present MID. Firmware probably, and radio maybe will also fail due to MID. It depends on what exactly you tried to flash, and if the MID check was removed.
Click to expand...
Click to collapse
xunholyx said:
Get into ADB/fastboot, and do fastboot getvar all. Post the readout here (delete your IMEI and serial# ~ that is private info you should never post on a public forum) and someone will be able to direct you on how to update properly.
I'm not positive (but I mostly am), but I don't think WWE/EU firmware is compatible with you model.
Click to expand...
Click to collapse
Here is the thing, guys
Nothing has failed.
The RUU has been installed, but LTE still doesn't work
This is my old getvar info that I saved for those "just in case" situations:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.422.19
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: HTC__017
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
And here is my actual getvar info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
This may be a stupid question, but are you sure your SIM supports LTE? That is a carrier option that can be enabled or disabled. It may not be an issue, but it is certainly worth checking if you aren't sure.
jshamlet said:
This may be a stupid question, but are you sure your SIM supports LTE? That is a carrier option that can be enabled or disabled. It may not be an issue, but it is certainly worth checking if you aren't sure.
Click to expand...
Click to collapse
Not a stupid question at all. Assuming the proper LTE band support has been enabled, and proper APN settings, there isn't any reason for LTE to not work; unless there is something wrong carrier/network side, such as account provisioning as you mention.
M7 didn't retain nv changes either.
jshamlet said:
This may be a stupid question, but are you sure your SIM supports LTE? That is a carrier option that can be enabled or disabled. It may not be an issue, but it is certainly worth checking if you aren't sure.
Click to expand...
Click to collapse
redpoint73 said:
Not a stupid question at all. Assuming the proper LTE band support has been enabled, and proper APN settings, there isn't any reason for LTE to not work; unless there is something wrong carrier/network side, such as account provisioning as you mention.
Click to expand...
Click to collapse
This is the same SIM a used to have on my old Xperia Z, I just cut off to fit on my M8.
My SIM is not the problem, because on my old phone I was able to connect on LTE.
SaHiLzZ said:
M7 didn't retain nv changes either.
Click to expand...
Click to collapse
Maybe is locked by the kernel (?)
I really don't know why I can't modify the NV values
On my sister Nexus 5 I changed the NV settings and it work just fine.
dxzdxz1 said:
This is the same SIM a used to have on my old Xperia Z, I just cut off to fit on my M8.
My SIM is not the problem, because on my old phone I was able to connect on LTE.
Maybe is locked by the kernel (?)
I really don't know why I can't modify the NV values
On my sister Nexus 5 I changed the NV settings and it work just fine.
Click to expand...
Click to collapse
The SIM is definitely the problem.
You can't just cut them to make them fit. The contact points are all different.
xunholyx said:
The SIM is definitely the problem.
You can't just cut them to make them fit. The contact points are all different.
Click to expand...
Click to collapse
I use one of these tools made for cut SIM chips, and I can still make calls and use 3G connection. If the cut is (was) the problem, why everything else is working?
Well, just in case, I will buy another SIM and transfer my phone number tomorrow
Thank you for everything so far.
dxzdxz1 said:
I use one of these tools made for cut SIM chips, and I can still make calls and use 3G connection. If the cut is (was) the problem, why everything else is working?
Well, just in case, I will buy another SIM and transfer my phone number tomorrow
Thank you for everything so far.
Click to expand...
Click to collapse
I've googled this now, and apparently you can cut them down.
But you'll still need to buy a SIM that supports LTE. Older ones don't.
Thanks for the knowledge about cutting them. I never knew. I always thought that the resize changed contacts.
Not a kernel issue, afaik. I have tried with S-OFF, Tmobile RUU, custom roms. Best of luck though..
xunholyx said:
I've googled this now, and apparently you can cut them down.
But you'll still need to buy a SIM that supports LTE. Older ones don't.
Thanks for the knowledge about cutting them. I never knew. I always thought that the resize changed contacts.
Click to expand...
Click to collapse
Today a bought a new SIM, and LTE still doesn't work.
SaHiLzZ said:
Not a kernel issue, afaik. I have tried with S-OFF, Tmobile RUU, custom roms. Best of luck though..
Click to expand...
Click to collapse
I searched for threads about NV editing here on XDA and it seems that some manufacturers DO lock changes on NV partition.
Quoted from this thread
One surprising finding was that people with older phones were having better results. Why? It seems that Qualcomm quietly added some anti-tamper code into recent Android versions to keep us from doing this. It's almost like they read our forum and know what we're trying to mod. But they wouldn't spy on us like that, would they?
Click to expand...
Click to collapse
So it seems to be that now only people with custom ROMs/kernels can do modifications to NV.
I also read on a Nexus 5 thread that a combination of AOSP ROM and Faux Hybrid Kernel is working for newer devices and/or new updates.
I have only tested CM12 nightlies and I couldn't enter on DiagMode. The default shell command isn't working there.
Tonight I will try another combinations and see if works.
I tested all aosp roms from Orig Development subforum and I wasn't able to mount my M8 in Diag Mode
There's anything else left to try?
dxzdxz1 said:
I tested all aosp roms from Orig Development subforum and I wasn't able to mount my M8 in Diag Mode
There's anything else left to try?
Click to expand...
Click to collapse
I'm in the same boat too.. trying to add band 3 to my M8 with stock rom android 5.0.1 , this one is from Canada with bands 4, 7 and 17, same issue, NV values won't stick in M8, tried with ElementalX-m8-4.05-Sense kernel too. already used QPST, QXDM tool combination and DFS CDMA tool to try editing the 6828 and 6829 values. no luck still, values won't stick. read a lot and found lots of people with M8 having the same issue, no clue though.
You can try use the method in this guide, it's for M9 but works for M8 as well except NV values won't stick for me. also you can use this DFS CDMA tool to confirm the LTE bands you are already having. read button in LTE tab displays the bands you are having. by this you can confirm that there is no issue with the sim but you do or do not have the required LTE bands.
http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401
i found two commands to get diag mood on,
1. echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
2. setprop sys.usb.diag.config diagon
you can try one of them to get diag mood on so you can use a tool. im about to give up on this now. let us know if you make any progress . :fingers-crossed:
Hello guys,
Months ago i bought an HTC One M8 on Aliexpress, it worked fine for a few days but suddently refused to detect my sd-card, so i managed to install a new rom (Android_Revolution_HD-One_M8_50.2_76b56b). Everything worked fine until a few days, when my phone was seemingly unrooted. So i decided to update to a newer version.
Then here we are, i downloaded dozens of roms but was unable to boot any rom i installed, im by far not an expert but i managed to use abd and fastboot to install twrp 3. I finally managed to install Cyanogen (cm-13.0-20151228-NIGHTLY-m8) but it didnt detecter either my SIM, IMEI and crashed all the time.
Now i'm running a nandroid backup with a Marshmallow Sense 7 rom i downloaded here: androidsage.com/2016/03/08/update-verizon-htc-one-m8-to-marshmallow-using-custom-files-ruu-ota using their firmware (m8MfirmwareTWRP3_0_0_1)
But it does not detect my sim card neither my IMEI
The phone is S-OFF with TWRP-3, supercid, modified MID (from 0P6B20000 to 0P6B10000) and Official HBOOT
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA45XXXXXXXX
(bootloader) imei: 3587180XXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000499686942
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
At my point i'm willing to install any rom as long as it works..
Thanks.
phoeniiiix said:
The phone is S-OFF with TWRP-3, supercid, modified MID (from 0P6B20000 to 0P6B10000) and Official HBOOT[/B]
(bootloader) version-main: 1.54.401.5
(bootloader) product: m8_wlv
Click to expand...
Click to collapse
MID 0P6B20000 and product ID m8_wlv are for the Verizon version (supports CDMA, in addition to GSM, but we call it the "CDMA version" here).
You flashed a Euro firmware 1.54.401.5 and bricked the radio. This is a known result of trying to flash non-CDMA firmware to the Verizon or Sprint M8 variants, which should never have been done.
The damage may be permanent. The most you can do is change back to the Verizon MID, and flash Verizon RUU, and pray it fixes the radio issue. http://forum.xda-developers.com/verizon-htc-one-m8/general/vzw-m8-master-ruu-firmware-collection-t2946473
If not, the radio is permanently bricked.
Thanks for the awnser
I can still flash the radio, does that mean its not bricked ? (im not familiar with android internal filesystem)
In case the phone is bricked, is changing the main motherboard a good idea (50€ on ebay), i also eard of jtag unbrick services
Back
So as you recommended, i installed a verizon rom, and this time it actually show my IMEI in settings :good:, and i launched adb shell to change my MID
Now it seems to "detect" my sim card, it ask for it but says "no service" and does not ask for the pin, does that mean the phone is carrier locked (some boxes are greyed out when i try to add APNs) ? In case it is, how can i safely unlock it, i'm from France and my carrier is Orange
phoeniiiix said:
Back
So as you recommended, i installed a verizon rom, and this time it actually show my IMEI in settings :good:, and i launched adb shell to change my MID
Now it seems to "detect" my sim card, it ask for it but says "no service" and does not ask for the pin, does that mean the phone is carrier locked (some boxes are greyed out when i try to add APNs) ? In case it is, how can i safely unlock it, i'm from France and my carrier is Orange
Click to expand...
Click to collapse
You'll have to buy an Unlock code.
Also, the IMEI on your phone has been changed.
Verizon and Sprint IMEIs start with 99x, yours is starting with 35x to try and make it look like an international model.
Notice the meid still starts with 99, as the seller probably didn't bother or forgot to change it.
Sent from my HTC One_M8
phoeniiiix said:
So as you recommended, i installed a verizon rom, and this time it actually show my IMEI in settings :good:, and i launched adb shell to change my MID
Click to expand...
Click to collapse
Try not to use the term "ROM" interchangeably with "RUU", as doing so may add unnecessary confusion to the discussion. They are different things. The RUU re-images all partitions, something like 41 partitions. Of which, the ROM is just one.
phoeniiiix said:
Now it seems to "detect" my sim card, it ask for it but says "no service" and does not ask for the pin, does that mean the phone is carrier locked (some boxes are greyed out when i try to add APNs) ? In case it is, how can i safely unlock it, i'm from France and my carrier is Orange
Click to expand...
Click to collapse
The Verizon version is unlocked from the factory. So I'm suspicious whether a SIM unlock will actually work, or if its a function of the radio brick (improper firmware flash). I suppose trying to unlock is low risk, as long as you use a service that does not charge money if it doesn't work (as many of them have that policy).
I'm also not sure if a SIM unlock will work, if the IMEI has been hacked (as the previous user pointed out).
---------- Post added at 09:39 AM ---------- Previous post was at 09:35 AM ----------
phoeniiiix said:
In case the phone is bricked, is changing the main motherboard a good idea (50€ on ebay), i also eard of jtag unbrick services
Click to expand...
Click to collapse
Either may be an option. But changing the motherboard yourself is not that easy, and I don't personally recommend it unless you are very experienced and comfortable doing such things. I've seen more than a few reports of such repairs go badly on this device. Its fairly common to break something else while trying to "fix" the mobo.
A paid mobo or JTAG may be a better option.
Thanks a lot, using the RUU update you provided (0P6BIMG) i was able to fix it, you saved my phone i'm so glad =)
hi there,
I just get an htc one m8 wich is still in kitkat, but rooted and S-off !
can't do an OTA update, I think to install a custom rom (maximusHD) but before I begin, I want to be sure of what i'm doing, must do a nandroid backup and I don't know how
the other issue is that I dont know how to get the original CID, and on the lower back, I have "0P6B100" model but in the Hboot menu I have "m8 whl pvt ship", how to choose the good custom ROM or even to return to the stock one
help plz
epervier1983 said:
before I begin, I want to be sure of what i'm doing, must do a nandroid backup and I don't know how
Click to expand...
Click to collapse
Making a nandroid is normally quite easy, if you have TWRP (custom recovery) installed. Just boot into TWRP, and select the "Backup" option.
However, you have a lot of other considerations you need to look at, before you flash anything. See more below.
Also, if you aren't familiar with the basic processes (like making a nandroid) plus the device peculiarities of the M8; I'd highly recommend you do some more research and reading of the basic guides and threads here. I'd say minimum 1 hour, before trying anything, like flashing a ROM.
epervier1983 said:
the other issue is that I dont know how to get the original CID, and on the lower back, I have "0P6B100" model but in the Hboot menu I have "m8 whl pvt ship
Click to expand...
Click to collapse
First of all, you can not go by what is on the back cover. We've see a lot of refurbished, modified M8 phones, which have had their back cover replaced to remove carrier brand logos (particularly US carrier branded models). So in those cases (and it appears to be the case for you) the model number on the back cover is nor representative of the original model, or the internal components (which is the most important thing to go by).
You need to do fastboot getvar all, and post the results (delete IMEI and serial number before posting) before we can proceed, and definitely before you try any ROMs or other mods. We need more info about the device, before we can proceed safely.
Reason being, the product ID m8 whl indicates you probably have the US Sprint version. This model is fairly peculiar (and annoying) as it supports CDMA (in addition to GSM, LTE, etc.), and that makes it different from most other M8 versions. Trying to flash another versions stock RUU or firmware is in fact dangerous and can possibly permanently brick the phone.
Further, many custom ROMs which don't specifically support the Sprint version, will not boot. This is due to the fact that the Sprint version uses a different kernel from most other M8 models.
In addition, since your firmware appears to still be on KitKat, you will need to update it before flashing any custom ROMs (even ones that support Sprint version). Otherwise, the ROMs will have severe problems, like failure to boot, extreme long boot time, and broken WiFi.
So really, we need the getvar info before we can advise further, and definitely before you try to mess with anything.
Also, on the bootloader screen, does it say LOCKED, UNLOCKED or RELOCKED near the top. And is TWRP installed; and if so what version?
Hi, thanks for your response! Sorry about the delay,
But I finally returned the phone to sender, the big issue that I found it was a Sprint model and in my country I can't use 4G lte even I change Rom or something else like id number, and according to members it's not a good idea to try flashing it, the hardware is different, I can't unlock the LTE bands of my career (northern africa or Europe) even the flash work correctly,
But if u have some solutions it will be great, because the sender still searching help
The entire characteristics :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.0119
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44BS******
(bootloader) imei: 3520900********
(bootloader) imei2: Not Support
(bootloader) meid: 99000499******
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
Thnx in advance
epervier1983 said:
But if u have some solutions it will be great, because the sender still searching help
(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
The seller is looking for solutions for what exactly?
The product name (m8_whl) as well as model number (0P6B70000) confirm that this is originally the Sprint version M8. The back cover has been swapped to remove the Sprint logo. And the phone was mad s-off and SuperCID (1111111) most likely to unlock the SIM.
Sprint RUUs will return the phone to stock ROM, plus update the firmware (radio, hboot, etc.), which the getvar data (version main = 3.30.651.2) identifies the firmware is extremely outdated, and still on KitKat.
https://forum.xda-developers.com/showthread.php?t=2729173
However, stock RUU may not be that desirable. Sprint stock ROM has a lot of bloat, Sprint carrier branding, and some things (WiFi hotspot/tethering) are probably disabled. Therefore, a custom ROM may be desirable. Custom ROMs which support the Sprint version M8 are recommended, since the Sprint version uses a different kernel from most other M8 versions: https://forum.xda-developers.com/sprint-htc-one-m8/development
However, the user will still probably want to update the firmware first. Otherwise, using current custom ROMs with outdated firmware, will cause a lot of serious problems: extreme slow boot or not boot, broken WiFi, audio issues, etc.
Again, the user is warned to NOT try RUUs or firmware.zip for other M8 versions (other than Sprint) as they are not compatible, and can cause permanent damage.
Also, you should delete the serial number from getvar data, as well as MEID. These are private info, which should not be posted online.
Hi ! Thnx a lot to take Time to respond, the seller wants to update android version at least, official or custom Rom doesn't matter, and sure keep WiFi and all features ok
For the 4G it's not possible because the smartphone doesn't support the 3b (1800) bands, so ..
I'll give him u r links and we'll see,
Ty
epervier1983 said:
the seller wants to update android version at least, official or custom Rom doesn't matter, and sure keep WiFi and all features ok
Click to expand...
Click to collapse
It might not matter to the seller, but it will make a big difference in your approach:
Stock/official Sprint RUU:
1) Flash Marshmallow Sprint firmware
2) Flash Sprint Marshmallow RUU
Custom ROM:
1) Flash Marshmallow Sprint firmware
2) Unlock bootloader (if not already unlocked)
3) Flash TWRP 3.1
4) Flash custom ROM (which support Sprint version M8)
Either of the above will result in WiFi working properly. But I'm not sure what you mean by "all features ok" as that statement is too vague. For instance, the official Sprint software most likely block WiFi hotspot/tethering. As blocking that feature is common on US variants.
epervier1983 said:
For the 4G it's not possible because the smartphone doesn't support the 3b (1800) bands, so ..
Click to expand...
Click to collapse
You might give the following threads a look/try (to enable the 1800 LTE band) - of course at your own risk. But unlocking bands on the Sprint version has mixed results (easier on the other "CDMA" version M8 - Verizon):
https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
https://forum.xda-developers.com/htc-one-m8/general/unlock-bands-qualcomm-device-phone-t2880239
Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!
A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.
Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.
Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).
Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.
Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.
Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.
My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
Hello Everyone , i've been lurking in the forum since i've had my htc one x, and you guys are geniuses.
But yet im here with another issue , i've searched over the threads and couldn't find an answer.
My Htc one m8 recently had a catastrophic hardware failure, and it was so much of a good phone that i bought a new one , but , when i started configuring it , and downloading the OTA it failed with the message: variant System version , so i looked it up , and realized this phone is maybe a reburbished one , i've unlocked the bootloader to try to apply RUU.exe , but it fails , this one m8 is for At&t , but here is the getvar all info :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.010s
i've noted that CID is 11111111, it just came out of the box with this configuration , thats why i think i've been tricked , the phone seems to work fine anyway.
So here's my question , can i turn this phone back to stock , to allow the official updates, and have the phone on 100% stock ? i've tried but failed in every way , and im scared of destroy this second one.
Thank you guys in advance
Regards
Santiago.
ReD! said:
Hello Everyone , i've been lurking in the forum since i've had my htc one x, and you guys are geniuses.
But yet im here with another issue , i've searched over the threads and couldn't find an answer.
My Htc one m8 recently had a catastrophic hardware failure, and it was so much of a good phone that i bought a new one , but , when i started configuring it , and downloading the OTA it failed with the message: variant System version , so i looked it up , and realized this phone is maybe a reburbished one , i've unlocked the bootloader to try to apply RUU.exe , but it fails , this one m8 is for At&t , but here is the getvar all info :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.010s
i've noted that CID is 11111111, it just came out of the box with this configuration , thats why i think i've been tricked , the phone seems to work fine anyway.
So here's my question , can i turn this phone back to stock , to allow the official updates, and have the phone on 100% stock ? i've tried but failed in every way , and im scared of destroy this second one.
Thank you guys in advance
Regards
Santiago.
Click to expand...
Click to collapse
Hi again , after many hours of trying i've fixed it , finally i was able to make the RUU work by changing my USB port to one of the rear , and unlocking the bootloader , everything looks fine now.
Regards
Santiago
ReD! said:
i've noted that CID is 11111111, it just came out of the box with this configuration , thats why i think i've been tricked , the phone seems to work fine anyway.
Click to expand...
Click to collapse
The device has definitely been modified, made s-off, SuperCID, and Euro firmware 3.28.401.6 installed.
I find it somewhat unlikely that any legitimately brand new (from factory) exist anymore, as this device is over 4 years old. If you paid a premium for a "new" device, then I agree you've been tricked. But if you paid a reasonable price for a working device (used/refurb) then I would say you can be content that you got what you paid for (although a somewhat dishonest description on the part of the seller).
---------- Post added at 09:29 AM ---------- Previous post was at 09:25 AM ----------
ReD! said:
Hi again , after many hours of trying i've fixed it , finally i was able to make the RUU work by changing my USB port to one of the rear , and unlocking the bootloader , everything looks fine now.
Click to expand...
Click to collapse
I believe you meant you "relocked" the bootloader. As with s-on, that is the only way an RUU will work, as I believe you have now figured out.
Further, you may or may not find the stock AT&T software/firmware is not to your liking. Depending on your location and carrier, the bands are meant for US, and you may not be missing some bands (flashing RUU changes the band support). Further, you will find the stock AT&T ROM annoyingly blocks some functions, like WiFi hotspot. Let us know if you want to switch to Euro Marshmallow RUU, since you have the ability to do so. But if everything is working to your liking, you can obviously just leave it alone.
redpoint73 said:
The device has definitely been modified, made s-off, SuperCID, and Euro firmware 3.28.401.6 installed.
I find it somewhat unlikely that any legitimately brand new (from factory) exist anymore, as this device is over 4 years old. If you paid a premium for a "new" device, then I agree you've been tricked. But if you paid a reasonable price for a working device (used/refurb) then I would say you can be content that you got what you paid for (although a somewhat dishonest description on the part of the seller).
---------- Post added at 09:29 AM ---------- Previous post was at 09:25 AM ----------
I believe you meant you "relocked" the bootloader. As with s-on, that is the only way an RUU will work, as I believe you have now figured out.
Further, you may or may not find the stock AT&T software/firmware is not to your liking. Depending on your location and carrier, the bands are meant for US, and you may not be missing some bands (flashing RUU changes the band support). Further, you will find the stock AT&T ROM annoyingly blocks some functions, like WiFi hotspot. Let us know if you want to switch to Euro Marshmallow RUU, since you have the ability to do so. But if everything is working to your liking, you can obviously just leave it alone.
Click to expand...
Click to collapse
Hi redpoint73,
i've read a lot of your posts , and if i'm here is thanks to your knowledge, so first . Thank you.
Yes, i meant i "relocked the bootloader" i'm sorry, and yes , i've notice by now , that certain functions do not work, as you said one is Wifi Hotspot as it uses an At&t software and not the original one it seems. What do you mean by Euro Marshmallow? , i'm from Argentina and my carrier is Movistar . Does applying that RUU, overrides the radio firmware? My previous One m8 that died was an international from VodaPhone bought on spain , and with that one i was never able to use it on 4g only on H+. I'm currently trying to configure the APN to test out if mobile internet works.
Thanks for your response
Regards
Santiago.
ReD! said:
i'm from Argentina and my carrier is Movistar . Does applying that RUU, overrides the radio firmware?
Click to expand...
Click to collapse
Yes, RUU contains radio baseband. So flashing a different RUU will install a new radio baseband, and therefore change the specific band support.
I can't tell what bands your carrier uses for LTE. I often refer to the following webpage to try to determine the bands used in other countries, and all it says for Movistar in Argentina is "4G LTE" which is not very helpful!
In any case, getting LTE to work is tricky on this device (when not intended for your specific region/carrier). I've seen a number of folks fail to get LTE, even after installing RUU or radio baseband that supports the correct LTE bands used by their carrier.
redpoint73 said:
Yes, RUU contains radio baseband. So flashing a different RUU will install a new radio baseband, and therefore change the specific band support.
I can't tell what bands your carrier uses for LTE. I often refer to the following webpage to try to determine the bands used in other countries, and all it says for Movistar in Argentina is "4G LTE" which is not very helpful!
In any case, getting LTE to work is tricky on this device (when not intended for your specific region/carrier). I've seen a number of folks fail to get LTE, even after installing RUU or radio baseband that supports the correct LTE bands used by their carrier.
Click to expand...
Click to collapse
Hi again , i've configured LTE and it seems to work fine , i don't know if Euro Marshmallow RUU will work the same, the bands supported in here are :
2G (EDGE, GSM/GPRS): bands 850 / 1900 MHz
3G (HSPA+, UMTS/WCDMA): bands 850 / 1900 MHz
4G (LTE): bands 4 (AWS o 1700) / 7 (2600) / 28 (APT o 700*)
i've double checked on here and it says its ok.
But the wifi hotspot is a shame, i use it a lot , and here we don't have any restrictions about it.
if you are kind , i'd like to know how to apply the Euro Marshmallow RUU to test it, is it the same as the one i've applied ? just download and run ? o do i have to modify CID/MID to any specific values? or apply a custom rom which is good but retains sense as i like it a lot.
Thanks
Regards
ReD! said:
Hi again , i've configured LTE and it seems to work fine , i don't know if Euro Marshmallow RUU will work the same, the bands supported in here are :
2G (EDGE, GSM/GPRS): bands 850 / 1900 MHz
3G (HSPA+, UMTS/WCDMA): bands 850 / 1900 MHz
4G (LTE): bands 4 (AWS o 1700) / 7 (2600) / 28 (APT o 700*)
Click to expand...
Click to collapse
Warning about the stock AT&T ROM, it will say "4G" in the status bar even if you are only on HSPA. Only if you seen an icon "4G LTE" does it mean you actually have LTE connectivity. You can blame AT&T marketing baloney for that.
Check to see if you really have LTE, before we explore other RUUs.
Comparing the band support as listed on the following specs website, the AT&T RUU does in fact better support the bands you indicate. It supports LTE bands 4 and 7 (but not 28). Where the Euro version only supports LTE band 7 (of the ones your carrier uses) and not 4 or 28.
https://www.gsmarena.com/htc_one_(m8)-6074.php#emea
ReD! said:
But the wifi hotspot is a shame, i use it a lot , and here we don't have any restrictions about it.
Click to expand...
Click to collapse
If you like, you can unlock the bootloader, and run a custom ROM which will remove the WiFi hotspot restriction. But again, let's see if you really have LTE or not, before we proceed too far down any path.
redpoint73 said:
Warning about the stock AT&T ROM, it will say "4G" in the status bar even if you are only on HSPA. Only if you seen an icon "4G LTE" does it mean you actually have LTE connectivity. You can blame AT&T marketing baloney for that.
Check to see if you really have LTE, before we explore other RUUs.
Comparing the band support as listed on the following specs website, the AT&T RUU does in fact better support the bands you indicate. It supports LTE bands 4 and 7 (but not 28). Where the Euro version only supports LTE band 7 (of the ones your carrier uses) and not 4 or 28.
https://www.gsmarena.com/htc_one_(m8)-6074.php#emea
If you like, you can unlock the bootloader, and run a custom ROM which will remove the WiFi hotspot restriction. But again, let's see if you really have LTE or not, before we proceed too far down any path.
Click to expand...
Click to collapse
Hi again Redpoint73,
i've adquired a new sim card at my carrier , which is 4g compatible , now its showing 4g LTE in the display instead of 4g only, so 4g is working. Which rom is available to flash that has sense 7 , like the original , and do i have to flash the recovery in order to flash the rom?
Regards
ReD! said:
i've adquired a new sim card at my carrier , which is 4g compatible , now its showing 4g LTE in the display instead of 4g only, so 4g is working. Which rom is available to flash that has sense 7 , like the original , and do i have to flash the recovery in order to flash the rom?
Click to expand...
Click to collapse
Okay, that's good that LTE is working. Since that is the case, I would tend towards not trying a different RUU. Which I would believe would most likely make your LTE connectivity worse, not better.
You can check out the Development section for ROMs which fit the description of what you are looking for. I don't typically recommend any certain ROMs over another. What ROM is best for you, you need to decide for yourself. There are too many variables based on user patters, preferences, and expectations.
Yes, you need custom recovery (TWRP) to install any custom ROM. And to install custom recovery, you need to unlock the bootloader.