last year my mobile become hard bricked due to use of KDZ Tools. It was dead. Last month i repaired it through mobile shop. My mobile become alive.. but they send me a mobile which has no IMEI. They said they are unable to restore my IMEI. Luckily i have nv file backup. I used it to restore my IMEI Number. Now everything working fine BUT THERE IS NO CARRIER and showing SECURITY ERROR / EMERGENCY CALLS ONLY error.
I consulted many member's on xda.. some of them said it happened because of faulty nv file.. so i arranged an another nv file from a xda member.
after flashing the ANOTHER NV file... SAME PROBLEM STILL THERE...
i tried to flashed OLD/NEW Baseband and even through flash firmware again through KDZ / LGmdp.
what i did wrong.. guide me please ... :crying:
You need IMEI from a member different than your country. For example, if you are in Romania, consult an Indian/American etc. member here for IMEI
Used one another nv file. I got it through a member. Nv file related to same country, i used it to just verify the problem.
Is there any other reason?
Try flashing the old bb fix after mounting system in recovery...
@warlock911, I had exactly same problem.
You have only two solutions, any other will be unsuccessful.
Believe me I tried everything very deep.
1. Preferred
Find repair shop with special box – VygisToolbox.
Only it can repair security zone and also restore original IMEI.
2. Constrained
I can provide you specific correct fullflash file.
Copy it on usb-drive and go to any repair store.
Tell guys just to write that file via JTAG.
Then problem will gone, BUT you will have not original IMEI.
Writing your NV-backup don't restore your IMEI because security zone block this.
WARNING: changing IMEI can be illegal in your country!
Bonoboo said:
@warlock911, I had exactly same problem.
You have only two solutions, any other will be unsuccessful.
Believe me I tried everything very deep.
1. Preferred
Find repair shop with special box – VygisToolbox.
Only it can repair security zone and also restore original IMEI.
2. Constrained
I can provide you specific correct fullflash file.
Copy it on usb-drive and go to any repair store.
Tell guys just to write that file via JTAG.
Then problem will gone, BUT you will have not original IMEI.
Writing your NV-backup don't restore your IMEI because security zone block this.
WARNING: changing IMEI can be illegal in your country!
Click to expand...
Click to collapse
i am still in problem.... can you still provide me fullflash file now??
warlock911 said:
can you still provide me fullflash file now?
Click to expand...
Click to collapse
Link into your PM.
Please, write here about result.
I am in need of some help. I have a galaxy s7 that the efs files have been deleted, therefore, it wont connect to any network as well as unknown base band. when i type in *#06# mt imei number is null (all zeros). I have tried flashing stock firmware onto the device but that doesnt help. I dont know which combination binary software to install because i dont know the correct pda for the device. i am looking for any help to fix this problem.
note: i have another s7 with all the files i think i need, is there anyway to swap the files into the toher device and have it generate its original imei number ?
impure2live said:
I am in need of some help. I have a galaxy s7 that the efs files have been deleted, therefore, it wont connect to any network as well as unknown base band. when i type in *#06# mt imei number is null (all zeros). I have tried flashing stock firmware onto the device but that doesnt help. I dont know which combination binary software to install because i dont know the correct pda for the device. i am looking for any help to fix this problem.
note: i have another s7 with all the files i think i need, is there anyway to swap the files into the toher device and have it generate its original imei number ?
Click to expand...
Click to collapse
You need a backup of the efs folder of that device. If you never did one using a custom recovery like TWRP you are doomed. I believe that there are boxes like the Octopus one that, if you know the imei of the device they can flash that partition/folder and assign the device its imei once again. I don't know if the official service will be willing or able to fix the imei issue, I would suggest reaching out to them and ask.
Sent from my SM-G930F using Tapatalk
Greetings,
I would like to ask for anybody's help on fixing a dilemma that I can't seem to solve due to how limited my knowledge is.
Colleague messed up his phone very bad, he was trying to "Unlock" his phone through SamsungTool. Here's what happened;
1. Phone is carrier locked.
2. Read a guide that suggests that he should flash a "lower" baseband.
3. Flashed a lower modem file through Odin. Didn't backup EFS. But did take a photo of IMEI and S/N using *#06#.
4. Faced with DRK error. Phone is inaccessible.
5. Rooted the phone to remove DRK error.
6. Phone is now accessible. Used *#06#, IMEI is now 3500000000006, S/N is none.
7. Force flashed IMEI using Samsung Tool. Luckily, he took a photo of the *#06# details.
8. IMEI is now in place but MEID is different, S/N says "None"
Is there in anyway in fixing this?
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.