IMEI =0, after reverting back to Stock Rom from PIE custom rom - Moto G4 Plus Questions & Answers

My Moto g4 has some weird issue , after flashing Stock rom the IMEI shows 0 , tried with some rfs method which was available in forum still the issue is same.
Any fix for this friends?

vinay lucy said:
My Moto g4 has some weird issue , after flashing Stock rom the IMEI shows 0 , tried with some rfs method which was available in forum still the issue is same.
Any fix for this friends?
Click to expand...
Click to collapse
Have a look at this https://forum.xda-developers.com/mo...oto-g4-plus-imei0-issue-t3859068/post77986531

strongst said:
Have a look at this https://forum.xda-developers.com/mo...oto-g4-plus-imei0-issue-t3859068/post77986531
Click to expand...
Click to collapse
Tried with that method, its showing IMEI but no service in SIM slot

Tried with that method after ADB codes,
IMEI number is shown and IMEI SV is 11,
Baseband version : M8952_70030.25.03.62.02R DFLT_FSG
Still Sim card showing NO service

Its a baseband problem since the baseband ends with "DFLT_FSG". I am currently as of now trying to fix this issue and it seems I have succeeded a bit (partially).
Were you able to restore your IMEI back after trying the above link mentioned in this thread?
And a question, do you have Moto G4 (not the plus variant) with single sim??
And can you tell what variant do you have, (I am not able to recall its name) like we have XT1622, XT1642, etc.

Heeth21 said:
Its a baseband problem since the baseband ends with "DFLT_FSG". I am currently as of now trying to fix this issue and it seems I have succeeded a bit (partially).
Were you able to restore your IMEI back after trying the above link mentioned in this thread?
And a question, do you have Moto G4 (not the plus variant) with single sim??
And can you tell what variant do you have, (I am not able to recall its name) like we have XT1622, XT1642, etc.
Click to expand...
Click to collapse
Yes only one IMEI number is found.
Model : XT1624 (Moto G4)
But Sim Card showing no service.
Its a dual sim model device.

vinay lucy said:
Yes only one IMEI number is found.
Model : XT1624 (Moto G4)
But Sim Card showing no service.
Its a dual sim model device.
Click to expand...
Click to collapse
Man, I have the same issue. After back to stock after install Pie (ArrowOS), and then this happened. I hope someone help us! :/

edjalmo said:
Man, I have the same issue. After back to stock after install Pie (ArrowOS), and then this happened. I hope someone help us! :/
Click to expand...
Click to collapse
Finger crossed

edjalmo said:
Man, I have the same issue. After back to stock after install Pie (ArrowOS), and then this happened. I hope someone help us! :/
Click to expand...
Click to collapse
Can you please tell whether you tried bringing your IMEI back with this this method?: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
If, yes how many IMEIs are you able to currently see in your device? Is it one or two??
And also which device model do you have?? Mention its variant (like XT1622, XT1642) and the number of sims which it supported earlier

