Database Develop

[Q] Messed up the root folder(/)

I accidentally messed up the root folder(/), which contains system, cache, data, lta-label etc folders
Now how can I make the whole root folder back to the original state?
To solve this, can I flash a firmware by Flashtool with "Exclude Partition" unticked?
Will every folder and file under the root folder come back to the original state?
By the way, can lta-label folder be deleted?
Thank you!

Can you elaborate on messing up the root folder? What exactly is messed up?

DevShaft said:
Can you elaborate on messing up the root folder? What exactly is messed up?
Click to expand...
Click to collapse
I wrongly created and moved some files and folders just under the Android root folder(/)(PS not sdcard root folder)
so now the root folder has been messed up and i want to make the whole root directory go back to factory state.
thanks

....cant you just delete them?
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.

Just reflash using flashtool

flytomars said:
I wrongly created and moved some files and folders just under the Android root folder(/)(PS not sdcard root folder)
so now the root folder has been messed up and i want to make the whole root directory go back to factory state.
thanks
Click to expand...
Click to collapse
Which folders are you referring to exactly?
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
Michealtbh said:
Just reflash using flashtool
Click to expand...
Click to collapse
May not help in this case.

tangosierra_ said:
....cant you just delete them?
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.
Click to expand...
Click to collapse
after a reboot the wrongly created files and folders disappear and i don't know where they have gone
i worry that they still exist but cannot be found

DevShaft said:
Which folders are you referring to exactly?
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
May not help in this case.
Click to expand...
Click to collapse
If flashing a FTF can clear every partition then it will help

DevShaft said:
Which folders are you referring to exactly?
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
May not help in this case.
Click to expand...
Click to collapse
i wrongly copied TitaniumBackup folder just to the root folder
after a reboot it disappeared i don't know where it is

flytomars said:
If flashing a FTF can clear every partition then it will help
Click to expand...
Click to collapse
Flashing a FTF can clear most partitions, but not everything like TA. So no 100% clean slade I'm afraid. However this can solve problems such as yours.
---------- Post added at 05:37 AM ---------- Previous post was at 05:26 AM ----------
flytomars said:
i wrongly copied TitaniumBackup folder just to the root folder
after a reboot it disappeared i don't know where it is
Click to expand...
Click to collapse
I believe / is a ramdisk mounting everything together. This means that on every boot this ramdisk is recreated and all adjustments you made to / before will be gone. So your TB folder is actually nowhere, so nothing for you to worry about. It's like it was before you wrongly copied the folder. No need to flash an ftf, but if it makes you feel good .

DevShaft said:
Flashing a FTF can clear most partitions, but not everything like TA. So no 100% clean slade I'm afraid. However this can solve problems such as yours.
---------- Post added at 05:37 AM ---------- Previous post was at 05:26 AM ----------
I believe / is a ramdisk mounting everything together. This means that on every boot this ramdisk is recreated and all adjustments you made to / before will be gone. So your TB folder is actually nowhere, so nothing for you to worry about. It's like it was before you wrongly copied the folder. No need to flash an ftf, but if it makes you feel good .
Click to expand...
Click to collapse
what you said makes me stop worrying.
Besides TB folder I also wrongly copied some files just under the root folder.
I once worried that after a reboot they will not be deleted and just be hidden and be nowhere to be found so that they will permanently exist in a unknown place on my phone.
Now I know that they can be simply 'killed' by completely flashing a ftf.
So can I get a conclusion:
If the root folder is messed up, for example, saving files and folders under lta-lable folder or under any other folder in the root folder or just under the root folder(/), everything that shouldn't exist will be deleted and everything under the root folder will be back to the factory state by flashing the whole ftf.
Is this right?
Thank you!

DevShaft said:
Flashing a FTF can clear most partitions, but not everything like TA. So no 100% clean slade I'm afraid. However this can solve problems such as yours.
---------- Post added at 05:37 AM ---------- Previous post was at 05:26 AM ----------
I believe / is a ramdisk mounting everything together. This means that on every boot this ramdisk is recreated and all adjustments you made to / before will be gone. So your TB folder is actually nowhere, so nothing for you to worry about. It's like it was before you wrongly copied the folder. No need to flash an ftf, but if it makes you feel good .
Click to expand...
Click to collapse
:good:

