Database Develop

IMEI - Repair [Just A Flashable Zip] [ The Fastest Way ] For All Android One Devices

Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
https://www.dropbox.com/s/9pzf18wxtj7i40l/IMEI MAKER.zip?dl=0
& IMEI REPAIR.zip
SCREENSHOT
https://www.dropbox.com/s/4p2rwoi5oxpth15/IMEI REPAIR.zip?dl=0
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
https://www.dropbox.com/s/o0vs89lob4yf4pv/vlcsnap-2015-01-03-22h23m53s216.png?dl=0
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
https://www.dropbox.com/s/lbdzp9ko0t9yons/vlcsnap-2015-01-03-22h24m10s140.png?dl=0
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
https://www.dropbox.com/s/j0uss286iv94red/vlcsnap-2015-01-03-22h24m48s31.png?dl=0
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
http://www.dropbox.com/s/femtg309chk147v/vlcsnap-2015-01-03-22h25m03s169.png?dl=0
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
https://www.dropbox.com/s/y1ign53lmqrwubs/vlcsnap-2015-01-03-22h26m03s7.png?dl=0
https://www.dropbox.com/s/bsbd0s1jhjt4eww/vlcsnap-2015-01-03-22h26m07s44.png?dl=0
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
http://youtu.be/8DT-32tPbMY
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:

Sagar Kapasi said:
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
https://www.dropbox.com/s/9pzf18wxtj7i40l/IMEI MAKER.zip?dl=0
& IMEI REPAIR.zip
SCREENSHOT
https://www.dropbox.com/s/4p2rwoi5oxpth15/IMEI REPAIR.zip?dl=0
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
https://www.dropbox.com/s/o0vs89lob4yf4pv/vlcsnap-2015-01-03-22h23m53s216.png?dl=0
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
https://www.dropbox.com/s/lbdzp9ko0t9yons/vlcsnap-2015-01-03-22h24m10s140.png?dl=0
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
https://www.dropbox.com/s/j0uss286iv94red/vlcsnap-2015-01-03-22h24m48s31.png?dl=0
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
http://www.dropbox.com/s/femtg309chk147v/vlcsnap-2015-01-03-22h25m03s169.png?dl=0
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
https://www.dropbox.com/s/y1ign53lmqrwubs/vlcsnap-2015-01-03-22h26m03s7.png?dl=0
https://www.dropbox.com/s/bsbd0s1jhjt4eww/vlcsnap-2015-01-03-22h26m07s44.png?dl=0
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
http://youtu.be/8DT-32tPbMY
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Click to expand...
Click to collapse
didnt help..it didnt work

Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).

What You Did
How it didn't helped
Can you say something about it?
-Adarsh- said:
didnt help..it didnt work
Click to expand...
Click to collapse

Here We Are Taking About An Error Which Occurs Mainly After flashing stock Rom On Android One Devices And Yes We Cannot make phone calls in this situation too, So here a Guide to fix it
my imei was also gone that's why this guide
the_prodigal_coder said:
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
Click to expand...
Click to collapse

Got an error:
set_perm: some changes failed
E:Error in IMEI Repair.zip
(Status 7)
Installation Aborted

the_prodigal_coder said:
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
Click to expand...
Click to collapse
I accidentally restored the EFS partition from one Nexus 5 to another and ended up with an IMEI of all zeros. It can happen. I was able to repair it with Qualcomm software, but the phone still doesn't see the network. Possibly an antenna issue...
Anyway, it can definitely happen. Also, it is illegal to change your IMEI (in the US at least). I would think it's OK to repair one however. I think the OP should specify that this method should only be used to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray. Check documentation for your model.

Help Needed !! IMEI Fix for Android One not working for me...
I was using CM11 sprout earlier and tried moving back to Stock. I lost my IMEI during this time. I have moved to stock kitkat by doing scatter loading of stock firmware. I have rooted my Android one with CWM recovery. I have used the above tools and generated the MTB_001 and created a zip and installed it with recovery. But, still i have my IMEI as invalid. I even tried replacing the MTB_001 file manually using ES_File explorer and giving permissions 777. Still no luck.
Can someone help me out on how to load proper IMEI as am completely blocked :crying::crying::crying::crying:
Thanks in Advance.

Great Guide! Liked it..Step by Step guide!
But i dont understand why people flash so much..where there is Official Lollipop & CM12 Available for us! Flash Freaking People! :/

