Database Info

[Q] Unable to backup in TWRP 2.6.3.0

Hi,
I unlocked and installed TWRP recovery yesterday, and then I flashed CM10.2. All went without problems.
Now I tried to make a backup from within TWRP (2.6.3.0), but it always ends with an error;
Backing up System is fine.
Backing up Data is fine.
But, when Backing up Boot...it ends with the error:
E:Backup file size for '/data/media/0/TWRP...........
I'm 100% sure I installed the correct recovery (-4,2-version)
I also see this on the terminal screen in TWRP:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
Any ideas?

realgreef said:
Hi,
I unlocked and installed TWRP recovery yesterday, and then I flashed CM10.2. All went without problems.
Now I tried to make a backup from within TWRP (2.6.3.0), but it always ends with an error;
Backing up System is fine.
Backing up Data is fine.
But, when Backing up Boot...it ends with the error:
E:Backup file size for '/data/media/0/TWRP...........
I'm 100% sure I installed the correct recovery (-4,2-version)
I also see this on the terminal screen in TWRP:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
Any ideas?
Click to expand...
Click to collapse
I always have gotten those last two error and I thought the latest TWRP was supposed to have fixed them.
Make sure you have the correct filesystems mounted before starting the backup and you have enough space free on them.

I'm having a similar issue but with restoring any backups. The "boot" partition fails the recovery, but if I choose to restore the other three positions (system cache and data) it goes through.
In "mount" the only options are system (default unchecked), cache, data, Micro SDcard, and SD-Ext (unchecked).
Even with all checked (except sd-ext, which is not able to be checked) /boot partition size is not found.. twrp 2.6.3.0 was on grimlock cm10.2 and got bootloop tried flashing, wiping caches.
I flashed cm 10.2 over the partial restore and got it to work. Flashed twrp again, but the boot and recovery errors remained, thinking of going down to 2.6.1.0, maybe.
Anyone have a solution or idea?

DaringDomino3s said:
I'm having a similar issue but with restoring any backups. The "boot" partition fails the recovery, but if I choose to restore the other three positions (system cache and data) it goes through.
In "mount" the only options are system (default unchecked), cache, data, Micro SDcard, and SD-Ext (unchecked).
Even with all checked (except sd-ext, which is not able to be checked) /boot partition size is not found.. twrp 2.6.3.0 was on grimlock cm10.2 and got bootloop tried flashing, wiping caches.
I flashed cm 10.2 over the partial restore and got it to work. Flashed twrp again, but the boot and recovery errors remained, thinking of going down to 2.6.1.0, maybe.
Anyone have a solution or idea?
Click to expand...
Click to collapse
Instead of restoring the boot partition, you could flash the target ROM to the the boot partition you want and the restore the data and cache and system.

I am having this problem on my tf300t with twrp 2.6.3.0 running cm-10.2. Is there a more recent version that fixes this for this unit?
Also, with 2.6.3.0 (if there is no tf300t upgrade) can I install cm-11?

kmoffat said:
I am having this problem on my tf300t with twrp 2.6.3.0 running cm-10.2. Is there a more recent version that fixes this for this unit?
Also, with 2.6.3.0 (if there is no tf300t upgrade) can I install cm-11?
Click to expand...
Click to collapse
Unofficial twrp 2.6.3.2 has this fixed and can install cm11. 2.6.3.0 will not work with kitkat ROMs; look in scannos omnirom thread for the twrp download.
Sent from my GS3 on AOSB 4.4.2 using Tapatalk 4

fixed backup problem
I saw a post elsewhere that has fixed my backup problem. Uncheck data, run backup (success) then recheck data, run backup (success!)
Thought to share.
QUOTE:
Walter DeMoss
• 22 days ago
−
I have asus tf300t with twrp 2.6.3.0-4.2 and cm10.2 stable. All works well but backup fails every time. Backup of system and data seems to go well and generate the MD5 sum. But then immediately it fails.
Have tried backing up to internal and external. Same every time. What am I doing wrong?
Thanks in advance.
•
Reply
•
Share ›
Avatar
Jason Lenz Walter DeMoss
• 9 days ago
−
I was having the same issue trying to backup the stock rom and it was driving me crazy. When I went to backup and left the default partitions selected (System and Data checked with Cache unchecked) it tried to backup three partitions!? It looks like the third partition it was trying to backup was the Boot partition and it was getting some sort of zero file size error at the end of the backup process. I'm not sure why it was trying to backup Boot. Anyway I retried backup only checking the "System" partition, and it correctly backed up only 1 partition. I then tried again selecting System and Data (same as what showed up with the original default) and this time it correctly backed up two partitions. Must have been some leftover spurious setting that was correctly updated when I started manually selecting the partitions. Hope that helps.
1
•
Reply
•
Share ›
Avatar
Walter DeMoss Jason Lenz
• 9 days ago
−
Jason,
Thanks, that was exactly it. Well done.
Walt
UNQUOTE
---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------
http://teamw.in/project/twrp2/97