Heeth21 said:
Can you please tell whether you tried bringing your IMEI back with this this method?: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
If, yes how many IMEIs are you able to currently see in your device? Is it one or two??
And also which device model do you have?? Mention its variant (like XT1622, XT1642) and the number of sims which it supported earlier
Click to expand...
Click to collapse
Yes! Using this method I got the IMEI back. But the SIM network does not appear. When I trie to make a call this apper: "turn off airplane mode to make a call" (or someting like that. I'm from Brazil and do not speek english so well).
I can see two IMEIs.
My device is XT1640, two SIM support.
Screenshort: https :// imgur. com/ a/ kIdk4LZ (I could not get the normal link, sorry)
(I put the cell phone in english to make more easy)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

vinay lucy said:
Yes only one IMEI number is found.
Model : XT1624 (Moto G4)
But Sim Card showing no service.
Its a dual sim model device.
Click to expand...
Click to collapse
edjalmo said:
Yes! Using this method I got the IMEI back. But the SIM network does not appear. When I trie to make a call this apper: "turn off airplane mode to make a call" (or someting like that. I'm from Brazil and do not speek english so well).
I can see two IMEIs.
My device is XT1640, two SIM support.
Click to expand...
Click to collapse
@vinay lucy, you have converted your phone to Moto G4 (single sim variant).
Both of your IMEIs are restored but since your device thinks it has single sim, it just shows one IMEI.
Do not worry, there is a solution to this problem!
This was the method which worked for me, but unfortunately, my baseband got changed to LATAM, so if you are ready for it, then you may proceed.
1. Download these files and keep them in your adb directory: https://drive.google.com/open?id=1NtOTKgmJIP_Ys26CYd9KBdwhWdGfbCqH
2. Flash or boot with official TWRP for the device located here: https://dl.twrp.me/athene/twrp-3.2.1-0-athene.img.html
If you want to flash TWRP (that means to replace your current recovery with TWRP), use this command:
Code:
fastboot flash recovery <recovery-name>.img
If you want to boot TWRP (that means be able to boot into TWRP without replacing your stock recovery), use this command:
Code:
fastboot boot <recovery-name>.img
3. Boot into TWRP, if you haven't already,connect your device to PC and type these commands:
Code:
adb push modem.img /dev/block/mmcblk0p1
adb push fsg.img /dev/block/mmcblk0p16
adb push hw.img /dev/block/mmcblk0p43
Note: If you are using any unofficial versions of TWRP, you will not be able to push the last file i.e hw.img as it will be stuck at 100% so use official TWRP only.
Now we have almost completed. Reboot your device and check if you are able to see IMEIs. At this point, your IMEIs and baseband will be unknown, but that doesn't matter, just check whether your device is recognizing 2 IMEIs in there or not.
Now flash the stock firmware and this time, you will be able to see both your IMEIs and baseband (you may or may not have network).
If you have got your network back, enjoy as you have your phone back to life, however if you do not have network, there is one more step.
Repeat step 2 and boot into TWRP and type this command:
Code:
adb push hw2.img /dev/block/mmcblk0p43
Once successfully pushed hw2.img, reboot and you will have your network back with both the sims working.
This will change your baseband so Volte won't work. I somehow got Volte working (I just don't know how).
If hw2.img doesn't work, try pushing hw3.img with the same commands. Good luck!
@edjalmo, after pusing hw2.img, you will still be missing your fingerprint as your device will be Moto G4 and not Moto G4 Plus, so you will have to push hw3.img to get your fingerprint back
Note: The above method which I have shown is working for Indian version of Moto G4/Plus (but now my baseband is changed to LATAM), and it may work or may not work on other versions, but you may try it. Before trying make sure that you have recovered your IMEIs by this method: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068

I seriously said a couple of times to backup the EFS. But yeah, keep ignoring the warnings and someday you'll fully brick the phone.

Heeth21 said:
@vinay lucy, you have converted your phone to Moto G4 (single sim variant).
Both of your IMEIs are restored but since your device thinks it has single sim, it just shows one IMEI.
Do not worry, there is a solution to this problem!
This was the method which worked for me, but unfortunately, my baseband got changed to LATAM, so if you are ready for it, then you may proceed.
1. Download these files and keep them in your adb directory: https://drive.google.com/open?id=1qpyZ8X4jKXg9puAp88aslNURgpYTuyE9
2. Flash or boot with official TWRP for the device located here: https://dl.twrp.me/athene/twrp-3.2.1-0-athene.img.html
If you want to flash TWRP (that means to replace your current recovery with TWRP), use this command:
Code:
fastboot flash recovery <recovery-name>.img
If you want to boot TWRP (that means be able to boot into TWRP without replacing your stock recovery), use this command:
Code:
fastboot boot <recovery-name>.img
3. Boot into TWRP, if you haven't already,connect your device to PC and type these commands:
Code:
adb push modem.img /dev/block/mmcblk0p1
adb push fsg.img /dev/block/mmcblk0p16
adb push hw.img /dev/block/mmcblk0p43
Note: If you are using any unofficial versions of TWRP, you will not be able to push the last file i.e hw.img as it will be stuck at 100% so use official TWRP only.
Now we have almost completed. Reboot your device and check if you are able to see IMEIs. At this point, your IMEIs and baseband will be unknown, but that doesn't matter, just check whether your device is recognizing 2 IMEIs in there or not.
Now flash the stock firmware and this time, you will be able to see both your IMEIs and baseband (you may or may not have network).
If you have got your network back, enjoy as you have your phone back to life, however if you do not have network, there is one more step.
Repeat step 2 and boot into TWRP and type this command:
Code:
adb push hw2.img /dev/block/mmcblk0p43
Once successfully pushed hw2.img, reboot and you will have your network back with both the sims working.
This will change your baseband so Volte won't work. I somehow got Volte working (I just don't know how).
If hw2.img doesn't work, try pushing hw3.img with the same commands. Good luck!
@edjalmo, after pusing hw2.img, you will still be missing your fingerprint as your device will be Moto G4 and not Moto G4 Plus, so you will have to push hw3.img to get your fingerprint back
Note: The above method which I have shown is working for Indian version of Moto G4/Plus (but now my baseband is changed to LATAM), and it may work or may not work on other versions, but you may try it. Before trying make sure that you have recovered your IMEIs by this method: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
Well, since you were able to restore your IMEIs back, would you mind pressing the thanks button in the thread of restoring IMEI (above link), it really took a lot of time and research to fix that issue!
Click to expand...
Click to collapse
HI i got both the sims imei now,
But im unable to get signal because the base band version is same still after flashing stock rom

