Related
Hello everyone!
I have a galaxy s i9000b with 8gb.
was using the Christian rom a gingerbread 2.3.3.
of a sudden he started to restart on lopping and ended up entering the system after some time. until it stopped booting the system permanently.
this is a recurring problem found much information on google about it!
solves the problem most easily by using the stock rom tim.
in my case.
after much research I learned to use the adb basically and was following a tutorial
parted on then it should go to the directory / dev / block and find mmcblk0.
but he was not there!
I tried to copy the etc / fstab file to a folder on your pc so I can read and see if mmcblk0 was listed there.
I used the command:
C: \ android-sdk-windows \ platform-tools> adb push / etc / fstab c :/
and I returned this:
can not stat '/ etc / fstab': No such file or directory
though I see him there in the adb shell browsing the folder / etc
finally began to get discouraged with the problem and for not having found the mmcblk0 there in / dev / block.
I'm beginning to think that with the 8GB internal memory of my beloved GS I9000B actually damaged.
Can someone help me confirm this or help me somehow?
just pointing out that the system does not start, but I have access to recovery mode and download
I'm using the recovery is the CMW RECOVERY v2.5.1.0 SPEEDMOD ULFK
to have access to the cell by adb!
sorry for bad english!
re:
Very sorry to hear this . You can try to find some solutions in this thread:
http://forum.xda-developers.com/showthread.php?t=845708
There are some more topics here on xda, try anything, before a year, i had one i9000 int dead, and there is no solution , hope your problem can be solved.
At the end if nothing helps, now we have some sort of fix, and this can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=973687&page=3
look at Catanni post, this must work if anything else fail. This is vold file needed for this.
Good luck.
hey! tanks man!
thanks for the reply! I'll read all these topics and then I see that fstab!
then write here what happened!
Thank you so!
bispoom said:
I tried to copy the etc / fstab file to a folder on your pc so I can read and see if mmcblk0 was listed there.
I used the command:
C: \ android-sdk-windows \ platform-tools> adb push / etc / fstab c :/
and I returned this:
can not stat '/ etc / fstab': No such file or directory
Click to expand...
Click to collapse
your command that you used above is incorrect.
To transfer from phone to computer use "pull"
To transfer from computer to phone use "push"
re: read this please
It is very important, before u start flashing and work with abd, to do backup your /efs folder if u dont have already. If your phone really have dead internal sd then is almost impossible to recover your imei if /efs folder become corrupted. This is covered by this thread:
http://forum.xda-developers.com/showthread.php?t=859914
After that you can try to flash some older firmwares, try with repartition, try to manually set up partitions, and u have full procedure in first link on my previous post.
You can try this command from adb:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
this command will mount your internal sd in windows, and then u can try to partition in windows
In second link, is procedure how to change internal and external sd, this is last that u can try (that mean that your internal sd is really dead). Attached fold.fstab will make your external sd to work like internal (this is not tested by myself, but a lot of people have succsess with this).
Bye and good luck, and please tell us how progress work.
hi!
result of command:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
is here
cannot create /sys/devices/platform/s3c-usbgadget/gadget/lun1/file: directory no
nexistent
to access the folder dev / block there is no a mmcblk0
and not one or the other as mmcblk0p1 or p2
and inside the folder / sys/devices/platform/s3c-usbgadget/gadget / folder does not exist lun1 / ...
sorry for bad English, and tanks for the help
re:
If mmcblk do not exist, best u can do is to try to flash with repartition in odin. If this does not help, always can try this
http://forum.xda-developers.com/show...=973687&page=3
Wish u best
broken link
hi!
man tanks for the help but this link
http://forum.xda-developers.com/show...=973687&page=3
is broken!!!
hi guys i am looking here for thread that will give tutorial on how are we going to back up the said EFS which is the very important file of the phone where IMEI resides, suddenly after searching for so many days still haven't found an answer. I already tried using EFS Pro 1.9.2 and it prompts that the said directory isn't there.. i checked it out on the root of my phone and found that EFS folder isn't there.. now my question is there any apps or tool that will backup our efs so that if incase we accidentally mess with our phone, it will be easy for us to revert back to the time when the phone is functioning well..
The EFS Partition is "stl5" .
So , for mounting the partition at boot , You need to unpack your boot.img, Open init.rc and add the following lines:
mkdir /efs
mount /dev/block/stl5 /efs
Click to expand...
Click to collapse
Then You have to repack the boot.img
----------------------------------------------------------------------------------------
We are done with the mounting part. |
----------------------------------------------------------------------------------------
Now , Flash the boot.img
Reboot Your phone
Connect it to your PC (Note : ADB must be enabled)
Run adb pull /efs command
................................
There might be a way using the "*#7284#" code . It creates a service com port on PC. (Stock Roms Only)
dev0xteam said:
The EFS Partition is "stl5" .
So , for mounting the partition at boot , You need to unpack your boot.img, Open init.rc and add the following lines:
Then You have to repack the boot.img
----------------------------------------------------------------------------------------
We are done with the mounting part. |
----------------------------------------------------------------------------------------
Now , Flash the boot.img
Reboot Your phone
Connect it to your PC (Note : ADB must be enabled)
Run adb pull /efs command
................................
There might be a way using the "*#7284#" code . It creates a service com port on PC. (Stock Roms Only)
Click to expand...
Click to collapse
hitted thanks...
this is a nice tutorial, but it will be very best if u can provide the complete step by step on how am i going to do this, and where to input the said line..sori for asking too much..just a noob one..hehe dont know much bout adb shell and commads not an advance user too..hehe
mizukage said:
hitted thanks...
this is a nice tutorial, but it will be very best if u can provide the complete step by step on how am i going to do this, and where to input the said line..sori for asking too much..just a noob one..hehe dont know much bout adb shell and commads not an advance user too..hehe
Click to expand...
Click to collapse
DON'T MOUNT EFS PARTITION!
You will most likely brick your phone.
Sent from my GT-S5830 using Tapatalk 2
(Frank) said:
DON'T MOUNT EFS PARTITION!
You will most likely brick your phone.
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
do u have any better idea on how are we going to save our efs partition so that we can revert back if we messed with our phone?flashing is risky especially for noobs..
Hi all first sorry for my bad english, i hope can convey me porpuse
I caught of friend an i9305 for recovery baseband and imei
I havent any backup of imei or nv_data and my baseband and imei is null ver.4.1.2
When use *#1234# it shows this detail
AP:I9305XXBMD5 ,CP:UNKNOWN ,CSC:I9305DBTBME1
I did this relation that consist:
Root by cf, install busybox 1.20.2 ,intall rom toolbox lite flash by param file in forum but it not effect, than via efs professional and terminal and multiple software get efs.img. after delete efs folder by rom toolbox. when i restore this img file, all method become done.
After reboot phone my problem is whitout changeable.
I think my efs folder is failure.
So finally i have to used QPST for get nv data, all driver is mounted of phone but this softwear not detect my phone and shows no phone i test it by several pc and all like message.
Via nv tool give too error phone connection has been lost! and no answer from phone.
In the situation please help me to solve this issue.
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
Hello,
I have posted on various threads that i can fix DRK (Device root key), but after large demand in PM for the fix i have decided to make a tutorial, since i don't have much time to help everyone, this tutorial is only tested on SM-N910C, could work on other variants of Exynos, perhaps snapdragon but NOT TESTED!!!!
So how is DRK broken? Usually when you flash roms and stuff you should have EFS backup as its most important thing while rooting samsung phones, but some people just dont do that, other people use boxes like z3x for unlocking and they wipe EFS, while unlocking phones the process sometimes changes IMEI number and leaves device root key wiped. These modifications sometimes make it hard to revert back to stock and i personally had problems with device suddenly rebooting etc... with this tutorial we will try to mitigate these problems.
PLEASE DO NOT PROCEED WITHOUT SHELL/ADB KNOWLEDGE IF YOU MESS SOMETHING UP YOU WILL LOOSE IMEI AND WILL HAVE A BRICK! You have been warned and i am not to be held liable!
First we need to make backup of your EFS, we will use TAR and shell which is most reliable way (Partition Backup is good too), with adb shell:
1. su
2. cd /efs
3. tar czf efsbackup.tgz *
4. mv efsbackup.tgz /data/media/0/
Now go to your internal memory in My Computer and there should be file called efsbackup.tgz copy it somewhere safe on your PC. This is your efs backup!
Now we need to take two files which we will reuse latter, you can extract them from efsbackup.tgz but this is easyer:
1. su
2. cd /efs
3. cp nv_data.bin /data/media/0/
4. cp nv_data.bin.md5 /data/media/0/
Now go to your internal memory and copy nv_data.bin and nv_data.bin.m5 to your desktop, we will need these files later. These files contain your imei!
Now we need to reboot to TWRP and format EFS partition via terminal (We are doing this to force radio to recreate the files we lost while flashing and make system more stable, no reboots etc..)
TWRP --> Advanced --> Terminal type these (These will also fix "Failed to mount /efs (Invalid Argument)) Don't missspell, if you get error no mount in fstab, that is ok!
1. mke2fs /dev/block/mmcblk0p3
2. mount -w -t ext4 /dev/block/mmcblk0p3
3. reboot
Now the system will be booting, once done when you dial *#06# you will see generic IMEI and it's not yours, don't freakout this is how its supposed to be. Radio also recovered your default values in FactoryApp folder which is nice. Now reboot phone twice!
Let's restore nv_data and restore imei, assuming you still have those files in your internal memory do this with ADB:
1. su
2. cd /efs
2. rm -rf /efs/nv_data.bin
3. rm -rf /efs/nv_data.bin.md5
4. mv /data/media/0/nv_data.bin* /efs/
5. chmod 700 /efs/nv_data.bin*
6. chown radio:radio nv_data.bin*
7. reboot
After phone reboots your factory IMEI is back and registering to network properly, now we have achieved stable device no random reboots and clean remade factory EFS!!!
DRK REPAIR PART!
Now lets go to the part of fixing DRK Device Root Key and dm-verity error! I have attached file called prov_data.zip, extract the prov_data folder to your internal memory (This is not a flashabe zip) And run these commands with your ADB Shell:
1. su
2. cd /efs
3. mv /data/media/0/prov_data /efs/
4. chmod -R 755 /efs/prov_data
5. chown -R root:root /efs/prov_data
Device root key is now present in your device but not yet active/validated, in order to validate this, you need to flash your factory firmware with ODIN, go to factory recovery and wipe data/factory reset, and dm-verity error is now gone!
SERIAL NUMBER FIX PART
I have attached file called serial_no.zip (Not a flashable zip file), extract the file from it called serial_no open it with notepad or whatever text editor you use and replace XXXXXXXXXXX with your own serial number that is written behind your phone. Now copy serial_no file to your internal memory again and with adb we do this:
1. su
2. cd /efs
3. mv /data/media/0/serial_no /efs/FactoryApp/
4. chmod 700 /efs/FactoryApp/serial_no
Reboot and done, you have your serial number back *#06#!
FACTORY CSC FIX PART
Download the file called csc_repair.zip, inside you will see the file called mps_code.dat, open it with notepad or whatever text editor you use, type in your factory CSC instead of XXX in my file and save. If you cant find your factory CSC, go to Kies or SmartSwitch, initialize firmware, type in your serial number and device model it will show your factory CSC for reinstall, this is your CSC. Now copy mps_code.dat file to your internal memory and again we run ADB Shell:
1. su
2. cd /efs
3. mv /data/media/0/mps_code.dat /efs/imei/
4. chown root:root /efs/imei/mps_code.dat
5. chmod 755 /efs/imei/mps_code.dat
This is it, if you can follow these steps you can get clean factory remade EFS partition, with your own IMEI, Serial Number, CSC Code, DRK/dm-verity fixed. Flashing factory ODIN firmware after this will make your phone work as it should!
i have this issue on the n910t... I have full access and a working phone but it lags a lot... youtube videos stutter and when typing some words they keyboard, well all keyboards stutter too... this began to happen when my phone started showing me this message, you see the phone was unlocked by certfile with octoplus or z3x... then it lost signal but when i tried to wipe efs, the phone recovered its own imei and serial... So i unlocked it normally with z3x but had to downgrade the modem from EPE3 to DOK2 to unlock it.... then i restored the complete firmware to the latest version of android 6.0.1 and it showed me the DRK problem..
I'm going to try this tutorial and see it this stops all the stuttering every 8 seconds,..
SeerePetrova said:
i have this issue on the n910t... I have full access and a working phone but it lags a lot... youtube videos stutter and when typing some words they keyboard, well all keyboards stutter too... this began to happen when my phone started showing me this message, you see the phone was unlocked by certfile with octoplus or z3x... then it lost signal but when i tried to wipe efs, the phone recovered its own imei and serial... So i unlocked it normally with z3x but had to downgrade the modem from EPE3 to DOK2 to unlock it.... then i restored the complete firmware to the latest version of android 6.0.1 and it showed me the DRK problem..
I'm going to try this tutorial and see it this stops all the stuttering every 8 seconds,..
Click to expand...
Click to collapse
I am not sure if it will work on N910T variant, but you can try it. DRK error happened on your note because z3x wipes EFS and then writes new nv_data.bin, but by wiping it destroys your prov_data/dev_root folder which contains DRK. If you think your EFS partition created your problem, you can start from the start and format EFS to make it factory and then proceed.
Hey there!
I recently bought a used Note 4 910C. I was told by the shopkeeper that it has never been tempered with. But OTA update fails bcuz of DRK error. I guess someone did try something with it previously. I manged to update Marshmallow via ODIN.
yesterday I rooted it and followed your DRK REPAIR Part. flashed via ODIN for validation but the error still exists. I did not do the whole method from the beginning ( I backed up EFS and nv_bin). Plz tell me what did I do wrong.
Another thing that may be of some importance. The serial no was different form phone's back in just one letter in the middle. Instead of '5' it was showing 'S'. I wonder it can not be by mistake. there must be some messing up previously.
Anyway I followed ur method of SERIAL NO repair and managed to repair the serial no. The IMEI was already a match.
Plz help me what should I do for DRK repair.
Regards.
Usually when you restore prov_data folder properly, you need to go to twrp, format system, data and cache. Then with odin flash stock firmware with your own csc code (do csc repair if its not a match). After that phone should boot to stock recovery, then do format data/factory reset from stock recovery. It should say something like "verifiyng dm-verity" when you go to reboot. After system boots when you go to recovery again it wont show drk error anymore. Tested 100% on 910c variant.
magix01 said:
Usually when you restore prov_data folder properly, you need to go to twrp, format system, data and cache. Then with odin flash stock firmware with your own csc code (do csc repair if its not a match). After that phone should boot to stock recovery, then do format data/factory reset from stock recovery. It should say something like "verifiyng dm-verity" when you go to reboot. After system boots when you go to recovery again it wont show drk error anymore. Tested 100% on 910c variant.
Click to expand...
Click to collapse
So I'm doing the drk fix on my smg925p device and when doing the drk commands the prov_data folder doesn't move to the efs folder it stays in my internal memory and i did the restore and reset and i still get the drk error clearly a command or something is wrong
Use root explorer to move the folder then
magix01 said:
This is it, if you can follow these steps you can get clean factory remade EFS partition, with your own IMEI, Serial Number, CSC Code, DRK/dm-verity fixed. Flashing factory ODIN firmware after this will make your phone work as it should!
Click to expand...
Click to collapse
1. su
2. cd /efs
3. tar czf efsbackup.tgz *
4. mv efsbackup.tgz /data/media/0/
Testing........I was able to make a backup of efsbackup.tgz on a phone without any dm-verity damage. So the command works.
But on the phone that needs efs repair, when I run the command tar czf efsbackup.tgz * with Terminal Emulator
I get the error message tar: efsbackup.tgz: file is the archive; skipping
Any thoughts anyone?
Try with busybox installed and system root not systemless.
magix01 said:
Try with busybox installed and system root not systemless.
Click to expand...
Click to collapse
Thanks, that worked. The phone I'm working on is a SM-N910V and it does not have the files nv_data.bin or nv_data.bin.md5 inside the efs folder, any suggestions?
Can I send you my efs folder for repair?
I have two SM-N910V one is Okay. could I pull some files from the good one to help fix the damaged one?
+1 N910F have dont the nv_data's...my efs it's okay, i only wanna look
magix01 said:
Try with busybox installed and system root not systemless.
Click to expand...
Click to collapse
SM-N910V I decided to give this a try.
I used Root Browser to change the name of every file and folder inside the efs folder. I just added a 1 to the end of the names so I could revert back if needed.
I rebooted the phone, went back to check the efs folder and it had regenerated everything I needed to keep. And it didn't load the junk files. The phone runs like it's using AdAway on steroids.
What do you think about that. Why did it work.
http://forum.xda-developers.com/note-4-verizon/general/spyware-fix-fixed-lag-wi-fi-problems-t3433839
HI im having trouble doing the third command in DRK repair . it say that it cant be moved becuase the directory is not empty what should i do ?
I can confirm that it doesn't work with the Samsung Galaxy S6 Edge Sprint Model (SM-G925P)
bro i use your method to recover sn number and i get my serial number back but when i reboot its gone null again what can i do bro
Thank you! I use this method to restore the serial number and fix DRK on the phone Samsung SM-A310F Galaxy A3 (2016)
This method is full working on sm-n910g but still dm verification failed messages
Efs restore and phone working well
So thank u magix01
is it possible to use your files on my note edge n915fy ??
i have done everything but i can get back original emei. DRK everthing seem ok.serial number said no when i dial *#06# but i can see it on settings -status...
my phone can no register nto network
..please help.
doctor-cool said:
Thanks, that worked. The phone I'm working on is a SM-N910V and it does not have the files nv_data.bin or nv_data.bin.md5 inside the efs folder, any suggestions?
Can I send you my efs folder for repair?
I have two SM-N910V one is Okay. could I pull some files from the good one to help fix the damaged one?
Click to expand...
Click to collapse
Did you get any fix? I'm also missing these files in my N910T.