Database Develop

[GUIDE] how to get IMEI to stick across reboots

This is a rundown of restoring your IMEI and /efs partition. A lot of people lose their IMEI and have no problem restoring it a variety of ways. But if your restored IMEI disappears on next reboot, your problem is something else. I had this, and I believe it was a corrupted /efs partition.
solution, short answer: flash a good efs.rfs file. I did it in Heimdall; I assume it'll also work in Odin. The one I found online (see attachment) restored my efs to the dummy IMEI of 004999010640000. Where I live and on my provider, this gives me network access. From there I could restore my backup nv_data.bin file to /efs. And then my proper IMEI sticks across reboots.
also: kitch posts another way to fix this, here and here.
NOTE: Messing with IMEI has potential legal problems. The attached file restores IMEI to a fairly common dummy number, so I assume it's not a problem. (mods, please delete if this is a problem). The dummy IMEI could work in your area, but that still could pose legal problems. Check in your area, and see the next paragraph.
WARNING/DISCLAIMER: I found this file on Rapidshare. I don't know who made it, put it there, where it might have been linked from, or what exactly is in it. All I had was a filename and I googled it. And all I know about it is that if you have the problems described above and below, then this may work for you. It did for me. If anyone can "see" inside the file to check that it doesn't contain anything malicious, please comment. All I can say is that ClamXav found nothing wrong with BML3_RESTORE.tar.md5 or the efs.rfs contained within it. And that I'm not responsible for what you do to your own phone.
More ways to check if this is your problem:
- You have no signal. In System Settings > About phone, Baseband says Unknown, even if you know you have a modem in there. Also, them going to Status, your IMEI and IMEI SV also say "Unknown". Other people posting about lost IMEI say they have either all zeroes there, or the dummy IMEI 004999010640000.
The rest of this is what I did in GB. I assume if you have this problem, you tried other solutions that got you here too.
- Flashing stock Samsung ROM with repartition doesn't restore IMEI (at least in Heimdall; I can't check Odin). Flashing EZbase Recovery in Heimdall doesn't do it either. They flash, but afterward boots to recovery mode and shows errors about not being able to apply Multi-CSC.
- in Terminal Emulator or adb, running 'mount /efs' returns: 'mount: can't read 'etc/fstab/': no such file or directory'.
- From here, you can still flash a rooted kernel and flash GB ROMs in CWM recovery mode. After each flash, recovery mode shows errors about not being able to mount /efs and/or /dbdata, and not being able to apply CSC.
- From here, if you try flashing to CM7 or CM9, installation aborts. Onscreen error message shows problems with /tmp/updater.sh.
- If you tried to flash a recent kernel with Heimdall, you can get in its recovery mode. I did this trying to get to a known working JB nandroid. I flashed the JB rom again, and it completes. Rebooting sent me back to recovery mode. Repeat rebooting until fed up. Restoring nandroid completes. Rebooting sent me back to recovery mode. Repeat rebooting until fed up.
solution, long answer:
For me, this was from GB.
- Flash the attached file. For Heimdall, untar it (in command line, run 'tar -xvf /path/to/BML3_RESTORE.tar' without quotes, and replacing /path/to/ with the proper filesystem path. If you don't know what this is, try dragging and dropping the file into your terminal window on your computer.)
Then run: 'heimdall flash --efs /path/to/efs.rfs' (without quotes, again replacing path, or drag-and-drop the file into your terminal window)
On first attempt (second was other human error), I did not flash a whole package with PIT file, or repartition. I did later, and that worked fine, too.
- It automatically reboots (unless you told Heimdall not to). You may go to recovery mode and see a bunch of errors about mounting, but applying Multi-CSC is a success. Reboot, and the phone starts normally. You may momentarily see the circle-and-slash no-signal icon in the upper left corner, but soon after it should show signal bars. Your homescreen may show your network somewhere.
- Check IMEI. It should be the dummy number. You can do this with the phone's number keypad (typing *#06#). I prefer to go to System Settings > About phone > Status. This way you can see the dummy IMEI, and IMEI SV should now also show a number. Go back up one level and also check Baseband; that should now show your modem.
- Restore actual IMEI. This requires that you previously backed up your /efs folder. Restoring this is documented better and more thoroughly elsewhere. I went into my /efs backup folder and copied nv_data.bin to /efs. This is easy with Root Explorer. Press the filename, select copy, navigate back up and to /efs. At the top of the screen, click Mount R/W. Delete everything in there (menu, multi-select, select all, delete). Paste the file. Long press the file, change permissions. Make it 644 (Owner is Read+Write, others are Read), save. Long press again, scroll toward bottom of menu and Change Ownership. Make it Radio (1001) and Radio (1001), save. Click to Mount R/O and exit.
- Check it. Go back and check your IMEI and it should be your real one. IMEI SV should probably change, too. (For me, it was 01 in GB, but now it's 03 in ICS). Reboot, and it should remain. Baseband is also filled in.
From here you can flash up to ICS, or whatever, and your IMEI should remain.
note on attachment: The original filename I searched for and found on Rapidshare was BML3_RESTORE.tar.md5. I've changed the extension to be *.tar, so it can upload to XDA. I think Odin users need to add the .md5 extension.
md5 checksum for BML3_RESTORE.tar: f5ab4c90ed60105c8b50e4e9b112e50b
Credit: XDA user magarto is the one whose post led me to this file and fix, from his post here.
errata: This was originally a [Q]-tagged Question thread. I overwrote the OP with this guide and changed the thread title. Hence, the next several posts may seem out of context.

Still unsolved huh? Khmers do have limited access, due to what happened in their country, anyway you can get a better idea here http://forum.gsmhosting.com/vbb/f258/ how efs problems are solved by various box. Just search this forum about efs or post, many Filipinos there .
Having said that, the version of Galaxy S I am using is Korean (has DMB TV, so hardware differences), and to solve this in our version , we simply flash the beginning ROM (with MOVI Files) Its like the Installation Files of Windows, which does a complete setup . This is the last resort for the Korean Galaxy S, solves any and every problems, always wondered why the Galaxy S, does not have this compilation or its only with samsung service centers. anyway
If you have an efs backup, you should try using Root explorer to overwrite (copy paste) the the current efs folder, fix chmod 644 and EXIT using the menu of root explorer and reboot phone to see if it sticks.

thanks for the forum link. yeah, the phone shop nerd was stuck, too. and they did have a box, several that sounded like the octopus box you said.
i've been doing some looking, too, and wondering if it's corrupted file system. i saw several posts about corrupted internal SD, and I don't know if that could be related. my internal SD mounts fine when I boot up, and all my files are there and working. nonetheless, this post seemed interesting, about reformatting in adb with parted:
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
but i still have yet to find out if it's related. flashing anything in recovery, i see this:
E:failed to mount /efs /dbdata your storage not prepared yet please use UI menu for format and reboot actions
ehhh... i'd put off learning more about adb on the backburner. looks like i'm diving in.

Two different issues, internal SD get corrupted when one fails to UNDO lag fix, since samsung uses rfs and lag fixing changes it to ext 4, internal SD will fail to be recognized and needs to be formated to rfs by any Rom using rfs ( mostly stock Roms (to solve that flashing a speedmod kernel, does the trick) But your problem is efs folder
and i came across one person, who had both because he had made a onenand mode lagfix and failed to undo before flashing and was pretty impossible to get over

xsenman said:
and i came across one person, who had both because he had made a onenand mode lagfix and failed to undo before flashing and was pretty impossible to get over
Click to expand...
Click to collapse
ugh ... that does not sound promising.
and i'm not even fully aware yet what lagfix is or does. it had never been an option on any kernel i used since i started flashing roms, only early this year from stock to CM7 and soon after to CM9 and other ICSes. Well, until yesterday, when i tried flashing a supercurio kernel on a GB rom, and that failed. But I did see lagfix options under recovery>advanced. at any rate, i hope i'm not in the same boat.
is there any way in adb to find out if i am?

groksteady said:
ugh ... that does not sound promising.
and i'm not even fully aware yet what lagfix is or does. it had never been an option on any kernel i used since i started flashing roms, only early this year from stock to CM7 and soon after to CM9 and other ICSes. Well, until yesterday, when i tried flashing a supercurio kernel on a GB rom, and that failed. But I did see lagfix options under recovery>advanced. at any rate, i hope i'm not in the same boat.
is there any way in adb to find out if i am?
Click to expand...
Click to collapse
what I am saying is that, you do not have this problem, cause If you had, your internal SD will become unavailable and cannot be used and cannot be formated either ...so just solve the efs problem , thats what you need to concentrate on.

xsenman said:
what I am saying is that, you do not have this problem, cause If you had, your internal SD will become unavailable and cannot be used and cannot be formated either ...so just solve the efs problem , thats what you need to concentrate on.
Click to expand...
Click to collapse
thanks, man. i just did try this, simply taking a Camera photo and opening it in Gallery. also, ran mount in terminal to see, and yeah, saw rfs not ext.
when i try to mount /efs, i get an error:
moutn: can't read '/etc/fstab/': no such file or directory. there's a vold.fstab in there, with paths for mounting the internal and external sdcards. ehhhh... still learning what all this is about.

groksteady said:
thanks, man. i just did try this, simply taking a Camera photo and opening it in Gallery. also, ran mount in terminal to see, and yeah, saw rfs not ext.
when i try to mount /efs, i get an error:
moutn: can't read '/etc/fstab/': no such file or directory. there's a vold.fstab in there, with paths for mounting the internal and external sdcards. ehhhh... still learning what all this is about.
Click to expand...
Click to collapse
efs folder has read only permission, so you cannot do anything you like...don't mess with vold.fstab...you will have problems with your SD cards .
The only thing I can suggest is to go back to th earliest eclair or froyo to recover.
you may need to unarchive the downloaded file and then unarchive the resulting TAR files too
Hence in heimdall you should have
PIT file (s1_odin_20100512.pit), CHECK repartition
IBL+PBL = boot.bin
SBL = Sbl.bin
MODEM = modem.bin
PARAM = param.lfs
CACHE = cache.rfs
DBDATAFS = dbdata.rfs
FACTORYFS = factoryfs.rfs
KERNEL = zImage
But First, try to delete the EFS Folder (using root explorer) shut down, Go into recovery and wipe everything than battery pull to shut down and go onto download mode after that Flash
just a suggestion

xsenman said:
Hence in heimdall you should have
PIT file (s1_odin_20100512.pit), CHECK repartition
Click to expand...
Click to collapse
thanks ... this is where I get hung up. Anytime I check repartition, I get libusb End of Pit errors. It runs fine without repartition. This is Heimdall 1.3.1 and 1.3.2 on a Mac 10.5.8.
I'm going to make an Ubuntu Live CD and see if I can get it that way. I used to have an old Lubuntu laptop, and I remember Heimdall working to flash a kernel when the Mac didn't. It'd be great if the repartitioning is what's holding me back.

aargh. didn't work. Heimdall on Linux does let me repartition, but on the reboot I still get errors that /efs can't be mounted, multi-CSC can't be applied, etc. I tried ezbase recovery and the full stock setup for the original provider from sammobile. I tried deleting /efs, full wiping and pulling the battery like you suggested. I tried separately flashing a dbdata.rfs in heimdall, which was suggested for someone else with mount problems. but, it seems like all the other mount problems people have are with sdcard, and not /efs.
If I restore /efs, is it supposed to write data to /dev/block/stl3? because that file is always 0kb. But I could try the dd command to restore that way... maybe later tonight. it's been a long afternoon working through this.
I also don't know what is the deal with not being able to find /etc/fstab. I saw in some other places that Android doesn't use it, so I don't know what's calling it, and why. Or if that's tied to why I can't flash anything beyond a GB rom; I get errors about /tmp/updater.sh.
EDIT: OK, so at some point with ezbase recovery and manually restoring nv_data.bin to /efs, after a little while I saw that my /sys/block/stl3 (and so /dev/block/stl3) were looking normal. I successfully restored the file, plus the IMEI folder, which has bluetooth info. I did this with flight mode on, toggled it off and connected to my network. About Phone was showing my real IMEI, plus BT and wifi MAC addresses. And I had /sys/block/stl3 looking normal. So I ran the dd if=/sys/block/stl3 of=/sdcard/efs.rfs, and used that efs.rfs file to flash full roms in heimdall, repartitioned. I used ezbase recovery and the stock firmware from sammobile.com for the original mobile provider. Neither worked. On first boot both times, I got errors about not being able to mount /efs or apply multi-CSC. My IMEI on reboot is always "unknown", not even all zeroes, until I fix it. And CWM won't flash any CM7 or CM9 zips, giving status 7 errors that it couldn't mount. I also tried flashing the efs.rfs file alone in heimdall command line, and that didn't work. Ezbase is 2.3.3 and my stock is 2.3.5, and serial number info indicates it was made in 2011 or really late 2010 (i'm loathe to pull the battery off these days), so I wouldn't think Froyo could help out. I've reached out to a few people here who had the same problem, but never posted about a fix, or finally giving up. I'm almost at my wit's end. There must be a solution, some way to reformat or push back /efs data to /stl3.
BTW, can anyone post the filenames of what is in /sys/data/stl3 for their i9000? I'd like to know if I'm missing something in there, at least when it does fill up. Right now, I'm thinking it's gotta be a bad partition.

weird..just can't help wondering why it seems so difficult, I assume you are always practicing standard requirements before and after flashing like
1. Using CWM, make sure to wipe data/factory reset,
2. Then wipe cache, and then go into advanced, and wipe the dalvik cache too.
3. From there, flash the ROM
4. Afterwards, repeat the wipe step as in step #1
5. Continuing on, go into advanced and fix permissions.
6. Finally, reboot the device.
In my version its even more stricter, take a look this is required for an uncomplicated Flash

Hm, I've always done 1-3, as that's what's prescribed in most installation instructions, and still Dalvik even if it's not specified. I've only ever wiped post-flash a couple times, and only because it was mentioned in some threads, plus a whole re-flash of the rom. And I'd never heard of fixing permissions after flashing until HellyBean, but I always did with that.
This problem came up coming off of HellyBean with the test idle2 kernel, to AOKP JB, which apparently boots after a status 7 error and abort, but I only knew that later and didn't try that. I then flashed Semaphore to get to the working CWM 6 backups, and ended up in a loop of recovery modes. In hindsight I should have flashed a whole rom -- I went from a datadata rom to one without that I never booted, then to a kernel without datadata just to get the recovery and nandroid.
Rats, I didn't even think about that.until just now typing this out.
sent from a telephonic device

IMEI BACK.
There was a link in a post here that got me there -- basically, someone uploaded an efs.rfs file. Mods, flag me if this is illegal/against rules, but I'd guess it's not because the file gives you the 0049 IMEI.
But for me that didn't matter -- my partition or the linking was screwed up somehow, and I needed a proper one to flash in Heimdall. I couldn't simply correct my nv_data.bin backup and then export bml3.
The Spanish forum link goes to a dead upload, but I was able to find the file BML3_RESTORE.tar.md5 on Rapidshare. If you need this, it was a rollercoaster. At this point I didn't expect anything to work, and I'm still suspicious of finding a file on the web and flashing it without at least some community I can "talk" to about it.
What happened with the file: I flashed it in heimdall, onto a pretty overloaded and laggy JW5. Rebooted, and immediately saw the circle-and-slash no signal logo, so thought it didn't work -- then it pops up to four bars. I swipe to unlock the screen and it completely freezes. So I went back to ezbase recovery kit and flashed the whole thing (with the CF-root kernel, not stock) plus the efs.rfs file. I didn't repartition because I'm on a Mac, and that doesn't work for some reason, and the linux live CD is painfully slow. It flashes, and after completion, I still get a bunch of errors about mounting, but i get a success message about applying multi-CSC. I reboot, and About Phone shows the fake IMEI, but the homescreen is showing my provider. Also, the file explorer showed my internal and external sdcards.
I reinstalled Root Explorer with Titanium Backup, deleted all in /efs and dropped in my backed up nv_data.bin, changed perms and ownership to radio and radio. Exited folder and reopened, and it was all repopulated. Then I dropped in my backup of the /efs/IMEI folder, only because that has a file with BT info and that didn't regenerate. Rebooted, and all was still there! Finally getting out of this weeklong rabbit hole, and able to come back up to ICS with my real IMEI.
Word of caution, though, if going back up from there to one of the latest ICSes. There's people saying to take the latest CM9 nightly -- if you do that, you're flashing up to CWM 6. If you want to go from there to any of several other ICS roms, you might run into a problem because they might be CWM 5.*. After I had CM9 booted, I went into recovery to flash AOKP M6, lost recovery and ended up having to go *back again* to heimdall. Then onto Team Hacksung's CM9 build 16, then finally to AOKP. Done. And I think at this point I'll lay off the Jellybeans for a little while.

groksteady said:
IMEI BACK.
Click to expand...
Click to collapse
This is great, Now in order to get others who may get into this situation, out of this mess, can you post a step by step guide ( simplified as much as possible)
such that I can link your post to my EFS problems and solutions post, already downloaded Bml3 and will upload to another , so a step by step guide to resolve this will be helpful to others.

xsenman said:
This is great, Now in order to get others who may get into this situation, out of this mess, can you post a step by step guide ( simplified as much as possible)
such that I can link your post to my EFS problems and solutions post, already downloaded Bml3 and will upload to another , so a step by step guide to resolve this will be helpful to others.
Click to expand...
Click to collapse
Sure thing... I'll amend the OP later today. So glad to be out of this mess. I seriously thought I'd be manually restoring my imei on every reboot until I get a new phone.
sent from a telephonic device

xsenman, I changed the OP to a guide, hopefully the symptoms and instructions are clear enough. and thanks for talking me through this; I was losing my mind, and so close to throwing my phone in the river.
for anyone else: xsenman was helping me in another thread too. There, I mention how the official Samsung Service Center here said I had a memory board problem, can't recover IMEI without replacing that, for US$150. I went to one of the many phone seller shops with decent hackers/tinkerers, and they couldn't do it either, and they had Octopus Boxes, or at least a box for Samsung.
anyway. HTH others.
and a tinfoil-hat request: anyone who is able to look at the file attached in the OP, can you see if there's anything troubling or 'weird' in it. I just found the damn thing and tried it. It wasn't the most security-conscious step, but I was in a pinch.

so i had this same problem flashing hellybean 20120820 and used one of the guides here to return to stock then copied my good efs off to my computer flashed all the way back then restored the efs folder but it wouldnt stick. I tried several times fixing permissions and a few other suggestions on this forum but nothing worked. Finally i read somewhere that the cache would restore the efs folder if it wasnt cleared, so i restored my efs thru root explorer to the good one from gingerbread rebooted to recovery, wiped cache, and rebooted. Voila it finally stuck, i dont know exactly why it worked or where i heard clear the cache but it did. Maybe it will work for oyu

Psykologikal said:
Finally i read somewhere that the cache would restore the efs folder if it wasnt cleared, so i restored my efs thru root explorer to the good one from gingerbread rebooted to recovery, wiped cache, and rebooted. Voila it finally stuck, i dont know exactly why it worked or where i heard clear the cache but it did. Maybe it will work for oyu
Click to expand...
Click to collapse
Huh, that's cool. I hadn't read that anywhere before. I'm not in that jam anymore, but its good to know.
I do wonder if I all the other 'normal' methods never worked for me because I was using Heimdall. It shouldn't make a difference, but I did run into basic common problems, like repartitioning not working on Macs.
Thanks for the tip. I hope I won't need to try it.
sent from a telephonic device

I have SC-01C docom tab. during unlocking its imei became null and baseband became unknow. I try this tutorial and result in imei 0000946xxxxx.
But when I restart tab. Imei again null.
Note: there is no option of 644 in Permission.
Please help me to solve this.

nsnobel2 said:
I have SC-01C docom tab. during unlocking its imei became null and baseband became unknow. I try this tutorial and result in imei 0000946xxxxx.
But when I restart tab. Imei again null.
Note: there is no option of 644 in Permission.
Please help me to solve this.
Click to expand...
Click to collapse
Sorry to get to this reply so late. And, that I'm not sure I can help you -- I don't know anything about this tablet. This guide helped me with a Samsung Galaxy S i9000. From a quick search online, the PIT file you'd use is different. I don't know for sure, but I would guess it's possible that your EFS partition is different from the i9000, and this method would not work for you.
For permissions, you should be able to change them by long-pressing a file in Root Explorer, Root Browser or similar apps; it's not an option you choose, you manually toggle r/w, r and r for owner, group and others, respectively. Or you can use the chmod command in Terminal to set to 644, same thing.

[Q] No network, no IMEI, unknown Baseband, SIM not recognized,

Hi,
After trying to install an home-made CyanogenMod ROM, I can't connect anymore to the network.
When I type *#06#, it says "null / null"
*#1234# says "AP : I8190XXALL2" (the original ROM I just flashed) "CP : Unknown" and "CSC : Unknown"
Baseband version says Unknown too.
When I try to go to mobile network configuration, it says I've to put a SIM card.
Unfortunately, I've no backup of EFS or ModemFS, if the issue comes from here.
Already tried to flash stock ROMs like the I8190XXALL2_I8190OXXALL1, I8190XXAMA1_I8190OXAAMA1, or I8190XXAMA2_I8190XEFAMA1_XEF, or restoring a few old backups of the whole system. Still nothing.
I've heard I could've corrupted the EFS and lost the .nv_data file, but AFAIK it's not on the EFS partition on the I8190.
I can successfully make a backup of the EFS with EFSPro and it contains several files :
Code:
11/04/2013 19:28 <REP> .files
11/04/2013 19:28 <REP> bluetooth
11/04/2013 19:28 <REP> FactoryApp
26/11/2012 15:43 0 GUARDFIL
01/01/2012 02:15 12 gyro_cal_data
11/04/2013 19:28 <REP> imei
01/01/2012 02:02 222 pre_recovery.log
11/04/2013 19:28 <REP> RFHAL
11/04/2013 19:28 <REP> RFHAL.DEF
11/04/2013 19:28 <REP> wifi
If someone has an idea it'd be great, thanks in advance.

did u flashed stock roms with custom recovery?

I'm flashing it using Odin3 v3.07 with the phone in download mode. But I've TWRP 2.5.0.0 on it. Should I flash stock recovery and re-flash a stock ROM ?

Take it to Samsung's service center, but first make sure you flash Samsung's stock ROM and a stock recovery. I had this problem too and they've fixed it.

Is it really the only solution ? Because it's not easy for me to contact Samsung and go to a repairer.
And since this type of problems should never happens and might happen only when you're tweaking your device, can't they refuse to repair it ?
Someone working on smartphones at Intel can't fix it ?
And if I got it fixed, how should I prevent from further problems ?
Many questions, sorry… Thanks anyway.

I had this problem to and i flashed ot trough odin with a stock rom and a pit file and checked re-par. Square helped for me
Sent from my GT-I8190 using xda premium

piernov said:
Is it really the only solution ? Because it's not easy for me to contact Samsung and go to a repairer.
And since this type of problems should never happens and might happen only when you're tweaking your device, can't they refuse to repair it ?
Someone working on smartphones at Intel can't fix it ?
And if I got it fixed, how should I prevent from further problems ?
Many questions, sorry… Thanks anyway.
Click to expand...
Click to collapse
Well if you get a sloppy serviceman he won't see what you did with a device, so it all depends on him. And yes they can refuse a warranty repair, in which case you're screwed.
I recommend that you backup your partitions in the future. All of them to prevent it from happening again.
You can try repartitioning but I'm 80% sure it won't work.

Yes man, you've lost most of your efs datas.. if you don't have a backup of efs, take it to the service center

Hey, finally corrupted all my modem partition while trying a few things to get back my IMEI, none of them worked. After having it corrupted, it put me in Factory mode and I wasn't able to do anything (only system, cache and efs partitions were mounted AFAIK). Took me some time to find I had to format my modem partition (/dev/block/mmcblk0p12 if I remember correctly), but I still don't have an IMEI. Now I think all the "important" datas were stored in this partition, for exemple in the file named NV.dat (which I don't have any copy). So is a backup of this partition enough to prevent this type of problems ? And since this file might be similar with the EFS file called .nv_data.bin in other Samsung phones, interverting them might make it work ? Or am I totally wrong ? I didn't find any information related to what this file contains in reality, how it is encoded… no one tried to hack it already ?
PS: Now before sending my phone to the service center, I tried to run CM10.1 on it, but it's stuck on the boot animation and I can't connect with adb (that's not the whole story, but it's the last thing I get). Does anyone have an idea ? (I know it's a separate topic and it requires much more informations and we can't make a "working" ROM until we have source code for the NovaThor, but it may interest someone) (you can contact me by IM on the IRC Freenode network for exemple)

i dont know if this will help http://forum.xda-developers.com/showthread.php?t=1264021

Will not work since we don't have a .nv_data file or something similar, I think…

do u have efs back up?

No, that's the main problem, but event with an EFS backup, if the efs datas aren't all stored in the EFS partition, I'd have lost them, no ? (but no one confirms that they are stored in the EFS partition or elsewhere)

Main mistake was to use EFSPro. This program doesn't work correctly with i8190.
Code:
[b]GT-I8190 Partiotions layout. Названия разделов для GT-I8190.[/b]
mmcblk0p1=MBR,GPT
mmcblk0p2=MasterTOC
mmcblk0p3=PIT
mmcblk0p4=MD5HDR
mmcblk0p5=STEboot1
mmcblk0p6=STEboot2
mmcblk0p7=Dnt
mmcblk0p8=reserved
mmcblk0p9=CSPSAFS
mmcblk0p10=CSPSAFS2
mmcblk0p11=EFS
mmcblk0p12=ModemFS
mmcblk0p13=ModemFS2
mmcblk0p14=Fota
mmcblk0p15=IPL Modem
mmcblk0p16=Modem
mmcblk0p17=Loke4
mmcblk0p18=2ndLoke4
mmcblk0p19=PARAM
mmcblk0p20=Kernel
mmcblk0p21=Kernel2
mmcblk0p22=SYSTEM
mmcblk0p23E=CACHEFS
mmcblk0p24=HIDDEN
mmcblk0p25=DATAFS

I need File backup TWRP system for honor7

Hello.
I'm having issues TWRP backups. Maybe I was undone system. I need a friend using the honor 7 PLK-L01 system backup of your phone by then compressed .zip TWRP.roi nk.len up for me to use. My machine is now no longer on the operating system.
*Help me.
thank you

There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.

memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
Thank.
multi tool can use the phone while I was hanging not. and restore them in any way.

memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?

hotboymen2026 said:
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?
Click to expand...
Click to collapse
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.

memht said:
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.
Click to expand...
Click to collapse
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"

hotboymen2026 said:
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"
Click to expand...
Click to collapse
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?

memht said:
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?
Click to expand...
Click to collapse
Status phone rom I'm wrong. logo only lead to hang on is TWRP, connect PC and Fastboot. but when I rom stock (PLK-L01 C432B270) is successful but unable to reboot the operating system. H7 is due to the security, it's hard to be rescued. I also put it into the service center (not the local machine), they also confused with my H7. I need to find ways to revive it, no matter how well!

[Tutorial] Crossflash, Bypass OPID Mismatched Error

Hi there
Thanks to all other guys here who have made helpful development to tame this beautiful =)
To crossflash models other than LG G8 please read post 3.
Before asking any question please read the troubleshooting section at the bottom of the page.
If you still need some specific help I would appreciate if you bring it up just in the thread instead of sending direct messages.
LG has made things difficult in flashing custom and even stock roms by this new OPID thing! It prevents us from crossflashing but we have been able to use TWRP and change the system and some other partitions to have a different rom. We had to make some changes into OP partition using HxD editor.
But now, through this tutorial, we're able to flash any rom without the need to change OPID in OP partition. Also, there is no need to root or unlock boot-loader.
I was successful to do this on some G8 (LMG820UM) but I AM NOT RESPONSIBLE FOR ANY HARM TO YOUR PHONE!
By continuing to read the following instructions you are actually accepting the risk.
IMPORTANT!
first, MAKE A FULL BACKUP OF ALL PARTITIONS; and I mean it!!!
at least, for your sake, make a backup of "modemst1, modemst2, fsg, fsc, ftm" partitions, for emergency.
Requirements
QPST and Qualcomm USB Driver (get)
LGE SM8150 Firehose (get)
LGUP 1.16.0.3 (get)
LGUP_Common.dll (get)
UI_Config.lgl (get)
LG Mobile Driver 4.4.2 (get)
Preparation
1. Install QPST and Qualcomm USB Driver.
2. Install LGUP.
3. Find the folder named "model" in the installation directory of LGUP, then Create a folder named "common" in the "model" folder.
4. Move "LGUP_Common.dll" and "UI_Config.lgl" into "common" folder. Change the attribute of "UI_Config.lgl" to read only.
5. Install LG Mobile Driver 4.4.2.
Steps
A)
1. Open QFIL.
2. Change "Storage Type" to UFS.
3. Select "Flat Build".
4. Browse for "LGE SM8150 Firehose" and pick it.
5. Now, connect the phone to PC and boot into EDL mode.
6. Open "Select Port" and select the phone, press OK.
7. In "Tools" open the "Partition Manager".
B)
!!!BE CAREFUL TO DO EXACTLY AS THE INSTRUCTIONS SAY OR YOU WILL BRICK THE PHONE!!!
1. Make a backup of and erase these 7 partitions: FTM, Modem_A, Modem_B, SID_A, SID_B, OP_A, OP_B.
1.1. You have to left-click on a partition then right-click on it and select "Manage Partition Data".
1.2. In the pop-up window, you have 4 choices: I. Erase (to erase data on the partition), II. Read Data (to dump or back up the partition), III. Load Image (to restore the partition), IV. Close (to close the window).
1.3. First dump/back up the partition by choosing "Read Data" then Erase it.
2. Close the "Partition Manager" window.
3. Wait for 5 seconds then press Vol- and Power until it restarts.
3.1. Immediately after rebooting, Release the Vol- and Power buttons and press Vol+ to get into Download Mode.
Note: Do not let the phone to begin to boot! If it begins to boot, it may regenerate the SID and FTM partitions data and so you need to redo the whole step B.
C)
1. Open LGUP.
2. Pick your favorite KDZ.
3. Select "PARTITION DL".
4. Press Start. And a pop-up window will appear. In this window you can select which partitions to be flashed.
5. Here, uncheck these partitions: SID_A and SID_B. It will make it able to bypass the OPID Mismatched Error.
6. If you are in Sprint or other platforms you will get the message whether to change the model or not. Of course you know what to do =)
after completing the process it will boot up in some minutes and before starting the customization it will do one restart. just be patient.
ERRORS, QUESTIONS, TROUBLESHOOTING
1. Can I crossflash V50, V60, G8X or other LG devices using this method?
I did it on V50. Maybe it'll work on your devices maybe won't. There's one way to find out; make backup and give it a try.
2. SN is gone, zero, etc.
Restore your original FTM.
3. I can't get into recovery.
Restore the original FTM.
4. I got NT-Code error.
It's been discussed many times in the thread and some solutions have been presented (such as this one, thanks to @animo214 and this, thanks to @kt-Froggy as well as this one, thanks to @StvOchi ). However, you can ignore it if the phone got network.
Note: You need to disable verity on the phone in advance otherwise changes in cust_path_mapping.cfg won't be saved.
5. IMEI is lost, zero, null etc.
Restore LUN5 partitions. If you have no backup it should be repaired using Octopus box. Go to 16.
6. I got "permanently locked" error.
This is because of IMPL lock and you have to restore LUN5 partitions. In case of having no backup you should use Octopus box.
7. All partitions are deleted accidentally.
Follow this instructions.
8. I need to get into PDM mode.
Unzip and restore the attached PDM to FTM partition. Remember, you need to restore your FTM to get into OS.
9. Can I use another phone's LUN5 backup?
NO.
10. Can I use another phone's FTM backup?
Yes. All partitions can be restored from another phone's backup except LUN5 partitions.
11. My phone is stuck in boot-loop.
Restore the original FTM and if it doesn't help redo the whole crossflash process and use a different KDZ this time.
12. Which KDZ is the best (for any matter of use)?
I do not know.
13. Can I crossflash from any source variant to Korean variant or vice versa?
Yes it is possible but you may get error on opening stock camera application because of hardware differences. There are some methods to solve the issue which you can search and find them.
14. Can I downgrade using this method?
Yes.
15. I erased partitions (ftm, op_a, op_b, modem_a, modem_b, sid_a, sid_b) but it still does not let me to crossflash.
Redo the whole process and this time make backup of and erase these partitions too, on both sides A and B: vendor, product, system, boot and userdata. Do not make backup of userdata partition.
16. How can I write IMEI?
A) Dump modem_a and create a copy of it. Then open it in UltraISO and remove IMEIPROT files from image folder. Save and restore it in place of modem_a and modem_b partitions.
B) Make backup of FTM and then flash or restore the PDM file (attached) into your ftm partition. Restart the phone; you'll get into PDM mode.
C) Open Tutty (attached). Select "Serial" in protocol and the proper port of your phone's modem driver. Click open. To test if you have selected the proper port number type "at" and hit enter it should respond"ok". Type the code at%imei=# (replace # with your IMEI) and hit enter. It doesn't matter you get "error" or "ok" after that, just check if IMEI is written via this code at%imei=?. If IMEI is written so you'll have the right MEID and ESN too.
D) Restore the original ftm and modem_a in place of modem_a and modem_b. Restart the phone.
I've already tested this method on V30, V50 and G8. Remember, if the phone has IMPL lock it'll throw "perm. locked" error even if you have written the IMEI.
17. I have lost GPT files of my LG G8, G8X, G8S, V50, etc. and Qfil partition manager does not show anything in the list.
You need to flash GPT files to your device with fh_loader (see this, part C). For that matter use KDZ_Tools to Extract DZ from a KDZ of your device. Then extract the DZ using -c at the end of extracting command. For example: unkdz -f FILE_NAME.kdz -c. It will extract all files besides all GPTs.
18. Which are the LUN5 partitions?
SM8150 has 7 physical partitions known as LUNs which are numbered from 0 to 6. Each LUN is split into several partitions. In Qfil Partition Manager you can see all partitions except those of LUN3 and LUN6 which are hidden. The number of LUNs are shown under the first column named LUN. Therefore, all partitions in front of number 5 are LUN5 partitions.

Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^