Most likely you patched to the latest security patch before rooting/flashing PIE? (february security patch)
When you flashed the stock ROM it did not include the right modem because the february security patch changed the modem
I am in the process of restoring the same exact problem where adb can tell me my IMEI, but my phone shows IMEI=0
My theory is that if I backup the other Moto G4+ I have, same model number 1644.
I will just make a backup of this stock february patch after I install TWRP and then hope to install the backup onto the IMEI=0 G4+.
For you to do this you will likely have to find a backup of the 1640 on february patch stock or find someone who is willing to share the backup like you asked...
This happened on my galaxy 3 when i was just starting too and I fixed it by flashing the correct modem.
Im not sure if its just the modem or if its something else entirely so i will restore the entire backup rather than just the modem, but just to make sure this will not write any EFS info as long as Im using official TWRP? I wouldnt want 2 phones with the same EFS
I am just getting back into installing custom recovery, roms, kernels, etc on my phone so any more experienced users please let me know if I am wrong in thinking this will work.

dluds10 said:
Most likely you patched to the latest security patch before rooting/flashing PIE? (february security patch)
When you flashed the stock ROM it did not include the right modem because the february security patch changed the modem
I am in the process of restoring the same exact problem where adb can tell me my IMEI, but my phone shows IMEI=0
My theory is that if I backup the other Moto G4+ I have, same model number 1644.
I will just make a backup of this stock february patch after I install TWRP and then hope to install the backup onto the IMEI=0 G4+.
For you to do this you will likely have to find a backup of the 1640 on february patch stock or find someone who is willing to share the backup like you asked...
This happened on my galaxy 3 when i was just starting too and I fixed it by flashing the correct modem.
Im not sure if its just the modem or if its something else entirely so i will restore the entire backup rather than just the modem, but just to make sure this will not write any EFS info as long as Im using official TWRP? I wouldnt want 2 phones with the same EFS
I am just getting back into installing custom recovery, roms, kernels, etc on my phone so any more experienced users please let me know if I am wrong in thinking this will work.
Click to expand...
Click to collapse
No thats not the case. I tried this with April 2018 upate, April 2017 update and November 2016 update and the issue is on all the three firmwares. Android Pie is doing some changes with the persist partition and changing the permissions. I have made a specific thread about this issue which I too faced after reverting back to stock from Pie. Have a look at it over here: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
(P.S: I know I am posting this everywhere and in a way doing publicity so you may or may not hit the thanks button)

Now somehow i got both sims working
Thanks for suggestion. But Volte not working in JIO.

Did you try pushing hw2.img after getting both IMEIs??
Well I think it wouldn't work as the baseband has some problem. Moreover pushing hw, modem, fsg files too aren't the permenant solution and you will need to do them again if you flash stock ROM after getting signal back.
And can you tell if you noticed something different during the process other than what I mentioned?
Edit:
vinay lucy said:
Now somehow i got both sims working
Thanks for suggestion. But Volte not working in JIO.
Click to expand...
Click to collapse
Alright.....now the problem is resolved........Can you tell what was the last step did you do after which you got both the sims working?
Volte won't work as there is baseband mismatch. I somehow got Volte working (I just don't know how and I am now in LATAM baseband) and when trying to replicate the process which I did to get Volte working, it didn't work this time. So I am back with system restore. I tried using an earlier efs backup (with Indian baseband) and volte doesn't work.....
I just don't know why or how, so I am now sure that there's something in fsg, oem or system partition that is making Volte to work. Can you upload your build.prop so that we can check for some differences which hopefully can make volte work.

