I'm "cloning" 200 Jiayu G3 (MediaTek) Android devices for a non-profit organization working in Africa. I make a nandroid backup via CWM of one G3 device and then restore it to the other 200 devices, however the NVRAM/IMEI info (wifi/bluetooth MAC addresses + IMEI #) get cloned as well. Is there way to remove the NVRAM/IMEI data from the Nandroid backup so the device specific identifiers are retained on the other phones? MTKDroid Tools restore process is laborious and it seems the guys who post ROMs are able to prevent overwriting the unique identifiers...
Help on this would be much appreciated!
Is my question not clear enough, or is it a stupid question? Really struggling to find an answer... it seems absurd that there would be no way to retain the unique identifiers other than restoring them via MTKDroid Tools... perhaps someone has written a script to retain the unique identifiers? Or moved them out of the data partition?
Related
probably a stupid question but is safe to restore a CWM rom backup from one S3 to another S3?
presuming there might be some slight hardware component differences between phones depending on the batch, would the rom from one work on another one or are they strictly exclusive?
thanks
It will work.
However I'm not sure if it includes an EFS backup, so just to be sure backup that folder first for the target phone and check the IMEI afterwards.
Since IMEI transplantation is illegal and brings a lot of technical issues (such as being refused from the network)
Hi XDA's,
I know there have been many threads about IMEIs with 0049.... My situation is a little different though.
My phone was soft bricked whilst flashing ROM's. When I restored it I found that the base band was unknown and the IMEI was 0049.... A common problem after reading up on a number of threads.
Where my situation is different though is that after flashing back to old stock(from what I read a common solution to the problem) I am able to use my phone however my IMEI is still 0049.... and not what is on the back of the phone. Additional info - even when the moden was corrupted I could always use my WIFI and BT.
I know that it is possible to edit IMEI through a terminal su function and have already tried it with no success.
Could someone check my code or offer constructive advice on how I can fix this as I would like to learn how to correct this issue. I would like to have the correct IMEI for my phone displayed in the software? I originally bought this phone under contract with Vodafone when the S2 first came out and have all my papers.
Thanks.
Without a good EFS backup, your chances of fixing this are close to zero. By all means try the stuff in threads here which claim to be able to restore/recover it from nothing, you may luck out if it's one of those cases where the IMEI 'disappears' temporarily for whatever reason (flashing some roms seems to cause this, hence the advice to try going back to stock in the first instance).
But more than likely it's a service centre or local mobile repair shop job.
Thanks, I have been able to find a copy of an EFS backup in my /sdcard however I did not intentionally create it - one of the ROMs I flashed seemed to have made it.
I'm not experienced but as far as I understand my EFS is working - I just need to edit the IMEI.
Currently I can boot and make\receive phone calls however the IMEI is showing 0049.... not what is displayed under the battery(3590*******).
No. You do not need to 'edit the IMEI' or anything of the sort (which is impossible without specialist equipment regardless of what some thread might say). If you've got a generic IMEI, it's because the EFS files are corrupt/broken. Your EFS is not 'fine'.
You need to restore the EFS backup that was fortunately made by whatever kernel you flashed (which you should have done manually yourself as soon as you rooted your phone). Use an app like Hellcat's kTool (or others) to restore the backup (there's a thread on here devoted to the app/that process; search).
Most carriers block phones with generic IMEI's in civilised parts of the world (Tier one carriers at least; some MVNO's may not), if you don't fix this problem you will more than likely find yourself without connectivity at some point soon.
MistahBungle said:
No. You do not need to 'edit the IMEI' or anything of the sort (which is impossible without specialist equipment regardless of what some thread might say). If you've got a generic IMEI, it's because the EFS files are corrupt/broken. Your EFS is not 'fine'.
You need to restore the EFS backup that was fortunately made by whatever kernel you flashed (which you should have done manually yourself as soon as you rooted your phone). Use an app like Hellcat's kTool (or others) to restore the backup (there's a thread on here devoted to the app/that process; search).
Most carriers block phones with generic IMEI's in civilised parts of the world, if you don't fix this problem you will more than likely find yourself without connectivity at some point soon.
Click to expand...
Click to collapse
Thanks, already tried k-tool but I was not able to find the backup with k-tool only create a new one and restore that new one. I will read the k-tool thread to get a better understanding of how to work the app. Probably just need to copy & paste the old EFS to some folder.
Yep the copy/paste thing has been known to work sometimes so definitely try that. Also (though I've never used it), some people swear by EFS Pro for fixing these things. If you do manage to fix it, make sure you keep a copy of that EFS backup somewhere safe (keep one copy on your PC & back that up, keep another other copy on the external SD card in your phone if you have one).
I try to update 3.000sp, received a 8705 error; I had replacing the boot, recovery, system partition. I can not phone, with QPST amend the wrong parameters can anyone give me a complete system backup, it is best to include all partitions, it is best to tell the specific methods;. I was able to carry out simple commands to operate. Who can provide a mobile phone qpst the NV file backup? Please give me help! Or can anyone tell me the phone's NV data in that partition, how backup and recovery? Thank you!
I'm trying to update too.. No luck same code error.. But I think the problem is the update looks for specific apps (bloatware) that I uninstalled when I rooted it.. Sorry I'm not much help in just looking for the same system backup you are.. But more specifically the DEVICE/SYSTEM/APP folder from a stock device...
Hi all, I would like to know if LG devices have the same problem with corrupted data on EFS folder/partition, and if so therefore lose the IMEI by a bad flashing getting a corrupted imei.
So, if LG devices have the same problem as Samsung ones, which apps are the best to backing up those files? Maybe using Terminal Emulator (dd if=/dev/block/......)? Also, I wanted to tried the following apps on Android, but I never have done any backup with them, until now.:
- FlashFire (this give me more confidence)
- EFS Backup
- Partitions Backup & Restore
- EFS Professional Tool (for PC)
My device: LG K10 (k420) - ROOTED with locked bootloader (if possible, I don't want to unlock it).
Nobody know?
I'd like to help out a fellow xda user who requested a stock flashable ZIP, meaning a TWRP backup of the stock clean system.
However, I'd like to make sure no identifying information is in the backup before sharing it, including
IMEI
MAC addresses
Any other device IDs unique to my device
Keys
System logs
NFC data and logs
Wifi passwords and list of Wifis found during the last scan(s)
Personal data (e.g. photos) - though from what I read those aren't backed up anyway
Old deleted data
How can I make sure (and ideally verify) the backup doesn't contain this information?