ebildude123 said:
Unofficial twrp 2.6.3.2 has this fixed and can install cm11. 2.6.3.0 will not work with kitkat ROMs; look in scannos omnirom thread for the twrp download.
Click to expand...
Click to collapse
Sorry, pretty new... So, I would need to flash this using fastboot? but the format is different when I unzip it. I see a "recovery.img" file in the unzipped folder, along with a META-INF folder containing files. Do I just use fastboot to flash the "recovery.img" file? Do I need to move this to a folder containing fastboot files? Should I rename it to twrp-2.6.3.2?
Also, to revert I would need to flash 2.6.3.0 first?
Thanks again!

kmoffat said:
Sorry, pretty new... So, I would need to flash this using fastboot? but the format is different when I unzip it. I see a "recovery.img" file in the unzipped folder, along with a META-INF folder containing files. Do I just use fastboot to flash the "recovery.img" file? Do I need to move this to a folder containing fastboot files? Should I rename it to twrp-2.6.3.2?
Also, to revert I would need to flash 2.6.3.0 first?
Thanks again!
Click to expand...
Click to collapse
You flash the img file via fastboot or you can flash the zip file in an older version of TWRP, both assuming your bootloader is up to date. To flash old JB ROM, reflash 2.6.3.0 TWRP.

Thanks! (no thanks button in tapatalk....)
Sent from my TF300T using Tapatalk

kmoffat said:
Thanks! (no thanks button in tapatalk....)
Click to expand...
Click to collapse
There is!
Just select the post by touching it, then use the thumb-up icon on the top-right of the screen.
Sent from my TF300T using Tapatalk

Error updating CM13, and others.

Hi, i have the next versions:
CyanogenMod: 13.0-20161004-NIGHTLY-osprey
Kernel: 3.10.49-MPI24.107-56-g09ff0d1
And when trying to install the 1009-NIGHTLY update i get an error without a log in the cianogenmod recovery. When I try to "Apply update" and then "Choose from emulated", it shows the next message:
"E:failed to mount /data (Invalid argument)
Installation aborted"
Then, i go to see the recovery logs, but it blanks and shows the main menu again.
Why do I want to update to the latest version, having 5 days of difference with the installed version?
Because I'm having repeatedly bugs with the Firefox browser, can't update Telegram, can't connect via Bluetooth to the most of the devices, can't update the binaries of SuperSU, and other minor errors.
Which could be the cause of some of this problems?
Sorry for my poor english, Saludos!

Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.

Henriquefeira said:
Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.
Click to expand...
Click to collapse
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?

Gonzon said:
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?
Click to expand...
Click to collapse
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you

Just as a side question, did anyone got AICP nightlies .zip stuck at extracting image to /system? I tried clean install (wipe /system, /data, /cache and dalvik) but its just stuck there. Tried multiple nightlies. Tried deleting Android and .android_secure folders in both external and internal storage. I haven't tried wiping internal storage yet (I will do it ASAP). Any tips will be great. Thanks
Broadcasted from Zeta Reticuli

Henriquefeira said:
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you
Click to expand...
Click to collapse
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Code:
[email protected]:~$ fastboot -p xxxxxxxxxx flash /data/media /home/imperial/Android2/cmupdater/cm-13.0-20161009-NIGHTLY-osprey.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 91972855 is not a multiple of the block size 4096
fastboot: /build/android-tools-hIu7Bj/android-tools-4.2.2+git20130529/core/libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Abortado
Do you know what it means?

Gonzon said:
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Do you know what it means?
Click to expand...
Click to collapse
You can't flash the zip of a ROM via fastboot, follow this tutorial >goo.gl/JfRzZu and on the next time avoid installing the CM bundled recovery

Solved.
I flashed vía fastboot a stable twrp, then after a lot of errors and strange things i was able to flash the ROM.
Thanks a lot for your help.
I was seeing a bricked phone already jajaja.

Gapps install

I have downloaded Gapps pico. When I try to install error: Not enough space in System partition. Any remedy other than deleting apps?
John