Heeth21 said:
Did you try pushing hw2.img after getting both IMEIs??
Well I think it wouldn't work as the baseband has some problem. Moreover pushing hw, modem, fsg files too aren't the permenant solution and you will need to do them again if you flash stock ROM after getting signal back.
And can you tell if you noticed something different during the process other than what I mentioned?
Click to expand...
Click to collapse
I flashed only hw img via abd and sims imei were restored and later flashed stock rom.
Both sims working now except volte Thanks mate

Either way it sounds very similar to my problem because it happened when i flashed stock rom after having Arrow OS. Have you tried ls -l partition? Mine is showing as a blank so maybe i full bricked it.
---------- Post added at 09:27 AM ---------- Previous post was at 09:27 AM ----------
good to hear, I will try next!

dluds10 said:
Either way it sounds very similar to my problem because it happened when i flashed stock rom after having Arrow OS. Have you tried ls -l partition? Mine is showing as a blank so maybe i full bricked it.
Click to expand...
Click to collapse
As I already mentioned, I had made a guide about fixing IMEI, so read it carefully.
The guide indeed mentions about "ls -l /partition" and not "ls -l partition", so you haven't completely bricked it yet just typed in wrong command......Also make sure to type "su" to gain root access.
---------- Post added at 05:32 PM ---------- Previous post was at 05:28 PM ----------
vinay lucy said:
I flashed only hw img via abd and sims imei were restored and later flashed stock rom.
Both sims working now except volte Thanks mate
Click to expand...
Click to collapse
That's exactly what is needed. But for some people, hw.img alone didn't work so hw2.img was required.
Please attach your build.prop so that we can compare it to see what's causing Volte problem.

Related

F320K F320L F320S no network problem after flashing original kdz

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 ....

Accidentally chose some other radio band!!!