You Should Tick All W-R-T All The 9 Then Only It Will Work & Dont Forget To Reboot
SpiceAndroidOne said:
I was using CM11 sprout earlier and tried moving back to Stock. I lost my IMEI during this time. I have moved to stock kitkat by doing scatter loading of stock firmware. I have rooted my Android one with CWM recovery. I have used the above tools and generated the MTB_001 and created a zip and installed it with recovery. But, still i have my IMEI as invalid. I even tried replacing the MTB_001 file manually using ES_File explorer and giving permissions 777. Still no luck.
Can someone help me out on how to load proper IMEI as am completely blocked :crying::crying::crying::crying:
Thanks in Advance.
Click to expand...
Click to collapse

Installation aborted in canvas A1.
When i m flashing the zip file it says installation aborted in canvas A1.:crying::crying::crying::crying::crying:

aryan9090 said:
When i m flashing the zip file it says installation aborted in canvas A1.:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Try to copy paste the IMEI file you just made manually to the directory which is in the main post. It works on my Sparkle V everytime(the copy-paste method).

Does not work for me... please help.....
Sagar Kapasi said:
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
& IMEI REPAIR.zip
SCREENSHOT
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Click to expand...
Click to collapse
I followed complete steps and it got installed successfully but the IMEI is still 0 !! Does this even works on Nexus 5? Please help.

deepak21 said:
I followed complete steps and it got installed successfully but the IMEI is still 0 !! Does this even works on Nexus 5? Please help.
Click to expand...
Click to collapse
did you replace the file and rename it (just asking).

Saurabh K said:
did you replace the file and rename it (just asking).
Click to expand...
Click to collapse
Yes, I did... I followed every step very carefully and there were no error message at all.. everything was successful.

deepak21 said:
Yes, I did... I followed every step very carefully and there were no error message at all.. everything was successful.
Click to expand...
Click to collapse
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply

Saurabh K said:
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Click to expand...
Click to collapse
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Saurabh K said:
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Click to expand...
Click to collapse
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?

deepak21 said:
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
Click to expand...
Click to collapse
I have the stock KITKAT 4.4.4 nvram image, but I dont know will it work. I will try to extract the image from stock 5.1 and reply soon...
---------- Post added at 09:09 AM ---------- Previous post was at 08:56 AM ----------
deepak21 said:
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
Click to expand...
Click to collapse
sorry, but i couldn't backup the 5.1 stock nvram but i will send you nvram.img from stock kitkat ROM. Flash and redo the procedure from scratch...and tell your device model also..

First point to note is that only full formatting makes the device lose IMEI,not normal data,system,cache formatting which is required for installing custom roms.When your partition table is messed up you get lots of errors when trying to wipe or mount any partition from custom recoveries,thus leaving you with only option to format before flashing stock rom through sp flash tools.It is after this flash that nvram loses your unique IMEI number.In my case I had backed up my stock rom through cwm recovery,now to restore my IMEI, I just extract the contents of /data/nvram/.....NVD_IMEI from my backup( three files in total) and push it to my to the same directory using adb push command,and it works for me.There is no need to push three cos only one file is relevant .But this is only temporary solution,cos after every reset you will lose your IMEI. It is better to backup the nvram partiton using dd command so that it could be flashed later,which would persist through installs.

tealio said:
I accidentally restored the EFS partition from one Nexus 5 to another and ended up with an IMEI of all zeros. It can happen. I was able to repair it with Qualcomm software, but the phone still doesn't see the network. Possibly an antenna issue...
Anyway, it can definitely happen. Also, it is illegal to change your IMEI (in the US at least). I would think it's OK to repair one however. I think the OP should specify that this method should only be used to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray. Check documentation for your model.
Click to expand...
Click to collapse
please brother how did you "repair it with Qualcomm software to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray"? please can you pm me or email: [email protected] the software and guide pleeeeeeeeeeeeeeeeeeeeaaaaaaasssssssssssseeeeeee
need to fix my htc mytouch 4G and my LG vu II
Thanks

no recovery, no download mode, no micro usb, but root?

hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks

mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
How did you install that Hong Kong lollipop?

mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.

i installed hk lollipop zip from my custom twrp recovery. and when rom istall has finished ; recovery gone.

