Database Users

SOLVED: Flashed TruPureXMM rom in Indian dualsim XT1572 and now No sim detection

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:

Baseband unknown

My nexus 6p is not showing IMEI and also showing unknown for Baseband version. I have no efs backup. Tried reflashing stock firmware, erasing modemst1, modemst2, modem, fsg, custom rom (RR), and tried them in different combinations. Yet it still shown baseband unknown. :crying:
Is there any way I can get modemst1 and modemst2? Please suggest a solution to fix this. Warranty over a week before this happened. And it happened out of nowhere. :crying:

Baseband is the radio, isn't it? You can get the latest image from here:
http://forum.xda-developers.com/nexus-6p/general/nmf26f-official-7-1-1-radio-vendor-t3513430
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
You might want to do a complete install of the latest system image if flashing the radio doesn't solve your problem:
https://developers.google.com/android/images
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
I'm not sure that either of these will restore your IMEI, however. Do you have a CDMA or GSM phone?

jhs39 said:
Baseband is the radio, isn't it? You can get the latest image from here:
http://forum.xda-developers.com/nexus-6p/general/nmf26f-official-7-1-1-radio-vendor-t3513430
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
You might want to do a complete install of the latest system image if flashing the radio doesn't solve your problem:
https://developers.google.com/android/images
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
I'm not sure that either of these will restore your IMEI, however. Do you have a CDMA or GSM phone?
Click to expand...
Click to collapse
Thanks for the reply. I tried both of em. Is there any way i can get fsg, modemst1, modemst2 files? Im thinking of finding another Nexus 6P and copying its files and somehow editing the IMEI information using some HEX editor and then uploading to my phone.
If it is alright then can you or someone send me their modemst1, modemst2 and fsg files after editing their IMEI no. ?
This site provide how to edit your IMEI: androidbrick (Change it to something like 876543210123456)
Btw my phone is LTE/GSM

I think if you can get a hold of someone's EFS backup and restore it on your phone it would restore your missing IMEI number. The problem is finding someone who is willing to provide you with a copy of their EFS backup.

I was able to get the IMEI number for my Nexus 6P from Google Dashboard:
http://www.google.com/settings/dashboard
Once you know your IMEI you may be able to restore it with an app like IMEI Tweak.

jhs39 said:
I think if you can get a hold of someone's EFS backup and restore it on your phone it would restore your missing IMEI number. The problem is finding someone who is willing to provide you with a copy of their EFS backup.
Click to expand...
Click to collapse
Yes. I'm trying to find someone who can provide me with modem files.

jhs39 said:
I was able to get the IMEI number for my Nexus 6P from Google Dashboard:
http://www.google.com/settings/dashboard
Once you know your IMEI you may be able to restore it with an app like IMEI Tweak.
Click to expand...
Click to collapse
I have the box which has the IMEI. I tried some apps like IMEI Tweaks. Even tried some apps through XPOSED framework. Nothing worked. Hope someone gives me the modem files.

pronuba66 said:
My nexus 6p is not showing IMEI and also showing unknown for Baseband version. I have no efs backup. Tried reflashing stock firmware, erasing modemst1, modemst2, modem, fsg, custom rom (RR), and tried them in different combinations. Yet it still shown baseband unknown. :crying:
Is there any way I can get modemst1 and modemst2? Please suggest a solution to fix this. Warranty over a week before this happened. And it happened out of nowhere. :crying:
Click to expand...
Click to collapse
How did you erase modemst1 & modemst2? From an ADB shell like this? I can't find it to save my life, but I did read if the EFS partitions are formatted properly they will rebuild from firmware on first boot. You stated phone is out of warranty, but did you actually get denied when you called Huawei? There may be an unadvertised warranty/RMA for your phone's current state, or they may be able to suggest a fix.

v12xke said:
How did you erase modemst1 & modemst2? From an ADB shell like this? I can't find it to save my life, but I did read if the EFS partitions are formatted properly they will rebuild from firmware on first boot. You stated phone is out of warranty, but did you actually get denied when you called Huawei? There may be an unadvertised warranty/RMA for your phone's current state, or they may be able to suggest a fix.
Click to expand...
Click to collapse
I erased using dd command as stated in your link provided. But even after several reboots, and several uploads of different ROMS, it still is zero (Both modemst1 and modemst2).
My phone was bought from a different country, and hence warranty was not accepted in my country. Even the people at the Huawei service center was not very helpful.
I'm actually waiting for my friend to root his phone(unlocking required which will erase the user data) so that I can get the modem files. If fixed I'll message you.

