Hey guys
I am a newbie here and this is my first post here . I want to backup the efs on my galaxy core before installing the monster rom . I have searched everything on the web but didn't get anything about it.
Please I need help coz without efs backup I cant flash my rom . I have tried the efs pro but my phone wouldn't be detectable on the application.
Thanks
TWRP
You can backup EFS by Team Win Recovery Project (twrp)
Related
Hi!
i would like to know if we can recover the GN from an extSDcard, and how we do it(if it does exist)? is it only limited to sumsung Kies?
Thanks
Richie
If you have a Nandroid backup on EXt SD card it can be restored .
Guide - Installing Firmware, CWM recovery & Rooting
http://forum.xda-developers.com/showthread.php?t=2080366
Apart from that i don't understand your post .
recover the GN >>>> what do you want to recover ???
sumsung Kies?
jje
thanks
Can someone please help me on taking EFS Backup for n8000.
Thanks in advance...:angel:
vindost said:
Can someone please help me on taking EFS Backup for n8000.
Thanks in advance...:angel:
Click to expand...
Click to collapse
Install Philz recovery, you can find it in the Note 10.1 Original Dev forum and then backup efs from the custom backup menu.
TWRP Recovery backs up the EFS as well.
I made mistake and wipe system folder with twrp recovery now my tab says no os installed and is stuck on Samsung screen need help plz its a Samsung tab 3 10.1 gt-5210
If you have a Nandroid backup, restore it... Or just find a new rom you like and flash it.
Regnas said:
If you have a Nandroid backup, restore it... Or just find a new rom you like and flash it.
Click to expand...
Click to collapse
ok ty
Hi,
This is my first post on XDA, so please forgive if i miss some of the things !! So i will start with the issue i am facing. I was running Prism Barebone v14.6 on my S4 i9500, i was trying to install the Xposed Framewrok for Lollipop but somehow i missed the part where it said that "Xposed it not yet working for Samsung TW roms and you will end up in bootloop if you flash it".
So as expected i ended up in bootloop, so i tried to restore my Nandroid backup from Philz recovery. Everything went just fine in the recovery but i was again stuck in bootloop and my phone was not proceeding from Samsung logo loading screen. So i flashed the PB rom again and restored my apps and data with Titanium Backup.
Since then i am having strange issue that for some reason i am not able to restore my Nand backups even after creating the fresh nandroid backups. I was creating the Nandroid backup using "Online nandroid backup" tool; so i thought maybe the issue could be with this app(though it worked just fine on my previous rom Omega v27).
So finally i thought of creating the Nandroid backup from PhilZ recovery and the weird thing was nandroid backup creation failed at "/system" saying "Error backing up /system".
So please guys help me understand what exactly went wrong and how can i fix this. I am facing this issue from last 2 days and i have tried everything which could think of, so i need help from you Android Gurus out here !!!
Thanks in advance !!
rbhanot2 said:
Hi,
This is my first post on XDA, so please forgive if i miss some of the things !! So i will start with the issue i am facing. I was running Prism Barebone v14.6 on my S4 i9500, i was trying to install the Xposed Framewrok for Lollipop but somehow i missed the part where it said that "Xposed it not yet working for Samsung TW roms and you will end up in bootloop if you flash it".
So as expected i ended up in bootloop, so i tried to restore my Nandroid backup from Philz recovery. Everything went just fine in the recovery but i was again stuck in bootloop and my phone was not proceeding from Samsung logo loading screen. So i flashed the PB rom again and restored my apps and data with Titanium Backup.
Since then i am having strange issue that for some reason i am not able to restore my Nand backups even after creating the fresh nandroid backups. I was creating the Nandroid backup using "Online nandroid backup" tool; so i thought maybe the issue could be with this app(though it worked just fine on my previous rom Omega v27).
So finally i thought of creating the Nandroid backup from PhilZ recovery and the weird thing was nandroid backup creation failed at "/system" saying "Error backing up /system".
So please guys help me understand what exactly went wrong and how can i fix this. I am facing this issue from last 2 days and i have tried everything which could think of, so i need help from you Android Gurus out here !!!
Thanks in advance !!
Click to expand...
Click to collapse
Have you tried TWRP ? PhilZ development has been stopped, so you should think about switching someday.
I would do it like this:
-Make a nadroid backup with your custom recovery
-Perform a full wipe
-Flash latest stock firmware via ODIN
-Let the system boot up
-Flash custom recovery and check if the error persists
tried TWRP as well however i was still getting the same issue(boot up process getting stuck at samsung logo screen). Will flashing the Stock Firmware reset the recovery also to Stock recovery ?
Can anyone please reply !!
rbhanot2 said:
Can anyone please reply !!
Click to expand...
Click to collapse
Yup, stock firmware will restore everything. Flash it as i linked it earlier. Once done, perform a factory reset in stock recovery before you boot up android.
I having galaxy s4 i9505 ....I had custom GP ROM on my s4...then I backed up my ROM and flashed cm 12.1 nightly d I didn't like it....so I tryd to restore the backup...boot get restore system also...but when to restore data in does a lot then in between it showes failed....I tryed to restore my old backuped ROM but Still same error... it won't boot up if restoring data fails the ROM won't boot up.....help cuz I got all the stuff in that ROM....I ofcours have nandroid manager app so I can restore data....but I want to restore that ROM help!
Hi
Thanks for writing to us at XDA Assist. Have you tried only restoring the boot and system partitions and then using Nandroid Manager to restore the data?
No response in two days, thread closed.