Related
Hello all.. I just purchased a unlocked note 2 from at&t from good 'ol craigslist lol... I have it flashed now to stock 4.1.2 with root. I plan to use this phone on t-mobile, and read forums about how you have to enable aws on the phone to get 3g/4g for their network. I also want to use this phone in the future for international use, as well as at&t's 4g and lte network. By changing the aws file, will I be able to achieve this?
Also in order to use call over wifi, I have to flash a tmobile rom as told by members on the forums, but there's also an international rom http://forum.xda-developers.com/showthread.php?t=2016575 here, will this rom already have the aws band enabled or do I still need to enable it? I know it's kind of a lot to ask for a rom that covers everything, but what is the closest to it? Would using a tmobile stock rom hurt me in anyways?
You're posting in the wrong section, but I'll answer you anyways.
1. The AWS mod is independent from everything else, except modem flashes. Meaning no matter what you flash, unless you're flashing a modem, the mod will stick (remain functional).
2. All the mod does is enable the AWS band that is natively supported by the phone, but AT&T purposely disabled. It doesn't disable any functionality. The file itself is a modem memory (very very low level) backup from a T-Mobile model, with the IMEI removed so that yours does not get overwritten. It flips an internal switch to enable AWS support, just like the T-Mobile model. Aside from lack of wireless charging on the T-Mobile model, the AT&T and T-Mobile models are identical. This mod just turns on something that was artifically disabled. Your phone will work on both T-Mobile and AT&T (2G, 3G, 4G, LTE) perfectly.
3. Wifi calling is built into the ROM. It's only available on T-Mobile ROMs. You can flash an international ROM but you won't have Wifi calling. I can verify this as I'm using an international ROM.
The only things to watch out for:
1) ONLY FLASH AT&T MODEMs. And when you do (even if you're reflashing the same one that's on your phone), you have to reapply the mod. If you accidentally flash a different modem (say a T-Mobile modem), you'll lose your IMEI temporarily and your phone will reboot every few minutes until you flash back an AT&T modem. Don't freak out.
2) AT&T and T-Mobile ROMs are intercompatible across both models. But again, only use the modem for your device.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Product F(RED) said:
You're posting in the wrong section, but I'll answer you anyways.
1. The AWS mod is independent from everything else, except modem flashes. Meaning no matter what you flash, unless you're flashing a modem, the mod will stick (remain functional).
2. All the mod does is enable the AWS band that is natively supported by the phone, but AT&T purposely disabled. It doesn't disable any functionality. The file itself is a modem memory (very very low level) backup from a T-Mobile model, with the IMEI removed so that yours does not get overwritten. It flips an internal switch to enable AWS support, just like the T-Mobile model. Aside from lack of wireless charging on the T-Mobile model, the AT&T and T-Mobile models are identical. This mod just turns on something that was artifically disabled. Your phone will work on both T-Mobile and AT&T (2G, 3G, 4G, LTE) perfectly.
3. Wifi calling is built into the ROM. It's only available on T-Mobile ROMs. You can flash an international ROM but you won't have Wifi calling. I can verify this as I'm using an international ROM.
The only things to watch out for:
1) ONLY FLASH AT&T MODEMs. And when you do (even if you're reflashing the same one that's on your phone), you have to reapply the mod. If you accidentally flash a different modem (say a T-Mobile modem), you'll lose your IMEI temporarily and your phone will reboot every few minutes until you flash back an AT&T modem. Don't freak out.
2) AT&T and T-Mobile ROMs are intercompatible across both models. But again, only use the modem for your device.
Click to expand...
Click to collapse
Thank you for this clear response! What will flashing the modem do for me, as far as advantages than the stock? I am not planning to do massive overhaul on this device, I just want it to be compatible with every carrier including it's data! Also when performing this aws mod, do I need to manually change any apn settings, or will it automatically be picked up by the phone?
xterminater07 said:
Thank you for this clear response! What will flashing the modem do for me, as far as advantages than the stock? I am not planning to do massive overhaul on this device, I just want it to be compatible with every carrier including it's data! Also when performing this aws mod, do I need to manually change any apn settings, or will it automatically be picked up by the phone?
Click to expand...
Click to collapse
Nothing really. Sometimes a new modem will improve power consumption or data speeds. Sometimes it'll do the opposite and you'll want to flash back the old modem. And if you don't care, you rarely ever have to do anything. The modems are stock modems btw. They're extracted from official OTA updates so that you can use them on any ROM. As for APN settings, they may or may not be automatically set by the SIM. If I remember correctly my T-Mobile SIM automatically set it up. It's not hard to do though.
By the way, all AT&T LTE devices work with T-Mobile LTE out of the box. This mod just enables it for 3G ("4G").
Sent from my Galaxy Note 2
Product F(RED) said:
Nothing really. Sometimes a new modem will improve power consumption or data speeds. Sometimes it'll do the opposite and you'll want to flash back the old modem. And if you don't care, you rarely ever have to do anything. The modems are stock modems btw. They're extracted from official OTA updates so that you can use them on any ROM. As for APN settings, they may or may not be automatically set by the SIM. If I remember correctly my T-Mobile SIM automatically set it up. It's not hard to do though.
By the way, all AT&T LTE devices work with T-Mobile LTE out of the box. This mod just enables it for 3G ("4G").
Sent from my Galaxy Note 2
Click to expand...
Click to collapse
Ok i flashed the aws file but i only got edge speed! How do i manually change it to get lte or 4g
Edit 1.... Ok so it connected to 4G like 5-10 min later!! Also what is the main differences for an international labeled rom vs the tmobile rom for the att version? I mean since my phone is already unlocked, and have this aws mode enabled there's not a need for an international rom right?
So I have am using already a T-Mobile S4 (m919) on At&t's network... I have already rooted it, flashed Hyperdrive, entered the correct APN, and it works basically well...
Here is what I am wondering, my signal strength seems to be not the best and it makes me wonder, is there a modem, baseband I can flash on the T-mobile version of the S4 that could possibly help it work better on the At&t network... and do so with out making my S4 a paper weight?
abovenbeyond said:
So I have am using already a T-Mobile S4 (m919) on At&t's network... I have already rooted it, flashed Hyperdrive, entered the correct APN, and it works basically well...
Here is what I am wondering, my signal strength seems to be not the best and it makes me wonder, is there a modem, baseband I can flash on the T-mobile version of the S4 that could possibly help it work better on the At&t network... and do so with out making my S4 a paper weight?
Click to expand...
Click to collapse
Any M919 modem. MKL is the newest.
abovenbeyond said:
So I have am using already a T-Mobile S4 (m919) on At&t's network... I have already rooted it, flashed Hyperdrive, entered the correct APN, and it works basically well...
Here is what I am wondering, my signal strength seems to be not the best and it makes me wonder, is there a modem, baseband I can flash on the T-mobile version of the S4 that could possibly help it work better on the At&t network... and do so with out making my S4 a paper weight?
Click to expand...
Click to collapse
Glad someone asked that. I looked for a few hours last night and came up empty(been working an off shift so I might have missed it). I am on 4.2.2 MDL and signal is definitely much weaker than my Active on 4.3 . Has anyone compared modems to see which are better?
pahick said:
Glad someone asked that. I looked for a few hours last night and came up empty(been working an off shift so I might have missed it). I am on 4.2.2 MDL and signal is definitely much weaker than my Active on 4.3 . Has anyone compared modems to see which are better?
Click to expand...
Click to collapse
I can provide anecdotal evidence but nothing real...
MK2 is better.
Also, as for which modem to flash; T-Mobile's MK2 would be the one to flash. I've read you can flash other carrier's modems as long as they are the same version, i.e. AT&T MK2 or T-Mobile MK2... but that just doesn't make sense to me and I wouldn't recommend it. The modem you flash is independent of who your carrier is; you go by what brand of phone you have. If you have the M919 then you flash T-Mobile firmwares/modems/etc regardless of which carrier your bill comes from.
abovenbeyond said:
Here is what I am wondering, my signal strength seems to be not the best and it makes me wonder, is there a modem, baseband I can flash on the T-mobile version of the S4 that could possibly help it work better on the At&t network... and do so with out making my S4 a paper weight?
Click to expand...
Click to collapse
I've encountered the same thing with my M919. Switching between Android 4.3 and 4.4.2 modem.bin files made no difference.
I did notice that when I changed my network preference from 3G/2G to 2G-only, I gained about 10 dBa when the handset fell back to GSM-EDGE mode. It made a big difference. I verified that AT&T only uses band II (1900MHz) for GSM and UMTS in my county, so it wasn't because I switched to band V (850MHz) which seems to have better range. What I find annoying is that the handset isn't dropping down to 2G automatically when reception is poor. It'll stick with 3G even when the signal strength is as low as -107 dBa.
No LTE at the moment since my AT&T MNVO doesn't support it.
I'm thinking of buying an M919, carrier unlocked, to use on ATT, so that I can get a proper recovery and have full access to custom ROMs without the safestrap limitations.
Is it safe to say that:
1. If I buy a T-Mobile S4, and it comes carrier unlocked, it will work fine on the ATT network, including 4G / LTE? Lots of data points suggest this but I haven't heard it explicitly stated...
2. Though I could use the phone as identified as an M919, I really want Play Store to see it as an I337 (ATT version), so I can install some ATT specific apps. Is there any problem flashing a build.prop (available in the ATT threads) with the ATT identifiers & APN info, to enable this?
3. Are there any gotchas I should be aware of? Basically, I just want a phone with unlocked bootloader / kernel so I can play. Not too worried about Knox/warranty.
Any insights would be appreciated!
Marc
Frankenscript said:
I'm thinking of buying an M919, carrier unlocked, to use on ATT, so that I can get a proper recovery and have full access to custom ROMs without the safestrap limitations.
Is it safe to say that:
1. If I buy a T-Mobile S4, and it comes carrier unlocked, it will work fine on the ATT network, including 4G / LTE? Lots of data points suggest this but I haven't heard it explicitly stated...
2. Though I could use the phone as identified as an M919, I really want Play Store to see it as an I337 (ATT version), so I can install some ATT specific apps. Is there any problem flashing a build.prop (available in the ATT threads) with the ATT identifiers & APN info, to enable this?
3. Are there any gotchas I should be aware of? Basically, I just want a phone with unlocked bootloader / kernel so I can play. Not too worried about Knox/warranty.
Any insights would be appreciated!
Marc
Click to expand...
Click to collapse
Will the T-Mobile S4 work on the AT&T network; yes it will work if it's carrier unlocked. I purchased my M919 full price out of contract while I was still on AT&T service. Once I carrier-unlocked I was able to pick up AT&T's 4G/LTE and was even able to make use of the AT&T 3G Microcell device which transmits a 3G cell signal and runs over your WiFi. I now have Net10 Wireless with an AT&T SIM card and I still get 4G/LTE when it's around.
Your second question: I do believe that's all that would be required. I'm not 100% sure if just modifying the build.prop would allow you to use the AT&T-specific apps in the Play Store. I never used them to begin with so I never explored whether or not I could make them work on the T-Mobile firmware. Now, I know this involves more than just a build.prop edit, but a 100% sure way to get AT&T Apps working would be to flash a custom ROM based on AT&T firmware. Being that you have a T-Mobile device and are using it on another carrier's network, always remember; when it comes to Odin especially, flash things meant for the T-Mobile M919 ONLY. It doesn't matter that you use AT&T service, your device needs T-Mobile Modems/stock firmwares/etc.
As far as gotchas... not that I can think of. The M919 has an unlocked bootloader and even with KNOX is very easy to root and use custom ROMS on. If you're not concerned with KNOX then you really don't have to take into consideration any special rooting method, no safestrap junk, etc. Without root, just flash a recovery in Odin and flash away.
I know this thread is a bit old, but the situation is very relevant to me. I just won a S4 M919 on eBay which will be delivered tomorrow. T-mobile has agreed to send me an unlock code. My motivation is to install TWRP recovery which I can't do on the i337. I intend to activate it on Cricket (AT&T network). Is it still true that I should stick with firmware, ROMs, and modems designed for the M919? I don't care about AT&T or T-mobile apps so that's not an issue. Basically, I want the best data rates available. Any gotchas that I need to be aware of?
flroots said:
I know this thread is a bit old, but the situation is very relevant to me. I just won a S4 M919 on eBay which will be delivered tomorrow. T-mobile has agreed to send me an unlock code. My motivation is to install TWRP recovery which I can't do on the i337. I intend to activate it on Cricket (AT&T network). Is it still true that I should stick with firmware, ROMs, and modems designed for the M919? I don't care about AT&T or T-mobile apps so that's not an issue. Basically, I want the best data rates available. Any gotchas that I need to be aware of?
Click to expand...
Click to collapse
@flroots
Basically, you're best off bringing the phone to current M919 stock through ODIN. Is that NK2 or has there been a more recent version? I've lost track. But do the entire phone, and in fact as you will see from some threads it is often necessary to flash it twice in succession to get everything to stick. This will bring you to the latest modem. Remember, the modem is two parts: the modem.bin (also known as the gsm modem, which isn't specifically dependent on the bootloader version you have) and the LTE modem (non-hlos.bin, which is dependent on the firmware version, and bad things happen if you mismatch).
Since your phone is out of warranty, there's no downside to going to the latest, even if the phone arrives with 4.2.2 firmware (pre-knox). Tripping the knox bit is only a problem if you would be sending the phone in for warranty service.
I've got the M919 and am using it on ATT, with no problems. I've got the pre-knox firmware (MDL), and will be updating to the latest next time I flash.
Here is an old, but still relevant, thread about my experiences with M919 on ATT.
http://forum.xda-developers.com/galaxy-s4-tmobile/help/using-t-mobile-m919-att-network-t2880349
You will have to configure your APN to match your Cricket service. Sorry, can't help you with those settings but I'm sure they are on XDA somewhere!
Marc
Frankenscript said:
@flroots
Basically, you're best off bringing the phone to current M919 stock through ODIN. Is that NK2 or has there been a more recent version? I've lost track. But do the entire phone, and in fact as you will see from some threads it is often necessary to flash it twice in succession to get everything to stick. This will bring you to the latest modem. Remember, the modem is two parts: the modem.bin (also known as the gsm modem, which isn't specifically dependent on the bootloader version you have) and the LTE modem (non-hlos.bin, which is dependent on the firmware version, and bad things happen if you mismatch).
Since your phone is out of warranty, there's no downside to going to the latest, even if the phone arrives with 4.2.2 firmware (pre-knox). Tripping the knox bit is only a problem if you would be sending the phone in for warranty service.
I've got the M919 and am using it on ATT, with no problems. I've got the pre-knox firmware (MDL), and will be updating to the latest next time I flash.
Here is an old, but still relevant, thread about my experiences with M919 on ATT.
http://forum.xda-developers.com/galaxy-s4-tmobile/help/using-t-mobile-m919-att-network-t2880349
You will have to configure your APN to match your Cricket service. Sorry, can't help you with those settings but I'm sure they are on XDA somewhere!
Marc
Click to expand...
Click to collapse
Thanks a lot for that update. As I understand it, the current firmware is NB4 according to this site:
http://galaxys4root.com/galaxy-s4-stock-firmware/
Not sure what your reference to NK2 is? That doesn't seem to correspond to either 4.2.2 nor 4.4.2? I'm currently on Cricket with a S4 I337 and hope to move the SIM over as soon as my M919 arrives tomorrow.
I believe after NB4 there was NH7 then NK2. Check the firmware thread in the general section for details / links.
Sent from my SGH-M919 using Tapatalk
@flroots
How did this work out for you? I want to do the same thing you said you where going to do.
flroots said:
I know this thread is a bit old, but the situation is very relevant to me. I just won a S4 M919 on eBay which will be delivered tomorrow. T-mobile has agreed to send me an unlock code. My motivation is to install TWRP recovery which I can't do on the i337. I intend to activate it on Cricket (AT&T network). Is it still true that I should stick with firmware, ROMs, and modems designed for the M919? I don't care about AT&T or T-mobile apps so that's not an issue. Basically, I want the best data rates available. Any gotchas that I need to be aware of?
Click to expand...
Click to collapse
Robert417919 said:
@flroots
How did this work out for you? I want to do the same thing you said you where going to do.
Click to expand...
Click to collapse
Robert417919,
I use my SGH-M919 on an AT&T network also. I use the OK3 modem firmware and it seems to work great here. Although I am in Alaska, so top speeds of LTE are only about 6 Mbps where I live. Usually I can only get about 3 Mbps due to the lack of coverage around here.
You can either update to the latest OH3 firmware on your phone, or if you have an old model, with the MDL bootloader, you could also use this guide by lordodin912:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/foh3-modem-bin-mdl-bootloader-t3191094
Also, if you are looking for good roms, you can always check out SlimLP:
http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-slimlp-jfltetmo-t3377731
Or Resurrection Remix:
http://forum.xda-developers.com/gal...ent/rom-resurrection-lollipop-v5-4-5-t3115155
Hope that helps!
Thanks, this does help out, and another quick question. Are you able to use wifi calling?
AlaskaLinuxUser said:
Robert417919,
I use my SGH-M919 on an AT&T network also. I use the OK3 modem firmware and it seems to work great here. Although I am in Alaska, so top speeds of LTE are only about 6 Mbps where I live. Usually I can only get about 3 Mbps due to the lack of coverage around here.
You can either update to the latest OH3 firmware on your phone, or if you have an old model, with the MDL bootloader, you could also use this guide by lordodin912:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/foh3-modem-bin-mdl-bootloader-t3191094
Also, if you are looking for good roms, you can always check out SlimLP:
http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-slimlp-jfltetmo-t3377731
Or Resurrection Remix:
http://forum.xda-developers.com/gal...ent/rom-resurrection-lollipop-v5-4-5-t3115155
Hope that helps!
Click to expand...
Click to collapse
Robert417919 said:
Thanks, this does help out, and another quick question. Are you able to use wifi calling?
Click to expand...
Click to collapse
Glad to help, and no, unfortunately not.
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com
This is my first smart phone, I had a Asus TF700 tablet that i unlocked and did a lot of custom ROM work on. Well I am military moving back to the US soon and i was visiting to take my wife back. I bought a Verizon M8 that of course was unlocked but i was going to use t-mobile. While in the states i had the issues that is common with this setup and was losing 4g, couldnt text while on 4g, etc. At this point i flew back over to europe and thought i could use t-mobile's deal of unlimited text and data in other countries. But i dont receive a signal at all. Started looking into how to unlock and custom ROM to fix the issues. I watched all the videos and read the how-tos that i could find and did the firewater to S-off and unlock. I installed TWRP 2.7.1.0 since it was the latest on the TWRP website. I changed over to superCID. I have installed viperONE M8 ROM. I tried flashing the ATT radios that i could find in tread on the regular M8 boards but after i flashed it, it would boot up all the way, i still didnt get any bars for signal but after about 5 minutes it would just reboot. i reflashed my originial radio and it worked fine again. Well i just tried to flash the WWE radio and same thing happened. Is there something i am missing to flash radios and not have it bootloop? Also, anyone have any ideas on what i can do to get signal on my phone? I have data roaming enabled and anything else i can find about roaming enabled. Thanks for any help.
In a nutshell you purchased the wrong unit.
The Verizon unit is a CDMA based version of the HTC One M8. So the Sprint and verizon share similar radios.
Your trying to use that on a GSM network. Not compatible.
You would need an AT&T / T-Mobile or Google Play Edition version for what your trying to do.
Some people have bricked their phones flashing CDMA to GSM and visa verse so be careful. Theres a lot more detail there but that pretty much covers it.
I received a used s3 which had stock 4.3 , modem/bootloader mjb, and knox. I rooted, removed knox and installed slim 4.4.4 rom, lean 4.4.4 kernel and latest philz. All running ok
including cell calls to/from, mms, apps and wifi data. Same modem/bootloader (MJB), IMEI available However cellular data will not connect and or transmit/receive using att, phone or lte APN.
Any help/thoughts appreciated?
Have you updated the bootloader and modem to kk?
audit13 said:
Have you updated the bootloader and modem to kk?
Click to expand...
Click to collapse
My research suggested that the modem mjb and bootloader mjb did not have to be updated if cell calls and sms were working. Also I have an older S3 with modem mjb and bootloader mg2 and the same rom and kernel
that was working fine.
??
Can you manually add the APN? Have you tried other KK custom ROMs?
audit13 said:
Can you manually add the APN? Have you tried other KK custom ROMs?
Click to expand...
Click to collapse
I just added an APN, tested and deleted it. I was holding off changing roms because it seems to me that this might be an ATT cell data network registration problem in which the choice of ROM is
irrelevant.
When you added the APN, were you able to connect to ATT?
audit13 said:
When you added the APN, were you able to connect to ATT?
Click to expand...
Click to collapse
Not for data, cell calls and sms work.
Are any APNs present in the phone? With every custom ROM I have installed on a phone (i747m, Atrix HD, Nexus 4, Galaxy Nexus, LG Optimus G), the APN was always automatically added.
audit13 said:
Are any APNs present in the phone? With every custom ROM I have installed on a phone (i747m, Atrix HD, Nexus 4, Galaxy Nexus, LG Optimus G), the APN was always automatically added.
Click to expand...
Click to collapse
Yes, there were att based apns labeled phone, att, lte, broadband, attactivate and two for smarttalk. I have tried the phone, lte and att apns and they all fail.
This is strange that it can't connect the ATT data network. Is ATT's data network functioning properly in your area? Are you able to try your sim in another phone?
audit13 said:
This is strange that it can't connect the ATT data network. Is ATT's data network functioning properly in your area? Are you able to try your sim in another phone?
Click to expand...
Click to collapse
I just tested the ATT data network with another sim and phone. AOK. Unable to easily test with the same sim due to a std/micro sim card mismatch. Will be able to
do that after 6p cdt today.
Weird, I would suggest creating a nandroid backup of your current ROM and try another ROM.
Do you have a link to the ROM you installed?
audit13 said:
Weird, I would suggest creating a nandroid backup of your current ROM and try another ROM.
Do you have a link to the ROM you installed?
Click to expand...
Click to collapse
Here is a link to the main d2lte download page. I downloaded the 7.0 version as my searches showed some instability in later releases .
http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
kwmike said:
Here is a link to the main d2lte download page. I downloaded the 7.0 version as my searches showed some instability in later releases .
http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
Click to expand...
Click to collapse
Will have to hold for now on another rom install due to external issues.
I don't see any assert lines in the ROM's updater-script file. I also noticed that it has been updated since Aug 5.
audit13 said:
I don't see any assert lines in the ROM's updater-script file. I also noticed that it has been updated since Aug 5.
Click to expand...
Click to collapse
Not knowledgeable enough to understand assert impact. Also held off on later version due to thread discussion about instability.
The only thing left to do seems to be trying another ROM. If that doesn't solve the issue, it may be a defective sim card or possible hardware issue.
audit13 said:
The only thing left to do seems to be trying another ROM. If that doesn't solve the issue, it may be a defective sim card or possible hardware issue.
Click to expand...
Click to collapse
Have to go on hold for a while now.
Thanks for the efforts
Any other thoughts/help appreciated!!
If you get it solved, let us know how you did it.
Sorry I couldn't solve the problem for you.
Cheers
Resolved. By removal of lean kernel and extensive correction of ATT registration data. Thanks for the help
Sent from my SGH-I777 using XDA Free mobile app
For some reason, every time I try to install a sense based rom, it never boots.
I'm fairly new to flashing, and have flashed 4 or 5 aosp roms. Every time I install one of those, it always works correctly, no issues.
I have tried to flash several Sense based roms, such as ARHD 20.1, Insert Coin, and nv, and each time, it never works. I always do a factory wipe beforehand as well as a wipe in the aroma installer. It will go thru the process and install, and then prompt me to reboot, which it does. Once the screen comes back onm however, it just hangs on the white htc screen with the red development text. When i get back to the hboot, itll show nothing for os.
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom. Also, I just tried the NV rom which is based off my firmware, and it still gives me the same trouble. Does anyone know what I'm doing wrong?
I'm running an ATT Htc One m8, rooted, unlocked, s-off with sunshine, twrp recovery
mattprice86 said:
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom.
Click to expand...
Click to collapse
Give the ROMs about 10 minutes, and I bet they will boot. The extremely long boot time, and lack of boot animation (another symptom of this issue) makes a lot of folks believe the phone is stuck/frozen, when in fact its just taking a reeeeeally long time to boot.
If its true that the ROMs in fact never boot, it might just be an issue with your recovery. fastboot erase cache and either re-install recovery, update to the latest version, or try another recovery (Philz).
Even if the Sense ROMs boot, you might find some serious things are broken with your outdated firmware, such a broken WiFi. So I suggest either update your firmware or stick or ROMs based on your present firmware.
Ok thanks, i will try again. Ive read a bunch of threads about updating my firmware but couldnt find an answer to a question I have about it.
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
mattprice86 said:
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
Click to expand...
Click to collapse
Firmware includes the radio baseband, so it may cause issues with reception on AT&T. It seems at least a couple folks have been flashing the 3.28 firmware, but I haven't seen enough reports to give me a warm and cozy feeling. With S-off (which is required to flash the firmware, anyway) you can always revert. But still, basic reception is more important to me than a couple updated features. Personally, I'll probably wait until the 3.x firmware specific to AT&T starts rolling out.
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Leads me to believe that the radio does not matter like the N5 where the 820 and 821 radios were interchangeable.
HTC One M8
Thanks redpoint, you were right, I gave it some time and it did come on. You always seem to be the one answering my questions, I appreciate it.
As for the new fw, I was thinking that would happen too from what I've read, I just needed someone more experienced to confirm that. I think I'll wait as well.
Thanks again
Elisha said:
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Click to expand...
Click to collapse
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
mattprice86 said:
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
No probs.
redpoint73 said:
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
Click to expand...
Click to collapse
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former. For the record, my M8 is a "whelp", and I had to pay for Sunshine.
OMGMatrix said:
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former.
Click to expand...
Click to collapse
My guess would be the former as well. Keep mind that AT&T uses five different bands for LTE depending on your market region. Also keep in mind that travelling to another location may result in losing LTE reception (when you otherwise would have LTE on a AT&T specific radio).
Although none of this explains why I've seen some folks get NO SIGNAL whatsoever on AT&T's network after flashing the international firmware (2.x version, haven't seen any complaint yet on 3.28). Even if no LTE, those folks still should have been able to get HSPA and/or GSM since those AT&T bands appear to be supported by EMEA specs. So it leads me to believe there is something else going on aside from just band compatibility. Such as the network not falling back properly to HSPA/GSM.
I certainly don't have an issue if folks want to experiment with the 3.28 firmware on the AT&T network (as long as you know what you are doing, and are aware of the possible issues). Its certainly tempting with the 3.x based custom ROMs coming out. I might even experiment myself if I free up some time. But that spare time is a bit of a premium for me right now; and I also can't really afford ATM to have the possibility of reception issues or no service.
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
mattprice86 said:
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
Click to expand...
Click to collapse
You could always restore the backup you should be making before you do any mods on your phone. That would be the safest way.
So if I upgrade my fw then restore a backup, I will lose my fw changes?
I make nandroid backups before I do any, so I have approximately 60gb of backups on an external HD, and I always keep 1 or 2 on my internal and external storage