technodino said:
I have downloaded Gapps pico. When I try to install error: Not enough space in System partition. Any remedy other than deleting apps?
John
Click to expand...
Click to collapse
Are you doing a full TWRP wipe before flashing the ZIPs?
Start Page TWRP> [WIPE]> [FORMAT DATA]> type YES press Blue CHECK in bottom right. - NP

No. I will format data & see what happens.
Thanks
John

I formatted Data and then changed to f2fs format. I received the same error: Insufficient storage space in System partition. I used TWRP 2.8.6.0. to format and to try to flash.
When I format Data should all my Apps get removed? All my apps are still present after format and changing to f2fs.
Anyway still stumped and would appreciate any help.
Thanks
John

technodino said:
I formatted Data and then changed to f2fs format. I received the same error: Insufficient storage space in System partition. I used TWRP 2.8.6.0. to format and to try to flash.
When I format Data should all my Apps get removed? All my apps are still present after format and changing to f2fs.
Anyway still stumped and would appreciate any help.
Thanks
John
Click to expand...
Click to collapse
Update the TWRP to 2.8.7.4 found here;
https://androidfilehost.com/?fid=24352994023705510
And yes all you apps should be gone you might also try a factory reset before you format data, circled int the pic. - NP

Thanks for your help.
All is working. Reflashed TWRP (latest 3.2 version and the TWRP app). Factory wipe, formatted data and then changed to f2fs format (all with TWRP). Installed KitKass 7.2.1 and gapps pico. Configured network and browser. Setup app did not work; kept shutting down so I installed system from my nandroid.
:highfive:
John
Nektopoli said:
Update the TWRP to 2.8.7.4 found here;
https://androidfilehost.com/?fid=24352994023705510
And yes all you apps should be gone you might also try a factory reset before you format data, circled int the pic. - NP
Click to expand...
Click to collapse

MiNote3 Unable to mount data

Basically I screw up last night, trying to flash a file that was not supposed to work on minote 3, android 7.
After some tries(flashing pixel experience and appearing the encrypted phone), I was able to flash miuiPro 8.9.20.
The phone works perfectly, but I have some errors, that I need some help:
-when I go to twrp, there is 0 zips in folder, I' can't find them anywhere
-basically when I try to flash magisk, it appears Installation failed
-I can't repair data, error: failed to mount /data
Thanks for all the help I receive.

Try mounting /data manually or format data.

Hi, try to flash fastboot rom with MiFlash and then flash the rom you want.

omercicek43 said:
Try mounting /data manually or format data.
Click to expand...
Click to collapse
thanks for your response.
I already formated my data
what do u mean by: format manually?

Wistake said:
thanks for your response.
I already formated my data
what do u mean by: format manually?
Click to expand...
Click to collapse
I didn't say something like that. I said try mounting data manually.

Unable to mount data TWRP

Hello guys
so I was using TWRP Recovery for years and everything worked fine, till I installed lightrom, after the installation I wanted to flash a zip file it said unable to mount storage and failed to mount /data
So I formated data rebooted in recovery and it worked for the first time after a reboot in the system, the error came again. I tried to change file system from ext4 to ext2 and back to ext4 and it worked but after a reboot it was failing again, I tried to flash no-verity-opt-encrypt-6.0 and it was failing after a reboot as well. This is making me so much troubles. Does anybody has a fix on it I would be very thankful.

Sharky45 said:
Hello guys
so I was using TWRP Recovery for years and everything worked fine, till I installed lightrom, after the installation I wanted to flash a zip file it said unable to mount storage and failed to mount /data
So I formated data rebooted in recovery and it worked for the first time after a reboot in the system, the error came again. I tried to change file system from ext4 to ext2 and back to ext4 and it worked but after a reboot it was failing again, I tried to flash no-verity-opt-encrypt-6.0 and it was failing after a reboot as well. This is making me so much troubles. Does anybody has a fix on it I would be very
You need twrp with quota management
Click to expand...
Click to collapse

cooltt said:
Sharky45 said:
Hello guys
so I was using TWRP Recovery for years and everything worked fine, till I installed lightrom, after the installation I wanted to flash a zip file it said unable to mount storage and failed to mount /data
So I formated data rebooted in recovery and it worked for the first time after a reboot in the system, the error came again. I tried to change file system from ext4 to ext2 and back to ext4 and it worked but after a reboot it was failing again, I tried to flash no-verity-opt-encrypt-6.0 and it was failing after a reboot as well. This is making me so much troubles. Does anybody has a fix on it I would be very
You need twrp with quota management
Click to expand...
Click to collapse
I solved the problem with the twrp from Tkkg1994
Click to expand...
Click to collapse