Related
Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)
politelyowned said:
Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)
Click to expand...
Click to collapse
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?
dawgdoc said:
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?
Click to expand...
Click to collapse
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.
politelyowned said:
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.
Click to expand...
Click to collapse
Some of the stock ROMs will remove root, that would be one way to resolve the issue. If you flash a stock image that is rooted, and it is rooted with SuperSu you can use the options in the SuperSu app to either temporarily unroot or to completely remove root.
I don't recall seeing a specific source for info about what bootloader / modem is needed in each situation. Most is accumulated knowledge from reading many posts and threads.
There are variations on what is correct, it all depends on the specifics of a device's status. For example, CM 11 would run on 4.3 bootloaders and modems up until about September of a year ago (or was that two years ago), since then you need to be on 4.4.2 bootloaders and modems. I think the same held true for AOSP based roms. I don't recall seeing where any of the 5.x.x roms have run on 4.3 bootloaders and modems. (Well, I think the devices run but have signal and data issues - both 4.4.x and 5.x.x roms.)
Generally you will see it said that the 4.4.2 Touchwiz based custom roms must be on 4.4.2 bootloaders and modems. In truth there were a number of such roms that would run with the 4.3 bootloader and modem IF one of a few specific kernels were flashed just after the rom was flashed.
Hello. I have d855 android 5.0 . Wanted to install cm 13. and here are my steps:
1. Rooted my 5.0 , flashed TWRP, and flashed CM13 and gapps. There was a problems with dialer after flash, so i downgraded phone into 4.4.2 V10a (using .tot and .dll files) . .
2. Again tried to flash CM13, but process was aborted and phone bricked.
3. Flashed stock 4.4.2 again. Again no luck to write CM .
4. Flashed stock 5.0 v21a using lg flashtool. Again - if i want to flash CM - phone always bricked (error executing updater binary) . And now, even with stock 5.0 my phone data connection do not work (only wifi works)
Please help .... how to reflash my phone and get CM and back data connection??
Just tried flash 4.4.2 again. Flashed successfully, but still any data connection Tried update into 5.0 using phone software updater, but after few updaters it fails (invalid software package).
Today found, that data connection works perfectly if i set GSM/WCDMA . If LTE is selected, there are no data connection at all. Also, can't flash custom rom, phone always stuck at LG logo. Anybody can help so solve my problems?
imdarex said:
Hello. I have d855 android 5.0 . Wanted to install cm 13. and here are my steps:
1. Rooted my 5.0 , flashed TWRP, and flashed CM13 and gapps. There was a problems with dialer after flash, so i downgraded phone into 4.4.2 V10a (using .tot and .dll files) . .
Click to expand...
Click to collapse
I want to cite only the first point you described, because it's "abominable"!
Sorry for the harsh tones, but... the dialer issues obviously involved the Cyanogen rom, especially because you're using the first nightlies, often unstable.
Why you accused the official firmware (therefore no more existing since you replaced them) and decided to downgrade?
Then you've to known that important downgrades like Lollilop > KitKat may irreversibly corrupt system partitions like "efs", which make your device losing of IMEI code and mobile data!
Now the only thing you can do is updating your device by settings menu until you reach latest firmware (21A).
Since you've to manually confirm each updates (10A, 10E, 20A etc.), the process will take almost 1-2 hour.
When the update process in definitely completed, you can try to root device, install TWRP and flash latest CM13 nightly.
In case of other issues, try the quite stable CM 12.1, or the stock-based FulmicsRom.
If you continue to have troubles, do a CSE flash of 21A firmware and send your device to warranty.
Simone98RC said:
I want to cite only the first point you described, because it's "abominable"!
Sorry for the harsh tones, but... the dialer issues obviously involved the Cyanogen rom, especially because you're using the first nightlies, often unstable.
Why you accused the official firmware (therefore no more existing since you replaced them) and decided to downgrade?
Then you've to known that important downgrades like Lollilop > KitKat may irreversibly corrupt system partitions like "efs", which make your device losing of IMEI code and mobile data!
Now the only thing you can do is updating your device by settings menu until you reach latest firmware (21A).
Since you've to manually confirm each updates (10A, 10E, 20A etc.), the process will take almost 1-2 hour.
When the update process in definitely completed, you can try to root device, install TWRP and flash latest CM13 nightly.
In case of other issues, try the quite stable CM 12.1, or the stock-based FulmicsRom.
If you continue to have troubles, do a CSE flash of 21A firmware and send your device to warranty.
Click to expand...
Click to collapse
Last time I connected my phone to LG mobile support, and it automaticallly updated my phone into newest official 21A firmware. IMEI - OK, data connection - still do not work when LTE is selected. So what i need to do now ? Try to root, install TWRP and flash CM 12.1 or FulmicsRom ?
imdarex said:
Last time I connected my phone to LG mobile support, and it automaticallly updated my phone into newest official 21A firmware. IMEI - OK, data connection - still do not work when LTE is selected. So what i need to do now ? Try to root, install TWRP and flash CM 12.1 or FulmicsRom ?
Click to expand...
Click to collapse
So what's your problem when LTE is enabled?
Mobile data won't work or simply fallback to HDSPA?
Simone98RC said:
So what's your problem when LTE is enabled?
Mobile data won't work or simply fallback to HDSPA?
Click to expand...
Click to collapse
When LTE is enabled, then there are no data connection at all.
imdarex said:
When LTE is enabled, then there are no data connection at all.
Click to expand...
Click to collapse
Surely downgrading the entire firmware to the first release of KitKat broke the radio part of your device.
Probably if you downgraded to latest KitKat firmware (10h maybe, instead of 10a), LTE should works properly.
Have you encountered that connectivity issue even before flashing CM 13 (on official firmware)?
Simone98RC said:
Surely downgrading the entire firmware to the first release of KitKat broke the radio part of your device.
Probably if you downgraded to latest KitKat firmware (10h maybe, instead of 10a), LTE should works properly.
Have you encountered that connectivity issue even before flashing CM 13 (on official firmware)?
Click to expand...
Click to collapse
No, after flashing everything was fine. There is a way to reflash radio part without downgrading again ? Because when i spoted that data connection do not working, i downgraded firstly to 10a (no data connection), then i get 10h update - still no data connection. And after 10h update, my phone got another update, but showed that can't update because package is wrong of something. After that i flashed 21A what i have in my phone now.
imdarex said:
No, after flashing everything was fine. There is a way to reflash radio part without downgrading again ? Because when i spoted that data connection do not working, i downgraded firstly to 10a (no data connection), then i get 10h update - still no data connection. And after 10h update, my phone got another update, but showed that can't update because package is wrong of something. After that i flashed 21A what i have in my phone now.
Click to expand...
Click to collapse
Probably the mobile data issue was related to CM 13.
But when you downgraded to 10A, the radio part was really damaged.
As I said if you want to downgrade, always preger the "less old" firmware you need.
Like you, I downgraded in past to KitKat, but I never looked for 10A! I directly flashed 10H.
Sorry, but at this point I don't know what you have to do.
When you flashed 21A firmware, have you done a CSE flash instead of a normal one?
If not, do it.
If yes, you have to appeal to warranty without any problem, since your device has official firmware.
Simone98RC said:
Probably the mobile data issue was related to CM 13.
But when you downgraded to 10A, the radio part was really damaged.
As I said if you want to downgrade, always preger the "less old" firmware you need.
Like you, I downgraded in past to KitKat, but I never looked for 10A! I directly flashed 10H.
Sorry, but at this point I don't know what you have to do.
When you flashed 21A firmware, have you done a CSE flash instead of a normal one?
If not, do it.
If yes, you have to appeal to warranty without any problem, since your device has official firmware.
Click to expand...
Click to collapse
Yes, i did CSE flash. Ok, thank you. I think there are no more options than warranty.
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!
All,
my sgh-i747 WiFi doesn't appear to work. under settings> WiFi slider (OFF)> slide to on (remains off)
next goto WiFi setup screen: no devices listed, buttons at bottom of screen dim/greyed out.
history:
phone was bricked by a forced ATT update. I finally did a rom update/reinstall to push a working stock kernel kitkat 4.4.2
thx
Rob
ALSO i need working links to Lollipop for sgh-1747 using oden
PS: I do ROM , hardware and software updates on data storage systems with petabytes of storage. BUT THIS PHONE MAKES ME FEEL STUPID....
My Hats Off to All Of You Who Hack, Play, or Make Mods for the Phones.
Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.
jason2678 said:
Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.
Click to expand...
Click to collapse
Thank You
jason2678 what you said makes perfect sense to me. like needing a VIN # for a 2002 Toyota to figure out what water pump or alternator because they used 6 different versions of each, LOL
so i would like to use 5.1 lollipop which is a custom ROM i believe, if you can suggest one i will defer to your judgement
but as a fallback suggest a kitkat ROM as well
bootloader I747UCUFNJ1
BASEBAND I747UCUFNJ1
KERNEL VERSION:
3.4.0-1514807
[email protected] #1
32-bit
modem msm8960
please and thank you
respectfully
123RobH
At NJ1 you're not on the latest bootloader and modem, but you're close enough. And your bootloader and modem match. I wouldn't mess with it. You'll be able to run all the latest custom ROMs on that, no problem.
If you want lollipop, look around the development section here. I'm not sure if you'll be able to track down a lollipop rom download linked to XDA. You might have to poke around old uploads for d2att on androidfilehost.com for 5.1.1 roms. I'm pretty partial to slimkat stable 9 on this phone, and it runs fine on NJ1 firmware too.
Oct-Os is probably the most actively supported rom currently. They've moved on to nougat these days. You'll be able to run it on NJ1 too. You might want to give it a shot.
Track down a rom and matching gapps. Then full wipe and flash them with TWRP recovery. If you run into any trouble or have any questions, just ask. I'm pretty certain once you get a custom rom on your phone your wifi problems will go away. Stick to lollipop, marshmallow, or nougat and you'll be fine. Even newer KitKat ROMs will be OK on NJ1.
Is there a way just to flash the Verizon radio only to a unlocked 6 pro and not have any issues on custom roms. I am currently on a custom rom and I flashed a non Verizon July ota update, but I have a Verizon sim in it now and something's not right with the cell/data service
Thanks !
It would be best asking in the ROM thread for that particular custom ROM, in my opinion. If the custom ROM already just uses the stock radio image as is without problems, then yes, you should definitely be able to just flash whatever stock radio image you want, to experiment, but there might be details I wouldn't know without being more knowledgeable about the custom ROM itself.
If you can flash it, you can Google it but it's probably something like fastboot flash radio <radio.img>. Replace <radio.img> with the filename of the radio image file that you have in the same folder as your ADB/Fastboot commands, or however you prefer to do it.
Good luck!
roirraW edor ehT said:
It would be best asking in the ROM thread for that particular custom ROM, in my opinion. If the custom ROM already just uses the stock radio image as is without problems, then yes, you should definitely be able to just flash whatever stock radio image you want, to experiment, but there might be details I wouldn't know without being more knowledgeable about the custom ROM itself.
If you can flash it, you can Google it but it's probably something like fastboot flash radio <radio.img>. Replace <radio.img> with the filename of the radio image file that you have in the same folder as your ADB/Fastboot commands, or however you prefer to do it.
Good luck!
Click to expand...
Click to collapse
Yeah I know the commands from past experiences but rooting and unlocking has changed since I last rooted. Because of the different partition set up it changes things. I was used to having cwm recovery or twrp but it seems most phones now a days need to be fastboot flashed and not really having a custom recovery to flash things. Anyways I appreciate the feedback.
I will try just flashing the radio.img unless someone tells me it's won't work like it used to
I'd take a look at this thread:
Thread 'Verizon calling problems' https://forum.xda-developers.com/t/verizon-calling-problems.4460389/
I'm using the current VZW firmware (I'm on prepaid VZW) but flashed A13's beta 4.1 radio because it seems to work better for me in my locale. Do I have objective data to back it up?
Nope.
jgrimberg1979 said:
Is there a way just to flash the Verizon radio only to a unlocked 6 pro and not have any issues on custom roms. I am currently on a custom rom and I flashed a non Verizon July ota update, but I have a Verizon sim in it now and something's not right with the cell/data service
Thanks !
Click to expand...
Click to collapse
I'm willing to bet most of the radios for American based stock ROMs are the same. I think vendor and various system things are what is changed between carriers because they're all designed to run all the same bands.
shag_on_e said:
I'm willing to bet most of the radios for American based stock ROMs are the same. I think vendor and various system things are what is changed between carriers because they're all designed to run all the same bands.
Click to expand...
Click to collapse
I think right but if so my service feels like it did 10 years ago speeds on lte/5G