Database Users

Tayutama One Click Lag Fix!!!

********Please Mods remove thread if possible!! New Tatuyama fix (ext4) has been incorporated into SuperRooter by DesignGears ********
LINK: http://forum.xda-developers.com/showthread.php?t=751934
DISCLAIMER
DO IT ON YOUR OWN RISK.
ME OR ANYONE ELSE ON THIS FORUM IS NOT RESPONSIBLE FOR BRICKED/DEAD DEVICES AND/OR DEAD SD CARDS.
YOU SHOULD UNDERSTAND EVERY STEP IN THIS HOW-TO BEFORE ATTEMPTING TO FOLLOW.
**********EDIT LOG*******************
8/10/2010: Added Startup Issue Reversion
8/11/2010: Added Alternate Manual Method that might work better than AUTO
8/11/2010: Added Possible Method of Backing EXT2 Partition
Here everyone... I have been trying lag fixes all over the place and I always seem to have issues partitioning the external sd for the apps... so after so many attempts, this was BY FAR the best lag fix out there.... It doesn't rely on the externalsd for functionality.
Easy and nothing special needed.
The steps below are pretty good, but I did things a little different.
Copied the update.zip to my external sdcard.
Then used Root Explorer to copy the update.zip to my internal sd card.
(******Here is the updated filed: http://forum.xda-developers.com/attachment.php?attachmentid=376882&d=1281390347******)
Then I used ROM Manager (Reboot into Recovery) to boot into the Linux Loader
Then I said update using update.zip (not install update.zip)
Then Reboot
For some reason it didn't install busybox 1.17.1 so install it manually
(located: http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229)
Make sure after you install busybox.apk that you go into busybox and check to MAKE SURE you are running 1.17.1 ONLY. You might have an older version or newer version but it must be 1.17.1; if different just click install.
After that follow the MCR Scripts below. (Took about 6 minutes to do everything)
*** If MCR Scripts DOES NOT show up, its probably because you don't have the non market install hack on your phone. In the update.zip you can find the apk and install via ADB, but I didn't do it this way. ******
(Original Thread! Alternate method on OP in link below! Some people say it worked better for them.)
http://forum.xda-developers.com/showpost.php?p=7587405&postcount=417
@Tayutama
I ran the Tayutama update.zip using the up+power+menu button method, it installed in seconds and I restarted the phone. I ran the benchmark but still got 8xx scores. I'm an Noob, so needed more thorough instructions. These are now given below. NOTE: THIS METHOD IS MUCH MORE NOOB FRIENDLY AND DOES NOT REQUIRE A PC OR USB DEBUGGING MODE.
EDIT I had realised I needed to launch the newly installed MCR app after restart and choose a lagfix file to run. I ran the file and 'all complete'. This worked a treat. Ran Quadrant and now have a top score of 2114 running on JM2. System is much snappier. This mod of RyanZA fix by Tayutama is the most noob friendly also. Full instructions as follows:
EDIT Requirements: Make sure your phone has 'superuser' app installed by checking your app list. If it isn't installed, you can use a newer beta version of Tayutama's update.zip
available at; http://forum.xda-developers.com/atta...4&d=1281437129
Full instructions:
1. The update.zip installs all the files needed. It is attached here; http://forum.xda-developers.com/atta...2&d=1281390347
2. Place it on your internal sdcard
3. Turn off your phone.
4. Hold down Up+powerbutton+Menubutton for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it
7. It installs root, correct busybox (1.17.1) as well as all the scripts needed for the fix and the 'MCR Scripts' app to run the scripts. (NOTE: This version does not install superuser.app which is needed, although the beta update.zip does, so read 'requirements' above if needed)
8. After install, the phone restarts.
9. Go to the newly installed 'MCR Scripts' application from the app list, open it and choose from 3 scripts. For example, Lagfix10024 is the 1gb ex2 version.
10. The script should run and take a few minutes.
11. You should see an 'all complete' prompt, and this means you can close the application.
12. Run quadrant to test if the fix was applied.
Originally Posted by Tayutama
Don't know if you mind me posting this here RyanZA, but i made a update.zip out of your script. NOTE THIS ONLY WORKS ON 2.1
What this update.zip file does is that it copies a few files to your internal sdcard and installs ASE which can be used to run .sh files without the need to use a terminal.
There are 3 scripts included:
LagFix1024.sh - Makes a 1GB file on /data
LagFix512.sh - Makes a 512MB file on /data
RemoveFix.sh - Removes the lagfix
This also includes BusyBox 1.17.1 so no need to install that first.
Testet this on JM1
Click to expand...
Click to collapse
********Alternate Method that might even work better!! ****************
All the files are located in the update.zip file that you need to download.
1. Connect phone to PC, make sure adb can see it:
adb devices
2. adb kill-server
3. adb push createlagfix.txt /sdcard/createlagfix.sh
4. adb push playlogos1 /sdcard/playlogos1
5. adb push userinit.sh /sdcard/userinit.sh
6. adb shell su -c "/system/bin/sh /sdcard/createlagfix.sh"
7. adb kill-server
8. adb reboot
************ Reverting back if there are boot up and black screen issues ****************
If you have black screen and doesn't boot into the desktop, this is the fix to return back to normal state:
To fix that problem:
1. Boot into Recovery Mode (Vol Up + Vol Down + Power) Let go of Power after you see AT&T.
2. Delete User Cache
3. Delete All User Data
4. Then see if your phone boots up
5. If your phone does boot up then navigate to Settings -> Security -> Factory Reset
6. After factory reset your phone should be useable again.
DO NOT INSTALL THIS UPDATE IF YOU DO NOT KNOW WHAT YOU ARE DOING.
**********Possible method of Backing up Your EXT2 Partition **********
BTW I would also perform a NANDROID Backup as well which can be done by using ROM Manager to boot into the Android Loader....
Nandroid does NOT back up the apps off your SD card.
AppsToSD (I'm speaking re MoDaCo's rom here) uses the ext2 partition on your SD card for the /data/app and /data/app-private folders, where your actual downloaded application files are kept. Nandroid does NOT back this up, and simply mounting your SD card and copying the files off also does not back this up.
The only way to back up these critical folders is to directly copy them to somewhere else. You can use command line or Droid Explorer.
If you want to use command line, do this from an ADB shell or terminal:
mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
This will create two folders on your SD card: app and app-private, both in a folder called Backup. It will then copy the entire contents of your /data/app and /data/app-private folders to your SD card.
After you do this, back up the entire contents of your SD card as normal.
To restore the files after replacing/partitioning your SD card, head to this thread:
http://forum.xda-developers.com/showthread.php?t=585349
Click to expand...
Click to collapse

Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6

slider2828 said:
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
Click to expand...
Click to collapse
Does it show strong real world improvements?

good job explaining nothing. troll harder

So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.

This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.

Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.

hm... i applied the update in clockwork mod recovery, i have super user and the correct busybox version installed and rebooted the system. i went to the app list and could not find the "MCR SCRIPT" you mentioned i should be seeing... am i doing something wrong?

THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....

solufein said:
good job explaining nothing. troll harder
Click to expand...
Click to collapse
What the hell does that mean.... You saying it doesn't work? Why not try it and it is an EXT2 fix.
max_warheads said:
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
Click to expand...
Click to collapse
This isn't one step because I don't have the USB cable with me. I just had a USB adapter for the microsd and I can't boot into the linux loader correctly without the cable, so I used ROM Manager. It would have been easier if I did.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Yup it is but on the internal card. Are you sure its the same? Look at the OG thread, a LOT of people have tried it with great success....
darth_vato said:
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
Click to expand...
Click to collapse
How do you back it up?

i updated the zip and rebooted used busy box and i dont have that MCR app

Bionicboto said:
i updated the zip and rebooted used busy box and i dont have that MCR app
Click to expand...
Click to collapse
Same instructions before, did you download the update.zip? I just added that instruction. Can you try again after that?

slider2828 said:
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
Click to expand...
Click to collapse
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.

its still the same cant find the app i reboot to recovery apply sd card update.zip go to yes and it says installed reboot and its not there

arsinic said:
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
Click to expand...
Click to collapse
Sorry for the bad reply.
Rename the update.zip that is already on the internal sd cards root because that is ROM Managers using ROOT Explorer
Then copy the update.zip that you downloaded to the external SD card.
Then copy update.zip from the external sd card to the internal sd cards root.
Then use ROM Manager to reboot into the linux loader.
Hope that helps?
-Ken

slider2828 said:
Sorry for the bad reply.
The update.zip that you use download, copy it the the internal sd card's root... (Basically where ROM Manager update.zip was. Like you did Rename the update.zip that is already there, because that is ROM Managers).
Hope that helps?
Click to expand...
Click to collapse
hm... the only update.zip i have is in the Recovery Mod folder named: recovery-update.zip. the only update.zip i have in the sdcard root is the update.zip i downloaded from the your url and have been applying that as the update. i seem to be having the same problem as Bionicboto.
should i have the rom manager's update.zip in there also or it doesn't matter? and i also have no external sd card. is that something i need in order to get this update working properly?

Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Basically when I log into root explorer and click on SDCARD.... you should see the update.zip in that folder along with Android folder, busybox folder, clockworkmod folder, DCIM folder, downloads folder, etc etc....

slider2828 said:
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Click to expand...
Click to collapse
i preformed a backup right before i did all this. i did notice the update.zip in there. i took it out and put in the update.zip you uploaded. do i need both in there?
thanks for the quick replies btw.

Nope... Try this... with ROM Manager,
Choose Flash ClockWorkMod Recovery and that will recreate the boot files for ROM Manager.... and also backup your current ROM again.
Then try the steps again.
OMG Dude I noticed you in oakland, I am in hayward/san leandro.... We can try after I get off work which is in 30 minutes. and then take 30 minutes to get back to SL....
You wanna meet at the starbux on marina?

Flashed and installed perfectly. Bumped my quadrant up to 2117. Good post, thanks.

Cannot see twrp back up files. Please help.

I recently switched over to team win recovery from cwm. I do like the ui and functionality way better then cwm. The problem I'm having is that I cannot access my back up files from my PC via USB. When I use the file browser that is built into twrp I can see the back up files in the twrp folder. When I plug my tablet into my PC via USB and open the twrp folder it is empty. Also when I open the twrp folder in es file browser it is empty there too. I would like to store the back up on my PC rather then on my tablet. Am I missing something? I was having this same problem with titanium with backed up apps so I upgraded to the paid version and uploaded my back ups to Google drive. After that I looked in the titanium back up folder again on my PC and all the sudden the files were there when before they were not. Its very frustrating. Please help.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.

Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.

mtrs said:
I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.
Click to expand...
Click to collapse
Thank you for the tip. I went everywhere yesterday...
Best buy, radio shack, staples etc looking for an otg cable and had no luck. I'm going to order one online today. I will give the other techniques a try today though. I'm not familiar with pseudo terminal but I'm gonna dig in anyway. That's the best thing about these gadgets for me is hacking in and figuring out. Thanks again for your help!
mtrs said:
Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.
Click to expand...
Click to collapse
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

norcal61 said:
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Click to expand...
Click to collapse
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.

mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
Cool, that totally makes sense. Can't believe I didn't try that all ready. I will definitely make a new back up with the latest version of twrp. I'm running the same ROM and kernel as the back up that I currently have stored. Gonna give it a shot right now and let you know how it works.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.

norcal61 said:
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.
Click to expand...
Click to collapse
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.

mtrs said:
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.
Click to expand...
Click to collapse
It worked! I deleted the twrp folder all together and it worked like a charm. I'm now able to see and move the backups to my PC. Thank you very much for your help. It is greatly appreciated!
Sent from my Nexus 7 using Xparent Green Tapatalk 2

Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.

trungdtdev said:
Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.
Click to expand...
Click to collapse
I had the same issue and tried searching for "TWRP" to locate every instance of that folder. Turns out that I had previous backups in:
/mnt/shell/emulated/TWRP/BACKUPS/
I am happy to report that I was able to delete several past and hidden backups and recovered over 9gb of space!

Nexus 7 partition table messed up/ broken?

Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP

That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/

Tasssadar said:
That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/
Click to expand...
Click to collapse
Thank you for your help but I'm using clockworkmod recovery. What do i need to change in that command to suit CWM?

Matty Matt said:
Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP
Click to expand...
Click to collapse
Haha, I thought I was the only one! I thought I had partitioned my card somehow. I basically did the same thing as you. I also am running CWM. Its making Rom flashing almost impossible for me, I can only select & flash files from the SD "O". All my nandroids are on the regular SD selection. Did you ever find you answer Matt.?
Sent from my Nexus 7 using Tapatalk 2

How can I access & write to my /data partition

Hi,
My tablet was having some issues yesterday and wouldn't turn on, so I managed to do a factory reset, planning on restoring everything from Titanium Backup (from my TWRP backup), however, when I look at my TWRP Backup in TiBu, there doesn't seem to be anything there?
However, when I copy the data.win file to my computer and extract it, I can see all the files and I would like to try and copy some of the saves back to my data partition, however, I can't seem to find a way to find it or write to it?
Any ideas?
Stewart

There are many possibilities, on of them:
- boot Nexus 7 into recovery mode
- connect the Nexus 7 with USB to you PC
- mount /data in recovery
- adb push the files / directories you want to restore to the /data partition
- ...
There is only one problem: as you have done a factory reset / wipe the corresponding apps are no longer installed and even if you install them again,they will get a different uid so that the restored data is no longer accessible to them. Probably fix_permissions can help in that situations, but I didn't try yet.

AndDiSa said:
There are many possibilities, on of them:
- boot Nexus 7 into recovery mode
- connect the Nexus 7 with USB to you PC
- mount /data in recovery
- adb push the files / directories you want to restore to the /data partition
- ...
There is only one problem: as you have done a factory reset / wipe the corresponding apps are no longer installed and even if you install them again,they will get a different uid so that the restored data is no longer accessible to them. Probably fix_permissions can help in that situations, but I didn't try yet.
Click to expand...
Click to collapse
Ah ok, that sucks!
Is there not anyway I can use an Android based GUI tool to copy the files from my SDCard to /data.
I am not the best with adb, but I imagine the command would be "./adb push <insert file name here> /data/com.bigideas.swys/files", would that work?
Cheers
Stewart

Yes, that should work. Unfortunately I don't know any tool providing the functionality you are looking for.
Sent from my Nexus 7 using xda app-developers app

Ummm... how about you restore it in TWRP like you're supposed to?
Sent from my SGH-I777 using xda premium

TWRP should work, too, but if I remember well, the USB id is different, so you might get problems with adb if you do not have the correct driver installed.
To push a file to the device:
- unzip/untar data.win on your PC
- boot device to recovery
- on PC cmd-line:
- adb shell mount /data
- adb push <file_or_dir_to_push> /data/
But as I said, most likely it's not enough ...
Sent from my Nexus 7 using xda app-developers app

korockinout13 said:
Ummm... how about you restore it in TWRP like you're supposed to?
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Because that caused it to stop booting like it did when it first powered off!
Sent from my Nexus 4 using Tapatalk 2

StuMcBill said:
Because that caused it to stop booting like it did when it first powered off!
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
The data.win file is just a tar archive. You can extract whatever you want, although there are a couple caveats:
- the .tar archives seem to be absolutely rooted (e.g. /foo/bar instead of ./foo/bar) so you might need to fool with -C or other tar command line options to get the result you are after.
- while you certainly could use 7-zip or similar to unpack the archive and cherry pick whatever you want on a Windoze box, you probably ought to do offline unpacking using Linux so you don't lose file permission settings. An alternative would be to unpack on the device itself to someplace such as /data/local/tmp using your preferred terminal emulator (or adb command line) and busybox combination. Then you can adjust ownership via "chmod -r" as needed and "mv" to move your cherry picks into place. Note you also need to pay attention to /data/app-lib/* in addition to /data/data/* and /data/app/* cherry picks.
- To reiterate about file ownership, probably what you should do is install only the .apks you want first, and then after rebooting, note the assigned user/group IDs chosen for each app install, and change the restored /data/data/* and /data/app-lib/* files to that uid.
Confused? Well, you asked. Look up a decent Linux administration guide for clarification.
good luck

[Q] Can't move several Titanium Backup .gz files to PC. Permission issues?

Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.

deusfaux said:
Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.
Click to expand...
Click to collapse
I think TIBU needs a big update....I have same issue but my biggest problem is I can´t uninstall any system apps (there a some I don´t need) when I tap the uninstall button always same thing...."Cannot find the .apk file .....no problem whith my personally apk´s..?
Somebody same issue?

I ran into the same issue and solved (?) it by rebooting into recovery and doing an adb pull from there. It doesn't work from within Android like you said but once you're in the recovery partition things are different.
I think this not a problem with TiBu (or maybe it just needs an update like shivasrage said), because I can't copy my Nandroids to my PC either. I had to do a adb pull from recovery as well in that case. In fact, now that I remember, yesterday I tried to copy some backups I did in ES Explorer and some of them failed.
Android 4.3 is secure but that's messing with our old habits and making things more difficult.

Yeah but I had this problem before updating to 4.3

deusfaux said:
Yeah but I had this problem before updating to 4.3
Click to expand...
Click to collapse
Oh, that's weird. I never had this problem before 4.3.

I just went through this exact same problem with my TWRP backup files yesterday (Except in that case it was an issue with the latest 2.6 version of TWRP, not the Android OS). For Titanium Backup, I am going to have to go back today and count the files that I copied over to my PC using Windows Explorer and compare it to an adb pull under Recovery. There are so many files as part of the backup that I would never have noticed a couple of missing ones like I did on TWRP.
EDIT: Just checked and 427 files were copied over doing it each way with a full Titanium Backup (Windows Explorer or an adb pull), so it works fine for me. I am on Android version 4.2.2.

I solved the problem by installing BusyBox from Play Store (Normal install). Then, opened a command window (you can also do it using Terminal Emulator) from within my platform-tools folder in C and typed:
adb shell
su (grant permission in the phone)
busybox chown -R 1023.1023 /data/media/*
Click to expand...
Click to collapse
Now I can safely copy all files by drag-n-drop or adb pull from within android.
Cheers

Can someone walk me through solving this? I'm wanting to do a factory reset immediately, but I can't before copying over these Titanium Backup'd apps.
Why is this even happening?
ABD, ES File Explorer, everything is giving me a permission error. The latter said EACCES (Permission denied) Refused by system.
edit: nevermind. I narrowed down the offending files, and forced new backups by deleting the old ones and re-doing them. Something about the way TiBu wrote a handful of the backups was not allowing anything to copy the files.