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 ....
Hi all,
I picked up a used G5 Plus (XT1687) on eBay, with the bootloader already unlocked. I immediately installed AICP ROM with a VZW SIM from a working G4. The phone showed LTE for data, but no voice service. That started a long series of firmware changes that saw me trying Pixel Experience, and a few stock ROMs, having my IMEI show as 0 a few times as well.
I'm at a point with the phone now where I'm on the latest retus channel stock ROM (POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) with the bootloader locked. The phone now connects with 1xRTT for voice and EvDo (3G) for data. If I swap this SIM into my other phone (Pixel XL) I get full LTE in the Pixel but still 3G only in the G5+.
The only other standout item is in the BP tools SIM menu, where I get the following errors.
Phone ICCID Compare with SIM ICCID: ERROR
and
PHONE ICCID: PHONE_ICCID_UNKNOWN
I feel like with all the flashes I may have really screwed things up. does anyone have any recommendations on what to try to get LTE service back?
TIA!
I am in the exact same boat. Searching around the web, there are several reports of this model phone not switching properly, from EvDo revA to LTE channels. Many of these are from non bootloader unlocked phones, and Verizon {and other carriers} pass it off to Lenovo and vice versa. I unlocked mine myself, but being an Ebay phone and knowingly unlocking it, I realize their is no recourse, except hoping for a proper modem software fix from moto. I've been able to get LTE/4g working a couple times, but it doesn't last, so it is a 3g phone for now.
[email protected] said:
I am in the exact same boat. Searching around the web, there are several reports of this model phone not switching properly, from EvDo revA to LTE channels. Many of these are from non bootloader unlocked phones, and Verizon {and other carriers} pass it off to Lenovo and vice versa. I unlocked mine myself, but being an Ebay phone and knowingly unlocking it, I realize their is no recourse, except hoping for a proper modem software fix from moto. I've been able to get LTE/4g working a couple times, but it doesn't last, so it is a 3g phone for now.
Click to expand...
Click to collapse
glad I'm not alone here. I'm surprised to hear it happens to phones that have never been unlocked and Moto isn't forthcoming with a fix.
Sent from my Pixel XL using Tapatalk
bra1niac said:
glad I'm not alone here. I'm surprised to hear it happens to phones that have never been unlocked and Moto isn't forthcoming with a fix.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It seems they would rather replace than fix.
Same with my phone. It has been unlocked and I've been on numerous variations of ROMs stock and custom. Everything was smooth with no issues until I decided to flash an Oreo 8.1 ROM. Immediately after I was greeted with 3G EVDO-Rev A./1xRTT mode with no access to 4G/LTE on Verizon. Sim Card status is screwy with some apps seeing it, albeit improperly configured, most not able to detect it at all. If I return to any ROM below 8.1 I have no data service whatsoever. Hoping a fix is found as all the workarounds do nothing.
Also like the OP, I can get LTE to stick sometimes by messing around with Radio Bands and switching options around in the 4636 menu. But that leaves me without voice/text/mms service.
[email protected] said:
It seems they would rather replace than fix.
Click to expand...
Click to collapse
sad but true
Sent from my Pixel XL using Tapatalk
I came from a Droid Turbo [quark] and have always liked the motorola phones, in my remote area, for the superior radio reception. My Galaxy S4 dropped calls and data in many of the remote areas, so the Turbo was a welcome upgrade. However, even the with the Turbo, there were Roms that we had to clean and flash updated modems for, when they became balky. I wonder if someone with more engineering knowledge than I have, could look at these twrp flashable modem files, and convert to these G5 plus modems.
[email protected] said:
I came from a Droid Turbo [quark] and have always liked the motorola phones, in my remote area, for the superior radio reception. My Galaxy S4 dropped calls and data in many of the remote areas, so the Turbo was a welcome upgrade. However, even the with the Turbo, there were Roms that we had to clean and flash updated modems for, when they became balky. I wonder if someone with more engineering knowledge than I have, could look at these twrp flashable modem files, and convert to these G5 plus modems.
Click to expand...
Click to collapse
Yeah it seems like there should be some way to un**** the phones after flashing an 8.1 ROM. I just don't know enough about the innards of the ROMs either. I had to follow the instructions here https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808 in order to fix an issue with the phone showing an IMEI of 0. There you end up deleting modemst1 and modemst2. I guess they get replaced by the stock or custom ROM, but I have no idea where you would get copies of those from a ROM that would fix this issue, if such a thing exists.
bra1niac said:
Yeah it seems like there should be some way to un**** the phones after flashing an 8.1 ROM. I just don't know enough about the innards of the ROMs either. I had to follow the instructions here https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808 in order to fix an issue with the phone showing an IMEI of 0. There you end up deleting modemst1 and modemst2. I guess they get replaced by the stock or custom ROM, but I have no idea where you would get copies of those from a ROM that would fix this issue, if such a thing exists.
Click to expand...
Click to collapse
Flashing the modem bin. "NON-HLOS.bin" then erasing modemst1 & 2 gets the 4g/lTE back for some, but has never worked for me. The quark modem we installed the "clean modem" zip which according to the read-me
this zip will "erase" format the modem status partition:
mdm1m9kefs1 = modemst1
mdm1m9kefs2 = modemst2
Click to expand...
Click to collapse
Then flash the modem according to rev of the rom, which included META-INF file folder, boot.img, emmc_appsboot.mbm, fsg.mbn, gpt.bin, logo.bin, modem.img, rpm.img, sbl1.mbn, sdi.mbm, and tz.mbn files.
[email protected] said:
Flashing the modem bin. "NON-HLOS.bin" then erasing modemst1 & 2 gets the 4g/lTE back for some, but has never worked for me. The quark modem we installed the "clean modem" zip which according to the read-me Then flash the modem according to rev of the rom, which included META-INF file folder, boot.img, emmc_appsboot.mbm, fsg.mbn, gpt.bin, logo.bin, modem.img, rpm.img, sbl1.mbn, sdi.mbm, and tz.mbn files.
Click to expand...
Click to collapse
Hm so you're saying to do this:
Flash NON-HLOS.bin from the stock ROM zip
erase modemst1
erase modemst2
reboot
And that might restore LTE? I've never just flashed that bin and erased.
In the info file in the stock ROM I'm using, it shows modem version M8953_37.46.07.47R. In the ROM zip I have
boot.img
fsg.mgn
gpt.bin
logo.bin
missing from the list are
emmc_appsboot.mbm
modem.img
rpm.img
sbl1.mbn
sdi.mbm
tz.mbn
I wonder if the stock ROMs from OTA only include the files that changed, so an older stock ROM might have one or more of those missing files. Or those files just don't apply to the G5+ but do to the Quark.
I'll try downloading a bunch of the older stock ROMs and unpacking them and seeing if any of them contain files that aren't included in the one I've been using.
I've also been ignoring this, but I believe these two steps in the stock ROM reflash have always failed for me:
fastboot erase customize
fastboot erase clogo
I'm not sure what they do so I'll have to dig into that.
It is weird that out of the blue I flashed a 8.1 rom,,,after flashing different 8.1 roms before that,,,I lost VZM service all together. Was able to get back 4G data service only, no voice service. However, after a few mins voice service comes back. Never happened the numerous times I flashed 8.1 before so wonder why it happens all the time now? Makes me think there is a design flaw with the internal radio,,,not the modems software? Would really be nice to see an 8.1 update from Moto,,,may help solve these problems.
Archangel said:
It is weird that out of the blue I flashed a 8.1 rom,,,after flashing different 8.1 roms before that,,,I lost VZM service all together. Was able to get back 4G data service only, no voice service. However, after a few mins voice service comes back. Never happened the numerous times I flashed 8.1 before so wonder why it happens all the time now? Makes me think there is a design flaw with the internal radio,,,not the modems software? Would really be nice to see an 8.1 update from Moto,,,may help solve these problems.
Click to expand...
Click to collapse
yeah a factory Oreo ROM would probably help straighten a bunch of things out.
Sent from my Pixel XL using Tapatalk
bra1niac said:
Hm so you're saying to do this:
Flash NON-HLOS.bin from the stock ROM zip
erase modemst1
erase modemst2
reboot
And that might restore LTE? I've never just flashed that bin and erased.
In the info file in the stock ROM I'm using, it shows modem version M8953_37.46.07.47R. In the ROM zip I have
boot.img
fsg.mgn
gpt.bin
logo.bin
missing from the list are
emmc_appsboot.mbm
modem.img
rpm.img
sbl1.mbn
sdi.mbm
tz.mbn
I wonder if the stock ROMs from OTA only include the files that changed, so an older stock ROM might have one or more of those missing files. Or those files just don't apply to the G5+ but do to the Quark.
I'll try downloading a bunch of the older stock ROMs and unpacking them and seeing if any of them contain files that aren't included in the one I've been using.
I've also been ignoring this, but I believe these two steps in the stock ROM reflash have always failed for me:
fastboot erase customize
fastboot erase clogo
I'm not sure what they do so I'll have to dig into that.
Click to expand...
Click to collapse
I think those errors are normal, at least with some stock roms.
Those extra files were from the quark modem files, which is an older modem/radio, so the drivers are going to be different. By the way, I have flashed the modem, flashed the erase modemst1 & 2 and every combo, yet no luv.
This problem can be attributed to one of 2 things. First would be hardware, but by selecting LTE only in the testing menu, I was able to get data in LTE. So the radio's frequency band that supports LTE from Verizon in these phones does work. The Motorola Moto G5 Plus TD-LTE 32GB XT1687 which I have, supports 4 GSM bands, 5 UMTS bands, 15 LTE bands, and 3 CDMA bands. My carrier Verizon uses 3 LTE bands and 2 CDMA bands. The way I understand how it works, is by default, all 4g/LTE capable phones look for a signal in the bands, approved by your sim, in the LTE range first. If not found, it switches to 3g or CDMA , and if that isn't found, 2g. If we are correct in assuming the radio's ability to receive the 3 LTE bands is still functional, it stands to reason the driver that auto switches to CDMA is corrupt. I lost my 4g/LTE on the Pixel Rom, and not by reverting back to stock. It was the only Rom I had ever flashed on the phone after unlocking and installing twrp recovery. I have since gone back to stock and relocked the bootloader, hoping the next ota will jog the drivers to look for LTE before passing off. The times I have briefly had 4g kind of reinforces the theory that the drivers that pass off to 3g are corrupt.
A little research into the baseband processor and its radio firmware RTOS [real-time operating system,] shows it to be closed source, proprietary, yet full of flaws. It is even susceptible to the long standing "Hayes command set" but I don't believe this to be where our particular problem lies. Because it is so closed, it is doubtful the Oreo roms were able to inadvertently touch anything inside this secondary operating system all phones have. It is more likely it is the communication between our android firmware, and the radio firmware, but why the restoration back to stock, doesn't remedy it, is a mystery. The devs that adapted the Oreo roms to this device, missed this link or they would not have written to that area, I'm sure.
You guys are a lot smarter than me,,,it just scared the heck out of me. I flashed a 8.1 rom like I have done at least a dozen or so times on this phone and then suddenly no signal at all,,,then just 4g data and no voice service. I went back to a 8.1 back up that I have and within a few mins everything came back. Now, I am afraid to flash anything rom wise for fear of not getting any signal back.
Something like this really deserves an official statement by Lenovo, Motorola or Verizon. Even if that statement is an unfortunate "you knew the risks associated with unlocking the bootloader and flashing ROMs / modems". Even if none of the three know what exactly is going on they should at least let us know.
Is this problem something that happens with all carriers and their LTE signals? Am I right in thinking that using Verizon is currently the only carrier in which the issue can't be fully repaired?
I havent yet restored my partially working (3g/1x) EFS backup to a stock Nougat Rom yet as I want to have 4G working as well if I do that. If the other carriers can be fully repaired I'll just switch carriers until I get a new phone.
There have been some reports around that putting in a GSM sim even temporarily brings back LTE. I haven't had access to one to try.
[email protected] said:
I think those errors are normal, at least with some stock roms.
Those extra files were from the quark modem files, which is an older modem/radio, so the drivers are going to be different. By the way, I have flashed the modem, flashed the erase modemst1 & 2 and every combo, yet no luv.
This problem can be attributed to one of 2 things. First would be hardware, but by selecting LTE only in the testing menu, I was able to get data in LTE. So the radio's frequency band that supports LTE from Verizon in these phones does work. The Motorola Moto G5 Plus TD-LTE 32GB XT1687 which I have, supports 4 GSM bands, 5 UMTS bands, 15 LTE bands, and 3 CDMA bands. My carrier Verizon uses 3 LTE bands and 2 CDMA bands. The way I understand how it works, is by default, all 4g/LTE capable phones look for a signal in the bands, approved by your sim, in the LTE range first. If not found, it switches to 3g or CDMA , and if that isn't found, 2g. If we are correct in assuming the radio's ability to receive the 3 LTE bands is still functional, it stands to reason the driver that auto switches to CDMA is corrupt. I lost my 4g/LTE on the Pixel Rom, and not by reverting back to stock. It was the only Rom I had ever flashed on the phone after unlocking and installing twrp recovery. I have since gone back to stock and relocked the bootloader, hoping the next ota will jog the drivers to look for LTE before passing off. The times I have briefly had 4g kind of reinforces the theory that the drivers that pass off to 3g are corrupt.
Click to expand...
Click to collapse
Yeah that all seems to make sense. Something we broke with a software change should be fixable with a software change. Hopefully the next OTA isn't too far away.
[email protected] said:
There have been some reports around that putting in a GSM sim even temporarily brings back LTE. I haven't had access to one to try.
Click to expand...
Click to collapse
That's interesting. My wife is on T-Mobile and was using a Moto G4, now a Pixel. I'll have to snag her SIM for a few minutes to see what happens later this afternoon. I'll report back. :good:
bra1niac said:
That's interesting. My wife is on T-Mobile and was using a Moto G4, now a Pixel. I'll have to snag her SIM for a few minutes to see what happens later this afternoon. I'll report back. :good:
Click to expand...
Click to collapse
It might pay to remove your sim, flash the
Code:
fastboot erase modemst1 fastboot erase modemst2
and then insert her sim. I'm just thinking that would clear the modem for the new bands to set themselves.
Hello,
I bought a H910 off ebay, it said it was unlocked, the frequencies matched the ones of our carriers and it was not mentioned that the phone was AT&T.
Is there any way to get it to work on the local antennas?
I have attempted to :
- Use access points the carrier support
- Use the hidden menu to attempt to unlock frequencies, however the H910 has barely any options in there.
- Flash a H915 Rom in there while following the runningnak3d's guide : https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
It gave much more options within the hidden menus, total control over any bands, protocals etc. However, it is in my understanding that the modem doesn't work when flashing a H915 from H910 even if the
hardware is apparently the same.
I have then continued the root procedure thinking it might give me the functional modem back with the additionnal options of the H915 but that wasn't the case. I even gained a bad looking warning startup screen.
So now I am wondering..... is there any way to get the signal working? I didn't find any guide or any posts which seemed to indicate steps. It is pretty frustrating that they give us so much troubles even if the hardware has all the capabilities, damn carriers.
If nobody has any suggestions, could I know where I could get the same H915 rom used on the kdz within the root guide? I would like to keep that rom and see if applying the modem fix would allow me to have signal.
Edit : ..... I just tried to flash the H915 again... and I was dumb, instead of selecting all, I kept the modem and recovery......... now my phone no longer want to boot and I can't even use LGUP since it is not booted. Download mode doesn't work either.
I thinks I just killed it
Edit 2 : Oh my god, just got Download mode to work, the procedure was slightly different than usual.
"The step I was missing was to remove the battery, disconnect the USB cable, put the battery back in, hold volume down but don't press power, instead connect usb cable" -chuckyanutsup
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
Hello XDA,
I recently purchased a H910 from EBAY.
I was able to install Oreo and root it using the excellent tutorials before I was able to have a working sim card on hand so I cannot confirm if this phone was good or bad as I received it. I am using an activated ATT sim card and have used it in another phone with calls, texts, and data working. I have not for the life of me been able to get the any of these features to work on the H910. I have checked the APN settings, I have confirmed both the IMEI number and the sim ID number with ATT. The H910 is able to see the sim card but no mobile network is connected. I can use wifi calling and texting.
I did make a backup/dump of the phone and have flashed the modems, fsg, and misc images with no effect.
I have tried to restore to a stock image of 10q and 20G with the results ending in boot loops so I have not been able to test the stock firmware.
Is there any way to test for a hardware fault?
I would like to avoid returning this phone for something that could be fixed on my end.
Any advice would be greatly appreciated.
MDM3D said:
Hello XDA,
I recently purchased a H910 from EBAY.
I was able to install Oreo and root it using the excellent tutorials before I was able to have a working sim card on hand so I cannot confirm if this phone was good or bad as I received it. I am using an activated ATT sim card and have used it in another phone with calls, texts, and data working. I have not for the life of me been able to get the any of these features to work on the H910. I have checked the APN settings, I have confirmed both the IMEI number and the sim ID number with ATT. The H910 is able to see the sim card but no mobile network is connected. I can use wifi calling and texting.
Click to expand...
Click to collapse
What APN are you using ?
I did make a backup/dump of the phone and have flashed the modems, fsg, and misc images with no effect.
Click to expand...
Click to collapse
This sounds like a hardware failure
I have tried to restore to a stock image of 10q and 20G with the results ending in boot loops so I have not been able to test the stock firmware.
Click to expand...
Click to collapse
are you sure the roms are flashing correctly ? no errors in TWRP ?
I have restored many times with those 2 files and never had a bootloop, flash the 10q or 20G rom then format data before you reboot
Is there any way to test for a hardware fault?
I would like to avoid returning this phone for something that could be fixed on my end.
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Ive had nothing but great luck getting phones off ebay, but it really sounds like you may have gotten a lemon.
The H910v20 is one of the easiest phones to root and return to stock the 20G rom should work and immediately ask to update to 20H with a AT&T sim in it.
taking the 20G to 20H update will insure you have all the correct modem files and APN.
clsA said:
What APN are you using ?
This sounds like a hardware failure
are you sure the roms are flashing correctly ? no errors in TWRP ?
I have restored many times with those 2 files and never had a bootloop, flash the 10q or 20G rom then format data before you reboot
Ive had nothing but great luck getting phones off ebay, but it really sounds like you may have gotten a lemon.
The H910v20 is one of the easiest phones to root and return to stock the 20G rom should work and immediately ask to update to 20H with a AT&T sim in it.
taking the 20G to 20H update will insure you have all the correct modem files and APN.
Click to expand...
Click to collapse
clsA, Thank you for taking the time to reply, and for your excellent tutorials.
I tried both the stock(default) APN and manually entering the nxtgenphone APN info I was prompted by ATT but no change. Searches for a signal for about 30 seconds and the throws an x over the signal bars. The phone does detect the sim card and shows my phone number.
I do think it is hardware failure. All of the modem problems I have read have an error saying that the radio is off. I do not get this I get a message stating out of service. I also copied the Modem files from another stock H910 20H from a friend and that did not change anything. Their phone also shows signal bars even when the sim card is removed.
I checked the MD5 Hashes and they are correct on the SD card I was using. I saw no errors in TWRP and I tried 3 different flashing combos with both 10q and 20H. The first was to format device and then advance wipe system, cache, and dalvik, then flash, followed by format device. I then tried just format before and format after flashing, and then not formatting before and only formatting after and got the same boot loops with the 3 combos depending on whether I was using 10q or 20g. ie 2 different boot loops with the different zips. Once the boot loop started I could get to the stock recovery to "erase" the phone but that had no change. The only way I found to stop the loops was to flash the 996.kdz file using lgup and start over. The 20H file works perfectly. as does the 10R. It is really odd.