Assuming that most users use their phone in the region they bought it why would you flash a another one, since the original was probably optimized for their region. Will flashing all these various ROMs also change my radio? Also...is radio the baseband?
RE: Radio Flashing
cstrips said:
Assuming that most users use their phone in the region they bought it why would you flash a another one, since the original was probably optimized for their region. Will flashing all these various ROMs also change my radio? Also...is radio the baseband?
Click to expand...
Click to collapse
Depending on where and when you got your phone could mean a newer, faster radio might have come out. I do believe radios are area specific, but not sure.
I think any radio for the t989 will work but your data speeds, call clarity or even phone performance might take a hit.
Usually roms wont erase or put another radio on and if they do you can always just flash the proper radio.
Generally going from rom to rom while doing a full wipe will not remove your installed radio. And yes the baseband is your radio version.
Hope this helps, I only have a basic understanding and usually try to stick to the radio my provider pre-loaded.
I have a International GSM GNEX from Negri which was recently flashed to stock 4.2.2 via fastboot. I have flashed every north american radio and most European radios and have not been able to get more than about -100 dbm signal strength since the flash. My IMEI is not corrupted and other than the signal disparity, everything is functioning fine. My carrier is AT&T and my current baseband is UGLL1. I can access all the information on my SIM card so I'm not sure if that is the issue. Returning to prior versions all the way back to 4.0.4 does not resolve the issue. Does anyone have any ideas?
Thanks.
I've got the same.. Ive flashed everything roms, radios, kernels and the GSM radio is still crazy unstable.
Update if you have a break through.
Sent from my Galaxy Nexus using Tapatalk 2
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 am on Stock Lollipop N900TUVUFOB6 rooted, ever since I updated to Lollipop my radio sucks, call drops, low signals, crappy WiFi. wasn't bad at all before the update.
Does anyone have or has found a better radio?
Heff66 said:
I am on Stock Lollipop N900TUVUFOB6 rooted, ever since I updated to Lollipop my radio sucks, call drops, low signals, crappy WiFi. wasn't bad at all before the update.
Does anyone have or has found a better radio?
Click to expand...
Click to collapse
Same issue. I lost network when I enter in some building or club/caffe. ALso my phone doesnt want to connect on 4G even if its on 4G network, max is 3G download speed 11mbps.
as of 2020 the latest stock rom is of lollipop and the rom is on sammobile.com, you will need to create a free account to access everything (at least I did have to do so) the newest flashable zip is the one you want, it is supposed to have a fix for bad cell and wifi signal built in
Hello,
After some troubles I've converted my S-OFF x.xx.410.xx phone to a dev edition 2 weeks ago by reading a lot on this forum. I believe I did the following:
- flash 0PJAIMG nougat.zip from bootloader mode / SD
- run 4.14.617.6 RUU after flash
This worked for perfectly for a time.
On 1-1-2017 I got the 4.19.617.1 OTA notification which I accepted as I did not modify the system in any way. OTA completed succesfully however after OTA the phone lost mobile reception. In Android IMEI was not visible. In fastboot I saw IMEI with "fastboot getvar all".
Re-flashing RUU 4.14.617.6 worked to regain mobile reception however OTA nofication would of course still appear. Today I retried but with the same results -- no mobile reception after OTA.
To confirm with the new RUU available I ran the 4.19.617.1 RUU to re-flash phone and indeed no signal at all.
Then I ran the 4.14.617.6 RUU and signal again.
I read this in the FAQ:
"Q1: Everytime I flash a custom rom I lose my IMEI, my mobile reception and my phone stops recognizing my sim card. What's the reason for this?
A: You probably flashed a custom rom that is based on firmware 3.35.x although the firmware of your phone is 3.y (with y being any other number than 35). The boot image of 3.35.x based roms is not compatible with your firmware version. The solution of the problem depends on the question whether you are trying to install a Sense-based rom (like ICE or ViperOneM9) or a non-Sense-based rom (like CM): For Sense-based roms you just need to re-flash the stock boot image of your current firmware version."
This seems like my problem except I run RUU directly from HTC. Any idea on what I can do to accept OTA / reflash phone with 4.19.617.1 RUU ?
Thank you!
Was the phone rooted at the time of accepting the ota?.
There is a thread somewhere that explains how to fix the no signal issue on nougat dev edition.
I don't see the point in risking a brick for a beta firmware (dev edition is the beta to carrier versions) which is not necessarily a better firmware.
Also, make sure the rom and firmware you flash IS GSM and NOT CDMA.
Beamed in by telepathy.
@Fritti: The error that is described in the FAQ only appears if you flash a custom rom while using an incompatible firmware. You've used a RUU and are using the stock rom that got flashed by the RUU. That means firmware and rom are matching. Unfortunately, that means that I have no clue why you're facing this issue. There's no reason why you should lose your reception since all GSM versions are more or less the same if you compare their hardware. As far as I know only the LTE bands of the GSM versions differ.
shivadow said:
Was the phone rooted at the time of accepting the ota?.
There is a thread somewhere that explains how to fix the no signal issue on nougat dev edition.
I don't see the point in risking a brick for a beta firmware (dev edition is the beta to carrier versions) which is not necessarily a better firmware.
Also, make sure the rom and firmware you flash IS GSM and NOT CDMA.
Beamed in by telepathy.
Click to expand...
Click to collapse
If the phone was rooted the OTA wouldn't have been installable.
And please stop posting things that aren't true. The dev firmware is not a beta version. It's the US equivalent of the European 401 firmware or the Asian 708, 709 or 710 firmware. Beta firmwares look like this one: 2.10.401.180. They have three numbers behind the last dot. If you compare the 3.x firmware of SKU 401 and 617 you'll notice that 3.35.401.12 and 3.35.617.12 are almost exactly the same except for some contintent-specific tweaks.
It is true that the dev edition is not necessarily better than the 401 one. However, it's up to every single user to choose whether he or she wants to wait until the latest update gets released for his/her SKU or whether they want to convert to the dev edition which receives all updates first (in case of the M9).
Flippy498 said:
@Fritti: The error that is described in the FAQ only appears if you flash a custom rom while using an incompatible firmware. You're used a RUU and are using the stock rom that got flashed by the RUU. That means firmware and rom are matching.
Click to expand...
Click to collapse
Yes, that's what I thought.
Unfortunately, that means that I have no clue why you're facing this issue. There's no reason why you should lose your reception since all GSM versions are more or less the same if you compare their hardware. As far as I know only the LTE bands of the GSM versions differ.
Click to expand...
Click to collapse
Exactly. I don't understand either. Something get's flashed by the 4.19 RUU that messes up the IMEI detection? Is it possible to extract system.img from 4.19 RUU and just flash that to check whether that works?
If the phone was rooted the OTA wouldn't have been installable.
Click to expand...
Click to collapse
Indeed, phone was not rooted. I used 4.14 RUU and then no other flashes/mods.
And to be clear, for now it seems that I can repeat this -- run 4.19 RUU and no signal, run 4.14 RUU and signal again. If there is some radio partition and/or radio data partition that I can dump to check hex diffs I could try.
Fritti said:
Yes, that's what I thought.
Exactly. I don't understand either. Something get's flashed by the 4.19 RUU that messes up the IMEI detection? Is it possible to extract system.img from 4.19 RUU and just flash that to check whether that works?
Indeed, phone was not rooted. I used 4.14 RUU and then no other flashes/mods.
And to be clear, for now it seems that I can repeat this -- run 4.19 RUU and no signal, run 4.14 RUU and signal again. If there is some radio partition and/or radio data partition that I can dump to check hex diffs I could try.
Click to expand...
Click to collapse
You could use the decryption tool that is linked in the readme thread for extracting the system image and the firmware files.
Hi,
I'm facing the same issue - I think. I'm currently using a 4.14 original RUU ROM from HTC without modification.
When I accept the 4.19 OTA I lose connectivity in a most peculiar way: there are still signal bars and the phone confirms a LTE connection.
But there are no more APN options and no data. Also when I place a call the phone claims I'm out of service area.
One other thing I noticed is that the dialer shows a different number format when entering a phone number. With 4.14 I have the normal DUtch standard for dashes and area codes. With 4.19 I have a US standard. Could it be that the phone thinks I'm in the US and would a edit to the build.prop help?
I hope someone has some advice.
Gawain1986 said:
Hi,
I'm facing the same issue - I think. I'm currently using a 4.14 original RUU ROM from HTC without modification.
When I accept the 4.19 OTA I lose connectivity in a most peculiar way: there are still signal bars and the phone confirms a LTE connection.
But there are no more APN options and no data. Also when I place a call the phone claims I'm out of service area.
One other thing I noticed is that the dialer shows a different number format when entering a phone number. With 4.14 I have the normal DUtch standard for dashes and area codes. With 4.19 I have a US standard. Could it be that the phone thinks I'm in the US and would a edit to the build.prop help?
I hope someone has some advice.
Click to expand...
Click to collapse
Yes, that sounds like the same issue. You can actually edit the settings in the phone to disable the US international prefix. However it does not help for the out of service issue.
I have not yet had the time to try and flash only the firmware / recovery / system from 4.19, I will report back once I have tried.
Fritti said:
Yes, that sounds like the same issue. You can actually edit the settings in the phone to disable the US international prefix. However it does not help for the out of service issue.
I have not yet had the time to try and flash only the firmware / recovery / system from 4.19, I will report back once I have tried.
Click to expand...
Click to collapse
I have some news. I took the 4.19 No-Wipe firmware and flashed it by putting it on my SD card as 0PJAIMG.zip. It flashed and now I'm working on the 4.14 ROM with 4.19 firmware. All is working wel, most notibly making calls and using data.
This leads me to believe there is something in the Kernel/ROM of 4.19 that breaks our calling and data.
Does anybody have any other ideas to make 4.19 work?
The plot thickens .
I installed ICE ROM 4.19 after flashing firmware 4.19 and I had the same problem back, out of service area.
So I started comparing the build.prop files in the 4.14 ROM from HTC and the 4.19 ICE ROM. Then I changes a few lines to these values and I was able to call:
ro.ril.hsxpa=4
ro.ril.hsdpa.category=14
ro.ril.hsupa.category=6
ro.aa.rid=115
To get data (and be able to log in to a google account) I did another thing. I used the dialer to call *#*#4636#*#* and set the phone to WCDMA preferred and I had data.
The only thing left is to be able to use LTE/4G but that's for another time, I can finally use my phone on this firmware!
Gawain1986 said:
The plot thickens .
I used the dialer to call *#*#4636#*#* and set the phone to WCDMA preferred and I had data.
The only thing left is to be able to use LTE/4G but that's for another time, I can finally use my phone on this firmware!
Click to expand...
Click to collapse
Now try switching it back to LTE/WCDMA/GSM.
I had the same with S.Rom and after getting it to connect the way you did, switching back to auto gave me 4G again
bonesy said:
Now try switching it back to LTE/WCDMA/GSM.
I had the same with S.Rom and after getting it to connect the way you did, switching back to auto gave me 4G again
Click to expand...
Click to collapse
No such luck for me... As soon as my phone sees LTE, the phone force closes and aftter I have no Data and I'm out of service area again.
So I know this is nearly a necro but I wanted to give an update that I cannot try this anymore -- shortly after the failures started my phone got stuck in a bootloop. This had to be hardware error as it simply started one morning while I did not change anything. The Vodafone shop I brought it to agreed and send my unit in for (warranty!) repairs. I've since got it back with Android 7.0 on version 4.28.401.3, so there is no need for me to switch to dev edition now. I cannot say whether the signal issues were a symptom or a cause for my unit to fail.
Hoping that Gawain1986 has fixed his issues as well!