Database Users

[Q] Galaxy Note 3 (IMEI Lost) Need help

Hey Guys!
Firstly, I know this same thread has been made for other devices. Most of which have solutions, but these do not work for me. I really need your help with my problem!
The Problem: My GN3 has lost its IMEI, the EFS folder might have gotten corrupt somehow. But by a stroke of bad luck, the IMEI turned to unknown and no methods seem to solve this.
Thus far I have tried changing the IMEI with NV Tools and EFS Pro. None of which work, I tried generating a new file and flashing it on, that did also not help.
It was stock 4.4.2 Samsung, rooted. We sent it in to a service center, but since Knox now says 0x1 they want to charge us R3500 (~$300) to repair it.
Upon inspection, I noticed from my EFS folder that all files starting with 'nv' was gone. SO I copied these from my rooted Note 2 and placed them in the folder. Idea being that I could just change the IMEI using NV Tools, as it didn't work otherwise. This however did not work.
The only sollution I can think of, would be for someone to make a backup (using TWRP or CWM) of their EFS folder, then for me to restore it and then change the IMEI with NV Tools.
I promise I did not steal this phone, and it is not blacklisted or anything. Ill send any who might help me a picture of the IMEI on the back of the phone + the original box and the receipt if they doubt me.
I DON'T WANT YOUR IMEI NUMBER, but I need a full Note 3 EFS folder with the original files, so I can attempt to fix mine.
If anyone has a different solution I'm all ears, and up for anything.

cant u just flash stock in odin.

masze said:
cant u just flash stock in odin.
Click to expand...
Click to collapse
I have done that, all it has done is increase the flash counter from 1 to 2. And remove my root. The EFS is broken (somehow) and I can't figure out how to fix it....

Odin upload the latest version of the modem

Hitman7987 said:
Hey Guys!
Firstly, I know this same thread has been made for other devices. Most of which have solutions, but these do not work for me. I really need your help with my problem!
The Problem: My GN3 has lost its IMEI, the EFS folder might have gotten corrupt somehow. But by a stroke of bad luck, the IMEI turned to unknown and no methods seem to solve this.
Thus far I have tried changing the IMEI with NV Tools and EFS Pro. None of which work, I tried generating a new file and flashing it on, that did also not help.
It was stock 4.4.2 Samsung, rooted. We sent it in to a service center, but since Knox now says 0x1 they want to charge us R3500 (~$300) to repair it.
Upon inspection, I noticed from my EFS folder that all files starting with 'nv' was gone. SO I copied these from my rooted Note 2 and placed them in the folder. Idea being that I could just change the IMEI using NV Tools, as it didn't work otherwise. This however did not work.
The only sollution I can think of, would be for someone to make a backup (using TWRP or CWM) of their EFS folder, then for me to restore it and then change the IMEI with NV Tools.
I promise I did not steal this phone, and it is not blacklisted or anything. Ill send any who might help me a picture of the IMEI on the back of the phone + the original box and the receipt if they doubt me.
I DON'T WANT YOUR IMEI NUMBER, but I need a full Note 3 EFS folder with the original files, so I can attempt to fix mine.
If anyone has a different solution I'm all ears, and up for anything.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2985624

Rosli59564 said:
http://forum.xda-developers.com/showthread.php?t=2985624
Click to expand...
Click to collapse
Ok, what I found out as a solution was to delete EFS folder. Android will rebuild it! BUT: My EFS and Baseband are still gone. I reflashed stock (again) using Odin. No Dice. My NV_DATA, NV_CORE ect files are gone!
And IMEI isnt coming back.
If anyone has a spare EFS backup, or a script or something that i can flash to make my device have those files again I would appreciate it very much.

