Related
Hello,
I upgraded my 9020T from 2.3.6 to 4.0.3, as you all. I tried with the upgrade, with the full version,and with the new CM9 kang based on 4.0.3. I tried to keeping my existing apps, and to clen install.
In all scenarios, the result is the same : My efs folder (IMEI storage...) disappears after a reboot.
Never had this problem on 2.3.6.
I have kept the new bootloader and the new radio, I am back to 2.3.6 and it works, so it is coming from something in the rom itself.
Hopefully, I have an EFS backup .
Anyone else with this bug ? What should I try ?
Thanks.
daniel3ric said:
Hello,
I upgraded my 9020T from 2.3.6 to 4.0.3, as you all. I tried with the upgrade, with the full version,and with the new CM9 kang based on 4.0.3. I tried to keeping my existing apps, and to clen install.
In all scenarios, the result is the same : My efs folder (IMEI storage...) disappears after a reboot.
Never had this problem on 2.3.6.
I have kept the new bootloader and the new radio, I am back to 2.3.6 and it works, so it is coming from something in the rom itself.
Hopefully, I have an EFS backup .
Anyone else with this bug ? What should I try ?
Thanks.
Click to expand...
Click to collapse
same here I can't straighten out this problem.
Try flashing into something more stable and then restore your efs.
Sent from my Ice cream Nexus S sandwich
aic719 said:
Try flashing into something more stable and then restore your efs.
Sent from my Ice cream Nexus S sandwich
Click to expand...
Click to collapse
Btw questions like these should really be in the Q&A section. Unless you'll are looking for a ban.
Sent from my Ice cream Nexus S sandwich
aic719 said:
Btw questions like these should really be in the Q&A section. Unless you'll are looking for a ban.
Click to expand...
Click to collapse
Btw looks like I am more looking for help.
aic719 said:
Try flashing into something more stable and then restore your efs.
Click to expand...
Click to collapse
I went back to 2.3.6.
Btw what do you mean by more stable than an official update ?
Something weird is happening with my efs too. A few weeks ago my phone started to intermittently not connect calls out of the blue (i.e. hadn't just flashed a new rom). I installed the 2.3.6 update followed by the incremental ICS build on Sunday and it stopped being able to make calls altogether.
Last night I realised this was an efs problem and managed to restore it from a backup. I then installed the full ICS OTA and could still make calls. This morning the problem has returned and *#06# confirms that my IMEI is missing again.
Either this ROM is overwritting my EFS afters being flashed (e.g. on reboot) or the portion of internal storage for efs is corrupting.
Will try restoring the efs backup tonight whilst sticking with the ICS rom and will report back.
Solved!
[TOOL][Multi-Platform] EFS Backup & Restore
This restoring caused problem on ICS. Some files' permission do not meet the originals. There's no trouble on GB.
Original permission
770 /efs/bluetooth
770 /efs/imei
700 /efs/lost+found
700 /efs/.nv_data.bak
700 /efs/.nv_data.bak.md5
600 /efs/.nv_state
600 /efs/nv.log
700 /efs/nv_data.bin
700 /efs/nv_data.bin.md5
666 /efs/bluetooth/bt_addr
666 /efs/imei/.nvmac.info
600 /efs/imei/bt.txt
So I deleted /efs/, copy and paste the backuped /efs/ and put permissions samely with original and rebooted the device but IMEI was not restored.
At this point, I did Recover your IMEI in 9 steps
Solved!!
phone_user said:
Solved!
[TOOL][Multi-Platform] EFS Backup & Restore
This restoring caused problem on ICS. Some files' permission do not meet the originals. There's no trouble on GB.
Original permission
770 /efs/bluetooth
770 /efs/imei
700 /efs/lost+found
700 /efs/.nv_data.bak
700 /efs/.nv_data.bak.md5
600 /efs/.nv_state
600 /efs/nv.log
700 /efs/nv_data.bin
700 /efs/nv_data.bin.md5
666 /efs/bluetooth/bt_addr
666 /efs/imei/.nvmac.info
600 /efs/imei/bt.txt
So I deleted /efs/, copy and paste the backuped /efs/ and put permissions samely with original and rebooted the device but IMEI was not restored.
At this point, I did Recover your IMEI in 9 steps
Solved!!
Click to expand...
Click to collapse
Thanks for the link
Any help guys? I'm facing the same prob. Tried many stuff n nothing has worked.. Now I'm back to GB 2.3.3 n no luck..
phone_user said:
Solved!
[TOOL][Multi-Platform] EFS Backup & Restore
This restoring caused problem on ICS. Some files' permission do not meet the originals. There's no trouble on GB.
Original permission
770 /efs/bluetooth
770 /efs/imei
700 /efs/lost+found
700 /efs/.nv_data.bak
700 /efs/.nv_data.bak.md5
600 /efs/.nv_state
600 /efs/nv.log
700 /efs/nv_data.bin
700 /efs/nv_data.bin.md5
666 /efs/bluetooth/bt_addr
666 /efs/imei/.nvmac.info
600 /efs/imei/bt.txt
So I deleted /efs/, copy and paste the backuped /efs/ and put permissions samely with original and rebooted the device but IMEI was not restored.
At this point, I did Recover your IMEI in 9 steps
Solved!!
Click to expand...
Click to collapse
Great, I've passed this on to window7 who might be able to add it to his radio post.
arite. I finally found this thread becuase I'm having IMEI issues on reboot. What's the best way to reset the permissions of all those files? (linux newb here)
I do have a backup of my /efs/ folder on my SD card.
I'd like to fix my phone.
dmo580 said:
arite. I finally found this thread becuase I'm having IMEI issues on reboot. What's the best way to reset the permissions of all those files? (linux newb here)
I do have a backup of my /efs/ folder on my SD card.
I'd like to fix my phone.
Click to expand...
Click to collapse
Backup must be done before the phone corrupted. Did you?
Sent from my Nexus S using XDA App
android_nexus said:
Backup must be done before the phone corrupted. Did you?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes. my backup was done months and months ago. it works fine for GB but apparently ICS has permission problems so I keep corrupting IMEI every reboot.
dmo580 said:
yes. my backup was done months and months ago. it works fine for GB but apparently ICS has permission problems so I keep corrupting IMEI every reboot.
Click to expand...
Click to collapse
Yeap, that'll be OK! Good Luck dude
Sent from my Nexus S using XDA App
Having the same problem. Upgrading to ICS kills my emei number and reverts to the default 00049.
In GB restoring the emei works fine.
In ICS restoring emei works as well, but after a reboot, it reverts back to 00049.
Very annoying
Luckely everything seems to work fine with the default emei, but i dont like it one bit
After spending days and nights with a fried EFS (IMEI null / null), which in no way can be restored - no receipt, no box, no more sticker under battery. I've read a lot of people got their motherboards replaced by service centers.
Where can I get these?
Service center is a no-go in my case, they said they can't help.
Edit: "GH82-07651A" is the official product number for one of the N9005 board types, maybe this one is for the 16GB version tho not sure
Soo Star said:
After spending days and nights with a fried EFS (IMEI null / null), which in no way can be restored - no receipt, no box, no more sticker under battery. I've read a lot of people got their motherboards replaced by service centers.
I take it as a new motherboard means you get a new IMEI?
If so, where can I get these?
Service center is a no-go in my case, they said they can't help.
EDIT: Okay.. searching for its spare part number is easier.. the thing is called "GH82-07651A"
EDIT2: GH82-07651A is the 16GB model I think
Click to expand...
Click to collapse
Yeah a new motherboard will contain a new IMEI. - How did you fry your EFS? - you know it can actually be saved with some ADB trickery (quite a few have done so)
radicalisto said:
Yeah a new motherboard will contain a new IMEI. - How did you fry your EFS? - you know it can actually be saved with some ADB trickery (quite a few have done so)
Click to expand...
Click to collapse
I've been trying day and night to restore it by flashing hundreds of stock roms - of no avail.
Well the IMEI most likely got formatted away by odin by the previous seller - though if I could restore it I could file a proper lawsuit against the vendor, cause it's obviously stolen (no sticker etc).
Which "ADB trickery" method did you refer to? Cause every method I've found so far requires the IMEI to be reentered from a sticker / receipt or whatever
Soo Star said:
I've been trying day and night to restore it by flashing hundreds of stock roms - of no avail.
Well the IMEI most likely got formatted away by odin by the previous seller - though if I could restore it I could file a proper lawsuit against the vendor, cause it's obviously stolen (no sticker etc).
Which "ADB trickery" method did you refer to? Cause every method I've found so far requires the IMEI to be reentered from a sticker / receipt or whatever
Click to expand...
Click to collapse
Ahh, I (assumed) thought you had the original IMEI somewhere, in regards to the ADB I mentioned, there is a thread by Marek on how to restore IMEI and Serial number - The EFS partition btw doesn't actually ever vanish. The Note 3 has the ability to rebuild the EFS by itself using the correct scripts and commands. So all hope isn't lost tbh :good:
EDIT: Have you tried the Fire script?
---------- Post added at 12:31 PM ---------- Previous post was at 12:28 PM ----------
As if by magic here is the link
radicalisto said:
Ahh, I (assumed) thought you had the original IMEI somewhere, in regards to the ADB I mentioned, there is a thread by Marek on how to restore IMEI and Serial number - The EFS partition btw doesn't actually ever vanish. The Note 3 has the ability to rebuild the EFS by itself using the correct scripts and commands. So all hope isn't lost tbh :good:
EDIT: Have you tried the Fire script?
---------- Post added at 12:31 PM ---------- Previous post was at 12:28 PM ----------
As if by magic here is the link
Click to expand...
Click to collapse
Actually I've given it another shot with the EFS Pro tool & Qualcomm NV Tools though somehow I can't get the QC tools to connect properly causing the tool to crash... I'd say it's because there is no IMEI (or null/null, where it should be), if I knew better.
fire's script didn't restore the missing IMEI ever tho ..guess I'm really fubar'd
EDIT:
radicalisto said:
The EFS partition btw doesn't actually ever vanish.
Click to expand...
Click to collapse
apparently partition is just perfectly fine up to the contents of the /efs/imei (nv files missing). I've seen things like people recreating the imei from their meid?
But whenever I read oft it, it proven not to work in the later posts of the threads lol -_- (why I tried QC again)
EDIT 2: "I'd say it's because there is no IMEI (or null/null, where it should be), if I knew better."
It might have something to do with EFS Professional switching the USB settings from "MTP + ADB" to "DIAG + Modem + ADB" when starting up NV Tools. (Since I get "Mobile Network not available" after dialing *#7284#) ..it's probably connected to the "Baseband unknown" thing.. idk
Google SuperIMEI, I think it's your only hope here.
The first
Efs partition not contain imei number on qualcomm device!
It is stored on mmcblk0p 12 and mmcblk0p 13 if you try use the script from the beginning of my threat if it not work... Just find someone with proper box to repair it.
mirek190 said:
The first
Efs partition not contain imei number on qualcomm device!
It is stored on mmcblk0p 12 and mmcblk0p 13 if you try use the script from the beginning of my threat if it not work... Just find someone with proper box to repair it.
Click to expand...
Click to collapse
Still can't post in your thread lol
I did run through the process as described in Soft bricked [ SOLVED ] again. With the sole difference that I had to use a different CWM (6.0.4.7) from
[RECOVERY]CWM Based Recovery 6.0.4.7 for N900 N9005 N900T N900S because it wouldn't work with "n9005-cwm-recovery-6.0.4.4(1025)" - I've read it's a KK bootloader issue.
So I ran all the 23
Code:
dd if=/external_sd/mmcblk0xxx of=/dev/block/mmcblk0xxx
as
Code:
dd if=/storage/extSdCard/mmcblk0xxx of=/dev/block/mmcblk0xxx
and can't start the phone anymore at all. It bootloops right after the "Samsung GALAXY Note 3 SM-N9005" write. (doesn't go to the pulsating logo).
I doubt it's cause the CWM I've used has another mount point for the ext SD ;;
Sure an octopus or something might help, but it will be hard to find someone in Switzerland lol.
EDIT: After that, I'm flashing the latest stock KK it boots again, but the IMEI remains null/null, as well as Baseband unknown
From my post just push mmcblk0p11 but you need root and adb on PC and busy box on android.
ㅠㅡㅠ
mirek190 said:
From my post just push mmcblk0p11 but you need root and adb on PC and busy box on android.
Click to expand...
Click to collapse
Kay, on a clean stock ROM I put;
- CWM with recovery su,
- SuperSU-v1.99r3 app
- booted and put busybox
- set super su to perm root / default access [ grant ]
Then I adb to the device and found it suddenly refusing root access.
So I upped to file to sd card, use terminal emu and dd mmcblk0p11...
that's right so far?
rebooted and still
View attachment 2785241
Hello to all you developers out there.
For quit some while now is recieve a consistent warning pop-up whenever i reboot my phone. It only occourse when i'v installed a TW rom. When i'm running any other rom like a GPE for example, the warning does not appear.
Currently i'm on Goldeneye 49.2. My phone is a GT-I9505 on baseband-version: I9505XXUGNK4
I'm not a developer, but a true flashjunky. I would not now how many times is flashed one of your roms and so i do not now specific when this problem started. I'v spend much time browsing the internet in search of this problem and how to fix it. But my effords where not succesfull. The only thing i might have picked up about it, is that is could be related to a corrupt EFS. I hope some of you out there can give me a headsup about this.
Plus! I want to thank all you devoted developers out there. Your hard work and effords are much apreciated.
I have made a picture of the warning.
Thank you for taking your time reading this and i hope someone knows how to fix this.
Greatings,
Peter
From the Netherlands
peterd689 said:
Hello to all you developers out there.
For quit some while now is recieve a consistent warning pop-up whenever i reboot my phone. It only occourse when i'v installed a TW rom. When i'm running any other rom like a GPE for example, the warning does not appear.
Currently i'm on Goldeneye 49.2. My phone is a GT-I9505 on baseband-version: I9505XXUGNK4
I'm not a developer, but a true flashjunky. I would not now how many times is flashed one of your roms and so i do not now specific when this problem started. I'v spend much time browsing the internet in search of this problem and how to fix it. But my effords where not succesfull. The only thing i might have picked up about it, is that is could be related to a corrupt EFS. I hope some of you out there can give me a headsup about this.
Plus! I want to thank all you devoted developers out there. Your hard work and effords are much apreciated.
I have made a picture of the warning.
Thank you for taking your time reading this and i hope someone knows how to fix this.
Greatings,
Peter
From the Netherlands
Click to expand...
Click to collapse
Hi mate,
Indeed it could be related to an EFS problem......It would help us to help you if you tell us what you tried so far to fix it
MAX 404 said:
Hi mate,
Indeed it could be related to an EFS problem......It would help us to help you if you tell us what you tried so far to fix it
Click to expand...
Click to collapse
Hi There,
Thanks for your quick reply. As soon as i read about the EFS, i also read about the backup of the EFS. But i didn't have on.
I made a backup and tried to restore. But i gues a corruption would also be backuped. I also tried to manualy adjust the EFS. Neither workt. Following that i tried holding down the power button for more then 10 seconds till it rebooted (read that somewere between de lines). I also tried various other roms, kernels and basebands. I full despiration i tried returning to fully stock rom. Nothing worked.
Now it has been about a month and a half i left this issieu. So ik can not be very specific about mij tries to resolve.
Is this in any way helpfull?
that is one of the saddest thing that will happen to your phone. My sister has s2 and s3 and she was a flashaholic with different roms and now both phones have no signal/baseband unknown.. She never back up her efs so she cant fix it. I tried my very best to search for an answer, i saw some but it never solve it anyways. Im using my s4 and i backed up my efs every flash that i do. Try to flash official rom, latest modem and pray that it will fix it.
peterd689 said:
Hi There,
Thanks for your quick reply. As soon as i read about the EFS, i also read about the backup of the EFS. But i didn't have on.
I made a backup and tried to restore. But i gues a corruption would also be backuped. I also tried to manualy adjust the EFS. Neither workt. Following that i tried holding down the power button for more then 10 seconds till it rebooted (read that somewere between de lines). I also tried various other roms, kernels and basebands. I full despiration i tried returning to fully stock rom. Nothing worked.
Now it has been about a month and a half i left this issieu. So ik can not be very specific about mij tries to resolve.
Is this in any way helpfull?
Click to expand...
Click to collapse
Hi
Well let me tell you about a few things you can try , with some luck they may be enough if not you may have to take it to a local repair shop with a Z3X box of similar they may be able to rebuilt the EFS folder
Check if the EFS folder is mounted correctly
Install / use Terminal Emulator
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
mke2fs /dev/block/mmcblk0p10
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
Reboot
With a root explorer go to EFS/factoryApp/factorymode and open it if it says off change it to on
In case none of the above worked check this great thread about EFS and Factory Mode for further help…..
http://forum.xda-developers.com/showthread.php?t=2392632
If those points do not work and without an working EFS backup you may have to look for professional help ( with a Z3X box or similar )
MAX 404 said:
Hi
Well let me tell you about a few things you can try , with some luck they may be enough if not you may have to take it to a local repair shop with a Z3X box of similar they may be able to rebuilt the EFS folder
Check if the EFS folder is mounted correctly
Install / use Terminal Emulator
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
mke2fs /dev/block/mmcblk0p10
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
Reboot
With a root explorer go to EFS/factoryApp/factorymode and open it if it says off change it to on
In case none of the above worked check this great thread about EFS and Factory Mode for further help…..
http://forum.xda-developers.com/showthread.php?t=2392632
If those points do not work and without an working EFS backup you may have to look for professional help ( with a Z3X box or similar )
Click to expand...
Click to collapse
Thank you very much for your help. I did tried to fix the EFS with the guides in the site you mentioned repeatedly. But none were succesfull. The strings you mention in your post, do not look formiliar and i tried them just now. After the second string i get the following in the Emulator:
" can't format mounted filesystem"
Could this be the issieu? Both de FactoryApp and Keystr are on ' ON ' when i open them in a rootexplorer.
And i'm starting to think this problem will, despite all your help, not be resolved.
@MAX 404 try to go to the nearest cellphone repair shop they have this cable that can fix that issue. Its around 4-5$ depends on your country.
shthppns said:
that is one of the saddest thing that will happen to your phone. My sister has s2 and s3 and she was a flashaholic with different roms and now both phones have no signal/baseband unknown.. She never back up her efs so she cant fix it. I tried my very best to search for an answer, i saw some but it never solve it anyways. Im using my s4 and i backed up my efs every flash that i do. Try to flash official rom, latest modem and pray that it will fix it.
Click to expand...
Click to collapse
I did a full restore to official rom, but did not do the trick. This problem is a real pain in the ...
Maybe in a little while, when i can get the Note 4, i need to think about controlling my flashfrenzy. My wife would certanly like that
peterd689 said:
I did a full restore to official rom, but did not do the trick. This problem is a real pain in the ...
Maybe in a little while, when i can get the Note 4, i need to think about controlling my flashfrenzy. My wife would certanly like that
Click to expand...
Click to collapse
GL peter! Going to switch with s6 edge soon though my s4 still a beast.
peterd689 said:
Thank you very much for your help. I did tried to fix the EFS with the guides in the site you mentioned repeatedly. But none were succesfull. The strings you mention in your post, do not look formiliar and i tried them just now. After the second string i get the following in the Emulator:
" can't format mounted filesystem"
Could this be the issieu? Both de FactoryApp and Keystr are on ' ON ' when i open them in a rootexplorer.
And i'm starting to think this problem will, despite all your help, not be resolved.
Click to expand...
Click to collapse
Hi
Regarding the string , Are you root at the moment , maybe that is the problem , i have not tried in while but they should work...did you check in the thread i gave you?
regarding your other point , ON is the normal , ON is not factory mode...strange but is like that..
MAX 404 said:
Hi
Regarding the string , Are you root at the moment , maybe that is the problem , i have not tried in while but they should work...did you check in the thread i gave you?
regarding your other point , ON is the normal , ON is not factory mode...strange but is like that..
Click to expand...
Click to collapse
I found a wrong reverence in the string. In your string you refer to mmcblk0p10. Except voor the S4 it's ...0p3. Found that out after you let me check the thread again. Although the factory mode is still on after inserting your three strings.
Second thing i noticed was that with the first two string, i get a repley string and info that i can't understand. With the third string, i get no reply string in the emulator. Do you think this can be part of the problem?
I also included a screenshot from the emulator.
peterd689 said:
I found a wrong reverence in the string. In your string you refer to mmcblk0p10. Except voor the S4 it's ...0p3. Found that out after you let me check the thread again. Although the factory mode is still on after inserting your three strings.
Second thing i noticed was that with the first two string, i get a repley string and info that i can't understand. With the third string, i get no reply string in the emulator. Do you think this can be part of the problem?
I also included a screenshot from the emulator.
Click to expand...
Click to collapse
Hi
Try this
http://forum.xda-developers.com/showpost.php?p=44315069&postcount=21
This guide is for those who have lost their IMEI, have corrupted EFS, or erased EFS partition. So, follow these under your own risk, it may or may not work, and if something happens or doesn't happen, then i am not to blame. So, once again i will not take credit for bricked phones or something along those lines, however i will take full credit if this works for you. I will also provide assistance to those who could not restore their EFS following this guide.
Before proceeding with this guide, backup what you have left. Use twrp to backup and in case something goes wrong and your problem escalates, you can restore using twrp backup.
Restore EFS
Change IMEI Number
Restore EFS
Do this if and only if you believe your EFS is corrupted, or you somehow erased it. If you are not sure about it, then simply follow the next guide to change you IMEI number. In most cases people loose their IMEI only and not the whole partition. Again, it may or may not work, so do this on your risk, and i am not to blame if anything bad happens, but if you do succeed, then don't forget to give me credit.
Note:
If your EFS is erased or corrupted, your IMEI and Baseband will be shown as unknown. In this case recover the EFS following this post, and then change the IMEI following the next post. If your IMEI is shown as 0, then you EFS is safe and most probably your IMEI is gone. In that case, no need to recover EFS, only change the IMEI number following my next post.
In TWRP, backup of kate wont show on kenzo and the backup up kenzo wont show on kate. In case no backup is shown even if you are using the right device, then try the dump flashing method or try changing the TWRP recovery.
Flashing this will only restore your EFS partition, but the IMEI will still be gone, so you will have to follow the next guide to change your IMEI.
Even after flashing a new EFS, you Mac and BT address will not recovery. The android system will assign a software generated address to both devices. Dont worry cause even without the EFS partition there will be a Mac and BT address assigned to your device and both the things will work normally.
If your Baseband is still unknown, even after flashing a new EFS, then try flashing latest radio file. It can be found in any firmware update package, either the official or the one from the strix.
1. Download the required files from the link given below.
EFS Backup[Kenzo] - Contact me if someone has backup of this.
EFS Backup[Kate] - Contact me if someone has backup of this.
2. Extract the Dump Backup files and flash them using the following commands.
Code:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
3. Now reboot and voila you have you a new EFS partition at your disposal.
Change IMEI Number
Requirements:
Root
USB Debugging is turn on
Windows Driver Signature is turned off
ADB and Fastboot Binary Files
Latest MiFlash Installed for the latest drivers
1. Connect your device to pc and open the adb folder. Then open a command promt window.
Code:
>> [B]Shift + Right Click[/B] anywhere in the adb folder
>> Click on [B]Open Command Window Here[/B]
2. Type the following command to enable Diagnostics mode. Allow debugging if asked.
Code:
adb shell
su
setprop sys.usb.config diag,adb
4. Download the IMEI Changer from the link given below.
IMEI Changer [Credit: Archeolot]
5. Now, open the imei changer, and enter imei number in both the fields. And click on start. After a moment it will show as passed. If it fails make sure that you have followed the points i stated.
Note: Make sure that the driver in driver management under ports is listed as "Qualcom HS-USB Android DIAG 901D" and not as "Marshall London HS-USB Android DIAG 901D". If it is listed in any other name, then go to driver management and update driver. Select browse driver, then let me pick driver from a list. Then select "Qualcom HS-USB Android DIAG 901D" and then finish.
WOW.. Thanks mate..
It's gonna very Helpful for me & other ppl.. ??
Sent from my Redmi Note 3 using Tapatalk
didn't work..
showing error as no diag even after typing those commands
kindly help me
nuk.nama said:
showing error as no diag even after typing those commands
kindly help me
Click to expand...
Click to collapse
At what part, the imei change or flashing.
The simplest, and the fastest guide to restoring EFS and IMEI! I haven't backed up my EFS and this revived my phone! Much apprecieated!
Broski32 said:
The simplest, and the fastest guide to restoring EFS and IMEI! I haven't backed up my EFS and this revived my phone! Much apprecieated!
Click to expand...
Click to collapse
Glad i could help mate. Can you confirm your mac address and bluetooth address, whether it is same or changed.
archit.bajpai.ab said:
Glad i could help mate. Can you confirm your mac address and bluetooth address, whether it is same or changed.
Click to expand...
Click to collapse
Can't confirm. My EFS partition was so corrupted from trying other tutorials to restore my IMEI that I didn't even bother backing it up because I thought that it could have been changed already (tried writing to NVRAM with QPST). Since I don't have my original mac and bluetooth addresses written down anywhere (I haven't written them down myself and I don't think they are to be found anywhere on the box or on the phone) I think the only way to check it would be to compare my current addresses on the phone to the addresses contained in your EFS backup. Can you extract them so I can check if they match or not?
Broski32 said:
Can't confirm. My EFS partition was so corrupted from trying other tutorials to restore my IMEI that I didn't even bother backing it up because I thought that it could have been changed already (tried writing to NVRAM with QPST). Since I don't have my original mac and bluetooth addresses written down anywhere (I haven't written them down myself and I don't think they are to be found anywhere on the box or on the phone) I think the only way to check it would be to compare my current addresses on the phone to the addresses contained in your EFS backup. Can you extract them so I can check if they match or not?
Click to expand...
Click to collapse
The mac address and bluetooth address in the efs are my own. I only changed the imei so that no one else can copy it, i didnt know anyway to change mac address. Besides the mac address doesnt matter that much, and i dont think that we will ever be on the same wifi network.
If you dont know then i can explain, that the mac address is required to maintain switches and broadcast in the router, so it technically does not matter.
You can change it later with some apps or use it like that if you wish, if i find any way to restore you mac i will post it too. In the mean time just post a snapshot of wifi mac and bluetooth address so that i can compare them with my own.
So, using this way, one can change the IMEI no. also?
mGforCe said:
So, using this way, one can change the IMEI no. also?
Click to expand...
Click to collapse
Yes, just use the imei changer in the rar file to change your imei. But make sure to backup or atleast note down your imei before doing so.
archit.bajpai.ab said:
The mac address and bluetooth address in the efs are my own. I only changed the imei so that no one else can copy it, i didnt know anyway to change mac address. Besides the mac address doesnt matter that much, and i dont think that we will ever be on the same wifi network.
If you dont know then i can explain, that the mac address is required to maintain switches and broadcast in the router, so it technically does not matter.
You can change it later with some apps or use it like that if you wish, if i find any way to restore you mac i will post it too. In the mean time just post a snapshot of wifi mac and bluetooth address so that i can compare them with my own.
Click to expand...
Click to collapse
Current addresses on my phone:
MAC - 00:0a:f5:a9:XX:XX
Bluetooth - 7C:7F:F0:82:XX:XX
Left out some numbers just in case they are mine. For the purpose of checking that will still be enough
Broski32 said:
Current addresses on my phone:
MAC - 00:0a:f5:a9:XX:XX
Bluetooth - 7C:7F:F0:82:XX:XX
Left out some numbers just in case they are mine. For the purpose of checking that will still be enough
Click to expand...
Click to collapse
Yup, they are not mine. Mine start with 64:cc and so on for both mac and bluetooth. They may be software generated or may be your own, technically i am not sure.
Edit: did you use imei changer to change imei no. Or are you using the default values. If you are using the default values, pls post them too. If you change them, then give your review, ie was it hard or easy, did you encointer any problem, stuff like that.
archit.bajpai.ab said:
Yup, they are not mine. Mine start with 64:cc and so on for both mac and bluetooth. They may be software generated or may be your own, technically i am not sure.
Edit: did you use imei changer to change imei no. Or are you using the default values. If you are using the default values, pls post them too. If you change them, then give your review, ie was it hard or easy, did you encointer any problem, stuff like that.
Click to expand...
Click to collapse
After flashing your EFS backup both IMEI values were set to "0". On the default values I don't think the phone would be able to register on any network with the sim inside, but I haven't tried that. Then I flashed my IMEI with the app you provided in the .rar. Set my IMEI same for both slots because I've got only one written down on the box so I think it is set how it should be out of the box. After that I've rebooted to EDL and flashed global developer rom. And it's all working, I'm able to make calls from both sim slots, however didn't try having 2 sims inside.
All in all the process is very easy, definitely the easiest out there. I haven't encountered any problems, however I think others may have a problem with drivers to get "Qualcom HS-USB Android DIAG 901D" working. Mine was working already because I tried this tutorial before. Thank you for this guide, and providing your backup
Broski32 said:
After flashing your EFS backup both IMEI values were set to "0". On the default values I don't think the phone would be able to register on any network with the sim inside, but I haven't tried that. Then I flashed my IMEI with the app you provided in the .rar. Set my IMEI same for both slots because I've got only one written down on the box so I think it is set how it should be out of the box. After that I've rebooted to EDL and flashed global developer rom. And it's all working, I'm able to make calls from both sim slots, however didn't try having 2 sims inside.
All in all the process is very easy, definitely the easiest out there. I haven't encountered any problems, however I think others may have a problem with drivers to get "Qualcom HS-USB Android DIAG 901D" working. Mine was working already because I tried this tutorial before. Thank you for this guide, and providing your backup
Click to expand...
Click to collapse
Enjoy your revived phone buddy.
Thanks buddy!!!!! you saved my phone
pandyajoe said:
Thanks buddy!!!!! you saved my phone
Click to expand...
Click to collapse
It do what i can do buddy...
Guys. I messed up my phone by restoring a nandroid backup from a different one.
I was able to restore my IMEI using some qualcomm tools. My problem now is that fingerprint scanner won't work on any rom, even official.
Any idea what else I have messed Up? I don't think restoring this efs will fix my fingerprint scanner. Is fingerprint scanner info in a different partition?
chr0m said:
Guys. I messed up my phone by restoring a nandroid backup from a different one.
I was able to restore my IMEI using some qualcomm tools. My problem now is that fingerprint scanner won't work on any rom, even official.
Any idea what else I have messed Up? I don't think restoring this efs will fix my fingerprint scanner. Is fingerprint scanner info in a different partition?
Click to expand...
Click to collapse
Have you checked with miui7 stock rom. As far as i know there are three sensor modules for fingerprint, on of them is goodfix which is currently not supported by many roms. If your is goodfix then it will not be supported too. You can flash miui rom to check whether the fingerprint works or not...
If it doesnot work, then try to resotre your nandroid backup agaian. This tym simply untick efs.
can anyone who has root access provide me with a dump of the misc partition from their H918 LGV20? I flashed a ROM that apparently included the misc.bin from the KDZ and now mine is wiped. HELP! the command to use would be the following
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/backup/misc.img
I unpacked the 10K KDZ, surprisingly there was a misc.bin there. It was not on the previous 10J I checked.
Anyway, here you go. I'm bricked so this is all I can give you. I assume it will be fine.
Hmm... I just looked at it, and it's zeroed-out. But it must be supposed to, right? If you flash the KDZ then that is what happens.
Edit: Or maybe it's only included by accident, and isn't actually flashed...hmm I'll leave it here until you respond, if it's not what you need I'll remove it, so not to detract from you request
Edit2: Removed
askermk2000 said:
I unpacked the 10K KDZ, surprisingly there was a misc.bin there. It was not on the previous 10J I checked.
Anyway, here you go. I'm bricked so this is all I can give you. I assume it will be fine.
Hmm... I just looked at it, and it's zeroed-out. But it must be supposed to, right? If you flash the KDZ then that is what happens.
Edit: Or maybe it's only included by accident, and isn't actually flashed...hmm I'll leave it here until you respond, if it's not what you need I'll remove it, so not to detract from you request
Click to expand...
Click to collapse
thanks, however I believe the KDZ was what caused mine to be zeroed out... now my phone's MAC address is no longer fixed and keeps changing as a result of no misc partition
Wow. You flashed this *H91810k.zip* right? I used that one too while my phone was functioning. And yes I noticed that exact problem with the MAC address because I was using FTP server on the phone. DAMN
How do we fix it? Manual edit of misc partition to insert our original MAC?
Ok I see you wrote KDZ. I flashed a TWRP H918 10K rom from the forum. I suppose many will have this problem.
MISC partition. What does it do
China user
andy_zhang said:
MISC partition. What does it do
China user
Click to expand...
Click to collapse
misc partition contains device info like WiFi and BT MAC addresses, device IMEI and serial number... if you want to help me out, it may be best to open up the file in a hex editor after creating it to block out those information.
Your device is 100% usable without a misc partition. i regularly wiped mine because twrp stores its config there.
me2151 said:
Your device is 100% usable without a misc partition. i regularly wiped mine because twrp stores its config there.
Click to expand...
Click to collapse
So you're saying the IP address changing at every reboot is not related to this?
askermk2000 said:
So you're saying the IP address changing at every reboot is not related to this?
Click to expand...
Click to collapse
IP address changing is related to the DHCP server of your network changing your IP. If you mean MAC changing at every boot its a issue with custom roms. Not the Misc Partition.
me2151 said:
IP address changing is related to the DHCP server of your network changing your IP. If you mean MAC changing at every boot its a issue with custom roms. Not the Misc Partition.
Click to expand...
Click to collapse
Yes the MAC address is changing, therefore IP address changes as a consequence. That is what I meant.
We thought this was because the misc partition was wiped. (I was using stock 10k)
askermk2000 said:
Yes the MAC address is changing, therefore IP address changes as a consequence. That is what I meant.
We thought this was because the misc partition was wiped. (I was using stock 10k)
Click to expand...
Click to collapse
There IS a possibility that the MAC is stored in MISC but im pretty sure its stored in the FIRMWARE partition. Regardless. If you use someone elses MISC partition that you mean you would have their MAC address IF its stored in there. You would still not have yours.
me2151 said:
There IS a possibility that the MAC is stored in MISC but im pretty sure its stored in the FIRMWARE partition. Regardless. If you use someone elses MISC partition that you mean you would have their MAC address IF its stored in there. You would still not have yours.
Click to expand...
Click to collapse
Yes, well it was not my idea to get a misc backup from someone. But @dimm0k did bring to my attention the MAC address problem, and it just seemed very logical that it was caused by that botched 10K KDZ file.
askermk2000 said:
Yes, well it was not my idea to get a misc backup from someone. But @dimm0k did bring to my attention the MAC address problem, and it just seemed very logical that it was caused by that botched 10K KDZ file.
Click to expand...
Click to collapse
The MAC address issue is on almost every aosp rom and aosp roms dont touch MISC so its probably not caused but the MISC partition. Yes theres always a possibility but still. There might be other stuff going on.
@me2151 @askermk2000
while I'm a novice to all of this, I can say with 100% certainty that on the LGV20 the MAC address is tied to the misc partition, which looks to be the /dev/block/sda5 partition. as mentioned, the H91810k KDZ contained a misc.bin that I had in my original release of the TWRP flashable 10k zip. because of this my MAC address has been constantly changing after a reboot to that of something beginning with 00:90:4c. I don't know much about AOSP so I can't comment on that, but because I have 2 LGV20s of different variants I was able to get a dump from the US996 variant for the misc partition and compare that to the "damaged" misc partition on the H918. The size is exactly the same, 32MB, with the beginning parts being different between the two dumps. I was able to restore my MAC address by hex editing the "damaged" misc using the same location from the US996 variant's misc partition as a reference. I was also able to restore the BT MAC address and serial number using the same method. prior to these edits my WiFi and BT MAC addresses kept changing and the serial number was actually missing in the Settings > About Phone section. after these edits they have been constant to what I set them as. the only reason I want the misc partition now is so that I can compare to see if there was anything else in the misc partition that I need to restore that's specific to the H918. the misc partition isn't crucial for the device to work, but it is needed to avoid random MAC addresses that I know for sure.
that said, askermk2000, do you happen to have a misc dump for the US996? that would help me confirm what's missing from the H918 as I have a good US996 misc dump.
This was very enlightening. I was with @me2151 as far as the misc partition goes. I have wiped it many times, for various reasons -- just thought it was used by the stock recovery. One being forgetting to turn off auto updates, and getting caught in a boot loop (wiping fota wasn't enough). But I never used my phone as a server, so no need to consistently get the same address from a DHCP server. Once I get my H918, I will definitely go through it and see what else is in there.
Doing some searching, apparently on older phones it was possible to re-lock your boot loader without wiping data if you dumped the misc partition before and after unlocking. Just flash the "locked" version back, and viola, locked boot loader. This may come in handy on the H918 since T-Mobile allows unlocking, and can't use the eng boot loader that claims it is locked when it isn't.
-- Brian
dimm0k said:
misc partition contains device info like WiFi and BT MAC addresses, device IMEI and serial number... if you want to help me out, it may be best to open up the file in a hex editor after creating it to block out those information.
Click to expand...
Click to collapse
I have uploaded two types of files
China user
andy_zhang said:
I have uploaded two types of files
China user
Click to expand...
Click to collapse
two types of files? can you give more details, as well as the location?
dimm0k said:
two types of files? can you give more details, as well as the location?
Click to expand...
Click to collapse
我可以用工具提取手机底层。
996 的TOT,但是刷不进去。lgv20 刷不进tot.
China user
---------- Post added at 03:17 AM ---------- Previous post was at 03:17 AM ----------
andy_zhang said:
我可以用工具提取手机底层。
996 的TOT,但是刷不进去。lgv20 刷不进tot.
China user
Click to expand...
Click to collapse
https://mega.nz/#F!I4IHTQbR!8Pf3kwL-jirY7zrnia3cow
China user
I am pretty sure the MAC address (& IMEI) is stored in the modemst1 & modemst2 partitions.
I was able to easily change them when I wiped those on my H990DS.
Try going to dialpad & type *#546368#*918# (it is *#546368#*990# for my H990DS)-->SVC Menu-->CRCWIZARD Test-->Auto MID-->MID Setting
(should be able to set with wiped modemst1 & modemst2 partitions however option wasn't available when I restored those partitions)
Prowler_gr said:
I am pretty sure the MAC address (& IMEI) is stored in the modemst1 & modemst2 partitions.
I was able to easily change them when I wiped those on my H990DS.
Try going to dialpad & type *#546368#*918# (it is *#546368#*990# for my H990DS)-->SVC Menu-->CRCWIZARD Test-->Auto MID-->MID Setting
(should be able to set with wiped modemst1 & modemst2 partitions however option wasn't available when I restored those partitions)
Click to expand...
Click to collapse
That is not the point. It's just a shadow copy in the misc, probably for easy access by apps. But as a courtesy to the users wanting to help, he mentions it, though I wouldn't sweat about that imei stuff.
Who cares? I've been reading smartphone forums en-mass for a long time now, and there's no shortage of people posting their imei for various reasons. Or go to Ebay and look at almost every phone listing, you will find the IMEI so ppl can check if it's blacklisted.
You can even generate your own imei if you really wanna change it.
Edit: He already said that he fixed his wlan & bt mac address by editing the misc partition.