mrp1375 said:
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.
Click to expand...
Click to collapse
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.

mca1 said:
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.
Click to expand...
Click to collapse
Below are 2 solutions to get a properly working recovery
Preperation:
1. Download Dual recovery installer: XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip
2. Install NDRUtils
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this: http://nut.xperia-files.com/path/XZDualRecovery/Kernel_Builder
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: X-plore File Manager The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!

thank you

mca1 said:
thank you
Click to expand...
Click to collapse
Does that mean it worked?

tetsuo55 said:
Does that mean it worked?
Click to expand...
Click to collapse
Yes it worked, thank you much. :good:

tetsuo55 said:
Below are 2 solutions to get a properly working recovery
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this:
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!
Click to expand...
Click to collapse
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!

comcastic08 said:
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!
Click to expand...
Click to collapse
That error sounds like either you dont have root or you have a typo, can you make a screenshot?

tetsuo55 said:
That error sounds like either you dont have root or you have a typo, can you make a screenshot?
Click to expand...
Click to collapse
snag. gy/gi8Ji. jpg
sorry i cant post links yet

comcastic08 said:
snag. gy/gi8Ji. jpg
sorry i cant post links yet
Click to expand...
Click to collapse
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.

tetsuo55 said:
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.
Click to expand...
Click to collapse
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh

comcastic08 said:
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh
Click to expand...
Click to collapse
Can I have another screenshot of that?

tetsuo55 said:
Can I have another screenshot of that?
Click to expand...
Click to collapse
snag .gy/AekHa. jpg

comcastic08 said:
snag .gy/AekHa. jpg
Click to expand...
Click to collapse
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.

tetsuo55 said:
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.
Click to expand...
Click to collapse
snag. gy/aWyCY .jpg

comcastic08 said:
snag. gy/aWyCY .jpg
Click to expand...
Click to collapse
All i can think of is that you have the wrong boot.img

tetsuo55 said:
All i can think of is that you have the wrong boot.img
Click to expand...
Click to collapse
i downloaded the one you said XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and renamed it to boot.img
even the twrp.img doesnt work ugh

[FIX] Empty IMEI, Unknown Baseband, No SIM, WiFi/Bluetooth unusable, Corrupted EFS

