Develop Bugs

I/O error write to sd card (mybackup pro)

trying to restore apps and i get this message! ? fix?
the restore of data was fine but apps wont!

I'm getting this too when trying to restore my data after flashing a new rom. Let me know if you hear of any solutions.
The mybackup website says its an SD card error.. that may be the case, but it was working fine an hour ago on the old rom I had (because I'm new I can't post the link, but a quick google to their FAQ and you'll see what I mean)

I think my issue was due to the SD card. I reformatted it and then copied the contents back again from my laptop. I've now re-installed the new ROM and am using mybackup root to restore my contents as I type this - all seems fine so far

Thanks for the feedback.
What did you format normal or ext or both
Sent from my HTC Desire using XDA App

I had the same error. I don't find how to fix it but how to recover my data app.
Save the backup on your PC
Execute all .apk in my save folder from your phone
Launch mybackup to do another apps save with data
Copy all file wich are not .apk in the old backup (on your pc) and past them in the new backup folder on your phone (replace all existing file)
And finaly restor the backup, it will restore the data with the app
It's not "user friendly" but it worked for me, it was not a SD card issue

I was having this same issue. Watching alogcat revealed that an apk that MBP was expecting was not there, causing an IO error.
I tried to restore again, this time unselecting that specific app and it appears to be working.
So to fix it, install alogcat and watch for errors as the restore is taking place. This should clue you in on the problem.

gthing said:
I was having this same issue. Watching alogcat revealed that an apk that MBP was expecting was not there, causing an IO error.
I tried to restore again, this time unselecting that specific app and it appears to be working.
So to fix it, install alogcat and watch for errors as the restore is taking place. This should clue you in on the problem.
Click to expand...
Click to collapse
This was exactly my problem. Seems like the ****ing program didn't actually back up a damned thing. The folder which was supposed to have the backed-up APKs was completely empty.
I had to restore from an older backup and it worked.
I guess that's just what happens when you rely on free apps.

Just got the same STUPID problem - I'll try the fix above.
The only reason I chose MyBackup Root was because you can do "0-click batch restore" for free which you can't with the free version of Titanium Backup.
EDIT: Backups won't restore. It says "I/O Error". I've had the SD card for a few weeks and it was working perfectly with Titanium Backup. Also, everything's been properly installed formatted and fixing permissions and clearing caches makes no difference.
EDIT 2: After running aLogcat, it says that Mybackup has the following error: "...apps/appnamehere: open failed: EM0ENT (No such file or directory). It's like this for most of my of apps (and I have hundreds) that are now lost with all their data!
Also, none of the apps that do restore so far link to the market (it says this after restore).
This app really needs updating to resolve these serious issues.
Ouroboros29 said:
I had the same error. I don't find how to fix it but how to recover my data app.
Save the backup on your PC
Execute all .apk in my save folder from your phone
Launch mybackup to do another apps save with data
Copy all file wich are not .apk in the old backup (on your pc) and past them in the new backup folder on your phone (replace all existing file)
And finaly restor the backup, it will restore the data with the app
It's not "user friendly" but it worked for me, it was not a SD card issue
Click to expand...
Click to collapse
When backing up apps and data again it STILL won't backup some apps!! Any suggestions?

[Q] Insufficient Free Storage Space

While trying to update my titanium Backup, I receive this message.
"Batch Backup interrupted: Insufficient free storage space"
I am backing up to my external SD card, and have over 23GB of free space. Titanium Backup has been working fine since I updated to 4.2.2 and just today for the first time generated this error.
Has anyone seen this before. I will try deleting the backup folder and generating a complete backup. I will off load my TI backup to my desktop before deleting the folder on the ext SD card.

The problem was that somehow the ext SD card got mounted as R/O, so just changed to R/W and all is fine.
Not sure what app did that, but will look about.

BobC43 said:
The problem was that somehow the ext SD card got mounted as R/O, so just changed to R/W and all is fine.
Not sure what app did that, but will look about.
Click to expand...
Click to collapse
How can i verify/change mine?
Thanks in advance.

I need help with the same issue...
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4

I am not certain on the Note 8 as I am a Droid person. However, I am rooted and used my file manager to change from R/O to RW. Not sure how to do this if you are not rooted.

Here's the fix!
Follow these steps to fix...
1.) Open Preferences and choose backup folder location
2.) Select Detect and choose whole device
3.) Choose the option /storage/emulated/legacy
4.) Select Use the current folder
5.) Benefit

