Hello guys,
I installed the latest Oreo firmware via odin and then installed TWRP, been using the phone for a while but I couldn't use twrp because data couldn't be mounted so I took a backup with twrp and then formatted data so the data was mounted and restarted the phone and it started up normally then I went back into twrp and the data became unmounted again and when I try to restore the backup it completes 100% and the phone restarts and nothing is restored, Can anybody help me with what should I do to be able to restore the backup?
Related
Hi guys,
I have LG G2 nd i have backed up my whole data using TWRP
and i have copied the data to my PC and deleted them from my mobile
and after that i deleted all the data on the phone by mistake
so
i have my backup on my PC but i can't copy it to my phone to restore it
i can only open the TWRP recovery
please tell me how can i copy the data to my Phone
thanks
U only have 1 solution since mounting storage in twrp doesnt work u can use the method here http://forum.xda-developers.com/showthread.php?t=2432476 by flashing stock kdz via the lg flash tool then after booting the rom u can root it again install recovery the put ur backup on the phone again and restore it.
Hi experts,
I would very much appreciate some help regarding the following:
I have a Samsung Galaxy S5 SM-G900F with factory installed stock rom G900FXXU1BPA2 (Android 5.0). I used the SkipSoft Unified Android Toolkit 1.4.5 to root the phone and install TWRP recovery (2.7.1.0-klte as recommended by Unified Android Toolkit). I made a first Nandroid Backup and was able to successfully restore this backup (I restored boot, system and data to verify that Nandroid restore works). I then used Titanium Backup to restore my apps from another phone, and all was well.
A week or so later I wanted to modify something I wasn't sure I wanted to keep (using apktool). I therefore made a second Nandroid backup and then proceeded to make modifications to the phone. After I saw the result, I didn't like it, and therefore restored the second Nandroid backup. After rebooting, the phone gave a flurry of forced stops ("Unfortunately XXX has stopped"). It is not a bootloop but I can't do anything meaningful with the phone other than restart it.
To try and resolve this, I used TWRP to wipe cache and dalvik cache and rebooted. The phone went through the lengthy "Android is upgrading" process but the result was the same: all my apps force stop.
I then decided to try and restore the original first Nandroid backup (which I had been able to restore successfully earlier), and this resulted in the same issue. Since I have several backups of this first backup I was able to verify that the files were good. Also did MD5 checksum verification in TWRP and it all checked out.
Using Odin, I was able to restore a stock ROM from SamMobile (G900FXXU1BOL1_G900FOJK1BOL1_ILO) and after restart, the phone works as usual, but of course all my apps and data were gone.
I was then able to use TWRP to restore only boot and system from the second backup, so I would be back on the exact same ROM that my phone came with, and this worked just fine; the phone started as if factory restored.
I then used TWRP to restore only data, and this resulted again in the same problem: all apps force close. Note that this is a restore of data only to the same phone running the exact same ROM that the Nandroid backup was made on, and it still did not work.
I have been thinking about this issue and searching through the various forums but I did not find anyone having this same exact issue. Here are some questions I came up with:
1. Is TWRP 2.7.1.0 completely compatible with this phone and with Android 5.0? Would it help if I installed a newer version of TWRP? Would I be able to restore Nandroid backups made with TWRP 2.7.1.0 with TWRP 3.X?
2. Assuming my second Nandroid backup is not corrupt, is there a better (less intrusive) restore I can do of the apps? Can Titanium Backup read TWRP 2.7.1.0 backups and restore them, including SMS?
3. What could be the reason for TWRP 2.7.1.0 restore not to be working properly? I did activate the fingerprint reader after the first Nandroid Backup, but if that is the issue I would have expected that first backup (in which fingerprints were not yet enabled) to restore properly and it doesn't.
Would appreciate any help!
Thanks,
AH
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
https://dl.twrp.me/klte/
Flash .tar version with ODIN 3.10.7
TiBu can read Nandroid backups and restore apps yes
Not sure about SMS
The method you used to root and flash TWRP is not a usual method used here, most of us use ODIN to flash TWRP and then flash SuperSU from recovery
or use CF Auto Root to root, and then flash TWRP with ODIN
I'd flash stock again, factory reset, and then flash TWRP and SuperSU, then try restoring your apps with TiBu
*Detection* said:
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
dl.twrp.me/klte
Flash .tar version with ODIN 3.10.7
Click to expand...
Click to collapse
Thanks *Detection*! I installed TWRP 3.0.0.0 as per your instructions and restored just data. Same result as before.
Then I used TWRP 3.0.0.0 to restore the entire backup including system, boot, recovery, and data. Same result (of course I lost TWRP 3.0.0.0 and was back on TWRP 2.7.1.0).
This exercise was useful for one reason: I now know that TWRP 3.0.0.0 is able to read Nandroid backups from TWRP 2.7.1.0.
This is quite crazy but I seem to be unable to restore a full Nandroid backup and get a working system.
Am going to try Titanium Backup.
Thanks again!
AH
My international Glalaxy Note 3 just started boot looping. When I turned it on first thing today. Yesterday it was functioning fine.
I removed the battery for 30 seconds still nothing. I booted into recovery, (TWRP) and wiped cache still nothing. So I backed up my phone to an External SDCard, and wiped data still nothing.
So I erased the whole device except recovery, and restored from the backup to try, and retrieve some essential files. Before reinstalling a fresh. The issue is when I go to the internal sdcard on storage it shows as empty with only a TWRP visible. I did get a notification that supersu was not installed. When rebooting the phone after wiping it. But I selected for twrp to install it so it should be there.
I have also tried to recover the data via looking at the backup on my computer but the backup is in a non human readable format.
Any idea how to get the data I need out of the phone or from the backup before I reinstall the OS?
What twrp you are using? Try reflash the twrp recovery to see if the twrp backup still there? Before you wipe did u wipe internal storage too?
Sent from my SM-N930F using Tapatalk
fastfibre said:
My international Glalaxy Note 3 just started boot looping. When I turned it on first thing today. Yesterday it was functioning fine.
I removed the battery for 30 seconds still nothing. I booted into recovery, (TWRP) and wiped cache still nothing. So I backed up my phone to an External SDCard, and wiped data still nothing.
So I erased the whole device except recovery, and restored from the backup to try, and retrieve some essential files. Before reinstalling a fresh. The issue is when I go to the internal sdcard on storage it shows as empty with only a TWRP visible. I did get a notification that supersu was not installed. When rebooting the phone after wiping it. But I selected for twrp to install it so it should be there.
I have also tried to recover the data via looking at the backup on my computer but the backup is in a non human readable format.
Any idea how to get the data I need out of the phone or from the backup before I reinstall the OS?
Click to expand...
Click to collapse
You said you wiped evrything.. So it includes Internal storage too right! And TWRP automatically creates the folder evrytime you boot into it.. If want the data from your External storage, try taking the card out and copy it or use MTP with TWRP. Then flash your fresh Rom.
Sent from my Xiaomi Mi 5 using XDA Labs
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
fred06007 said:
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
Click to expand...
Click to collapse
Corrupted backup maybe?
A long time ago I made a backup of stock and was able to go back and forth with no issues. You can try and go back to stock, root again and try another back up.
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
fred06007 said:
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
Click to expand...
Click to collapse
It happens sometimes, I had an SD card with a bad sector so every time I would make a back up it would get corrupted if I deleted the back up. I ended up leaving the backup so it will no longer write on the bad sectors.
fred06007 said:
Where is my mistake ? Could someone give me an advice ?
Click to expand...
Click to collapse
I think, you have to flash or restore the right kernel.
Which partitions have you backed up?
Sorry for the late response, the backup includes in my mind system, data and boot partition because the backup consit's of the following files:
boot.emmc.win
boot.emmc.win.sha2
data.ext4.win
data.ext4.win.sha2
data.info
recovery.log
system.ext4.win000
system.ext4.win000.sha2
system.ext4.win001
system.ext4.win001.sha2
system.info
Hello,
when I try to restore my TWRP backup of Lineage 17 on my Samsung Galaxy A5 2016 I run into the
extractTarFork() process ended with ERROR: 255​issue, and have tried several methods which I have found when googling for fixes, but none has worked so far.
This is what I've tried:
- unmount the data partition before restoring backup
- just restore system, data and boot, tick off the others
- wiped data/system/cache, flashed rom+gapps, flashed backup with all sections activated (radio, system, data,...)
- wiped data/system/cache, flashed rom+gapps, flashed backup with only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, wiped dalvik/cache after, flashed backup w/ only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, reboot, clicking next on every configuration screen, reboot to recovery, restore only data from backup
The issue seems to always occur at the same point in the process, in the progress bar its either at ca 45% or 58%, depending on if only data or everything is supposed to be restored. Restoring everything _BUT_ the data partition works, but the stuff I need to access is the data.
Kind regards
Hello,
I managed to fully restore the backup follwing this guide
Now my phone boots up to the point right after the Lineage logo is shown, where it says "starting the phone" and would probably ask for sim pin if I had a sim card in it. Then it reboots and does the whole thing again.
Does anyone have an idea how to fix this?
Kind regards