pronuba66 said:
I erased using dd command as stated in your link provided. But even after several reboots, and several uploads of different ROMS, it still is zero (Both modemst1 and modemst2).
My phone was bought from a different country, and hence warranty was not accepted in my country. Even the people at the Huawei service center was not very helpful.
I'm actually waiting for my friend to root his phone(unlocking required which will erase the user data) so that I can get the modem files. If fixed I'll message you.
Click to expand...
Click to collapse
Good luck.
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
jhs39 said:
Good luck.
Click to expand...
Click to collapse
From what I've read if your friend makes an EFS backup you can use that to restore yours. If the modem restore doesn't work you might want to try that,

pronuba66 said:
I erased using dd command as stated in your link provided. But even after several reboots, and several uploads of different ROMS, it still is zero (Both modemst1 and modemst2).
My phone was bought from a different country, and hence warranty was not accepted in my country. Even the people at the Huawei service center was not very helpful.
I'm actually waiting for my friend to root his phone(unlocking required which will erase the user data) so that I can get the modem files. If fixed I'll message you.
Click to expand...
Click to collapse
Any solution for this? I also have imei unknown, baseband unknown issue. I don't have an efs backup either. Also flashed stock rom, but it didn't help. Any suggestions would be really appreciated.

chathura2020 said:
Any solution for this? I also have imei unknown, baseband unknown issue. I don't have an efs backup either. Also flashed stock rom, but it didn't help. Any suggestions would be really appreciated.
Click to expand...
Click to collapse
Hi,
You can try this:
Find someone having the same firmware. Root his phone and download all the partitions from his phone (from "/dev/block/platform/soc.0/f9824900.sdhci/by-name" using dd command or adb pull (in root mode). To change the IMEI from his to yours, use a hex editor and edit the IMEI in one of the partitions (I think it was in modemst1 or modem or devinfo partition).
I have tried this but my mobile was bought from UAE and Indian firmware did not work. But that fixed some restart issue, heating problem and the phone was more stable which implied the problem was definitely some corrupted partitions.
If you get it fixed please do tell me. Good luck.
Please do keep backup of your partitions

pronuba66 said:
Hi,
You can try this:
Find someone having the same firmware. Root his phone and download all the partitions from his phone (from "/dev/block/platform/soc.0/f9824900.sdhci/by-name" using dd command or adb pull (in root mode). To change the IMEI from his to yours, use a hex editor and edit the IMEI in one of the partitions (I think it was in modemst1 or modem or devinfo partition).
I have tried this but my mobile was bought from UAE and Indian firmware did not work. But that fixed some restart issue, heating problem and the phone was more stable which implied the problem was definitely some corrupted partitions.
If you get it fixed please do tell me. Good luck.
Please do keep backup of your partitions
Click to expand...
Click to collapse
My phone is going through exact same problem. My device was stuck in bootloop I got it fixed from a market place and my device would not show any carrier signals or my imei. How can I get modem files or what is a fix to it? Please help.

hkingpro said:
My phone is going through exact same problem. My device was stuck in bootloop I got it fixed from a market place and my device would not show any carrier signals or my imei. How can I get modem files or what is a fix to it? Please help.
Click to expand...
Click to collapse
In theory the Nexus 6P should rebuild the EFS Partitions if you overwrite them with zeros.
I used the following to fix my 6P back when TWRP v3.0.2-1 had a bug that restored the EFS1 partition to both EFS slots, causing the phone to not boot.
Try this:
Boot your Nexus 6P into TWRP;
Plug the phone into a PC that has ADB tools installed;
Then on PC, open Command Prompt with access to ADB and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Let me know if this works for you.

defcondev said:
In theory the Nexus 6P should rebuild the EFS Partitions if you overwrite them with zeros.
I used the following to fix my 6P back when TWRP v3.0.2-1 had a bug that restored the EFS1 partition to both EFS slots, causing the phone to not boot.
Try this:
Boot your Nexus 6P into TWRP;
Plug the phone into a PC that has ADB tools installed;
Then on PC, open Command Prompt with access to ADB and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Let me know if this works for you.
Click to expand...
Click to collapse
THANK YOU SO MUCH FOR YOUR REPLY. I tried this but it did not work for me brother. I have been searching day and night for this but not getting any solution for this. I was browsing Xda the other day and found a thread https://forum.xda-developers.com/nexus-6p/help/lost-imei-sim-error-t3282545 in comments section Tyson568 has shared a link which I think might be EFS modem files? Do you think that can help? If that can how can I flash them?

hkingpro said:
THANK YOU SO MUCH FOR YOUR REPLY. I tried this but it did not work for me brother. I have been searching day and night for this but not getting any solution for this. I was browsing Xda the other day and found a thread https://forum.xda-developers.com/nexus-6p/help/lost-imei-sim-error-t3282545 in comments section Tyson568 has shared a link which I think might be EFS modem files? Do you think that can help? If that can how can I flash them?
Click to expand...
Click to collapse
Have you tried flashing a factory image to your 6P?
If not, I would backup all of your data to a computer and flash a stock factory image to your 6P and see if this resolves the issue.
You can find the images and instructions at the link below under the section titled "angler for Nexus 6P"
Make sure to NOT re-lock the bootloader at this point (just skip that step in the flashing instructions).
Keep in mind, this will remove TWRP from your 6P and revert back to the stock Recovery - keep the stock recovery and boot the 6P fully to see if the issue is resolved. If your IMEI returns, you can then flash TWRP and backup your EFS partitions.
https://developers.google.com/android/images

defcondev said:
Have you tried flashing a factory image to your 6P?
If not, I would backup all of your data to a computer and flash a stock factory image to your 6P and see if this resolves the issue.
You can find the images and instructions at the link below under the section titled "angler for Nexus 6P"
Make sure to NOT re-lock the bootloader at this point (just skip that step in the flashing instructions).
Keep in mind, this will remove TWRP from your 6P and revert back to the stock Recovery - keep the stock recovery and boot the 6P fully to see if the issue is resolved. If your IMEI returns, you can then flash TWRP and backup your EFS partitions.
https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried multiple Images but none of them worked. My phone was bootlooping again and again and then finally I followed this thread. I flashed 8.0 factory image and flashed rest of images suggested by this thread and my phone booted up. I don't know what to do here.

hkingpro said:
I tried multiple Images but none of them worked. My phone was bootlooping again and again and then finally I followed this thread. I flashed 8.0 factory image and flashed rest of images suggested by this thread and my phone booted up. I don't know what to do here.
Click to expand...
Click to collapse
I had same issue on my OnePlus X. I kept backing up and restoring EFS partion everytime I needed a restore which now know not suppose to do. Unknown baseband and no imei. Anyways the way I fixed it was simply booting into bootloader mode, fastboot command window type
"fastboot erase modemst1 "
"fastboot erase modemst2 "
I never tested on my Nexus 6p so use at own risk.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[GUIDE] How to install official Global Rom V9.6.8.0.OEDMIFD on Antirollback device

NOTES:
- This will fix the modem on the global rom, you will be able to call and use the internet.
- I know MIUI 10.0.1.0.OEDMIFH has been released. If you have no problem with MIUI 10 AND with Antirollback, just use the fastboot version and flash that.
- If you want MIUI 10.0.1.0.OEDMIFH firmwareless go to @yshalsager thread and flash that instead of my MIUI 9 fw-less rom (installation process is the same)
- This thread is useful for people who want Global Stable MIUI 9 on Mi Max 3 with a working modem.
- If you installed MIUI 9.6.6.0.OEDMIFD fw-less from here before, just download the MIUI 9.6.8.0.OEDMIFD / 10.0.1.0.OEDMIFH FW-LESS and flash that above your rom using TWRP.
- if you install this rom on a non-Antirollback device, make sure not to update to MIUI 10 from updater or you will get Antirollback.
- if you have antirollback and you want this rom, follow the guide below and dont update to MIUI 10 if you prefer MIUI 9.
- V9.6.8.0.OEDMIFD has Antirollback, So people who want to have less problems with their rom, you can flash the full rom with the firmware-update folder instead of the fw-less one as you already have
antirollback, and you will get the correct firmware for your phone
- Read more about Antirollback here: here
Installation guide:
NOTE: By flashing this you agree that Im not responsible for any bricking situation that might happen because of this process!
YOU MUST HAVE UNLOCKED BOOTLOADER
1. Go to twrp on your device and wipe everything! (system,vendor,internal .....)
2. Change your data partition to F2FS
3. Reboot to twrp and format userdata
4. Flash China Stable 9.6.12.0 via Fastboot (or 9.6.11.0 if you dont have Antirollback because 9.6.12.0 has antirollback)
5. Flash twrp and reboot to it
6. in TWRP wipe everything (system,vendor,internal .....)
7. Change your data partition to F2FS
8. Reboot to twrp and format userdata
9. Change the data partition back to EXT4
10. Reboot one last time to TWRP and copy the fw-less rom to your internal storage
11. flash the fw-less rom / (full rom 9.6.8.0 if you already have antirollback and you want MIUI 9)
12. wipe cache/ dalvik
13. mount cust partition in twrp, go to the file explorer and go to the cust folder from the root of the device
15. delete everything in that folder
17. delete the rom from your internal storage using MTP
16. boot to fastboot mode and flash the cust.img using "fastboot flash cust cust.img"
17. delete all the files on your internal storage using MTP
18. reboot, it will say reset phone, click on it, wait until the device boots and enjoy!
Downloads
fw-less 9.6.8.0.OEDMIFD Rom: here
Cust Partition Fix (Cust.img): here
Known Problems:
- The software keys sometimes fail
- The play store isnt certified (safetynet doesnt pass) (can be fixed using magisk root)

Lets reserve one comment

thank your time and work, want test when i have some time, thanks X 1000

Thank you for the guide!
Sent from my MI MAX 3 using Tapatalk

If you are not on an antirollback device (Currently on china 9.6.11.0) How would I go about flashing?

omniphil said:
If you are not on an antirollback device (Currently on china 9.6.11.0) How would I go about flashing?
Click to expand...
Click to collapse
same as the antirollback device.
Flashing the normal rom will cause problems and might not work without the cust fix.
If you dont flash the fw-less rom, the rom will update the firmware (firmware-update folder) to its own version which will brick your modem again.

omer919 said:
same as the antirollback device.
Flashing the normal rom will cause problems and might not work without the cust fix.
If you dont flash the fw-less rom, the rom will update the firmware (firmware-update folder) to its own version which will brick your modem again.
Click to expand...
Click to collapse
Ok, so I followed this exactly with the exception of the step 17, There were no files on on internal storage showing up in MTP at all?
Also on step 4 I flashed the China rom successfully but when finished I did not restart the phone and let it boot up and go thru the initial setup of the rom, I just flashed the China rom and proceeded to the next step.
But it certainly gives me the 9.6.6.0 global rom, however the radio is now broken again, I cant get out to the internet. This really makes no sense? On the China rom the radio certainly works fine.
Any ideas? What a frustrating phone this has been, I'm sort of mad at the vendors putting these fake roms on here with non working modems....
There's go to be a way to flash just the modem firmware from the China rom?

omniphil said:
Ok, so I followed this exactly with the exception of the step 17, There were no files on on internal storage showing up in MTP at all?
Also on step 4 I flashed the China rom successfully but when finished I did not restart the phone and let it boot up and go thru the initial setup of the rom, I just flashed the China rom and proceeded to the next step.
But it certainly gives me the 9.6.6.0 global rom, however the radio is now broken again, I cant get out to the internet. This really makes no sense? On the China rom the radio certainly works fine.
Any ideas? What a frustrating phone this has been, I'm sort of mad at the vendors putting these fake roms on here with non working modems....
There's go to be a way to flash just the modem firmware from the China rom?
Click to expand...
Click to collapse
I have none of the stated issues.
Follow the guide again from step 1 and this time setup the phone on 9.6.11.0 (dont let it update to 9.6.12.0)
Make sure that on fastboot you choose clean all and not save my data

omer919 said:
I have none of the stated issues.
Follow the guide again from step 1 and this time setup the phone on 9.6.11.0 (dont let it update to 9.6.12.0)
Make sure that on fastboot you choose clean all and not save my data
Click to expand...
Click to collapse
Ok so once 9.6.11.0 flashes, let the phone boot up and go through all the initial setup, then reboot in TWRP and continue. I will do that...
Yes, on fast boot I am choosing "Clean All"
How about step 17? I don't seem to see what i'm supposed to be doing there?

omniphil said:
Ok so once 9.6.11.0 flashes, let the phone boot up and go through all the initial setup, then reboot in TWRP and continue. I will do that...
Yes, on fast boot I am choosing "Clean All"
How about step 17? I don't seem to see what i'm supposed to be doing there?
Click to expand...
Click to collapse
after you flash the rom, you need to mount the cust partition.
after that you need to use the file manager in twrp to delete everything in the cust partition and then copy all the files from the cust fix zip to the cust folder on your phone using the twrp file explorer. on 17 I meant that you delete the files on your Internal storage that you used to copy to the cust folder so you wont have any files left before running the system for the first time

omer919 said:
after you flash the rom, you need to mount the cust partition.
after that you need to use the file manager in twrp to delete everything in the cust partition and then copy all the files from the cust fix zip to the cust folder on your phone using the twrp file explorer. on 17 I meant that you delete the files on your Internal storage that you used to copy to the cust folder so you wont have any files left before running the system for the first time
Click to expand...
Click to collapse
I certainly mounted the Cust partition and copy everything copied over, I actually copied the Cust Fix files from an sd card to internal so there was nothing to clean up in my case.
Ok, I am crossing my fingers here
---------- Post added at 11:11 AM ---------- Previous post was at 10:41 AM ----------
So while I was restoring my data from google I was certainly getting text messages. A phone call worked too. However after all my data finished restoring from my google account and I rebooted I now have no cell signal again.
I couldn't imagine something that gets restored would mess up the cellular connection, but I am going to have to wipe and start over and not restore anything from my account to see if that helps at all...
Ugh....

omniphil said:
I certainly mounted the Cust partition and copy everything copied over, I actually copied the Cust Fix files from an sd card to internal so there was nothing to clean up in my case.
Ok, I am crossing my fingers here
---------- Post added at 11:11 AM ---------- Previous post was at 10:41 AM ----------
So while I was restoring my data from google I was certainly getting text messages. A phone call worked too. However after all my data finished restoring from my google account and I rebooted I now have no cell signal again.
I couldn't imagine something that gets restored would mess up the cellular connection, but I am going to have to wipe and start over and not restore anything from my account to see if that helps at all...
Ugh....
Click to expand...
Click to collapse
basic rule number 1, always start clean without any restores if you want 0 bugs/problems

omer919 said:
basic rule number 1, always start clean without any restores if you want 0 bugs/problems
Click to expand...
Click to collapse
Copy that, I will report back with the clean start...
---------- Post added at 12:09 PM ---------- Previous post was at 11:56 AM ----------
Negative... Still no service....
Maybe I just have a flaky phone? Tho i do have service fine with the China rom.
I guess i'll just have to wait until there is a flashable global rom complete with modem and stuff.

Thank for the big effort. I made it following this guide.
But I think this is MIUI 9 but I like MIUI 10 much more.
So I revert back to EU 8.9.6 and I satisfy with this.

fordarm said:
Thank for the big effort. I made it following this guide.
But I think this is MIUI 9 but I like MIUI 10 much more.
So I revert back to EU 8.9.6 and I satisfy with this.
Click to expand...
Click to collapse
I'M using eu 8.9.6 and stock sms app problem do you have it too.?
but in 8.8.9 it was OK

azhar63 said:
I'M using eu 8.9.6 and stock sms app problem do you have it too.?
but in 8.8.9 it was OK
Click to expand...
Click to collapse
I am using special version which already fix SMS issue and also remove ARB related stuffs.
You can download that from https://drive.google.com/file/d/1AejzODOxusDfeD125KbClDnJGHbHPh-U/view

Official global rom version is 9.6.7.0
I got an information from Korean xiaomi community that the official global rom version is 9.6.7.0 but not 9.6.6.0.
He bought it from the aliexpress and seller shipped it with sealed package. And it put "Global Versiso" sticker on the box.
Here I attach the ROM version image.
We better wait until official site put mi max 3 global rom there.

fordarm said:
I got an information from Korean xiaomi community that the official global rom version is 9.6.7.0 but not 9.6.6.0.
He bought it from the aliexpress and seller shipped it with sealed package. And it put "Global Versiso" sticker on the box.
Here I attach the ROM version image.
We better wait until official site put mi max 3 global rom there.
Click to expand...
Click to collapse
Thats a real global rom.
Its not uploaded to xiaomi's database yet so its unavailable for download
just like 9.6.8.0 which is also real but not released yet.

omer919 said:
Thats a real global rom.
Its not uploaded to xiaomi's database yet so its unavailable for download
just like 9.6.8.0 which is also real but not released yet.
Click to expand...
Click to collapse
I don't understand why Xiaomi doesn't support OTA on the mi max3 with former glabal rom. Really shame.

So let's say i managed to flash on my non anti-rolled back mi max 3 with your steps, in future updates can i just update normally OTA?

H918 Stuck on secure startup "decryption unsuccessful" on boot

after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.

noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information

mikekote666 said:
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
Click to expand...
Click to collapse
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.

noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918

mikekote666 said:
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
Click to expand...
Click to collapse
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.

noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
you need to format data first time

noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
Format data

gandyprakoso said:
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Format data
Click to expand...
Click to collapse
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)

noddledizzy said:
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
Click to expand...
Click to collapse
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L.. and since your TWRP has been nuked, youll have to reflash TWRP again yes? ?
Or, if youbdont want to downgrade TWRP, you can use AOSP based rom such as LOS15.1.. i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.

gandyprakoso said:
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L..
Or, you can use AOSP based rom such as LOS15.1.
i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
Click to expand...
Click to collapse
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep

noddledizzy said:
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
Click to expand...
Click to collapse
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591

gandyprakoso said:
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
Click to expand...
Click to collapse
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?

noddledizzy said:
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
Click to expand...
Click to collapse
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051

gandyprakoso said:
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
Click to expand...
Click to collapse
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.

noddledizzy said:
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
Click to expand...
Click to collapse
Ok then and happy flashing m8 ?

noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
Where? Right in the portion where it says Known Issues of the first link.
Downgrading TWRP to 3.2.3-4 will fix it. I had the same issue.

Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob

frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
From TWRP thread:
Changed one last thing to try to fix stock Oreo decryption.
There were an upstream TWRP change that should fix the issue where formatting was still leaving /data encrypted as well (this was actually in the last build, but I didn't notice it then)
Click to expand...
Click to collapse
If you still have your non-Encryption-supporting TWRP as download mode, wipe data from there. For some reason which was documented in the TWRP thread, most versions of V20 TWRP doesn't remove the encryption flag even on a full wipe. I've gone through the pain several times, but here's roughly what I went through about a month ago. It's possible that using the latest TWRP may allow you to skip straight to step 8. As of this latest wipe, I'm finally at a point again where my phone works properly and TWRP can still see my data.
Basic process to hopefully have a working ongoing phone and TWRP:
1. Reboot to download-mode TWRP
2. Wipe dalvik/cache/data from the older download-mode TWRP
3. Factory reset with YES, still in older download-mode TWRP
4. Reboot to system; it should give you the new-system-setup past the Decryption unsuccessful screen on your wiped device
5. Setup without a Google account or fingerprint
6. Reboot back to recovery, not download TWRP; use download mode to get there if you need to
7. Flash the latest TWRP version from the thread (no older than October 25, 2019)
8. Reboot back to recovery
9. Wipe dalvik/cache/data
10. Reboot back to system
11. Setup as you like
12. Reboot back to recovery and make sure you can see your storage
If it gets a decryption error on latest TWRP at step 12 and you can't see data while in Recovery, try skipping adding a fingerprint during setup (run through steps 8-12, no fingerprint on 11) and see if that fixes it.

frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
My solution turned out to be formatting /data. Wiping it was apparently not really wiping it clean. Formatting it got me back to a working phone, though I had to re-install everything.
Thanks everyone for the help!
Rob

anyone knows how to fix fingerprints not working? h990 oreo rom mk2000 kernel is there any fix?
do i need to return to nougat but than what? please help
edit: was able to fix that by flashing nougat modem
now wifi wont turn on tho anyone know how to fix?