Just an FYI, same thing happened to me today. It ended up being a permissions problem for me too. I used Root Explorer to add write back to my backup directory and all is fine now.

tobymacfreak said:
Follow these steps to fix...
1.) Open Preferences and choose backup folder location
2.) Select Detect and choose whole device
3.) Choose the option /storage/emulated/legacy
4.) Select Use the current folder
5.) Benefit
Click to expand...
Click to collapse
Awesome! Works perfectly!!!
Was 1 month that my backups were stucked on my Galaxy Nexus

tobymacfreak said:
Follow these steps to fix...
1.) Open Preferences and choose backup folder location
2.) Select Detect and choose whole device
3.) Choose the option /storage/emulated/legacy
4.) Select Use the current folder
5.) Benefit
Click to expand...
Click to collapse
I had to reboot for this to fix the issue, but after that everything worked great. Thanks.

HI guys,
Can anyone help me? I'm having above same issue but not with ext sd card. Mines my internal storage. I have 10gb space. Tried the above but it needs me to create a folder.
Cheers guys.

Stuart99 said:
HI guys,
Can anyone help me? I'm having above same issue but not with ext sd card. Mines my internal storage. I have 10gb space. Tried the above but it needs me to create a folder.
Cheers guys.
Click to expand...
Click to collapse
I use TiBu to store to uSD myself. Root Explorer navigates to uSD click the + key to create a folder and name it whatever you wish. Do the preference deal then use the back key to navigate to that folder you created (wherever it may be). Select if then the setting will be saved when you reboot TiBu.

The above fix did not work for me. I have TiB pro installed on my rooted stock Samsung D710. TiB says that my 32GB external card is not writable. According to ES file explorer, it is. How do I fix this conflict? The last backup that I know of is over a week old.

tobymacfreak said:
Follow these steps to fix...
1.) Open Preferences and choose backup folder location
2.) Select Detect and choose whole device
3.) Choose the option /storage/emulated/legacy
4.) Select Use the current folder
5.) Benefit
Click to expand...
Click to collapse
Champ!

faddyie said:
Champ!
Click to expand...
Click to collapse
This method didn't help me either. I had to uninstall the app and then just install the new one from market.

I have the same issue. Just started with the latest version. I tried changing the bu folder and even uninstalling and reinstalling. Both to no avail.
Sent from my SCH-I545 using Tapatalk

problem on second step
tobymacfreak said:
Follow these steps to fix...
1.) Open Preferences and choose backup folder location
2.) Select Detect and choose whole device
3.) Choose the option /storage/emulated/legacy
4.) Select Use the current folder
5.) Benefit
Click to expand...
Click to collapse
genius

Hi to all I have encountered the same issue with insufficient storage space in my Nexus 7 2012 3g after the last update to v.6.1.5.1. I have tried the preferences fix and nothing happened, I have also created a new folder and used it as a new backup location and still no fix. I have even uninstalled the app and the pro key, rebooted and re-installed both and still the issue persists.I have checked the permissions on the folders used thru root explorer and total commander and they were both read and write ticked...
I also fixed permissions of the app thru ROM toolbox pro, I cleared thru app management in settings the cache of the app....
I have even ensured that the Superuser setting is set to apps and adb. Any ideas on how to proceed??? I start to feel a bit stupid (besides irritated!)
Note that after the last update the app is working great in my GNex but not in my N7 2012 3g so what is the issue??
I thank you in advance for any reply...
and yes I know that this sub forum is for another device but I am getting desperate...

Stuart99 said:
HI guys,
Can anyone help me? I'm having above same issue but not with ext sd card. Mines my internal storage. I have 10gb space. Tried the above but it needs me to create a folder.
Cheers guys.
Click to expand...
Click to collapse
1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.
Then try doing your normal backup procedure.
Source http://forum.xda-developers.com/showpost.php?p=45401236&postcount=13