LG K31 Crossflashing:
To crossflash LG K31 go to this guide. Thanks to @Wish39.
LG Stylo 6 Crossflashing:
To crossflash LG Stylo 6 using LG K71 Android 12 firmware see this. Thanks to @Wish39.
LG V50 Crossflashing:
I had two LG V50 (LMV450) to which I flashed Korean Andorid 12 using the method mentioned in the first post. I cannot guarantee that it will work on every V50. After corssflashing I found out that one of them had the problem of draining battery due to not getting into deep sleep mode. To overcome the issue, I reflashed it via "Chip Erase" this time, and then again reflashed it but in the same way mentioned for crossflashing in the first post. Of course, I had created backup and at the end I restored LUN5 partitions.

Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!

great, thank you

netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update

Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
You didnt follow preparation correctly I guess?

netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
What OPID does it get assigned once you boot the device? OPEN_CA?

AsItLies said:
Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!
Click to expand...
Click to collapse
Like the a11 korean one?

cloud1250000 said:
You didnt follow preparation correctly I guess?
Click to expand...
Click to collapse
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched

Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
i got the same problem, just 3 options

Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting

AsItLies said:
Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
How to make it?srry i cant understand

alright, G8x Sprint succesfully crossflashed to OPEN CA

Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
Sebastian Thiago said:
i got the same problem, just 3 options
Click to expand...
Click to collapse
Azs5165 said:
How to make it?srry i cant understand
Click to expand...
Click to collapse
Follow preparation.
cloud1250000 said:
What OPID does it get assigned once you boot the device? OPEN_CA?
Click to expand...
Click to collapse
AsItLies said:
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Azs5165 said:
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched
Click to expand...
Click to collapse
Follow the steps in part C.