Hitman7987 said:
Ok, what I found out as a solution was to delete EFS folder. Android will rebuild it! BUT: My EFS and Baseband are still gone. I reflashed stock (again) using Odin. No Dice. My NV_DATA, NV_CORE ect files are gone!
And IMEI isnt coming back.
If anyone has a spare EFS backup, or a script or something that i can flash to make my device have those files again I would appreciate it very much.
Click to expand...
Click to collapse
Check your inbox
---------- Post added at 03:17 AM ---------- Previous post was at 02:31 AM ----------
Hitman7987 said:
Ok, what I found out as a solution was to delete EFS folder. Android will rebuild it! BUT: My EFS and Baseband are still gone. I reflashed stock (again) using Odin. No Dice. My NV_DATA, NV_CORE ect files are gone!
And IMEI isnt coming back.
If anyone has a spare EFS backup, or a script or something that i can flash to make my device have those files again I would appreciate it very much.
Click to expand...
Click to collapse
The following might be uotdated but no harm to try anyway(Can't copy the link so i copied everything)
1. Install Stock firmware via Odin, then re-run auto-root (to regain root of course)*
2. Install TWRP 2.6.3.2 via odin, reboot to recovery.
3. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12*
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Do a factory reset, reboot system

Rosli59564 said:
Check your inbox
---------- Post added at 03:17 AM ---------- Previous post was at 02:31 AM ----------
The following might be uotdated but no harm to try anyway(Can't copy the link so i copied everything)
1. Install Stock firmware via Odin, then re-run auto-root (to regain root of course)*
2. Install TWRP 2.6.3.2 via odin, reboot to recovery.
3. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12*
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Do a factory reset, reboot system
Click to expand...
Click to collapse
Ok I did that, and after a fresh setup. I still have the same issues. LOOOOOONG Reboot, and finally nothing. IMEI still gone. SIM Card not present even though it is in. Other ideas?

Hitman7987 said:
Ok I did that, and after a fresh setup. I still have the same issues. LOOOOOONG Reboot, and finally nothing. IMEI still gone. SIM Card not present even though it is in. Other ideas?
Click to expand...
Click to collapse
DUDDEEEEEEEE!!!!!
NO WAIT, IT WORKED!!!
THANK YOU VERY MUCH!!!!, everyone who reads this, plz thank user Rosli59564.
Rosli, I dont know where you got that info, plz post here so ppl can go thank that person. BUT IT WORKED, so thank you veyr much. You gave me back my FAVORITE PHONE ever!

Hitman7987 said:
DUDDEEEEEEEE!!!!!
NO WAIT, IT WORKED!!!
THANK YOU VERY MUCH!!!!, everyone who reads this, plz thank user Rosli59564.
Rosli, I dont know where you got that info, plz post here so ppl can go thank that person. BUT IT WORKED, so thank you veyr much. You gave me back my FAVORITE PHONE ever!
Click to expand...
Click to collapse
Huh just learnt how to repost a post. It's here:
http://forum.xda-developers.com/showthread.php?p=46436273
Glad you sort it out[emoji106]

Do an "adb shell"?
Hitman7987 said:
DUDDEEEEEEEE!!!!!
NO WAIT, IT WORKED!!!
THANK YOU VERY MUCH!!!!, everyone who reads this, plz thank user Rosli59564.
Rosli, I dont know where you got that info, plz post here so ppl can go thank that person. BUT IT WORKED, so thank you veyr much. You gave me back my FAVORITE PHONE ever!
Click to expand...
Click to collapse
Sorry @Hitman7987 but I'm new here but had the exact same problem you did.
I do not really understand the solution Rosli gave though. Could you help me out: point me to a post or explain here
What is an "adb shell" and how does one "do it"?
Thanks

tobyChidolue said:
Sorry @Hitman7987 but I'm new here but had the exact same problem you did.
I do not really understand the solution Rosli gave though. Could you help me out: point me to a post or explain here
What is an "adb shell" and how does one "do it"?
Thanks
Click to expand...
Click to collapse
I honestly can't remember, I think I just flashed TWRP and wiped the partitions he said to wipe. Then did the reboot.
Sorry for my lack of help, but I really can't remember the exact steps.

tobyChidolue said:
Sorry @Hitman7987 but I'm new here but had the exact same problem you did.
I do not really understand the solution Rosli gave though. Could you help me out: point me to a post or explain here
What is an "adb shell" and how does one "do it"?
Thanks
Click to expand...
Click to collapse
To flash a firmware or custom recovery:
http://forum.xda-developers.com/showthread.php?t=2704363
The rest are quite straight forward

[HELP] One plus 2 IMEI Showing 0

Hello,
I have One plus 2 64 Gb its IMEI is 0
i have tried many roms Still its 0
also Tried to change imei using QPST, efs Pro, cdma tool, whenever i write its showing NV ITEMS Read Only
i have successfully installed diag and normal drivers.
and device is showing in under port tab.
please help me to remove that write protection
( I Dont Have any EFS Backup)
No networks are coming
Please Help
(Sorry For Worst English ):angel:

Just use the ordinary factory restore using the factory qualcomm tool from the "how to factory restore my phone" thread. That way your phone should be back to the state it came in.

Still its showing 0
is There any kernel that removed write protection from nv items? I want cmto change the imei permently with Original One
or xposed installer will change the whole Imei or just masks?

BlueLemon1892 said:
Still its showing 0
is There any kernel that removed write protection from nv items? I want cmto change the imei permently with Original One
or xposed installer will change the whole Imei or just masks?
Click to expand...
Click to collapse
i think QPST configuration works, if its read only there is some other error
also a twrp backup of efs from some other phone will maybe fix it (dont ask for it)

Have you tried entering fastboot mode and doing a modemst erase? That fixed one of my IMEI numbers some time ago when I had the same problem that you detail. More info: http://forum.xda-developers.com/showpost.php?p=65712557&postcount=3

i have used fastboot to earse modemst files
but it worked not fully whenever i reboot 1st imei is 0 and second one is shown again after i reboot first will show second one is 0
tired of this is there any way to edit nv items write protection by editing kernel?

even i have flashed one of my friends efs backup but the problem is still continued

BlueLemon1892 said:
even i have flashed one of my friends efs backup but the problem is still continued
Click to expand...
Click to collapse
Contact OnePlus support and then tell us the solution they gave you.

no reply From Them

no reply From Them

After using fastboot erase command on modemst1 & modemst2,
My OP2's both sim slots stopped working,
So I flashed new+modem.zip by benschhold.
Which made sim-slot-1, work again !
But sadly, sim-slot-2 shows as "0", when checking through *#06#.
If somebody knows, how to write IMEI on OP2,
let me know.

bump..same problem

By bit of searching i've Found That firmware part is readonly, its not accepting any permission related read and Write. is there any way to rewrite it.?
or by modding kernel can we remove write protection? reply asap.

osr.arora said:
After using fastboot erase command on modemst1 & modemst2,
My OP2's both sim slots stopped working,
So I flashed new+modem.zip by benschhold.
Which made sim-slot-1, work again !
But sadly, sim-slot-2 shows as "0", when checking through *#06#.
If somebody knows, how to write IMEI on OP2,
let me know.
Click to expand...
Click to collapse
U can write ur IMEI by using QPST Tools
Sent from my ONE A2003 using XDA-Developers mobile app

Jyoti_re said:
U can write ur IMEI by using QPST Tools
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
No qpst tool Giving Error while writing
(NV_ITEM READ ONLY)
Even i've tried cdma workshop, efs pro they also giving same problem

BlueLemon1892 said:
No qpst tool Giving Error while writing
(NV_ITEM READ ONLY)
Even i've tried cdma workshop, efs pro they also giving same problem
Click to expand...
Click to collapse
my phone faced random reboot since the IMEI2 lost.

lockmunk said:
my phone faced random reboot since the IMEI2 lost.
Click to expand...
Click to collapse
Which one OP2?

Any solution, for writing IMEI#2 for my OnePlus 2 ?
Phone is out of warranty,
No efs backup.
Qualcomm restore tool, didn't fix this problem either.

I know this probably won't help here BC I don't think Color OS was made for the OPO2. But I had this exact problem with my OP One... Saw on XDA where someone said to flash ColorOS and it fixed the problem. I have no idea why this would work but it did.
---------- Post added at 08:40 AM ---------- Previous post was at 08:39 AM ----------
Is it possible that flashing Hydrogen OS could have the same effect on the OP2?

there is a usb dongle that can fix this thing, but i'm not too sure whether it can fix imei2 for our op2 or not
if someone reported works, i'm willing to buy this dongle also rather than use the phone faced the problem random reboot because of no imei2.
http://www.ebay.com/itm/Ultimate-Mu...833083?hash=item1c6aea6f3b:g:zsQAAOSwUUdXDja5

Invalid Imei, Locked Bootloader, no EDL. Can anyone help?

Hi Guys.
This is a Mediatek Helio X25 Redmi Pro and it came to me bricked from its owner who tried to root it the wrong way. I managed to flash an official rom and bring it back to life but as apparently is the case with these phones, the nvram has been corrupted/rewritten and there's no Imei numbers on the phone, which means no calls and stuff. WiFi works fine. I've already had permission to unlock the bootloader but obviously I can't do anything about it since the software won't ID the device. I believe I might be able to flash a backup of nvram.bin, but I don't have one from this phone, which is why I am posting this here, hoping that maybe one of you can help me by sending me a copy of his own Redmi Pro nvram.bin file. Of course I only need it to get the thing back in the system, after which I can unlock it and use the original Imei numbers. Or if someone has another suggestion, I would greatly appreciate it.
Thanks in advance.

Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.

Binnylaw said:
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Click to expand...
Click to collapse
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers

nsterjo said:
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
Click to expand...
Click to collapse
Tried this method?
http://en.miui.com/thread-411112-1-1.html
Sent from my Redmi Note 4 using Tapatalk

If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648

Binnylaw said:
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Click to expand...
Click to collapse
I have tried maybe 3 different versions of Sp Flashtool, including this one. I usually get a timeout message. But I will try again. Is there any specifics I should observe regarding the mdb files I need to use? I have tried all the ones that come with the roms I've tried, but without luck.

MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!

Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
No, you understood fine; it was me who typed SP Flashtool instead of SN Writer, which was what I meant. Everything else is as I wrote. I have tried 3 different versions of SN Writer, I connect fine and it starts the procedure following the same instructions you mentioned, but it stops half way, giving me an error message. I have tried different combinations of MDB and APDB files from several different ROMs I've downloaded, but they all fail. I'm not very familiar with these things but I can follow instructions and am quick to learn. Still, I have no idea why SN Writer or Maui Meta are not working. I tried to download an nvram.bin file I got from the internet with SP Flashtool, but it would not accept it as it was for Helio X20 I believe, which is why I was hoping someone would make available a copy of nvram.bin for this particular phone. I will also try to make a deepflash cable, hoping that might get me into EDL after which I can use MiFlash to reflash a new official Rom, but I don't know if it will work.

help please
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
Hi there, please can you tell me where I find the files (mdb and adb)? Are they somewhere on the phone's firmware? Or somewhere in the rom i flashed?
I'm a beginner having a very similar issue having flashed a rom in rescuing a bricked phone and now have invalid IMEI numbers.
Thanks so much

Need EFS Backup of WORKING Nexus 6P

Google will not admit this but there were major security flaws in factory images before jan,2017.
Read for yourself below article.
Link: https://www.google.com/amp/www.tech...d-nexus-6-patch-fixes-modem-vulnerability.htm
They patched it in Jan. But effected users like us(who got effected on 2016) got proper fu***.
The result : NO SERVICE but detects sim card.
Kindly.....Plz....plz...plz....make a copy of your efs and provide it in this thread. Please also mention what factory image/build number u are using.

No one will give you his EFS backup because its unique for each phone..so you cant use someone else EFS on your phone...

scrin378 said:
No one will give you his EFS backup because its unique for each phone..so you cant use someone else EFS on your phone...
Click to expand...
Click to collapse
Hey,
Yes, you can use it... The.problem is: are you ok to give it to someone you don't know?
Cheers...

5.1 said:
Hey,
Yes, you can use it... The.problem is: are you ok to give it to someone you don't know?
Cheers...
Click to expand...
Click to collapse
Really?? Thats a big news for me its no problem do i know him or not.. How can you use someone else EFS/IMEI.. it would be 2 phones with same IMEI number..maybe it will work, but its like you use someone else ID card and present it like its yours..

scrin378 said:
Really?? Thats a big news for me its no problem do i know him or not.. How can you use someone else EFS/IMEI.. it would be 2 phones with same IMEI number..maybe it will work, but its like you use someone else ID card and present it like its yours..
Click to expand...
Click to collapse
Hey,
When the IMEI is corrupted on the software side, it still shows up using:
fastboot getvar all
So the IMEI is somehow corrupted on the EFS partition. How, I don't know. Seems like the EFS acts like a bridge between hardware/software. Of course, I could be wrong...
Some have tried but didn't succeed. Now, it's not the first time I see someone using another EFS backup and getting his IMEI back. I don't know why it would get "their"" original IMEI instead of the one included in the EFS backup either. But i guess they must all lie saying it fixed their device.
Cheers...

I have restored EFS using a backup from someone else's device EFS. It did not change my original imei.

parvezrobi said:
Google will not admit this but there were major security flaws in factory images before jan,2017.
Read for yourself below article.
Link: https://www.google.com/amp/www.tech...d-nexus-6-patch-fixes-modem-vulnerability.htm
They patched it in Jan. But effected users like us(who got effected on 2016) got proper fu***.
The result : NO SERVICE but detects sim card.
Kindly.....Plz....plz...plz....make a copy of your efs and provide it in this thread. Please also mention what factory image/build number u are using.
Click to expand...
Click to collapse
Still need an efs?

DEVILOPS 007 said:
Still need an efs?
Click to expand...
Click to collapse
Hi, I'm facing the same issue after 7.1.2 OTA no IMEI, baseband anymore, If you don't mind I would like to have it.

blckhwkone said:
Hi, I'm facing the same issue after 7.1.2 OTA no IMEI, baseband anymore, If you don't mind I would like to have it.
Click to expand...
Click to collapse
I'll share one soon for everyone here. I'm just a bit worried about security though as I don't know what happens and what data is stored in an efs backup.

blckhwkone said:
Hi, I'm facing the same issue after 7.1.2 OTA no IMEI, baseband anymore, If you don't mind I would like to have it.
Click to expand...
Click to collapse
Welcome to The tragic Club of network less Nexus 6P.. You are not alone here.

DEVILOPS 007 said:
I'll share one soon for everyone here. I'm just a bit worried about security though as I don't know what happens and what data is stored in an efs backup.
Click to expand...
Click to collapse
Down do it. The efs is device dependent. It will contain things like your imei. So even if restored on another device it will end up causing issues due to the same imei on different devices. It can also make it so things like WiFi don't work

zelendel said:
Down do it. The efs is device dependent. It will contain things like your imei. So even if restored on another device it will end up causing issues due to the same imei on different devices. It can also make it so things like WiFi don't work
Click to expand...
Click to collapse
Okay thank you, I had no clue about efs so I'll take your word on it.

Guys can anyone share efs so that I can restore and save my phone..I Have no signal ispitevof detection sim card...it shows no service.. But when I use jio it shows full signal..kindly help..

I had similar problem with my OnePlus X. Apparently I was saving and restoring my efs partion with every twrp backup which eventually caused it to become currupt. Thought my phone was toast until a friend on telegram suggested deleting modem1 and modem2 files with adb commands. Sounded more destructive then good but it actually worked sim was reading again and got full use of my phone. It's good to make backup of efs but only once. Not sure if this is the fix for every phone but works with OnePlus and Xiaomi.
How to Fix EFS from Bootloader Mode using Fastboot commands
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Got my information from here

kach22 said:
I have restored EFS using a backup from someone else's device EFS. It did not change my original imei.
Click to expand...
Click to collapse
can send me plz your bakcup i need

Boot persist.img from MSMDownLoad Tool

Hello!
Oneplus 8 pro 12/256.
Such Problem.
CrashDump Mode after MSMdownload tool. I think the problem is with persist.img.
I have backup of persist.img which I made after buying device.
But I can't boot it because bootloader is locked.
I can't unlock bootloader because remote flashing is not allowed.
I can't allow remote flashing in Dev's Options because system doesn't boot.
I have an idea to boot persist.img from msmdownload tool but I don't know how.
I read that on xiaomi devices it is possible.
Can anybody suggest something?
​

n1kola14 said:
I have an idea to boot persist.img from msmdownload tool
​
Click to expand...
Click to collapse
Maybe by changing something in ROM for MSMdownload tool. But I don't know how to do it

one idea would be a modified MSMtool that installs TWRP recovery

n1kola14 said:
Hello!
Oneplus 8 pro 12/256.
Such Problem.
CrashDump Mode after MSMdownload tool. I think the problem is with persist.img.
I have backup of persist.img which I made after buying device.
But I can't boot it because bootloader is locked.
I can't unlock bootloader because remote flashing is not allowed.
I can't allow remote flashing in Dev's Options because system doesn't boot.
I have an idea to boot persist.img from msmdownload tool but I don't know how.
I read that on xiaomi devices it is possible.
Can anybody suggest something?
​
Click to expand...
Click to collapse
This makes no sense. The msm tool overwrites and fixes all partitions. Like, did you have a bad persist.img and use msm, it will revert all to stock. Its basically reinstalling OOS as if phone has no partitions on it. An example, on my oneplus 7 pro using dual boot, I have 3 data partitions a/b/c but when I use msm tool, it fixes and reverts back to a/b. And I don't have the same persist.img that came with phone installed. I had to install a different one

jamescable said:
This makes no sense.
Click to expand...
Click to collapse
Unfortunately, but it is.
I tried India 10.5.13 and global 10.5.4. The same result.
Msm downloads 100% without any mistakes (and locks bootloader) and than I have this:
Qualcom Crash Dump Mode
err_qdi.c:1038:EF:sensor_process:0x1:SNS_REG_INIT :0x5c:sns_registry_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - slpi crashed. subsys_unregister

n1kola14 said:
Unfortunately, but it is.
I tried India 10.5.13 and global 10.5.4. The same result.
Msm downloads 100% without any mistakes (and locks bootloader) and than I have this:
Qualcom Crash Dump Mode
err_qdi.c:1038:EF:sensor_process:0x1:SNS_REG_INIT :0x5c:sns_registry_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - slpi crashed. subsys_unregister
Click to expand...
Click to collapse
That might have been what ****ed your phone up. You are ONLY supposed to use the msm tool that matches your model. For me, global msm tool not Europe or china etc. There is a thread in development stating this

If you're going to use MSM, match your device variant it's not safe to rebrand using this method.
If your bootloader locks (which it should). And your fingerprint is still borked..,(which it could still be)
Then unlock the bootloader and run through the persist.img guide found in the guides section.
Tbh the MSM tool doesn't always fix the persist partition that's why people have RMAd their devices before there was a viable fix, otherwise there wouldn't have been like a 100 threads created when the persist issue arised.
FYI you don't need the back up to your persist partition to fix it..

had the same issue. Use Android 11 MSM tool and my battery was low like 0% idk if it helps but try.

Yeh, full battery is a wise idea!
I wish they had a Linux MSM tool for our Chromebooks, etc...

The only thing that fixes and overwrites ur persist partition is SMT download mode in MSM. But BE CAREFUL cuz it will delete ur IMEI and the Widevine certificates from the phone. I used it before and wished I didn't do it, now I'm with 0 IMEI and can't flash unlock_token to unlock bootloader cuz it says verify failed obviously due to no IMEI.
So use it with care and ONLY if you have no choice.

L0ND0NB0Y said:
The only thing that fixes and overwrites ur persist partition is SMT download mode in MSM. But BE CAREFUL cuz it will delete ur IMEI and the Widevine certificates from the phone. I used it before and wished I didn't do it, now I'm with 0 IMEI and can't flash unlock_token to unlock bootloader cuz it says verify failed obviously due to no IMEI.
So use it with care and ONLY if you have no choice.
Click to expand...
Click to collapse
You dont need an unlocked bootloader to fix your imei hit me up on telegram i will help you

gsser said:
You dont need an unlocked bootloader to fix your imei hit me up on telegram i will help you
Click to expand...
Click to collapse
Ok sir I'll PM you as soon as I get home

L0ND0NB0Y said:
Ok sir I'll PM you as soon as I get home
Click to expand...
Click to collapse
hey can you help as my imei is lost and baseband is also showing unknown after i flashed with smt download mode
i have serched everywhere but cant find the solution of this i m feeling dumb now

Nimnim12 said:
hey can you help as my imei is lost and baseband is also showing unknown after i flashed with smt download mode
i have serched everywhere but cant find the solution of this i m feeling dumb now
Click to expand...
Click to collapse
Just use SMT again it'll fix your baseband, and don't use random qcn files to fix IMEI cuz they corrupt the baseband.

L0ND0NB0Y said:
Just use SMT again it'll fix your baseband, and don't use random qcn files to fix IMEI cuz they corrupt the baseband.
Click to expand...
Click to collapse
thanks bro will be replying back if it works or not

Nimnim12 said:
thanks bro will be replying back if it works or not
Click to expand...
Click to collapse
Np I'll wait for response.

thankyou so much bro baseband is back now although imei is still not revered but got a hope

Happy I helped, now you reached my point no IMEI. Hmu on telegram so we can work on a solution @l0nd0nb0y_alt