flytomars said:
what you said makes me stop worrying.
Besides TB folder I also wrongly copied some files just under the root folder.
I once worried that after a reboot they will not be deleted and just be hidden and be nowhere to be found so that they will permanently exist in a unknown place on my phone.
Now I know that they can be simply 'killed' by completely flashing a ftf.
So can I get a conclusion:
If the root folder is messed up, for example, saving files and folders under lta-lable folder or under any other folder in the root folder or just under the root folder(/), everything that shouldn't exist will be deleted and everything under the root folder will be back to the factory state by flashing the whole ftf.
Is this right?
Thank you!
Click to expand...
Click to collapse
just reflash FTF or if you have custom rom reflash the rom in recovery...

G1_enthusiast said:
just reflash FTF or if you have custom rom reflash the rom in recovery...
Click to expand...
Click to collapse
flashing a custom rom won't format partitions so i think it's better to flash ftf

flytomars said:
flashing a custom rom won't format partitions so i think it's better to flash ftf
Click to expand...
Click to collapse
if you wipe system, data and cache it will...worth a try it takes 5 minute to know if it work..

G1_enthusiast said:
if you wipe system, data and cache it will...worth a try it takes 5 minute to know if it work..
Click to expand...
Click to collapse
i messed up the root folder /
not data, system etc which are under the root folder

flytomars said:
flashing a custom rom won't format partitions so i think it's better to flash ftf
Click to expand...
Click to collapse
Yes, only you don't have to because of the fact you wrote to ram, so nothing is messed up .
---------- Post added at 06:07 PM ---------- Previous post was at 05:57 PM ----------
flytomars said:
So can I get a conclusion:
If the root folder is messed up, for example, saving files and folders under lta-lable folder or under any other folder in the root folder or just under the root folder(/), everything that shouldn't exist will be deleted and everything under the root folder will be back to the factory state by flashing the whole ftf.
Is this right?
Thank you!
Click to expand...
Click to collapse
No, that's not right .
When you write anything to / (not further down!), it will be gone like it never existed. This is because writing to / is actually to RAM. RAM is cleared on reboot.
So conclusion is, you don't have a messed up /, since it is restored after a reboot. This is only the case when you write directly to /. So not necessarily when you write to a folder called /foo or /bar. You don't have to do anything, since there is no mess and all is fine.
A RAM disk is an area in memory which is mounted as disk, as if it is disk space while it actually is RAM space which is cleared when the device reboots or shuts down. When the device boots it recreates this RAM disk and copies the necessary files and folders to it. It also mounts certain partitions under aliases like /system and /data. When the RAM disk is removed from memory - at a shutdown or reboot - it will only clear the files and folders copied to / and the aliases of the partitions mounted, not the content of the partitions themselves. So when you write to /system/ it will not be gone at next boot while something written to / directly will. I hope it makes a bit more sense now .

DevShaft said:
Yes, only you don't have to because of the fact you wrote to ram, so nothing is messed up .
---------- Post added at 06:07 PM ---------- Previous post was at 05:57 PM ----------
No, that's not right .
When you write anything to / (not further down!), it will be gone like it never existed. This is because writing to / is actually to RAM. RAM is cleared on reboot.
So conclusion is, you don't have a messed up /, since it is restored after a reboot. This is only the case when you write directly to /. So not necessarily when you write to a folder called /foo or /bar. You don't have to do anything, since there is no mess and all is fine.
A RAM disk is an area in memory which is mounted as disk, as if it is disk space while it actually is RAM space which is cleared when the device reboots or shuts down. When the device boots it recreates this RAM disk and copies the necessary files and folders to it. It also mounts certain partitions under aliases like /system and /data. When the RAM disk is removed from memory - at a shutdown or reboot - it will only clear the files and folders copied to / and the aliases of the partitions mounted, not the content of the partitions themselves. So when you write to /system/ it will not be gone at next boot while something written to / directly will. I hope it makes a bit more sense now .
Click to expand...
Click to collapse
now i understand
and i did a test.
i created a folder and a file under / whose permissions were set the same as the permission of other files under /
after a reboot the created folder and file disappear
so i think what you said is undoubtly right
but if i write something further down then i have to flash a ftf because flashing a ftf can wipe every partition mounted under /
is this right?
thank you!

