Got a Note 4x Mido with twrp 3.1.1-0. Did a full backup, checked every box, and transferred it over to my laptop. Tried some custom roms and wanted to go back to my previous backed up rom. Did a wipe and transferred the backup back to my phone but when I tried to restore it EFS and Firmware were causing error, everything else worked fine, booted up the phone, no wifi, bluetooth, imei gone, provably hard to fix... Tried wiping in all kinds of ways but the EFS and firmware just don't want to be restored.
EFS throws:
Unable to find file system (first period).
Unknown restore method for '/efs2'
EDIT: Tried some different versions of twrp and it worked (only EFS)
Firmware throws:
extractTarFork() process ended with ERROR: 255
Thanks in advance for the help
Try with this procedure and let us know if it worked for you:
https://forum.xda-developers.com/showpost.php?p=73770600&postcount=12
Related
I've done everything: cleared all data, tried to restore backups, do a full charge, nothing's working.
I upgraded to 4.4.4 Liquidsmooth, but I decided to restore (with clockworkmod) back to 4.3.
I got the infamous MD5 Mismatch error, so I recreated the nandroid.md5 file, and I successfully booted back into 4.3.
Now 4.3 kept giving me errors so I turned it off and tried to restore BACK to a backup I had once I upgraded to 4.4.4, and nothing happened.
Now I'm in limbo: the phone crashes on the boot screen, and if i restore either the 4.3 or 4.4.4 backup, clockworkmod just crashes while restoring.
At this point I'd be fine with deleting EVERYTHING and starting with a fresh phone, but I don't even know how to do that...
Help would be MUCH appreciated, thanks.
Follow the guide in general forum sticky on how to wipe and flash a stick firmware with Odin. Make sure you factory reset after flashing.
Hello,
I'm a rather experienced Android user. Before I flashed my S3 for the first time, I made sure to back up my EFS. After about a year and a flash of the newest ArchiDroid version, I couldn't get any signal all of a sudden. It worked the days before, and I flashed nothing new or installed anything. I read online about what that might have caused, and it seems like the problem of a lost EFS partition was the problem. I restored my EFS, rebooted, and the phone won't turn on now. It is stuck on the flashing "SAMSUNG" logo on start-up. Thinking I did something, I tried to boot into Clockwork recovery, but it only shows the ClockworkMod logo for about a second, then it reboots again. What should I do?
Try flashing a full stock firmware with Odin, but sudden failure could be nand wear.
Thanks for the reply, I flashed stock firmware with Odin. No errors, but I'm still stuck at the flashing "SAMSUNG" logo.
Boot into recovery and factory reset.
Alright, got into recovery.
Got an error: "E:Failed to mount /efs". How do I restore my EFS with my efs.img now?
EDIT: Managed to get my phone back to work, However, still no signal. Mobile data and phoning does not work.
Format the efs partition then restore your backup, check the permissions then factory reset again.
Edit. If your efs backup was really old, ie. efs v1, then you might have to flash a firmware from before EMG4 to get the efs read, then update to 4.3.
On my Galaxy S5 (SM-G900F, Android 4.4.2) I made a nandroid backup of "everything" (boot, cache, recovery, system, etc.) about six weeks ago (using PhilzTouch recovery). Yesterday I tried to restore it, and it seemed to work but when Android had booted up I started getting force closes all over the place.
I tried wiping cache and data, but it didn't make any difference. I had a look at the log for one app when it crashed, and it was due to java.io.IOException: open failed: EACCES (Permission denied). I have not changed anything on the SD card since I did the backup (sent the phone in to repair a dead pixel but they wouldn't do it on warranty, so I got the phone back the way it was).
One idea I had was that something was messed up with the file permissions, so I tried the app "Fix permissions" but that didn't help either.
I then thought I'd try to flash Lollipop using FlashFire. Everything went well, and I was really surprised to see that now all the apps were working flawlessly! So to get back to KitKat (which is what I want), I then tried flashing the KitKat ROM (BTW, these are all official samsung ROMs from SamMobile. Now it didn't even boot properly, it got stuck on "Android is upgrading - Starting apps...". Tried wiping data/cache again but nothing worked.
I have since tried repeating the but without flashing Lollipop (i.e. flashing the same ROM as the one in the nandroid backup when running the restored KitKat installation), but it always gets stuck on the "Android is upgrading" screen (have tried many combinations of boot/preload/system/etc).
So it seems that I CAN restore the KitKat nandroid backup, but it's unusable "as is" because of most the apps force closing. However, if I flash Lollipop "on top" of the backup, everything works.
Can someone explain this, and possibly provide a solution? I'd really like to have this phone exactly as it was when I did the nandroid backup.
Hello Everybody,
first of all thanks for reading my thread.
I have a problem...tried to flash a custom kernel 2 days ago, and it went wrong. So I had to flash official fw again to come back to Xiaomi.eu then.
Before I tried to flash the kernel, I made a backup with TWRP.
My problem now is, every time I try to restore this backup, TWRP gives me an ERROR 255 when it tries to restore data partition.
Error message says something with "error create fork" or similar.
Have tried different things, also for example to wipe data before, or to format data, but nothing helps.
Device is decrypted on start of TWRP. So that is not the problem, I guess.
Anyone eventually has a clue/a tipp what I can try or what may be the problem?
Or isn't LRTWRP generally not able to restore backups?
Would be grateful for any help... ?
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
alfaholic said:
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
Click to expand...
Click to collapse
Backups and restore on the TWRP with some phone models does not work correctly either because it does not decrypt or is too old compared to the rom or you try to restore an older rom version on a more recent rom and sometimes the reverse also does not work (because of the system).
Try a more recent Twrp (just in case) but anyway the restoration will not be done with a more recent Twrp.
If you are on MIUI micloud works relatively well but obviously you can only restore the data not the system.
https://androidfilehost.com/?w=files&flid=318277
alfaholic said:
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
Click to expand...
Click to collapse
try flashing miui 12 rom first, then restore twrp back up (format data also before restoring)
and chose the latest version of twrp for android 11 or 12 (depends on your Rom)
maybe it will work