I was trying to force 3G in my OP2 and used *#*#4636#*#* to enter testing menu.
Under that menu, I accidentally selected some other radio band and now one sim( SIM 2) is disabled(unable to find network).
I tried resetting phone to factory setting, but it didn't helped.
Also updated to latest OxygenOS 2.2.1, still one sim is disabled.
Please help....
thaaaanks
Flash OxygenOS Zip via Stock Recovery
---------- Post added at 09:37 AM ---------- Previous post was at 09:37 AM ----------
Before Flash Remember to Wipe All the Data
Hi,
My OnePlus 2 was running Exodus ROM, which had 2 Sim's: Vodafone (2G/3G) & other Jio (Only 4G/LTE).
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
*****
Clean flashed OOS 3.0.2 via TWRP, but SIM-Slot-2 = "No service| Vodafone".
I tried to manually search for networks,
It shows all the networks 2G & 3G in my city.
But connecting to Vodafone network from the list, always fails.
I think the latching (on to network) mechanism of SIM-slot 2, is faulty.
*****
Then clean flashed Exodus 29/8 build, but no fix.
Later, dirty flashed Exodus 31/8 build, which was supposed to flash the correct radio/modem/baseband on my OnePlus 2, but SIM-Slot-2, still doesn't let the SIM latch on to the network.
*****
Today, flashed "old-modem.zip" from benschhold, which resulted in phone stuck in boot loop.
Started OnePlus 2 Toolbox on PC, & flashed TWRP 2.8.7.0 via fastboot mode.
,successfully booted in TWRP 2.8.7.0 recovery.
flashed "new+modem.zip" (by benschhold).
Phone is working again, but SIM-Slot-2 = "No service| Vodafone".
@Spannaa @RajaMu @thegreatlex @Gonnelli1355
Will stock reset to OOS 3.0.2 from this link:
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
fix this SIM-Slot-2 / EFS / Modem problem ?
Also, while stock reset, can this happen without formatting the internal storage ?
As I have 35+ GB of pics/music/data, which will take a lot of time to backup !
osr.arora said:
@Spannaa @RajaMu @thegreatlex @Gonnelli1355
Will stock reset to OOS 3.0.2 from this link:
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
fix this SIM-Slot-2 / EFS / Modem problem ?
Also, while stock reset, can this happen without formatting the internal storage ?
As I have 35+ GB of pics/music/data, which will take a lot of time to backup !
Click to expand...
Click to collapse
Stock Reset to OOS 3.0.2 might fix your issue but it will completely wipe your phone so you'll need to backup anything you want to keep first.
Not sure why you wiped your EFS partitions without taking a backup first...
Spannaa said:
Stock Reset to OOS 3.0.2might fix your issue but it will completely wipe your phone so you'll need to backup anything you want to keep first.
Not sure why you wiped your EFS partitions without taking a backup first...
Click to expand...
Click to collapse
Thanks for replying back.
I'm downloading your fastboot.zip file (1.13 GB) right now (does the zip file also contain all steps, to flash correctly ?).
You mentioned in that post, that we can add REM command in .bat file to avoid format to data partition, can this be done with internal storage too ?
Also, I don't know what is EFS partition, & did not knew I had to back it up, before flashing custom ROM.
Anyways, can you tell, out of all the steps I did.
Which step actually made the SIM-Slot-2, to behave in this way ?
Was it, the "erase modemst1 & modemst2" in fastboot ?
Or
flashing new or old modem zip of benschhold ?
As at first step, selecting the band 40, only made the Vodafone SIM not work, but the both the SIM-slots were still working fine with Jio sim.
& Erasing modem st1 & st2, made both SIM-Slots stopped working.
& flashing new-modem.zip, actually made SIM-slot-1 work again (with both Vodafone & Jio),
Then why did this not work with SIM-Slot-2 ?
Logically, whatever made SIM-Slot-1 work, should also work for SIM-Slot-2 too (with slight modifications) ?
Will flashing a good/proper modem.zip make the sim-slot-2 work again ?
Rather than me, wiping my phone to OOS ?
What do you think ?
osr.arora said:
Thanks for replying back.
I'm downloading your fastboot.zip file (1.13 GB) right now (does the zip file also contain all steps, to flash correctly ?).
You mentioned in that post, that we can add REM command in .bat file to avoid format to data partition, can this be done with internal storage too ?
Also, I don't know what is EFS partition, & did not knew I had to back it up, before flashing custom ROM.
Anyways, can you tell, out of all the steps I did.
Which step actually made the SIM-Slot-2, to behave in this way ?
Was it, the "erase modemst1 & modemst2" in fastboot ?
Or
flashing new or old modem zip of benschhold ?
As at first step, selecting the band 40, only made the Vodafone SIM not work, but the both the SIM-slots were still working fine with Jio sim.
& Erasing modem st1 & st2, made both SIM-Slots stopped working.
& flashing new-modem.zip, actually made SIM-slot-1 work again (with both Vodafone & Jio),
Then why did this not work with SIM-Slot-2 ?
Logically, whatever made SIM-Slot-1 work, should also work for SIM-Slot-2 too (with slight modifications) ?
Will flashing a good/proper modem.zip make the sim-slot-2 work again ?
Rather than me, wiping my phone to OOS ?
What do you think ?
Click to expand...
Click to collapse
I don't think the fastboot zip will solve your problem as it only contains the rom and firmware. I'm not sure that even the Stock Reset to OOS 3.0.2 tool will either but it's worth a go.
Erasing modemst1 & modemst2 with fastboot is what's caused your problem but I'm not sure how to solve it.
Spannaa said:
Erasing modemst1 & modemst2 with fastboot is what's caused your problem but I'm not sure how to solve it.
Click to expand...
Click to collapse
I don't think he can fix that.
EFS has the information about the IMEI of a phone as far as I know.
No IMEI = No signal
A dual SIM phone has two IMEIs, and that probably explains why one is working after restoring one EFS...
iCapa said:
I don't think he can fix that.
EFS has the information about the IMEI of a phone as far as I know.
No IMEI = No signal
A dual SIM phone has two IMEIs, and that probably explains why one is working after restoring one EFS...
Click to expand...
Click to collapse
But I did not restore any EFS,
then how come IMEI 1, is working fine, even after erase command,
I checked IMEI 2 = 0.
& I checked a lot of OnePlus One forums. (OnePlus 2 has a lot less threads)
It's mentioned many times, that erasing modemst1 modemst2, does not erase the actual IMEI info from phone. (As it's stored in some other deep partitions).
Modemst1 modemst2, are supposed to rebuild themselves, after they are erased.
Correct me, if I'm wrong.
osr.arora said:
& I checked a lot of OnePlus One forums. (OnePlus 2 has a lot less threads)
It's mentioned many times, that erasing modemst1 modemst2, does not erase the actual IMEI info from phone. (As it's stored in some other deep partitions).
Modemst1 modemst2, are supposed to rebuild themselves, after they are erased.
Correct me, if I'm wrong.
Click to expand...
Click to collapse
On some devices they're rebuilt from a backup in the fsg partition but it looks like this doesn't work properly for SIM2 on the OP2.
I see you've posted this in a couple of threads in the OP forums too! Good luck - there are very few people over there that know what they're talking about so be careful before trying anything that anyone suggests.
Spannaa said:
Stock Reset to OOS 3.0.2might fix your issue but it will completely wipe your phone so you'll need to backup anything you want to keep first.
Not sure why you wiped your EFS partitions without taking a backup first...
Click to expand...
Click to collapse
@fareed_xtreme
Will appreciate your opinion on this issue,
Before I start the lengthy process of "backing up 45+GB data of my OP2, & stock reset it, by your method", in order to fix the IMEI#2=0 problem.
osr.arora said:
@fareed_xtreme
Will appreciate your opinion on this issue,
Before I start the lengthy process of "backing up 45+GB data of my OP2, & stock reset it, by your method", in order to fix the IMEI#2=0 problem.
Click to expand...
Click to collapse
Hi @osr.arora,
Unfortunately I do not think the stock reset will help you with this issue (as those partitions are not at all touched by the OnePlus Stock Reset), however I would strongly suggest you to take a backup and reset the device as a starting point.
Do you have a nandroid backup of your device (all partitions)? Even if it is an old one, try restoring them.
Sorry but I am out of ideas for getting this sorted.
fareed_xtreme said:
Hi @osr.arora,
Unfortunately I do not think the stock reset will help you with this issue (as those partitions are not at all touched by the OnePlus Stock Reset), however I would strongly suggest you to take a backup and reset the device as a starting point.
Do you have a nandroid backup of your device (all partitions)? Even if it is an old one, try restoring them.
Sorry but I am out of ideas for getting this sorted.
Click to expand...
Click to collapse
Should I use this:
http://m.youtube.com/watch?v=XODOYdSJuxg
to set my original IMEI (from Box) on SIM-Slot-2 ?
osr.arora said:
Should I use this:
http://m.youtube.com/watch?v=XODOYdSJuxg
to set my original IMEI (from Box) on SIM-Slot-2 ?
Click to expand...
Click to collapse
No, that's for the OnePlus One - you'll end up bricking your phone if you use tools built specifically for another device.
Spannaa said:
No, that's for the OnePlus One - you'll end up bricking your phone if you use tools built specifically for another device.
Click to expand...
Click to collapse
It also has option for OnePlus 2 (shown in video).
I haven't actually downloaded that software yet.
Can you recommend any other software, which allows writing IMEI !
osr.arora said:
It also has option for OnePlus 2 (shown in video).
I haven't actually downloaded that software yet.
Can you recommend any other software, which allows writing IMEI !
Click to expand...
Click to collapse
No, I'm not aware of any.
Looks like the tool you linked to costs $150 for the working version...
fareed_xtreme said:
Hi @osr.arora,
Unfortunately I do not think the stock reset will help you with this issue (as those partitions are not at all touched by the OnePlus Stock Reset), however I would strongly suggest you to take a backup and reset the device as a starting point.
Do you have a nandroid backup of your device (all partitions)? Even if it is an old one, try restoring them.
Sorry but I am out of ideas for getting this sorted.
Click to expand...
Click to collapse
Hi,
Could you provide me the email id of the developer team of OnePlus, from whom you obtained the Stock reset prcodeure & files.
You can PM me.
---------- Post added at 07:27 PM ---------- Previous post was at 07:24 PM ----------
Spannaa said:
On some devices they're rebuilt from a backup in the fsg partition but it looks like this doesn't work properly for SIM2 on the OP2.
I see you've posted this in a couple of threads in the OP forums too! Good luck - there are very few people over there that know what they're talking about so be careful before trying anything that anyone suggests.
Click to expand...
Click to collapse
Hi,
Could you tag the names of those few people, who have the actual know-how of technical issues.
LOL, I guess no one has solved this issue till now. Every thread regarding this issue on every site remains unanswered . I request the developers to try finding a solution to this problem. All the best ppl.
wrong radio band issue
Even I changed the band to band 40 however, I am getting the networks on both the Sim one being Jio and other being Vodafone. But the issue is I am not able to make calls from my vodafone number. There is no problem with incoming calls but out bound calls are not happening. JIO is working fine on both sim slots. Vodafone giving problem no matter if I switch the sim slots as well.

