I'm not able to create backup of Stock ROM through TWRP. The error says "Failed to mount /system". While in the Mount menu, the "system" is unmounted by default. When I select "Mount system partition read only" option, I'm able to mount it. And the size of the system is shown abnormally large(check SS).
Any solution for this? And can anyone explain what that "Mount system partition read only" option meant for? Will there be any risk if I create backup keeping mount system partition read only?
Kailash Choudhary said:
I'm not able to create backup of Stock ROM through TWRP. The error says "Failed to mount /system". While in the Mount menu, the "system" is unmounted by default. When I select "Mount system partition read only" option, I'm able to mount it. And the size of the system is shown abnormally large(check SS).
Any solution for this? And can anyone explain what that "Mount system partition read only" option meant for? Will there be any risk if I create backup keeping mount system partition read only?
Click to expand...
Click to collapse
I am betting your device is encrypted. If that is the case backups will not work.
zelendel said:
I am betting your device is encrypted. If that is the case backups will not work.
Click to expand...
Click to collapse
It's not encrypted. I always remove all the passwords before creating a nandroid backup.
Kailash Choudhary said:
It's not encrypted. I always remove all the passwords before creating a nandroid backup.
Click to expand...
Click to collapse
Removing passwords doesnt encrypt the device. That happens on the very first boot. unecrypting the device wipes it.
To be honest I wouldnt worry about it too much. Even when backed up stock roms dont like to be restored and people that do normally just end up flashing the stock os due to the issues that popup.
zelendel said:
Removing passwords doesnt encrypt the device. That happens on the very first boot. unecrypting the device wipes it.
To be honest I wouldnt worry about it too much. Even when backed up stock roms dont like to be restored and people that do normally just end up flashing the stock os due to the issues that popup.
Click to expand...
Click to collapse
Do you mean removing passwords do not decrypt the device?
Do you know what that option "Mount system partition read only" is meant for? What changes will it make to my backup when I restore it in future.
Kailash Choudhary said:
Do you mean removing passwords do not decrypt the device?
Do you know what that option "Mount system partition read only" is meant for? What changes will it make to my backup when I restore it in future.
Click to expand...
Click to collapse
Yes that is exactly what I mean. That just means That the system is read only. It cant be modified. Too be honest I gave up on backing up my device years ago due to restores never going well and having to reflash full stock anyway
So now you've to flash stock ROM and start as a fresh device everytime when you want to revert back?
Actually this issue wasn't there before zlendel. I've created a backup 1½ month ago. Then I've flashed a custom ROM, didn't liked it so I restored the backup. Since then, I haven't did any modifications to the device.
Kailash Choudhary said:
So now you've to flash stock ROM and start as a fresh device everytime when you want to revert back?
Actually this issue wasn't there before zlendel. I've created a backup 1½ month ago. Then I've flashed a custom ROM, didn't liked it so I restored the backup. Since then, I haven't did any modifications to the device.
Click to expand...
Click to collapse
I always flash a pure clean flash. Mostly because dirty flashing always causes issues.
What rom did you flash? Not all roms are made some same.
zelendel said:
I always flash a pure clean flash. Mostly because dirty flashing always causes issues.
What rom did you flash? Not all roms are made some same.
Click to expand...
Click to collapse
zelendel I'm on OOS 4.1.6, trying to create it's backup. I wanted to flash Paranoid Android after creating the backup.
Kailash Choudhary said:
zelendel I'm on OOS 4.1.6, trying to create it's backup. I wanted to flash Paranoid Android after creating the backup.
Click to expand...
Click to collapse
At this point I am not sure. I dont use either and never have. If I recall right You will have to change the file system to ext4 for PA which will wipe your device. I could be wrong.
I would ask in the OOS thread.
I do a clean install everytime. At any rom. Never have any problems, conflicts.
I notice problems with restoring twrp backup, made, like 2 hours ago..
Kailash Choudhary said:
zelendel I'm on OOS 4.1.6, trying to create it's backup. I wanted to flash Paranoid Android after creating the backup.
Click to expand...
Click to collapse
It's not mandatory to change the file system to ext4 for AOSPA, but it works better rather than on f2fs and they aren't supporting possible problems on f2fs.
Also, If you're going to flash AOSPA, I suggest a clean flash to avoid possible problems with battery drain or other bugs that have been reported in that thread.
Cheers!
dugi9991 said:
It's not mandatory to change the file system to ext4 for AOSPA, but it works better rather than on f2fs and they aren't supporting possible problems on f2fs.
Also, If you're going to flash AOSPA, I suggest a clean flash to avoid possible problems with battery drain or other bugs that have been reported in that thread.
Cheers!
Click to expand...
Click to collapse
Yeah, I did a clean flash. IDK which file system it is. Battery life has improved a bit and no heating issues. Gaming performance have improved a lot.
what version of TWRP are u using? having complete Stock OS should not cause issues, i have never decrypted my device and no issues backing up, also u may not want to back up every single thing, try doing it without the System Image, i would just back up System, Data, and Boot, maybe EFS too but i don't
Suggests that there is an error in the /system partition. Have you modified the system partition? If not, you don't really need a back up of it.
Related
So this started happening last night, after i wanted to make a backup of a rom it said it failed and couldnt mount the /data and then it asked me to type a passwrod to decrypt storage data....i have never had a password enabled for that and nothing i do can get past that unless i format my data completely.... i did that last night, lost all my data but it worked so whatever! however, today i try to do the same thing, make a backup to flash a new rom and backup failed and here we are again! DOes anyone know what is going on? Or how to set the damn password myself?? I dont wanna keep doing this! HELP!
Simer03 said:
So this started happening last night, after i wanted to make a backup of a rom it said it failed and couldnt mount the /data and then it asked me to type a passwrod to decrypt storage data....i have never had a password enabled for that and nothing i do can get past that unless i format my data completely.... i did that last night, lost all my data but it worked so whatever! however, today i try to do the same thing, make a backup to flash a new rom and backup failed and here we are again! DOes anyone know what is going on? I dont wanna keep doing this! HELP!
Click to expand...
Click to collapse
More info required. What are you flashing? (ROM)
This sounds similar to the RUU Google Play Edition which changes the partition sizes. When you try to flash a sense rom it sees the partition sizes have changed an assumes it is unauthorised so brings up the password to decrypt message. - this is a security measure. It doesn't matter that you haven't set a password up.
This method works to avoid the decrypt storage message.
http://forum.xda-developers.com/showthread.php?t=2733523
grentuu said:
More info required. What are you flashing? (ROM)
This sounds similar to the RUU Google Play Edition which changes the partition sizes. When you try to flash a sense rom it sees the partition sizes have changed an assumes it is unauthorised so brings up the password to decrypt message. - this is a security measure. It doesn't matter that you haven't set a password up.
This method works to avoid the decrypt storage message.
http://forum.xda-developers.com/showthread.php?t=2733523
Click to expand...
Click to collapse
so for more details, last night i was on Philz recovery, i was on ARHD 5.0 and i simply wanted to go from that to Liquid Smooth, an aosp rom, and bam, thats when it started happening and so i thought it was the recovery img, so i am using TWRP now.....but today, i tried going from Liquid to Slim rom, but before i could make a backup it said it couldnt mount the data which is weird because i had literally just backed up my apps with Titanium backup onto my internal storage....
will your method work permanently? Even going from a aosp to aosp?
Simer03 said:
so for more details, last night i was on Philz recovery, i was on ARHD 5.0 and i simply wanted to go from that to Liquid Smooth, an aosp rom, and bam, thats when it started happening and so i thought it was the recovery img, so i am using TWRP now.....but today, i tried going from Liquid to Slim rom, but before i could make a backup it said it couldnt mount the data which is weird because i had literally just backed up my apps with Titanium backup onto my internal storage....
will your method work permanently? Even going from a aosp to aosp?
Click to expand...
Click to collapse
The key part is the stock recovery wipe as this resets the partition info. From there you can restore what you want
grentuu said:
The key part is the stock recovery wipe as this resets the partition info. From there you can restore what you want
Click to expand...
Click to collapse
i formatted the internal storage via TWRP, it seems to work but could it be an app doing it, do you think? im just baffled as to why it happened twice in the past 12 hours
I'm having this problem too.
I was using Philz touch recovery to restore my stock nandroid to see if the location issues I was having was device or CM11 specific. I got the /data message the OP posted, but did not think anything of it as I did not really care about any data as the device was virtually untouched from purchase.
I am not able to boot into fastboot or recovery. Adb does not see the device. When I boot it connected to my PC via usb I can see this for a short period before the window closes on it's own.
View attachment 2917354
Device is Verizon branded
[UPDATE]A friend pointed out that if you use the stock "Close apps and reboot" option it is a slower boot. Once you select that hold power and volume down and you can get into fastboot. From there I was able to get into recovery and reflash CM11. Can not get my stock nandroid to work though.
I also have a problem
impossible:
1 - unlock bootloader
2 - enter to stock recovery
3 - install ruu
what to do ?? how to revive the phone ??
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!
From reading the dev forums it seems no one else has been able to do so either. Does anyone know what the heck is going on? Is there any toggle (like compression?) that we cant use?
This is a bit of a pain but not the end of the world. Certainly makes me hesitate to mess around with new roms though if I cant go back to my solid daily without having to start from scratch.
khanam said:
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!
From reading the dev forums it seems no one else has been able to do so either. Does anyone know what the heck is going on? Is there any toggle (like compression?) that we cant use?
This is a bit of a pain but not the end of the world. Certainly makes me hesitate to mess around with new roms though if I cant go back to my solid daily without having to start from scratch.
Click to expand...
Click to collapse
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
Thats true - I did read about that. And that would definitely explain being unable to restore a kitkat rom.
However, I cant even restore a lollipop backup after flashing a different lollipop rom! Even if they are both derived from the same FOB6 base! That is what is even more confusing. Try it - backup, wipe all the partitions except int and ext sd of course and then try to restore... it just doesnt work!
Way I dit it just use factory reset only don't wipe anything specialy internal storage and don't use format. While restoring TWRP formats partition that been restored. I'm using TWRP 2.7.2.0
I've had no problem restoring from a TWRP Backup on Lollipop numerous times.
najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
I noticed that in every folder in /data/app/ there is an apk called base and a folder lib, can i backup just the apk? Or when i need to share an apk or take an apk i need to take also rhe lib?
dugryce said:
I've had no problem restoring from a TWRP Backup on Lollipop numerous times.
Click to expand...
Click to collapse
What is your TWRP version? Also, did you do any wipes before you fully restored a backup?
khanam said:
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!.
Click to expand...
Click to collapse
Does yours ever end up losing touch screen sensitivity when you restore a backup? Mine always looks like it has fully restored everything, but then no response to screen taps.
senozlu1 said:
Way I dit it just use factory reset only don't wipe anything specialy internal storage and don't use format. While restoring TWRP formats partition that been restored. I'm using TWRP 2.7.2.0
Click to expand...
Click to collapse
Oh I'll try this and report back. Thanks
Sent from my SM-N900T using XDA Free mobile app
yummymango said:
What is your TWRP version? Also, did you do any wipes before you fully restored a backup?
Does yours ever end up losing touch screen sensitivity when you restore a backup? Mine always looks like it has fully restored everything, but then no response to screen taps.
Click to expand...
Click to collapse
Mine just fails. But then again I've been wiping the partitions before restoring. Maybe that impacts it?
Sent from my SM-N900T using XDA Free mobile app
khanam said:
Mine just fails. But then again I've been wiping the partitions before restoring. Maybe that impacts it?
Click to expand...
Click to collapse
One of the devs, who runs the Lollipop ROM I've been using, warned against restoring data. He suggested backing up apps + data through Titanium Backup instead. Maybe it depends on the ROM?
najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
Hi
I have a rooted S4 running Carbon. Im using TWRP 2.8.5.0 and can backup and restore any
KK rom with no issues. I can flash Lollipop and backup but it will not restore this backup.
Its says restore successful but then just boots back into recovery. If someone could resolve
this it would be great
Hello all,
TB doesn't seem to pick up the apk file when backing up which is quite frustrating. Does anyone have a solution?
i had backup using TWRP 2.8.7.0 my stock TW lollipop rom...Now i had flashed Dirty Unicorns v9.5...If i wanted to goto stock rom that nandroid backup wont work??? thats what people are complaining over here??
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?
ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?
Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.
Hello HTC 10 users! I just got this device and thoroughly enjoying the speed and features. I got it s-off, Lees v2.41 rom loaded and using the team viper pnp balanced. Before installing the pnp I wanted to make a backup since I haven't done one since I got the 10. I noticed my data backup is 25GB. I don't even have 4GB used up by the internal space on the 10. In comparison my old m8 ARHD v53.1 backup is around 6GB , that rom was lolipop and using TWRP 3. Can anyone shed some light on this?
revoltech said:
Hello HTC 10 users! I just got this device and thoroughly enjoying the speed and features. I got it s-off, Lees v2.41 rom loaded and using the team viper pnp balanced. Before installing the pnp I wanted to make a backup since I haven't done one since I got the 10. I noticed my data backup is 25GB. I don't even have 4GB used up by the internal space on the 10. In comparison my old m8 ARHD v53.1 backup is around 6GB , that rom was lolipop and using TWRP 3. Can anyone shed some light on this?
Click to expand...
Click to collapse
Are you sure you are using the latest twrp?
i've not even unlocked yet, but that smells to me like it's looking at an encrypted partition, which it should be, but i can't speak to whether or not that's normal (assuming not). may try posting this ? in the TWRP thread.
That's a huge backup, roughly double the size of a typical backup for me (12.59GB, including boot, data, & system). What all are you choosing to backup when you make a backup?
Sent from my HTC 10
dangle79 said:
i've not even unlocked yet, but that smells to me like it's looking at an encrypted partition, which it should be, but i can't speak to whether or not that's normal (assuming not). may try posting this ? in the TWRP thread.
Click to expand...
Click to collapse
I forgot my startup is encrypted. I kept on hitting cancel before I mounted the partition found on the s-off youtube tutorial. Thanks for letting me know.
The Data only part is 25gb?
My Backups are normaly 8gb, in TWRP 3.0.2-5
3.7gb System Image
around 4.5gb User Data
64mb Boot and 64mb Recovery
Did you activate compression in the TWRP settings?
revoltech said:
Hello HTC 10 users! I just got this device and thoroughly enjoying the speed and features. I got it s-off, Lees v2.41 rom loaded and using the team viper pnp balanced. Before installing the pnp I wanted to make a backup since I haven't done one since I got the 10. I noticed my data backup is 25GB. I don't even have 4GB used up by the internal space on the 10. In comparison my old m8 ARHD v53.1 backup is around 6GB , that rom was lolipop and using TWRP 3. Can anyone shed some light on this?
Click to expand...
Click to collapse
You are using a really old version of twrp. Please use the latest, which is 3.0.2-6.
Magnum_Enforcer said:
That's a huge backup, roughly double the size of a typical backup for me (12.59GB, including boot, data, & system). What all are you choosing to backup when you make a backup?
Sent from my HTC 10
Click to expand...
Click to collapse
What are you suppose to chose in your back-up? I back-up system, system image, data, and boot. Is that a correct back-up?
Sorry for the noob question as I am new to HTC.
mamdroid said:
What are you suppose to chose in your back-up? I back-up system, system image, data, and boot. Is that a correct back-up?
Sorry for the noob question as I am new to HTC.
Click to expand...
Click to collapse
Boot, data, and system is all I ever backup.
Sent from my HTC 10
jollywhitefoot said:
You are using a really old version of twrp. Please use the latest, which is 3.0.2-6.
Click to expand...
Click to collapse
Yes because that was on my HTC One m8. I'm on the latest version on the HTC 10. I already figured it out that the backups were copying the full encrypted data partition if I didn't enter the password.
revoltech said:
Yes because that was on my HTC One m8. I'm on the latest version on the HTC 10. I already figured it out that the backups were copying the full encrypted data partition if I didn't enter the password.
Click to expand...
Click to collapse
That makes sense. Starting with 3.0.2-4 TWRP has been able to decrypt data partition. I missed the part where you said you were hitting cancel on the pin prompt.
Is there an option in twrp that allows me to switch between encrypted and decrypted data partitions?
LakesideWiseman said:
Is there an option in twrp that allows me to switch between encrypted and decrypted data partitions?
Click to expand...
Click to collapse
That's controlled by your rom. Natively, Android M requires encrypted data partition, but some custom ROMs allow you to use un-encrypted data. I believe that there is also a script that you can flash in TWRP to allow stock rom to be un-encrypted, but you'll have to fish around in the ROM/Development section for that.
To decrypt your data partition, you have to flash a rom that supports un-encrypted data (or the zip file I mentioned above) and then format (NOT WIPE) data partition in TWRP.
mamdroid said:
What are you suppose to chose in your back-up? I back-up system, system image, data, and boot. Is that a correct back-up?
Sorry for the noob question as I am new to HTC.
Click to expand...
Click to collapse
System and System Image are the same.
For Custom ROM's System is fine, if you want to take OTAs on Stock ROM you need a System Image.
I almost never backup Data as every app should have a Cloud Save feature and i prefer to wipe my phone every few months to get rid of stuff i never use.
Mainly before flashing a Custom ROM or playing around i backup UserData aswell.
And yeah, always backup Boot when you backup System, only takes 64MB so doesn't really matter.
jollywhitefoot said:
That's controlled by your rom. Natively, Android M requires encrypted data partition, but some custom ROMs allow you to use un-encrypted data. I believe that there is also a script that you can flash in TWRP to allow stock rom to be un-encrypted, but you'll have to fish around in the ROM/Development section for that.
To decrypt your data partition, you have to flash a rom that supports un-encrypted data (or the zip file I mentioned above) and then format (NOT WIPE) data partition in TWRP.
Click to expand...
Click to collapse
Makes perfect sense. I'm running stock debloated Verizon ROM.
Magnum_Enforcer said:
Boot, data, and system is all I ever backup.
Sent from my HTC 10
Click to expand...
Click to collapse
Haldi4803 said:
System and System Image are the same.
For Custom ROM's System is fine, if you want to take OTAs on Stock ROM you need a System Image.
I almost never backup Data as every app should have a Cloud Save feature and i prefer to wipe my phone every few months to get rid of stuff i never use.
Mainly before flashing a Custom ROM or playing around i backup UserData aswell.
And yeah, always backup Boot when you backup System, only takes 64MB so doesn't really matter.
Click to expand...
Click to collapse
Thank you to both you, I appreciate the responses. I kinda figured I was doing it wrong by the time and size of the back-up's. Thanks again fellas!!
I was thinking about changing ROMs due to problems with the camera, But, what do I have to backup in TWRP? I've seen a lot of videos and I've done a lot of research and they all say different things, I just want to backup everything I need if I have problems installing another rom (Like the IMEI is at 0 or does not start or things of that type), and not saving all apps / photos. What do I select and what not?
FranGAMER321 said:
I was thinking about changing ROMs due to problems with the camera, But, what do I have to backup in TWRP? I've seen a lot of videos and I've done a lot of research and they all say different things, I just want to backup everything I need if I have problems installing another rom (Like the IMEI is at 0 or does not start or things of that type), and not saving all apps / photos. What do I select and what not?
Click to expand...
Click to collapse
You should backup everything except Data, Internal Storage and Vendor.
FranGAMER321 said:
I was thinking about changing ROMs due to problems with the camera, But, what do I have to backup in TWRP? I've seen a lot of videos and I've done a lot of research and they all say different things, I just want to backup everything I need if I have problems installing another rom (Like the IMEI is at 0 or does not start or things of that type), and not saving all apps / photos. What do I select and what not?
Click to expand...
Click to collapse
System - backs up current rom
Boot - backs up current roms kernel
Data - backs up current roms app data (do not restore on different rom)
Efi/persist - backs up imei/modem
If you want to restore from a different rom format data first to avoid extracttar errors (probably would only happen if encrypted) reboot back to recovery then you can restore everything back to how it was when the backups were made
TheFixItMan said:
System - backs up current rom
Boot - backs up current roms kernel
Data - backs up current roms app data (do not restore on different rom)
Efi/persist - backs up imei/modem
If you want to restore from a different rom format data first to avoid extracttar errors (probably would only happen if encrypted) reboot back to recovery then you can restore everything back to how it was when the backups were made
Click to expand...
Click to collapse
I did not find any option for EFI / Persist, what I need to do?
FranGAMER321 said:
I did not find any option for EFI / Persist, what I need to do?
Click to expand...
Click to collapse
Make sure you are using the latest official twrp 3.4.0-1
It maybe displayed as modem
TheFixItMan said:
Make sure you are using the latest official twrp 3.4.0-1
It maybe displayed as modem
Click to expand...
Click to collapse
How do I update TWRP? I have version 3.2.3-0, I need 64 bit version
FranGAMER321 said:
How do I update TWRP? I have version 3.2.3-0, I need 64 bit version
Click to expand...
Click to collapse
The same way you installed the version you have
Read official twrp thread in dev section