Hi, all
May be this is already solved, or even answered already zillion times but after doing my homework.
Owner of an axon 7 2017 model, with an external SD of 256 GB formatted FAT32 as seems this filesystem is the one chosen for the external SD (have tried exFAT but not recognised).
As the size of one of the backup files is higher than 4GB, TWRP (3.2.1.0) fails doing the backup to the SD.
Is there any solution to this problem?
Regards
I checked some of my backups on this G3. One ROM had a 9GB data.ext4.win (in Nandroid Manager) but that's just a total. The individual files are broken up into sub-2GB files.
Also on the Axon. But I was using TWRP 3.1.x.
Haven't made any backups with 3.2.x as I installed that after doing the multiboot thing.
If 3.2 is not breaking things up that's not good, IMO.
LG G3 D851, LiquidSmooth v4.1 ROM, MultiROM, Tapatalk 4.9.5
Is not. I have 6.x GB system image file not sliced, so no way to keep a backup in external SD...
Thank you for your comments.
Regards
@jrotaetxe, hello.
Did you ever figure out the deal with the backups? Finally got TWRP 3.2 for my G3 (was waiting for MultiROM-TWRP) and did a test backup. Data was 7GB. It backed up normally with the data being broken up into smaller pieces. So it doesn't seem to be a version thing.
Still not able to test on the Axon 7 due to the multiboot thing.
LG G3 D851, CyanogenMod 12.1 ROM, Fechda Kernel R7, MultiROM, Tapatalk 4.9.5
marcdw said:
@jrotaetxe, hello.
Did you ever figure out the deal with the backups? Finally got TWRP 3.2 for my G3 (was waiting for MultiROM-TWRP) and did a test backup. Data was 7GB. It backed up normally with the data being broken up into smaller pieces. So it doesn't seem to be a version thing.
Still not able to test on the Axon 7 due to the multiboot thing.
LG G3 D851, CyanogenMod 12.1 ROM, Fechda Kernel R7, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
Hi, Marc. Did not. But also did not try again,as I have enough room (so far) in the internal memory.... May happen is model-specific....
Anyway, thank you for your back up and interest. This kind of things are the enjoyable ones in these forum.
Regards
Hello @jrotaetxe, it's me again.
NFound just put out an extended/enhanced version of TWRP 3.2.
Maybe give this one a try and see if the backups work properly.
I'm running it but haven't done a backup yet.
http://forum.xda-developers.com/showthread.php?t=3591075
[Recovery 3.2.1-7 TWRP][Exclusive][the best in the world]
ZTE Axon 7 A2017U, SL!M4 DF!NR B09 ROM, Multiboot, Tapatalk 4.9.5
marcdw said:
Hello @jrotaetxe, it's me again.
NFound just put out an extended/enhanced version of TWRP 3.2.
Maybe give this one a try and see if the backups work properly.
I'm running it but haven't done a backup yet.
http://forum.xda-developers.com/showthread.php?t=3591075
[Recovery 3.2.1-7 TWRP][Exclusive][the best in the world]
ZTE Axon 7 A2017U, SL!M4 DF!NR B09 ROM, Multiboot, Tapatalk 4.9.5
Click to expand...
Click to collapse
Hey, Marc. Thank you sooooooo much.
TWRP 3.2.1-7
I installed TWRP 3.2.1-7 over 3.2.1-5 version, and ran backup.
I can confirm this version does not split files, system_image.emmc.win is 6 gigs.
Running ZTE Axon 7 A2017G, SL!M4 DF!NR B09 ROM
Ugh, bummer.
ZTE Axon 7 A2017U, Stock B32, Tapatalk 4.9.5
Hm, yes, you're right. I never noticed this because I back up to a USB-C flash drive formatted to exFAT, but sure enough, the system_image backup is one big 6 GB file, which is not supposed to happen.
Is system image even necessary? I just backup boot,system and data. Never backedup system image because of this problem....
Related
I saw the cm website had a new cm13 nightly for angler, so I decided to try it out, so I downloaded it and gapps, and rebooted into twrp, then I wiped everything besides for internal storage and then I proceeded to Install cm, it took a few minutes, and then when it was done I rebooted. The first sign of something weird was that after the regular your device can't be checked for corruption message it went black and then said that my device is corrupt in red letters, then it started the cm boot animation, I waited about 5 minutes and nothing happened so I rebooted into recovery and it asked me for an encryption password... My device was not previously encrypted and I didn't require a password to Install cm, so I tried wiping everything besides for internal storage, and then I was about to flash again, but non of my files were there so I had nothing to flash.... So I rebooted into my bootloader and fastbooted stock and now I'm on stock, but all my files and backups are gone. I guess that's why it's good to have an external sd, because that never got wiped by installing a rom before, and if I would have one, I would have all my pictures, music, and app backups. But now I have to start from scratch all because I tried a new build cyanogen mod
This is your fault not CM. You said you were on a rom that was unencrypted. CM roms default to encrypt so that is how you lost your data. You should have done research before you installed as CM with the start of LP ships encrypted.
CM ROMs usually encrypt the data partition which may explain your loss?
coldconfession13 said:
This is your fault not CM. You said you were on a rom that was unencrypted. CM roms default to encrypt so that is how you lost your data. You should have done research before you installed as CM with the start of LP ships encrypted.
Click to expand...
Click to collapse
So if I'm unencrypted and I Install an encrypted rom I lose the data partition?
Yes, you would have had to flash cm13 then a kernel that supports unencrypted storage then boot
coldconfession13 said:
Yes, you would have had to flash cm13 then a kernel that supports unencrypted storage then boot
Click to expand...
Click to collapse
Well I always flashed elementalX after flashing any roms but Its for aosp... I never had a nexus before and I guess I didn't know enough about encryption.
Yea it's one of those trial and error kind of deals. It sucks. That corruption error is because you need to flash the vendor.img file in fastboot. I believe we have a twrp one available as well but that link is buried in the chroma rom thread.
---------- Post added at 10:05 AM ---------- Previous post was at 10:01 AM ----------
https://androidfilehost.com/?fid=24269982086996393
You can flash that in twrp to get that corruption. But that could be the unlocked bootloader message which nobody has found to get rid of yet
coldconfession13 said:
Yea it's one of those trial and error kind of deals. It sucks. That corruption error is because you need to flash the vendor.img file in fastboot. I believe we have a twrp one available as well but that link is buried in the chroma rom thread.
---------- Post added at 10:05 AM ---------- Previous post was at 10:01 AM ----------
https://androidfilehost.com/?fid=24269982086996393
You can flash that in twrp to get that corruption. But that could be the unlocked bootloader message which nobody has found to get rid of yet
Click to expand...
Click to collapse
So its different than the stock vendor.img that come with the factory build?
I saw two messages one about that it can't check for corruption and that I always see, and another that my device is corrupted and that was a first.
I think that second one is also kernel related. I remember Leankernel saying the corruption and then he fixed it and now its just the bootloader one.
coldconfession13 said:
I think that second one is also kernel related. I remember Leankernel saying the corruption and then he fixed it and now its just the bootloader one.
Click to expand...
Click to collapse
What I mean is that I had already flashed the vendor.img that came with the mdb08m build using fastboot
Then I believe you are experiencing that kernel error. They have to change some settings in the default kernel in cm13 to get rid of that error. If you flash leankernel it should get rid of that one.
aryehzev said:
.....[cut] So I rebooted into my bootloader and fastbooted stock and now I'm on stock, but all my files and backups are gone.
Click to expand...
Click to collapse
If you used the flash-all helper script to reinstall stock, it will wipe all internal storage (if you look at the script contents, that's what the "-w" does).
I know it's a bit late now but I'd recommend always copying backups off the device when making major changes.
sam3000 said:
If you used the flash-all helper script to reinstall stock, it will wipe all internal storage (if you look at the script contents, that's what the "-w" does).
I know it's a bit late now but I'd recommend always copying backups off the device when making major changes.
Click to expand...
Click to collapse
I did not use flashall I flash everything individually. (system,boot,cache,vendor)
Guys I'm a liitle late to the party on this convo but I'm in a similar but different situation. I installed the latest temasek 11/29 ROM. Was previously on purenexus. After installing the ROM and gapps I restarted the system and got a message that my phone can't be trusted. The phone then went on to encrypt itself. Booted fine so I just wanted to see if I could still access twrp and if all my internal storage was OK. Good on both accounts. So my question is do I have to decrypt before switching ROMs say back to purenex or can I boot to recovery and just wipe cache,dalvik, sys and data and flash whatever rom I want?
Sent from my Nexus 6P using Tapatalk
jeff5347 said:
Guys I'm a liitle late to the party on this convo but I'm in a similar but different situation. I installed the latest temasek 11/29 ROM. Was previously on purenexus. After installing the ROM and gapps I restarted the system and got a message that my phone can't be trusted. The phone then went on to encrypt itself. Booted fine so I just wanted to see if I could still access twrp and if all my internal storage was OK. Good on both accounts. So my question is do I have to decrypt before switching ROMs say back to purenex or can I boot to recovery and just wipe cache,dalvik, sys and data and flash whatever rom I want?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No you never have to unencrypt
How are you guys even booting? I keep getting stuck at the Google logo on reboot.
akellar said:
No you never have to unencrypt
Click to expand...
Click to collapse
That I didn't know.
Sent from my Nexus 6P using Tapatalk
The last time I tried MIUI 7 on my G2, everything worked well but my signal kept dropping and picking back up. Right now, I am on
Cloudy G2 3.3
Bootstack: vs980 39a
From here, what steps do I take to install MIUI 7 without any issues? I'm a huge fan of the MIUI software and have no idea how to install it
Thanks in advance!
TheSkilledPlaya said:
The last time I tried MIUI 7 on my G2, everything worked well but my signal kept dropping and picking back up. Right now, I am on
Cloudy G2 3.3
Bootstack: vs980 39a
From here, what steps do I take to install MIUI 7 without any issues? I'm a huge fan of the MIUI software and have no idea how to install it
Thanks in advance!
Click to expand...
Click to collapse
You would flash it like you would any other rom:
1. Download the ROM.
2. Copy the file to your internal or external SD Card
3. Reboot into recovery and perform a nandroid backup (or your backup of choice)
4. In recovery, wipe data (perform a full wipe)
5. Browse to where you saved the files and Install the ROM
6. Reboot your phone & enjoy it!
You have to keep in mind that all custom/modified roms are experimental at best, so if it doesn't work as it should, you should move onto something else. Also, most of the custom roms are made around the gsm variants to if you're using the cmda variants such as vs980 and ls980 you would be better off using stock(or stock based if you must) roms. I know you want to use miui but it's simply not optimized for the vs980 so you will never get the same performance/stability.
stan54 said:
You would flash it like you would any other rom:
1. Download the ROM.
2. Copy the file to your internal or external SD Card
3. Reboot into recovery and perform a nandroid backup (or your backup of choice)
4. In recovery, wipe data (perform a full wipe)
5. Browse to where you saved the files and Install the ROM
6. Reboot your phone & enjoy it!
You have to keep in mind that all custom/modified roms are experimental at best, so if it doesn't work as it should, you should move onto something else. Also, most of the custom roms are made around the gsm variants to if you're using the cmda variants such as vs980 and ls980 you would be better off using stock(or stock based if you must) roms. I know you want to use miui but it's simply not optimized for the vs980 so you will never get the same performance/stability.
Click to expand...
Click to collapse
Thanks for the help, yeah.. many ROMs have issues with VS980 :\
Hi
Is it possible to partition the 64gb memory such that my data is retained after every new rom installation?
I came from note 2 and was very confident when formatting the mobile as i can take the sd card out before doing any experiments, but on Nexus 6P i have lost data 3 times as the rom. Was encrypted and custom recovery doesn't enter without formatting user data.
If partitioning is possible please help me.
Sent from my Nexus 6P using XDA-Developers mobile app
You do know if you remove the security pin/finger print that twrp will be able to backup and restore data?
If I'm not mistaken they've also released a new twrp that allows decryption.
Keep in mind that ROMs of different bases may not boot without wiping. Quite honestly since Google's restore function has gotten better I haven't had the need to keep data. Everything from my home screen layout to my app data gets restored after a flash.
Sent from my Nexus 6P using Tapatalk
I really didn't know that. Need to try it. Its been one week without root. First time ever. Its really hard.
Sent from my Nexus 6P using XDA-Developers mobile app
Is the answer 'NO' to the partitioning of internal memory?
Sent from my Nexus 6P using XDA-Developers mobile app
superchilpil said:
You do know if you remove the security pin/finger print that twrp will be able to backup and restore data?
Click to expand...
Click to collapse
I removed all security but TWRP doesnt work. stuck at Splash.
firoz3321 said:
I removed all security but TWRP doesnt work. stuck at Splash.
Click to expand...
Click to collapse
How are you producing this issue? What is your setup? This sounds like you're either using an older version of TWRP or N developer preview. For N Developer Previews, you must be and stay decrypted to use TWRP. Format userdata then install a modified boot.img to remain decrypted. The stock boot forces encryption.
Sent from my Nexus 5X using Tapatalk
superchilpil said:
You do know if you remove the security pin/finger print that twrp will be able to backup and restore data?
If I'm not mistaken they've also released a new twrp that allows decryption.
Keep in mind that ROMs of different bases may not boot without wiping. Quite honestly since Google's restore function has gotten better I haven't had the need to keep data. Everything from my home screen layout to my app data gets restored after a flash.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
SlimSnoopOS said:
How are you producing this issue? What is your setup? This sounds like you're either using an older version of TWRP or N developer preview. For N Developer Previews, you must be and stay decrypted to use TWRP. Format userdata then install a modified boot.img to remain decrypted. The stock boot forces encryption.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I am using latest TWRP (version 3.x.x.x) with N Preview 3. Diasbled all securities.
rebooted into bootloader and installed TWRP, rebooted to Recovery. Stuck at splash.
Took backup of internal memory and installed modified Boot and now working fine.
taking a backup and restoring takes hours for some reason.
firoz3321 said:
I am using latest TWRP (version 3.x.x.x) with N Preview 3. Diasbled all securities.
rebooted into bootloader and installed TWRP, rebooted to Recovery. Stuck at splash.
Took backup of internal memory and installed modified Boot and now working fine.
taking a backup and restoring takes hours for some reason.
Click to expand...
Click to collapse
Ok. To flash a Marshmallow rom, I believe you need to just flash the matching OS' vendor.img before booting into the Marshmallow rom. Make sure to do your factory reset and system wipe like usual.
If you intend to use N previews each month, you'll likely have to stay decrypted. I do not see a reason for the TWRP team to officially support Android N until it's official release.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Ok. To flash a Marshmallow rom, I believe you need to just flash the matching OS' vendor.img before booting into the Marshmallow rom. Make sure to do your factory reset and system wipe like usual.
If you intend to use N previews each month, you'll likely have to stay decrypted. I do not see a reason for the TWRP team to officially support Android N until it's official release.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I am not blaming anyone. but was only curious if partitioning internal memory was possible. I remember changing the partition tables on Nexus One.
firoz3321 said:
I am not blaming anyone. but was only curious if partitioning internal memory was possible. I remember changing the partition tables on Nexus One.
Click to expand...
Click to collapse
Oh, I wasn't implying that. Hope you don't take it that way. I just meant, if you plan on using N previews, unfortunately this scenario is not likely to change. Just wanted to help you resolve your issue with encryption, TWRP, and switching between Android MM/N.
I don't know about partitioning but maybe it is possible? Maybe someone else can chime with their experience?
Sent from my Nexus 5X using Tapatalk
Hello guys,
i have a simple question, is it possibile to flash official MIUI using our custom TWRP recovery?
will i lose TWRP recovery if i flash official MIUI ?
thanks
You can only flash official MIUI roms again in flashboot mode
thomasginn said:
You can only flash official MIUI roms again in flashboot mode
Click to expand...
Click to collapse
I think you actually can roll-back to MIUI normaly
I also would like to know this, i believe you can flash through TWRP but i'm not sure and i would like someone to confirm this because i need to do it today and i don't have a windows system to recover it with ease if something fails.
Thanks.
I flashed miui rom zips on twrp
Sent from my Redmi 4 using XDA-Developers Legacy app
qaz.xc said:
I also would like to know this, i believe you can flash through TWRP but i'm not sure and i would like someone to confirm this because i need to do it today and i don't have a windows system to recover it with ease if something fails.
Thanks.
Click to expand...
Click to collapse
It's possible but you need to disable dm-verity in twrp (or flash lazyflasher) else it will not boot, and it will wipe your internal storage partition during installation so make sure to backup your data and place your rom in microsd rather than internal storage.
I think you better use xiaomi.eu rom rather than official, since it easier and not wiping your internal storage during installation.
Just flashed the official ROM through TWRP, disabled verify in the options just in case, threw some mount errors but installed correctly.
I just did it and it works fine.
I am currently using the oreo roms(lineage,aicp and etc..), but I would like to get back to the stock based twrp roms like genesys and the other ones. The problem is that when I flash them via twrp, the phone boots and shows an error: encryption unsuccessful.
rdlegy said:
I am currently using the oreo roms(lineage,aicp and etc..), but I would like to get back to the stock based twrp roms like genesys and the other ones. The problem is that when I flash them via twrp, the phone boots and shows an error: encryption unsuccessful.
Click to expand...
Click to collapse
Hi,
you need to format data via twrp.
Sent from my LEX722 using Tapatalk
Johndays01 said:
Hi,
you need to format data via twrp.
Sent from my LEX722 using Tapatalk
Click to expand...
Click to collapse
Thanks it worked
Just as a sub question, how to avoid encryption on Oreo ROMs?
you cant, the latest twrp the one with 3 2.1.1 encrypts the phone and it can be used only on oreo. if you want to go back to nougat or less you have to wipe all internal storage with all in one tool.
Remember abt backing up all photos, videos or your personal files in internal storage.