I was on indian_mm_deodexed_rooted then flashed TruPureXMM as one of my friends suggested trying it out as it is smooth etc.
I didn't knew that it is Pure single sim version and after flashing no network and then i checked only single sim showed :crying: then i again formated and flashed back indian_mm_deodexed_rooted and modem_indian_mm_fixed but this time it shows two sims with no network atall and Emergency calls on both... In settings SIM cards its SIM 1 emty and SIM 2 empty :crying::crying: tried flashing with indian modem again and also tried lp modem but nothing is working, please help :crying::crying:
Both IMEI Unknown status.
I didn't even took back of my stock as i didn't knew about it before
Bootloader is unlocked and TWRP is installed.
Note: My x style came with lollipop and then i did official update with marshmallow and then i wanted to root so flashed.
Please help me get back dual sim with network if possible
EDIT: Solved the issue now and here is the solution:
Download Stockrom from this link according to your exact model and follow the commands exactly:
[Firmware] Moto X Style/Pure Stock Software by lAndroXl
I just ignored command fastboot oem lock begin as told by @dj_ooms so boot loader is still unlocked and also i have installed TWRP and rooted by flashing SuperSu.
Also very important thing is take nandroid backup after installing TWRP i.e backup your stock rom by selecting backup in TWRP... please also take backup your EFS partition also, thanks
@dj_ooms @Unicornzz and @bw03
:angel: Thank you guys for your valuable replies and thanks to lAndroXl uploader and thread... really helped :angel:
Use the ROM from here.
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
Edit: you may get the modem working with just flashing the modem zip but I'm not sure as I don't have a dual sim phone to try. You can try it. If that doesn't work, then flash the ROM.
bw03 said:
Use the ROM from here.
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
Edit: you may get the modem working with just flashing the modem zip but I'm not sure as I don't have a dual sim phone to try. You can try it. If that doesn't work, then flash the ROM.
Click to expand...
Click to collapse
Thanks for the reply.
I already did flashed the modem zip but it didn't worked and also flashed to indian_mm_deodexed_rooted.zip with indian mm but still my imei is unknown.
Any other way or any other rom which i can try??
desiaddict said:
Thanks for the reply.
I already did flashed the modem zip but it didn't worked and also flashed to indian_mm_deodexed_rooted.zip with indian mm but still my imei is unknown.
Any other way or any other rom which i can try??
Click to expand...
Click to collapse
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
bw03 said:
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
Click to expand...
Click to collapse
I used twrp and wiped cache data and also system and then flashed ROM and modem but still it is not working
didn't flashed internal rom as it had ROM but wiped everything else but still no luck.
bw03 said:
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
Click to expand...
Click to collapse
I used twrp and wiped cache data and also system and then flashed ROM and modem but still it is not working
didn't flashed internal rom as it had ROM but wiped everything else but still no luck.
Perhaps do a clean flash on a ROM from here? I don't know. Just throwing it out there.
http://forum.xda-developers.com/mot...-stock-x1572-1575-5-1-1-lph23-116-18-t3229355
bw03 said:
Perhaps do a clean flash on a ROM from here? I don't know. Just throwing it out there.
http://forum.xda-developers.com/mot...-stock-x1572-1575-5-1-1-lph23-116-18-t3229355
Click to expand...
Click to collapse
I will try it out... downloading now and will let you know later when dl and flashing finishes and hope i get it working this time, fingers crossed.
If you check my modem thread i posted last night try the code at the bottom after you have flashed the India Dual sim modem you already have, it purges the cache's for modem/general cache
If your still struggling after that ill see what files i have stored away for modems, Im sure i have another dual sim modem other than the indian one..
Edit:
Packaging you afew flashable zip's now with Dualsim Modems for the XT1572
You may need to do the Indian LP modem from the first linked thread too.
http://forum.xda-developers.com/mot...-eu-single-t3297051/post64888714#post64888714
I have posted up more DUAL Sim modems for you to try. Hope it helps and you get it sorted
Unicornzz said:
If you check my modem thread i posted last night try the code at the bottom after you have flashed the India Dual sim modem you already have, it purges the cache's for modem/general cache
If your still struggling after that ill see what files i have stored away for modems, Im sure i have another dual sim modem other than the indian one..
Edit:
Packaging you afew flashable zip's now with Dualsim Modems for the XT1572
Click to expand...
Click to collapse
Hey thanks for the reply... the code did not worked and now trying your modems from ur thread ASIA Dual Sim.
bw03 said:
You may need to do the Indian LP modem from the first linked thread too.
Click to expand...
Click to collapse
Yes i will LP modem flash.
Just one question to all : when i got moto x style in dec it was having Lollipop then i did marshmallow update and then flashed for rooting so now if i again flash to lP stock rom will it get bricked or work?? As i am not getting signals so i will try it later when nothing else works
desiaddict said:
Hey thanks for the reply... the code did not worked and now trying your modems from ur thread ASIA Dual Sim.
Click to expand...
Click to collapse
Try both LP and MM one
I don't agree how you got shafted into this mess, ROM Makers should NEVER package Radio/Modem or Bootloader files in with a ROM ever.
When i release mine in the coming weeks it will be X175x with all the optional modem files or none at all.
Best of luck to you
Unicornzz said:
Try both LP and MM one
I don't agree how you got shafted into this mess, ROM Makers should NEVER package Radio/Modem or Bootloader files in with a ROM ever.
When i release mine in the coming weeks it will be X175x with all the optional modem files or none at all.
Best of luck to you
Click to expand...
Click to collapse
Guys still no luck... nothing worked. I tried both DS modem but did not got sim detection.
I hope somehow who might have faced same issue and got solved will see and reply the thread and save me.
You guys tried to solve my problem... Thank you to both.
Stock ROMs
Have you tried the guide in this thread?:
[Firmware] Moto X Style/Pure Stock Software
You will need a computer and to follow the guide exactly and will lose all data off your internal storage so back up your sdcard to external storage or computer beforehand. Flashing this solved my problems when I had them. Just make sure you back up things before you start. The ROMs are completely stock so you will need to root and install a custom recovery again once done.
Hope this helps.
Ooms
dj_ooms said:
Have you tried the guide in this thread?:
[Firmware] Moto X Style/Pure Stock Software
You will need a computer and to follow the guide exactly and will lose all data off your internal storage so back up your sdcard to external storage or computer beforehand. Flashing this solved my problems when I had them. Just make sure you back up things before you start. The ROMs are completely stock so you will need to root and install a custom recovery again once done.
Hope this helps.
Ooms
Click to expand...
Click to collapse
Okay i am dling the Asian dual sim variant now and hope it works.
But i am little unclear about process as i already have unlocked bootloader and TWRP so can i directly clean flash ROM via TWRP??
Also pls check my reply in that thread for better understanding and not confusing:
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486/page8
Did you backup your efs partition? Your imei is inside that partition...
desiaddict said:
Okay i am dling the Asian dual sim variant now and hope it works.
But i am little unclear about process as i already have unlocked bootloader and TWRP so can i directly clean flash ROM via TWRP??
Also pls check my reply in that thread for better understanding and not confusing:
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486/page8
Click to expand...
Click to collapse
To be honest, I left the lock bit out. These are the commands I used when I did it:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
The bootloader will stay unlocked this way meaning you can flash TWRP after. I would flash as above first and once the phone is booted and confirmed to be working, I would then flash TWRP and other mods. On a note, I have an EU XT1572 so I only had 9 parts on the system flash part (upto system.img_sparsechunk.8). The dual sim version may have 10 or more parts. Check how many parts you have beforehand and make sure you flash all bits.
Hope this helps.
Ooms
dj_ooms said:
To be honest, I left the lock bit out. These are the commands I used when I did it:
The bootloader will stay unlocked this way meaning you can flash TWRP after. I would flash as above first and once the phone is booted and confirmed to be working, I would then flash TWRP and other mods. On a note, I have an EU XT1572 so I only had 9 parts on the system flash part (upto system.img_sparsechunk.8). The dual sim version may have 10 or more parts. Check how many parts you have beforehand and make sure you flash all bits.
Hope this helps.
Ooms
Click to expand...
Click to collapse
Oh GOD that totaly worked out great :good::good:
Everything is working fine now
Also rooted again without any problem :cyclops:
Thank you buddy.
@dj_ooms @Unicornzz and @bw03
:angel: Thank you guys for your valuable replies... really helped :angel:
Related
I've made a huge mistake.
I created a system backup in TWRP before rooting as recommended but later when I wanted to move the backup to my PC, I accidentally deleted it instead.
Meanwhile I've installed ElementalX to my system partition and thus I have no chance to get the next OTA.
Does anybody have by chance a TWRP backup of MotoG Plus XT1642 DualSIM UK (preferably MPJ24.139-63) system partition ?
I think it doesn't have to be a phone from the UK, it should be the same in all of Europe.
Baseband version: M8952_70009.08.03.48R ATHENE_EMEA_DSDS_CUST
dsmid said:
I've made a huge mistake.
I created a system backup in TWRP before rooting as recommended but later when I wanted to move the backup to my PC, I accidentally deleted it instead.
Meanwhile I've installed ElementalX to my system partition and thus I have no chance to get the next OTA.
Does anybody have by chance a TWRP backup of MotoG Plus XT1642 DualSIM UK (preferably MPJ24.139-63) system partition ?
I think it doesn't have to be a phone from the UK, it should be the same in all of Europe.
Baseband version: M8952_70009.08.03.48R ATHENE_EMEA_DSDS_CUST
Click to expand...
Click to collapse
If you flashed root systemless you can take another twrp backup, your system is unchanged.
When you flashed ElementalX you replaced your boot partition, so again your system partition is still unchanged.
gabriwinter said:
If you flashed root systemless you can take another twrp backup, your system is unchanged.
When you flashed ElementalX you replaced your boot partition, so again your system partition is still unchanged.
Click to expand...
Click to collapse
I am not sure, this is what the creator of ElementalX says on his site:
Always reflash your ROM when changing kernels. Reflashing without wiping data (known as a “dirty flash”) is the best way to ensure your new kernel works properly. It is not enough to simply reflash the stock boot.img. Many kernel installers make changes to the /system partition as well, which could prevent your new kernel from working correctly. Many kernels (including most versions of ElementalX) use the existing boot.img as a base (often called the “anykernel” installation method), so it’s very important to have the kernel boot.img that came with your ROM, as this contains scripts necessary for the ROM and kernel to work correctly together. Dirty flashing before you install a new kernel will do the trick.
Click to expand...
Click to collapse
dsmid said:
I am not sure, this is what the creator of ElementalX says on his site:
Click to expand...
Click to collapse
I think this is the best you can do:
Make a twrp backup.
Reboot into bootloader and do:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot reboot
Your data will remain unchanged, then take the ota and finally take a twrp backup before flashing supersu and ElementalX again.
Just do a factory restore using fastboot. Simplest solution.
I know I have to flash the boot and system partitions with stock images.
My problem is that I don't know where to get these images.
EDIT:
Just to clarify my concerns:
I know there is a stock firmware for XT1642 available (XT1642_ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip).
However it is not clear which region this firmware is intended for (INDIA, EMEA or RETUSA ?). I don't want to loose the extra European LTE & WiFi bands.
Also I don't want to loose the dual SIM ability as there are XT1642 models that are single SIM.
I have the xt1642 bought in France. I think the right firmware is :
XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip.
I flashed it just to test the firmware and i had ota and wifi works. Don't know about dual sim because i have only one.
titou4488 said:
I flashed it just to test the firmware and i had ota and wifi works. Don't know about dual sim because i have only one.
Click to expand...
Click to collapse
Well, it is not instantly obvious that LTE band 20 and WiFi channels 12, 13 are missing.
You will notice it only when you need it.
Are you sure b20 and wifi channels 12 and 13 are missing in this firmware? I can't test because i restored my backup
titou4488 said:
Are you sure b20 and wifi channels 12 and 13 are missing in this firmware? I can't test because i restored my backup
Click to expand...
Click to collapse
I am not sure but if this firmware is intended for USA, India or Brazil, then LTE band 20 is missing (models sold there lack it) and I have an experience that WiFi channels 12 and 13 are not available in US firmwares.
Not sure about India and Brazil.
BTW what backup did you restore from? The original French firmware you had on your phone when you purchased it?
Such backup would be worth a try if you would be so kind and share it with me.
Sadly my backup is the original firmware rooted and with elementalx kernel that's the reason why i look for the stock firmware.
deleted.
Hello xda community,
I've rooted my G4+ successfully and i can use my phone normally.
But from time to time i ran into bootloops after powering it up at the morning. Sometimes it took some loops at the “oem unlock warning” and then the boot animation shows up.
Sometimes the loop end up by booting automatically into the TWRP.
I am using the “ElementalX 1.04” kernel.
And sometimes my phone powers on by plugging in the charger….
Anyone got a clue or solution
BlackBull said:
Hello xda community,
I've rooted my G4+ successfully and i can use my phone normally.
But from time to time i ran into bootloops after powering it up at the morning. Sometimes it took some loops at the “oem unlock warning” and then the boot animation shows up.
Sometimes the loop end up by booting automatically into the TWRP.
I am using the “ElementalX 1.04” kernel.
And sometimes my phone powers on by plugging in the charger….
Anyone got a clue or solution
Click to expand...
Click to collapse
Try reflashing the stock ROM by fastboot..
It'll most probably solve the problem.
Swapney Raul said:
Try reflashing the stock ROM by fastboot..
It'll most probably solve the problem.
Click to expand...
Click to collapse
Hello Swapney Raul,
I´ve done that before. Everything works fine untill i root the device.
BlackBull said:
Hello Swapney Raul,
I´ve done that before. Everything works fine untill i root the device.
Click to expand...
Click to collapse
Which version of stock are you using?
Swapney Raul said:
Which version of stock are you using?
Click to expand...
Click to collapse
7.0
Buid:
NPJ25.93-11
BlackBull said:
7.0
Buid:
NPJ25.93-11
Click to expand...
Click to collapse
Try upgrading to 93-14
BlackBull said:
7.0
Buid:
NPJ25.93-11
Click to expand...
Click to collapse
Also, what rooting manager are you using? Check if it's SuperSU v2.79 SR3 beta (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133) or the latest Magisk v12 (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) - I'm not sure what the latest version of phhsuperuser is (https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394). You may wish to update to the latest rooting manager, see if that resolves your issue.
echo92 said:
Also, what rooting manager are you using? Check if it's SuperSU v2.79 SR3 beta (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133) or the latest Magisk v12 (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) - I'm not sure what the latest version of phhsuperuser is (https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394). You may wish to update to the latest rooting manager, see if that resolves your issue.
Click to expand...
Click to collapse
@BlackBull you'd also like to flash the 93-14 version of the stock rom via fastboot and then proceed with rooting and follow what @echo92 has mentioned. Updating to 93-14 will ensure stability as per the release notes.
I am rooted by magisk su.. Have not faced any such issue! I am on latest 14-4..
U can even try that..
abhi212b said:
I am rooted by magisk su.. Have not faced any such issue! I am on latest 14-4..
U can even try that..
Click to expand...
Click to collapse
On which phone?
I have an 4GB RAM / 64 GB ROM XT1642 G4 Plus.
I rooted it now with Magiks. But i Can only start the phone with "ElementalX 1.04" installed.
But the wiered bootloops still happend.
Maybe its the kernel....
BlackBull said:
On which phone?
I have an 4GB RAM / 64 GB ROM XT1642 G4 Plus.
I rooted it now with Magiks. But i Can only start the phone with "ElementalX 1.04" installed.
But the wiered bootloops still happend.
Maybe its the kernel....
Click to expand...
Click to collapse
Xt 1643, 3 gb, 32gb ROM... even i use EX... I flashed the EX 1st, magisk! Never faced any bootloops!
BlackBull said:
On which phone?
I have an 4GB RAM / 64 GB ROM XT1642 G4 Plus.
I rooted it now with Magiks. But i Can only start the phone with "ElementalX 1.04" installed.
But the wiered bootloops still happend.
Maybe its the kernel....
Click to expand...
Click to collapse
No its not the kernel problem ...
Its something eles..
Swapney Raul said:
No its not the kernel problem ...
Its something eles..
Click to expand...
Click to collapse
If i flash the unrooted stock boot again, my phone acts normal.
BlackBull said:
If i flash the unrooted stock boot again, my phone acts normal.
Click to expand...
Click to collapse
So, on the stock kernel, custom recovery and stock system, you don't experience any bootloops or powering on whilst charging?
I'd suggest, like others have already, to flash/update your device to NPJ25.93-14, as that newer update may fix issues that you're encountering. Of course, this will remove root, TWRP and though not certain, may remove your data too, so back up accordingly.
Perhaps one thing to try, if you're not willing to update, is to download a fresh copy of ElementalX 1.0.4 directly onto your device (either over Wi-Fi/mobile data). You may wish to use a file browser (e.g. Amaze) to inspect the properties of the ElementalX file and check that the downloaded file has the same md5 checksum and same/similar file size to that reported on Android File Host.
Reboot to TWRP (what TWRP version are you running, btw?).
Flash ElementalX as directed.
Wipe cache/Dalvik
Reboot.
Check your system is running, you may wish to try to see if you experience any of those odd behaviours.
If your system looks stable, download a fresh copy of magisk or SuperSU (depending on what root manager you had before, I don't think you can mix root managers without properly unrooting them via their respective root methods! You may run into odd issues, though I think magisk will install over SuperSU...)
Reboot. Back up your device in TWRP.
Flash the root manager of choice.
Reboot.
If you still face bootloops after fresh installs of both ElementalX/your root manager, then a re-flash of the stock ROM might be in order, to bring you up to date and also to remove traces of previous rooting from your ramdisk/kernel (which may be conflicting with later attempts to root, possibly). https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for the Nougat NPJ25.93-14 fastboot ROM.
@BlackBull : I have faced no such issues after rooting my stock firmware. But "phh" SuperSu doesn't seem to be as efficient as the "chainfire's" SuperSu. Especially felt the difference while using apps like Servicely and Greenify. Both those apps worked perfectly with chainfire's SU but inefficiently with phh SU.
Probably the bootloops you experienced could be due to corrupted SU zip or flashing the wrong SU zip.
BlackBull said:
On which phone?
I have an 4GB RAM / 64 GB ROM XT1642 G4 Plus.
I rooted it now with Magiks. But i Can only start the phone with "ElementalX 1.04" installed.
But the wiered bootloops still happend.
Maybe its the kernel....
Click to expand...
Click to collapse
Having Elemental-X installed is pretty much required to successfully root Nougat stock. And it was always stable and solid for me when on rooted stock. But I have found the best way to root it is with SuperSU-2.79-SR3. Magisk has always been a pain in the a-- for me and for the life of me I can't see why everybody raves about it so much. I've tried it on 3 different devices and always disliked it. If the method of rooting for a custom ROM is Magisk, I will avoid that ROM.
Just my opinion (you know what they say about those) based on my own experiences. I know many others will disagree and that's okay too. But I have yet to find a a more stable way to root than SuperSU.
So I´ve tried differend combinations.
twrp-3.0.2-0-athene.img & ElementalX-G4-1.04 & SuperSU
twrp-3.0.3-n4-athene_shreps.img & ElementalX-G4-1.04 & SuperSU
twrp-3.0.2-0-athene.img & ElementalX-G4-1.04 & Magiks
twrp-3.0.3-n4-athene_shreps.img & ElementalX-G4-1.04 & Magiks
Boot only into TWRP with stock recovery and then root……
Every time I flash something, my phone gets weird…...
I have those bootloops witch ends up booting the system after a minute or so or by booting into recovery….
Even by only flashing TWRP without rooting running stock i have those problems.
But if i flash the stock data the phone acts normaly:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
I am running on "Moto G4 Plus XT1640-43 ATHENE NPJ25.93-14 Stock"
Hi all I have unfortunately lost the proper baseband for my device (XT1643-indian model g4 plus 3gb/32gb)
Prior to posting this, I had my fingerprint lost too. My stupidity was flashing the june fastboot firmware I found on one of the links for motorola rsd cloud clients. :/ With the help of @echo92 i was able to revive the missing fingerprint by pushing hw.img to /dev/block/mmcblk0p43 but still the SIMs won't show up as the baseband has changed to MSM8952_70030.25.03.62.01R DFLT_FSG
I have tried flashing the modem and fsg partitions from the March 1 ROM but still no solution
Any kind of help would be appreciated
Update SIM card recognized but no network at all
tywinlannister7 said:
Update SIM card recognized but no network at all
Click to expand...
Click to collapse
Flashing the modem file for you device didn't change the baseband version? Meaning it didn't remove the suffix at the end...
What happens if you flash a complete stock ROM via fastboot for you device? One that includes all of the files...
Jleeblanch said:
Flashing the modem file for you device didn't change the baseband version? Meaning it didn't remove the suffix at the end...
What happens if you flash a complete stock ROM via fastboot for you device? One that includes all of the files...
Click to expand...
Click to collapse
Bro I already flashed the firmware again..tried the march and june firmwares both
tywinlannister7 said:
Bro I already flashed the firmware again..tried the march and june firmwares both
Click to expand...
Click to collapse
What about this FSG backup (SS, in TWRP) ? Do you have any old backups ?
____Mdd said:
What about this FSG backup (SS, in TWRP) ? Do you have any old backups ?
Click to expand...
Click to collapse
I actually had made these backups specifically for such conditions but i'm unable to find them as of now. I have been able to get the Sims working somehow with @Droidphilev 's flashable modem zip (Available here: https://forum.xda-developers.com/moto-g4-plus/how-to/fxz-flashable-stock-npjs25-93-14-4-t3623010 ). But the baseband I have after flashing this zip is M8952_70030.25.03.62.01p ATHENE_EMEA_DSDS_CUST . Let's see what can be done to revive my phone fully.
tywinlannister7 said:
I actually had made these backups specifically for such conditions but i'm unable to find them as of now. I have been able to get the Sims working somehow with @Droidphilev 's flashable modem zip (Available here: https://forum.xda-developers.com/moto-g4-plus/how-to/fxz-flashable-stock-npjs25-93-14-4-t3623010 ). But the baseband I have after flashing this zip is M8952_70030.25.03.62.01p ATHENE_EMEA_DSDS_CUST . Let's see what can be done to revive my phone fully.
Click to expand...
Click to collapse
your signal is back?
Droidphilev said:
your signal is back?
Click to expand...
Click to collapse
Yes but since the baseband version is different at all, unable to use VoLTE and hence no calls from one of the SIM cards (Jio 4G).
Sent from my Moto G4 Plus using Tapatalk
Please help
tywinlannister7 said:
Yes but since the baseband version is different at all, unable to use VoLTE and hence no calls from one of the SIM cards (Jio 4G).
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I FLASHED THE MODEM FILE SPECIFIED ABOVE, BUT STILL BASEBAND SUFFIX IS DFLT_FSG
I'M ON INDIAN XT1643
HELP PLEASE
My problem started as i was using 7.1.2 AOSP custom rom
then i switched back to MM Stock rom
Everything was fine till i received June Nougat Update
during update my phone went blank
Somewhere with the help of XDA i found a blankflash file and got bootloader back
then i flashed TWRP and wiped full system, cache, and everything
then through fastboot i installed nougat xt1643, xt1626-40-41
i tried every possible firmware, every modem file available.
Still my fingerprint and SIMs are not working
my bootloader is B1.06
I cant downgrade bootloader and gpt.bin even with unlocked bootloader, my model is switched to g4 i think
i can only flash bootloader and gpt of june update
rest all firmwares give Security Downgrade error
Help me please!!!
How did you solved the fingerprint problem.
rajatgupta1998 said:
Yes but since the baseband version is different at all, unable to use VoLTE and hence no calls from one of the SIM cards (Jio 4G).
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Try this link. I was having same problem. Solved it successfully.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
If u hav Imei num and only required baseband u try this it will work for sure has it corrected mine and others https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270/page2
I cant flash hw.img file
rajatgupta1998 said:
Hi all I have unfortunately lost the proper baseband for my device (XT1643-indian model g4 plus 3gb/32gb)
Prior to posting this, I had my fingerprint lost too. My stupidity was flashing the june fastboot firmware I found on one of the links for motorola rsd cloud clients. :/ With the help of @echo92 i was able to revive the missing fingerprint by pushing hw.img to /dev/block/mmcblk0p43 but still the SIMs won't show up as the baseband has changed to MSM8952_70030.25.03.62.01R DFLT_FSG
I have tried flashing the modem and fsg partitions from the March 1 ROM but still no solution
Any kind of help would be appreciated
Click to expand...
Click to collapse
When I push the hw file.it got struck the boot loader.and the adb command prompt struck on 100%.
rajatgupta1998 said:
I actually had made these backups specifically for such conditions but i'm unable to find them as of now. I have been able to get the Sims working somehow with @Droidphilev 's flashable modem zip (Available here: https://forum.xda-developers.com/moto-g4-plus/how-to/fxz-flashable-stock-npjs25-93-14-4-t3623010 ). But the baseband I have after flashing this zip is M8952_70030.25.03.62.01p ATHENE_EMEA_DSDS_CUST . Let's see what can be done to revive my phone fully.
Click to expand...
Click to collapse
i tried the above mention procedure but it didn't help me and i am also facing the same problem my baseband is changed to european variant 'ATHENE_EMEA_DSDS_CUST" please help me.
rajatgupta1998 said:
Hi all I have unfortunately lost the proper baseband for my device (XT1643-indian model g4 plus 3gb/32gb)
Prior to posting this, I had my fingerprint lost too. My stupidity was flashing the june fastboot firmware I found on one of the links for motorola rsd cloud clients. :/ With the help of @echo92 i was able to revive the missing fingerprint by pushing hw.img to /dev/block/mmcblk0p43 but still the SIMs won't show up as the baseband has changed to MSM8952_70030.25.03.62.01R DFLT_FSG
I have tried flashing the modem and fsg partitions from the March 1 ROM but still no solution
Any kind of help would be appreciated
Click to expand...
Click to collapse
How to revive fingerprint?
Helpme please
Baseband, Dual Sim and FP Issue
BORNIOS said:
How to revive fingerprint?
Helpme please
Click to expand...
Click to collapse
Originally Posted by anon10041998
Steps u should follow :
1. Download stock rom from this link androidfilehost.com/?fid=890278863836286757
2.Flash the stock rom
3. Restart your phone in bootloader and flash TWRP, do not boot system. Restart in TWRP
3. Download these files from drive.google.com/drive/folde...mymw-UNe9KtRNm
4. copy the files to your adb or miniboot folder.
4. Flash using the following commands
adb push modem.img /dev/block/mmcblk0p1
adb push fsg.img /dev/block/mmcblk0p16
adb push hw.img /dev/block/mmcblk0p43
5.Go to ur bootloader again. with fastboot. and flash with that same latest stock rom and check. ur baseband once.
6. I think this baseband will come as EMEA_CUST. But it will get signal network.
7. Now download this zip cloud.mail.ru/public/2Xrm/3vbzbxX5U
8. unzip pws is lenovo-forums.ru
9. Copy all files in ADB folder and delete all previous files
10. Put device into bootloader mode
11. Run programutags --> select APAC --> select INDIA
12. Done
Urgent help
I'm unable to recover sim card and fingerprint (after rooting) option in setting on my Moto g4 plus XT1643 3/32gb Indian version.unrooted successfully currently on stock rom. But no difference. Need help. Please email me on [email protected].
Anand9552 said:
I'm unable to recover sim card and fingerprint (after rooting) option in setting on my Moto g4 plus XT1643 3/32gb Indian version.unrooted successfully currently on stock rom. But no difference. Need help. Please email me on [email protected].
Click to expand...
Click to collapse
do you see any baseband
please share pic
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.
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