First post, long time lurker, so i'll start with a big thanks to the entire community for all the help you've unknowingly given me.
I just got a nexus 5 to replace my original n5 which has a broken screen. I took a backup of the original and restored it to the new one. Unfortunately i didn't know what EFS was, so i restored the old EFS to the new phone. IMEI went to zero. HUGE BUMMER.
I was able to fix the IMEI with QPST, but the new phone will not connect to the network. I've run a check on the IMEI and it is not blacklisted. Without incriminating myself, lets just say that i'm positive that the new IMEI is good.
The phone recognizes that i've inserted a SIM but shows no signal. I've tried to search for networks, i've checked the APN settings...
I REALLY don't want to send this to LG since they can't give me a price or even a ballpark figure without me shipping them the phone...
Any advice on next steps would be greatly appreciated.
What should i try next?!
flash the factory img and do not restore your efs on it.
simms22 said:
flash the factory img and do not restore your efs on it.
Click to expand...
Click to collapse
I guess i should have mentioned that i've flashed factory also. Currently the phone is on the latest firmware, unrooted, locked bootloader. Flashing factory had no effect at any point.
I bought this phone on Swappa BTW, so i am assuming there are no hardware issues. I'm not at all certain what else may have been screwed up by having another phone's EFS restored over this "new" phone's EFS...
More Info
I am able to attempt to manually select the network. When i search for networks, the available networks are shown, but when i try to connect it shows the Registering dialog for quite a while, then fails. This is the same behavior as a working phone without a SIM installed. The odd part is that the phone will recognize when a SIM is installed or removed. It seems that my problem may be that the SIM is not being read properly or the data is being lost/corrupted between SIM and antenna. Is this possible? Is this EFS corruption? is this something i can fix? Please help.
Bump?
I purchased a g930f off of Swappa and somehow soft bricked it to the point where it lost its imei and even if I get it to boot, it won't access my provider (ATT). I bought another one (yeah) and it appears to have exactly the same firmware that the bricked one did when I got it. I wonder if by making a nandroid backup of the new phone, I can get the old one working again, and somehow get the original imei reinstated on the bricked phone. I do NOT want to fake an imei, or do any other illegal thing, just get the first phone working again and hopefully reinstate its imei and serial number. Anyone have thoughts on this?
kettir said:
I purchased a g930f off of Swappa and somehow soft bricked it to the point where it lost its imei and even if I get it to boot, it won't access my provider (ATT). I bought another one (yeah) and it appears to have exactly the same firmware that the bricked one did when I got it. I wonder if by making a nandroid backup of the new phone, I can get the old one working again, and somehow get the original imei reinstated on the bricked phone. I do NOT want to fake an imei, or do any other illegal thing, just get the first phone working again and hopefully reinstate its imei and serial number. Anyone have thoughts on this?
Click to expand...
Click to collapse
Try using Odin and download mode to get back to stock. That should bring back your imei. I think because you restored a backup from another phone, it tried to write the new imei on the old phone causing an error. Let me know how it goes.
Sent from my SM-G935T using Tapatalk
xmayhemreturnsx said:
Try using Odin and download mode to get back to stock. That should bring back your imei. I think because you restored a backup from another phone, it tried to write the new imei on the old phone causing an error. Let me know how it goes.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I never did get back about your reply, but you were on track with your suggestion. I ended up finding the factory binary and flashing that, which got me back my IMEI and able to boot again, and then flashed the proper firmware. All is well since then.
I have a CC9 Pro Premium. Even if i can't fix my problem, hopefully this story will PREVENT people from messing with their IMEIs... I hope no one ever goes through what I just did
I'm obviously by no means encouraging changing IMEIs, even in certain 3rd world countries where it could be necessary!
So here's a detailed backstory: When you purchase a phone where I live, you need a valid passport in order to pay tax and register it's IMEI number, and if not you get cut off by your operator within a month.
I didn't have one, since it also takes about 4-8 months to process, and I couldn't even preform a request due to the corona virus situation.
So, being the ignorant idiot I am, I thought it would be a great idea to change it's IMEI number till I can register the original one, since a lot of people do this over here apparently, white market
I followed a tutorial I found online (And re-posted on XDA, so there's nothing really wrong with it), and here's what happened:
(Root, TWRP and Diag is OK in all steps)
I made a .qcn backup using QPST build 480, saved the original somewhere safe, edited the copy, wiped modemst1, modemst2 and fsg, then restored it
*phone reboots*
Everything's the same, and still getting reception, no change
Took another backup and saw it was the same, so I give up
The next day I try again, but this time is when the problems started... I take another QCN backup just to be sure, and it's slightly larger (Could be because I just inserted a 2nd SIM for the first time right before it), edit it, then wipe modemst1, modemst2, fsg and this time: "fsc" since I saw someone do it in another tutorial for the Mi Note 10
*phone reboots*
*boot animation*
*resets and goes to recovery*
I was shocked. I wipe the 4 partitions again and the phone boots normally, nothing has changed (apparently).
So I put my SIMs in and go watch a movie. Then I switch it on, only to see there's no reception!!!
I wipe the partitions, and restore the first original backup... boots to recovery again...
Wipe... Boots normally... restore the 2nd original one (slightly larger, both sims)... boots to recovery...
Then I just decide to miflash a fastboot rom, maybe that will get things back to normal!
So I wipe, flash rom... IMEI and Baseband now Unknown... Yikes...
I next find an xQCN backup online for the Mi Note 10 that only has a single IMEI in it, that belongs to the 2nd sim (SIM 1 550 only, QCN View, the 1st 550 missing)
Replace it with my original and reboot, IMEI 2 and baseband is back! But no reception, even after multiple reboots...
I wipe partitions again, IMEI 2 is still there... Interesting...
I continue trouble shooting, even: wiping the partitions, restoring the original backup, flashing fastboot rom... still boots to recovery (Mi Recovery of course), setting 755 permission for modem files...
------------------------------------------------
SUMMERY:
I need to find out why the original backup keeps booting to recovery!!! Also some information about "fsc" partition would be nice, since wiping that probably started the whole issue (Is it a backup for fsg?!)
Important things I discovered:
1) Wiping modemst1 and modemst2 at the same time is enough for the phone to boot
2) The reboot to recovery (Recovery loop?) with the original backups is caused on an OS level, because one time it took so long that I even saw the lockscreen for half a second before it rebooted (no SIMcard in the phone either)
3) After hours of dorking I found 2 other similar instances that could be related:
https://forum.xda-developers.com/ze...onor-qcn-file-ze550kl-z00ld-ww-t3520647/page4 (Page 4-5)
(Normal boot using a custom rom?? Interesting... maybe Xiaomi.eu made no difference for me because it's still pretty much just MIUI)
https://www.youtube.com/watch?v=8Ym0FP4BkY0 (The bottom comment):
"We cannot repair both SIM slots.
We can only repair SIM2 slot for IMEI repairing. After IMEI repair process, SIM1 IMEI getting '0' value. When we are trying to repair both SIM slot phone is entering the Bootloop and entering the recovery mode(twrp). Thats why we are remove SIM1 IMEI from qcn file and this time we can will repair to SIM2 slot. Do you know this Problem ? What can we do to solve this problem? Thank you in advance for your help."
Regards, and many thanks... DON'T MESS WITH IMEIs!!!
imei repair is done.
the only problem is returning to "Factory settings" and imei is deleted.
gokmenm said:
imei repair is done.
the only problem is returning to "Factory settings" and imei is deleted.
Click to expand...
Click to collapse
Really?! How did you do it?! Both SIM cards or just SIM 2 ????????
ZINHAR said:
Really?! How did you do it?! Both SIM cards or just SIM 2 ????????
Click to expand...
Click to collapse
I am also facing same problem... I restored only one IMEI with Redmi Note 7
If found solution please inform me too
macblaze said:
I am also facing same problem... I restored only one IMEI with Redmi Note 7
If found solution please inform me too
Click to expand...
Click to collapse
So far it only seems possible to restore sim 2, I contacted a professional IMEI dealer and this is what he said:
"IMEIs cannot be changed simply through a USB port on modern snapdragon SOCs. Only the secondary sim modem can be restored, because the primary sim is locked to the chipset. When tampered with, it goes into a lockdown state which means it can probably never be used again unless a breach is found"
I sold the phone and got a Nokia 9 Pureview, much more consistent but still has it's own issues
ZINHAR said:
So far it only seems possible to restore sim 2, I contacted a professional IMEI dealer and this is what he said:
"IMEIs cannot be changed simply through a USB port on modern snapdragon SOCs. Only the secondary sim modem can be restored, because the primary sim is locked to the chipset. When tampered with, it goes into a lockdown state which means it can probably never be used again unless a breach is found"
I sold the phone and got a Nokia 9 Pureview, much more consistent but still has it's own issues
Click to expand...
Click to collapse
:crying::crying::crying: Okay thanks for your sharing :good:
Same issue with Mi Note 10
Hi I also flash to EU ROM and now Im facing the same no service issue. So how to solve this?
gaiya said:
Hi I also flash to EU ROM and now Im facing the same no service issue. So how to solve this?
Click to expand...
Click to collapse
If it's related to the IMEI, multiple guides have already been made since I made this post. Just search for it on YouTube!
If not, could be a bad rom, bad recovery, incomplete unlock, etc.
Try a stable Orange Fox Recovery, that might fix it
No service mi note 10
gaiya said:
Hi I also flash to EU ROM and now Im facing the same no service issue. So how to solve this?
Click to expand...
Click to collapse
Hi have you solved the no service issue?
No not yet, no any solution for it
gaiya said:
Hi have you solved the no service issue?
Click to expand...
Click to collapse
Just flash the SIM 2 QCN I provided (edit the IMEI), and write the IMEI using pirated box software for free, you can find everything you need on YouTube. When I had the problem, pirated box software for the Mi Note 10 wasn't available yet
redmi note 9s
ZINHAR said:
Just flash the SIM 2 QCN I provided (edit the IMEI), and write the IMEI using pirated box software for free, you can find everything you need on YouTube. When I had the problem, pirated box software for the Mi Note 10 wasn't available yet
Click to expand...
Click to collapse
Hi can you help me to change Redmi Note 9S IMEI repair ?
where can I find tutorial and programs
ZINHAR said:
Just flash the SIM 2 QCN I provided (edit the IMEI), and write the IMEI using pirated box software for free, you can find everything you need on YouTube. When I had the problem, pirated box software for the Mi Note 10 wasn't available yet
Click to expand...
Click to collapse
hey help me.
How to disable sim 1 imei.
Which pirated box tool you have used
ZINHAR said:
I have a CC9 Pro Premium. Even if i can't fix my problem, hopefully this story will PREVENT people from messing with their IMEIs... I hope no one ever goes through what I just did
I'm obviously by no means encouraging changing IMEIs, even in certain 3rd world countries where it could be necessary!
So here's a detailed backstory: When you purchase a phone where I live, you need a valid passport in order to pay tax and register it's IMEI number, and if not you get cut off by your operator within a month.
I didn't have one, since it also takes about 4-8 months to process, and I couldn't even preform a request due to the corona virus situation.
So, being the ignorant idiot I am, I thought it would be a great idea to change it's IMEI number till I can register the original one, since a lot of people do this over here apparently, white market
I followed a tutorial I found online (And re-posted on XDA, so there's nothing really wrong with it), and here's what happened:
(Root, TWRP and Diag is OK in all steps)
I made a .qcn backup using QPST build 480, saved the original somewhere safe, edited the copy, wiped modemst1, modemst2 and fsg, then restored it
*phone reboots*
Everything's the same, and still getting reception, no change
Took another backup and saw it was the same, so I give up
The next day I try again, but this time is when the problems started... I take another QCN backup just to be sure, and it's slightly larger (Could be because I just inserted a 2nd SIM for the first time right before it), edit it, then wipe modemst1, modemst2, fsg and this time: "fsc" since I saw someone do it in another tutorial for the Mi Note 10
*phone reboots*
*boot animation*
*resets and goes to recovery*
I was shocked. I wipe the 4 partitions again and the phone boots normally, nothing has changed (apparently).
So I put my SIMs in and go watch a movie. Then I switch it on, only to see there's no reception!!!
I wipe the partitions, and restore the first original backup... boots to recovery again...
Wipe... Boots normally... restore the 2nd original one (slightly larger, both sims)... boots to recovery...
Then I just decide to miflash a fastboot rom, maybe that will get things back to normal!
So I wipe, flash rom... IMEI and Baseband now Unknown... Yikes...
I next find an xQCN backup online for the Mi Note 10 that only has a single IMEI in it, that belongs to the 2nd sim (SIM 1 550 only, QCN View, the 1st 550 missing)
Replace it with my original and reboot, IMEI 2 and baseband is back! But no reception, even after multiple reboots...
I wipe partitions again, IMEI 2 is still there... Interesting...
I continue trouble shooting, even: wiping the partitions, restoring the original backup, flashing fastboot rom... still boots to recovery (Mi Recovery of course), setting 755 permission for modem files...
------------------------------------------------
SUMMERY:
I need to find out why the original backup keeps booting to recovery!!! Also some information about "fsc" partition would be nice, since wiping that probably started the whole issue (Is it a backup for fsg?!)
Important things I discovered:
1) Wiping modemst1 and modemst2 at the same time is enough for the phone to boot
2) The reboot to recovery (Recovery loop?) with the original backups is caused on an OS level, because one time it took so long that I even saw the lockscreen for half a second before it rebooted (no SIMcard in the phone either)
3) After hours of dorking I found 2 other similar instances that could be related:
https://forum.xda-developers.com/ze...onor-qcn-file-ze550kl-z00ld-ww-t3520647/page4 (Page 4-5)
(Normal boot using a custom rom?? Interesting... maybe Xiaomi.eu made no difference for me because it's still pretty much just MIUI)
https://www.youtube.com/watch?v=8Ym0FP4BkY0 (The bottom comment):
"We cannot repair both SIM slots.
We can only repair SIM2 slot for IMEI repairing. After IMEI repair process, SIM1 IMEI getting '0' value. When we are trying to repair both SIM slot phone is entering the Bootloop and entering the recovery mode(twrp). Thats why we are remove SIM1 IMEI from qcn file and this time we can will repair to SIM2 slot. Do you know this Problem ? What can we do to solve this problem? Thank you in advance for your help."
Regards, and many thanks... DON'T MESS WITH IMEIs!!!
Click to expand...
Click to collapse
Hi , same things happen to me.I have mi note 10 lite.
before the dealing to imei I take modemst1,modemst2,and fsg backup via dd codes.
and take qcn and xqcn backup via qpst.
And after that In fastboot commend I write
"fastboot erase modemst1"
"fastboot erase modemst2"
"fastboot erase fsg"
so my imei have gone.When I edit the qcn ( imei1 and imei2 both) and flash back to the phone. phone is going to recovery mode and nvdata is corrupted error happen.There is two possibility to the save to phone. First one you wipe-data in stock-recovery or again in fastboot mode you have to erase modemst1,modemst2,fsg.
So I erased again and open the phone.
This time I edited qcn file (only imei2,imei1 codes deleted in codes line and string) so my edited qcn only exist imei2 codes.
so I flashed back to phone and imei1 shows 0 and imei2 shows my original imei(I want to recover my original imei). and after that in the adb I flashed my stock modemst1,modemst2,fsg via dd codes and (also some secret codes and combination ) and after reboot my both imei show and start working.I dont know the reason but somehow my phone skip the security.Interesetingly .I guess phone security in the software not to hardware.
I want to check something so I tried 20 time to flash my stock backups via dd codes but it is only work 2 time whenever I tried the flash and after reboot my phone add ramdump(app 2 gb every time) files in the main stroage ( I search it,it is crash log). Interesting
Right now I search to skip security so I find some codes in build.prop
"ro.miui.restrict_imei=1" I think this one cause the problem to change imei so I try to disable it but I cant change to build.prop because in android 10 you can't mount system(rw) so cant change to build.prop.I think only solution is flashing edited system.new.dat file but I cant decompile system.dat.file so .
After Android 10 magisk root app just work in systemless way(this is not even a root not like the old time).You have root but you cant change anything with root access so in originally this is not root and it is sucks and bull****.
Do you know any rom tool for the edit system.new.dat file or how can I create new custom rom so if I success it I want to change both imei. I googled it but every tool is too old to use.
Regards..
i have problem with mi 8 no basedband unknow and restart.....no qcn write...try with UMT or QFIL not work.
Mi Note 10 losts IMEIs after factory reset
gokmenm said:
imei repair is done.
the only problem is returning to "Factory settings" and imei is deleted.
Click to expand...
Click to collapse
Good morning, yes, I'm working on a brother in law's smartphone (tucana) and I notice same issue, can it be solved?
We also bought Hydra Dongle Qualcomm Tool and Software but I'm not able to fix the IMEIs on his Mi Note 10 (tucana)
Maybe you can help me (tucana)!
37berat37 said:
Hi , same things happen to me.I have mi note 10 lite.
before the dealing to imei I take modemst1,modemst2,and fsg backup via dd codes.
and take qcn and xqcn backup via qpst.
And after that In fastboot commend I write
"fastboot erase modemst1"
"fastboot erase modemst2"
"fastboot erase fsg"
so my imei have gone.When I edit the qcn ( imei1 and imei2 both) and flash back to the phone. phone is going to recovery mode and nvdata is corrupted error happen.There is two possibility to the save to phone. First one you wipe-data in stock-recovery or again in fastboot mode you have to erase modemst1,modemst2,fsg.
So I erased again and open the phone.
This time I edited qcn file (only imei2,imei1 codes deleted in codes line and string) so my edited qcn only exist imei2 codes.
so I flashed back to phone and imei1 shows 0 and imei2 shows my original imei(I want to recover my original imei). and after that in the adb I flashed my stock modemst1,modemst2,fsg via dd codes and (also some secret codes and combination ) and after reboot my both imei show and start working.I dont know the reason but somehow my phone skip the security.Interesetingly .I guess phone security in the software not to hardware.
I want to check something so I tried 20 time to flash my stock backups via dd codes but it is only work 2 time whenever I tried the flash and after reboot my phone add ramdump(app 2 gb every time) files in the main stroage ( I search it,it is crash log). Interesting
Right now I search to skip security so I find some codes in build.prop
"ro.miui.restrict_imei=1" I think this one cause the problem to change imei so I try to disable it but I cant change to build.prop because in android 10 you can't mount system(rw) so cant change to build.prop.I think only solution is flashing edited system.new.dat file but I cant decompile system.dat.file so .
After Android 10 magisk root app just work in systemless way(this is not even a root not like the old time).You have root but you cant change anything with root access so in originally this is not root and it is sucks and bull****.
Do you know any rom tool for the edit system.new.dat file or how can I create new custom rom so if I success it I want to change both imei. I googled it but every tool is too old to use.
Regards..
Click to expand...
Click to collapse
I read all your whole post and I can suggest to try to use XiaoMiFlash.exe of 2019-12-06 (WARNING: option below must be CLEAN ALL to save your unlocked state of the Bootloader) for flashing back to Android 9 in Fastboot mode original flash (those of about 4GB) , after that you can try to edit the build.prop with some Apps that work with root / Magisk.
But please, 1st I really urgently need your 4 partitions backup (also the fsc), can you send to me?
TIA and best regards!
effesse72 said:
I read all your whole post and I can suggest to try to use XiaoMiFlash.exe of 2019-12-06 (WARNING: option below must be CLEAN ALL to save your unlocked state of the Bootloader) for flashing back to Android 9 in Fastboot mode original flash (those of about 4GB) , after that you can try to edit the build.prop with some Apps that work with root / Magisk.
But please, 1st I really urgently need your 4 partitions backup (also the fsc), can you send to me?
TIA and best regards!
Click to expand...
Click to collapse
I am using mi note 10 lite not mi note 10 so there is no android 9 for mi note 10 lite
37berat37 said:
I am using mi note 10 lite not mi note 10 so there is no android 9 for mi note 10 lite
Click to expand...
Click to collapse
Sorry, I didn't know it.
Btw, did you already try File Explorer apps with root access?
37berat37 said:
Hi , same things happen to me.I have mi note 10 lite.
before the dealing to imei I take modemst1,modemst2,and fsg backup via dd codes.
and take qcn and xqcn backup via qpst.
And after that In fastboot commend I write
"fastboot erase modemst1"
"fastboot erase modemst2"
"fastboot erase fsg"
so my imei have gone.When I edit the qcn ( imei1 and imei2 both) and flash back to the phone. phone is going to recovery mode and nvdata is corrupted error happen.There is two possibility to the save to phone. First one you wipe-data in stock-recovery or again in fastboot mode you have to erase modemst1,modemst2,fsg.
So I erased again and open the phone.
This time I edited qcn file (only imei2,imei1 codes deleted in codes line and string) so my edited qcn only exist imei2 codes.
so I flashed back to phone and imei1 shows 0 and imei2 shows my original imei(I want to recover my original imei). and after that in the adb I flashed my stock modemst1,modemst2,fsg via dd codes and (also some secret codes and combination ) and after reboot my both imei show and start working.I dont know the reason but somehow my phone skip the security.Interesetingly .I guess phone security in the software not to hardware.
I want to check something so I tried 20 time to flash my stock backups via dd codes but it is only work 2 time whenever I tried the flash and after reboot my phone add ramdump(app 2 gb every time) files in the main stroage ( I search it,it is crash log). Interesting
Right now I search to skip security so I find some codes in build.prop
"ro.miui.restrict_imei=1" I think this one cause the problem to change imei so I try to disable it but I cant change to build.prop because in android 10 you can't mount system(rw) so cant change to build.prop.I think only solution is flashing edited system.new.dat file but I cant decompile system.dat.file so .
After Android 10 magisk root app just work in systemless way(this is not even a root not like the old time).You have root but you cant change anything with root access so in originally this is not root and it is sucks and bull****.
Do you know any rom tool for the edit system.new.dat file or how can I create new custom rom so if I success it I want to change both imei. I googled it but every tool is too old to use.
Regards..
Click to expand...
Click to collapse
Thank you for posting your findings on the thread! I believe the solution for Mi Note 10 users could be flashing Android 9 and changing that build.prop line, we need someone to confirm this. I hope you discover a fix for your phone as well, please write a step by step guide if so. Good luck!
I make a software by QFIL - after that imei null
I Have The Box with IMEI but I don't Know how to restore It ??
there any solution to fix the network?
You need to hex edit your IMEI into your QCN file and flash it back to the device. Also from QFIL.
Andrologic said:
You need to hex edit your IMEI into your QCN file and flash it back to the device. Also from QFIL.
Click to expand...
Click to collapse
Can you help me explain how to fix ?
alolbedoo said:
Can you help me explain how to fix ?
Click to expand...
Click to collapse
There are a lot of guides on XDA and elsewhere for the steps. However you need to first secure a working QCN file if you don't have a backup of your own and know the IMEIs in that file, so you can locate and overwrite with your own IMEI. Without that, you won't get far... I don't have a QCN file for this device on hand, maybe someone else here does and an share with you...
Andrologic said:
There are a lot of guides on XDA and elsewhere for the steps. However you need to first secure a working QCN file if you don't have a backup of your own and know the IMEIs in that file, so you can locate and overwrite with your own IMEI. Without that, you won't get far... I don't have a QCN file for this device by hand, maybe someone else here does and an share with you...
Click to expand...
Click to collapse
Thank you for your help I don't have a file QCN A search on the internet found a file name QCN-Patched
But I don't know how to use it
Andrologic said:
There are a lot of guides on XDA and elsewhere for the steps. However you need to first secure a working QCN file if you don't have a backup of your own and know the IMEIs in that file, so you can locate and overwrite with your own IMEI. Without that, you won't get far... I don't have a QCN file for this device on hand, maybe someone else here does and an share with you...
Click to expand...
Click to collapse
Is there a solution to unlock bootloader always Error11003
@Andrologic
Hey! I have been long trying to recover my nulled IMEI on ROG5. Every single tutorial I can find asks for a qcn file along with hex editor to input your box IMEIs. All follows up on my end until I use Qfil to restore a changed qcn file. It only writes till 2% and then phone goes into ramdump screen which means there's some kind of IMEI write protection on device or something like that. Because all other IMEI writing methods fail the phone to same RAM Dump screen. Desperate for some help.
Also there seems to be a problem getting diag mode to work on all stock ROMS. The only way diag mode works is by using ENG factory firmware on my ROG 5 which enables diag mode by default. The Asus_volte_su_fixed apk provided by @twistedumbrella Also doesn't enable diag mode on ROG5.
mhrs_1193 said:
@Andrologic
Hey! I have been long trying to recover my nulled IMEI on ROG5. Every single tutorial I can find asks for a qcn file along with hex editor to input your box IMEIs. All follows up on my end until I use Qfil to restore a changed qcn file. It only writes till 2% and then phone goes into ramdump screen which means there's some kind of IMEI write protection on device or something like that. Because all other IMEI writing methods fail the phone to same RAM Dump screen. Desperate for some help.
Also there seems to be a problem getting diag mode to work on all stock ROMS. The only way diag mode works is by using ENG factory firmware on my ROG 5 which enables diag mode by default. The Asus_volte_su_fixed apk provided by @twistedumbrella Also doesn't enable diag mode on ROG5.
Click to expand...
Click to collapse
Search results for query: AsusVoLTE
forum.xda-developers.com
The fix was to allow it to see your root, nothing more.
twistedumbrella said:
Search results for query: AsusVoLTE
forum.xda-developers.com
The fix was to allow it to see your root, nothing more.
Click to expand...
Click to collapse
ahh ok. So, basically we're stuck with a phone whose diag port can't be opened..
mhrs_1193 said:
ahh ok. So, basically we're stuck with a phone whose diag port can't be opened..
Click to expand...
Click to collapse
Dunno. I wasn't part of how that ended. I think it eventually got figured out.
mhrs_1193 said:
ahh ok. So, basically we're stuck with a phone whose diag port can't be opened..
Click to expand...
Click to collapse
This is not based on my own experience - but it looks like you may have access to write the IMEIs to this device via one of the ASUS Key partitions - in which case you may (or may not) be able to bypass writing QCN altogether.
I forgot the name of the guy who posted it, I believe it was under a CN>WW conversion guide - try to look it up and give it a try...
Andrologic said:
This is not based on my own experience - but it looks like you may have access to write the IMEIs to this device via one of the ASUS Key partitions - in which case you may (or may not) be able to bypass writing QCN altogether.
I forgot the name of the guy who posted it, I believe it was under a CN>WW conversion guide - try to look it up and give it a try...
Click to expand...
Click to collapse
The Imei part was mentioned in the very last part of thhis guide:
Repair ROG Phone 5 ZS673KS through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
These materials can only be used for ROG Phone 5_ZS673KS, and ROG Phone 5S_ZS676KS cannot be used. ROG Phone 5S ZS676KS Please see...
forum.xda-developers.com
Someone tried that for a seperate reason and apparently it changed their IMEI:
Repair ROG Phone 5 ZS673KS through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
These materials can only be used for ROG Phone 5_ZS673KS, and ROG Phone 5S_ZS676KS cannot be used. ROG Phone 5S ZS676KS Please see...
forum.xda-developers.com
Now, When I change the asuskey4 file, My IMEI do appear in the bootloader screen but when phone starts, it goes into a boot loop which stays even if I reflash the ENG firmware or stock firmware and ending in RAM dump screen.
Erasing the modemst1,modemst2 and fsg partitions from the phone does allow to get out of the bootloop. But shows Null Imei in the phone, while showing the IMEI in the bootloader screen.
So, apparently if I cannot restore the qcn file, There's no other way.
But Restoring QCN in ENG factoey firmware using QFIL or QPST only goes till 2% and then fails and phone goes to RAM Dump screen. Which apparently means that the phone has somekind of NV data write or IMEI write protection.
Writing QCN via Qfil goes till 2% then phone turns off and then status goes this 164% after which it shows that:
2022-05-05 08:53:19.685 Subscription ID:1 EFS File:/sd/mru001_ext_Subscription01, Function:NV_Tool_WriteNVsToMobile, Event:3 164%
2022-05-05 08:53:19.686 Done uploading the QCN file: C:\Users\mhrs_\Downloads\Compressed\GenericIMEI\patched.qcn, Sync EFS
2022-05-05 08:53:19.687 Done EFS Sync
2022-05-05 08:53:20.689 Reset Phone
2022-05-05 08:53:24.207 Restore QCN Fail:Restore QCN FailError in QTA.Phone.ModeControl :Error in setting phone mode to MODE_OFFLINE_D_F
2022-05-05 08:53:24.208 Finish Restore QCN
Attached is the log file from Qfil.
After this, phones goes into RamDump screen and when I hard reboot the phone, I can see IMEI changed from Null to 0 but still not my original IMEI :/
using qpst to restore only goes till 4% after which phone gets stuck in Ramdump screen.
Please help me to solve the network problem
alolbedoo said:
Please help me to solve the network problem
Click to expand...
Click to collapse
Searching for a solution myself.
mhrs_1193 said:
Searching for a solution myself.
Click to expand...
Click to collapse
Hi, Guys. I have the same problem since few days... Hope we will find a solution soon.
You cannot use others's qcn file to restore your imei. The imei store in fsg, modemst1, modemst2 also in your qcn file. If you use others qcn then they don't match each other, you'll failed to restore. The key: you need to empty the partition of fsg, modemst1, modemst2 in oder to restore other qcn file, but the system is read only so you cant do anything.