Baseband not found [XT1766 SPerry/Boost Mobile]

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

Moto G4 Plus SIMCARD No Signal

My Moto G4 Plus (XT1640) was on Stock Rom 7.0 everything working fine, so i got a OTA update, downloaded it and installed, at first it got bootloop so i forced it to power off (Power button and Volume minus) and rebooted it, but the Simcard doesnt get signal , only recognizes tells my sim number but no signal
I already tried everything, after the problems with the official 8.1 via OTA, i tried to downgrade to Stock Rom 7.0, unlocked bootloader , downgraded to 7.0 and it still doesnt get signal on Simcard and when i check the IMEI it was 0, so i installed TWRP and flashed Arrow OS 9.0 triyng to get IMEI and Simcard signal back, Clean flash i got my IMEI back but the Simcard doesnt get signal, recognizes but i cant do calls or use 4g keeps all the time "No Signal"
So i see installed "Stable Oreo 8.1 OPJ28.111-22" flashed it through TWRP and it is with the same problem no signal ... If anyone can help me pls message me or reply this, i need my phone to work!
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
What does your baseband report as, can you provide the full string (including the line after the .77R)?
Here's a similar thread with some possibly useful help. https://forum.xda-developers.com/moto-g4-plus/help/xt1640-service-update-to-8-1-t3926054 in particular https://forum.xda-developers.com/showpost.php?p=79437813&postcount=14
echo92 said:
What does your baseband report as, can you provide the full string (including the line after the .77R)?
Here's a similar thread with some possibly useful help. https://forum.xda-developers.com/moto-g4-plus/help/xt1640-service-update-to-8-1-t3926054 in particular https://forum.xda-developers.com/showpost.php?p=79437813&postcount=14
Click to expand...
Click to collapse
My Baseband is : M8952_70030.25.03.77R DLFT_FSG
fegama said:
My Baseband is : M8952_70030.25.03.77R DLFT_FSG
Click to expand...
Click to collapse
With that baseband, I'd try downloading the factory firmware (do not flash) and use the programutags.bat as I mentioned in the other post. See if that repairs your device.
shawgluz said:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
Click to expand...
Click to collapse
My IMEI is ok
https://imgur.com/a/OosRkjG
echo92 said:
With that baseband, I'd try downloading the factory firmware (do not flash) and use the programutags.bat as I mentioned in the other post. See if that repairs your device.
Click to expand...
Click to collapse
Ill try it now if it works ill reply here!
When i opened the .bat it shows it, it doesnt show my country that is Brazil what i do ?
1 - LATAM
2 - APAC
3 - Canada
4 - US
5 - EMEA
6 - Quit
Please select Region:
https://imgur.com/a/LWmKkdl
After i use the programutags.bat i got my signal back for some seconds and lost it another time and now it shows "Only Emergency Calls" i check my IMEI and as u can see on the screenshots, ive lost my IMEI, so i think thats because i lost my IMEI using this that my SIM isnt working, i already try my Sim in another device and it is Ok. What can i do to recover my IMEI ? I have a TWRP EFS Backup that i did on Arrow Os 9.0 with IMEI fine, but with the same problem of signal ... , I tried to flash TWRP and restore this backup,it shows sucessful but my IMEI wasnt back
fegama said:
https://imgur.com/a/LWmKkdl
After i use the programutags.bat i got my signal back for some seconds and lost it another time and now it shows "Only Emergency Calls" i check my IMEI and as u can see on the screenshots, ive lost my IMEI, so i think thats because i lost my IMEI using this that my SIM isnt working, i already try my Sim in another device and it is Ok. What can i do to recover my IMEI ? I have a TWRP EFS Backup that i did on Arrow Os 9.0 with IMEI fine, but with the same problem of signal ... , I tried to flash TWRP and restore this backup,it shows sucessful but my IMEI wasnt back
Click to expand...
Click to collapse
You may have lost your baseband downgrading back to Nougat, since you mentioned you had already updated to stock Nougat.
You could either fastboot flash the Oreo firmware or try this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
That script should have reprogrammed your hw partition and set the correct parameters for your radio, so I'm not sure what's happened to your baseband.
fegama said:
https://imgur.com/a/LWmKkdl
After i use the programutags.bat i got my signal back for some seconds and lost it another time and now it shows "Only Emergency Calls" i check my IMEI and as u can see on the screenshots, ive lost my IMEI, so i think thats because i lost my IMEI using this that my SIM isnt working, i already try my Sim in another device and it is Ok. What can i do to recover my IMEI ? I have a TWRP EFS Backup that i did on Arrow Os 9.0 with IMEI fine, but with the same problem of signal ... , I tried to flash TWRP and restore this backup,it shows sucessful but my IMEI wasnt back
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068 i did the proceedments with the terminal app and got my IMEI and signal back, but now i want to try to use Arrow Os 9.0 if i flash it through TWRP will i lose my IMEI and Simcard signal another time ?
fegama said:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068 i did the proceedments with the terminal app and got my IMEI and signal back, but now i want to try to use Arrow Os 9.0 if i flash it through TWRP will i lose my IMEI and Simcard signal another time ?
Click to expand...
Click to collapse
I honestly do not know - your best bet is to backup your EFS using Lyuu's TWRP as recommended in the Arrow OS thread. At least you'll have a copy of your modemst1/modemst2 that hopefully will restore your signal. Then flash ArrowOS and the relevant GApps.
You may lose signal if you revert back to stock firmware.
echo92 said:
I honestly do not know - your best bet is to backup your EFS using Lyuu's TWRP as recommended in the Arrow OS thread. At least you'll have a copy of your modemst1/modemst2 that hopefully will restore your signal. Then flash ArrowOS and the relevant GApps.
You may lose signal if you revert back to stock firmware.
Click to expand...
Click to collapse
Thank you! I already post an update, after two days searching for solutions i finally got it, but i am on Stock ROM 7.0 with ElementalGX Kernel and root that was the requirements https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068 of this post that i used with your help too, but i dont know if this Kernel is better than the stock kernel, Im interested in flashing Arrow Os 9.0, what do u think is better i stay on the stock 7.0 or flash it ?
fegama said:
Thank you! I already post an update, after two days searching for solutions i finally got it, but i am on Stock ROM 7.0 with ElementalGX Kernel and root that was the requirements https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068 of this post that i used with your help too, but i dont know if this Kernel is better than the stock kernel, Im interested in flashing Arrow Os 9.0, what do u think is better i stay on the stock 7.0 or flash it ?
Click to expand...
Click to collapse
Again, it's up to you. ElementalX is a good kernel, though it really depends on what you want from your device. If you want stability, then the stock ROM and ElementalX (or flashing the stock Oreo firmware and then ElementalX/loony) are your choices. If you want more customisation, then Arrow OS or another custom ROM are your options. It really is up to you.
echo92 said:
Again, it's up to you. ElementalX is a good kernel, though it really depends on what you want from your device. If you want stability, then the stock ROM and ElementalX (or flashing the stock Oreo firmware and then ElementalX/loony) are your choices. If you want more customisation, then Arrow OS or another custom ROM are your options. It really is up to you.
Click to expand...
Click to collapse
After all this trouble i think is better i stay on the Stock 7.0 with the ElementalX Kernel, i need my phone to work, so ill stay on the stock i spent like 2 days to find the solution lol

No Cell Service/Modem after flashing dump modem images H910. Advice requested.

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.

Categories

Resources