anandbobby said:
1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.
Then try doing your normal backup procedure.
Source http://forum.xda-developers.com/showpost.php?p=45401236&postcount=13
Click to expand...
Click to collapse
What I got to work was basically following the steps above, but I created a new folder for my backups (/storage/emulated/legacy/TiBak) and it fixed my issue.

I found out the reason for Ti Backup not able to backup on SD card...
The fix that everyone is using, points Ti Backup to the internal storage. Which fixes the issue by routing the backups away from SD card.
Depending on version of Ti Backup and how you shut down or end Ti Backup, Android will mess up the file system of your SD card. The only way to fix the issue, is to unmount and remove the SD card and fix the SD card's filesystem on a laptop or computer.
I had an issue once with an older version of Ti backup... about a month ago. Since I have a lot of data and files on my 64GB exfat SD card, I take it out and do a few maintenance tasks time to time. Once I found the file fragments that were crosslinked and removed them Ti Backup found my folder and was able to perform all its functions.
Until the developer of Ti Backup has a better way of controlling background processes to be shutdown gracefully during exit, this can be problematic for some.

[Q] Strange file directory structure

I’m rooted and using CW for my recovery. I’m using a pre-owned phone that I (thought) I wiped before rooting. I am running stock 4.2.2, baseband MDL.
Initially all I wanted to do was nandroid to my SD card in preparation for flashing a custom ROM. I have a 32GB card that my phone recognizes just fine, so I thought it would make sense to put the backup there. So I enabled Use External Storage in ROM Manager settings and tried to begin the backup process.
First I tried it using the ROM Manager itself. Got this error message:
Unknown volume for path [/external_sd/clockworkmod/backup/name of the backupfile here]
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log
Please open ROM Manager to report the issue​
Then I tried doing it by going straight into Recovery and initiating it myself. That was in the Backup and Restore menu. The Backup location options were
/sdcard
/storage/sdcard1
Neither of those is the external card. Then I looked at the Advanced menu but there was no option that mentioned the external card. So it seems that the Recovery doesn’t see my external card. And the subdirectory options that Recovery wants to use do not exist on my phone.
At first I thought it was my SD card. I removed it, re-formatted it (non-Quick) on my computer, etc. I was still not able to save my recovery to my SD card. Again I see that CW want to put the recovery in a subdirectory that does not exist.
I was able to nandroid to the internal memory, so at least there’s that. But the file directories on my card are a mess that make no sense and don’t seem to match what I’ve seen on multiple forums.
Using ES File Explorer I see this from the root directory -
/storage/emulated/0
/storage/emulated/legacy
/storage/extSdCard
/storage/sdcard0 – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
/storage/container – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
Also from the root directory I see this –
/sdcard/ – this one has a little arrow at the start of the pathname
Then there are these –
/mnt which seems to have copies of sdcard and extSdCard
/mnt_1 which just has extSdCard, sdcard_1, sdcard_2, and sdcard_3
I’m running 4.2.2, baseband MDL. What I would like to do is get the directory structure back to stock and remove all the multiples of data and folders that I am seeing.
1. If I totally wipe the phone, will the stock file structure be restored?
2. If the answer to #1 is “yes”, what happens if I do an Advanced Restore, restoring Data from a nandroid created with the screwy structure? Does the screwy structure return?
Thanks,
Veronica

