Flashed 5.1 rom to 4.4 and missed the Rf-calibration - G3 Q&A, Help & Troubleshooting

Hello guys,
my first post here on XDA, I'm having problems with the G3 not finding 3g cellular. I can see the RF-calibration is not okay from the hidden menu so I guess on the process I messed up the digital band filters on the RF-module. The phone can find 2g cellular & sometimes 4g cellular but almost never 3g.
Heres the whole story:
1. Bought used and rooted LG G3, was on android 4.4
2. Flashed new modem and 5.1 rom --> lost IMEI(I guess at this point I lost the calibration also but didn't notice it)
3. Flashed original 4.4 rom & repaired the IMEI with the Qualcomm Qpst tool, PID and some other nv items seemed to be erased as well
4. The LG support tool updated the phone to 5.1 and then 6.0
5. Now I'm at the 6.0 with IMEI ok, but the rf-calibration status is "not okay"
Found several topics saying not to try flash 5.1 custom rom to 4.4. I also viewed the installation script of the modem and the rom and I think that there is possibility that 5.1 had somehow different memory structure or had more nv-items and in order to successfully update from 4.4 the script should have manipulated the nv-memory too.
Does anyone know what happens when you flash 5.1 rom to 4.4 phone?
So basically are the filter profiles & other nv-items overwrited in the memory or does my modem software just point on the wrong addresses in the memory at the moment and the data still is left? Found LG G3 factory guide from the internet and they calibrate the filters at production.
I'm basically quite new with android but know some of signal processing and c++ & python programming. Will be more than happy about all information.

Related

LG G3 (SPRINT VERSION) Unlocked and rooted Signal Help

I have an LG G3 sprint version LS990.
It has been Flashed with the CloudyG3 rom i beleive version 1.2
I had it unlocked to work with T-mobiles network
I am presently experience issues with the ability to maintain signal stability.
For instance I am present at -109dBm and 1asu using the WCDMA preferred option. Which to my understanding is a weak signal.
I would say that I stay between -90dBm and -110dBm although I know for a fact I am not in a dead zone area or an area without any towers near by supporting my network.
So my question is what are the potential issues that can be address such as
1. Any settings I can change either via the network option or Build.prop that will help fix this issue
2. Is it due to the individual rom that I am using.
3, How do I update the baseband if I am able to
4. What are the steps needed to flash over to a newer Rom and Kernel
Under software information
Android version 4.4.2
Baseband Version MPSS.DI.2.0.1.c1.13-00009-M8974AAAANPZM-1
Kernel Version 3.4.0
Build Number KVT49L.LS990ZV4
Software Version
LS990ZV4
Any insights are much appreaciated I am not the most experienced with the android O.S when it comes to flashing and rooting as I came from Iphones
Thanks
americangaming said:
So my question is what are the potential issues that can be address such as
1. Any settings I can change either via the network option or Build.prop that will help fix this issue
2. Is it due to the individual rom that I am using.
3, How do I update the baseband if I am able to
4. What are the steps needed to flash over to a newer Rom and Kernel
Click to expand...
Click to collapse
Do you ever get this problem with stock rom?
To update basedband. Download modem.img and run these commands
adb shell
su
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
Since you have CloudyG3 already which means you must have TWRP installed. Just download the rom for your LS990, wipe all partitions excluding internal storage and flash it using TWRP
itsbighead said:
Do you ever get this problem with stock rom?
To update basedband. Download modem.img and run these commands
adb shell
su
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
Since you have CloudyG3 already which means you must have TWRP installed. Just download the rom for your LS990, wipe all partitions excluding internal storage and flash it using TWRP
Click to expand...
Click to collapse
I had originally paid to have my g3 unlocked so if you're referring to the sprint os prior to unlock and flash then no i had no issues.
Is the modem.img completely reflashing my phone to a different OS or can i simply load it into the proper directory and execute it somehow?
I'm not exactly an expert with androids but know a crapton about computers so i beleieve my knowledge can carry over to a point.
In that case i think CloudyG3 is using a incorrect baseband for LS990 which is resulting in your poor signal
itsbighead said:
In that case i think CloudyG3 is using a incorrect baseband for LS990 which is resulting in your poor signal
Click to expand...
Click to collapse
Which one would you recommend at this point?

LG G3 d855 problems after flash

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.

No Service to Vodafone Australia

Hello
I currently have an LG G3 D855 with a software version of v20m, and an android version 5.0. This phone used to work perfectly with Vodafone when I was using the phone almost a year ago. I rooted the phone, and about 2 months after rooting, the play store couldn't establish a reliable connection to the server. About a month later the phone's digitizer broke (I'm trying to give as much information as possible whether relevant or not). I was given a Sony Xperia Z3 to use until 2 weeks ago, the digitizer has again, broke on this phone. Luckily beforehand, I performed a D.I.Y fix on my LG G3, and wanted to return to using this. I believe I updated the phone to android 5.0 (as stated earlier) and I am not too sure whether or not the software was updated from v10L to v20m (this could be wrong). The google play problem still persists (But This is not the problem I am currently focusing on), but now, after getting a new sim (since the nano sim from the Xperia does not fit in the LG G3) and transferring my number over, the LG G3 just continues to search for a network and never connects. I attempted to perform a stock factory firmware reset using two different methods: I followed the tutorial found on lg g3 root . c o m (I cannot post urls as a new member) and used the .tot and .dll file for v10E. after the flash tool stated 'ready', and I removed and reconnected the device as the tutorial states, After 2secs the program prompts 'FAIL; Model Information Check Fail. I also used the method from lg - phones . o r g and used the .kdz file for v10L and v20m. neither versions worked, as on the last stage, another window pops up (which I left alone, as the tutorial says to leave it) and the s/w update moves only to 15% and does not move further. I also tried clicking ok on the window that pops up (which by the way, the window states the phone is disconnected, or there is something wrong with the server connection, please try again in a moment) and the flash tool quits.
I have stayed up till 3am for 4 nights in a row. I have tried everything I have thought of, and now as I type this I have paid for an unlock code incase the phone has decided to lock itself to a carrier other than Vodafone. Any help would be very greatly appreciated as I currently do not have any phone.

G3 D855 No cellular connectivity since upgrade

Hi, my eBay UK purchased reconditioned D855 did an LG software update last night for "Google optimisations" and it installed, I believe, the v20i-aug-26-2015 update.
My phone says it's now running V20n-TUR-XX.
Hardware info
Model: LG-D855TR
Android version: 5.0
Baseband: MPSS.DI.2.0.1.c1.13.2-00002-M8974AAAAANPZM-1
Kernel 3.4.0
Build number LRX21R.A1445947622
Software version V20n-TUR-XX
Network: Three
Everything worked perfectly before the LG update, now it can't see to any cellular data network (I have the signal strength meter showing but no data icons at all) and it was working perfectly before the update.
It works fine on wifi.
I've factory reset and checked everything I could - it's still not seeing the cellular data network. I've manually selected three and let it do it automatically but still no joy. Data is enabled.
LG can't find the IMEI on their system which means it's a foreign or international version I guess and, despite the fact I'm 99.9% sure their update has screwed my phone, they won't take it back to fix it.
What are my options do you think, re-flashing? If I have to then I'd rather go to a stock LG rom or, if possible, a vanilla Android ROM. What do you think, and what flash options do you think I should go for if I have to flash? Fairly n00b when it comes to doing that.
Thanks for any help you can offer!
Solved, but don't know how to delete.

Unknown baseband along with null IMEI

So, recently, I've been struggling with a strange issue which I think that it's a hardware issue. Let me explain you all the things I've done so far.
I was on LOS 14.1 and wanted to go back to stock rom. I had used Nougat for long time and never used stock MM on my G4. I just wanted to give MM a try. Maybe it could give me better battery life and performance. I don't know.
Since I have an UsU'd H815, I properly flashed stock mm boot, mm system, mm modem and then the UsU H815 baseband. However, when the device boots, I got "com.android.phone stopped" warning all the time. Then I went into recovery mode, flashed UsU mm boot and stock MM modem. Now, I got cellular working, set up everything but then I realized that camera didn't work this time. So, basically,
Stock boot + stock modem + UsU baseband = no cellular - camera works
UsU boot + stock modem + stock baseband = cellular works - no camera
Stock boot + stock modem + stock baseband = must crash with blue screen. But now, it just boots and everything works except cellular
Thinking that since I had on LS991 bootloader and maybe it is necessary for both baseband and the bootloader to be the same model/version, I flashed LS991 baseband. During boot animation, the phone got an instant reboot. I don't remember if it booted to either that blue modem crash screen or android system. Most probably it was Android system. Anyway, cellular didn't work anymore.
I've flashed whole backup (except aboot, laf, raw_resources) that I had created with SALT before UsU'ing my device. Still no luck. I always get null imei from *#06# and unknown baseband. When I launch hidden menu (*#546368*#815#), I also get force close on SVC Test > Version info. The information there about baseband, hw version, and NT code say that 'should be implemented'. So far, I think that it's a hardware issue.
Well, but with
Code:
cat /data/loggers/modem**a file including modem in its name**
, I see my IMEI and factory version. Somehow, some things recongize my imei number. I also see my imei on imei screen (power off the phone and hold down vol -, vol +, and the power button at the same time until it gets into imei screen).
I tried erasing modemst1, modemst2, and fcg which a reboot followed that proccess as it's stated and confirmed by some others to work here (ofc I restored my backup, still no luck).
Everything made me think that it was a software issue until I see this thread. The screenshot that the op shared on his 2nd post is same with mine. It says null for everything. And his 8th reply and the 3rd option I listed above (Stock boot + stock modem + stock baseband) makes me think that this is totally a hardware issue. Why the 3rd option makes me think that this is a hardware issue is that some/a part is damaged on the main board, and the device/chip/whatever cannot connect to it. Thus, cellular service cannot start, and since it cannot start, the things that must be going wrong with modem just go well.
I feel like I'm ready to try anything (which won't make it completely dead) to get cellular work on my G4, including flashing LS991's ARB 2 TOT file. I'm open to new thoughts and ideas.
Edit: So, according to my researches, I have found out that RX Module is about cellular (@madiweb also stated that on his 8th post on his thread I linked above). I've checked the service manual of H815. It is told there that if there is no gsm/wcdma/lte signal, RX Module (EAT62994301) has to be replaced. I'll ask to LG Customer Care and surely will add info here for the ones who need it.
berkantkz said:
[....]
Thinking that since I had on LS991 bootloader and maybe it is necessary for both baseband and the bootloader to be the same model/version, I flashed LS991 baseband.
[....]
Edit: So, according to my researches, I have found out that RX Module is about cellular (@madiweb also stated that on his 8th post on his thread I linked above). I've checked the service manual of H815. It is told there that if there is no gsm/wcdma/lte signal, RX Module (EAT62994301) has to be replaced. I'll ask to LG Customer Care and surely will add info here for the ones who need it.
Click to expand...
Click to collapse
I never wrote anywhere that you should flash a baseband of another device. Just think about it: I have created for every model its very own baseband package. Why should I do that when you could cross flash them? Wouldn't make sense right? The main reason (while there are others) is: ARB and signature checking within the modem files. I knew it from VS986 which also heavily uses the ARB "feature" in their firmwares: when you flash a modem firmware of the vs986 to the h815 it will break signal forever. The same may apply to others liek the LS991 which also makes heavy use of the ARB "feature" in their firmwares.
The ONLY way I know to recover from here (for the h815) is replacing the hardware (or in my case faking the device as bootloop affected and sending it to LG for repair). I cannot tell you which one blows the fuse but maybe it is that module you found above.
.-
steadfasterX said:
I never wrote anywhere that you should flash a baseband of another device. Just think about it: I have created for every model its very own baseband package. Why should I do that when you could cross flash them? Wouldn't make sense right? The main reason (while there are others) is: ARB and signature checking within the modem files. I knew it from VS986 which also heavily uses the ARB "feature" in their firmwares: when you flash a modem firmware of the vs986 to the h815 it will break signal forever. The same may apply to others liek the LS991 which also makes heavy use of the ARB "feature" in their firmwares.
The ONLY way I know to recover from here (for the h815) is replacing the hardware (or in my case faking the device as bootloop affected and sending it to LG for repair). I cannot tell you which one blows the fuse but maybe it is that module you found above.
.-
Click to expand...
Click to collapse
So, my G4 tour ends here. I'd make it bootlooped and send to LG for repair. However, it has been more than 2 years, and the warranty time is 24 months. So, I am out of warranty. Instead of repairing this device, I guess I would buy something new.
Thank you for your help. Fortunately, G4 community have a person like you!

Categories

Resources