Related
I am sure that many of the new people in here are not exactly sure how to use ADB under linux.
So Ive been reading the Evo 3D forum, and I found this really nice guide by vboyz103. You can find the thread HERE
All props go to vboyz103 for creating it, im just sharing it with you guys.
P.S. - I found it in the Android Development forum, so Im putting it in ours. If it does not belong here - MODs - please move it to General.
vboyz103 said:
So I have been reading quite a few threads here on XDA, and the one thing I noticed for noobs to linux/unix world is that they are struggling with some basic command once adb shell is gained. I decided to whip out this quick tutorial to help those noobs out to become more of an expert...like me...lol j/k
Here we go:
Prerequisites:
You must know how to invoke a adb shell command already to drop into your phone.
ALL commands in Unix/Linux are case sensitive
For more details, go to this ADB tutorial (very good one): http://forum.xda-developers.com/showthread.php?t=517874
Let's get going:
Once a shell is gained via adb, let's look at some of the basic commands you can do to navigate around the filesystem. Note: you must remove the double-quotes (") for the actual command.
Code:
"cd" = is change directory
to change to any directory, you type: cd dir_name (where dir_name is a full path)
Example: I want to go to /data/local/tmp in my phone, I would do
cd /data/local/tmp <hit ENTER>
You can also use the ".." to go UP one directory.
Example: I'm in /data/local/tmp and I want to go up to /data folder, a command would be: cd ../.. alternatively, if I do cd .. then i'll drop into /data/local folder instead.
Code:
"ls" = list files/directories
to list files/directories within a folder, the command should be:
ls <hit enter> => this will list all NON-HIDDEN file/directories within your CURRENT directory.
ls /data/local/tmp => this will list all NON-HIDDEN file/directories within /data/local/tmp directory.
ls -l => this will list all NON-HIDDEN file/directories within your CURRENT directory, plus additional details. Consider this is like a "Details" view in Windows Explorer.
ls -a => this will list all files/directories (including hidden files) within your CURRENT directory.
ls -la => this will list all files/directories (including hidden files) within your CURRENT directory, plus details.
Code:
"chmod" = change mode
Goes to wikipedia for more details: https://secure.wikimedia.org/wikipedia/en/wiki/Chmod
Most commonly used modes on android phones are:
"755" or "777".
So if you have a root.sh shell script that you downloaded from XDA, and uploaded to your phone and try to execute it with ./root.sh and it said "Permission denied". That means your script does not have the execute permission. You need to do:
chmod 755 root.sh <hit enter>
[B]IMPORTANT: There is *NO* negative sign (-) in front of the mode bit. So it is NOT chmod -755 root.sh[/B]
If you get a "File or directory not found" error, which means you are chmod-ing a file that doesn't exist in your current directory. To execute a chmod on root.sh in /data/local/tmp you do:
chmod 755 /data/local/tmp/root.sh
If you want to chmod an ENTIRE DIRECTORY and ALL files underneath it you do:
chmod -R 755 /data/local/tmp => this will set /data/local/tmp and ALL files/folders underneath it to be 755.
Code:
"chown" = change ownership
Go to wikipedia for details: https://secure.wikimedia.org/wikipedia/en/wiki/Chown
Most common used chown for android is: "root:root" or "root:shell"
Example: if you want to change ownership of root.sh to root:shell then you do:
chown root:shell root.sh
NOTE: the -R (recursive) option is also available for chown.
chown -R root:shell /data/local/tmp
Code:
"pwd" = print working directory
so when you are within a directory and you want to know which directory you are in, then you issue the command:
pwd <hit enter>
The system will reply back with the currently directory you are in.
I'll try to add more if I think of anything else useful, or if you have suggestions, please feel free to add.
Click to expand...
Click to collapse
This is the new OTA update of droid 2 global.
winoz said:
This is the new OTA update of droid 2 global.
Click to expand...
Click to collapse
No known official root method is out at the moment. In the meantime you can try SuperOneClick or MotoFail
Seemingly does not work, but to no avail motofail
so I m guessing you HAD root, and lost it after updating? Can you confirm this?
More Info
I can confirm that. I had root and now, after receiving the update this morning, I do not.
I opened Superuser, entered Preferences, and scrolled down to the General section to tap on Su binary to check for updates (or even reapply my current binary, which is v3.0.3.2). Since my version is the latest version I clicked the button Update anyway. Superuser reports the following:
This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager.
Click to expand...
Click to collapse
I tried Pete's Motorola Root Tools (v1.06) to see if I could re-root, but no joy. Step three (the step that adds su, busybox and superuser) fails with the following message:
ERROR: adb could not be granted root access via local.prop method
Try again from the start, but if the problem continues, check your version of Gingerbread -- hopefully you don't have a version where this exploit was fixed.
Click to expand...
Click to collapse
It seems like perhaps the exploit has been patched. Here is the log from Pete's Tools at that point:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
$ su
rm /data/local/12m.bak
$ /system/xbin/su
fi
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
$ exit
$ exit
$ exit
(success)
> mv /data/local/12m /data/local/12m.bak
(success)
> ln -s /data /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
$ exit
$ exit
$ exit
(success)
> mv /data/local/12m.bak /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
$ exit
$ exit
$ exit
(success)
> mv /data/local.prop /data/local.prop.bak
> echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
> echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
$ mv /data/local.prop /data/local.prop.bak
failed on '/data/local.prop' - Permission denied
$ echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ exit
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /system/bin/su ];
> then
> rm /system/bin/su
> fi
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /system/bin/su ];
> then
> rm /system/bin/su
> fi
$ exit
$ exit
$ exit
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /system/sbin/su ];
> then
> rm /system/sbin/su
> fi
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /system/sbin/su ];
> then
> rm /system/sbin/su
> fi
$ exit
$ exit
$ exit
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> exit
> exit
$ su
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ exit
$ exit
$ exit
(success)
Anybody have any other ideas?
The phone is asking constantly to update. It just releases a timer that, if you are not watching it, will update without user consent. I disabled background data to no avail.
Is there any way to block the phone from installing the OTA automatically? I really prefer having root than to update.
XT311 3.2.4 Almost cracked it !! ??
I'm New around here and would love to get this sorted for the XT311. I got mine today and spent 6hrs trying all sorts.. Im a unix boy.... Old school and kinda liked getting back into it.. Ok i have some info
''The ro.sys.atvc_allow_all_adb property is a Motorola-specific configuration that prevents ADB from dropping its root privileges. Reboot the device one final time, and on logging in with “adb shell”, you should be presented with a root prompt''
Is this specific param our problem on Motorola device and not completing for all the same reasons.. All these root tools are failaing over the same lame Mount issue...
Im on SuperOneClick and the Exploit Pluggin for Motofail lol...
Hope we get the 311 rooted again soon.... those infamous Jap files are hard to track .....
barbaroja said:
Is there any way to block the phone from installing the OTA automatically? I really prefer having root than to update.
Click to expand...
Click to collapse
The list of files responsible for OTA updates:
/system/app/BlurUpdater_VZW.apk
/system/app/BlurUpdater_VZW.odex
/system/etc/security/otacerts.zip
Got it rooted !!
Model: Moto XT311
Ver: UK Motorola 'Fire'
Running: v2.3.4
Kernel: Apps_2.6.32.9
Build Number: 4_40C_4067
Here is how i did it to the letter... Even at times i questioned the sequence but it worked.. These instructions are formulated from various sources.. Before you begin unzip the main Zip file I have uploaded and then unzip all the contained zips to one folder. Call the folder Root and put it on your main drive ie(C:/). Ensure that the infamous FXX_PR3_NV.xml is in the root folder..
INSTRUCTIONS:-
Before Rooting:
Prepare your phone by doing the following:
- Go to Settings > Applications > CHECK "Unknown Sources"
- Go to Settings > Applications > Developer > CHECK "USB Debugging" and "Stay Awake"
- Connect your phone via USB, when prompted DO NOT select USB Mass Storage.
1. download and UN-compress all files. on your phone, choose application setting->development->enable "USB debugging", then connect your phone with your pc with USB cable and install driver automatically.
2. install SUT1.75 & RSD LiTE by Motorola which include drivers.
3. Run SUT1.75, choose FXX_PR3_NV.xml. Make sure you select file open option XML from drop down in file open menu.
4. Run cmd > adb shell (if your ROOT folder is located in c:\, then change directly to c:\ROOT, type adb shell), wait untill "#" appear, then you can minimise the cmd window.
5. Open RootD3 folder, run RootD3_zhCN.cmd,
Phone will reboot 3 times. After the 1st reboot, please check if the 2nd reboot starts automatically, if not, unplug the USB cable and plug it again, Goto step 5 again and complete when the 3rd reboot is done.
6. Go into SuperOneClick folder, run SuperOneClick.exe, press Root.
Force a connection with USB drivers. The software will automaticaly do this. The program will now executed and run with NO ERRORS.
After it says it is completed, check if you have the Skull Android icon ( Get SUuperUser APP) Now look in the menu, if Confirmed, your phone has been rooted.
I can't upload any files or provide links as im new round here..
I HAVE ALL FILES/SOFTWARE NEEDED FOR THIS PROCEDURE !!!
79.5 MB (83,442,583 bytes)..
BrB in next few ours with a link up to the DL Locations..
Hack build.prop
I'm trying to prevent this update OTA currently.
Is there a way to modify build.prop to trick the phone in to thinking it has already been updated?
Perhaps if someone who has had the update can post their build.prop we can figure out which properties have changed.
If you edit build.prop phone cant update. All i did was change 0 to 1 so I can have 5 bars for gsm signal and it didn't want to finish the update.
Maybe matie... This is my next job on my XT311 before i plug it into the web..
I found this may be of some use..
down vote accepted
TO STOP AUTO UPDATES
Remove SystemUpdater.apk from /system/app. From terminal (with ADB)
Code:
adb pull /system/app/SystemUpdater.apk C:/Path/to/your/desktop //Backup the file (just in case)
adb remount //Remount the system partition to read-write
adb shell rm /system/app/SystemUpdater.apk //Remove the apk
Warning - this will permanently disable system updates, until you push SystemUpdater back to /system/app
OR If your running different motorola look in the app for Updaters
Code:
adb pull /system/app/Upgrader.apk C:/Path/to/your/desktop //Backup the file (just in case)
adb remount //Remount the system partition to read-write
adb shell rm /system/app/Upgrader.apk //Remove the apk
This is MotoIII example..
Hope this helps....
Well I figured myself how to prevent the phone from upgrading. In fact it was easy.
1. You need titanium backup.
2. Freeze "upgrader" app.
3. Wipe its data. If you do not wipe, the order remains alive (in my case it already had started to download) and is taken by the downloader and it will continue to download and update the phone.
Thats it. Hope it helps.
It seems its similar to the solution above, only without involving adb.
UberSteiner said:
Got it rooted !!
Model: Moto XT311
Ver: UK Motorola 'Fire'
Running: v2.3.4
Kernel: Apps_2.6.32.9
Build Number: 4_40C_4067
Click to expand...
Click to collapse
Do you realise that you're in the DROID2 GLOBAL forum section?
Super One Click root method does not work for 4.5.629.
Rootkeeper
Just tested this. Install voodoo rootkeeper from market before updating. Root seems to work so far.
bummer that there's no way to SBF back. My device auto-updated on me.
i'm assuming that none of this matters if you're on a different rom. i'm using miui so my phone won't auto update right?
Custom ROMs naturally do not support VZW's OTA update mechanism as they're incompatible.
Stock ROM with /system/app/BlurUpdater_VZW.apk renamed also doesn't.
Stock ROM with CWM installed or bloatware frozen is incompatible with the update, however the phone will download and try to install it, only to fail and repeat that again 2 hours later.
Tried freezing 'Upgrader'
I tried freezing 'Upgrader' from titanium backup and wiping the data - this did not work for me.
The update was still downloaded. It has, however, not yet been installed.
Can anyone help me to
1. remove the download before it installs.
2. block this OTA upgrade after removal
I'd appreciate the help to prevent this thing from being unrooted.
Thanks
The update is downloaded to /cache. You can delete it from there.
To disable automatic updates, rename the following files:
/system/app/BlurUpdater_VZW.apk
/system/app/BlurUpdater_VZW.odex
/system/etc/security/otacerts.zip
by adding .bak on the end of their names.
Recently, I flashed CM10 to my phone. Since I bumped into the brightness problem, someone told me to run
Code:
echo 0,0,0,0,0,0,0 > /sys/class/leds/lcd-backlight/als/curve
and it did work.
So I wrote this script into /data/local/userinit.sh and hope it will automaticly edit the brightness level after every boot, but it didn't.
I'm sure I'm using userinit.sh correctly because I managed to run some other scripts like "echo test > /data/local/test.txt".
Is there any way to run this script correctly at startup? Or can I just edit the file permanently?
/*=========================================*/
Resolved by myself
It seems that the system will restore the file at startup after running the user script.
so just:
Code:
chmod 777 /sys/class/leds/lcd-backlight/als/curve
cat /data/local/curve > /sys/class/leds/lcd-backlight/als/curve
chmod 444 /sys/class/leds/lcd-backlight/als/curve
I've saved "0,0,0,0,0,0,0" to /data/local/curve
I tried
Code:
chmod 777 /sys/class/leds/lcd-backlight/als/curve
echo 0,0,0,0,0,0,0 > /sys/class/leds/lcd-backlight/als/curve
in the userinit.sh
Didn't work as well
I flash KDZ,TOT but it not work
When finish flashing, LG Logo and reset and LG Logo(reboot) and reset.
TOT - FBoot check failed
KDZ - WParam error
SerenityS said:
I flash KDZ,TOT but it not work
When finish flashing, LG Logo and reset and LG Logo(reboot) and reset.
TOT - FBoot check failed
KDZ - WParam error
Click to expand...
Click to collapse
try this, Chapter 3 Using ADB as solution. Sorry , my English too bad, so it's all i can find for you.Hope you can countinue with CM rom.
Source: http://forum.xda-developers.com/showthread.php?t=1660596
ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the samsung logo.
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is just after the Galaxy S Plus logo, so just when the bootanimation starts. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example (requires adb.exe and the 2 dlls)
Code:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb push mycwmfix.zip /sdcard/mycwmfix.zip
adb reboot recovery
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made.
You can also make an batch script that pushes the files automatically to your phone, here is an example:
Code:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb push framework-res.apk /system/framework/framework-res.apk
adb -d shell chmod 644 /system/framework/framework-res.apk
adb push SystemUI.apk /system/app/SystemUI.apk
adb -d shell chmod 644 /system/app/SystemUI.apk
adb reboot
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.
odatoshiie said:
try this, Chapter 3 Using ADB as solution. Sorry , my English too bad, so it's all i can find for you.Hope you can countinue with CM rom.
Source: http://forum.xda-developers.com/showthread.php?t=1660596
ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the samsung logo.
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is just after the Galaxy S Plus logo, so just when the bootanimation starts. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example (requires adb.exe and the 2 dlls)
Code:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb push mycwmfix.zip /sdcard/mycwmfix.zip
adb reboot recovery
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made.
You can also make an batch script that pushes the files automatically to your phone, here is an example:
Code:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb push framework-res.apk /system/framework/framework-res.apk
adb -d shell chmod 644 /system/framework/framework-res.apk
adb push SystemUI.apk /system/app/SystemUI.apk
adb -d shell chmod 644 /system/app/SystemUI.apk
adb reboot
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.
Click to expand...
Click to collapse
I try to anything for recovery my phone, but everything not work.
I think Some partition(Cant recover with TOT and KDZ) were broken.
SerenityS said:
I try to anything for recovery my phone, but everything not work.
I think Some partition(Cant recover with TOT and KDZ) were broken.
Click to expand...
Click to collapse
i think MR. Le Thanh Tung can help you. ask him about this problem
facebook.com/Tungkick777?fref=ts
SerenityS said:
I flash KDZ,TOT but it not work
When finish flashing, LG Logo and reset and LG Logo(reboot) and reset.
TOT - FBoot check failed
KDZ - WParam error
Click to expand...
Click to collapse
This is a Super Brick,i have the same Problem 2 Months ago,tungkick help me,but no change to repair this error.
I send my GP2 to Repair Station and he tell me,the Board is death.I have brought a new GP2.
R.I.P.
I think so too.
R.I.P.
ADB & FASTBOOT SAUCE V1.2
*YOUR WARRANTY IS ALREADY VOIDED*
*I AM NOT RESPONSIBLE FOR BRICKED DEVICES OR ANY OTHER DAMAGE*
* PLEASE USE THE README*
* YOU ARE THE ONE PRESSING THE BUTTONS SO DON'T BLAME ME*
This is for most devices and mainly for devices that are unlocked. This is also for most devices that use fastboot. This can be used with many devices as well. I have only tested on a few
It is a menu based batch file that combines many things from around this thread. It is also pretty self explanatory.
Update V1.2 FIXED Directory Issues Caused By Update v1.1 That I Missed
Update V1.1 added cmd prompt options for fastboot and adb. Also added fastboot oem unlock option.
README:
ALL THE CREDITS ARE LISTED BELOW, IF I MISSED ANY LET ME KNOW!
PLEASE READ EVERYTHING IN HERE AND ASK QUESTIONS IF THERE ARE ANY.
THE TWRP BACKUP AND RESTORE TOOL LOCATED AT OPTION 4 IS STILL
EXPERIMENTAL AND MIGHT NOT WORK. DO NOT RELY ON IT AS OF YET!
THIS IS TO BE RAN FROM RECOVERY, AS FROM ANDROID IS NOT WORKING
FOR ME. IT WILL PUSH THE BACKUPS FROM YOUR CHOICE AT THE MENU
TO THE SAME FOLDER AS THIS SCRIPT FILE IS LOCATED.
FOR THE RESTORE OPTION IT SEEMS TO HANG BUT ON TWRP IT SHOWS IT
COMPLETING. A CNTRL+C AFTER RESTORE COMPLETE SHOWS UP WILL
TERMINATE BATCH JOB AND PRESSING N WILL BRING YOU BACK TO THE MENU.
For Option 11 FASTBOOT FLASH RECOVERY You Can Substitute Any
Custom Recovery, But You Would Have To Rename It To twrp.img
As This Script Is Looking For That Particular Naming Convention.
This Is For Devices That Use Fastboot Only!
For Option 25 ADB SHELL After Your Done Using The Shell You
Can Type exit And It Will Allow You To Go Back To The Menu!
For Option 32 ADB SD-CARD INCREMENTAL BACKUP There Is An
ignore-list.ini File That Has Instructions To Ignore Specific
Folders To Not Sync. This Is Best Ran In Recovery Via ADB IMO.
ADB SD-CARD INCREMENTAL BACKUP Description
This Backs Up The Entire SDcard So That You Can Have A
Complete Snapshot Of Your Device When You Make Periodic
Backups, And Be Able To Restore Things Exactly As They Were.
CREDITS:
TWRP Backup And Restore Tool:
http://forum.xda-developers.com/showpost.php?p=71406861
Fb2Png:
https://github.com/PhilZ-cwm6/philz_touch_cwm6/tree/cm-11.0/fb2png
ADBSync:
http://forum.xda-developers.com/showthread.php?t=2133312
Cut, Grep, RM:
http://unxutils.sourceforge.net/
Zip:
http://forum.xda-developers.com/showthread.php?t=1207017
Batch Scripts For ADB Screenshot & SDcard Backup
[email protected] & A Little By Me!
https://forum.xda-developers.com/showthread.php?t=2239421
ADB and Fastboot Files:
..................................................................................................................................................................................................................
Copyright 2012 The Android Open Source Project.....................................................................................
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.........................................................................................................................................
...................................................................................................................................................................................................................
Android Screenshooter (fb2png) by Kyan He [email protected]
Maintained by Phil3759 & McKael @ xda-developers
TWRP Backup And Restore Tool v1.1 by dexbyte www.dexteroid.com
ADB Screenshot For Recovery By osm0sis @ xda-developers & A Little By Me!
https://forum.xda-developers.com/showthread.php?t=2239421
ADB Sync Utility Copyright (c) Temblast 2012-2014
By Renate NST @ xda-developers
SDcard Backup Automation By osm0sis @ xda-developers & A Little By Me!
https://forum.xda-developers.com/showthread.php?t=2239421
Secondary Download : Will add once thoroughly tested.
Version Info
Update V1.2 FIXED Directory Issues Caused By Update v1.1 That I Missed
Update V1.1 added cmd prompt options for fastboot and adb. Also added fastboot oem unlock option.
bryantjopplin said:
Version Info
Update V1.2 FIXED Directory Issues Caused By Update v1.1 That I Missed
Update V1.1 added cmd prompt options for fastboot and adb. Also added fastboot oem unlock option.
Click to expand...
Click to collapse
Nice work! Automation saves lives :angel:.
kirito9 said:
Nice work! Automation saves lives :angel:.
Click to expand...
Click to collapse
Have you used it? I am adding fastboot oem lock and fastboot flashing unlock / lock. There is an added MoaAB ADBlocker getting worked in as of now and last night I completed to sd card restore option. Still working on zip aligning apks and optimizing ogg's.
bryantjopplin said:
Have you used it? I am adding fastboot oem lock and fastboot flashing unlock / lock. There is an added MoaAB ADBlocker getting worked in as of now and last night I completed to sd card restore option. Still working on zip aligning apks and optimizing ogg's.
Click to expand...
Click to collapse
Haven't used it as yet, was on Linux. Hoping for a Linux version soon.
kirito9 said:
Haven't used it as yet, was on Linux. Hoping for a Linux version soon.
Click to expand...
Click to collapse
Well I might have to let someone else do that haha, I really have been reading and learning as I go, not sure how hard it is to turn into a sh. I started out doing something for the s4 to flash Loki bootloaders that I got lucky on making them with Loki patch, then went on to the HP touchpad and make some custom things for it. Then at work I made some enhancements for our CCTV software and used the same format as the others. That's when this started as I seen everything separated and not as one throughout the web, so I just added as I found interesting things. Some of my own design and code but a lot help from others. Just trial and error until it worked across all my devices.
Sent from my Pixel XL using Tapatalk
bryantjopplin said:
Well I might have to let someone else do that haha, I really have been reading and learning as I go, not sure how hard it is to turn into a sh. I started out doing something for the s4 to flash Loki bootloaders that I got lucky on making them with Loki patch, then went on to the HP touchpad and make some custom things for it. Then at work I made some enhancements for our CCTV software and used the same format as the others. That's when this started as I seen everything separated and not as one throughout the web, so I just added as I found interesting things. Some of my own design and code but a lot help from others. Just trial and error until it worked across all my devices.
Click to expand...
Click to collapse
That's cool as I have a dual boot setup. That's generally how those big tools begin, a side project leading to greater things.
---------- Post added at 05:29 PM ---------- Previous post was at 05:09 PM ----------
bryantjopplin said:
Well I might have to let someone else do that haha, I really have been reading and learning as I go, not sure how hard it is to turn into a sh. I started out doing something for the s4 to flash Loki bootloaders that I got lucky on making them with Loki patch, then went on to the HP touchpad and make some custom things for it. Then at work I made some enhancements for our CCTV software and used the same format as the others. That's when this started as I seen everything separated and not as one throughout the web, so I just added as I found interesting things. Some of my own design and code but a lot help from others. Just trial and error until it worked across all my devices.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Check this out when you have time. Really good stuff.
kirito9 said:
That's cool as I have a dual boot setup. That's generally how those big tools begin, a side project leading to greater things.
---------- Post added at 05:29 PM ---------- Previous post was at 05:09 PM ----------
Check this out when you have time. Really good stuff.
Click to expand...
Click to collapse
That's pretty sweet, I think I got my zipalign working finally, omg I'm in over my head haha.
Sent from my Pixel XL using Tapatalk
You wouldn't happen to be able and tell me if you see anything wrong with this code so far? Man this one is a pain. lol
Code:
:ZIPALIGNAPK
CLS
ECHO.
ECHO Before You Start Make Sure Your Device Has USB Debugging Enabled!
ECHO.
ECHO Presented By: B-RAD
ECHO FOR ADB ^& FASTBOOT ONLY
ECHO CHOOSE BELOW
ECHO __________________________________________________________________
ECHO 41 - /system/app VIA ADB
ECHO.
ECHO 42 - /system/priv-app VIA ADB
ECHO.
ECHO 43 - /data/app VIA ADB
ECHO.
ECHO 44 - OPTIMIZE ALL APKS VIA ADB
ECHO.
ECHO 99 - OPTIMIZATION MAIN MENU
ECHO.
ECHO.
set /p M=Type Your Choice Then Press ENTER:
ECHO.
ECHO.
IF %M% == 41 (
ECHO.
CD /d "%~dp0FILES"
CLS
ECHO.
ECHO ZIPALIGNING APK'S FROM '\system\app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server
adb pull /system/app TEMP
del /Q /S *.so
call :subzipalign
ECHO PUSHING APK'S
adb remount
adb push TEMP /system/app
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP
ECHO.
ECHO ZIPALIGN COMPLETE
ECHO.
Pause
goto zipalignapk
)
IF %M% == 42 (
ECHO.
CD /d "%~dp0FILES"
CLS
ECHO.
ECHO ZIPALIGNING APK'S FROM '\system\priv-app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server
adb pull /system/priv-app TEMP
del /Q /S *.so
call :subzipalign
ECHO PUSHING APK'S
adb remount
adb push TEMP\priv-app /system/
pause
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP
ECHO.
ECHO ZIPALIGN COMPLETE
ECHO.
Pause
goto ZIPALIGNAPK
)
IF %M% == 43 (
ECHO.
CD /d "%~dp0FILES"
CLS
ECHO.
ECHO ZIPALIGNING APK'S FROM '\data\app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server
adb pull /data/app TEMP
del /Q /S *.so
del /Q /S *.odex
call :subzipalign
ECHO PUSHING APK'S
adb remount
adb push TEMP\app\ /data/
pause
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP
ECHO.
ECHO ZIPALIGN COMPLETE
ECHO.
CD /d "%~dp0"
Pause
goto zipalignapk
)
IF %M% == 44 (
ECHO.
CD /d "%~dp0FILES"
CLS
ECHO.
ECHO PREPARING FOR ZIPALIGN OF ALL APK'S
ECHO.
ECHO ZIPALIGNING ALL APK'S FROM '\system\app'
ECHO.
ECHO PULLINGS APKs...
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server >nul 2>&1
adb pull /system/app TEMP >nul 2>&1
del /Q /S *.so >nul 2>&1
call :subzipalign
ECHO PUSHING APK'S
adb remount >nul 2>&1
adb push TEMP /system/app >nul 2>&1
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP >nul 2>&1
ECHO.
ECHO.
ECHO ZIPALIGNING ALL APK'S FROM '\system\priv-app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server >nul 2>&1
adb pull /system/priv-app TEMP >nul 2>&1
del /Q /S *.so >nul 2>&1
call :subzipalign
ECHO PUSHING APK'S
adb remount >nul 2>&1
adb push TEMP\priv-app /system/ >nul 2>&1
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP >nul 2>&1
ECHO.
ECHO.
ECHO ZIPALIGNING ALL APK'S FROM '\data\app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server >nul 2>&1
adb pull /data/app TEMP >nul 2>&1
del /Q /S *.so >nul 2>&1
del /Q /S *.odex >nul 2>&1
call :subzipalign
ECHO PUSHING APK'S
adb remount >nul 2>&1
adb push TEMP\app\ /data/ >nul 2>&1
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP >nul 2>&1
ECHO.
ECHO ZIPALIGN COMPLETE
ECHO.
CD /d "%~dp0"
Pause
goto zipalignapk
)
IF %M% == 99 goto M6MENU
:subzipalign
@echo off
@echo Zip aligning now...
for /R %%X in (*.apk) do zipalign 4 "%%X" "%%~dpX%%~nX.new"
@echo Replacing non-aligned files with zip aligned files...
for /R %%X in (*.new) do move /Y "%%X" "%%~dpX%%~nX.apk"
@echo Zip aligning done, press any key to exit
pause
Goto :eof
kirito9 said:
That's cool as I have a dual boot setup. That's generally how those big tools begin, a side project leading to greater things.
---------- Post added at 05:29 PM ---------- Previous post was at 05:09 PM ----------
Check this out when you have time. Really good stuff.
Click to expand...
Click to collapse
bryantjopplin said:
You wouldn't happen to be able and tell me if you see anything wrong with this code so far? Man this one is a pain. lol
Click to expand...
Click to collapse
Lol, I'm sorry if I gave the impression that I know bash :"). I don't, I did but I didn't get into the advanced stuff. Maybe @Ricky Divjakovski can help.
kirito9 said:
Lol, I'm sorry if I gave the impression that I know bash :"). I don't, I did but I didn't get into the advanced stuff. Maybe @Ricky Divjakovski can help.
Click to expand...
Click to collapse
The /data/app seems to do fine, still testing on a new flash haha. I guess trial and error will tell. Thanks though!
bryantjopplin said:
The /data/app seems to do fine, still testing on a new flash haha. I guess trial and error will tell. Thanks though!
Click to expand...
Click to collapse
Good luck .
kirito9 said:
Good luck .
Click to expand...
Click to collapse
Shows to be good. Haha now for a reboot.
bryantjopplin said:
You wouldn't happen to be able and tell me if you see anything wrong with this code so far? Man this one is a pain. lol
Code:
:ZIPALIGNAPK
CLS
ECHO.
ECHO Before You Start Make Sure Your Device Has USB Debugging Enabled!
ECHO.
ECHO Presented By: B-RAD
ECHO FOR ADB ^& FASTBOOT ONLY
ECHO CHOOSE BELOW
ECHO __________________________________________________________________
ECHO 41 - /system/app VIA ADB
ECHO.
ECHO 42 - /system/priv-app VIA ADB
ECHO.
ECHO 43 - /data/app VIA ADB
ECHO.
ECHO 44 - OPTIMIZE ALL APKS VIA ADB
ECHO.
ECHO 99 - OPTIMIZATION MAIN MENU
ECHO.
ECHO.
set /p M=Type Your Choice Then Press ENTER:
ECHO.
ECHO.
IF %M% == 41 (
ECHO.
CD /d "%~dp0FILES"
CLS
ECHO.
ECHO ZIPALIGNING APK'S FROM '\system\app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server
adb pull /system/app TEMP
del /Q /S *.so
call :subzipalign
ECHO PUSHING APK'S
adb remount
adb push TEMP /system/app
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP
ECHO.
ECHO ZIPALIGN COMPLETE
ECHO.
Pause
goto zipalignapk
)
IF %M% == 42 (
ECHO.
CD /d "%~dp0FILES"
CLS
ECHO.
ECHO ZIPALIGNING APK'S FROM '\system\priv-app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server
adb pull /system/priv-app TEMP
del /Q /S *.so
call :subzipalign
ECHO PUSHING APK'S
adb remount
adb push TEMP\priv-app /system/
pause
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP
ECHO.
ECHO ZIPALIGN COMPLETE
ECHO.
Pause
goto ZIPALIGNAPK
)
IF %M% == 43 (
ECHO.
CD /d "%~dp0FILES"
CLS
ECHO.
ECHO ZIPALIGNING APK'S FROM '\data\app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server
adb pull /data/app TEMP
del /Q /S *.so
del /Q /S *.odex
call :subzipalign
ECHO PUSHING APK'S
adb remount
adb push TEMP\app\ /data/
pause
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP
ECHO.
ECHO ZIPALIGN COMPLETE
ECHO.
CD /d "%~dp0"
Pause
goto zipalignapk
)
IF %M% == 44 (
ECHO.
CD /d "%~dp0FILES"
CLS
ECHO.
ECHO PREPARING FOR ZIPALIGN OF ALL APK'S
ECHO.
ECHO ZIPALIGNING ALL APK'S FROM '\system\app'
ECHO.
ECHO PULLINGS APKs...
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server >nul 2>&1
adb pull /system/app TEMP >nul 2>&1
del /Q /S *.so >nul 2>&1
call :subzipalign
ECHO PUSHING APK'S
adb remount >nul 2>&1
adb push TEMP /system/app >nul 2>&1
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP >nul 2>&1
ECHO.
ECHO.
ECHO ZIPALIGNING ALL APK'S FROM '\system\priv-app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server >nul 2>&1
adb pull /system/priv-app TEMP >nul 2>&1
del /Q /S *.so >nul 2>&1
call :subzipalign
ECHO PUSHING APK'S
adb remount >nul 2>&1
adb push TEMP\priv-app /system/ >nul 2>&1
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP >nul 2>&1
ECHO.
ECHO.
ECHO ZIPALIGNING ALL APK'S FROM '\data\app'
ECHO.
ECHO PULLING APK'S
IF exist TEMP rd /Q /S TEMP
mkdir TEMP
adb start-server >nul 2>&1
adb pull /data/app TEMP >nul 2>&1
del /Q /S *.so >nul 2>&1
del /Q /S *.odex >nul 2>&1
call :subzipalign
ECHO PUSHING APK'S
adb remount >nul 2>&1
adb push TEMP\app\ /data/ >nul 2>&1
ECHO CLEANING UP LOCAL TEMP FILES
rd /Q /S TEMP >nul 2>&1
ECHO.
ECHO ZIPALIGN COMPLETE
ECHO.
CD /d "%~dp0"
Pause
goto zipalignapk
)
IF %M% == 99 goto M6MENU
:subzipalign
@echo off
@echo Zip aligning now...
for /R %%X in (*.apk) do zipalign 4 "%%X" "%%~dpX%%~nX.new"
@echo Replacing non-aligned files with zip aligned files...
for /R %%X in (*.new) do move /Y "%%X" "%%~dpX%%~nX.apk"
@echo Zip aligning done, press any key to exit
pause
Goto :eof
Click to expand...
Click to collapse
best option would be trial and error and fix bugs, also clear the dalvik cache after pushing, just a cleaner more stable way of doing things
doesnt look like anything is wrong, but just had a quick flick through so i could be wrong
DONE? HAHA
Code:
ECHO CLEARING DALVIK CACHE
ECHO PRESS ENTER TO CLEAR
PAUSE >nul 2>&1
adb shell rm -r /data/dalvik-cache > nul 2>&1
adb shell rm -r /cache/dalvik-cache > nul 2>&1
Ricky Divjakovski said:
best option would be trial and error and fix bugs, also clear the dalvik cache after pushing, just a cleaner more stable way of doing things
doesnt look like anything is wrong, but just had a quick flick through so i could be wrong
Click to expand...
Click to collapse
Ricky Divjakovski said:
best option would be trial and error and fix bugs, also clear the dalvik cache after pushing, just a cleaner more stable way of doing things
doesnt look like anything is wrong, but just had a quick flick through so i could be wrong
Click to expand...
Click to collapse
You wouldn't happen to know the proper mount point for system via adb in recovery? I tried using adb shell mount -o rm,remount /system and it doesn't work, but adb shell mount -a does but its just all mount points not /system?
bryantjopplin said:
You wouldn't happen to know the proper mount point for system via adb in recovery? I tried using adb shell mount -o rm,remount /system and it doesn't work, but adb shell mount -a does but its just all mount points not /system?
Click to expand...
Click to collapse
check architecture then push correct busybox to /data/tmp, apply correct permissions and mount with busybox
Sounds like to much work haha, I'll just tell them to reboot recovery before doing anything else or just go to mount and deselect system haha
Sent from my Pixel XL using Tapatalk
Hey, I appreciate the mentions since you're using a few of my works. Could you please also throw a link in your OP to my Odds and Ends thread, where they originated, as you did for the other components?
osm0sis said:
Hey, I appreciate the mentions since you're using a few of my works. Could you please also throw a link in your OP to my Odds and Ends thread, where they originated, as you did for the other components?
Click to expand...
Click to collapse
Uodated!! I actually thought I did, Sorry. And thanks for reminding me, I'll need to update it again for the zip align idea.
Also any other cool things that I can play with in adb?
Thanks and sorry
Sent from my Pixel XL using Tapatalk