Hi,
I Accidently erased my two partitions name mdm1hob and mdm1dhob i have a qcn backup but since i've deleted mines. I cannot restore it. Can anyone send me those partitions? Thanks.
gurcay said:
Hi,
I Accidently erased my two partitions name mdm1hob and mdm1dhob i have a qcn backup but since i've deleted mines. I cannot restore it. Can anyone send me those partitions? Thanks.
Click to expand...
Click to collapse
Up
If those two partitions contain the IMEI, they cannot be offered as applying them to your device would in effect be cloning the IMEI, something which is illegal here in the US and most everywhere else to boot.
I'm afraid you're looking at having the device serviced, if your backup doesn't work.
There is surprisingly little info about these two partitions on the net. It seems that they only exist on the N6. If I find some time, I'll see if I can figure something out.
Strephon Alkhalikoi said:
If those two partitions contain the IMEI, they cannot be offered as applying them to your device would in effect be cloning the IMEI, something which is illegal here in the US and most everywhere else to boot.
I'm afraid you're looking at having the device serviced, if your backup doesn't work.
Click to expand...
Click to collapse
i believe those partitions contains modem usb services. Diag ports, usb debugging ports, communication services, etc. I have my efs on qcn but i can't restore it without missing partitions.
runekock said:
There is surprisingly little info about these two partitions on the net. It seems that they only exist on the N6. If I find some time, I'll see if I can figure something out.
Click to expand...
Click to collapse
Yes it's quite interesting. I think i looked everywhere, asked Google forum. It's dead end.
I'll ve very grateful, if you can help me.
Related
So. my IMEI is jacked up. I made a copy of /efs when I got the phone but instead of making an archive I did a straight copy, Seems like the fat filesystem owned the permissions.
I am trying to restore from that backup but I am not having luck. People say you can just drop those files into place but it seems that they are replaced after every reboot. What do the permissions need to be? I see that ownership needs to be 1001:1001. Also, can I do this on JH7 with any success?
If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo
I used the CWM flashable zip to get back to JH7, didn't use odin (im not at home yet, and this was eating away at me at work, heh).
Ill flash back with odin and then see where that gets me. For my own sanitys sake, could you tell me what the permissions are on your files in /efs?
i have a fix that worked for me posted in the dev section
bames said:
i have a fix that worked for me posted in the dev section
Click to expand...
Click to collapse
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply
z28james said:
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply
Click to expand...
Click to collapse
once in jf6 if your imei isn't corrected then delete everything but the nv_data.bin and .nv_data.bak.md5.
use android terminal emulator to execute following (must have busybox installed)
su
busybox chown 1001:1001 /efs/nv_data.bin
reboot
avgjoegeek said:
If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo
Click to expand...
Click to collapse
fyi android id is different than the device id. Device ID = IMEI.
I see my problem, the efs directory I have is from my OLD captivate. Arrrg....I have no backup of my current /efs. The random nv_data.bin it creates has the correct product code already.
There must be something in the phone that knows the imei as this is why it was not accepting my dropped in files (the files from my old phone).
Ah well...ill use it till ATT blocks the test IMEI "lose" mine and go get a refurb as I have insurance.
FYI, the stock original firmware does not create those .bak files from what I could see. I bet your files had jacked product IDs but perhaps the part that went with your IMEI was still intact. This would be why my phone wont accept my old phones nv_data.bin?
once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.
bames said:
once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.
Click to expand...
Click to collapse
None of those files get generated for me or exist. If I remove everything, a generic nv_data.bin and .imei get created. Thats it. If I copy over the files from my old captivate, I believe they do get created but since the IMEI in that file does not match whatever is being checked in the phone, new files are created anyways.
I suppose nobody as of now knows how to generate the string that is in the nv_data.bin based on an IMEI so it seems that I am out of luck.
Perhaps some shady place in town can help me repair the IMEI or something
I ended up calling Samsung today. I described the problem (damaged IMEI) and they sent me a pre-paid shipping label to send it off to Plano TX to have them take a look (i'm in Austin).
I will let you guys know how this turns out.
My phone is on its way back to me. They ended up swapping the mainboard under warranty.
I suppose if you have a damaged IMEI and can deal with using an old phone for a week, consider sending it over to samsung.
did you have to pay for new mainboard? cause i got the same problem but i am not the orginal owner for the phone.
Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.
Phateless said:
Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.
Click to expand...
Click to collapse
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text
z28james said:
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text
Click to expand...
Click to collapse
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...
Phateless said:
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...
Click to expand...
Click to collapse
Well, the warranty period is a year and so since its been less than a year since the captivates release, you should be good. It would seem the only way it would be out of warranty would be if samsung for some reason deemed it to be at some point. Im sure you could call samsung with the IMEI and verify.
In my case, my product ID had become damaged. My problem is although I had a backup of /efs, it was for my first captivate, not my current. I deleted /efs and moved the backup into place. Seeing that it was the nv_data.bin for some other phone with another IMEI (the IMEI is encrypted inside that file) it instead replaced the files with a generic set of files and the dreaded test IMEI.
Since nobody had a good way to write the IMEI to that file as it expects, I was SOL.
If I could do it again, I would make a .99 cent jig (I did this using a wonderful thread here labeled something like "make a jig without cutting up USB cable) which gets you into download mode if odin or something soft bricks your phone, root, make a backup of /efs and then take a nandroid backup. I THINK I remember reading that sgstools can backup /efs for you but in the sticky there is a method on how to make a .tar of /efs (good as this will retain permissions/ownership as if you straight copy them to the sd card with fat32, the filesystem does not understand linux permissions and blows them away).
Master-Clear did the trick 4 me
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!
TommyZee said:
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!
Click to expand...
Click to collapse
Do you know where I can find this ODIN3 one-click and how to do a master clear?
Can one of the devs, share with us what happens when Android loads what does it do to the efs directory, what is the purpose of each of the files in this directory. There are not so many.
efs
.....nv.log
.....nv_data.bin
.....nv_data.bin.md5
imei
......nvmac.info
.....bt.txt
.....mps_code.dat
I searched on google and did not find anything definitive.
StarLog said:
Can one of the devs, share with us what happens when Android loads what does it do to the efs directory, what is the purpose of each of the files in this directory. There are not so many.
efs
.....nv.log
.....nv_data.bin
.....nv_data.bin.md5
imei
......nvmac.info
.....bt.txt
.....mps_code.dat
I searched on google and did not find anything definitive.
Click to expand...
Click to collapse
Your Google-Fu is weak: http://www.galaxyroot.com/how-to-efs-folder-backup-restore-nv_data-bin/
General gist: Don't mess with it.
knightnz said:
Your Google-Fu is weak: http://www.galaxyroot.com/how-to-efs-folder-backup-restore-nv_data-bin/
General gist: Don't mess with it.
Click to expand...
Click to collapse
Hey thanks, but I did find that, I already know how to backup and restore it.
My question was implied to be a lot more technical, like what byte structure in each file, has what representation.
What part of the bootup process touches or creates the files.
But thanks for sharing.
The file format of files in /efs has not been disclosed. People have tried reverse engineering it with various degree of success.
It does contain IMEI, carrier lock information and other radio related stuff. See unlocking threads here and in Galaxy S forums.
There is also daemon (efsd) which monitors, backups and checksums files in efs.
The radio firmware must have some way of accessing files in efs, but not directly, probably via RIL, since Galaxy S CyanogenMod folks can move it to different file system.
There is probably a lot of useful and interesting stuff stored in these files but messing with them is also dangerous, so backup first.
Thats what I needed to hear, so I must dig more. thanks for the headsup on galaxy s forum
Hi! Anyone can upload EFS folder \efs) ? You can attach as zip file. Doesn't matter, it's important to be there all files.
I bricked my phone and I want to unbrick. Please, anyone who is experimented, please help me!
Best Regards,
Cristian Silaghi
NO one found this folder on the galaxy mini....the phone can turn on or not?? if yes u can unbrick...
efs folders are unique you have just removed your imei now if you don't have your own backup nothing can be done
now your mobile is a mp4 player if anyone uploads his efs file his mobile will also be a mp4player
dheeraj (dhlalit11) said:
... if anyone uploads his efs file his mobile will also be a mp4player
Click to expand...
Click to collapse
Just because you're a Recognized Contributor, that doesn't mean you can bull****.
That is not true! Admit it, you don't know how pull the /efs ot from your phone
Like you said, /efs folder contains alot of things that are unique for each phone (WiFi MAC adress, IMEI, product code and what not), so we can't just give someone our /efs. Even if we could, the way of pulling those files from the phone are not known to me.
Wish we knew a way to backup it, when something like this happens - you just put the backup and away you go
just because am an rc that doesn't mean am bullying
nothing difficult in backing up efs file just go to /efs and copy those files to your sdcard and they will be backed up
but efs is visible only in operator specific models in normal phones imei is hardcodded in the mobile
mine galaxy s is of at&t and I can see the efs folder, prior of flashing roms on it I did a backup of that folder
and sometimes it got deleted then I just need to copy them back
can't see on original galaxy s of my friend
the thing is one imei cannot be used in two mobile there can be many conflicts and some also related to laws
only one sim can be used at a time on a single imei
that's why I said mp4player but you can still try to share your efs files if it works then just keep it else delete it
op if you have your operator specific firmware and it contains an efs.rfs file then you may have the possibility of getting back your imei
just try it, may work
dheeraj (dhlalit11) said:
just because am an rc that doesn't mean am bullying
nothing difficult in backing up efs file just go to /efs and copy those files to your sdcard and they will be backed up
but efs is visible only in operator specific models in normal phones imei is hardcodded in the mobile
mine galaxy s is of at&t and I can see the efs folder, prior of flashing roms on it I did a backup of that folder
and sometimes it got deleted then I just need to copy them back
can't see on original galaxy s of my friend
the thing is one imei cannot be used in two mobile there can be many conflicts and some also related to laws
only one sim can be used at a time on a single imei
that's why I said mp4player but you can still try to share your efs files if it works then just keep it else delete it
Click to expand...
Click to collapse
Things on Galaxy S and on our mini are a little bit different for that /efs matter, because nvdata.bin is in devblock5 or something like that, an on Galaxy S it's in a different place. Strange, but it is that way, i tried all the Galaxy S tutorials to make a backup and none of them worked.
And yeah, you cant just copy the folder since that will **** up th permissions and then the files are almost useless.
Yeah, he has a great MP4 now, unfortunately :/
I know imei is unique, thats why i said ''if we could give our efs''
just copying the efs files works great for me
I never changed permission of efs files
and had done it three times by just copying
If you distroy your IMEI becouse of bml/efs you can repair it with JTAG. Write full dump then repair its IMEI (to be the one from you stiker). Generaly this is a Service job becouse you dont't have the necessary tools.
i don't have this /efs folder, but i still can browse internet, call my friends, do a SMS, play music. Just like a normal phone do.
F4uzan said:
i don't have this /efs folder, but i still can browse internet, call my friends, do a SMS, play music. Just like a normal phone do.
Click to expand...
Click to collapse
if you cant see that doesn't mean you don't have efs
it is just that you cannot see it like you cannot see bootloader, kernel etc.
I bought a used mix which has no wifi functionality due to what seems to be a corrupt EFS. The mac address is 02:00:00:00:00, however the IMEI is correct and is the same one on the box.
I've flashed it with the official rom, but the mac address is still empty. I've been able to get the QCN file off the phone but I do not have a non-corrupt version to restore to.
Can someone be kind enough to send me their QCN without their IMEI? Would very much appreciate it. I have the 6GB ram 256GB version of the phone.
certitude said:
I bought a used mix which has no wifi functionality due to what seems to be a corrupt EFS. The mac address is 02:00:00:00:00, however the IMEI is correct and is the same one on the box.
I've flashed it with the official rom, but the mac address is still empty. I've been able to get the QCN file off the phone but I do not have a non-corrupt version to restore to.
Can someone be kind enough to send me their QCN without their IMEI? Would very much appreciate it. I have the 6GB ram 256GB version of the phone.
Click to expand...
Click to collapse
Did you also post on miui.com
james1089 said:
Did you also post on miui.com
Click to expand...
Click to collapse
I did. I posted it under the 'Q&A' section. No response yet lol.
certitude said:
I did. I posted it under the 'Q&A' section. No response yet lol.
Click to expand...
Click to collapse
I haven't got 256 version or I would send you, seen on other sites listing the files but not for mix
qcn File
james1089 said:
I haven't got 256 version or I would send you, seen on other sites listing the files but not for mix
Click to expand...
Click to collapse
Hi , here a qcn file, the lines 0x1E700 / 0x02530 with IMEI has been replaced by 088A AAAA AAAA AAAA AA,
use the IMEI converter and put your own IMEI with the HEXeditor.
Thanks alexlovar! I was able to restore the qcn using your file.
Unfortunately, the mac address is still 02:00:00:00:00:00. I'm starting to think something hardware related is wrong with this phone. Really sucks to be burned buying a used phone.
certitude said:
Thanks alexlovar! I was able to restore the qcn using your file.
Unfortunately, the mac address is still 02:00:00:00:00:00. I'm starting to think something hardware related is wrong with this phone. Really sucks to be burned buying a used phone.
Click to expand...
Click to collapse
hi, what ROM you have installed?, in my mix only work the original MIUI global version, i don't know if the mac address is include with the qcn file but i don't believe this, because this manage only the modemst1 and modemst2 partitions.
i see something on goolge search: https://appuals.com/fix-020000-mac-address-android-custom-roms/
alexlovar said:
hi, what ROM you have installed?, in my mix only work the original MIUI global version, i don't know if the mac address is include with the qcn file but i don't believe this, because this manage only the modemst1 and modemst2 partitions.
i see something on goolge search: https://appuals.com/fix-020000-mac-address-android-custom-roms/
Click to expand...
Click to collapse
I tried multiple roms from the latest global version, china stable, china dev, and some custom roms. They all result in the same problem. I'm not sure if the qcn contains the mac address for the mix, but from what I read the mac address is contained in the qcn for other xiaomi phones.
I also haven't been able to purposely clear the IMEI. I've tried using the adb commands and also the command through the dialer. Granted, those guides were for other xiaomi phones. I figure it would be a good idea to clear the efs before restoring the qcn you sent, but the IMEI never clears.
certitude said:
I tried multiple roms from the latest global version, china stable, china dev, and some custom roms. They all result in the same problem. I'm not sure if the qcn contains the mac address for the mix, but from what I read the mac address is contained in the qcn for other xiaomi phones.
I also haven't been able to purposely clear the IMEI. I've tried using the adb commands and also the command through the dialer. Granted, those guides were for other xiaomi phones. I figure it would be a good idea to clear the efs before restoring the qcn you sent, but the IMEI never clears.
Click to expand...
Click to collapse
in my case, the commands :
dd if=/dev/zero of=/dev/block/sdf3
dd if=/dev/zero of=/dev/block/sdf5
dd if=/dev/zero of=/dev/block/sde28
doesn't work (for me), i must delete the modemst1 /modemst2 /fsg partition manually, using root explorer. (Rom MIUI 8.5. rooted) reboot and verify that the IMEI is cleared, if not, delete manually again, reboot and then restore the qcn backup file with Qfil_QPST.2.7.430 . look http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/
i hope this helps!
Hi.
I ask for help, as I have IMEI cleared. I tried to reflash the phone, but IMEI is still gone. I noticed there aren't images of NVDATA and NVRAM partitions on any of firmware available online.
Also, wt_custom can't be flashed because of verified boot, haven't noticed any problems caused by it, just saying it if it's important. Raw data of this partition says it has carrier configuration files.
Can it be created by myself? SN Write Tool either doesn't work or I don't know how to use it. Other tool says something about authentication.
I don't know if it's appropriate for this forum, please delete it in case of.
Did you solve that? I have the same problem.
I need the boot partition does anyone has it?