Most, not every. Partitions like TA cannot be wiped by flashing a ftf.
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.

flytomars said:
but if i write something further down then i have to flash a ftf because flashing a ftf can wipe every partition mounted under /
is this right?
thank you!
Click to expand...
Click to collapse
As said not every partition, like the TA for instance. However in most cases flashing ftf will do.

[Q] lost all files on sdcard, but still only have 15 gigs of space?

I have a 32gb locked bootloader att moto x.
I've got it rooted on 4.4 with write protection off, and i've safestrapped a rooted 4.4.2 stock rom to it.
Recently I wanted to upgrade to 4.4.3 with the Krypton rom, so I was cleaning up my sdcard at the same time to get some more space. I guess I made a mistake somewhere along the line because shortly after deleting a couple files, my sdcard came up blank and I lost all my files. The thing is, my phone still shows up with about 15gb of used space, and I know that the rom and system files themselves can't take up that much space. Furthermore, if I go in the google play music app, it's able to play certain songs that were previously on my sdcard, despite it seeming empty to me.
Is it possible the files were relocated somewhere? Kind of like what happens when the sdcard files end up in an 'emulated' folder? (it's not the case here, at least not in /sdcard)
I appreciate your time and help!

frenchie007 said:
I have a 32gb locked bootloader att moto x.
I've got it rooted on 4.4 with write protection off, and i've safestrapped a rooted 4.4.2 stock rom to it.
Recently I wanted to upgrade to 4.4.3 with the Krypton rom, so I was cleaning up my sdcard at the same time to get some more space. I guess I made a mistake somewhere along the line because shortly after deleting a couple files, my sdcard came up blank and I lost all my files. The thing is, my phone still shows up with about 15gb of used space, and I know that the rom and system files themselves can't take up that much space. Furthermore, if I go in the google play music app, it's able to play certain songs that were previously on my sdcard, despite it seeming empty to me.
Is it possible the files were relocated somewhere? Kind of like what happens when the sdcard files end up in an 'emulated' folder? (it's not the case here, at least not in /sdcard)
I appreciate your time and help!
Click to expand...
Click to collapse
Look for a folder called LOST.DIR in the emulated storage.
There are chances that your lost files are present there.This usually happens when you mount the SD card as opposed to connecting it to a PC vai MTP mode.
Do post your findings!

Bhargav4591 said:
Look for a folder called LOST.DIR in the emulated storage.
There are chances that your lost files are present there.This usually happens when you mount the SD card as opposed to connecting it to a PC vai MTP mode.
Do post your findings!
Click to expand...
Click to collapse
Unfortunately it was really wiped clean. It was done via MTP mode. Nothing other than the android folder and download folder, which were both empty.
What I don't understand is what kind of file on my sdcard could have erased all others when deleted? Could it be safestrap related? I'm quite certain the cable was nicely plugged in and didn't move.
And why is some of my music still present? :/

Pretty sure you're flash was corrupt.
I would flash 4.4 again with fastboot and as long as you don't erase anything with fast boot.... I bet all you're files turn back up.
I'm not sure what special steps, if any you need to take with safestrap and that.... But refreshing stock will likely fix it.
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
Of course you'll need to do the whole root and safestrap stuff again after.
---------- Post added at 12:29 PM ---------- Previous post was at 12:19 PM ----------
Here is a guide with a return to stock section. In fact, since you are on 4.4....correct? You could flash 4.2.2 post camera update... Not pre camera.... Cause I think you need that version to root again....
http://forum.xda-developers.com/showthread.php?t=2603358
Basically whatever you did to root and safestrap, you need to do again.

KJ said:
Pretty sure you're flash was corrupt.
I would flash 4.4 again with fastboot and as long as you don't erase anything with fast boot.... I bet all you're files turn back up.
I'm not sure what special steps, if any you need to take with safestrap and that.... But refreshing stock will likely fix it.
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
Of course you'll need to do the whole root and safestrap stuff again after.
---------- Post added at 12:29 PM ---------- Previous post was at 12:19 PM ----------
Here is a guide with a return to stock section. In fact, since you are on 4.4....correct? You could flash 4.2.2 post camera update... Not pre camera.... Cause I think you need that version to root again....
http://forum.xda-developers.com/showthread.php?t=2603358
Basically whatever you did to root and safestrap, you need to do again.
Click to expand...
Click to collapse
The thing is, I've been running this rom just fine for at least 2 months now... And I've connected it to my pc using MTP in the past and it worked without a problem, so I don't see what would be causing one now. That being said I may RSD back to post camera just to make sure, who knows maybe it will fix this. I'll probably do that tomorrow and I'll be sure to post my results. In the meantime if anyone has a less time-consuming method feel free to let me know! haha

Won't hurt to try. ?

Just a follow up: I wiped data via safestrap recovery and installed Krypton. Works fine and now my storage shows about 3 gigs of used space, so my sdcard files are lost for good. How it happened is still a mystery! All I can say is be careful what files you delete from your sdcards!

[ROM] STOCK T210R Debloated, Deodex, blah, blah, blah

Here is PIMPED Stock SM-T210R T210RUEU0CNI1 (Canada)
Features
- Highly Debloated
- Rooted
- Busybox
- Zipalign
- etc
-And an easter egg
Download link: http://www.mediafire.com/download/eg3swl50ymflxc0/PIMPED_STOCK_T210R
NOTES: For SM-T210 user flash Werewolf kernel to get it to work
Also it might take a while to install because of the compression
Delete phservice (/system/bin) to set CPU governors and I/O
And there isn't a bootanimation for quicker boot time

Bugs: You tell me

One more

What Version 4.1.2 or 4.4.2..?

Teknodad1974 said:
What Version 4.1.2 or 4.4.2..?
Click to expand...
Click to collapse
T210RUEU0CNI1 = Android 4.4.2

Link not working

svicenty said:
Link not working
Click to expand...
Click to collapse
Try again?
EDIT: Click on the link don't copy it

I think thiers something wrong with miediafire it doesn't give you Nothing to copy

svicenty said:
I think thiers something wrong with miediafire it doesn't give you Nothing to copy
Click to expand...
Click to collapse
Works for me

HerroYou said:
Here is PIMPED Stock SM-T210R T210RUEU0CNI1 (Canada)
Features
- Highly Debloated
- Rooted
- Busybox
- Zipalign
- etc
-And an easter egg
Download link: http://www.mediafire.com/download/eg3swl50ymflxc0/PIMPED_STOCK_T210R
NOTES: For SM-T210 user flash Werewolf kernel to get it to work
Also it might take a while to install because of the compression
Delete phservice (/system/bin) to set CPU governors and I/O
And there isn't a bootanimation for quicker boot time
Click to expand...
Click to collapse
I tried this and many others on my T210R with TWRP 2.7.1.0. Nothing has stuck. It's like I don't have an OS on it at all. If I reboot, it just boots into recovery, nothing else. Where did I go wrong?

gonehaywire said:
I tried this and many others on my T210R with TWRP 2.7.1.0. Nothing has stuck. It's like I don't have an OS on it at all. If I reboot, it just boots into recovery, nothing else. Where did I go wrong?
Click to expand...
Click to collapse
You are not using the latest version of your custom recovery. Update it right meow!

Screenshots?

shayind4 said:
Screenshots?
Click to expand...
Click to collapse
It is stock rom so there won't be a big difference, only a ton of apps removed

Any one else having issues saving to the external sd card? every time i try to do a TB it says I have insufficient storage space. I have like 10gb left on my card, It wont even save one thing.

bnb25 said:
Any one else having issues saving to the external sd card? every time i try to do a TB it says I have insufficient storage space. I have like 10gb left on my card, It wont even save one thing.
Click to expand...
Click to collapse
Did you tell the recovery to do a backup to your sdcard1?

HerroYou said:
Did you tell the recovery to do a backup to your sdcard1?
Click to expand...
Click to collapse
@HerroYou,
Have you changed the permisson for apps to write on the Sdcard, KK dont allow apps to write on sdcard.

bierma32 said:
@HerroYou,
Have you changed the permisson for apps to write on the Sdcard, KK dont allow apps to write on sdcard.
Click to expand...
Click to collapse
how do i do that? I use KK on other devices and haven't had this issue.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
HerroYou said:
Did you tell the recovery to do a backup to your sdcard1?
Click to expand...
Click to collapse
Recovery does a nanoid just fine. I can't get titanium backup to back up apps.

bnb25 said:
how do i do that? I use KK on other devices and haven't had this issue.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
Recovery does a nanoid just fine. I can't get titanium backup to back up apps.
Click to expand...
Click to collapse
Take a look to this thread. http://forum.xda-developers.com/showthread.php?t=2617921
Post # 10

bierma32 said:
Take a look to this thread. http://forum.xda-developers.com/showthread.php?t=2617921
Post # 10
Click to expand...
Click to collapse
Fomat your sdcard using the recovery, works for me.

Does anyone have a link for the factory boot animation? I actually like it lol.

Could someone please upload vendor.img

I have very slow internet and only need the latest vendor.img from the MOB30M OTA. Could someone please upload it for me so I don't have to download the whole 1gb OTA?
Thanks

Stylez Ray. said:
I have very slow internet and only need the latest vendor.img from the MOB30M OTA. Could someone please upload it for me so I don't have to download the whole 1gb OTA?
Thanks
Click to expand...
Click to collapse
why would you need a vendor.img? and for which phone?

simms22 said:
why would you need a vendor.img? and for which phone?
Click to expand...
Click to collapse
Well i'm not sure if my plan is correct: I am running Dirty Unicorns for a long time now but also flashed A.R.I.S.E sound systems. I wanted to get rid of the sound system completely, normally a dirty flash of the rom is enough but I just had a look at the /vendor folder and saw some files which were edited by the sound system.
So as I remember flashing the rom zip doesn't touch the /vendor partition and looking in the rom .zip looks like I am right as I only see /system and /boot images

Stylez Ray. said:
Well i'm not sure if my plan is correct: I am running Dirty Unicorns for a long time now but also flashed A.R.I.S.E sound systems. I wanted to get rid of the sound system completely, normally a dirty flash of the rom is enough but I just had a look at the /vendor folder and saw some files which were edited by the sound system.
So as I remember flashing the rom zip doesn't touch the /vendor partition and looking in the rom .zip looks like I am right as I only see /system and /boot images
Click to expand...
Click to collapse
ohh.. i see. i thought you were on a n6p or a n5x, since they need the vendor.img, and we dont. i was going to let you know, but youre on top of it
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
Stylez Ray. said:
Well i'm not sure if my plan is correct: I am running Dirty Unicorns for a long time now but also flashed A.R.I.S.E sound systems. I wanted to get rid of the sound system completely, normally a dirty flash of the rom is enough but I just had a look at the /vendor folder and saw some files which were edited by the sound system.
So as I remember flashing the rom zip doesn't touch the /vendor partition and looking in the rom .zip looks like I am right as I only see /system and /boot images
Click to expand...
Click to collapse
btw, i gave you a thanks for..
Originally Posted by morfic
Just flash over.
Only thing we wipe here is our butts.
Click to expand...
Click to collapse
i dont know why you added it, but it seems as you added it for me

simms22 said:
ohh.. i see. i thought you were on a n6p or a n5x, since they need the vendor.img, and we dont. i was going to let you know, but youre on top of it
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
btw, i gave you a thanks for..
Originally Posted by morfic
Just flash over.
Only thing we wipe here is our butts.
i dont know why you added it, but it seems as you added it for me
Click to expand...
Click to collapse
That's my signature for a long time back in the days of Trinity kernel i read this comment, but whom am I telling this

simms22 said:
ohh.. i see. i thought you were on a n6p or a n5x, since they need the vendor.img, and we dont. i was going to let you know, but youre on top of it
Click to expand...
Click to collapse
Just curious, why do those devices need a vendor.img?

ceo4eva said:
Just curious, why do those devices need a vendor.img?
Click to expand...
Click to collapse
no idea, since i dont have one. and ive not done any imvestigating either. but they do need it.

ceo4eva said:
Just curious, why do those devices need a vendor.img?
Click to expand...
Click to collapse
Its do to the way the OEM did it. One of the biggest complaints from people with the device. It is also thought that google is doing it to make things harder for custom rom users and devs and with some of the recent info about Google It wouldnt surprise me at all.

So I downloaded the whole OTA myself and had a look at it. There's no vendor.img in it...
Makes me wonder, how can I get a clean vendor partition now?!

Stylez Ray. said:
So I downloaded the whole OTA myself and had a look at it. There's no vendor.img in it...
Makes me wonder, how can I get a clean vendor partition now?!
Click to expand...
Click to collapse
The only way will be to completely flash the device with the stock files. It wipes all partitions 2hich should fix things

Stylez Ray. said:
So I downloaded the whole OTA myself and had a look at it. There's no vendor.img in it...
Makes me wonder, how can I get a clean vendor partition now?!
Click to expand...
Click to collapse
just flash a rom, maybe it builds fresh each flash?

ceo4eva said:
Just curious, why do those devices need a vendor.img?
Click to expand...
Click to collapse
simms22 said:
no idea, since i dont have one. and ive not done any imvestigating either. but they do need it.
Click to expand...
Click to collapse
We have a vendor image but it is in /system and symlink from /system/vendor to /vendor.
New Google device that have been released with L or M have now the vendor as a separate partition from system.
Why? I think it's more simple and secure for everybody.
---------- Post added at 05:21 AM ---------- Previous post was at 05:18 AM ----------
Stylez Ray. said:
So I downloaded the whole OTA myself and had a look at it. There's no vendor.img in it...
Makes me wonder, how can I get a clean vendor partition now?!
Click to expand...
Click to collapse
So no normally dirty flash your rom will wipe the vendor in n6 because it is stored in /system/vendor.
If a dirty flash doesn't work. In twrp wipe system partition then flash rom - gapps etc...
If you see a /vendor directory it's just a symlink dir like /etc or /sdcard

Dead-neM said:
We have a vendor image but it is in /system and symlink from /system/vendor to /vendor.
New Google device that have been released with L or M have now the vendor as a separate partition from system.
Why? I think it's more simple and secure for everybody.
---------- Post added at 05:21 AM ---------- Previous post was at 05:18 AM ----------
So no normally dirty flash your rom will wipe the vendor in n6 because it is stored in /system/vendor.
If a dirty flash doesn't work. In twrp wipe system partition then flash rom - gapps etc...
If you see a /vendor directory it's just a symlink dir like /etc or /sdcard
Click to expand...
Click to collapse
That's a very nice explanation, thanks!
Found out the same just as I downloaded the factory image and couldn't even see a vendor. img in there.
Dirty flashing rom does the job

Trying to restore update.zip from Titanium Backup but get errors

I have never been able to get this feature in TB work. When I try to flash the update.zip I am met with: 'Failed to map file '/sdcard/update.zip' Error installing zip file '/sdcard/update.zip'
No idea where to start with this one.
Anyone?

This may be a WAG, but worth a try.
https://www.xda-developers.com/psa-...broke-titanium-backup-substratum-heres-a-fix/

Pkt_Lnt said:
This may be a WAG, but worth a try.
https://www.xda-developers.com/psa-...broke-titanium-backup-substratum-heres-a-fix/
Click to expand...
Click to collapse
Thanks, I will check it out.

tjlmbklr said:
I have never been able to get this feature in TB work. When I try to flash the update.zip I am met with: 'Failed to map file '/sdcard/update.zip' Error installing zip file '/sdcard/update.zip'
No idea where to start with this one.
Anyone?
Click to expand...
Click to collapse
That feature hasn't worked since eclair... The script is borked and no one uses it

rignfool said:
That feature hasn't worked since eclair... The script is borked and no one uses it
Click to expand...
Click to collapse
Good to know. Thanks.

I'm making some tests now. It seems TWRP only flashes zips with at least 2GB of space. I'm thinking about divide the backup in two zips of apps and a data zip. i think it will work.
---------- Post added at 11:25 ---------- Previous post was at 11:15 ----------
It's official: it works! Divide your backup in zips with less than 2GB and it will work.