Database Users

Back up applications on non-apps2sd phone?

I've chosen not to use app2sd on my phone for various reasons and although I'm satisfied with my decision, flashing new roms has become quite a chore given the fact that I can't wipe without destroying all of my applications as well.
I've taken to using programs, but even using programs is a pain due to the long installation process. I'm currently using TI Package Installer.
Is there any way to backup and restore all applications (protected included) via adb shell or something in the recovery console?
I'm sorry if this has been asked and answered before, but I did a search and could not find anything specifically answering my question.
I'm running a Mytouch3g without a2sd with the newest AmonRa recovery.

I found this info on the following link:
http://forum.xda-developers.com/showthread.php?t=601567
So kudos to swissp:
backing up normal (public) apps:
adb shell cp -r -f /data/app/*.* /sdcard/backups/apps
private apps:
adb shell cp -r -f /data/app-private/*.* /sdcard/backups/apps

DullTree said:
I found this info on the following link:
http://forum.xda-developers.com/showthread.php?t=601567
So kudos to swissp:
backing up normal (public) apps:
adb shell cp -r -f /data/app/*.* /sdcard/backups/apps
private apps:
adb shell cp -r -f /data/app-private/*.* /sdcard/backups/apps
Click to expand...
Click to collapse
Going to make a nandroid backup and try this out. Thanks! Hoping it takes when I send them back.
Edit: Seems to have worked perfectly. For some reason i figured something that simple wouldn't work or it'd be included in Amon RA. Thanks!

My pleasure

If you then want to reinstall all the apps at once :
1. Mount the SD Card on the PC
2. Open a cmd window in the Android SDK\Tools folder and launch this
for %I in ("I:\backups\apps\*.apk") do adb install "%I"
(Replace I: with your mounted SD card's drive letter)
Quite useful

swissp said:
If you then want to reinstall all the apps at once :
1. Mount the SD Card on the PC
2. Open a cmd window in the Android SDK\Tools folder and launch this
for %I in ("I:\backups\apps\*.apk") do adb install "%I"
(Replace I: with your mounted SD card's drive letter)
Quite useful
Click to expand...
Click to collapse
Excellent. Thanks!

[Q] chmod: operation not permitted

I rooted a NookColor with the AutoNooter for 1.0.1 (root, softkeys, google apps) and installed Ubuntu according to this guide. Then I updated to 1.1 (of course). I also have clockwork recovery with backups
Anyways, for some unknown reason: my friend was having problems signing into the market. So I had her erase and de-register. This also apparently removes root. So I used AutoNooter for 1.1. Everything seems to work fine except that YouTube wouldn't launch (which was fine because I signed into it before AutoNooter).
I then uninstalled and pushed YouTube on the device.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell rm /system/app/Youtube.apk
adb push YouTube.apk /system
adb reboot
The old version of YouTube then worked just fine (didn't use "adb uninstall" because it didn't work). I then installed other non-market apps.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p6 /data
adb shell rm /data/app/$APPNAME
adb push $APPNAME /data
adb reboot
Some of these apps wouldn't launch [ :'( ]. All of this was done using ADB over Wifi. Anyways, I tried to run bootubuntu (via ConnectBot) and it didn't work. So I figure I out to rerun the script "sh ./ubuntu.sh" and got several "chmod: operation not permitted" errors. I also ran "su" before each command for superuser permission of course. Therefore, I'm not able to boot ubuntu (even though it's still all on the sdcard).
So am I only partially rooted or what? Should I run AutoNooter for 1.1 again?

AVanover5 said:
I rooted a NookColor with the AutoNooter for 1.0.1 (root, softkeys, google apps) and installed Ubuntu according to this guide. Then I updated to 1.1 (of course). I also have clockwork recovery with backups
Anyways, for some unknown reason: my friend was having problems signing into the market. So I had her erase and de-register. This also apparently removes root. So I used AutoNooter for 1.1. Everything seems to work fine except that YouTube wouldn't launch (which was fine because I signed into it before AutoNooter).
I then uninstalled and pushed YouTube on the device.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell rm /system/app/Youtube.apk
adb push YouTube.apk /system
adb reboot
The old version of YouTube then worked just fine (didn't use "adb uninstall" because it didn't work). I then installed other non-market apps.
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p6 /data
adb shell rm /data/app/$APPNAME
adb push $APPNAME /data
adb reboot
Some of these apps wouldn't launch [ :'( ]. All of this was done using ADB over Wifi. Anyways, I tried to run bootubuntu (via ConnectBot) and it didn't work. So I figure I out to rerun the script "sh ./ubuntu.sh" and got several "chmod: operation not permitted" errors. I also ran "su" before each command for superuser permission of course. Therefore, I'm not able to boot ubuntu (even though it's still all on the sdcard).
So am I only partially rooted or what? Should I run AutoNooter for 1.1 again?
Click to expand...
Click to collapse
First off:
Changing the ROM =/= "rooting". Stop confusing people.
Also, is your friend on ubuntu, or just you? I don't see a correlation.

ace7196 said:
First off:
Changing the ROM =/= "rooting". Stop confusing people.
Also, is your friend on ubuntu, or just you? I don't see a correlation.
Click to expand...
Click to collapse
I realize that. Autonooter does, in fact, root the device. It's my friends.

SOLVED
The NookColor has been sleeping for a while (because I ate dinner) and Ubuntu now works >.< I'm not sure what's up with the apps, but maybe they'll install and launch now. I'll try clearing their caches and what not as well. If anyone has suggestions, feel free to post them.

AVanover5 said:
I realize that. Autonooter does, in fact, root the device. It's my friends.
Click to expand...
Click to collapse
So you running ubuntu has nothing to do with anything? Cool.
Run autonooter again. If apps don't show, just install them from system/app folder. Also fix permissions.

ace7196 said:
So you running ubuntu has nothing to do with anything? Cool.
Run autonooter again. If apps don't show, just install them from system/app folder. Also fix permissions.
Click to expand...
Click to collapse
No, Ubuntu runs off of the SD through VNC. It's not a ROM. I've fixed it already anyways...

ace7196 said:
So you running ubuntu has nothing to do with anything? Cool.
Run autonooter again. If apps don't show, just install them from system/app folder. Also fix permissions.
Click to expand...
Click to collapse
I'm having similar problems with my HTC first But I'm not good w/ coding, so it's a user defect. I can't chmod and so I can't get the device to stay rooted. Some apps can get su and many cannot. Superuser also cannot get su. ??? Any advice?

[CM9A0] Superuser app no longer crashes in setting

Built a version of Superuser.apk from the github source to make preferences work. All I've done is remove the code that checks for a new version. It works perfectly now.
http://dl.dropbox.com/u/19946299/Superuser.apk
Directions:
1. Uninstall your current version of Superuser with:
adb remount /system
adb shell rm -f /system/app/Superuser.apk
2. Install new one using adb
adb install Superuser.apk
Or
adb push Superuser.apk /system/app/Superuser.apk
Alternatively you can remove your current Superuser.apk with a root system file manager and install the new one the same way.
I've also put in the issue with ChainsDD on his issues list and where I found it, seems to be to do with the waiting thread when it requests the current su binary version.

Thanks for the post. I'm wondering, and yes I've searched plenty on XDA and RootzWiki, will this fix su issues all around? For example, using TB 4.0.2 sends my CM9 TP into a reboot. I've read this may be an issue with Busybox.
Any insight anyone?

I don't think it's busybox and the exact point that Superusers waits for the su binary to return the version number. The actual command works 100% OK, you can do the exact same commands in shell and it's fine. It seems to be something to do with the actual java exec thread. TB has the same issue, where as other backup apps (ultimate backup) do not, and they still call su binary. I'm still trying to figure it out.

GavChap said:
adb shell rm -f /system/Superuser.apk
Click to expand...
Click to collapse
change to:
Code:
adb shell rm -f /system[COLOR="Red"]/app[/COLOR]/Superuser.apk
thanks
edit: and i had to push the su app instead of install

Good job...works nice. Did you commit ur change to source so future builds will be free from this bug? If not, commit to either evervolv or cm...or detail the change in source and I can.
Thanks
Sent from classicnerd ICS Touchpad

Thanks....this did not fix the crash/Reddit issue with TiBU current version...installed and launched TiBU, and it froze and then rebooted my TO, tried it two times.

Working now. Reset it and installed good to go

Redflea said:
Thanks....this did not fix the crash/Reddit issue with TiBU current version...installed and launched TiBU, and it froze and then rebooted my TO, tried it two times.
Click to expand...
Click to collapse
This is a workaround rather than a fix. The su binary is fine. There is a kernel issue that causes the crash. The logs I have state it's with the msm ioctl code.
There are other root using apps that don't crash at all.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App

TMan459 said:
Thanks for the post. I'm wondering, and yes I've searched plenty on XDA and RootzWiki, will this fix su issues all around? For example, using TB 4.0.2 sends my CM9 TP into a reboot. I've read this may be an issue with Busybox.
Any insight anyone?
Click to expand...
Click to collapse
This doesn't fix the SU problems, just the Superuser front end.

Thanks for the tips.
I replaced my Superuser.apk with yours and now I can get into the settings without FC.
I used root explorer to replace the files but I also had to changed the permissions of your version of the superuser.apk to match the other files (rw-r--r--) to work properly.
One thing I noticed that even though I can get in to settings in SU, I still cannot update the binaries. If scans for updates but when I ask it to actually update the binary, it reboots the TP.
Thanks anyways...

There is a bugfix kernel coming from the CM team soon that'll fix these issues, I've tested the fix on my kernel and it's working fine.

So I just updated my kernel (bricked-kernel 2.6.35) to fix the TIBU issues and as a side benefit, my SU no longer reboots the TP when I try to update the binaries. It finds the update and tries to apply the update. It returns an "update failed" message, but it no longer hard reboots my TP.
I think it's getting closer to being perfect... ^_^

You can try my kernel if you like
http://dl.dropbox.com/u/19946299/uImage.CyanogenMod
download onto your computer, boot into ClockworkMod
Then do the following using adb on the computer
adb mount /boot
(optional) adb shell mv /boot/uImage.CyanogenMod /boot/uImage.CyanogenMod.old
adb push uImage.CyanogenMod /boot/uImage.CyanogenMod
adb umount /boot
adb reboot

GavChap said:
You can try my kernel if you like
http://dl.dropbox.com/u/19946299/uImage.CyanogenMod
download onto your computer, boot into ClockworkMod
Then do the following using adb on the computer
adb mount /boot
(optional) adb shell mv /boot/uImage.CyanogenMod /boot/uImage.CyanogenMod.old
adb push uImage.CyanogenMod /boot/uImage.CyanogenMod
adb umount /boot
adb reboot
Click to expand...
Click to collapse
Is this based off just the CM team or do you also use the commit's from Bricked-Kernel?

I had to re-copy the superuser.apk after the alpha 0.5 update. I will say with the 0.5 update and this adjustment, all is well. Couldn't be happier.

Best thing to do about Superuser if you get force close on setting in CM9A0.5 is to remove the Superuser app using Titanium Backup or root explorer. Then install the one from the Android Market, settings works 100% now. I think the one in CM90.5 is an older version.

Good tip! Worked for me on .5 and can now use TB from market. Thanks.

Possible new way to ROOT

New possible root method on Thinkpad tablet forums, by OPDECIRKEL. He needs help testing it out.
look here and lets cross our fingers =D
http://www.thinkpadtabletforums.com...nt/yareftpt-yet-another-root-exploit-for-tpt/

opdecirkel released the exploit -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/

unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
***EDIT***
updated script worked!

-=HOLLYW00D=- said:
unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
Click to expand...
Click to collapse
Not sure if it can help you, but try checking the TPT forum thread again, there has been some advances and troubleshooting going on

Moved To General​
As the first post is just a link and contains no development, this has no place in this section​

updated -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
Someone thinkpadtabletforum reported that it worked for him.

updated script worked for me! cwm installed fine as well!

I achieved root with the new method on OTA 2.5. Also installed CWM with no issues. Works great.
Sent from my PC36100 using Tapatalk

I can confirm it worked!
I had to update first because the "Disable Battery Discharge" option was not there. (I guess my Tablet stopped getting OTA updates since I was on ThinkPadTablet_A310_02_0024_0065_US... Also, you have to update one at a time, you can't go from 24_65 straight to 37_75. Also, I stopped at 39_86 since I was impatient.)
I like this once since we can see how it worked rather than blindly running some guys program (I never tried the first root.)

I can also confirm the new method to be working. Just rooted my 0089_WE TPT. Works like a charm

I am quoting the following post (i don't have privilege to post there): forum.xda-developers.com/showpost.php?p=23902281&postcount=64
daswahnsinn said:
I unrooted and then updated, now I can't root. I updated the SDK and made sure I have the proper drivers needed. So I take back my easy comment. I'll keep trying I might just manually push the files back.
Click to expand...
Click to collapse
How did it fail? At which stage and what error did you get?

Okay, I'll try and flash the oldest update zip, and it fails as it should, then I wipe the cache part, reboot, and I hit enter when I gets to the unlock screen then the CMD window closes.
EDIT: I spent a good hour or so combing through my PC and these forums and tried both methods a lot, and this one finally worked. It wouldn't let me get to the /cache/recovery/pwn/su part of the script. Thank you all for your support.

I have problems...
Hi all,
Apologizes for my english, too bad to discuss this kind of issues. Sorry in advance.
I had the "fantastic" idea to update the firmware some weeks ago, when I was SU. After this, I've lost most of capabilities!
I tried to follow the procedure, but I cannot reach 'root' in any case. I have version WE089. Downloaded US060, but there's only 065 for Western Europe. I got both, just in case..
Unfortunately, in the first step it failed I'm not able to update anything. The process crashes when is loading old firmware, either US060 or WE065.
I've realised that during the process I loose the USB link connection (when I reboot), and the system tries to install again and again the driver. If the TPT is running in recovery mode, it seems that is not connected via USB... If I have the tablet in "normal use", I see it through the Windows Desktop.
Other question: should I disconnect the Internet connection?
I guess other requirements are right (ADBD, debugging mode,...). It's really annoying, it took me a lot of hours and I haven't found any solution.
Can anybody help me? What I'm doing wrong?
Cheers!
jm
W7 64bits - TPT WE089

@jm
goto device manager. right click on Android device. reinstall device driver.
This worked for me in recovery when the device was not recognized.
Edit: look here: http://forum.xda-developers.com/showthread.php?t=1471106&page=2

What do you mean with loosing the connection? Is the adb driver installed correctly? Where did you get it from? Is it an genuine lenovo driver? If so, than you shouldn't worry!
Perhabs it's the MTP driver, that is missing when you boot into recovery? If it's the adb driver, than you should try jlove's method.
In addition I wanted to inform you, that the new method worked for me, too! Even with some complications... by this way, thanks again to opdecirkel!
Because the run.bat script did't worked correctly, I had to do it manually. So I put the "yareftpt" on C:\\, started cmd.exe, booted the TPT into recovery and changed the directory in cmd.exe with "cd.." to "cd yareftpt" ...followed the instructions with the update...
echo 4. Reboot in RECOVERY: (shutdown the tablet, then start it and press volume + few times until it starts in recovery)
echo 5. Go to apply update, select the update from the sdcard and try to apply it. It will fail, but that is OK.
echo 5. Then, go to 'WIPE CACHE PARTITION' and select it (navigate with volume buttons and select it with power button),
echo 6. When wipe cache complete, press (here) ^<ENTER^>.
and after that I copied the first line of the script into cmd and executed. I did it line after line, just to the next step. (dark green= copy line after line, paste and execute)
adb shell "/system/bin/mkdir /data/local/pwn"
adb shell "/system/bin/mkdir /data/local/pwn-bak"
adb shell "/system/bin/cat /system/etc/install-recovery.sh > /data/local/pwn-bak/install-recovery.sh.orig"
adb shell "/system/bin/mkdir /cache/recovery/pwn"
adb push su /cache/recovery/pwn
adb shell "/system/bin/rm /cache/recovery/log"
adb shell "/system/bin/ln -s /system/etc/install-recovery.sh /cache/recovery/log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -oremount,rw -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache/recovery\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chown root /cache/recovery/pwn/su\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 4777 /cache/recovery/pwn/su\" >> /tmp/recovery.log"
echo 7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete press (here) ^<ENTER^>
pause
some of commands might cause failures, but don't worry and just go on
adb shell "/system/bin/rm /cache/recovery/log"
echo 8. On the device, select REBOOT. When startup COMPLETE press (here) ^<ENTER^>
pause
adb push Superuser.apk /data/local/pwn/Superuser.apk
adb push busybox /data/local/pwn/busybox
adb push su /data/local/pwn/su
adb push pwn-in.sh /data/local/pwn/pwn-in.sh
adb shell "/system/bin/chmod 777 /data/local/pwn/pwn-in.sh"
echo Your PC command prompt appears next. Do the following things:
echo 1. adb shell
echo when '$' (adb shell) appear, do:
echo 2. /cache/recovery/pwn/su
echo when '#' appears. You are root. run the following:
echo 3. /data/local/pwn/pwn-in.sh
now you should try if you have su, even if you don't see in your app list..
download root checker, install, open and try it!
You should have root right now.
In my case, i had root, but no CWM!
So I had to install in manually, but with root it should't be a problem. you only have to download the correct cwm version:
http://forum.xda-developers.com/showpost.php?p=21916505&postcount=71
then I installed it with the Android Terminal Emulator app, because the cmd.exe method did't worked for me. You should just follow the instructions:
or you can copy img file on /data/local/ folder of your tablet (with a file manager with root permissions)
launch "Android Terminal Emulator" application
and tape the instructions
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/NameOfCWMFile.img of=/dev/block/mmcblk0p1
http://www.thinkpadtabletforums.com...nd-development/clockworkmod-recovery-for-tpt/
After a shutdown and reboot into recovery I had cwm! So I am able to do nandroid backups...
In this way, I would particularly like to thank to all devs that made the TPT root possible! Now i like my TPT 1000% more than before...e.g. no status-bar in lecture notes -> sooo great!!

I do get the following error maybe someone can help me out
[*]
[*]
[*]
/system/bin/mkdir: not found
/system/bin/mkdir: not found
cannot create /data/local/pwn-bak/install-recovery.sh.orig: directory nonexisten
t
/system/bin/mkdir: not found
699 KB/s (22364 bytes in 0.031s)
/system/bin/rm: not found
/system/bin/ln: not found
7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete
press (here) <ENTER>
Drücken Sie eine beliebige Taste . . .
it cant find the mkdir command very strange

I'm a little rusty, but are the / and \ facing the correct way? And are you in the correct directory? Not found usually means path is incorrect.

@rangercaptain
thats the commands from the root script. I didnt change them.
the commands are send over from adb shell and the tablet is in root directory i think.
When i go into shell and type in ls i get access denied error.

and you load the update zip and wiped cache before typing the commands, right? You have to do this every time you try to root...
Try to do it with another method. Don't do it directly trough adb shell...just type the shell commands in the cmd.exe
You just have to chance the directory in cmd, before executing the commands.
Then try not to input 'adb shell' before the shortened command, but the whole command as one line like:
adb shell "/system/bin/mkdir /data/local/pwn"
Perhabs it will work..?!?

@neos
yes i do the same procedure.
I also tried over cmd with adb shell "command" and also in shell.
Always the same error.
I looked into the system/bin directory and mkdir does have filesize of 0kb...

Help: Is there an Windows app that can backup the Streak ROM as an image file?

Hi,
Is there an app that you can run from a Windows XP laptop that can backup a Dell Streak ROM Image as a single file to a hard drive?
My apologies if this has been asked before, but I seem to only find backup apps that run on the device itself.
Thanks.
PS: Assuming if this is not possible, what is the best way to backup to a laptop hard drive?

me4tux said:
Hi,
Is there an app that you can run from a Windows XP laptop that can backup a Dell Streak ROM Image as a single file to a hard drive?
My apologies if this has been asked before, but I seem to only find backup apps that run on the device itself.
Thanks.
PS: Assuming if this is not possible, what is the best way to backup to a laptop hard drive?
Click to expand...
Click to collapse
You have to flash either StreakMod or ClockworkMod recovery and from there you do a nandroid backup and then copy that to your PC
Sent from my cm_tenderloin using Tapatalk HD

cdzo72 said:
You have to flash either StreakMod or ClockworkMod recovery and from there you do a nandroid backup and then copy that to your PC
Sent from my cm_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
Thanks for you reply. That's the step I wanted to avoid by installing a custom recovery.
So I suppose there is no other easier way if I just have a stock Streak with the stock Dell recovery?

me4tux said:
Thanks for you reply. That's the step I wanted to avoid by installing a custom recovery.
So I suppose there is no other easier way if I just have a stock Streak with the stock Dell recovery?
Click to expand...
Click to collapse
Nothing at all. There are non root apps that will allow you to backup your user apps and their settings but anything related to the system will have to be manually reconfigured because your not rooted more than likely either. And those don't work well either.
Sent from my cm_tenderloin using Tapatalk 2

He could do a system dump using ADB, but to do so he would...
...have to be rooted.
...have busybox installed.
...have to determine where the system partitions are (e.g. /dev/mnt/nanda for /system).
From there he could then execute the commands in a command prompt. For example, to do a system dump on my el cheapo Coby tablet, I use the following commands:
Code:
adb.exe wait-for-device
adb.exe shell mkdir /sdcard/dump
adb.exe shell su -c "cat /dev/block/nanda > /sdcard/dump/bootloader.img"
adb.exe shell su -c "cat /dev/block/nandc > /sdcard/dump/boot.img"
adb.exe shell su -c "cat /dev/block/nandg > /sdcard/dump/recovery.img"
adb.exe shell su -c "busybox tar -czvf /sdcard/dump/system.tgz /system"
mkdir dump
adb.exe pull /sdcard/dump dump
Putting it all together into a single file though is not going to happen. Besides, installing ClockworkMod or StreakMod and doing a nandroid backup through it is the best means of backing up the Streak.