netmsm said:
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Click to expand...
Click to collapse
curious how the sprint v50 will react to this.. I`ll try this guide when korean A11 gets release.. I'll let you know..
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..

cloud1250000 said:
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..
Click to expand...
Click to collapse
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.

netmsm said:
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.
Click to expand...
Click to collapse
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that

cloud1250000 said:
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that
Click to expand...
Click to collapse
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.

netmsm said:
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.
Click to expand...
Click to collapse
can you check which mcfg is used? (field test > mcfg status)

Can someone send me the backup image or bin of NVDATA,persist,proinfo,protect1,protect2, NVRAM and nvcfg?

I Flashed the stock using SP flash Tool and i don't have backup of the partition.
and now i want the file so i can edit it and paste my imei and baseband.
NVDATA, NVRAM and nvcfg
mine boots to recovery and it says unable to mount /nvdata (Permission Denied).
PLZ HELP!

chakrabortyshubham66 said:
I Flashed the stock using SP flash Tool and i don't have backup of the partition.
and now i want the file so i can edit it and paste my imei and baseband.
NVDATA, NVRAM and nvcfg
mine boots to recovery and it says unable to mount /nvdata (Permission Denied).
PLZ HELP!
Click to expand...
Click to collapse
No one will provide NVRAM or protected system data.
Is there any alternative way by which you can fix this issue?
Please PM me so that I can coordinate on this thing.

If you wiped those things without making a backup, you're fked. Those files are tailored specifically unique for every device.

bruh you want having someone else's IMEI and SN !!!!

chakrabortyshubham66 said:
I Flashed the stock using SP flash Tool and i don't have backup of the partition.
and now i want the file so i can edit it and paste my imei and baseband.
NVDATA, NVRAM and nvcfg
mine boots to recovery and it says unable to mount /nvdata (Permission Denied).
PLZ HELP!
Click to expand...
Click to collapse
try flashing older ROMs like MIUI 12.5 or 13 Global ones via SP flash tool. I were flashed my stolen Redmi 9 many times via SP and never faced issue. also make sure you have right DA and auth file among right rom