[Q] Froyo App 2 SD Script Help - General Questions and Answers

I've got a rooted G1 running CM-6.1.0 stable. Because I'm too lazy to move numerous apps one by one to the SD card by going to system>applications>manage applications, i have decided to write a script that will move all non-system apps that are installed on internal storage to the SD card. This is what i have so far.
Code:
# list=$(ls /data/app/)
# for file in $list
> do
> dir=$(file%.apk)
> mkdir /mnt/asec/$dir
> mv /data/app/$file /mnt/asec/$dir/pkg.apk
> done
my problem is that other than moving the .apk files from "/data/app/" to the appropriate directory in "/mnt/asec/", i don't know what App2SD does. can someone please tell me exactly what other actions are preformed by clicking "move app to SD card"? once i know what it does, then i should be able to finish my script.
note: please do not respond by saying "pm setInstallLocation 2", anything regarding ADB pull/push/install, or by telling me to go install some app off of the market. i already have the install location set correctly, i don't always have a computer near me to use ADB, and I'm not going to waste my time waiting for some goddamn GUI to load just so i can do something that could surely be done more efficiently via a simple script. Thanks.

Related

Apps to SD Problem on Haykuro H Build

I've been using Haykuro's G build because H has never worked for me. But now with the market problem I'm needing to switch to H because there are a lot of apps I want to download.
When I flash over to the H build and try to setup apps to sd, I always get stuck in a boot loop and I can't seem to figure out why that is. I thought maybe it was an app I had on my sdcard so I formatted both partitions and it still doesn't work.
If anyone can help it'd be greatly appreciated. =)
1st: you are trying the apps to sd H build right(not just the normal H version)?
2nd: what steps are you doing to try apps to sd and are any reporting errors?
3rd: are you trying to move the app cache also(/data/data)? If so that might be your problem.
It's the apps to sd version and I was just following the steps on the wiki pg.
http://android-dls.com/wiki/index.php?title=Haykuro_Apps_to_SD
And no I wasn't trying to move cache.
Hmm try going into the recovery terminal and do the following:
Code:
mount data
cd data
ls -l
look for the app directory listing and tell me what it says on that line(it'll probably carry over to the next line as well)
If the app directory doesn't exist well... then there's your problem.
app -> /system/sd/app
is that what you needed?
xocassidychick15ox said:
app -> /system/sd/app
is that what you needed?
Click to expand...
Click to collapse
Hmm ya, that looks correct. Was there anything else with that "->" next to it? If not, something is wrong with the sd card setup. Either /system/sd/app doesn't exist or the partitions aren't set up correctly. As a temporary fix(if there's nothing else with a '->') you can do this:
Code:
rm /data/app
mkdir/data/app
The only thing else that has '->' is:
app-private-> /system/sd/app-private
Hmm not looking good... try the code segment I put before, it should at least let you get into your phone. From there you can look into the /system/sd directory and make sure everything is correct.
EDIT: by not looking good I meant all that is correct which means it's something that'll be harder to fix.
When I try to enter the code it says:
rm /data/app
rm: cannot remove '/data/app' : No such file or directory
mkdir/data/app
sh: mkdir/data/app: not found
And when I look in /system/sd all it shows is lost+found
When I tried the code in ADB the first part went through but it still said
mkdir/data/app: not found
wfirst: there's a space between mkdir and /data/app.
also: you didn't restart the phone or anything since typing in the "mount data" bit have you? If so you need to type that again before doing that code segment.
EDIT: PM me your answers, I'll try to solve this through pm.
This has been solved. Reflashing the ROM fixed it.
The same thing happened to me. Went from 5.01G apps to SD, to 5.01Hr3 apps to SD. After setting up and changing the references to have apps point to the SD card (note that I already had apps on the SD card), all my apps appeared after rebooting. When I tried to reboot again, that's when I saw the endless HTC logo loop.
I reflashed the phone and it seemed to fix it. However, the phone later locked on me and I had to reboot by removing the battery. When the phone started again, I got the HTC logo loop.
I ended up going to Dude's G release instead. Hope someone figures this out.

Simple Guide for Rooting (Tweaks Coming Soon)

I owe much credit to toastcfh, none of this would be possibly without his work on originally rooting the EVO.
Getting Root & Recovery Mode
(My version, dumbed down even more)
You have three options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support
3) Unrevoked Root Patch - No system access in recovery (can't remove sprint apps, etc)
To get a rooted stock ROM, you have to start with Toasts, instructions below; you can find details after.
If you want the Unrevoked Root patch, install a file browser on your EVO and install this.
1. Copy this to the root folder of the SD card, you can do this by syncing the Evo as a disc and just copying in windows.
2. Shut off the Evo, and hold the "volume down" button while powering it on until you see a white screen. Every question it asks, just answer yes. DO NOT UNPLUG, let it finish at all costs, no matter how long it takes.
3. Rename the file you copied to the SD card. (to avoid accidental re-flash and save it for later)
4. Download this and unzip to anywhere of you liking on your desktop. Run the setup, if it asks to accept and install a bunch of stuff, hit cancel, you wont be needing most of it. Select available packages and it will show a repository url, the actual url is irrelevant and will be google's be default...we want to expand the list and select SDK Platform 2.1. Accept an install the selection.
What you just did is installed the Android SDK which includes adb, a shell connector for your phone that we need to operate in recovery mode.
5. Hold the Windows key and press "R", type CMD in the run box. (Run the task with Administrative privileges if there is an option)
Type "cd " in the CMD window, do not forget the trailing space, it is important and DO NOT HIT ENTER yet.
Now, with that CMD windows open, go to the folder you installed the android sdk. There will be a "tools" folder, drag the tools folder into the cmd window.
Press enter, this will set your working directory to the tools folder.
6. If you have not installed drivers for your Evo, there is a folder that comes of the sd card called "HTC-Sync", run the setup in there and it will install sufficient drivers automatically.
After drivers are setup sync the phone using the HTC Sync mode, this will ensure we can control the phone using adb.
Go to your CMD window and type "adb reboot recovery", you will see your phone reboot...it will show a red warning icon on the screen afterwards, this is perfectly normal and good to see such.
7. Your phone should not be in recovery mode, but the filesystem will be offline. Download this to setup the shell for us before we can mount the filesystem. Run "recovery-windows.bat", if you are using Vista or Win7, make to sure right click the file and "Run as Administrator"...you will see another CMD window popup and do some work, just leave it open. You should now have the shell setup in Recovery Mode on your Evo.
8. Go back to your original CMD window we setup, type "adb shell" and hit enter, this will set all commands to work right on the phone. You should see a line with just "#", that is what we want.
Now type "mount /dev/block/mtdblock4 /system" and hit enter.
You should now have your Evo in recovery mode with a shell setup and filesystem mounted. This is where we can begin making changes.
Now that this has all been setup, you may want to go back after making some changes.
Repeat steps 5-8 to re-enter recovery mode with the filesystem mounted.
If you want to continue and do the stock update, check here.
Basically, copy that file to the SD and do steps 5-7.
Then use the onscreen (on the EVO Recovery Mode) to "Flash from ZIP" and select the rooted stock rom update.
WARNING: You must clear user data if the update creates issue, you will know right away.
so this is a third way of rooting, if i used a different way how do i get rid of it and use yours, i'm so tired and confused.
Post Removed to maintain consistancy, see 1st post in thread.
root rom and activesync?
I'm a complete noob here but: By using this method do I still retain the ability to run ActiveSync/Exchange support? (Didn't think this was in the SDK Platform 2.1)
What about Sense?
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Good noob friendly guide, kinda tldr, but what I did readlooked good!
Change ur title
Neotelos_com;
[B said:
You have two options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support[/B]
....
Click to expand...
Click to collapse
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
adeyo said:
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
Click to expand...
Click to collapse
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
johnsongrantr said:
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Change ur title
Click to expand...
Click to collapse
I have plans for adding in tweaks, which will be delayed a bit...
Sorry for any inconvenience.
Neotelos_com said:
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
Click to expand...
Click to collapse
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Click to expand...
Click to collapse
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Neotelos_com said:
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Click to expand...
Click to collapse
Well thats all kinds of dumb..
I give it a week and there will be something better working.
Nice write up. The only problem is, I don't have the sync software on my sd card because the best buy employee knew about the evo's sd card problem and formatted it, erasing everything on the card. I checked htc's site and they had the drivers for download, but it keeps giving me an error saying it's not compatible. I'm using windows 7 64bit. Any ideas guys?
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Click to expand...
Click to collapse
you CAN remove apps like that, using toast's custom recovery. if you do your shell, and mount, in recovery, using adb, you can go to /system/app and rm whatever you want (be careful not to remove anything important, probably wise to pull whatever first, in case you need to push it back)
i had problems when i did an rm on a file, but that is because apparently i forgot to rm it's info in /data/data too. word to the wise
HTC Sync Torrent
http://thepiratebay.org/torrent/5609530
PLEASE SEED AFTER DOWNLOAD!
New android user here!
So to me it seems like all three have something they're not able to do. Seems best to wait for a root release that your able to take full advantage of, right?
I'm a former WM flasher , I need to learn android still. I want the free hot spot/tethering, more battery life as I need 2 batteries to make it through the day -.- (I kill apps constantly, 4g turned on rarely,ect, ect)
Any feedback is appreciated,
Sean
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
kingcliff00 said:
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
Click to expand...
Click to collapse
Try going to Settings -> Applications on the evo and enable usb debugging...if that5 gives you adb access that's all you need
confirmed working with unrevoked root method. It can tether 3G or 4G, depends on how you connected to the Sprint network. 3G was 0.80Mbps DL, 4G was 2.63Mbps DL.
Before using unrevoked root method, I had applied the sdcard patch already. so it doesn't matter if you applied the sdcard patch or not (OTA updated).
You really shouldn't kill tasks. Just cycle the battery a couple of times and turn your antennas off and on when u need them. Especially if u are in spotty 3g coverage. There already one or two official write ups that say task killing is bad I use to do it and got forceloses and errors all the time. Its not about how many tasks you have running I.e. memory, items about cpu and antenna signal that kills you're battery I'll find the link if I can. My battery life is pretty good and I'm a heavy user.
Sent from my PC36100 using Tapatalk
i cannot get recovery bat file to work. I am at the red exclamation point screen on my evo and i run the bat file as amdmin. it pops up for a second then closes and nothing happens.
Edit: NVM I figured it out. on to the next step.

[Tool] SaveMyApp - Preinstall Your Apps

Tired of having to redownload and reinstall all of your apps when you reflash your phone? SaveMyApp can help.
This script will setup your phone so that after your flash to your favorite rom, all* of your apps will be install on the first boot. These apps will show up in the market too!
Also, the script will allow you to backup your /data/data folder to your sdcard and then restore it after your reflash. The /data/data is where Most of your user data is stored. This is not guaranteed to fully restore everything. This also does not backup your Google, Android, or Motorola settings; this is to improve compatibility with roms.
*The /preinstall folder is limited to 120MB, so if you have more then of apps this script will not fully work.
This should work with all phones, however it has only been tested on the Droid 2/X.
If you want to test this script on a different phone, let me know the /preinstall size and if it worked or not.
v0.1.4.2 - 11/17/2010
-Improved backup and restore of data
-Improved script usability
v0.1.4.1 - 11/17/2010
-Improve safety of removing /preinstall/app
v0.1.4 - 11/16/2010
-Added option to clear the /preinstall/app folder
-Added messages to support clear /preinstall/app
v0.1.3 - 11/12/2010
-Added backup of /data/data
-Added messages to support Data Backup
v0.1.2 - 11/11/2010
-Added Backup /data/app-private
-Show /data/app size, prompt user for continue
-Additional messages added to improve user experience
v0.1.1 - 11/10/2010
-First Release
-Backup and Restore /data/app
Installation:
WARNING: This steps must be completed as listed, failure to do so may result in unexpected errors which I am not responsible for.
1. Enable USB debugging and make sure Sdcard is mounted on phone
1. adb push apps.sh /data
2. adb shell
3. cd /data
4. chmod 775 apps.sh
5. ./apps.sh
a. Follow the onscreen directions
6. Reboot and proceed to wipe and reflash
7. On boot, wait between 5 and 10 minutes depending on how many apps you have before logging into your account. (30 apps takes about 4-5 minutes)
8. Login to your account
9. Droid 2/X Bootstrapper -> Bootstrap Recovery
10. Enable USB debugging and make sure Sdcard is mounted on phone
11. adb shell
12. tar -xzpf /sdcard/savemyapp/backup.tgz
FAQS:
Market isn't showing apps!
settings->applications->Manage Applications->All->Market->Force Stop, Clear data
Why is there a MACOSX file when I extract the archive?
Because I am lazy and I zipped it using Mac's built in archiver.
The script isn't working right away!
Redownload the newest script, just to make sure
Disclaimer:
You may repost this, but you must quote it as is.
I will only be responding to the threads I started on the Xda-Developers forums.
First!
I'm just holding a parking spot for this post!
What a great idea...thank you for developing this, im so tired of re downloading my apps back and setting everything up...done it about 10 times in the past month between sbfing and updating the fission rom several updates in a row so thank you...will most definitely be using this when I flash roms in the future. Thanks again
Sent from my DROID2 using XDA App
Excellent program! I'm having trouble getting it to work unfortunately. When apps.sh begins to copy files from /data/apps, I get errors saying "No space left on device" after every single file it tries to copy. This is of course not true since this D2 has over 6 gigs free on the system storage.
I am running this through the window's command prompt, but I don't see much in the code that won't run on windows aside from "du" which isn't even relevant unless my app + app-private folders combined size is over 120 MB (it's not).
I'm also running Epic 2.5 if that has anything to with this.
Any ideas? Am I just doing this terribly wrong?
Thanks!
tildaSparky said:
Excellent program! I'm having trouble getting it to work unfortunately. When apps.sh begins to copy files from /data/apps, I get an error saying "No space left on device." This is of course not true since this D2 has over 6 gigs free on the system storage.
I am running this through the window's command prompt, but I don't see much in the code aside from "du" which can't run with windows.
Any ideas? Am I just doing this terribly wrong?
Thanks!
Click to expand...
Click to collapse
If you read the first post it states the /preinstall folder can only hold only 120mb so it you have more than that to backup it won't fully work..I'm guessing that's were the apps are being saved...
Sent from my DROID2 using XDA App
turkeybuzzard said:
If you read the first post it states the /preinstall folder can only hold only 120mb so it you have more than that to backup it won't fully work..I'm guessing that's were the apps are being saved...
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Apps are normally saved in /data/app this script copies those apks to /preinstall so that after a wipe they will automatically be installed on the first boot. Yes /preinstall is limited to about 120MB.
tildaSparky said:
Excellent program! I'm having trouble getting it to work unfortunately. When apps.sh begins to copy files from /data/apps, I get an error saying "No space left on device." This is of course not true since this D2 has over 6 gigs free on the system storage.
I am running this through the window's command prompt, but I don't see much in the code aside from "du" which can't run with windows.
Any ideas? Am I just doing this terribly wrong?
Thanks!
Click to expand...
Click to collapse
Do you get the "No space left on device" message instantly or after some apks were copied to the /preinstall folder?
Here's what I get
Working…
cp: /preinstall/app/com.google.android.apps.maps-1.apk: No space left on device
cp: /preinstall/app/com.google.android.apps.translate-2.apk: No space left on device
cp: /preinstall/app/com.google.android.gm-1.apk: No space left on device
cp: /preinstall/app/com.google.zxing.client.android-2.apk: No space left on device
etc.
=(
tildaSparky said:
Here's what I get
Working…
cp: /preinstall/app/com.google.android.apps.maps-1.apk: No space left on device
cp: /preinstall/app/com.google.android.apps.translate-2.apk: No space left on device
cp: /preinstall/app/com.google.android.gm-1.apk: No space left on device
cp: /preinstall/app/com.google.zxing.client.android-2.apk: No space left on device
etc.
=(
Click to expand...
Click to collapse
How big is your /data/app folder?
OK! I sort of have it fixed. In that I'm not getting my original error.
What I did (which in retrospect was not such a hot idea) was delete the /preinstall/ folder and then created a new one with the subfolders /app/ and /md5/. The logic behind was that I saw the script had nothing in it to clean out the original preinstall folder, and I noticed that it had silly things like NFS in it. As I said, in retrospect I should have just deleted specific items from the folder, but that's what I get for acting without thinking too much.
How bad do you think it is that I remade the preinstall folder from scratch?
Now my preinstall folder is properly populated (I think). But the data won't back up for some reason. I think it might have something to do with the if statements being broken. I'm gonna go ahead and modify your script to bypass the if/else statements and see what happens.
SaveMyApp v0.1.2
By csscmaster3
Your app folder takes up
du: not found
If your app folder is more then 114MB I don't recommend continuing
do you want you to continue? (y/n)y
y
[[: not found
Working…
ignore No such file or directory error if you get it
tee: not found
SaveMyApp has completed your apps
Do you want to backup your data? (y/n)y
y
[[: not found
SaveMyApp has completed.
As an aside my app folder is 28 MB and my app-private folder has only the apkinstaller.
tildaSparky said:
OK! I sort of have it fixed. In that I'm not getting my original error.
What I did (which in retrospect was not such a hot idea) was delete the /preinstall/ folder and then created a new one with the subfolders /app/ and /md5/. The logic behind was that I saw the script had nothing in it to clean out the original preinstall folder, and I noticed that it had silly things like NFS in it. As I said, in retrospect I should have just deleted specific items from the folder, but that's what I get for acting without thinking too much.
How bad do you think it is that I remade the preinstall folder from scratch?
Now my preinstall folder is properly populated (I think). But the data won't back up for some reason. I think it might have something to do with the if statements being broken. I'm gonna go ahead and modify your script to bypass the if/else statements and see what happens.
SaveMyApp v0.1.2
By csscmaster3
Your app folder takes up
du: not found
If your app folder is more then 114MB I don't recommend continuing
do you want you to continue? (y/n)y
y
[[: not found
Working…
ignore No such file or directory error if you get it
tee: not found
SaveMyApp has completed your apps
Do you want to backup your data? (y/n)y
y
[[: not found
SaveMyApp has completed.
As an aside my app folder is 28 MB and my app-private folder has only the apkinstaller.
Click to expand...
Click to collapse
The NFS removal is a good call, I will append the script to check the /preinstall folder and prompt to remove the files there
The reason you are having trouble with this script looks it be like because you are not running it on the phone itself...meaning to say you are not running it via a terminal emulator on the phone nor are you running it via adb shell. The backup uses tar, which isn't on windows by default.
Actually I'm running everything through the adb shell. It's puzzling to me too. My terminal emulator for some reason doesn't have root access. At this point I think I'm just going to SBF anyway.
At any rate, I just decided to pull /data/data/ from my phone onto my HD and I will replace it after I reflash and install my programs, but before I log into my google account. Do you see any reason for this not to work?
tildaSparky said:
Actually I'm running everything through the adb shell. It's puzzling to me too. My terminal emulator for some reason doesn't have root access. At this point I think I'm just going to SBF anyway.
At any rate, I just decided to pull /data/data/ from my phone onto my HD and I will replace it after I reflash and install my programs, but before I log into my google account. Do you see any reason for this not to work?
Click to expand...
Click to collapse
Hmmm, you might have to check your superuser app to see if you accidently are denying su access. In adb shell do you have a $ or a #?
Backing up the /data/data folder to your HD then restoring might not work because I am not sure if it will retain the owner, permissions, etc.
I had a # in my shell. There was something slightly wonky about my root I think. At any rate my backup method didn't work so well (as you predicted) - it caused timeriffic to force close when I tried to load in my old settings via /data/data/.
I will try using this again once I've got my shiny new Fission 2.1 set up as I want.
Thanks for your attentiveness!
I'm guessing this script should be run AFTER all of the applications have been installed. Is this correct?
wsfanatic said:
I'm guessing this script should be run AFTER all of the applications have been installed. Is this correct?
Click to expand...
Click to collapse
That is correct
Sent from my DROID2 using XDA App
Ooooo this is getting popularrrr
Is this D2 specific, or would it work on any phone?
theimpaler747 said:
Is this D2 specific, or would it work on any phone?
Click to expand...
Click to collapse
It works with the D2 and should work with the DX, anything else is use at your own risk, if it does work let me know though
csscmaster3 said:
It works with the D2 and should work with the DX, anything else is use at your own risk, if it does work let me know though
Click to expand...
Click to collapse
Might risk it and try it on my hero Regardless, nice work
theimpaler747 said:
Might risk it and try it on my hero Regardless, nice work
Click to expand...
Click to collapse
The only problem I could forsee would be the /preinstall folder being different or something, if you do end up trying the script could you let me know the size of the /preinstall folder?

[Q] XT720: App2SD gets destroyed after Factory Reset?

Hey guys,
Can some one confirm this for me?
So i installed App2SD (as App2Card is a little panicky at times, it works when it feels like, and not when it doesn't like it), it works great until the point you decides to do a Factory Reset (because AOS will not allow you to delete the 1st account you used to sign up to the phone), and then if you try to reinstall the hundreds of apps that fit in properly before, now they don't go to the SD but instead they remains in the internal memory storage space.
That's understandable in a way, but the annoying thing is, if you try to install.sh again to re-apply App2SD then it complains that the ext2.ko file is already there and wont do anything.
the only way i've found to get around that is to reFlash the ROM, which is a major pain in the back. as you will need to reRoot, reOptimize, reEverything again...
Is there any easier way to reEnable App2SD after a Factory Reset?
Have anyone tried this?
Settings > Privacy > Factory Data Reset
after that, if you install apps from Market they will not get installed to SD, it'll just stay in the phone internal memory.
if you run the install.sh again from the App2SD script, it complains that the ext2.ko is already there and it wont do anything.
I'm very new to to this but my guess is that the files are still on the SD. I would try backing up anything you want to keep from the sd card & then reset up the SD card from scratch again before trying to run the script.
HTH
Flash your phone with RSDLite and then use the script. To answer your question, yes, factory reset does screw with APP2SD.
AG,
Have you tried sh install.sh -f
last time, it works for me. if it's not working for you, just open the install.sh file with a text editor and comment out the line that install the ext2.ko file. then, run the script again.
spiderx_mm said:
AG,
Have you tried sh install.sh -f
last time, it works for me. if it's not working for you, just open the install.sh file with a text editor and comment out the line that install the ext2.ko file. then, run the script again.
Click to expand...
Click to collapse
ohhh.. yeah -force, i'll try that again and see how it goes.
that is way better than having to Reflash the ROM every time, just to be able to do the App2SD
the XT720 is an awesome phone, the only flaw i can see in the phone is the boot up time is horribly looooong, it takes forever to boot up, everything else is perfect.
Update:
it did not work same error
Code:
Installing APPS2SD, please wait...
insmod: init_module '/system/lib/modules/ext2.ko' failed (File exists)
Error loading ext2.ko, exiting script ...
seems like the only way is to keep flashing the ROM then do everything from scratch
So just reflash then?

[HOW TO] Fully Backup & Restore Android Device

NOTE:
I'm not a developer or something even near to that. I'm a newbie and will be, seems so. All information provided here is copied and compiled from different internet sources. This information is according to best of my knowledge and comprehension and is just for curious souls like me who want to understand things in quite simple words.
I have tested this on different devices. I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Encrypted memory may cause problem in backing up and restoring data. So better decrypt it before proceeding. Or the Recovery should support decryption of /data partition.
WHY YOU NEED TO BACKUP YOUR DATA
For security, in case if device is lost. Read here more about the risks.
If you are going to change your device.
If your device is running out of memory space.
If your device is slowing down or giving random errors and you want a clean start i.e. by factory data reset.
If you are upgrading your Factory Firmware or ROM (OS).
If you are a curious soul like me and interested in experimenting with device.
WHAT TO BACKUP
Backup is a broad term used in many contexts.
PERSONAL DATA
On an android device, backing up personal data like pictures, music, videos, documents, e-books etc. means backing up Internal Memory (/data/media/) and SD card (if you use one). If you have disabled internal memory (D.I.M), your SD Card would be working as Internal Memory.
Personal data might be created by apps (like Camera, Facebook, WhatsApp etc) or imported from internet or other devices by yourself.
APPS & APPS DATA
If you are upgrading your ROM permanently, you might be interested in backing up your apps and their data as well. So that you don't lose important data and don't have to install apps again. System apps are stored in different folders under /system/ while user apps under /data/.
Apps typically store their data in /data/data/ but it's not a rule. Many apps save / backup their data on Internal Memory and/or SD Card as well. That's why you see folders named 'Android', 'data' etc. on Internal Memory and SD Card. Also, there are numerous folders named after app names. These folders may contain Personal Data as well, created by that certain app.
Contacts and messages are also stored in their default apps' data folder i.e. in /data/data/ and are not usually backed up manually.
OPERATING SYSTEM & APPS & APPS DATA
If you are going to install new ROM temporarily, you may want a complete backup so that you don't have to go through the hassle of installing apps and setting up / personalizing your device again. It usually includes /system, /boot and /data partitions.
OS consists of SYSTEM and BOOT. While user apps & apps data is stored in DATA.
PARTITION IMAGES
From a developer's perspective, one may want to backup the whole device partitions, in case if something goes wrong during experimenting.
Read here more about android partitions.
WHERE TO BACKUP
INTERNAL MEMORY (/sdcard) (/storage/sdcard0) (/data/media/0)
This memory can be used to save data if you are not going to wipe / clean it. A Factory Data Reset usually doesn't wipe this but it can. It depends on the device. Similarly, Recoveries usually don't wipe internal memory but you can manually do so. However, formatting /data would certainly erase internal memory. Formatting might be a part of flashable zip if you are going to install new ROM. Flashing Factory Firmware using flasher will also erase internal memory.
EXTERNAL SD CARD (/external_sd) (/storage/sdcard1)
This is a more safer place to save / backup data because it is not wiped unless done manually or accidentally.
PERSONAL COMPUTER (USB Flash drive or Internal / External Hard Disk)
This is the safest place to keep data with abundant space and the least chances of losing / corrupting data.
ONLINE / CLOUD STORAGE
Some apps, including Google offer backing up your data online and auto-synchronizes it. You should certainly avail this option particularly for sensitive and light weight data like contacts, messages, documents, saved passwords, bookmarks, financial transactions etc. WhatsApp also has a good online backup option. You can use apps like Drive, SMS Backup & Restore, FolderSync, KeepSafe etc. to better utilize this option. But technically, this is a limited option.
HOW TO BACKUP
FILE EXPLORER APPS
You can use a file explorer like ES Explorer or Solid Explorer to manually copy files from, say, Internal Memory to SD Card to back it up.
BACKUP APPS
Some default apps have built-in feature to backup data and settings locally and online e.g. GO-SMS, Tasker etc. You can check apps for this feature.
Also, special backup apps like Titanium Backup can backup almost all of your user and system apps and their data. It can also backup contacts, messages, device settings etc. It can create a flashable zip of backed up data to flash through recovery. However, backups from one ROM may not fully work with other ROM's.
CUSTOM RECOVERY
Backing up data when ROM is running isn't safe. When files are being used by OS, they might not be written / read sometimes. So, a custom recovery is the best option to backup/restore data. Custom recoveries (TWRP/CWM) can backup / restore partitions SYSTEM, BOOT and DATA (excluding internal memory) for sure. Some new recoveries offer backing up more (or all) partitions on device. You can choose where to save backup files i.e. Internal Memory or SD Card. Then you can transfer these files to PC as well.
You can also use recovery's File Explorer to copy Internal Memory to SD Card. However, it's a slower process if you have a large number of files to backup.
PC
You can use PC in multiple ways to backup/restore data within device or from/to PC.
First of all, you will often come across different software advertised on net claiming to fully backup your device when connected to PC. They work but are not much useful / reliable according to my experience. Give them a try, if you want to.
Secondly, you can use USB cable to directly connect your device (as MTP in ROM or recovery) to PC or use apps like Wi-Fi File Transfer to wirelessly connect (in ROM) and then explore Internal Memory and SD Card. FTP or SFTP (SSH) server may also be setup on Android to remotely access it from PC if both are on same network.
Thirdly, you can mount SD Card as flash drive (UMS in ROM) or switch off your device, remove SD Card and then insert directly into PC through card reader to manually copy files. This method is faster, to copy large data. However, mounting as UMS in running ROM isn't recommended, particularly if you are using D.I.M. It will crash apps.
In Android 5+ UMS may not be available in USB settings as it has been deprecated in favor of MTP to avoid problems. However, to copy large data from internal SD card is really problematic without direct USB connection. Or what if we need to recover accidentally deleted data from internal memory? We can directly attach internal memory (as in UMS) to PC by a little hacking.
Fourthly and ultimately, like a boss , you can use life saving ADB feature of android to backup/restore your data as well as recovering your device from difficult situations and doing a lot of stuff. It's the best and fastest method to backup Internal Memory to SD Card and then restore (COPY WHOLE FOLDER (within device)). Or you can COPY WHOLE FOLDER (From/To PC) or COPY WHOLE PARTITION IMAGE (within device) or BACKUP / RESTORE APPS & DATA (From/To PC) in seconds.
Read here more about android partitions.
Another application that you can use to backup your phone to computer is Apowersoft Phone Manager. This works greatly in managing your devices plus it make sure that all your files are secured from being corrupted or loss.
doublematteo said:
Another application that you can use to backup your phone to computer is Apowersoft Phone Manager. This works greatly in managing your devices plus it make sure that all your files are secured from being corrupted or loss.
Click to expand...
Click to collapse
I can't determine the efficiency of the Apowersoft tool, but if you want to backup data , this is right way , after the phone data is backuped ,you don't have to worry about the deleted data unable be recovered back ,
The backup files is the best way to recover deleted data from phone
Kindly guide me on restoring app data alone from a nandroid to newer version of an app..
The scenario is that ,I upgraded to a higher android OS but find some of my apps(with no cloud storage),restored from my nandroid ,crashing; probably prompted by the change in OS.
I downloaded the compatible version of the app from playstore,but am clueless how to sync restored app data from nandroid to this version.
DIGVIJAY24 said:
Kindly guide me on restoring app data alone from a nandroid to newer version of an app..
The scenario is that ,I upgraded to a higher android OS but find some of my apps(with no cloud storage),restored from my nandroid ,crashing; probably prompted by the change in OS.
I downloaded the compatible version of the app from playstore,but am clueless how to sync restored app data from nandroid to this version.
Click to expand...
Click to collapse
Would you please mention apps names? Don't uninstall previous version. Just install compatible version over it. It should automatically have previous app data.
The backup program is much simpler than the android recovery program,
I came here looking for the best way to back up my internal storage before activities like flashing a new ROM or firmware. Previously, I'd plug my phone into my PC and just drag and drop the internal storage partition to a folder on my computer, but I'd often have to do it a few times because some file would get hung up, or the phone would randomly disconnect (even though my phone, cables, and computer are all new and high quality).
I'm currently using the TWRP file explorer to copy /sdcard to /external-sd/!InternalBackup, but there is no running log or progress indicator... So, this approach is less than ideal.
I'm still looking for the best method (not necessarily a software that will do it for me) that will do it fast, not get interrupted, and provide good feedback on if it's working and how much longer it will take. (The TWRP method above checks the first 2 criteria, but the 3rd is woefully insufficient.
I'm thinking that the best way to back up the internal SD will be in recovery, otherwise something might be in use and will halt the process.
Any suggestions?
DrPhant0m said:
I came here looking for the best way to back up my internal storage before activities like flashing a new ROM or firmware. Previously, I'd plug my phone into my PC and just drag and drop the internal storage partition to a folder on my computer, but I'd often have to do it a few times because some file would get hung up, or the phone would randomly disconnect (even though my phone, cables, and computer are all new and high quality).
I'm currently using the TWRP file explorer to copy /sdcard to /external-sd/!InternalBackup, but there is no running log or progress indicator... So, this approach is less than ideal.
I'm still looking for the best method (not necessarily a software that will do it for me) that will do it fast, not get interrupted, and provide good feedback on if it's working and how much longer it will take. (The TWRP method above checks the first 2 criteria, but the 3rd is woefully insufficient.
I'm thinking that the best way to back up the internal SD will be in recovery, otherwise something might be in use and will halt the process.
Any suggestions?
Click to expand...
Click to collapse
Commandline solutions are always best. You have better control over them. Use TWRP built-in terminal to run commands.
Simply 'cp' with verbose option "-v" is what fulfills your needs. 'rsync' is better if you want to save time by automatically skipping unchanged existing files. If you want to preserve file attributes and permissions, use 'tar'. Added compression can be achieved by 'xz' or '7za'. All of these commands are stable solutions, with high speed and ability to handle/resume broken/interrupted operations.
TWRP comes with busybox bundled. Busybox utilities have limited functionality and mostly suffice the need but rarely we face unexpected behavior. Instead you can use full static binaries of these commands.
Typing lengthy commands in TWRP shell terminal is somewhat challenging. Either use 'adb shell' or for repeated use, create a shell script and place it in internal memory or SD card. Or you can unpack TWRP image and save script in /sbin directly to run it just as a normal command. Another easy way is to create a flashable zip of your script. This way you can also see progress bar moving if you write a proper script for it.
Hope it helped.
mirfatif said:
Commandline solutions are always best. You have better control over them. Use TWRP built-in terminal to run commands.
Simply 'cp' with verbose option "-v" is what fulfills your needs. 'rsync' is better if you want to save time by automatically skipping unchanged existing files. If you want to preserve file attributes and permissions, use 'tar'. Added compression can be achieved by 'xz' or '7za'. All of these commands are stable solutions, with high speed and ability to handle/resume broken/interrupted operations.
TWRP comes with busybox bundled. Busybox utilities have limited functionality and mostly suffice the need but rarely we face unexpected behavior. Instead you can use full static binaries of these commands.
Typing lengthy commands in TWRP shell terminal is somewhat challenging. Either use 'adb shell' or for repeated use, create a shell script and place it in internal memory or SD card. Or you can unpack TWRP image and save script in /sbin directly to run it just as a normal command. Another easy way is to create a flashable zip of your script. This way you can also see progress bar moving if you write a proper script for it.
Hope it helped.
Click to expand...
Click to collapse
That's a lot of help... But I lack the basic understanding and experience to make use of it all. I'll have to Google it a bit and look at some examples. Thanks!
UPDATE: I did a little research, and I succeeded in using "cp" to do a test move in TWRP (I had to use -r and -v), but even using -v didn't create a progress bar or any indication that files were being moved. It just finished and went to the next new line. Is this expected?
Also... my version of TWRP doesn't seem to have rsync available. When I try to use rsync in TWRP, I get
Code:
sh: rsync: not found
So it seems that TWRP's terminal doesn't have rsync. I'm using TWRP 3.0.2-1
So... I'm currently using the Termux app to do the cp operation. I'd prefer to use rsync, which is supported in Termux, however, unless I do "su" first, it says it doesn't have access to the destination folder. And, when I use "su" I can't use rsync. I get pretty much the same message as when I try to use it in TWRP... something like "rsync not found"
Does this mean that when Termux is using root, it can't use rsync? Does that make sense?
Any help?
Thanks!
DrPhant0m said:
I did a little research, and I succeeded in using "cp" to do a test move in TWRP (I had to use -r and -v), but even using -v didn't create a progress bar or any indication that files were being moved. It just finished and went to the next new line. Is this expected?
Click to expand...
Click to collapse
'cp -r' copies recursively i.e. files/directories under directories and so on. So it's definitely required if you want to copy directories. 'cp -v' shows each file which is being copied, but not the progress during a single file copying. Check 'cp --help' for options.
Also... my version of TWRP doesn't seem to have rsync available. When I try to use rsync in TWRP, I get
Code:
sh: rsync: not found
So it seems that TWRP's terminal doesn't have rsync. I'm using TWRP 3.0.2-1
Click to expand...
Click to collapse
TWRP uses busybox which doesn't have rsync built-in. You can get a copy of static (independently working) rsync binary from many sources like this. Aarch64 will be a bit faster. Check 'getrpop | grep ro.product.cpu' to find your CPU architecture if it's 64-bit or 32. When in TWRP, place binary in /sbin directory. Then do 'chmod 0777 /sbin/rsync' to make it executable. Now you can use rsync. 'rsync --help' will show you options and basic help. Do note, /sbin is on volatile filesystem i.e. it will be gone on reboot. Don't expect it to be permanently there. You can also use rsync from other locations like sd card but that will need to call binary with full path and filesystem may put restrictions on execution.
So... I'm currently using the Termux app to do the cp operation. I'd prefer to use rsync, which is supported in Termux, however, unless I do "su" first, it says it doesn't have access to the destination folder. And, when I use "su" I can't use rsync. I get pretty much the same message as when I try to use it in TWRP... something like "rsync not found"
Does this mean that when Termux is using root, it can't use rsync? Does that make sense?
Click to expand...
Click to collapse
It's expected. When we do 'su' on Termux, it's environment is gone and PATH is set to /system/bin etc. So any binaries which Termux downloaded to /data/data/com.termux/files/usr/bin won't work. There are better options, but easiest is to use 'tsu' instead of 'su' on Termux. It will handle things for you to run Termux binaries in superuser mode. Do 'apt install tsu' when connected to internet. Once installed, simply execute 'tsu'. Now you can use Termux rsync binary.
Or use rsync static bianry instead as explained above. Copy rsync to /system/bin/ or /system/xbin/ etc. and set permissions. SELinux may interfere if it's set to "Enforcing". Do 'getenforce' to check and 'setenforce 0' to set it "Permissive".
DrPhant0m said:
That's a lot of help... But I lack the basic understanding and experience to make use of it all. I'll have to Google it a bit and look at some examples. Thanks!
UPDATE: I did a little research, and I succeeded in using "cp" to do a test move in TWRP (I had to use -r and -v), but even using -v didn't create a progress bar or any indication that files were being moved. It just finished and went to the next new line. Is this expected?
Also... my version of TWRP doesn't seem to have rsync available. When I try to use rsync in TWRP, I get
So it seems that TWRP's terminal doesn't have rsync. I'm using TWRP 3.0.2-1
So... I'm currently using the Termux app to do the cp operation. I'd prefer to use rsync, which is supported in Termux, however, unless I do "su" first, it says it doesn't have access to the destination folder. And, when I use "su" I can't use rsync. I get pretty much the same message as when I try to use it in TWRP... something like "rsync not found"
Does this mean that when Termux is using root, it can't use rsync? Does that make sense?
Any help?
Thanks!
Click to expand...
Click to collapse
This reply is probably a bit late for you, but...
If you install tsu (pkg install tsu) in TermUX and use tsu rather than su, it'll work.
Tsu sets up the runtime context for su properly.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
This reply is probably a bit late for you, but...
If you install tsu (pkg install tsu) in TermUX and use tsu rather than su, it'll work.
Tsu sets up the runtime context for su properly.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Hey, it's never too late to refine your backup strategy. Thanks for letting me know.
I installed tsu in Termux, and when it finished, I tried to use rsync with su, and got the same "rsync: not found" error. Please see the following output, with my entries in Bold[/B].
Code:
$ [B]pkg install tsu[/B]
[COLOR="Gray"][I]~~
~~[LOTS OF LINES DETAILING THE INSTALLATION OF TSU]~~
~~[/I][/COLOR]
Setting up tsu (1.1)...
$ [B]su[/B]
elsa:/data/data/com.termux/files/home # [B]rsync[/B]
sh: rsync: not found
127|elsa:/data/data/com.termux/files/home #
*** Though I did enjoy watching the movie with my son, I did not pick the name Elsa for my device. That's just what LG called the carrier-free V20, Model US996.
Am I doing something wrong? To be clear.. I just did "rsync" without any commands/switches to see if it would produce the help info. I knew it wouldn't actually attempt to copy anything.
DrPhant0m said:
Hey, it's never too late to refine your backup strategy. Thanks for letting me know.
I installed tsu in Termux, and when it finished, I tried to use rsync with su, and got the same "rsync: not found" error. Please see the following output, with my entries in Bold[/B].
*** Though I did enjoy watching the movie with my son, I did not pick the name Elsa for my device. That's just what LG called the carrier-free V20, Model US996.
Am I doing something wrong? To be clear.. I just did "rsync" without any commands/switches to see if it would produce the help info. I knew it wouldn't actually attempt to copy anything.
Click to expand...
Click to collapse
Lol! You missed the key point: use tsu instead of su.
Instead of typing "su", type "tsu".
But don't take it too hard - I did the same thing when I first started.
Sent from my OnePlus3T using XDA Labs
Got it. Worked just fine. Thanks!
DrPhant0m said:
I installed tsu in Termux, and when it finished, I tried to use rsync with su, and got the same "rsync: not found" error. Please see the following output, with my entries in Bold[/B].
Click to expand...
Click to collapse
I mentioned to use 'tsu' instead of 'su' but probably you missed that.
mirfatif said:
When we do 'su' on Termux, it's environment is gone and PATH is set to /system/bin etc. So any binaries which Termux downloaded to /data/data/com.termux/files/usr/bin won't work. There are better options, but easiest is to use 'tsu' instead of 'su' on Termux. It will handle things for you to run Termux binaries in superuser mode. Do 'apt install tsu' when connected to internet. Once installed, simply execute 'tsu'. Now you can use Termux rsync binary.
Click to expand...
Click to collapse
/data/data/com.termux/files/bin/tsu is just a wrapper i.e. a shell script that sets environment variables for Termux and then executes 'su'.
mirfatif said:
I mentioned to use 'tsu' instead of 'su' but probably you missed that.
/data/data/com.termux/files/bin/tsu is just a wrapper i.e. a shell script that sets environment variables for Termux and then executes 'su'.
Click to expand...
Click to collapse
I see it now. I gave a thanks, though admittedly late. Sorry!
Is backup feasible when sd external card has been mounted extending the internal storage (Android 6.0), working as internal storage as well?
Can some expert comment on this, just not to go crazy for nothing. I don't want to upgrade with last rom by manufacturer and lose my data.
I have ADB , fastboot and usb drivers, but trying and use Helium backup I was unable to pair, even though the phone is connected (I can select onscreen for instance PTP or usb storage, tried both, nothing).
Not even sure about nandroid backup also.
HeyRicardo said:
Is backup feasible when sd external card has been mounted extending the internal storage (Android 6.0), working as internal storage as well?
Can some expert comment on this, just not to go crazy for nothing. I don't want to upgrade with last rom by manufacturer and lose my data.
I have ADB , fastboot and usb drivers, but trying and use Helium backup I was unable to pair, even though the phone is connected (I can select onscreen for instance PTP or usb storage, tried both, nothing).
Not even sure about nandroid backup also.
Click to expand...
Click to collapse
Yes it's feasible but depends on what, how and where you want to backup.
mirfatif said:
Yes it's feasible but depends on what, how and where you want to backup.
Click to expand...
Click to collapse
Any solution is fine to me, I just want to be able to restore apps and launcher (Nova launcher prime) with icons arranged as they are, without having to start all over from scratch.
Other data are on the cloud, so if I can possibly backup some folder (from phone or sd card, if the difference matter in my case) good, or I'll take care of it in advance.
Just having the phone upgraded but not reset from the beginning.
If necessary I can try rooting it. Thx for replying.
how to use a twrp data backup for oder rom?

Categories

Resources