Database Users

IMEI showing up as zero, no sim cards work.

Hi, I'm receiving OTA updates, official software, oem locked. I had previously installed a lot of roms on this phone, rooted, etc, and once I flashed stock rom with moto g5 plus toolkit it killed my phone, or did it. It's pretty complex.
So right along the time this happened, I gave my imei to a verizon rep, he verified my phone was compatbile with verizon network, sent a verizon prepaid sim out (i'm switching to 40 plan from redpocket to verizon prepaid) the sim is still in the mail. Along this time I also was on lineage os from vache, 8.1 But I didn't like it so I reflashed stock rom with moto g5 plus toolkit, (google it)
So. it was PRECISELY after I re-flashed stock rom that no sim card worked. I immediately assumed it was verizon's fault, they must have locked my phone to their network, right? But then I dialed *#06# on my dialer and my IMEI showed up as ZERO. I talked in android discord, and was told I must have deleted EFS whatever that is.
So, I'm stuck. I have an imei that's zero, no sim card will work on this phone, i'm oem locked and receiving ota updates and official software status via fastboot. android security patch november 1, 2017 and build number = npn25.137-92
I did call Verizon to make sure they weren't causing the issue, but the rep was confused. My phone was showing up as an x1 or something on his screen, but he said I "can't use any other carriers/sims" until i "activate the verizon sim they shipped me" but then this information was falsified by the verizon folks at reddit, who said the rep didn't know what he was talking about.
So I'm thinking this issue is being caused by the stock rom I flashed, NOT verizon. Let me know, I was previously on Redpocket.
Either way, no sim will work right now, I called motorola support, they said they can only send me a new phone for $150, as flashing rom voids warranty, so my phone is essentially a wifi only device without cellular capabilities.
I am stumped as what to do. this is US NA moto g5 plus, again, official software status, oem locked. If someone could help me get my celullar back and identify WHAT CAUSED THIS, I would be eternally grateful. Again, I didn't do anything but erase everything in TWRP (data, cache, etc) and REFLASH stock rom, downloaded from moto g5 plus toolkit link. So HOW could I have deleted my EFS folder? It just doesn't make sense. So I'm debating after all, maybe it is Verizon messing up my phone?

beatlesfan5858 said:
Hi, I'm receiving OTA updates, official software, oem locked. I had previously installed a lot of roms on this phone, rooted, etc, and once I flashed stock rom with moto g5 plus toolkit it killed my phone, or did it. It's pretty complex.
So right along the time this happened, I gave my imei to a verizon rep, he verified my phone was compatbile with verizon network, sent a verizon prepaid sim out (i'm switching to 40 plan from redpocket to verizon prepaid) the sim is still in the mail. Along this time I also was on lineage os from vache, 8.1 But I didn't like it so I reflashed stock rom with moto g5 plus toolkit, (google it)
So. it was PRECISELY after I re-flashed stock rom that no sim card worked. I immediately assumed it was verizon's fault, they must have locked my phone to their network, right? But then I dialed *#06# on my dialer and my IMEI showed up as ZERO. I talked in android discord, and was told I must have deleted EFS whatever that is.
So, I'm stuck. I have an imei that's zero, no sim card will work on this phone, i'm oem locked and receiving ota updates and official software status via fastboot. android security patch november 1, 2017 and build number = npn25.137-92
I did call Verizon to make sure they weren't causing the issue, but the rep was confused. My phone was showing up as an x1 or something on his screen, but he said I "can't use any other carriers/sims" until i "activate the verizon sim they shipped me" but then this information was falsified by the verizon folks at reddit, who said the rep didn't know what he was talking about.
So I'm thinking this issue is being caused by the stock rom I flashed, NOT verizon. Let me know, I was previously on Redpocket.
Either way, no sim will work right now, I called motorola support, they said they can only send me a new phone for $150, as flashing rom voids warranty, so my phone is essentially a wifi only device without cellular capabilities.
I am stumped as what to do. this is US NA moto g5 plus, again, official software status, oem locked. If someone could help me get my celullar back and identify WHAT CAUSED THIS, I would be eternally grateful. Again, I didn't do anything but erase everything in TWRP (data, cache, etc) and REFLASH stock rom, downloaded from moto g5 plus toolkit link. So HOW could I have deleted my EFS folder? It just doesn't make sense. So I'm debating after all, maybe it is Verizon messing up my phone?
Click to expand...
Click to collapse
bro never use toolkit again to flash stock use fastboot instead there is no problem with your device now what you will do is unlock your bootloader with the code u received from moto and after that wipe everything in twrp check if in bootloader your baseband is showing some version then if it shows no problem now flash any 64bit oreo custom rom nos,validus,pe ur wish then reboot to bootloader now type the commands fastboot erase modemst1 ,fastboot erase modemst2 then boot into custom rom you installed now you will have signal,then again boot into twrp recovery and backup efs and store it on pc or cloud ur choice, now you can use any custom rom with signal without any hassle and if you want to move to stock while flashing stock rom skip fastboot erase modemst1 ,fastboot erase modemst2 commands you boot into rom it should have signal if you dont get signal flash twrp then restore your oreo efs backup you will surely get back your signal but no volte sadly for now.
after stock oreo release flash it may be everything will be normal again.
i wish you good luck.

Rakesh1b said:
bro never use toolkit again to flash stock use fastboot instead there is no problem with your device now what you will do is unlock your bootloader with the code u received from moto and after that wipe everything in twrp check if in bootloader your baseband is showing some version then if it shows no problem now flash any 64bit oreo custom rom nos,validus,pe ur wish then reboot to bootloader now type the commands fastboot erase modemst1 ,fastboot erase modemst2 then boot into custom rom you installed now you will have signal,then again boot into twrp recovery and backup efs and store it on pc or cloud ur choice, now you can use any custom rom with signal without any hassle and if you want to move to stock while flashing stock rom skip fastboot erase modemst1 ,fastboot erase modemst2 commands you boot into rom it should have signal if you dont get signal flash twrp then restore your oreo efs backup you will surely get back your signal but no volte sadly for now.
after stock oreo release flash it may be everything will be normal again.
i wish you good luck.
Click to expand...
Click to collapse
Thanks so much for replying I will try exactly everything you said

beatlesfan5858 said:
Thanks so much for replying I will try exactly everything you said
Click to expand...
Click to collapse
bro 1 advice dont ever use toolkit to flash stock use fastboot its the best secure way.

Rakesh1b said:
bro 1 advice dont ever use toolkit to flash stock use fastboot its the best secure way.
Click to expand...
Click to collapse
Hi which rom would you recommend? i try downloading validus and pixel experience, but the zip files extract to cpgz files, I can't get the actual files. I need flashable rom

beatlesfan5858 said:
Hi which rom would you recommend? i try downloading validus and pixel experience, but the zip files extract to cpgz files, I can't get the actual files. I need flashable rom
Click to expand...
Click to collapse
i will give u the link
---------- Post added at 04:22 AM ---------- Previous post was at 04:16 AM ----------
Rakesh1b said:
i will give u the link
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=746010030569952670
---------- Post added at 04:23 AM ---------- Previous post was at 04:22 AM ----------
Rakesh1b said:
i will give u the link
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=746010030569952670

thank you Rakesh, I'm downloading it now, I will update you to let you know if it works. I just want my phone back

what are instructions to flash this rom?

beatlesfan5858 said:
what are instructions to flash this rom?
Click to expand...
Click to collapse
bro just flash that rom then boot into bootloader then type these 2 fastboot commands and enter after every command
fastboot erase modemst1
fastboot erase modemst2
then boot into custom oreo you will have your imei back now you will have imei with any custom rom but if you want to go to stock then backup your efs from twrp menu and store the files inside your backup folder on potter that shows up in your computer when connected to pc it will have a folder with z******** some serial no and in it you will have 4 files but save only 3 files leave recovery log file and save them to pc and now you can fastboot flash stock rom now what the problem here is it cant detect imei on nougat stock so after flashing fastboot rom you flash twrp recovery and then backup efs then it will create a folder efs backup on you potter then move the previous 3 efs backup files to the backup directory where there will be 4 files same as before and now restoree that backup and you can boot into stock rom it will have imei.

I figured it out thanks.

beatlesfan5858 said:
I don't know how to flash the rom bro I just got a bunch of files, I have fastboot
Click to expand...
Click to collapse
follow this guide bro if you want to fastboot flash stock rom https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738

Rakesh1b said:
follow this guide bro if you want to fastboot flash stock rom https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
Click to expand...
Click to collapse
I'm trying to flash the validus zip you gave. I put it on an sd card and tried flashing it with twrp but it gave me error code 255

beatlesfan5858 said:
I'm trying to flash the validus zip you gave. I put it on an sd card and tried flashing it with twrp but it gave me error code 255
Click to expand...
Click to collapse
bro first wipe everything off your potter if you dont have any important data on it i mean clean flash take out your sd card and now select advanced wipe>select all options>wipe one by one
format potter using format option now copy validus zip to your potter internal storage it will show up when connected to pc then select installl in twrp then swipe to flash it should flash well then wipe dalvik cache then boot to bpootloader try those 2 commands then you boot to rom it will have signal bro. try it

Bro I did exactly what you said, copied Validus zip to internal, removed sd card and erased everything in twrp. It's still giving me error code 255 when I try to flash the Validus zip.

beatlesfan5858 said:
Bro I did exactly what you said, copied Validus zip to internal, removed sd card and erased everything in twrp. It's still giving me error code 255 when I try to flash the Validus zip.
Click to expand...
Click to collapse
bro wipe everything of ur device and try format then factory reset and then reboot to recovery again then try to flash the rom again
---------- Post added at 05:01 AM ---------- Previous post was at 04:58 AM ----------
Rakesh1b said:
bro wipe everything of ur device and try format then factory reset and then reboot to recovery again then try to flash the rom again
Click to expand...
Click to collapse
try this twrp it need s64bit supported twrp to flash that rom try this twrp flash this recovery then format then try to flash https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html
---------- Post added at 05:02 AM ---------- Previous post was at 05:01 AM ----------
Rakesh1b said:
bro wipe everything of ur device and try format then factory reset and then reboot to recovery again then try to flash the rom again
Click to expand...
Click to collapse
try this twrp it need s64bit supported twrp to flash that rom try this twrp flash this recovery then format then try to flash https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html

Thanks bro, much love, that was it. I can finally flash the rom. I'll flash it, and then try your next steps to get signal. Thanks again I really appreciate it.

What's the best way to backup EFS?

beatlesfan5858 said:
Thanks bro, much love, that was it. I can finally flash the rom. I'll flash it, and then try your next steps to get signal. Thanks again I really appreciate it.
Click to expand...
Click to collapse
good luck. stay safe with efs always.

Rakesh1b said:
good luck. stay safe with efs always.
Click to expand...
Click to collapse
I got signal much love bro, you really saved my day!

Rakesh1b said:
good luck. stay safe with efs always.
Click to expand...
Click to collapse
boot into oreo rom once you have signal then go to twrp then>backup >swpie to backup>it will save 4 backup files in internal memory twrp backup folder copy that whole folder and keep it safe when ever you loose signal just backupefs again in new rom then it will create backup folder then replace that backup folder with this oreo efs backup you can get back signa then.
is it working now having signal?
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Rakesh1b said:
boot into oreo rom once you have signal then go to twrp then>backup >swpie to backup>it will save 4 backup files in internal memory twrp backup folder copy that whole folder and keep it safe when ever you loose signal just backupefs again in new rom then it will create backup folder then replace that backup folder with this oreo efs backup you can get back signa then.
is it working now having signal?
Click to expand...
Click to collapse
once oreorom stock comes you willbe good to go and everything will be normal.

Downgrading to stock from 8.1

Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: [url]http://xda.tv/post75619905[/URL]
Please delete the EFS file, restoring another phone's EFS is illegal, sorry.

i lost my voLTE after flashing twrp based stock rom ( nov patch) on pixel experience feb build... now i cant use my jio sim for calls ... No VoLTE support...
if you have a backup of your EFS , can you please send me the file...

sir,what is your baseband version when the volte is working.?(if your current rom has volte working then what is your current baseband version.?)

IMEI shows 0 again after Restore your EFS file

Restore his efs file after flashing pixel experince 8.1,
Just go into twrp,
Flash pixel experince 8.1
And afther that restore his efs partition from twrp .
You will able to get your imei back,
But problem is after doing this way I still not able to get volte.

M8953_02.03.07.08r

Can you tell us what version of baseband do you see when you enter in boot loder.?
Because in my boot loder I see M8953_02.03.07.08U.

thedr34m13 said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser:
Click to expand...
Click to collapse
Persist backup may help to get volte back..please share if you can

yes,can you share the whole backup of pixel experience rom 8.1 (with volte working),by restoring that backup i think we may able to get volte.

i found this really helpful on another post,
what i did was deleting these files
fastboot erase modemst1
fastboot erase modemst2
from the fastboot comands before flashing back to stock
that works perfectly for me and i got back my signal &4glte.

Baseband: Not found/Unknown, imei 0... Let's find a definitive solution

XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.

I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try

mohitzr said:
I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try
Click to expand...
Click to collapse
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.

barbaroja said:
XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.
Click to expand...
Click to collapse
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.

barbaroja said:
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.
Click to expand...
Click to collapse
i get baseband

[email protected] said:
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.
Click to expand...
Click to collapse
Thanks for sharing. Very interesting, indeed.
In my particular case, it happened for no apparent reason. Quick reboots being a suspect here. It seems some got baseband and no imei, others no baseband at all... Any ideas on this?

dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img

rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?

akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
This a dump of an untouched XT1686 92-8 firmware.

rachitrawat said:
This a dump of an untouched XT1686 92-8 firmware.
Click to expand...
Click to collapse
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.

akshu2697 said:
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.
Click to expand...
Click to collapse
There isn't one as there is no 92-8 firmware out there.
Sent from my Moto G5 Plus using XDA Labs

did it worked ? .. im having the same problem .. cant get my network signal and imei
akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?

Repiix said:
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?
Click to expand...
Click to collapse
I haven't tried it yet,
I will tell you if this work.

rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.

1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....

I'm on an oreo rom(no volte). Will i be able to flash stock when the oreo rom is officially released? And hopefully get volte?

Arunxyz said:
1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....
Click to expand...
Click to collapse
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??

akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system

Arunxyz said:
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system
Click to expand...
Click to collapse
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.

akshu2697 said:
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.
Click to expand...
Click to collapse
Code:
fastboot flash modem NON-HLOS.bin
akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
system.img is a bit perfect backup of /system which will not break dm-verity.
akshu2697 said:
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.
Click to expand...
Click to collapse
you can restore via twrp or fastboot flash
Edit: fastboot won't work. Need to compress into sparse chunks. Try motofastboot

Possible fix for IMEI 0 after OTA update?

Like many people who have lost IMEI after flashing Oreo ROM and reverting to stock, I too have run into the same issue. I've managed to get my IMEI back and now have a working EFS backup. I've also got my VoLTE fixed using the VoLTE fix thread.
The problem I'm running into now is that the OTA updates from motorola keep breaking my IMEI. So every time I install an OTA, my IMEI becomes 0 afterwards. I then have to install TWRP and restore my EFS+persist backup to get my IMEI back. But this essentially prevents me from installing the next OTA update.
Has anyone found a way to install the OTA update without losing IMEI? Any help would be much appreciated!
I've thought of possible solution but I'm not sure if it will work. If someone could tell me if this will work, that would be great!
1. Using Partition Backup app from playstore, backup Modem, Modemst1, Modemst2 and persist on working stock ROM
2. Do a fresh install of stock ROM via fastboot and install OTA
3. Use Magisk to patch boot image and flash the image from fastboot
4. Re install Partition Backup from playstore, grant root access and restore the partition backup to get IMEI back?
This way you can restore the stock boot image and install next OTA all without installing and decrypting your storage with twrp.

PLEASE
please share the EFS folder:good::good:

Another users EFS paritition won't help you and sharing is not allowed on XDA, this has been addressed multiple times since there are over a dozen threads about the the same damn thing.
THE REAL FIX:
Accept that you made a mistake cause you didn't keep a secure backup of your original firmware, and let it be a learning experience in the future. Some users are in worst situations following some of these half-cocked fixes.

Randumb_User said:
Another users EFS paritition won't help you and sharing is not allowed on XDA, this has been addressed multiple times since there are over a dozen threads about the the same damn thing.
THE REAL FIX:
Accept that you made a mistake cause you didn't keep a secure backup of your original firmware, and let it be a learning experience in the future. Some users are in worst situations following some of these half-cocked fixes.
Click to expand...
Click to collapse
No....we did not make mistakes actually. Many things have been borked by Oreo development, I did nothing to lose my Imei other than flash 64bit Roms, keeping a secure backup of stock firmware would not restore your imei, if so, so would flashing via fastboot your original stock firmware.

Ok so I've been analyzing the app "Partition Backup" on the play store and it seems that you can also flash your backed up partition through fastboot. So if you back up those partitions, you can restore them through fastboot even without the app (As long as you backup the partition in the .img format). I haven't tried any of this yet so I'm not sure if it will work.

smartish123 said:
Ok so I've been analyzing the app "Partition Backup" on the play store and it seems that you can also flash your backed up partition through fastboot. So if you back up those partitions, you can restore them through fastboot even without the app (As long as you backup the partition in the .img format). I haven't tried any of this yet so I'm not sure if it will work.
Click to expand...
Click to collapse
Best way to back up partitions is to use ADB
Code:
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
which will give you a list of all partitions by name and their starting addresses. Then ADB shell and dd command, for instance for persist
Code:
dd if=/dev/block/mmcblk0p30 of=/external_sd/persist.img
This backs up that partition to your external sd card. To restore/write it
Code:
dd if=/external_sd/persist.img of=/dev/block/mmcblk0p30
Of course you would do this for each partition you want to back up.

[email protected] said:
Best way to back up partitions is to use ADB
Code:
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
which will give you a list of all partitions by name and their starting addresses. Then ADB shell and dd command, for instance for persist
Code:
dd if=/dev/block/mmcblk0p30 of=/external_sd/persist.img
This backs up that partition to your external sd card. To restore/write it
Code:
dd if=/external_sd/persist.img of=/dev/block/mmcblk0p30
Of course you would do this for each partition you want to back up.
Click to expand...
Click to collapse
Do you need to have root installed to run those commands through adb? What I'm planning on doing is to unroot my device and go to pure stock. I want to be able to restore my modem partitions when I install an OTA (which will probably break my IMEI).
UPDATE
I tried flashing the backed up image of modemst1 i got from the app through fastboot. It failed saying "flash permission denied"
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
target reported max download size of 536870912 bytes
sending 'modemst1' (2048 KB)...
OKAY [ 0.076s]
writing 'modemst1'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.101s

How to get back imie...??? Please help

madhu kumaraaa said:
How to get back imie...??? Please help
Click to expand...
Click to collapse
Try this thread
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808

Try this.
1-Pixel Experience workaround (Flash PE, don't turn on wifi, get to home screen, reboot to bootloader, run fastboot erase modemst1 and fastboot modemst2, let phone reboot, confirm network.)
2-Lock Bootloader (If the last OTA you got was 9x-8 you're in a tight spot til firmware is available. If it was -4, you're good.)
3-Flash Full Firmware (but not fastboot erase modemst1 and modemst1. Keep as-is)
4-Install and Flash OTA
I can make absolutely no promises it will work for you. But I was dealing with IMEI 0, and now my bootloader is locked, on Stock, OTA installed with IMEI. I've had the phone return IMEI 0 after OTA updates before this. I can't confirm LTE/voLTE connectivity, not much data in the first place cause I don't need it.
If it doesn't work. Try again but do this first. I dunno if it's redundant or not. I can't test further and I'm leaving this phone alone now.
--When I was messing with my phone while doing this. I ****ed up the first time and only did 1- and 3-. I ran the above steps after phone as on the home screen and not enabling wifi
For reference. I don't have an EFS backup and I never messed with persist.

Randumb_User said:
Try this.
1-Pixel Experience workaround (Flash PE, don't turn on wifi, get to home screen, reboot to bootloader, run fastboot erase modemst1 and fastboot modemst2, let phone reboot, confirm network.)
2-Lock Bootloader (If the last OTA you got was 9x-8 you're in a tight spot til firmware is available. If it was -4, you're good.)
3-Flash Full Firmware (but not fastboot erase modemst1 and modemst1. Keep as-is)
4-Install and Flash OTA
I can make absolutely no promises it will work for you. But I was dealing with IMEI 0, and now my bootloader is locked, on Stock, OTA installed with IMEI. I've had the phone return IMEI 0 after OTA updates before this. I can't confirm LTE/voLTE connectivity, not much data in the first place cause I don't need it.
If it doesn't work. Try again but do this first. I dunno if it's redundant or not. I can't test further and I'm leaving this phone alone now.
--When I was messing with my phone while doing this. I ****ed up the first time and only did 1- and 3-. I ran the above steps after phone as on the home screen and not enabling wifi
For reference. I don't have an EFS backup and I never messed with persist.
Click to expand...
Click to collapse
So just to clarify (I understand that this may not work for me):
After following the above steps, you were able to have a working IMEI and you were able to install an OTA update without having your IMEI go to 0 correct?
Also on step 4, when you say "Install and Flash OTA" do you mean you proceed to install the OTA normally (as in you click the install button in Stock and your phone reboots and installs it)?

smartish123 said:
So just to clarify (I understand that this may not work for me):
After following the above steps, you were able to have a working IMEI and you were able to install an OTA update without having your IMEI go to 0 correct?
Also on step 4, when you say "Install and Flash OTA" do you mean you proceed to install the OTA normally (as in you click the install button in Stock and your phone reboots and installs it)?
Click to expand...
Click to collapse
Correct and correct, I'm a ****show when it comes to explaining things.
I'm still not sure what's gonna happen after a factory reset. The reluctance is overwhelming.

Did anyone else have any luck?
If anyone manages to get thier IMEI at any point I'd suggest Unlocking/TWRP to make an EFS backup. First thing I did after rooting again. Then I got stuck on the logo, had to flash 93-4 and....IMEI 0. EFS backup worked proper and restored it just fine. I could wipe data in TWRP without losing IMEI.
Gonna avoid custom ROMs. Stick with Stock+ElementalX+Magisk.
What a fun device....
Here's some probable good news: https://www.xda-developers.com/google-require-oem-regular-security-patches/

Randumb_User said:
Did anyone else have any luck?
If anyone manages to get thier IMEI at any point I'd suggest Unlocking/TWRP to make an EFS backup. First thing I did after rooting again. Then I got stuck on the logo, had to flash 93-4 and....IMEI 0. EFS backup worked proper and restored it just fine. I could wipe data in TWRP without losing IMEI.
Gonna avoid custom ROMs. Stick with Stock+ElementalX+Magisk.
What a fun device....
Here's some probable good news: https://www.xda-developers.com/google-require-oem-regular-security-patches/
Click to expand...
Click to collapse
Yea as of now, no one has been able to figure out how to apply OTA without losing imei. However someone has managed to figure out how to apply an OTA using the firmware files without losing imei.
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808/post76468866
The only drawback with this method is that you need have the firmware zip of the OTA.

smartish123 said:
Yea as of now, no one has been able to figure out how to apply OTA without losing imei. However someone has managed to figure out how to apply an OTA using the firmware files without losing imei.
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808/post76468866
The only drawback with this method is that you need have the firmware zip of the OTA.
Click to expand...
Click to collapse
I have used OTA to update to 93-8 and the other day 93-10 (For XT1687 retus) without losing IMEI, it's an anomaly to me. Prior to that I was dealing with the same OTA updates reverting back to IMEI 0. I'm not trying to gloat or anything, I've been hoping at least one person managed the same outcome. It's a really $h!t situation for a lot of people.

Randumb_User said:
I have used OTA to update to 93-8 and the other day 93-10 (For XT1687 retus) without losing IMEI, it's an anomaly to me. Prior to that I was dealing with the same OTA updates reverting back to IMEI 0. I'm not trying to gloat or anything, I've been hoping at least one person managed the same outcome. It's a really $h!t situation for a lot of people.
Click to expand...
Click to collapse
What sucks so much is how random things are with this device. For example, a month ago I fastbooted one of the firmwares and my imei was there(was 0 before flashing). After that flashing an Oreo rom, my imei was 0. Going back and repeating the process, flashing same firmware, imei 0 still?????. So damn random. If only we had a safe way to manually insert our imei. Let's just hope the problems do not multiply when we get 32bit official Oreo .

Cupcake 1.5 said:
What sucks so much is how random things are with this device. For example, a month ago I fastbooted one of the firmwares and my imei was there(was 0 before flashing). After that flashing an Oreo rom, my imei was 0. Going back and repeating the process, flashing same firmware, imei 0 still?????. So damn random. If only we had a safe way to manually insert our imei. Let's just hope the problems do not multiply when we get 32bit official Oreo .
Click to expand...
Click to collapse
I've been doing a lot of thinking and I came up with this idea on how to install OTA safely without losing imei.
Essentially, the main goal is to be able to install the OTA and then restore a backup of your modemst1 and modemst2 partitions. You need to be able to do this without installing TWRP, since it will decrypt your data partition. The only way I can think of doing this is through backing up and restoring your modemst1 and modemst2 partitions through ADB, which unfortunately requires root. Using some logic, we can see that in order to do this you need to preserve root without installing it through TWRP. I'm proposing that if you can use magisk manager (the apk one) and use it create a patched boot.img (which can be obtained via any firmware zip) with root access , you can flash this patched boot.img in fastboot and obtain root access WITHOUT having to use TWRP. So whenever you install an OTA, you can restore the original boot.img through fastboot, install the OTA, restore patched boot.img, and use root access to restore modemst1 and modemst2 backups via ADB.
UPDATE
I came up with a better idea. It seems it is possible to boot into twrp without having to flash it on your phone via
fastboot boot twrp.img
If this works, you can restore an EFS backup everytime you install an OTA since your stock recovery remains intact.
I haven't tried any of this yet. It would be amazing if you guys could give me your opinions about this. I'd be happy to clarify any of this for you guys.

My G5 Plus was stolen and it's now someone's problem other than mine. Good luck to them. I've inherited a OnePlus X.
Farewell folks.

smartish123 said:
UPDATE
I came up with a better idea. It seems it is possible to boot into twrp without having to flash it on your phone via
fastboot boot twrp.img
If this works, you can restore an EFS backup everytime you install an OTA since your stock recovery remains intact.
I haven't tried any of this yet. It would be amazing if you guys could give me your opinions about this. I'd be happy to clarify any of this for you guys.
Click to expand...
Click to collapse
This doesn't work, I just tried it. You can of course restore EFS this way but the next OTA will not work, you get the "Error!" message.

fivefour said:
This doesn't work, I just tried it. You can of course restore EFS this way but the next OTA will not work, you get the "Error!" message.
Click to expand...
Click to collapse
Drat. This means that whatever efs we are using to recover our imei is tampered. I don't know how to fix that.

How to recovery 4G on Moto G5

Hi, I created this thread because I have solved the problem of the 4g at the time of losing my "moto g5 imei".
Just installed the "dotos rom v2. 2" 06/05/2018, I went into the bootloader, did the respective backup (currently at H +), and entered modem commands in fastboot mode, all this with the 64 twrp, say because I have read that he has to go to twrp's 32 " , but no, I didn't do it, well, at the time of start the rom again because you will have 4 g, well that was my case, I don't know if it will work with some of you, perhaps to serve them, my specific model is the xt1670.
Anyway here are the steps:
1 -- Get a backup of the file "EFS" (currently with H +), to me only appears me with the 64-bit TWRP '
2 -- Install the rom "dotOS v2.2 - 20180506 ", if you don't have any rom with android 8.1, install first the TWRP 64 and then the rom "dotos".
3 -- Once installed restart mobile to bootloader, and do not change anything.
4 -- Just enter via adb fastboot commands:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5 -- Will restart automatically, and you will already have the 4 g network.
6 -- Finally performs a backup of the file "EFS" 4g.
POSSIBLE PROBLEM...
Lack say something, possibly the "imei sv" is set to 0, the solution for me was after having keep the new file efs with 4 g, I installed the "moto g5 official rom (android 7.0)", with full commands, including modems, obviously we will lose the imei, but because we have our file efs 4g, we will restore it, we go back to bootloader mode, install again the 64 twrp, we also install the file "no verity opt encrypt 6.0", then, we return to the main menu of the twrp and restore, and choose the file that we have recovered the EFS 4 g, and " ready, we have a imei, imei sv, and 4 g correctly, upon restart, if you like you make another backup of the definitive efs file, and ready, now if you want to go back to the stock rom, already not to enter modem commands, thats all.
PD: Sorry for my english, I used a translator for this... And sorry for the links, xda will not allow me...
{
"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"
}

How i get backup of EFS file ?

Thanks for the tutorial, it has served me many gracais since I was 4 months in 3g. just follow the letter

Kindred403 said:
How i get backup of EFS file ?
Click to expand...
Click to collapse
Sorry for the delay in responding, you can only get the EFS file from the recovery Cedric TWRP 64 bits, that is very important, and being in the Backup menu, select the EFS file.

Finally my 4G is back! Thank you very much!

If I update after doing this, will I lose IMEI and have to flash stock again?

ap4ss3rby said:
If I update after doing this, will I lose IMEI and have to flash stock again?
Click to expand...
Click to collapse
No, not at all, just ignore the modem commands, and if you mean to install custom ROMs, will go normal, no errors

sashUser_2 said:
Hi, I created this thread because I have solved the problem of the 4g at the time of losing my "moto g5 imei".
Just installed the "dotos rom v2. 2" 06/05/2018, I went into the bootloader, did the respective backup (currently at H +), and entered modem commands in fastboot mode, all this with the 64 twrp, say because I have read that he has to go to twrp's 32 " , but no, I didn't do it, well, at the time of start the rom again because you will have 4 g, well that was my case, I don't know if it will work with some of you, perhaps to serve them, my specific model is the xt1670.
Anyway here are the steps:
1 -- Get a backup of the file "EFS" (currently with H +), to me only appears me with the 64-bit TWRP '
2 -- Install the rom "dotOS v2.2 - 20180506 ", if you don't have any rom with android 8.1, install first the TWRP 64 and then the rom "dotos".
3 -- Once installed restart mobile to bootloader, and do not change anything.
4 -- Just enter via adb fastboot commands:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5 -- Will restart automatically, and you will already have the 4 g network.
6 -- Finally performs a backup of the file "EFS" 4g.
POSSIBLE PROBLEM...
Lack say something, possibly the "imei sv" is set to 0, the solution for me was after having keep the new file efs with 4 g, I installed the "moto g5 official rom (android 7.0)", with full commands, including modems, obviously we will lose the imei, but because we have our file efs 4g, we will restore it, we go back to bootloader mode, install again the 64 twrp, we also install the file "no verity opt encrypt 6.0", then, we return to the main menu of the twrp and restore, and choose the file that we have recovered the EFS 4 g, and " ready, we have a imei, imei sv, and 4 g correctly, upon restart, if you like you make another backup of the definitive efs file, and ready, now if you want to go back to the stock rom, already not to enter modem commands, thats all.
PD: Sorry for my english, I used a translator for this... And sorry for the links, xda will not allow me...
Click to expand...
Click to collapse
Please make a video of it ?

I don't know why you keep saying you have to install dotos to do this? Worked on atomic os.
After doing the fastboot commands the IMEI went to 0 but then after restore the EFS it came back to normal....
I can't say if 4g is back because where I am I had never got 4g before.. I'll have to travel somewhere to see if 4g is back!
Seems possible that 4g is back now! Thanks! ?

Sadly this didn't fix my 4g not working issue ?

This worked perfectly, and I was just thinking about buying another phone. Thanks a lot!

where do we have to take backup of efs. stock rom or dotOS rom ??

Varun Maheshwari said:
where do we have to take backup of efs. stock rom or dotOS rom ??
Click to expand...
Click to collapse
First things first, you gotta be sure you are on stock rom AND have 3G signal. If you don't, flash the latest Pixel Experience so you get IMEI and 3G back (may need to reboot phone twice, I did). After that, you have to flash back stock rom via fastboot mode so make sure you enabled USB debugging (I'm assuming you already know that), but don't run the commands 'fastboot erase modemst1' and 'fastboot erase modemst2'. If you run these, you'll have to start all over. Once you're all set, backup EFS partition using TWRP 3.2.1-0 (64bit version linked above), save it somewhere safe, install dotOS rom (I used the exact version the tutorial suggests, so I would just stick with that), reboot to system (again, you may have to reboot it twice) and you should have 4G/LTE signal. Now create a new EFS backup, save it somewhere safe, and reinstall stock ROM, but this time including those two commands (I installed the latest version with July 2018 security patch). After that, reinstall TWRP 64bits, restore the EFS backup you created while on dotOS and you're done. On First boot you may face some problems while trying to use 4G, it may keep switching between 4G and 3G all the time making it impossible to connect, but should it happen to you, a simple reboot fixes the issue. If you wish to root your phone after the process (like I did for PoGO spoofing) just install 32bit TWRP 3.2.2-0 and flash Magisk 16.7 beta and reboot phone twice (First time may have 4G issue again, rebooting fixes it). Sorry for the late response, it's way past midnight here in Brazil. Hope you get It working again

I finally got my 4g back after a long time thanks brother!!!!

patricksouza472 said:
First things first, you gotta be sure you are on stock rom AND have 3G signal. If you don't, flash the latest Pixel Experience so you get IMEI and 3G back (may need to reboot phone twice, I did). After that, you have to flash back stock rom via fastboot mode so make sure you enabled USB debugging (I'm assuming you already know that), but don't run the commands 'fastboot erase modemst1' and 'fastboot erase modemst2'. If you run these, you'll have to start all over. Once you're all set, backup EFS partition using TWRP 3.2.1-0 (64bit version linked above), save it somewhere safe, install dotOS rom (I used the exact version the tutorial suggests, so I would just stick with that), reboot to system (again, you may have to reboot it twice) and you should have 4G/LTE signal. Now create a new EFS backup, save it somewhere safe, and reinstall stock ROM, but this time including those two commands (I installed the latest version with July 2018 security patch). After that, reinstall TWRP 64bits, restore the EFS backup you created while on dotOS and you're done. On First boot you may face some problems while trying to use 4G, it may keep switching between 4G and 3G all the time making it impossible to connect, but should it happen to you, a simple reboot fixes the issue. If you wish to root your phone after the process (like I did for PoGO spoofing) just install 32bit TWRP 3.2.2-0 and flash Magisk 16.7 beta and reboot phone twice (First time may have 4G issue again, rebooting fixes it). Sorry for the late response, it's way past midnight here in Brazil. Hope you get It working again
Click to expand...
Click to collapse
thankyou so much..it worked

Guys I can not get 4g back at all, I run the command fastboot erase modemst1
fastboot erase modemst2 on pixel rom as I only have 3G andnd this wiped my IMEI and put it to 0, so then I had to reinstall stock oreo rom with all the commands (not erase modemst etc) then wipe then install pixel rom to get 3g back, I can't get 4g how do I do it it's driving my crazy!
please help

Any update? I really need 4G working again, the erase modemst1/2 commands just wiped my IMEI on this guide, then I had to start all over again just to get 3G working and my IMEI back again.

junglebungle said:
Any update? I really need 4G working again, the erase modemst1/2 commands just wiped my IMEI on this guide, then I had to start all over again just to get 3G working and my IMEI back again.
Click to expand...
Click to collapse
Have a look at this guide. It is for Potter, but the same principles apply to Cedric
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147

NZedPred said:
Have a look at this guide. It is for Potter, but the same principles apply to Cedric
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Click to expand...
Click to collapse
Wow that looks very difficult, I don't want to mess up my phone even more
I mean I have IMEI and 3G, I just need my 4G back..

junglebungle said:
Wow that looks very difficult, I don't want to mess up my phone even more
I mean I have IMEI and 3G, I just need my 4G back..
Click to expand...
Click to collapse
Quite often 4G is missing for the same reason. What rom are you on right now? If you are on stock nougat, then flash this zip
https://androidfilehost.com/?fid=3700668719832240875
All this zip does is fix the ownership of a couple of folders in the persist partition. If this is the issue you're facing (can't tell for sure without getting some info from your phone), you should get back 4G.