I am trying to restore my EFS partitions through ADB, does anyone know what the block names are? And what command to use to accomplish this? My images look like modemst1.img modemst2.img which were backed up with freegee
Sent from my SM-P600 using XDA Premium 4 mobile app
Hello. Please refer to this thread
Related
When I wipe using TWRP, I still have some files left over in root directory. Do I have to clean those too to get a truly clean phone? Don't those files accumulate over time?
I can see those files in the TWRP recovery's file manager. How should I delete them? Some of them do not delete manually...
---------------------------------
Sent from my Nexus 4
Fastboot erase userdata
Sent from my Nexus 4 using xda app-developers app
in TWRP there are format options for you to use
Hello everybody...
How can I do Efc backup..?
Thanks
Sent from my GT-I9500 using Tapatalk now Free
install TWRP Recovey, get in Recovery mode, choose Backup, tick EFS box, wait and done, reboot..
and then make a copy of efs on your emails, burn in CDs, save to a floppy disks, print the hex code on stone, always store in safe places...
Sent from my GT-I9500 using xda app-developers app
Hello guys ,
How do i copy the backup created using CWM to my system(laptop) ?
As i understand the latest CWM backups are stored in locations which cannot be accessed by users . Is there any other way it can be achieved ?
Also please do provide the restore procedure for the same.
On nexus 4 running stock kitkat.
CWM version : 6.0.4.3
Any help would be greatly appreciated .
they can be acesses by users, at /data/media/clockworkmod or /sdcard/clockworkmod, u can use root explorer or adb to get them.
₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢
Just plug your phone to your system(laptop) and look for the biggest by size folder. That should be your cwm backup. Also mind the name. I am not talking about /Android!!! Just copy it somewhere the regular way and then delete it. The restore is simple but you have to have it back on the same place in the phone's memory. The restore process is carried out from the recovery. GL.
Sent from my Nexus 4 using xda app-developers app
How do I take esf backup?
Thank you for your kind answers.
Sent from my Nexus 4 using xda app-developers app
pwned_me said:
How do I take esf backup?
Thank you for your kind answers.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
AFAIK this partition is an exclusive partition on Samsung devices...
Isn't it efs on Samsung?
audit13 said:
Isn't it efs on Samsung?
Click to expand...
Click to collapse
Yeah you're right! Is it a spelling error? Never heard of esf...
Nexus 4 doesn't have a efs partition.
[DEVICE : N⁴][ROM : crDROID][KERNEL : AK]
[LAUNCHER : NOVA][CARRIER : T-MOBILE][CASE : NONE]
Well my friend lost his emi and stuff when he tried to flash a ROM on Gnex , when i googled about it, he mentioned about esf thing.
Sent from my Galaxy Note II using xda app-developers app
pwned_me said:
Well my friend lost his emi and stuff when he tried to flash a ROM on Gnex , when i googled about it, he mentioned about esf thing.
Sent from my Galaxy Note II using xda app-developers app
Click to expand...
Click to collapse
If your friend is lucky few ROMs will take EFS backup in SDCard and there are tools which can restore IMEI number. If you do flash other roms then better take a backup of efs folder. using root explorer you can archive and store efs folder.
imapk said:
If your friend is lucky few ROMs will take EFS backup in SDCard and there are tools which can restore IMEI number. If you do flash other roms then better take a backup of efs folder. using root explorer you can archive and store efs folder.
Click to expand...
Click to collapse
How do I take that?
Sent from my Nexus 4 using xda app-developers app
pwned_me said:
How do I take that?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
check this post: LINK
There isn't an efs partition on nexus 4. It's a samsung thing. Galaxy nexus had it because it was made by SAMSUNG
Backing up ur ESF Partition
U need Root,Android Terminal Emulator and busy box to successfully backup your ESF Partition. Type the following codes to backup/restore the ESF partition.There is another block mmcblk0p10 which contains the m9kefs3.img however the same is blank(So backup not mandatory). The m9kefs2.img contains the IMEI information. Also kindly backup the same to ur PC / Email or Drive
Also these codes remain the Same for Android 4.4(Kitkat) & 4.2(JB). However for Android 4.3(JB) change the storage path to storage/emulated/legacy
Code:
su
dd if=/dev/block/mmcblk0p8 of=/storage/emulated/0/m9kefs1.img
dd if=/dev/block/mmcblk0p9 of=/storage/emulated/0/m9kefs2.img
Restore.
su
dd if=/storage/emulated/0/m9kefs1.img of=/dev/block/mmcblk0p8
dd if=/storage/emulated/0/m9kefs2.img of=/dev/block/mmcblk0p9
Hit the Thanks Button as a Token of Appreciation
I really didn't want to start a new thread...but...Yes I know we have a locked bootloader. However, before I go and do something stupid, presuming the boot.img is properly unpacked, are we able to edit the ramdisk at all? For example on the HD 10, if I wanted to edit default.prop, and repacked the boot.img, would it still brick the tablet if flashed through flashfire?
Just adding: I just did a backup of system using the DD command and then also backed it up as a raw system.img using flashfire. Is there a reason why there are now TWRP files and folders inside the backup folder of Flashfire? They were created when the backup was made.
Sent from my Amazon KFSUWI using XDA Labs
DragonFire1024 said:
Just adding: I just did a backup of system using the DD command and then also backed it up as a raw system.img using flashfire. Is there a reason why there are now TWRP files and folders inside the backup folder of Flashfire? They were created when the backup was made.
Sent from my Amazon KFSUWI using XDA Labs
Click to expand...
Click to collapse
Interesting...
Unoacked, edited ramdisk, repacked and flashed boot.img on an Galaxy S4. It worked, flashed, booted, but the default.prop I edited didn't hold. Not sure what I missed here, but have a slight idea. Will look at the HD 10 boot.img tomorrow and look at something I suspect might be the issue, at least for the S4
Sent from my Galaxy S4 using XDA Labs