My EFS partition was corrupted after an EFS restore from TWRP (Check post #2 for link to explanation).
I was in panic mode when the super helpful folks over at #twrp sorted me out with this solution (thank you so much @jcadduono). Thought I would share it so it could possibly help someone else.
This has worked on my OnePlus 3, but it might even work on other devices.
Do this AT YOUR OWN RISK. I am not responsible for your device.
Boot into TWRP (Poweroff, then power on using Vol Down + Power Button)
Go to Advanced > Terminal
Type in the following commands:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot
Alternatively, you could also do this from your computer over adb with the following commands:
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
Alternatively, you could try this [Though I haven't tested this myself]:
Make sure you have fast boot and drivers (for info look here)
Boot into fastboot (Poweroff, then power on using Vol Up + Power Button)
Type in the following commands into terminal:
Code:
fastboot erase modemst1
Code:
fastboot erase modemst2
Reboot
Good luck and I hope this helps!
PS: It is best to backup your EFS before something like this happens.
Take 5 minutes out of your day to do this. You can find a tool to do this here, or do it yourself by following the instructions here.

I'm just going to go ahead and link here for an explanation:
http://forum.xda-developers.com/showpost.php?p=68500121&postcount=64
BTW: Is this issue still present on OnePlus 3 official TWRP? If so we can recompile it, we *should* have all the bugs fixed in android-6.0 latest branch right now. Currently main development is happening on android-7.0 branch of omnirom/android_bootable_recovery (TWRP) but we've backported bug fixes to android-6.0 only and it's probably a good idea for developers to use that as a "stable" branch for now.

jcadduono said:
I'm just going to go ahead and link here for an explanation:
http://forum.xda-developers.com/showpost.php?p=68500121&postcount=64
BTW: Is this issue still present on OnePlus 3 official TWRP? If so we can recompile it, we *should* have all the bugs fixed in android-6.0 latest branch right now. Currently main development is happening on android-7.0 branch of omnirom/android_bootable_recovery (TWRP) but we've backported bug fixes to android-6.0 only and it's probably a good idea for developers to use that as a "stable" branch for now.
Click to expand...
Click to collapse
So, I'm not sure what version of TWRP I used to backup, but whatever it was, I only had a single efs backup (efs1.emmc.win). efs2.emmc.win was not present at all. I am guessing during restore, this is what must have caused the problem. I am not sure if TWRP should be checking for sub partitions before restore, but it definitely didn't throw any errors. Only if I had md5 check enabled did it complain that the md5 did not match '' (empty string), which is when I realized what had happened.

kgs1992 said:
So, I'm not sure what version of TWRP I used to backup, but whatever it was, I only had a single efs backup (efs1.emmc.win). efs2.emmc.win was not present at all. I am guessing during restore, this is what must have caused the problem. I am not sure if TWRP should be checking for sub partitions before restore, but it definitely didn't throw any errors. Only if I had md5 check enabled did it complain that the md5 did not match '' (empty string), which is when I realized what had happened.
Click to expand...
Click to collapse
Yeah the adb backup patch went in and broke restore and backup of subpartitions, backup was fixed not much later so you must have had a twrp build from just after the adb backup patch (which broke stuff), it wasn't for a few weeks until the restore issue was noticed, where it restored 1st partition in the backup to all subpartitions of it. Those are all fixed now but there could still be builds out there with any or all of those issues.
Reason it wasn't so noticed was not many devices with multiple subpartitions attached to one partition and not many people backing up and restoring efs. (which is often subpartitioned in twrp)

3rd way worked for me. thx

NickosD said:
3rd way worked for me. thx
Click to expand...
Click to collapse
You're welcome, but it's the folks at twrp that deserve to be thanked.

sry if my question too noob
but im curious
whats that "fastboot erase modemst1" meaning?
delete something or what?
im google it before asking here, haha

D4almond said:
sry if my question too noob
but im curious
whats that "fastboot erase modemst1" meaning?
delete something or what?
im google it before asking here, haha
Click to expand...
Click to collapse
Yes, you are erasing that partition, which the modem then rebuilds, as mentioned in the link in post #2

Thx for the explanation!
Nice thread btw, i believe this will save many hard ass out there, kek
Sent from my A0001 using Tapatalk

This worked successfully on my Mi 5. So basically I restored a backup with TWRP 3.0.2-2 and it messed up my modem, lost IMEI etc.
I followed the steps in TWRP itself > Terminal and typed the codes. Rebooted and worked.
Thank you so much for putting up the guide. I though I'd be buying an iPhone 7+ or LGV20 but because this fixed my phone, you saved me a lot of money.

@ northropgrummanrq180
Please Help ME! Save US!
http://forum.xda-developers.com/mi-5/how-to/xiaomi-mi5-efs-backup-restore-methods-t3432730
https://xiaomi.eu/community/threads/mi5-no-imei-no-modem-no-baseband-need-help.36225/

Thank you for sharing this and everyone at TWRP!!!!!!! I thought my phone was deader than a door nail!!! Method 1 worked for me perfect. Has this bug been fixed yet in the latest official version of TWRP??

I've fixed my MI5, which didn't have a baseband anymore after I've accidentally restored the efs in TWRP, using this tutorial. Thanks so much!

kgs1992 said:
My EFS partition was corrupted after an EFS restore from TWRP (Check post #2 for link to explanation).
I was in panic mode when the super helpful folks over at #twrp sorted me out with this solution (thank you so much @jcadduono). Thought I would share it so it could possibly help someone else.
This has worked on my OnePlus 3, but it might even work on other devices.
Do this AT YOUR OWN RISK. I am not responsible for your device.
Boot into TWRP (Poweroff, then power on using Vol Down + Power Button)
Go to Advanced > Terminal
Type in the following commands:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot
Alternatively, you could also do this from your computer over adb with the following commands:
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
Alternatively, you could try this [Though I haven't tested this myself]:
Make sure you have fast boot and drivers (for info look here)
Boot into fastboot (Poweroff, then power on using Vol Up + Power Button)
Type in the following commands into terminal:
Code:
fastboot erase modemst1
Code:
fastboot erase modemst2
Reboot
Good luck and I hope this helps!
PS: It is best to backup your EFS before something like this happens.
Take 5 minutes out of your day to do this. You can find a tool to do this here, or do it yourself by following the instructions here.
Click to expand...
Click to collapse
"by-name" here means?

I didn't have wi-fi unusable or anything on my OP3, but I was only getting signal for emergency calls before trying a series of things including this. This happened after flashing open beta 9 from an earlier community build. First let me just say in my case in TWRP I wiped then changed /data partition to f2fs and clean flashed the beta as usual along with superSU. Then started my phone and realized I was only able to make emergency calls.
So I tried playing in Settings > Sim & Network > SIM 1 & tried resetting network operators & finding automatically. That may have helped.. but I didn't see any improvement so I removed my sim, reinserted & restarted. It didn't seem to be fixed by then so I tried the 3 methods OP posted. Only#1 worked in my case, but data appears to be working normally now. Whether it was the last thing I tried or some combination, IDK.
Just wanted to write all this out in case anyone is still having issues after following OP's instructions.
Thanks!

Used the dd commands in both adb shell and twrp terminal and get "dd: /dev/block/bootdevice/by-name/modemst1: No space left on device". Also tried the fastboo0t commands and got "FAILED (remote: Partition flashing is not allowed)" Any ideas?

Worked like a charm
Thank you so much! you just saved my new Mi5 prime which i messed up by trying to unlock more LTE bands.

kenboyles72 said:
Used the dd commands in both adb shell and twrp terminal and get "dd: /dev/block/bootdevice/by-name/modemst1: No space left on device". Also tried the fastboo0t commands and got "FAILED (remote: Partition flashing is not allowed)" Any ideas?
Click to expand...
Click to collapse
am also having the same issue with my htc one e8, am getting remote: partition is not allowed. Please anyone with a solution about this should share

thank you very much hope GOD replied to your knowledge

Great explanation! My phone was stuck in a soft-brick mode yesterday. Followed the mega unbrick guide and got it working again, albeit being reverted to OOS 3.1.2. The cellular network is fine (I can make and receive calls, and mobile data is working), although WiFi and Bluetooth don't work. I tried rebooting into fastboot and erasing the two
Code:
modemst
files but to no avail.
Any reason as to why this is happening?

moto e4 plus owen xt1776 vram backup

could someone with this model run these and give me the images
dd if=/dev/block/platform/.../.../by-name/nvram of=/sdcard/nvram.img
dd if=/dev/block/platform/.../.../by-name/nvdata of=/sdcard/nvdata.img

suckme69 said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post75038379
Click to expand...
Click to collapse
I would, but those are not block partitions that can be pulled like that.
Sent from my Moto E (4) Plus using XDA Labs

i dont know the excact block but my imie wifi baseband and bluetooth do not work ans was told i flashed my nv ram wouldyou know how to repair this?

Those are not block partitions on this device. I think they are only on Mediatek devices and your XT1776 is Qualcomm. You should probably try flashing stock firmware with fastboot or RSDlite. Download the one with owens_sprint_7.1.1 in the title.

i have like 5 times and i get null imei

Try flashing this modem/fsg:
https://www.androidfilehost.com/?fid=962157660013069126

nope did nothing

https://youtu.be/I8V9ud4PGUk

thats how i been flashing because in windows 10 rsd lite dont work

You should thank me later !
Copy and paste.
Click Here ! #Post8
EDIT : i don't have that device anymore. so i can't help you with this. unable to remind the full directory name.
EDIT : Here is the correct path.
---- For MediaTek Variant ----
Nvram :
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram of=/sdcard/nvram.img
Nvdata :
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata of=/sdcard/nvdata.img
---- For Qualcomm Variant ----
Nvram :
dd if=/dev/block/bootdevice/by-name/nvram of=/sdcard/nvram.img
Nvdata :
dd if=/dev/block/bootdevice/by-name/nvdata of=/sdcard/nvdata.img

They are not at that path on the Qualcomm variant. I'd post a screenshot if I could here.

drop here you device recovery.fstab data.

how do i get that?

https://github.com/ReimuHakurei/twrp_device_motorola_owens/blob/twrp/twrp.fstab

did anyone figure anything out?

Yes, your phone is probably basically a tablet now. When your problem started, what exactly did you do? Did you flash LineageOS or something without activating the phone on stock firmware first? Did you run any fastboot erase commands like fastboot erase recovery? If so, you should not ever do either of those. The only thing I can say to try, is to remove the sim card, flash stock firmware, boot the phone to the setupwizard and then power it off. Next re-insert the sim card and turn the phone back on. If you don't get it to connect now, or if you didn't activate it already, try calling your carrier customer service and see if they can help you.

In MediaTek, variant IMEI stored in Nvram partition (non-volatile random access memory). whereas in Qualcomm Variant it is stored in raw EFS, modemst1 & modemst2 partition. Probably you lose your device nvdata and it is of no use. Service center guy can fix this by replacing a small chip within the motherboard (in my case its *PCB*). After all this you will get a new imei number.
Hope this helps.

i flashed the files in the order my flash file said i generated the commands by hand because i could not find any on xda for my device

@suckme69 Try this, either with adb with the OS booted or with a terminal emulator on your device, type:
reboot nvbackup
With terminal emulator you'll have to type su then enter for su permissions. Hope this works!

thanks for your guys help but i finally figured it out for some reason my modem image from my sprint stock package i downloaded didn't work or i wrote the sequence wrong.but i decided to flash the partition package for boot on my sprint phone from getoffmylawns forum but it was giving my crashing for my phone ,phone has crashed but i got service!. so i opened up the boost flash package and got the modem image off there. after flashing my stock firmware package threw the boot-loader i then flashed the modem i pulled from the boost partition zip . i was also flashing threw Ubuntu with the rsd lite someone posted because rsd lite doesn't work with windows 10 .and the reason i decided to flash the boost package because well it was the same model phone and the carriers boost and sprint are the same they use the same towers and sprint owns boost so i saw no harm done.

Slot Sim 1 or 2 problems on Mi A2 4/32

Hi everyone, thanks in advance for anyone who will help me solve my A2 problem.
1. With the SIM in slot 1 It works calls and sends and receives SMS but does not connect in 4g (I think it's an IMEI problem) I also tried different APNs for my manager (Vodafone IT) but nothing
2. With the SIM in slot 2 everything works also connected to the 4g network (it does not go into 4g +) and wifi, but if I enter the code * # * # 4636 # * # * the phone does not recognize the SIM well (I always think of a question of IMEI)
I am desperate, I looked for something on the net to repair the phone's IMEI but not being very expert, I did not succeed.
Also trying to send the phone in USB DIAG MODE but goes to FIELD with the code # * # * 717717 # * # *
I ask you helpoooo
sorry my english but i translate from google translate
if you need it I can insert photos

elpikkio said:
Hi everyone, thanks in advance for anyone who will help me solve my A2 problem.
1. With the SIM in slot 1 It works calls and sends and receives SMS but does not connect in 4g (I think it's an IMEI problem) I also tried different APNs for my manager (Vodafone IT) but nothing
2. With the SIM in slot 2 everything works also connected to the 4g network (it does not go into 4g +) and wifi, but if I enter the code * # * # 4636 # * # * the phone does not recognize the SIM well (I always think of a question of IMEI)
I am desperate, I looked for something on the net to repair the phone's IMEI but not being very expert, I did not succeed.
Also trying to send the phone in USB DIAG MODE but goes to FIELD with the code # * # * 717717 # * # *
I ask you helpoooo
sorry my english but i translate from google translate
if you need it I can insert photos
Click to expand...
Click to collapse
can you see the imei when you look in settings ?
if you can it is not imei problem
if you can't see restore your persist partition

KevMetal said:
can you see the imei when you look in settings ?
if you can it is not imei problem
if you can't see restore your persist partition
Click to expand...
Click to collapse
thanks for the reply then if I go to the settings-information on the phone-IMEI (SIM1 slot) and IMEI (SIM2 slot) IMEI appears to me, but if I press in the popup that appears IMEI unknown for SIM1 slot and for SIM2 slot (where there is now the SIM) IMEI and IME SV 00 appears.
Then there is a simple guide to restore persit partitions because I am not an expert in modding
thanks

elpikkio said:
thanks for the reply then if I go to the settings-information on the phone-IMEI (SIM1 slot) and IMEI (SIM2 slot) IMEI appears to me, but if I press in the popup that appears IMEI unknown for SIM1 slot and for SIM2 slot (where there is now the SIM) IMEI and IME SV 00 appears.
Then there is a simple guide to restore persit partitions because I am not an expert in modding
thanks
Click to expand...
Click to collapse
well yes sort of easy ...do you have knowledge of adb & fastboot ? then it's easy
1. download the recovery in my link
2.download persist restore.zip
3.put the recovery.img in the adb folder ( change name to recovery.img )
4. put the persist .zip on the phone internal memory
5. connect the phone to pc
6. open cmd window on pc
7. put the cmd : adb devices .. if it shows a number it is connected to phone
8. put the cmd : adb reboot bootloader
*phone will boot to fastboot
9. run command : fastboot boot recovery.img
10. now on phone twrp recovery will boot ... flash the persist zip ...
11..change slot in reboot section
**this will require a full reboot so press change slot button ...then press reboot bootloader...then on computer repeat command: fastboot boot recovery.img
12. flash persist in your inactive slot
13. change back to active slot
14. reboot
*you need to have knowledge of twrp and fastboot and your bootloader must be unlocked
_if you don't you first need to install adb&fastboot and if you haven't unlocked bootloader you must unlock it and read up on how to do that
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
https://www.dropbox.com/s/zy8prxeum9qbkx5/TWRP-3.2.3-0810-XIAOMI6X-RU-wzsx150-hypeartist.zip?dl=0

KevMetal said:
well yes sort of easy ...do you have knowledge of adb & fastboot ? then it's easy
1. download the recovery in my link
2.download persist restore.zip
3.put the recovery.img in the adb folder ( change name to recovery.img )
4. put the persist .zip on the phone internal memory
5. connect the phone to pc
6. open cmd window on pc
7. put the cmd : adb devices .. if it shows a number it is connected to phone
8. put the cmd : adb reboot bootloader
*phone will boot to fastboot
9. run command : fastboot boot recovery.img
10. now on phone twrp recovery will boot ... flash the persist zip ...
11..change slot in reboot section
**this will require a full reboot so press change slot button ...then press reboot bootloader...then on computer repeat command: fastboot boot recovery.img
12. flash persist in your inactive slot
13. change back to active slot
14. reboot
*you need to have knowledge of twrp and fastboot and your bootloader must be unlocked
_if you don't you first need to install adb&fastboot and if you haven't unlocked bootloader you must unlock it and read up on how to do that
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
https://www.dropbox.com/s/zy8prxeum9qbkx5/TWRP-3.2.3-0810-XIAOMI6X-RU-wzsx150-hypeartist.zip?dl=0
Click to expand...
Click to collapse
thanks for the guide and files that you left, but I have no knowledge of everything so I will try to recover the information you have told me and I will follow your guide step by step, hoping not to crash the phone
Thanks again
last thing how long are the links with the relative files active?
anyway mine is a mi a2 4/32 with android 10 updated in march is your guide ok?

KevMetal said:
well yes sort of easy ...do you have knowledge of adb & fastboot ? then it's easy
1. download the recovery in my link
2.download persist restore.zip
3.put the recovery.img in the adb folder ( change name to recovery.img )
4. put the persist .zip on the phone internal memory
5. connect the phone to pc
6. open cmd window on pc
7. put the cmd : adb devices .. if it shows a number it is connected to phone
8. put the cmd : adb reboot bootloader
*phone will boot to fastboot
9. run command : fastboot boot recovery.img
10. now on phone twrp recovery will boot ... flash the persist zip ...
11..change slot in reboot section
**this will require a full reboot so press change slot button ...then press reboot bootloader...then on computer repeat command: fastboot boot recovery.img
12. flash persist in your inactive slot
13. change back to active slot
14. reboot
*you need to have knowledge of twrp and fastboot and your bootloader must be unlocked
_if you don't you first need to install adb&fastboot and if you haven't unlocked bootloader you must unlock it and read up on how to do that
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
https://www.dropbox.com/s/zy8prxeum9qbkx5/TWRP-3.2.3-0810-XIAOMI6X-RU-wzsx150-hypeartist.zip?dl=0
Click to expand...
Click to collapse
procedure performed the SIM is recognized but does not connect to the 4g data network even if the wording 4g is at the top

elpikkio said:
procedure performed the SIM is recognized but does not connect to the 4g data network even if the wording 4g is at the top
Click to expand...
Click to collapse
that is fine ... now in the settings of the sim program the correct apn for your cellphone provider ...you can the info on the internet

I have a similar problem, and I am find the solution with two sim cards. Tried to put two cards, because you must choose preferred one for data. After that everything will work (at least it was for me).