Hey guys,
Here is a story of stupid myself and now i need help with my phone Please enjoy and help if you can. Thanks.
I was trying to unlock LTE bands on EEA mi 9t (BAD DECISION, DON'T DO IT!) following any of those tutorials online, and i broke:
1, mobile network
2, wifi
3, diag mode/port
What i did:
- I have root with Magisk, used "adb shell / su / setprop sys.usb.config diag,adb" to enable diag port.
- Connected QPST and QXDM
- In QXDM's NV browers, i put "17592185995263" in both lines in NV item 06828 LTE_BC_CONFIG without backing up the original value (BAD DECISION, DON'T DO IT!)
- Rebooted the phone, and now mobile network and wifi disconnectes every 5 seconds.
What i have tried to fix this:
1, Reconnect QPST and QXDM, now QPST doesn't read phone's ESN number, and QXDM is saying that i can read/write to any NV items. Basically the diag mode is not communicating correctly anymore.
2, factory reset, no good.
3, recovery flashing, no good
4, fastboot flashing, no good
5, EDL/MiFlash tool flashing, (YES, with an authorized account), including persist partition (modified crclist.txt and etc), NO GOOD
I am here right now. I have done so much research on this topic and nobody has seem to run into this.
I am an embedded engineer and have a little bit android dev experience, and here is what i think based on what i have done and what i have read:
1, the NV items are stored in some location in flash memory, and they are loaded in the boot sequence when the phone boots up. But these NV items are not in persist, modem1 nor modem2 partitions as i have tried. And this block is not flashed by any flashing method, even EDL mode.
2, once the modified NV item (LTE_BC_CONFIG) has been loaded, it cause the firmware/hardware of qualcomm to not function correctly, thus the diag mode/port is not communicating properly to QPST/QXDM.
So I am (still) looking to fix this problem in 2 ways according to my theory above:
1, find the location that stores the NV items and try to revert the LTE_BC_CONFIG part back (but i don't know the original, yet possible to calculate it based on phones spec sheet).
2, find a way to reset the diag mode/port so that it talks to QPST/QXDM again.
Please help if you know anything about this.
Otherwise my phone is just a tablet that does not have internet lol
Thank you in advance!
tag: redmi k20 pro mi 9t global eea lte band unlock
Does a full reflash not fix it? You probably tried already.
SnowFuhrer said:
Does a full reflash not fix it? You probably tried already.
Click to expand...
Click to collapse
yea lol Qualcomm's EDL mode flash has no effect
Take it to service center after installing miui .
State that network is fluctuating by itself. I have done something similar on other device without taking backup . Only way is to change the whole motherboard .
Gaurav0007 said:
Take it to service center after installing miui .
State that network is fluctuating by itself. I have done something similar on other device without taking backup . Only way is to change the whole motherboard .
Click to expand...
Click to collapse
That method totally makes sense...expect that xiaomi has no service center in Canada and i bought this potentially European version phone ftom Gearbest (which ships from China) lol its a whole lot of locations that dont match up lol..
anyone?
worst case, i may need to sell the phone as a internet-less digital famera for scrap money lol
Tmobile brand 12
Is there a way to enable all the tmobile bands?
russellglen72 said:
Is there a way to enable all the tmobile bands?
Click to expand...
Click to collapse
if i can fix my phone i'd volunteer to try lol
If you need QCN backup for 9T, I got one working. This might restore your original settings after you wipe modemst1&2 and fsg.
SEXCAVATOR said:
If you need QCN backup for 9T, I got one working. This might restore your original settings after you wipe modemst1&2 and fsg.
Click to expand...
Click to collapse
Thanks! I could give it a try, as the problem is mainly that the phone does not talk to any of these tools any more.
Let me know where i can get it plz.
And what tool did uou create the backup with?
kezzuki said:
Thanks! I could give it a try, as the problem is mainly that the phone does not talk to any of these tools any more.
Let me know where i can get it plz.
And what tool did uou create the backup with?
Click to expand...
Click to collapse
This backup I found from a local forum is taken using QPST tool (2.7.477 I remember). It belongs to Xiaomi Mi 9T device. Only one IMEI is working though (the other one is nulled). Why your phone doesn't talk to tools anymore, can't get DIAG mode on?
https://gofile.io/?c=gxTHSm (IMEI of the backup is written in the name. You can search and change using HEX edit method).
SEXCAVATOR said:
This backup I found from a local forum is taken using QPST tool (2.7.477 I remember). It belongs to Xiaomi Mi 9T device. Only one IMEI is working though (the other one is nulled). Why your phone doesn't talk to tools anymore, can't get DIAG mode on?
https://gofile.io/?c=gxTHSm (IMEI of the backup is written in the name. You can search and change using HEX edit method).
Click to expand...
Click to collapse
Diag mode can be enabled, but qpst says says its in a wrong state and cannot read or write NV items lol
kezzuki said:
Diag mode can be enabled, but qpst says says its in a wrong state and cannot read or write NV items lol
Click to expand...
Click to collapse
I would have backup modemst1&2 and fsg then wipe those partitions. That might jump start.
SEXCAVATOR said:
I would have backup modemst1&2 and fsg then wipe those partitions. That might jump start.
Click to expand...
Click to collapse
May I ask what those partitions do?
kezzuki said:
May I ask what those partitions do?
Click to expand...
Click to collapse
They are where the NV items and modem config are located and their backup. Once you purge those partitions, android system will renew it from an inner source. If anything goes wrong, you can always restore those partitions from an image you took previously. I did it numerous times. My bootloader was unlocked and I had TWRP. Those are necessary.
SEXCAVATOR said:
They are where the NV items and modem config are located and their backup. Once you purge those partitions, android system will renew it from an inner source. If anything goes wrong, you can always restore those partitions from an image you took previously. I did it numerous times. My bootloader was unlocked and I had TWRP. Those are necessary.
Click to expand...
Click to collapse
Wow, that seems like it will work. I will try it when i get a chance.
Where did you find this information?...i tried searching the entire internet but didn't see anything like that...
Thanks!
kezzuki said:
Thanks! I could give it a try, as the problem is mainly that the phone does not talk to any of these tools any more.
Let me know where i can get it plz.
And what tool did uou create the backup with?
Click to expand...
Click to collapse
I learned in a hard way. Bricked my device while playing with the bands, lost my IMEI...
This info I gave you is served in XDA forums under different topics. If you gonna give it a try, I can give you exact steps.
SEXCAVATOR said:
I learned in a hard way. Bricked my device while playing with the bands, lost my IMEI...
This info I gave you is served in XDA forums under different topics. If you gonna give it a try, I can give you exact steps.
Click to expand...
Click to collapse
wow guess you saved your phone lol
I can wipe blocks and will try that method later. Thanks!
kezzuki said:
wow guess you saved your phone lol
I can wipe blocks and will try that method later. Thanks!
Click to expand...
Click to collapse
I know its an old thread, but did you manage to solve that problem? I got a phone here with exactly the same issue
Related
Hi,
Phone restarts automatically with no imei and unknown baseband, I download stock firmware 4.4.2 and install on it but same situation,
any suggestion or help pls,
thanks
br
Isn't IMEI used for phone identification along with MEID? If thats blank, would it be an issue on Verizons side?
Elite49 said:
Isn't IMEI used for phone identification along with MEID? If thats blank, would it be an issue on Verizons side?
Click to expand...
Click to collapse
imei is unknow
2 Choices
nsnobel2 said:
imei is unknow
Click to expand...
Click to collapse
Hi
I don't know if you've fixed your issue with your g900v or not, but i have the same problem and the same phone and obviously the same symptoms ...
As far as I've tried, nothing worked not ODIN flashing ROMs, or QPST to write IMEI or EFS professtiona ADB .... etc.
What I've come to know is this :
1- keep the phone in a safe place till next months reveal a solution through developers here or elsewhere.
2- Flash the Original Samsung Verizon Rom ( Full Package with efs and bootloader mounts and all partitions " Clean Flash" ) which costs about 100$ .
3- Change the board for a (200$) new one .
So, I would try to pay the 100$ and flash the original ROM, and comeback to tell if it solved the Problem.
I wish if you share any different approach or feedback . I would love to hear it .
Bye
It could possibly be that your EFS folder is damaged. This is where your IMEI and Baseband info is stored. If that's the case for your device, these steps should work. I've done this on two phones (one being an S5) and it fixed this problem.
I'm assuming that you're rooted. If not then you'll need to root your device first. And you need to have debugging enabled. What this does is backups the files from the EFS folder, repairs the partition tables, then restores the files to the repaired folder.
1. Connect the phone to your computer. (Windows)
2. Download this: https://www.dropbox.com/s/v2h5dzisjd0rgj5/EFS_Professional_2.1.73_Release.zip?dl=0
3. Extract and run the program
4. Click EFS Professional... It will open a window showing that it found your phone
5. Click on the Backup Tab and make sure all of the partitions are checked, and your Device Filter is recognized
6. Hit the Backup button to backup the EFS folder
7. After that's done, click the Restore button and it will restore your files to the EFS folder.
I hope this helps you.
There used to be a tool for the Note 2 I believe, maybe S4, that would let you re-write your EFS if it accidentally got erased. Not a backup/restore deal, but a tool to key in your IMEI and it would write it to the phone. Maybe research that tool for a fix?
joshw0000 said:
There used to be a tool for the Note 2 I believe, maybe S4, that would let you re-write your EFS if it accidentally got erased. Not a backup/restore deal, but a tool to key in your IMEI and it would write it to the phone. Maybe research that tool for a fix?
Click to expand...
Click to collapse
Was it a tool specifically for the Note 2, or multiple Samsung devices, or maybe a universal program like CDMA Workshop? I love that program. It's what I use when it comes to actually entirely rewriting files like this. Most of the time a full rewrite isn't needed though if the EFS folder has just been damaged. Which "damaged" is totally the wrong word here, but that's what it's called for some reason. I really don't even know how it happens, but I do know when it does, it usually just jumbles and/or fragments the info in the folder and needs to be put back in it's correct order. Kind of like defragging in Windows. Just a tool like you're talking about would definitely be cool for me to have though. I shall start my quest to find it. Lol
Please some help
Any luck yet ???
Got the same issue here, and none of the threads here worked .
Same problem
Hello,
I have the exact same problem. I bought the phone here in Mexico, and the phone came with erased EFS folder. Phone restarts automatically when screen turns off. When I'm using the phone, it works just fine, but some seconds after screen goes off, phone restarts automatically. EFS folder is messed up, I've tried out a lot EFS restoring tools with no luck.
I tried QPST but it does not detect the phone, only appears "?" and "No phone" blinking. The same happens with DFS Tool.
I will try to look for that tool joshw0000 talks about.
I hope we can find out a solution for this excellent phone.
Bye.
Hey ...
I did a factory reset and cache wipe, and now the phone stopped restarting when the screen goes off, but still got the "Unknown" issues.
But at least I got rid of the annoying restarts.
570 ppl read this and still no answer, I got to admit ... it's tough.
Sent from my SM-G900V using XDA Free mobile app
I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.
ethanscooter said:
I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.
Click to expand...
Click to collapse
Where did you find the fastboot file?
________
v7
XDA Assist
v7 said:
Where did you find the fastboot file?
________
v7
XDA Assist
Click to expand...
Click to collapse
I forgot where I found it from... do you know where he correct one is?
ethanscooter said:
I forgot where I found it from... do you know where he correct one is?
Click to expand...
Click to collapse
There's no official fastboot zip from the Oneplus.That's why I asked you.Did you find it from XDA?
__
v7
XDA Assist
v7 said:
There's no official fastboot zip from the Oneplus.That's why I asked you.Did you find it from XDA?
__
v7
XDA Assist
Click to expand...
Click to collapse
I forgot, honestly this happened a few weeks ago I tried looking through my history but I couldn't find it. How can I fix it?
EDIT: It wasn't from XDA for sure.
ethanscooter said:
I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.
Click to expand...
Click to collapse
This happened to me a few times in the past, all I had to do was wipe dalvik and cache again and it came back. Not sure if it's the same issue but I would give it a shot. Just boot into recovery and wipe them again and see if it gets you back up and running.
_MetalHead_ said:
This happened to me a few times in the past, all I had to do was wipe dalvik and cache again and it came back. Not sure if it's the same issue but I would give it a shot. Just boot into recovery and wipe them again and see if it gets you back up and running.
Click to expand...
Click to collapse
I tried it and still nothing...
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21
first try this.
then, flash H2OS. (Oxygen Os won't work from that recovery so, H2OS. Later you can re-flash though)
(Try this first!!!)
EDIT: if that doesn't reset, try this.
http://forum.xda-developers.com/one...over-oneplus-2-to-t3269543/page2#post64303240
Official O2OS files.
krishna442 said:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21
first try this.
then, flash H2OS. (Oxygen Os won't work from that recovery so, H2OS. Later you can re-flash though)
(Try this first!!!)
EDIT: if that doesn't reset, try this.
http://forum.xda-developers.com/one...over-oneplus-2-to-t3269543/page2#post64303240
Official O2OS files.
Click to expand...
Click to collapse
I cannot use that because my device is not hard bricked and it will not install the driver since I can enter the bootloader normally.
Not sure if you've seen this post its based on the post above but I think it just uses fastboot. Don't know if it will work for you, but figured it would be worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
I tried using the tool and it did not work, I purposely hard bricked the device to try it and still no signal or imei. Another problem is WiFi takes about 4 minutes just to turn on but I can live with that I just want service.
Basically flashing back the stock should bring back the efs. Let's see if someone has a solution. Sorry!
EFS files are unique to each phone. If the EFS is corrupt or damaged, and there is no backup, I don't know of any way to fix it ;_; You can try OnePlus support but they aren't as dumb as carrier warranty or other phone manufacturers. They'll be more likely to know what you did.
It is possible to restore your imei number, I did it on my brothers lg g2. It requires some software for PC (I can't remember the name, you'll have to google it) and the box your phone came in with the imei number. It is possible, so don't lose hope!
EddyH1993 said:
It is possible to restore your imei number, I did it on my brothers lg g2. It requires some software for PC (I can't remember the name, you'll have to google it) and the box your phone came in with the imei number. It is possible, so don't lose hope!
Click to expand...
Click to collapse
Is it called QPST configuration? If so all I need help with is getting the phone to be recognized by the tool. Don't you need it to be on some COM port or something?
ethanscooter said:
Is it called QPST configuration? If so all I need help with is getting the phone to be recognized by the tool. Don't you need it to be on some COM port or something?
Click to expand...
Click to collapse
Yeh that software rings a bell and yeh I believe it's something like com port 47 maybe. It was a while ago when I did it and I can't remember the process of doing it :/
EddyH1993 said:
Yeh that software rings a bell and yeh I believe it's something like com port 47 maybe. It was a while ago when I did it and I can't remember the process of doing it :/
Click to expand...
Click to collapse
Don't I need a special driver? Also, do I need to put the phone into diag mode and how would I do that?
ethanscooter said:
Don't I need a special driver? Also, do I need to put the phone into diag mode and how would I do that?
Click to expand...
Click to collapse
Have a look at this link http://droidmodderx.com/galaxys3/?page_id=79 I really can't remember how I did it and without researching again I won't know. It's a rough idea to maybe help you, I think the device just needs to be in USB debugging mode. I can't help anymore sorry and good luck.
any fix for this yet?
Same problem also with my op2 . No imei no baseband
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
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
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