re: nandroid backup/restore
verngator said:
I’m rooted and using CW for my recovery. I’m using a pre-owned phone that I (thought) I wiped before rooting. I am running stock 4.2.2, baseband MDL.
Initially all I wanted to do was nandroid to my SD card in preparation for flashing a custom ROM. I have a 32GB card that my phone recognizes just fine, so I thought it would make sense to put the backup there. So I enabled Use External Storage in ROM Manager settings and tried to begin the backup process.
First I tried it using the ROM Manager itself. Got this error message:Unknown volume for path [/external_sd/clockworkmod/backup/name of the backupfile here]
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log
Please open ROM Manager to report the issue​Then I tried doing it by going straight into Recovery and initiating it myself. That was in the Backup and Restore menu. The Backup location options were
/sdcard
/storage/sdcard1
Neither of those is the external card. Then I looked at the Advanced menu but there was no option that mentioned the external card. So it seems that the Recovery doesn’t see my external card. And the subdirectory options that Recovery wants to use do not exist on my phone.
At first I thought it was my SD card. I removed it, re-formatted it (non-Quick) on my computer, etc. I was still not able to save my recovery to my SD card. Again I see that CW want to put the recovery in a subdirectory that does not exist.
I was able to nandroid to the internal memory, so at least there’s that. But the file directories on my card are a mess that make no sense and don’t seem to match what I’ve seen on multiple forums.
Using ES File Explorer I see this from the root directory -
/storage/emulated/0
/storage/emulated/legacy
/storage/extSdCard
/storage/sdcard0 – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
/storage/container – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
Also from the root directory I see this –
/sdcard/ – this one has a little arrow at the start of the pathname
Then there are these –
/mnt which seems to have copies of sdcard and extSdCard
/mnt_1 which just has extSdCard, sdcard_1, sdcard_2, and sdcard_3
I’m running 4.2.2, baseband MDL. What I would like to do is get the directory structure back to stock and remove all the multiples of data and folders that I am seeing.
1. If I totally wipe the phone, will the stock file structure be restored?
2. If the answer to #1 is “yes”, what happens if I do an Advanced Restore, restoring Data from a nandroid created with the screwy structure? Does the screwy structure return?
Thanks,
Veronica
Click to expand...
Click to collapse
If you wipe the phone using it's internal "factory data reset"
(settings>accounts>backup and reset>factory data reset)
It will restore the stock phone's internal sdcard's structures, directories and folders.
But what I would suggest is to download and odin flash the TWRP custom recovery,
that way you will not loose any data or user files and you will not have any problems
making or restoring nandroid backups.
TWRP is really easy to use and basically self-explanatory.
Here is the direct download link for TWRP: http://techerrata.com/get/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Good luck!

Misterjunky said:
If you wipe the phone using it's internal "factory data reset"
(settings>accounts>backup and reset>factory data reset)
It will restore the stock phone's internal sdcard's structures, directories and folders.
But what I would suggest is to download and odin flash the TWRP custom recovery,
that way you will not loose any data or user files and you will not have any problems
making or restoring nandroid backups.
TWRP is really easy to use and basically self-explanatory.
Here is the direct download link for TWRP: http://techerrata.com/get/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Good luck!
Click to expand...
Click to collapse
Thanks!
Are you saying that using TWRP will preserve the file structures and that CW has some kind of effect on them...or that CW is the reason I can't put my backup on my SD card?

verngator said:
Thanks!
Are you saying that using TWRP will preserve the file structures and that CW has some kind of effect on them...or that CW is the reason I can't put my backup on my SD card?
Click to expand...
Click to collapse
CWM or TWRP do not effect the file structures.
All I am saying is create a nandroid backup using TWRP and then restore
the backup. Then if it works properly for you then keep using twrp.
You will be pleasantly surprised how well twrp works and how easy it is to use.
Good luck!

[Q] how to pull backup data with adb

hey guys
I'm completely desperate. Here's what happened the last two days:
Yesterday my Fairphone suddenly became very slowly and then wouldn't boot no more. Since then every time I try to start my phone, I get the message "process system doesn't react" or something like that. The only thing thats working is the recovery mode.
Today I wanted to make a complete backup so that I can make a hard reset afterwards. But then I had to realize, that the recovery mode isn't able (or I'm not able to see how) to make a backup on an external sd card but only on the internal storage (which is also called sd card which confused me about an hour).
The problem now is that I have a backup but I can't get it on my computer or on my external sd card and so it will be deleted too if I make a hard reset.
I searched the internet for hours and found out, that it is possible to somehow remote control the phone via adb. I read that the phone has to be in "usb debugging mode". I can just put my phone into adb sideload mode or however its called by choosing "update with adb" in the recovery menu.
Is this the reason why my "adb pull" command isn't working? It just says "error: closed". Or is it because I haven't wrote right the path of the backup file? (I used: /mnt/sdcard/userdata_20130801_134656.backup)
Please help me! I have tried so much already, my brain is sizzling:silly:
I'm working on a Mac and have installed sdk.
Thanks in advance!!!
------------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT:
Just to close this topic and maybe help other people with the same issue:
I finally managed to pull the /data folder using adb. What I didn't know was that the backup file (and all pictures, videos, music and so on too) is stored on the internal sd card which isn't affected by the factory reset in the recovery menu. What I also found out was that the backup file (that I had created during the "bootloop" or whatever it was) was corrupted. So the backup logically broke my FP again after I restored from it.
So the solution, as mentioned above, was to pull the /data folder which contains all important user data such as wifi passwords, contacts, messages and so on
I hope it helps
peace
SC

