Database Info

Can't backup sd-ext even though I partitioned it correctly.

Hi,
I used ROM Manager Premium v5.0.1.5 to partition my sd card and linked the apps with link2sd which worked just fine.
Problem is, when I wanted to backup the system ROM Manager didn't recognize my partition.
Why would that happen since I used ROM Manager itself to create the partition in the first place?
Doesn't make much sense that the app creates it and then can't backup it at all.
Can anyone shed some light on this issue?
Thanks!

Used EASEUS Partition Manager and it actually showed the partition as OTHER so I formatted it into EXT3. Still no luck mounting it through ROM Manager.
EDIT: Flashed CWM Recovery v.5.0.2.0 and after partitioning the sd card again it now mounts/backups it correctly. You can get it from: http://forum.xda-developers.com/showthread.php?t=1523050
EDIT: The earlier version of CWM doesn't work either. Flashed AmunRa recovery and it seems to work now.

i think its prblm with the clockwork mod recovery. instead of usng it try amonra recovery(flash amonra recovery and dnt use rom manager for this)

clockworkmod told me sd-ext backup is not supported on my device...
when i cleared my sdcard partition and did a backup it backed up sd-ext also.
i believe i just had not enough space on my sdcard..? may fix your problem

[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

[Q] Error restoring data from all backups in CWM Recovery

Hello I am having a problem with restoring backups from clockworkmod recovery. I am using Philz Touch recovery based on cwm 6.0.4.5. I was also having the same problem in the official cwm 6.0.4.5 recovery. What happens is that when I go to restore a recovery everything is fine until the data restoring part comes up. It starts restoring the data and then an error pops up and it stops restoring. I have tried restoring new backups from an android 4.3 and 4.4 rom and they both fail at restoring the data. What can I do to fix this? I am stumped.

jonny30bass said:
Hello I am having a problem with restoring backups from clockworkmod recovery. I am using Philz Touch recovery based on cwm 6.0.4.5. I was also having the same problem in the official cwm 6.0.4.5 recovery. What happens is that when I go to restore a recovery everything is fine until the data restoring part comes up. It starts restoring the data and then an error pops up and it stops restoring. I have tried restoring new backups from an android 4.3 and 4.4 rom and they both fail at restoring the data. What can I do to fix this? I am stumped.
Click to expand...
Click to collapse
Try to wipe system/data/cache/dalvik cache, then do format, after that make sure your storage are mounted then try restore again.

buhohitr said:
Try to wipe system/data/cache/dalvik cache, then do format, after that make sure your storage are mounted then try restore again.
Click to expand...
Click to collapse
It worked! First, I wiped everything, which I had been doing all along. Then I went to "Mounts and Storage" and formatted everything except for my external SD card (I feel like the last option in there that said "format /data and /data/media (/sdcard)" is what fixed my issue). Then I mounted /data and /storage/sdcard1. Then, I installed a new rom and made a backup to my external SD card instead of my internal SD card. Then I rebooted into system, and then I rebooted back to recovery and wiped everything to restored my backup from my external SD card. The restore actually worked and didn't give me an error when restoring the data. Thank you for your help! Can you let me know if /data needs to be mounted under the "Mounts and Storage" section of the recovery menu?

jonny30bass said:
It worked! First, I wiped everything, which I had been doing all along. Then I went to "Mounts and Storage" and formatted everything except for my external SD card (I feel like the last option in there that said "format /data and /data/media (/sdcard)" is what fixed my issue). Then I mounted /data and /storage/sdcard1. Then, I installed a new rom and made a backup to my external SD card instead of my internal SD card. Then I rebooted into system, and then I rebooted back to recovery and wiped everything to restored my backup from my external SD card. The restore actually worked and didn't give me an error when restoring the data. Thank you for your help! Can you let me know if /data needs to be mounted under the "Mounts and Storage" section of the recovery menu?
Click to expand...
Click to collapse
Just make sure everything is mounted, it should display "unmount" meaning it mounted. in any doubt, It won't hurt if you mounted them, versus if you mis the important one then you will run into issue.

[Q] SD Card no longer detected when downgrading from 12.1

I am facing a really weird problem.
Initially, my HTC Desire S was running CM10.1 ROM, with sdcard 32GB FAT32 formatted. Recovery was CWM 5.0.2.0. I saw CM 12.1 Lollipop ROM for HTC saga, and decided to try it out. Recovery was updated to TWRP-saga-2.8.5.2-unofficial, and installed successfully CM12.1 The phone was lagging, and decided to revert back to CM10.1.
The sdcard was not detected in CM10.1, neither when recovery was reverted back to CWM 5.0.2.0. I also tried recovery-clockwork-touch-5.8.1.5-saga and recovery-twrp-2.6.3.0-saga, none could mount the sdcard. I tried other sdcards (16GB and 8GB), formatting them using SDFormatter, checking using MiniTool Partition to make sure it's not set to logical. None could be detected.
But when I put back TWRP-saga-2.8.5.2-unofficial, all sdcards could be detected in recovery. I reinstalled CM12.1, it could also detect and use the sdcard.
It seems that installing recovery TWRP-saga-2.8.5.2-unofficial and/or upgrading to 12.1. had caused sdcard to be undetectable by earlier version of recovery and OS.
How can I fix this, and have my phone running CM10.1 again, with sdcard detected?

Try flashing 4ext recovery see if thats able to mount anything.
Theres a thread by me in Desire S General and its 4ext recovery as PG88IMG. Just extract the zip file and flash recovery.img via fastboot. (or just use the PG88IMG haha)

jmcclue said:
Try flashing 4ext recovery see if thats able to mount anything.
Theres a thread by me in Desire S General and its 4ext recovery as PG88IMG. Just extract the zip file and flash recovery.img via fastboot. (or just use the PG88IMG haha)
Click to expand...
Click to collapse
Nope, 4ext can't mount sdcard. It seems only TWRP-saga-2.8.5.2-unofficial recovery and CM12.1 can detect the sdcard.

tjhiwa said:
Nope, 4ext can't mount sdcard. It seems only TWRP-saga-2.8.5.2-unofficial recovery and CM12.1 can detect the sdcard.
Click to expand...
Click to collapse
Strange. U should ask the dev of twrp and or the rom dev to see if they know anything bout it.
Check ur sdcard for any recovery folder (twrp) and delete it then try flashing 4ext. There might be something in the folder f****** things up haha.

jmcclue said:
Check ur sdcard for any recovery folder (twrp) and delete it then try flashing 4ext. There might be something in the folder f****** things up haha.
Click to expand...
Click to collapse
It happens also to newly formatted sdcards.

How do u format the sdcard? Coz if u format it using recovery then it doesnt delete the recovery folder. Anyway im out of ideas so best contact the dev see if they know why.

Error trying to wipe Internal Storage (TWRP)

Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!

trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
Click to expand...
Click to collapse
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards

Are you using latest 2.8.6.0/2.8.6.1?

davebugyi said:
Are you using latest 2.8.6.0/2.8.6.1?
Click to expand...
Click to collapse
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
I am using 2.8.6.1 (latest version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response

trionic said:
I am using 2.8.6.1 (last version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
Click to expand...
Click to collapse
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards

real_pac said:
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
Click to expand...
Click to collapse
I installed again with TWRP Manager and everything works perfectly now (no error message). Thanks again

trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
[...]
Click to expand...
Click to collapse
I faced this error once on twrp 2.8.6.1 a week ago. I wanted to restore my nandroid and the error repeatedly happened while restoring data-partition. I then booted the system and deleted some files from internal storage (which was about half full at the time the error occurred). Afterwards I rebooted to twrp and could successfully restore my complete nandroid. It's a bit shocking if you face this error when restoring a nandroid, because the restore process wipes the data partition first and then begins the restore.

real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
That tip worked for me (i9192), I just install the last TWRP (I think this is not needed) and wipe /Data with ext4, wipe again to F2FS and restore, thank you.