Database Develop

FLashed Wrong ROM (downgraded)

Hello everyone,
I have a XT1079 and I made the mistake of flashing 1069´s ROM. Now I can´t install a custom rom and adb does not recognize my device (it is listed as 1069 with a question mark on the icon in device manager).
Any ideas for help me will be appreciated, thanks a lot.

If your phone is able to go into recovery , you just flash the stock firmware again or flash flashable zip of the stock ROM ( or may be some custom ROM (i'm not sure though)). This will kind of reset your phone and it will work again. But as you said, You have downgraded your phone, you need to check out which one to flash ...i mean whether to flash kitkat or lollipop version.

Custom ROM
andromuks said:
If your phone is able to go into recovery , you just flash the stock firmware again or flash flashable zip of the stock ROM ( or may be some custom ROM (i'm not sure though)). This will kind of reset your phone and it will work again. But as you said, You have downgraded your phone, you need to check out which one to flash ...i mean whether to flash kitkat or lollipop version.
Click to expand...
Click to collapse
Problem is that the stock rom does not come in a zip file and I receive downgrade error msg when I try to flash via mfastboot. But I want to use Cyanogenmod ROM. Thanks again.

GeekMaga said:
Hello everyone,
I have a XT1079 and I made the mistake of flashing 1069´s ROM. Now I can´t install a custom rom and adb does not recognize my device (it is listed as 1069 with a question mark on the icon in device manager).
Any ideas for help me will be appreciated, thanks a lot.
Click to expand...
Click to collapse
install motorola device manager 2.5.4 .exe for fastboot drivers for all motorola's and see if ADB recognises it then?

GeekMaga said:
Hello everyone,
I have a XT1079 and I made the mistake of flashing 1069´s ROM. Now I can´t install a custom rom and adb does not recognize my device (it is listed as 1069 with a question mark on the icon in device manager).
Any ideas for help me will be appreciated, thanks a lot.
Click to expand...
Click to collapse
If you flashed XT1069 motoboot.img then you're simply screwed as you won't be able to connect to mobile network.

One more try
LuK1337 said:
If you flashed XT1069 motoboot.img then you're simply screwed as you won't be able to connect to mobile network.
Click to expand...
Click to collapse
I sent to a technician to restore stock firmware and I will follow the tutorial here in the forum for the right model. Closing thread.

Solved for now
reefuge said:
install motorola device manager 2.5.4 .exe for fastboot drivers for all motorola's and see if ADB recognises it then?
Click to expand...
Click to collapse
Too late but thanks anyway I sent it to a local cell phone repair shop. After that I will follow the tutorial here to install rom and google apps thank you very much.

Man it´s never too late for android
I solved the first part. I was using titan files and for XT1078 the correct one is thea. Problem now is that none of the sim cards are recognized by the firmware. Any ideas guys
I used twrp (mfastboot flash recovery <file_name>. and it´s interface it is pretty friendly. Also installed google apps zips. It is amazing how much you can customize with this ROM.

GeekMaga said:
I solved the first part. I was using titan files and for XT1078 the correct one is thea. Problem now is that none of the sim cards are recognized by the firmware. Any ideas guys
Click to expand...
Click to collapse
you have a xt1079 right? stop flashing WRONG files until you get correct xt1079 firmware - please tell us what you originally had on phone and we will try to find it for you.
I cant seem to find any brazil xt1079 firmwares - yet - you have no signal due to incorrect radio/modem files - only can find xt1079 retcn files this modem / radio combo will be wrong - yours will become available but may take months to appear.....
THIS is why we backup our stock roms with TRWP to include the PDS area

Help installing custom rom

Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho

https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.

min1968 said:
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.
Click to expand...
Click to collapse
Thank you for your response.
I've already got twrp installed for 5.1
So i should just install this MM based ROM i said on the post and replace /etc/firmware folder?
Or i need to install stock MM from ota first?
Thing is, i cant OTA update, it says that the system is corrupted, i even tried from twrp but no luck

I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA

Nacholer said:
I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA
Click to expand...
Click to collapse
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.

min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
Alright, ill do that. Tried with the 4 files backup last night, didn't work as you just told.
Do you have a link to the 5.1 stock recovery i should flash with sp flash tool? I can't find it anywhere. It wont work if i still have twrp installed, right?
Thanks! i really appreciate it, and great guide btw

min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!

In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!

Nacholer said:
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!
Click to expand...
Click to collapse
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Rayan said:
In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!
Click to expand...
Click to collapse
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733

min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
Thank you!! i'll try that and report back.
Click to expand...
Click to collapse

min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Click to expand...
Click to collapse
Thanks for the reply Min1968!
Yes, I know how to recover IMEI on the stock ROM and I'm currently running stock MM rooted with working IMEI.
The problem I have is that I can't run custom ROMs even if I try the etc/firmware trick you mentioned.
What is the stock TWRP partition that has the modem and IMEI? Maybe if I flash it back through TWRP once I get AEX rom up and running?
Thanks!

min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Click to expand...
Click to collapse
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this

Nacholer said:
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this
Click to expand...
Click to collapse
Okay, i fixed it reformatting the data partition on twrp. Thing is, when i want to install the recovery that happens. Maybe if i dont oem unlock?

well, i did that and it booted with the stock recovery. But i still can't OTA, i really dont know why, i even could not when i bought the phone

Nacholer said:
Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho
Click to expand...
Click to collapse
to get imei working https://forum.xda-developers.com/vivo-xl/help/solution-to-sim-detected-flashing-t3620224

[SUSPENDED] fix volte issue in your moto g5s plus

i am sorry if this method did anything wrong with your device, but i already mentioned that this tweak worked for me and i would not be responsible for anyone else.

muklshakya123 said:
Now You Can Easily Fix Broken VoLTE, Follow All The Steps Carefully And Voilla You Are Done With Your Job
STEPS :-
1. Your Device Must Have Bootloader Unlocked With TWRP Installed.
2. Download Persist.zip From Attachments.
3. Put Extracted File In TWRP/Backups/XXXXX/XXXX Folder.
4. Go To TWRP And Restore Persist Backup.
5. Reboot And Check If VoLTE Works Fine Now.
P.S :- This Guide Is Personally Tested By Me On My Moto G5S Plus XT1804 (Still I Am Not Responsible If Anything Goes Wrong, Just Follow The Steps Carefully)
Credits
@akshu2697 For Persist Backup
Me For Testing On XT1804
HIT THANKS IF IT HELPED
Click to expand...
Click to collapse
Good work bro,share this method to as many people as possible to help them all

This worked for my xt1805 that had no LTE after installing a custom ROM then restoring stock. Had no IMEI at first and installing a new custom ROM fixed that, but tried everything including deleting the modem environment partition (e.g. here) but only this persist solution would restore the LTE.
Many thanks!

Can anyone help me and elaborate how to restore the persist file?
EDIT: I used older TWRP, I flashed newer one and I got it. Thanks.

Will this work on an XT1803?

@lynxblaine yes it'll work

Hi,
I restored this extracted file using TWRP and now my IMEI is 0.
Here are the steps I did to get back my IMEI. none of these worked. Please advice.
1. Locked bootloader and went back to stock ROM (version NPSS26.116-61-5 with march update)
2. Did erase of modemst1 &t2 with out any success
3. Flashed just Non-Hlos and Fsg and DSP only.
4. Flashed various ROMS like Pixel experience, Validus, Resurrection Remix, franken ROM. Didn't even get 3G after this.
None of this seem to restore my imei.
But when I did fastboot getvar all I am able to see one IMEI of 15 digits.. So I don't think I bricked my phone.

You should try the restore method in this section of forums for your imei it worked flawlessly for me.

muklshakya123 said:
Now You Can Easily Fix Broken VoLTE, Follow All The Steps Carefully And Voilla You Are Done With Your Job
STEPS :-
1. Your Device Must Have Bootloader Unlocked With TWRP Installed.
2. Download Persist.zip From Attachments.
3. Put Extracted File In TWRP/Backups/XXXXX/XXXX Folder.
4. Go To TWRP And Restore Persist Backup.
5. Reboot And Check If VoLTE Works Fine Now.
For Those Who Are Facing Green Cam Issue
Download persist_fix.zip And Restore Persist Only (Don't Restore EFS This Time)
P.S :- This Guide Is Personally Tested By Me On My Moto G5S Plus XT1804 (Still I Am Not Responsible If Anything Goes Wrong, Just Follow The Steps Carefully)
Credits
@akshu2697 For Persist Backup
Me For Testing On XT1804
HIT THANKS IF IT HELPED
Click to expand...
Click to collapse
flashed from your persist fix zip... imei went 0, and now i can't fix it. Kindly share your efs backup or provide any help if you can...

@caballerobhanu first restore your imei following the guide mentioned in another thread in this section and after that follow my guide. And most importantly follow all these steps on latest march stock rom

muklshakya123 said:
@caballerobhanu first restore your imei following the guide mentioned in another thread in this section and after that follow my guide. And most importantly follow all these steps on latest march stock rom
Click to expand...
Click to collapse
hey, i tried to restore it, but no matter what i do, i am not able to recover it.

caballerobhanu said:
hey, i tried to restore it, but no matter what i do, i am not able to recover it.
Click to expand...
Click to collapse
Same for me as well. I tried each and every rom but still no IMEI. No EFS backup available as well:crying::crying:

sreekanthdb said:
Same for me as well. I tried each and every rom but still no IMEI. No EFS backup available as well:crying::crying:
Click to expand...
Click to collapse
U have to restore these on stock rom bro
---------- Post added at 03:38 AM ---------- Previous post was at 03:38 AM ----------
sreekanthdb said:
Same for me as well. I tried each and every rom but still no IMEI. No EFS backup available as well:crying::crying:
Click to expand...
Click to collapse
For imei flash validus then rebopt Erase modemst1 modemst2... Or flash rr

s.k.rajput said:
U have to restore these on stock rom bro
---------- Post added at 03:38 AM ---------- Previous post was at 03:38 AM ----------
For imei flash validus then rebopt Erase modemst1 modemst2... Or flash rr
Click to expand...
Click to collapse
Did that as well. Flashed Validus Rom, Pixel Experience, Resurrection Remix, AOSP Extended Rom and Franken ROM. No success on any of the roms.
PS: I went to Moto service center today and asked them if they will restore software. They said for unlocked bootloaders they'll not do it.. :crying: Guess I need to wait till OREO is officially released.

sreekanthdb said:
Did that as well. Flashed Validus Rom, Pixel Experience, Resurrection Remix, AOSP Extended Rom and Franken ROM. No success on any of the roms.
PS: I went to Moto service center today and asked them if they will restore software. They said for unlocked bootloaders they'll not do it.. :crying: Guess I need to wait till OREO is officially released.
Click to expand...
Click to collapse
Flash validus/rr boot... Then reboot to Bootloader... Islf imei is still null... Then do erade modemst1 modemst2 commands

s.k.rajput said:
Flash validus/rr boot... Then reboot to Bootloader... Islf imei is still null... Then do erade modemst1 modemst2 commands
Click to expand...
Click to collapse
Done that. I flashed all the above mentioned roms and after boot there's no IMEI. so I erased modemst1 & t2. but not working

s.k.rajput said:
Flash validus/rr boot... Then reboot to Bootloader... Islf imei is still null... Then do erade modemst1 modemst2 commands
Click to expand...
Click to collapse
thing is signal is there, 4g is there, data can be used, but imei = 0.

caballerobhanu said:
thing is signal is there, 4g is there, data can be used, but imei = 0.
Click to expand...
Click to collapse
That's strange... As usually signal wont come if imei is null

s.k.rajput said:
That's strange... As usually signal wont come if imei is null
Click to expand...
Click to collapse
Yeah, I tried RR vali aex, nothing was happening so I reverted to stock and locked the bootloader and submitted it to service center , they might be able to do something here. But they said your phone was rooted and we can't help you here. We can replace PCB which will cost you around 9-10k... So will go back tomorrow to collect.
Then will try something else.

caballerobhanu said:
Yeah, I tried RR vali aex, nothing was happening so I reverted to stock and locked the bootloader and submitted it to service center , they might be able to do something here. But they said your phone was rooted and we can't help you here. We can replace PCB which will cost you around 9-10k... So will go back tomorrow to collect.
Then will try something else.
Click to expand...
Click to collapse
U lost imei & locked bootloader y tho?? Some peeps who did the same thing are unable to get unlock code from Moto... U need to contact them via social media to get if u dont get the code from official site... Also u cant be able to use data or ur device will shows signals if u have imei lost

Moto e5+ works with either stock rom or pixel experience sim card issue

So my moto e5+ works with a stock rom I have and auto flash folder for that I found somewhere around and it works with pixel experience but neither the pixel experience rom or the base factory (8.0) rom can read sim cards being in the phone however when I update the stock rom to 9.0 it registers the sim card being there.
So I'm curious which files tell the phone how to read sim cards and if there's some method to splice said file from stock 9.0 into the pixel rom (various things about the base rom annoy the **** outta me like the "Hello moto" boot message it feels the need to scream at you every boot or the motorola bloatware that a little of seems tied to important system files which would make debloating it cause issues.)

SketchSlayer said:
So my moto e5+ works with a stock rom I have and auto flash folder for that I found somewhere around and it works with pixel experience but neither the pixel experience rom or the base factory (8.0) rom can read sim cards being in the phone however when I update the stock rom to 9.0 it registers the sim card being there.
So I'm curious which files tell the phone how to read sim cards and if there's some method to splice said file from stock 9.0 into the pixel rom (various things about the base rom annoy the **** outta me like the "Hello moto" boot message it feels the need to scream at you every boot or the motorola bloatware that a little of seems tied to important system files which would make debloating it cause issues.)
Click to expand...
Click to collapse
My suggestion is to flash this from stock firmware
After installing custom rom.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my mata using XDA Labs

sd_shadow said:
My suggestion is to flash this from stock firmware
After installing custom rom.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
How would one extract them from an active rom to flash them?
As I mentioned it seems to require upgrading the stock rom to 9.0 so I assume the files in stock rom I have on hand for unbricking it aren't exactly functional as far as the sim port goes so I assume I'd need to tear the files out of the 9.0 droid install after upgrading to it.

SketchSlayer said:
My suggestion is to flash this from stock firmware
After installing custom rom.
How would one extract them from an active rom to flash them?
As I mentioned it seems to require upgrading the stock rom to 9.0 so I assume the files in stock rom I have on hand for unbricking it aren't exactly functional as far as the sim port goes so I assume I'd need to tear the files out of the 9.0 droid install after upgrading to it.
Click to expand...
Click to collapse
Do you have a link to the instructions that you are referring to?
Sent from my mata using XDA Labs

sd_shadow said:
Do you have a link to the instructions that you are referring to?
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Instructions? I've just had to mess around with flashing to work out which roms work and which don't for me and what parts of what seem to work hence knowing whatever controls the sim reading (likely modem by what has been said) only seems to work on stock 9.0 I believe the stock 8.0 I use for unbricking is the one found at https://drive.google.com/file/d/1AMquyKDx-5WvmMrkgXylv_7IaaVtovIC/view found through https://motostockrom.com/motorola-moto-e5-plus-xt1924-3 judging by my web history
What I'm asking is, since the modem files seem to be what controls the ability to detect sim cards, how would you copy the working modem files from the running phone to a computer to later flash via fastboot? I assume that when installed the modem files are not in a flash ready format or easily copied and I don't have the stock 9.0 rom (I've literally been flashing 8 then running the upgrade whenever it bricks due to a custom rom not working with it).
Sorry if I am being stupid but I'm more of a hardware nerd than a software one, I build my own computers and I tear broken tech apart to find probable faults but my software knowledge is somewhat limited so if I'm missing something obvious then that is totally on me.

SketchSlayer said:
As I mentioned it seems to require upgrading the stock rom to 9.0 .
Click to expand...
Click to collapse
By whom?
Sent from my mata using XDA Labs

sd_shadow said:
By whom?
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I found that out myself as the phone absolutely refuses to read the sim card on either the 8.0 rom or the current pixel experience rom and I was messing around checking if it read on the maybe 9.0 and it did. the method of upgrade being through the phones system menu, does this answer your somewhat confusing question?

The update that has the fix for me is version: OPP27.91.179-8 I may be mistaken about it being 9.0 I'd left the phone bricked for a while and was working from memory, the phone had an upgrade to 8.0 message and it being a rounded build I assumed it was jumping a version (knowing the base rom was 8 I assumed it was to 9 but that may be me being a dumb) I can check the build info more once the update runs for the like 10th time I've run it.

SketchSlayer said:
The update that has the fix for me is version: OPP27.91.179-8 I may be mistaken about it being 9.0 I'd left the phone bricked for a while and was working from memory, the phone had an upgrade to 8.0 message and it being a rounded build I assumed it was jumping a version (knowing the base rom was 8 I assumed it was to 9 but that may be me being a dumb) I can check the build info more once the update runs for the like 10th time I've run it.
Click to expand...
Click to collapse
Android 9 should should be like
29.114-134-7
Sent from my jerry_cheets using XDA Labs
---------- Post added at 10:12 PM ---------- Previous post was at 10:01 PM ----------
https://mirrors.lolinet.com/firmware/moto/ahannah/official/RETIN/
Sent from my jerry_cheets using XDA Labs

sd_shadow said:
Android 9 should should be like
29.114-134-7
Sent from my jerry_cheets using XDA Labs
---------- Post added at 10:12 PM ---------- Previous post was at 10:01 PM ----------
https://mirrors.lolinet.com/firmware/moto/ahannah/official/RETIN/
Sent from my jerry_cheets using XDA Labs
Click to expand...
Click to collapse
Yeah best I can determine I was wrong about it being 9, it appears to be a security update for 8.0 (though it is what fixs the modem files not working from the rom) that unlike all the other updates doesn't tell you it's a security update in the little notification of availability and under the settings menu the update says "update to android 8.0" which when going from memory my mind remembered as 9.0 cause I knew the rom was 8.0 and the clear next update that isn't a full new build would be either 8.0.x or 8.1 not 8.0 cause I'm used to rounded updates being different from the version running when you update.
My bad but that's what happens when I assume upfront info is going to follow some form of logic.

I need help with IMEI 0

Hello xda members I come to ask for help to fix the IMEI 0 with my moto g6 xt1925 cell phone, I have flashed the rom I am android 8 and 9 but it is still the same, someone will have the EFS files? since I also noticed that I can't find that folder

shawgluz said:
Hello xda members I come to ask for help to fix the IMEI 0 with my moto g6 xt1925 cell phone, I have flashed the rom I am android 8 and 9 but it is still the same, someone will have the EFS files? since I also noticed that I can't find that folder
Click to expand...
Click to collapse
You can't take someone else's files to get your IMEI back.
If you could explain more detailed what you've done, then it might be helpful for others to find a solution.
---------- Post added at 01:42 PM ---------- Previous post was at 01:34 PM ----------
Have a look here:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147/
Although this example is for Moto G5 it's nearly the same for G6.

WoKoschekk said:
You can't take someone else's files to get your IMEI back.
If you could explain more detailed what you've done, then it might be helpful for others to find a solution.
---------- Post added at 01:42 PM ---------- Previous post was at 01:34 PM ----------
Have a look here:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147/
Although this example is for Moto G5 it's nearly the same for G6.
Click to expand...
Click to collapse
My problem is that I have IMEI 0, what happens is that I flash the android rom 8 to 9, then I wanted to try the pixel experience rom but when I return to android 9 because I don't like its excessive battery usage I realize that I don't count With a signal to what I look at and I do not have my IMEI number, it is at 0, it looked for things to solve but it did not find anything, I cannot find my EFS folder or where the IMEI is, I wanted someone else's file to be able to put my imei again modifying the file and thus return but I don't know, I can't find anything

shawgluz said:
My problem is that I have IMEI 0, what happens is that I flash the android rom 8 to 9, then I wanted to try the pixel experience rom but when I return to android 9 because I don't like its excessive battery usage I realize that I don't count With a signal to what I look at and I do not have my IMEI number, it is at 0, it looked for things to solve but it did not find anything, I cannot find my EFS folder or where the IMEI is, I wanted someone else's file to be able to put my imei again modifying the file and thus return but I don't know, I can't find anything
Click to expand...
Click to collapse
You can't modify this file!! That's not a text file like "this is your IMEI 123456789"

shawgluz said:
My problem is that I have IMEI 0, what happens is that I flash the android rom 8 to 9, then I wanted to try the pixel experience rom but when I return to android 9 because I don't like its excessive battery usage I realize that I don't count With a signal to what I look at and I do not have my IMEI number, it is at 0, it looked for things to solve but it did not find anything, I cannot find my EFS folder or where the IMEI is, I wanted someone else's file to be able to put my imei again modifying the file and thus return but I don't know, I can't find anything
Click to expand...
Click to collapse
Your IMEI files are in /persist/rfs/msm/mpss/dhob.bin + shob.bin
EFS1=modemst1
EFS2=modemst2
That's a usual problem when downgrading your ROM and the reason why it is not recommended!!
Make sure you are running Android 9 and the mentioned files are available. You need also the NON-HLOS.bin from your stock firmware. Boot into fastboot mode and type
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot reboot

WoKoschekk said:
You can't modify this file!! That's not a text file like "this is your IMEI 123456789"
Click to expand...
Click to collapse
He had watched a video which he modified as well, edited it as text and at the time of restarting the imei it was changed, so it is not possible? since my imei is at 0 but my cell information shows that the base band is correct

WoKoschekk said:
Your IMEI files are in /persist/rfs/msm/mpss/dhob.bin + shob.bin
EFS1=modemst1
EFS2=modemst2
That's a usual problem when downgrading your ROM and the reason why it is not recommended!!
Make sure you are running Android 9 and the mentioned files are available. You need also the NON-HLOS.bin from your stock firmware. Boot into fastboot mode and type
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot reboot
Click to expand...
Click to collapse
Will my files be deleted? osea session of whatsapp and others?
How do I know what my stock version is? Since at this moment I have the recent version granted by Rescue and Smart Assistant, I have a security patch April 2020

WoKoschekk said:
Your IMEI files are in /persist/rfs/msm/mpss/dhob.bin + shob.bin
EFS1=modemst1
EFS2=modemst2
That's a usual problem when downgrading your ROM and the reason why it is not recommended!!
Make sure you are running Android 9 and the mentioned files are available. You need also the NON-HLOS.bin from your stock firmware. Boot into fastboot mode and type
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot reboot
Click to expand...
Click to collapse
I tried but I still com imei 0 :/

shawgluz said:
I tried but I still com imei 0 :/
Click to expand...
Click to collapse
Do you still have these files?
/persist/rfs/msm/mpss/dhob.bin
/persist/rfs/msm/mpss/shob.bin

WoKoschekk said:
Do you still have these files?
/persist/rfs/msm/mpss/dhob.bin
/persist/rfs/msm/mpss/shob.bin
Click to expand...
Click to collapse
Yep, look

shawgluz said:
Yep, look
Click to expand...
Click to collapse
Flash the stock firmware and then everything shoud be fine.

WoKoschekk said:
Flash the stock firmware and then everything shoud be fine.
Click to expand...
Click to collapse
I already did it, I put these versions
ALI_OPSS27.104-92-4-5-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info
ALI_PPSS29.55-37-7-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info
ALI_PPSS29.55-37-7-10_cid50_subsidy-DEFAULT_regulatory-XT1925-5_CFC.info
ALI_PPSS29.55-37-7-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info
And it doesn't fix :/

shawgluz said:
I already did it, I put these versions
ALI_OPSS27.104-92-4-5-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info
ALI_PPSS29.55-37-7-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info
ALI_PPSS29.55-37-7-10_cid50_subsidy-DEFAULT_regulatory-XT1925-5_CFC.info
ALI_PPSS29.55-37-7-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info
And it doesn't fix :/
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
Download and install this tool. Boot into fastboot, choose the rescue option for fastboot mode and let the tool flash the right firmware for your phone.

WoKoschekk said:
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
Download and install this tool. Boot into fastboot, choose the rescue option for fastboot mode and let the tool flash the right firmware for your phone.
Click to expand...
Click to collapse
I tried it and still continue with IMEI 0 :/
I also already used the new version RETAIL that came out (ALI_RETAIL_9.0_PPS29.118-15-11-16_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) and remain the same: /

shawgluz said:
I tried it and still continue with IMEI 0 :/
I also already used the new version RETAIL that came out (ALI_RETAIL_9.0_PPS29.118-15-11-16_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) and remain the same: /
Click to expand...
Click to collapse
I have got two devices: Moto G6 and Moto G6+
Due to a very dump mistake I killed my dhob.bin and shob.bin files on my G6+ and lost my IMEI forever. That's the reason why I bought the G6.
I know there are a few people here in this forum offering a persist.img for those who ruined their own. As I can see on your screenshot the hob+dhob_report.txt files are a clean sign for flashing someone else's persist.img on your device.
To make matters worse, your shob.bin file was created at May 2016!! The release date was March 2018! I don't think that Motorola developed that device two years before the official release date...
Option 1: You flashed another persist.img to get your IMEI back
Option 2: Your device is a used one and you bought it with a already messed up persist partition.
At the end it doesn't matter, because your IMEI will remain 0.
---------- Post added at 10:49 PM ---------- Previous post was at 10:44 PM ----------
Your persist should be this way
https://ibb.co/rMNk4xP

WoKoschekk said:
I have got two devices: Moto G6 and Moto G6+
Due to a very dump mistake I killed my dhob.bin and shob.bin files on my G6+ and lost my IMEI forever. That's the reason why I bought the G6.
I know there are a few people here in this forum offering a persist.img for those who ruined their own. As I can see on your screenshot the hob+dhob_report.txt files are a clean sign for flashing someone else's persist.img on your device.
To make matters worse, your shob.bin file was created at May 2016!! The release date was March 2018! I don't think that Motorola developed that device two years before the official release date...
Option 1: You flashed another persist.img to get your IMEI back
Option 2: Your device is a used one and you bought it with a already messed up persist partition.
At the end it doesn't matter, because your IMEI will remain 0.
---------- Post added at 10:49 PM ---------- Previous post was at 10:44 PM ----------
Your persist should be this way
https://ibb.co/rMNk4xP
Click to expand...
Click to collapse
Where can I get persist.img? To test, I'll make a copy of the ones I already have in case of doubt. Another thing is that my problem was that I used the rom pixel experience and when I saw that I did not like it, I returned to android 9 stock and there my problem

shawgluz said:
Where can I get persist.img? To test, I'll make a copy of the ones I already have in case of doubt. Another thing is that my problem was that I used the rom pixel experience and when I saw that I did not like it, I returned to android 9 stock and there my problem
Click to expand...
Click to collapse
The files shown on your screenshot do not belong to your phone. They belong to another Motorola device. But to get your IMEI back you need your own files. They are unique. These files were created and encrypted by Motorola and there is no chance to recreate them!! In case you haven't got a backup of your own your IMEI is dead, zero, 0, gone. bye bye!

WoKoschekk said:
The files shown on your screenshot do not belong to your phone. They belong to another Motorola device. But to get your IMEI back you need your own files. They are unique. These files were created and encrypted by Motorola and there is no chance to recreate them!! In case you haven't got a backup of your own your IMEI is dead, zero, 0, gone. bye bye!
Click to expand...
Click to collapse
Is there no file to do this?
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068

shawgluz said:
Is there no file to do this?
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
Click to expand...
Click to collapse
The second sentence:
This method will not work if you have restored other device's persist from some Youtube video or some Internet guide.
Here, you can flash my persist.img from my G6 (XT1925-5, ALI_RETEU_PPSS29.55-37-7-2)
https://mega.nz/file/hzYUDa4T#hAxvNSk4X5orTkUapJ35v3BY09QqIkH_Mq5-hM1IDGM
Have fun! It won't work!

I had this very same problem today after trying out Android 10. How I fixed it was to download the LineageOS 16 and install that over the top of whatever firmware/rom you have on your phone. Then once you've booted properly (Don't do root or anything, just boot the rom) check your IMEI has gone back to normal and if it has then you can flash a stock rom over the top (wipe all partitions as normal).