TiBu problem: Can't write to folder & insufficient storage

Today I started experiencing an issue where TiBu could not perform any backups because of "insufficient storage". Upon further research I found that this issue is related to the "no write permission" for the SD card. I've tried multiple fixes so far:
Adding the media read/write permission by manually editting platform.xml
Downloading SDfix patches from the playstore for 4.4.4
Flashing a zip that contained a modified platform.xml
Note, this issue started today after I restored to a nandroid backup after flashing the Google Play Edition ROM (4.4.4). I was originally on 4.4.2 and the GE rom was 4.4.4
I'm extremely frustrated because I can't seem to get TiBu to accept the fix. When I view my platform.xml through a root explorer it says the permission is there for writing to the external storage.

tcdos said:
Today I started experiencing an issue where TiBu could not perform any backups because of "insufficient storage". Upon further research I found that this issue is related to the "no write permission" for the SD card. I've tried multiple fixes so far:
Adding the media read/write permission by manually editting platform.xml
Downloading SDfix patches from the playstore for 4.4.4
Flashing a zip that contained a modified platform.xml
Note, this issue started today after I restored to a nandroid backup after flashing the Google Play Edition ROM (4.4.4). I was originally on 4.4.2 and the GE rom was 4.4.4
I'm extremely frustrated because I can't seem to get TiBu to accept the fix. When I view my platform.xml through a root explorer it says the permission is there for writing to the external storage.
Click to expand...
Click to collapse
I had a similar problem this past weekend. It seems that something changed the way that TiBu sees the folders on the External SD Card.
Go to Settings/Preferences/Backup Folder Location
Then use the Detect button. It will find the old backup files, but you will see a different folder path to get there.
After you tell it to use the detected folder, get back to main Settings, and then select Reload Application.
It should work again. At least it did for me.
Rob

rlichtefeld said:
I had a similar problem this past weekend. It seems that something changed the way that TiBu sees the folders on the External SD Card.
Go to Settings/Preferences/Backup Folder Location
Then use the Detect button. It will find the old backup files, but you will see a different folder path to get there.
After you tell it to use the detected folder, get back to main Settings, and then select Reload Application.
It should work again. At least it did for me.
Rob
Click to expand...
Click to collapse
Thanks for the suggestion Rob, but unfortunately that did not work. It folder location remained the same. As of now, the backup location is "storage/emulated/legacy/TitaniumBackup". Should I move the backup folder from my internal storage to my SD card and then try to detect the folder?

tcdos said:
Thanks for the suggestion Rob, but unfortunately that did not work. It folder location remained the same. As of now, the backup location is "storage/emulated/legacy/TitaniumBackup". Should I move the backup folder from my internal storage to my SD card and then try to detect the folder?
Click to expand...
Click to collapse
The Detect only looks for existing backups. I use by External SD card for two reasons: 1) it frees up some space on the internal, since some apps can't use the external, 2) if the phone dies, it should be possible to take the SD card to a new phone and use it to restore.
You could set the Backup folder location to your External SD card and see if it works when you attempt to backup.
Rob

rlichtefeld said:
The Detect only looks for existing backups. I use by External SD card for two reasons: 1) it frees up some space on the internal, since some apps can't use the external, 2) if the phone dies, it should be possible to take the SD card to a new phone and use it to restore.
You could set the Backup folder location to your External SD card and see if it works when you attempt to backup.
Rob
Click to expand...
Click to collapse
It works now! Anyways, do you have any idea why apps like Instagram and Snapchat dont work after an app/data restore from a TiBu update when flashing a new ROM? I can open the apps successfully but pictures arent being displayed. It's almost like the data is corrupt or something. Thanks again.