Related
I had a problem with my korean version LG G2 (i messed up some system files and i was stuck at reboot), i had to reflash the original kdz system file, and then i had to hack the phone network, and doing this also fixed all the network connectivity problems i had previously, which i tough was hardware but apperently wasn't.
I had to make extended searches to restore my phone to a working state, so i wanted to create a small guide for anyone interested in completly resetting phone to original and change to international network, this might work with D802 or other models too, but i have no idea, so try at your own risks, i am sure it will work on all the korean versions of the LG G2
Before you start for safety make a complete back up of your system
but most important backup up your QCN and backup your modem.img modemst1.img and modemst2.img all three of them in a safe place, you might need them if you want to restore phone basebands to old state, and i highly reccomend you do.
Backup is a very important precaution, please don't make me responsible for lost stuff, your internal SD will be completly erased, so backup everything you need, this will wipe clean everything on your phone.
If you are interested in where to get kdz files
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=
and write your phone IMEI after the = (found in settings or on the serial number of phone, under battery, korean version has battery removable)
Write down your imei because you are gonna need it again
Then to flash the kdz you can find tutorials on XDA
You should be on 4.4.2 when you are done (unless there is a 4.5 lollipop OTA in the future, finger crossed)
anyway after flashing frimware, the phone will only recognize branded SIM cards of the korean networks depending on what version you installed.
So if you want your phone to be international, and with all the sensors working and so on, you have to root the rom, install a recovery with autorec from cloudyfa
enter recovery and flash this http://pan.baidu.com/s/1jIe5o pass: us56
this is a link i found on a chinese forum, i downloaded the F320LSK_EDGE_V3.zip
after reboot give sometime for the mobile to find network, it will need 5minutes the first time, it did for me, after everything working perfectly
the only thing is your imei will be reset to 0
to fix this
http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
the second part of this guide
I think this will help a lot of people with network problems, or those who have bricked and wasnt to restore the phone to a working state.
also after you are done you can install any rom you'd like, i'm on cloudyG3 and everything is flawless, just don't flash the baseband like reccomended, the proper baseband is the one i linked
I have no problems with wifi to 3G switching, i have no problem with 3G whatsover, there should be no problem also with 4G but i can't confirm that, haven't tried GPS extensivly yet, but it seems to be fine.
For what i can understand these files that you need to flash are the basebands of the 802 international model, so in theory this should fix problems for other models too, but i haven't tested, so do at your own risk
Thanks, so I have a an f320 ls, is it ok to flash the d802 baseband? I would like more bands for the US and possibly LTE. Thanks
grandixximo said:
I had a problem with my korean version LG G2 (i messed up some system files and i was stuck at reboot), i had to reflash the original kdz system file, and then i had to hack the phone network, and doing this also fixed all the network connectivity problems i had previously, which i tough was hardware but apperently wasn't.
I had to make extended searches to restore my phone to a working state, so i wanted to create a small guide for anyone interested in completly resetting phone to original and change to international network, this might work with D802 or other models too, but i have no idea, so try at your own risks, i am sure it will work on all the korean versions of the LG G2
Before you start for safety make a complete back up of your system
but most important backup up your QCN and backup your modem.img modemst1.img and modemst2.img all three of them in a safe place, you might need them if you want to restore phone basebands to old state, and i highly reccomend you do.
Backup is a very important precaution, please don't make me responsible for lost stuff, your internal SD will be completly erased, so backup everything you need, this will wipe clean everything on your phone.
If you are interested in where to get kdz files
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=
and write your phone IMEI after the = (found in settings or on the serial number of phone, under battery, korean version has battery removable)
Write down your imei because you are gonna need it again
Then to flash the kdz you can find tutorials on XDA
You should be on 4.4.2 when you are done (unless there is a 4.5 lollipop OTA in the future, finger crossed)
anyway after flashing frimware, the phone will only recognize branded SIM cards of the korean networks depending on what version you installed.
So if you want your phone to be international, and with all the sensors working and so on, you have to root the rom, install a recovery with autorec from cloudyfa
enter recovery and flash this http://pan.baidu.com/s/1jIe5o pass: us56
this is a link i found on a chinese forum, i downloaded the F320LSK_EDGE_V3.zip
after reboot give sometime for the mobile to find network, it will need 5minutes the first time, it did for me, after everything working perfectly
the only thing is your imei will be reset to 0
to fix this
http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
the second part of this guide
I think this will help a lot of people with network problems, or those who have bricked and wasnt to restore the phone to a working state.
also after you are done you can install any rom you'd like, i'm on cloudyG3 and everything is flawless, just don't flash the baseband like reccomended, the proper baseband is the one i linked
I have no problems with wifi to 3G switching, i have no problem with 3G whatsover, there should be no problem also with 4G but i can't confirm that, haven't tried GPS extensivly yet, but it seems to be fine.
For what i can understand these files that you need to flash are the basebands of the 802 international model, so in theory this should fix problems for other models too, but i haven't tested, so do at your own risk
Click to expand...
Click to collapse
jedisurfer said:
Thanks, so I have a an f320 ls, is it ok to flash the d802 baseband? I would like more bands for the US and possibly LTE. Thanks
Click to expand...
Click to collapse
Not really the baseband i linked is based on the D802 but is heavily modified to have it work on all F320 models, also if you flash this baseband it will erase your IMEI, and you if you flash other basebands that other devs post here on XDA they won't work.
It's working very good for me i have no complain, wifi 3G 4G and calls even roaming
grandixximo said:
Not really the baseband i linked is based on the D802 but is heavily modified to have it work on all F320 models, also if you flash this baseband it will erase your IMEI, and you if you flash other basebands that other devs post here on XDA they won't work.
It's working very good for me i have no complain, wifi 3G 4G and calls even roaming
Click to expand...
Click to collapse
Thanks for answering
grandixximo said:
Not really the baseband i linked is based on the D802 but is heavily modified to have it work on all F320 models, also if you flash this baseband it will erase your IMEI, and you if you flash other basebands that other devs post here on XDA they won't work.
It's working very good for me i have no complain, wifi 3G 4G and calls even roaming
Click to expand...
Click to collapse
Thank you for your information
Of all the stuff I googled, this is by far the page/site that provided the best and most helpful information. I will start the story by stating I am jealous of a friend of mine that has the LG G3. Seeing his Android Operating System made me drool. I wanted it. I rooted my phone and flashed the OptimusG3 v1.4.1 rom without making a backup of anything on my phone; no EFS backup, no IMEI backup, no modem/baseband backup, nothing. My previous experience rooting and flashing my HTC EVO gave me a false confidence in rooting the LG G2. When OptimusG3 booted I somehow lost the network, APNs, baseband; thus I couldn't make any phone calls, send text messages, or send or receive any internet data. My first reaction was to revert back to the stock firmware. I could not find a kdz file that matched my phone and would work; an LG G2 F320L on the LG U+ network in South Korea. I tried multiple versions of the LG Flash Tool to try and flash the stock firmware back on the phone. I eventually found a tot file that worked, but I ended up losing my IMEI in the process. I tried taking the phone to get repaired by LG techs and they couldn't figure out how to fix it. They wanted 281,000W, about $281, to fix the motherboard. I tried getting a replacement phone and the LG employees tried to get me to renew my contract and purchase a new phone and SIM card, around $480 for that route. I ended up buying an older LG F160L and placing my SIM card in that while I attempted to repair my phone.
On to the good stuff, the tot file got me to a working version of 4.4.2 Android but it was not stable and constantly rebooted, showed up with errors, no wifi, no keyboard. I found 4 different kdz files that were various versions of 4.2.2 and 4.4.2. It took me awhile to find a way to flash the kdz file properly. I used LG Flash Tool 2014 Build 03/07/2014. I had to change the Type to CDMA and Phone Mode to CS_EMERGENCY before doing a CSE Flash. With those settings I had 4.4.2 on the phone running F320L21V. I rooted the phone, flashed F320L_EDGE-4_42_V2 *AND* KK_Baseband_F320L, before using the above fix to restore the IMEI on the phone. As of right now the phone is on F320L21V, I can make and receive calls, send text messages, the wifi hotspot works, and I can send and receive internet data. However, there are still a few issues: knock-on doesn't work and in the notification bar it states there is a software update is available. Every time I install the update the phone boots into TWRP. I have to hit Advanced, Terminal Command, Select and enter in the following two commands in the shell to get it to boot:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
I have since made an EFS backup, backed up the modems, and made a TWRP backup. Is it safe for me to flash another rom? Should I try using the LGMobile Support Tool to restore the firmware to F320L21y, to which I'm sure there isn't a root method for?
grandixximo said:
I had a problem with my korean version LG G2 (i messed up some system files and i was stuck at reboot)
Click to expand...
Click to collapse
Is this working with latest 30D Firmware Lollipop 5.0.1?
I was working great on Kitkat firmware but seems to be not working good on Latest 5.0.1.
If you have any new Mod like this for lollipop please share.
Hello, to both of you,
@AlphaQ99
You can safely flash clodyG3 and have a phone almost identical to the g3, that is the ROM I'm using, it's stable and looks fantastic, and I have decent battery also with original kernel.
It should remove the update requests and the other problems you are having, just don't flash the basebands that come separated from the ROM, keep the basebands posted in the OP, or reflash it if something doesn't work.
@Shivam Bhalla
You can try the edge v3 zip from the cloud baidu drive I posted in the OP?
Let me know if it works, I guess if it does let me know, because I want to flash the new update too, if not let me know too so I won't flash it...
If it doesn't work just download a 4.4 or 4.2 kdz and then flash the modified basebands and whatever ROM you'd like over that, I reccomend cloudyG3 if you want a G3 look.
And restore your imei with the OP instructions.
If the v3 doesnt work when there will be a lollipop version it will be posted in that drive in the OP.
I think we'd better wait still for updating to lollipop kdz or roms, I myself will attempt the update just after the clodyg3 ROM will be updated, and that will take sometimes, since they are waiting for a D803 official update...
Best of luck to both of you
I tried to flash CloudyG3, Optimus G, and CloudyFlex 2.7 all for the F320L. All of them did not work properly. I had data, I couldn't make phone calls or send text messages. I think the APN settings were incorrect and I tried changing the settings to match LG U+ and tried to change the build.prop file. They all made the com.android.phone cause a force close. To fix the knock on/off I had to go to the dialer, hit 3845#*320# > HW Device Test > Touch Test > Touch Firmware Upgrade.
I ended up going back to stock using the kdz file in this post and I'm having fun with lollipop: http://forum.xda-developers.com/showpost.php?p=58206425&postcount=1
You flashed lollipop and everything is working fine?
You are using my basebands?
Or was it unlocked already?
I simply flashed the stock kdz file and everything is working fine. I lost root which at this point I am fine with.
Sent from my LG-F320L using XDA Free mobile app
I see but you are using a U+ Sim?
Like the one ur phone is locked with?
Yes, I am using a U+ SIM card.
Sent from my LG-F320L using XDA Free mobile app
Then everything should have worked with the other kdz too, the problem is I'm not using a U+ Sim so I need to unlock the network, for that I probably need root, and a recovery, so I'll wait, unless the other guy can figure it out...
I'm happy everything turned out OK for you, how is lollipop? Worth the update?
I like lollipop. It's something fresh and new. I was really tired of the old keyboard and the UI was getting stale. I just wanted something new and different. Lollipop has been working flawlessly and had it come out two weeks ago I would probably wouldn't have bothered with rooting the phone to begin with. For some people it wouldn't be worth updating because I'm pretty sure there isn't a root method for it yet. For someone who doesn't care much about rooting the phone it would be worth it. When I get tired of lollipop I'm sure I'll be back on here looking for root options.
grandixximo said:
Then everything should have worked with the other kdz too, the problem is I'm not using a U+ Sim so I need to unlock the network, for that I probably need root, and a recovery, so I'll wait, unless the other guy can figure it out...
I'm happy everything turned out OK for you, how is lollipop? Worth the update?
Click to expand...
Click to collapse
I tried flashing it on lollipop but networks doesnt seems to be stable sometime whole day i dont have any problem sometime they never come.I am also not using U+ sim thats why I also need that hack to work on my phone. Now am again back to cloudy g3 rom and waiting for any updates regarding newbasebands for lollipop too.
grandixximo said:
Then everything should have worked with the other kdz too
Click to expand...
Click to collapse
@grandixximo
Are you still on Kitkat or using Lollipop???
These basebands are not working on lollipop and because of which I couldnt able to have taste of stock lollipop roms.
Networks works good in 30E latest firmware but not a single sensor is working after flashing this basebands on latest firmware.
If you got any solution for new basebands do share with us.
No lollipop baseband that i know of sorry....
I look at the chinese forums from time to time, and they seem to have figure out something, but i cannot understand very clearly, since i use google translate....
If someone who reads chinese can have a look.
http://bbs.gfan.com/forum-1345-1.html
this is the forum
Seems we'll be waiting for it
Hey guys !!! I fixed the network on Android 5.0 (f320l)
I am from Kazakhstan, and do not speak English use a translator .... so sorry.
1) First you need to install stock rom (I used f320l21y_00.kdz) (LG Flash Tool 2014)
2) Install Root (I used Stump-v1.2.0.apk)
3) Install Recovery (I used F320L_AutoRec.apk)
4) Then you need extract TWRP.rar to Internal Storage
5) Reboot to TWRP and tap to "Restore" => 2014-12-06--02-11-08 KOT49I => swipe to restore => Reboot (decided sim card)
6) Restore IMEI (post 1)
7) Then i install CloudyG2_3.0 (5.0) and I have all worked on Android 5.0
TWRP.rar can use for f320l and f320k (f320s not sure, but you can try)
Good luck!
Sorry for my English ....
Hey so i updated my LG G2 from 24A to 39A, but once I got to 39A my sim card could no longer be read. In the network settings tab it now says unknown and under Mobile network type it says disconnected. I tried bringing it back to stock 24A but it still did not work. I tried another sim card but nothing. Before I updated my phone I made a backup, but when I loaded it up it still did not work. I tried flashing different Roms but no dice. Its weird because I can use wi-fi calling and everything works. It is only when I am not on wi-fi where nothing gets read. Can anyone help me? Any help would be greatly appreciated.
Thanks
are you by any chance having this problem when you try vexxoaosp?
Im not entirely sure which one that is, but I dont think so. Could you provide a link to it so I can try it?
I don't think you should try it then.
Sorry mate, did you do a stock reset with a kdz file fitting your model?
I recommend you to use LG Flash Tool 2014 with a stock kdz file. There is a thread about it here.
I tried that...multiple times lol
Did you contact your service provider? Any warranty left?
I bought it second hand, so unfortunately no warranty
Hello, first of all I want to let you know that I am not an expert but have so far been able to convert my Axon A2017 to the US A2017U version.
Big thanks [email protected] for supplying the necessary files.
I have:
-unlocked the bootloader
-rooted the phone
-flashed successfully B20
However, When I upgraded to B29, I lost TWRP and the cell radio of the phone is non-responsive. It won't even turn on. Bootloader is sill unlocked. I made phone calls on my T-mobile network when it was the origional A2017 B8 version. So I believe the bandwidths are compatible.
I have already done the following troubleshooting: (note: WIFI currently works just fine)
-My network is with T-Mobile, and I have been using a different axon A2017U for over a year with no problems.
-When I type *#*#4636#*#* and got to phone Info says, GSM Service: Radio Off, and the Turn on Radio button does nothing.
- I have tried working with every setting in this menu with no luck.
-When I insert my SIM card that is working on my current axon 7 into the converted A2017U, it is able to pick up T-Mobile network u.s. LTE, (fast.tmobile.com) and T-Mobile US (tmus). However, there are no bars because the radio is not turned on.
-When I try to search for new networks an error message saying, "network search cannot proceed when the data service is enabled disabled it?" So I disable it and nothing happens except for an error message saying "error while searching for Networks".
-In network mode I have switched to every option available, LTE/wcdma/GSM, wcdma/GSM, and GSM only with no result.
I am currently running Android version 6.0.1 on build B-29. Any help to get the radio up and running to receive phone calls would be greatly appreciated. Everything else is working except for the phone radio to send and receive phone calls.
Thanks for any Help.
Do you still have your IMEI or did the partition get corrupted?
ultramag69 said:
Do you still have your IMEI or did the partition get corrupted?
Click to expand...
Click to collapse
I check the number with several online checks, as well as T-Mobile, and they are unable to bring up any information about the number. I imagine it got blocked or corrupted during the upgrades.
What do I do to unblock it or make it functional again?
Go to settings>About>Status and check your IMEI number. If it's blank its noyt gonna work on any network...
You might be able to restore it if you have a backup of it - no-one will give you their backup as you then have their phone - or as a last resort, you might need to restore to the stock Chinese Rom again and see if that fixes it...
Good luck, I'm off to bed after a long backshift...
ultramag69 said:
Go to settings>About>Status and check your IMEI number. If it's blank its noyt gonna work on any network...
You might be able to restore it if you have a backup of it - no-one will give you their backup as you then have their phone - or as a last resort, you might need to restore to the stock Chinese Rom again and see if that fixes it...
Good luck, I'm off to bed after a long backshift...
Click to expand...
Click to collapse
Thankfully the numbers are there on both IMEI slot 1 and IMEI Slot 2. Thanks for your help. I hope to hear from you after a good night of rest.
Flash the correct modem/bootstack for your device.
Shipcaptian said:
Thankfully the numbers are there on both IMEI slot 1 and IMEI Slot 2. Thanks for your help. I hope to hear from you after a good night of rest.
Click to expand...
Click to collapse
Just go to the LineageOS thread and download the A2017 modem file, then just flash it
Choose an username... said:
Just go to the LineageOS thread and download the A2017 modem file, then just flash it
Click to expand...
Click to collapse
Sounds Good
Will I need TWRP to flash it or can is just use the Reg. recovery system?
Shipcaptian said:
Sounds Good
Will I need TWRP to flash it or can is just use the Reg. recovery system?
Click to expand...
Click to collapse
You need TWRP. Just install it with axon7tool via edl if you don't have fastboot, or try axon7toolkit
Choose an username... said:
You need TWRP. Just install it with axon7tool via edl if you don't have fastboot, or try axon7toolkit
Click to expand...
Click to collapse
Here's the latest update:
I loaded TWRP onto the phone and installed the file A2017U_N_Modem.zip. (Several Times)
nothing has changed. The radio is still turned off and no signal is being picked up from my carrier T-Mobile.
While loading it says: Loading A2017U_N_Modem for nougat system. I am not running nougat and I cannot find any other modem to download. Will that make a difference?
Any other suggestions are welcome?
Shipcaptian said:
Here's the latest update:
I loaded TWRP onto the phone and installed the file A2017U_N_Modem.zip. (Several Times)
nothing has changed. The radio is still turned off and no signal is being picked up from my carrier T-Mobile.
While loading it says: Loading A2017U_N_Modem for nougat system. I am not running nougat and I cannot find any other modem to download. Will that make a difference?
Any other suggestions are welcome?
Click to expand...
Click to collapse
You need to flash the A2017 modem, not the A2017U one
Here: https://www.androidfilehost.com/?fid=457095661767137840
bkores said:
You need to flash the A2017 modem, not the A2017U one
Here: https://www.androidfilehost.com/?fid=457095661767137840
Click to expand...
Click to collapse
Okay it works! I've got signal but when I try to make a phone call and my other phone picks up I can't hear or say anything. Any idea what's happening? I have tried refreshing the signal with no luck.
Hey man, I'm having the same problem with my Axon 7, brand new A2017U. Turned it on for the first time and I haven't had an ounce of radio on. Same things you've tried I've tried and it refuses to work. Mine is not rooted and I don't want to. I've tried downgrading my update and to no avail. Factory reset etc. I've contacted ZTE and they said they have forwarded my details and my phone details, storage size, color etc. To the necessary representatives. I think I'm gonna be sent a replacement, but just wanted to let you know your not alone.
A few days I woke up with no service on the Nexus 6p. This was a few days after updating to the latest oreo build. Sim card seems detected because when I take it out another message shows up "No SIM card - No service", and when I put it back it only shows "No service". Tried putting the card in a Nexus 5X and it works fine.
Tried the following with nothing working so far:
- Switching 2G/3G/LTE and rebooting in between.
- *#*#4636#*#* and turning off the radio, switching between the different options of GSM/LTE/etc...
- Restoring a working nandroid backup
- Reflashing different ROMs
- Factory reset
- Factory reset then flashing ROMs
- Wiping cache and dalvik
- efs fix in twrp
Hardware version ANGLER-VN2
IMEI shows up under IMEI information tab but not under SIM Status tab, there it shows not available.
I live in Ontario Canada, carrier is Freedom mobile.
So now I'm stuck, tried calling google and hwawei and they won't do an RMA because my warranty is expired.
Anyone has any ideas to try?
Thanks in advance.
Not that this is going to help, but this has GOT to be an Oreo issue, myself as well as at least 4 others that I have seen has been getting the No service, or No Sim, mine did the No Sim, then started bootlooping.
---------- Post added at 07:36 AM ---------- Previous post was at 07:06 AM ----------
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
No this has nothing to do with O.
Which version phone do you have? H1511 or H1512?
What country are you in now?
What is your carrier? If MVNO state that.
Are your IMEI and phone numbers showing up in settings?
Everyone, please put the most basic information in your profile like where you live, which carrier you are currently on, and maybe even which variant of your phone.
I updated the first post with more info. How do I tell if I have H1511 or H1512? I bought it from the google store in Canada.
More information is good. Please update your XDA profile so the next person trying to help can check there first. You can find the device variant by booting to bootloader (not recovery) and using the vol toggle to navigate to "Barcodes". IMEI should show up there too. Date of manufacture, Serial #, etc. I think you should have started a normal thead, not Q/A, BUT your IMEI and a lot of other information should be showing up under SIM info. That's a problem. Second, you say you did the EFS fix in TWRP. Can you explain how you did this? Did you use one of YOUR OWN TWRP backups which contained the modemst1,modemst2 and restored ONLY those two partitions to your device? Did you receive any confirmation or error? Have you tried using a SIM from a Rogers or Telus in your phone to see if the SIM info shows up?
Thanks for the help, I'll update my profile with this info as well.
in the bootloader the IMEI shows up along with the rest of the info. It's a H1511 device.
The EFS fix is by following this: https://www.theandroidsoul.com/fix-empty-imei-corrupted-efs-no-sim-unknown-baseband-wifibluetooth-issues-restoring-twrp-backup/
is modemst1 and 2 contained in the twrp backup? and if so how do I restore it? in restore options there's system, data, vendor and boot only. I guess it's an option in the backup that I haven't selected?
I tried another SIM also from freedom and it didn't work. I don't have a Rogers or other SIM to try currently.
Right, so if you didn't ever select the EFS partitions when using TWRP Backup, you never backed them up so under Restore they don't show up (so you can't use that method). You can however use TWRP terminal or fastboot to wipe those and reboot. I would be sure to try at least one SIM from either Rogers or Telus. If that doesn't work, then wipe the EFS partitions and let them rebuild (hopefully).
Definitely Oreo issue. Google messed with something and it broke data for many people. I have been troubleshooting this for the last week (Verizon, US, fully stock 6P) and finally found a thread where a Google rep acknowledged the problem and said it was high priority for a fix.
I wish you luck with that one @LucJoe. This has been happening for the past 2 years from MM, N, and now O...and XDA is full of threads (just look). So you just go ahead and wait for Google to fix it for you, LOL. - Not a new issue related to O.
Never happened to me before updating. The data issues manifest differently across different carriers but for some reason Oreo likes to play it safe and disconnect data. I have not been able to get LTE for more than a couple seconds, but will get slow unstable 3G occasionally. Google confirmed the issue here: https://productforums.google.com/forum/#!msg/phone-by-google/kw3ZcXd1BVs/7HYuANdoAgAJ
A recent success using terminal from TWRP (or the OS if you are rooted). You can also use fastboot to do the same thing using the commands in the article posted in this Q/A (method 2). Good luck! See thread here.
This seems like it's a different issue described in that thread. I'm not running out of data, there's no service and no connection of at all to any network.
I did find that and try it before posting here. It did nothing to fix the problem. It did say that something was copied over '4 MB copied, at 14.3 MB/s' something like that but nothing changed.
I also have the same issue. Have tried everything including going back to stock 7.1.2 & locking the bootloader. Nothing seems to work. Interestingly, when i pull up the hidden phone diagnostic menu, it shows all cell measurement info which means that the antenna is receiving signals but the phone somehow is not registered on the network?
I can wipe those partitions with fastboot but is it safe? I have never used TWRP and my problems started after updating to Oreo. Is there a chance the official OTA could corrupt those partitions?
@LucJoe- That fix is not for you. That is for users who have no IMEI or phone number under About Phone>>SIM info. Your issue (as I understand it) is a weak and intermittent signal that keeps disconnecting LTE and sounds like a carrier or SIM issue. Why not go get a new SIM provisioned for your phone. That or pop somebody else's SIM in your phone and see if you get a different outcome.
Yes that was my first thought as well. I got a new SIM, then another one. So 3 SIMs now with the same result. I've been on the phone with so many techs from Verizon/Total Wireless and none of them have any answers. If I put the same SIMs into a Moto E4 I picked up for testing, it works fine. But the 6P immediately disconnects from LTE then bounces between 3G/1X.
My next test is to try a SIM from a different network I guess... maybe Verizon is blocking my 6P. Or maybe my LTE radio is damaged somehow.
So I did this using TWRP but wasn't sure if it actually went through or not. I did it now through adb from pc and also fastboot and it says permission denied. Any idea how to bypass that?
Somehow or another I have managed to screw up my modem on my SPerry XT1766 (Boost Mobile).
I only get Emergency Calls Only radio signal, Settings app and bootloader info shows Baseband Not Found or Unknown.
I tried using RSDLite to flash
XT1766_SPERRY_SPRINT_7.1.1_NCQS26.69-64-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
which contains the fsg.mbn and NON-HLOS.bin files, but this doesn't seem to help. I've tried multiple firmwares with multiple different modems and nothing seems to be getting my modem up and going. Back when I originally updated I flashed the partition updater also. I have no idea what to do now. I'm downloading the 69-56 version to try that, but I doubt it'll be any different. If anyone has any idea on what to do that would be great. Thanks
Knuxyl said:
Somehow or another I have managed to screw up my modem on my SPerry XT1766 (Boost Mobile).
I only get Emergency Calls Only radio signal, Settings app and bootloader info shows Baseband Not Found or Unknown.
I tried using RSDLite to flash
XT1766_SPERRY_SPRINT_7.1.1_NCQS26.69-64-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
which contains the fsg.mbn and NON-HLOS.bin files, but this doesn't seem to help. I've tried multiple firmwares with multiple different modems and nothing seems to be getting my modem up and going. Back when I originally updated I flashed the partition updater also. I have no idea what to do now. I'm downloading the 69-56 version to try that, but I doubt it'll be any different. If anyone has any idea on what to do that would be great. Thanks
Click to expand...
Click to collapse
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
@Knuxyl
Are you on Boost network? I've seen the radio off problem with ppl using a different sim.
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
Yeah I already tried that but it jept giving me an error saying unknown command [ ]] or somrthing along those lines. i looked through the script and didnt see any typis. i think your NON-HLOS.img is different format than the NON-HLOS.bin files found in the stock firmwares, plus it's much larger. Anyways, tried a fastboot flash the modem with it and that didnt work either.
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
madbat99 said:
@Knuxyl
Are you on Boost network? I've seen the radio off problem with ppl using a different sim.
Click to expand...
Click to collapse
No I am not on a boost network but this problem goes more into firmware than network compatibility because the bootloadet itself isnt even recognizing the baseband. For the record I am still using a CDMA network like boost (Verizon)
Also as an update, the 56 version didn't fix it either
Knuxyl said:
No I am not on a boost network but this problem goes more into firmware than network compatibility because the bootloadet itself isnt even recognizing the baseband. For the record I am still using a CDMA network like boost (Verizon)
Click to expand...
Click to collapse
The latest update did that too many people. It won't work with a different sim. The radio will be off.
I bet if you put in a boost SIM, it would pop right on.
They changed something in the -8 firmware.
One guy building ROMs (not here anymore) made some changes to his build that got certain networks to work on his ROM.
He never got the chance to share exactly what he was changing.
It seems that if you booted the phone ever with the original sim inserted, it tripped a qfuse (of sorts) and it seems they have added a way for that particular reading to turn off the radio completely if you're not using one of their SIMs.
madbat99 said:
The latest update did that too many people. It won't work with a different sim. The radio will be off.
I bet if you put in a boost SIM, it would pop right on.
They changed something in the -8 firmware.
One guy building ROMs (not here anymore) made some changes to his build that got certain networks to work on his ROM.
He never got the chance to share exactly what he was changing.
It seems that if you booted the phone ever with the original sim inserted, it tripped a qfuse (of sorts) and it seems they have added a way for that particular reading to turn off the radio completely if you're not using one of their SIMs.
Click to expand...
Click to collapse
You are 100% on point. Sprint (and its subsidiaries) had Motorola Mobility to include code in an OTA update which would disable functionality of any network other than the original UICC (SIM). In other words, when you got a new Sprint compatible xt1766 (Sprint, Boost or Virgin Mobile), opened the box and booted the device with the preinstalled SIM in it, the xt1766 became forever locked to that network -- the OTA update carved that in stone. The update made it impossible to downgrade the baseband radio, killed all GSM functionality, and broke the radio on custom ROMs (the latter being unintended most likely). The only people I have heard of getting around this are the ones that didn't take the -8 OTA update. Like you were saying, I'd like to know what Jason M. done in his custom ROM to fix radio function, whereas at least the radio would work with the original SIM on a custom ROM. He said something about "adding missing symlinks" to the build.
I did this too somehow. I think this might bring your baseband back (it did for me), but... well, I'll get to the "but..." Anyway, Boot to TWRP, mount the Persist partition, then go to terminal or pull up an ADB shell and do:
chmod 0700 /persist/rfs/msm/mpss/datablock/id_00
Click to expand...
Click to collapse
Reboot with a SIM card inserted and voila, you maybe might have a baseband again. Hooray! Except in my particular case, I regained a baseband and then somehow lost an IMEI. Well, not really "lost," it's still there when I pull up the barcodes page... but on bootup it thinks it's 000000000000001. I still haven't ever fixed it, though I did manage to turn it to a single 0 somewhere along the line. Fkit.
But I don't know of anyone else who's lost their IMEI this way, and it's been too long ago and I've tried way too many failed fixes to remember what else could have triggered the problem to start with, so who knows. If you decide to try it, definitely make a backup of the Persist partition before you do anything...and make sure your backup turns out to be good first, not corrupt like mine turned out to be....sigh.
lugnut2099 said:
I did this too somehow. I think this might bring your baseband back (it did for me), but... well, I'll get to the "but..." Anyway, Boot to TWRP, mount the Persist partition, then go to terminal or pull up an ADB shell and do:
Reboot with a SIM card inserted and voila, you maybe might have a baseband again. Hooray! Except in my particular case, I regained a baseband and then somehow lost an IMEI. Well, not really "lost," it's still there when I pull up the barcodes page... but on bootup it thinks it's 000000000000001. I still haven't ever fixed it, though I did manage to turn it to a single 0 somewhere along the line. Fkit.
But I don't know of anyone else who's lost their IMEI this way, and it's been too long ago and I've tried way too many failed fixes to remember what else could have triggered the problem to start with, so who knows. If you decide to try it, definitely make a backup of the Persist partition before you do anything...and make sure your backup turns out to be good first, not corrupt like mine turned out to be....sigh.
Click to expand...
Click to collapse
Seriously, you unbricked my kids phone!
Requested permission to access your file twice
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
Is your updater still available?
May I please download your file?
my email: [email protected]
thank you
ELEKTRIKMESSIAH said:
Is your updater still available?
May I please download your file?
my email: [email protected]
thank you
Click to expand...
Click to collapse
You see that member's account disabled? So.... You're talking to no one
Reading is fundamental