Related
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:
UPDATE (07-Jan-2017):
If your OnePlus 2's IMEI#2 = 0, (IMEI#1 is showing correct IMEI)
Because you run these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Then,
A fix has been made into this zip file.
https://www.androidfilehost.com/?fid=529152257862693598
Kindly thank Tony.L & Crystal.Z from OnePlus OOS team.
You have to be on OOS 3.5.6 (Clean-Flashed, non-rooted, from whatever ROM you are currently on).
I had TWRP Hybrid Recovery v3.4 installed.
IMEI#2 will come back again.
Now, Remember to backup EFS using terminal method.
& DONT erase modem ever again.
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
I would appreciate your help.
Click to expand...
Click to collapse
***************************************
lockmunk said:
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
Click to expand...
Click to collapse
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Tunatje said:
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Click to expand...
Click to collapse
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Spannaa said:
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Click to expand...
Click to collapse
True. Done it myself through terminal. Forgot about the dual sim :laugh:
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
***************************************
I would appreciate your help.
Click to expand...
Click to collapse
Did you managed to get any info on that??
I also encountered the exactly same issue..
ashu01 said:
Did you managed to get any info on that??
I also encountered the exactly same issue..
Click to expand...
Click to collapse
No Fix, as of yet !
Somebody said, he flashed modem files from beanstalk Rom thread, & that fixed the missing IMEI issue.
I haven't tried it yet,
If you try it, & it fixes this problem, update me on thia thread !
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
Can u send me persist.img pls
My email is [email protected]
Would be better, if you upload persist file here.
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
pitrus- said:
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
Click to expand...
Click to collapse
Before flashing H2Os firmware,
What was your OP2 running ?
Also can you list all links to files, which helped you.
Just an hour ago, i flashed "ResurrectionRemix-6.0-OOS-2.2.1-Modem.zip" on my OnePlus 2 (running Oxygen OS 3.1.0 with TWRP) & it went into bootloop.
So now i'm downloading @Spannaa 's "Oxygen OS 2.1.1 fastboot.zip" , to make my phone working again.
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
I though my phone was fine, then I noticed my swedish BankID just didn't want to work. Turns out my SIM2 has null IMEI just like yours. Tried Qualcomm restore to OOS 3.0.2 but still IMEI2:0, so it looks like trying out the H2OS 2.5 beta firmware and going back was a real killer for my phone. I get signal on both SIM cards and strangely I can call using both SIM cards even though one is showing no IMEI
Update
After analyzing the nv data of my phone, I can tell that the IMEI for SIM card 1 is there, and there does not seem to be any address register for a second IMEI so the phone must figure this out itself. For me the first IMEI ends with a 99 and second with a 81 which means a difference of -18, perhaps second IMEI is always -18 hexadecimal from the first and therefore automatically calculated and registered by the modem firmware?
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
pryggi said:
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
Click to expand...
Click to collapse
Yes, it's an A2003 European model. If only I had a dump of a working A2003 NV Data so I could find the difference between them. Whoever could give me this could just zap out 00550 NV Item (IMEI) so as not to share it with me. That would tell us which NV Items to change to swap between single och dual sim card modell.
@pitrus-
I have the IMEIs on my OP2 still intact, I have not flashed latest H2OS beta, nor have I used the fastboot erase/format commands. So I can analyse the /dev/block/mmcblk0p17 and /dev/block/mmcblk0p18 dd dumps. Could you tell me which tools to use, or how can I edit out my IMEIs?
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
osr.arora said:
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
Click to expand...
Click to collapse
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
pitrus- said:
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
Click to expand...
Click to collapse
i also used fastboot erase command..and in the same situation of showing imei2 0.
do you think the oos update will have a fix for this issue??
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
Hello everyone, i installed the leaked soak test with the "apply update from SD card" on stock recovery after locking my bootloader.
One week later, i unlocked it again and flashed TWRP for rooting with magisk.
Even with root tweaks i still face problems with soak 8.1, due to the lack of custom kernels.
So i decided to flash Stock N (1st April) with the TWRP Flashable zip from @Jleeblanch , how i avoid IMEI loss doing that? If i backup Oreo's EFS with TWRP, it will be compatible if i try to restore it after flashing, or it's not even necessary?
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Heeth21 said:
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat.
Click to expand...
Click to collapse
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
xSamukaBRx said:
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
Click to expand...
Click to collapse
Read the second post again, I have edited it.
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
I kinda fear it auto-updating, so i'll make sure to delete the "3c_ota" app from /priv-app
EDIT: Already know the risks of taking OTA with unlocked bootloader or after downgrade...
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
xSamukaBRx said:
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
Click to expand...
Click to collapse
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Heeth21 said:
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Click to expand...
Click to collapse
Even through i just want a pure lineage OS instead of a custom based on it (too many stuff comes with a risk, right?), i better not try...
Hello guys,
I bought a Mi 9T by a reseller couple of days ago and noticed how the auto-brightness was not working. Same for auto-rotation.
I found out through CIT that the accelerometer and gyroscope sensors weren't responding, calibrating them also not possible.
The installed ROM was 11.0.4.0 Global Stable.
I already looked through multiple threads on XDA since this seems to be a common issue and tried to solve the problem as instructed.
1) Unlocked Bootloader
2) Installed TWRP (3.3.1)
3) Flashed persist (after mounting it) with the persist.img I extracted from the 11.0.4.0 Global Stable Fastboot ROM
The process seemed to be fine, but after multiple reboots, CIT still showed that the sensors didn't wake up.
I then flashed the 10.3.11 Global ROM via MiFlash and flashed persist.img again (sensors still dead) .
Other things that were posted and that I've tried that couldn't solve the issue:
a) simg2img /sdcard/persist.img /sdcard/persist_EXT4.img <and> dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
b) Changing the persist lines in the Fastboot ROMs rawprogram0.xml and flash_all.sh .... only that there are no such lines in the several ROMs I've downloaded.
I've now rooted the phone in order to copy some sensor files to /persist/sensors as described in this thread (https://forum.xda-developers.com/mi-mix-2/help/mi-mix-2-sensors-expect-proximity-sensor-t3777015),
but could not find a persist folder in my root directory.
Is there no hope at all?
I am having the same issue, still could not fix it.
kinkinoa said:
Hello guys,
I bought a Mi 9T by a reseller couple of days ago and noticed how the auto-brightness was not working. Same for auto-rotation.
I found out through CIT that the accelerometer and gyroscope sensors weren't responding, calibrating them also not possible.
The installed ROM was 11.0.4.0 Global Stable.
I already looked through multiple threads on XDA since this seems to be a common issue and tried to solve the problem as instructed.
1) Unlocked Bootloader
2) Installed TWRP (3.3.1)
3) Flashed persist (after mounting it) with the persist.img I extracted from the 11.0.4.0 Global Stable Fastboot ROM
The process seemed to be fine, but after multiple reboots, CIT still showed that the sensors didn't wake up.
I then flashed the 10.3.11 Global ROM via MiFlash and flashed persist.img again (sensors still dead) .
Other things that were posted and that I've tried that couldn't solve the issue:
a) simg2img /sdcard/persist.img /sdcard/persist_EXT4.img <and> dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
b) Changing the persist lines in the Fastboot ROMs rawprogram0.xml and flash_all.sh .... only that there are no such lines in the several ROMs I've downloaded.
I've now rooted the phone in order to copy some sensor files to /persist/sensors as described in this thread (https://forum.xda-developers.com/mi-mix-2/help/mi-mix-2-sensors-expect-proximity-sensor-t3777015),
but could not find a persist folder in my root directory.
Is there no hope at all?
Click to expand...
Click to collapse
The method you mentioned requires flashing the fastboot/tgz stock rom
Anyway, in TWRP, mount Persist and then in Advanced, File manager, you can see the Persist PARTITION (and its folders) - as on the screenshot