I was suffering IMEI null but I fix that after that I can't flash any thing to my mi A1 even magisk . I use qcn file to restore my IMEI . Any solution to this.
Take backup of EFS partition
Flash anything (Magisk / rom / whatever ...)
If you get IMEI null / no baseband, boot to recovery and restore EFS Partition
Restart many times and will be okay
Press power button till restart
Try 5_6 times
I have same issue
Related
Hello everybody, today I have installed twrp 2.8.6.0 for n8000 through odin. for odin the flash was corrected because the program say "pass" but when my tablet have turned on, I haven't cellular signal so I went to settings if there was problem and my baseband is now unknown and in consequence my imei is null/null.
I have tried to reinstall again the twrp but nothing and also I have tried to install the original recovery but nothing, I havent' signal.
What can I do to recover baseband and imei?
I have Note n8000 4.4.2 buid n8000xxudof1. In EFS folder there is all files (nv_data.bin, nv_data.bin.md5)
Restore your backed up EFS folder as per forum identical posts .
I have strong reasons to believe latest TWRP is bigger than portion size that hold recovery and by flashing it you ruined modem partition. It happened to me few times. So do following: find older smaller size TWRP or other recovery like CM or based on it. Find correct modem for your model and region which is flashable in recovery. Boot into your recovery and flash first alternative recovery, reboot into recovery and flash modem. You should be OK and no data will be lost in that way. Flashing just modem in your TWRP will produce boot loop with very high probability and you would need to use flashing tools on PC, so be careful. Good luck and nice weekend.
Sent from my A0001 using Tapatalk
JJEgan said:
Restore your backed up EFS folder as per forum identical posts .
Click to expand...
Click to collapse
I haven't a backup of efs folder because first I installed the recovery and then I have done the root so I haven't the possibility of efs backup, probably in this way I made a mistake
AndriiG said:
I have strong reasons to believe latest TWRP is bigger than portion size that hold recovery and by flashing it you ruined modem partition. It happened to me few times. So do following: find older smaller size TWRP or other recovery like CM or based on it. Find correct modem for your model and region which is flashable in recovery. Boot into your recovery and flash first alternative recovery, reboot into recovery and flash modem. You should be OK and no data will be lost in that way. Flashing just modem in your TWRP will produce boot loop with very high probability and you would need to use flashing tools on PC, so be careful. Good luck and nice weekend.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Ok, I'll try. I have finded an old twrp and now I'll search for modem. Thanks for suggestion
I'm also unable to mount system in TWRP even after ticking it, so no ROMs are getting flashed.
I'm able to use WiFi properly, however, there is no sim detected and no IMEI either.
I have multiple EFS backups on TWRP as well as the modemst1 and modemst2 files.
Even after restoring the EFS backups, it doesn't help.
Any ideas on what I should do next?
Try finding system image and flash it via fastboot
Or tool.
But it will lose all data so be careful and try backing up on your pc.
Sometimes just flashing original system image can bring them back. But don't mess up too much wid it. Bcz i have dead note 2 bcz of that.
So try to flash system image full may ne it will help.
I dont know much about this, still a slight noob but did you flash the 15 may firmware in addition to the cm12 firmware and any firmware your rom suggests. I have a small collection of firmware files but I dont think I can upload or link them here :/
I created this thread just to help anyone with the same problem I had when restoring a TWRP backup on a ZTE Blade L3. The SIM Card was not detected at all!
The complete situation: I made a backup of a stock rom (4.4.2) with my stuff using TWRP (2.8.7.0) and when I restored it, the SIM card was not detected at all. In MTK Engineering Mode/CDS Information/ Phone x (or whatever number yours is) everthing was at null or unkown.
AND I FOUND A WAY TO SOLVE THIS!
Flash a ROM that detects the SIM card and enter the IMEI numbers. Then, go to TWRP, DON'T FORMAT ANYTHING and then restore the backup selecting the options to restore that you want (for example boot; nvram; system;... those ones). In my case, I restored all of them and I got it to work! I hope this helps! This because the phone memory needs to be installed and with android 4.4.2 kitkat the phone storage is not in the backup, only the system storage. I hope this helps the KitKat users and others (because I've never tested this in other versions)!
Cheers.
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
pr10dr said:
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
Click to expand...
Click to collapse
You just need to flash the latest G930F for Germany. The firmware code is DBT, it's unbranded so no netweork provider bloatware.
I've attached Samfirm tool. It gets the latest firmware straight from samsung servers version 8.
1. Unzip
2. Run application as admin
3. Check auto box
4. SM-G930F in Model box
4. DBT in Region box
5. Check Update
6. Wait to finish
7. Flash files with Odin
8. New Phone.
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Alright i think i resolved part of the issue as follows:
* i flashed the complete stock firmware as described above
* After flash was done i rebooted again into download mode and installed TWRP as recovery via odin
* I then booted into TWRP and copied the "no-verity-opt-encrypt" in the latest version to the phone
* The zip of "no-verity-opt-encrypt" i then installed with TWRP.
The phone booted up. Factory Samsung Android works but the imei is still shown as empty / unknown.
Some guides suggest to flash a factory combination image but i can not find one for bootloader version 8 which is on my phone.
pr10dr said:
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Click to expand...
Click to collapse
Yes sometimes this happens, try a different firmware like United Kingdom BTU.
Does Odin say Pass?
The updating and erasing screen is normal after flash just leave it.
Once the phone boots on BTU you can either change language to German or flash DBT again.
It's worth checking / reinstalling Samsung drivers. Use different USB port. Odin should be version 13.
As long as you can boot into download mode the problem is fixable.
Thanks for your advice.
I will try the BTU firmware later. Just to check we are on the right track: If i understand you correctly you are saying the lost imei will be "fixed" by installing either the BTU or DBT stock firmware via odin?
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
pr10dr said:
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
Click to expand...
Click to collapse
OK it sounds like the BL info on the EFS is missing or corrupt.
Just try one more thing before trying to repair the EFS.
Flash firmware again with Odin but uncheck "auto reboot"
When passed in Odin disconnect phone.
Hold volume down+home+power. As soon as the screen goes back move your finger to volume up while still pressing home +power. You want to boot into system recovery. It may take a few attempts.
Once in system recovery, wipe data/factory reset and reboot phone.
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
pr10dr said:
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
Click to expand...
Click to collapse
Anyone offering money to fix or connect to a server is a scammer, stay clear.
To repair the EFS you have to get the stock firmware back on there or flash someone esle's EFS back up file. You can buy a damaged S7, install TWRP, back up the EFS to the SD card, put that sd card in your phone then restore the efs. Your phone will then take on the identity of the phone the EFS file came from. Effectively you will have a new IMEI number and mac address. As long as the donor phone is not registered on the network your phone will work fine. You cannot have two phones with the same IMEI registered on the network, both will be blocked and black listed. Obviously the donor phone must be exactly the same model as yours.
However the method below should be tried first.
The error with the text "failed to open recovery" means the phone cannot find the partition where the stock recovery file is located.
Now to solve this we can install TWRP with ODIN and that will provide a way to install the stock firmware in .zip format direct from the sd card using TWRP as the recovery method instead of the inbuilt stock recovery which cannot be found.
You should then be left with a phone which has a restored EFS with your original IMEI and other data with TWRP as the recovery tool.
Which ever method you choose TWRP must be installed first.
I made a full backup via TWRP before testing out OOS13, and when did a wipe, and a full restore I got a Qualcomm modem boot error "Crashdump Mode".
I flashed a clean signed flashable zip od OOS11 11.0.12.12 and tried again and again. I have been 12h of trying so Im lost.
Long story short:
If I have a full twrp backup, how can I restore it and not get a Qualcomm modem boot error?
walthroughs of restoring are old and dont have the "super" restore option I includes more than just system.
Im at a loss.
Update: I got rid of the Qualcomm modem boot error "Crashdump Mode".
My problem is that if I restore the DATA partition, with or without other partitions, the phone boots, with logo, but the screen turns black and when holding power and/or volume I get a prompt that "com.android.phone" is crashing.
So in short, any solution for this? I thought a complete Nandroid backup would exclude these things.
It's normal to get the black screen and phone crash message after restoring data in TWRP. Just reboot the phone again and it should then come up cleanly.
Read the OP of the TWRP thread. It tells you to do this.
BillGoss said:
It's normal to get the black screen and phone crash message after restoring data in TWRP. Just reboot the phone again and it should then come up cleanly.
Read the OP of the TWRP thread. It tells you to do this.
Click to expand...
Click to collapse
This is probably the link to the thread, and thanks, it was eye opening, disable password before restoring the data partition and removing the sim card might been what causes the com.android.phone to crash and the display to be blank other than the crash pop-up.
You'll find similar requirements for TWRP 12 when restoring a backup (look in the TWRP 12 thread in the same forum).