Related
Just in case someone is
This page details how to root the Fujitsu Arrows TAB F-01D.
http://arrowstab-f01d.blogspot.com/2012/03/easy-rooting-toolkit-for-arrows-tab-f.html
it works.
Now if only somebody can post the firmware updates..
English instructions
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Thank you for this wonderful post! A few questions:
1.) I use the F-01D but I don't live in Japan. One of the gripes I've been having about this tablet is that there doesn't seem to be anyway for me to get firmware updates unless I go there. Once rooted am I able to use Market Enabler to fake a carrier and update my tablet?
2.) This is slightly off on a tangent but since I can't find much English material about this tablet anway I might as well ask here. Another one of my gripes about the tablet is it doesn't seem to handle video very well. even 720p video doesn't play smoothly on it. On most of the software I download, it seems hardware acceleration is not enabled? Is this a hardware issue, or is it blocked by the software. And if the latter would rooting the tablet help resolve this issue; or is there any other solution? From what I've read the OMAP processor in this thing should easily be able to handle 1080p video right?
Many thanks! :good:
Kinslayer81 said:
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Click to expand...
Click to collapse
Just wanted to say thank you again. The rooting worked perfectly, though it took me a while to manually type in all the commands. For people who want to try this, you do need to install busybox before any other programs such as rootchecker will properly verify that your device is actually rooted.
And just for anyone wondering - rooting and using MarketEnabler has NOT been able to resolve the issue of not being able to update the software overseas...
Hey, sorry for the late reply, busy times :>
Glad the post helped you! I know I was super amped to finally get rood and get rid of all the bloatware I couldn't even understand. Things have definitely been a lot smoother since then (but far from perfect, also dying for an ICS upgrade). As for your questions:
simzhewei said:
1.) I use the F-01D but I don't live in Japan. One of the gripes I've been having about this tablet is that there doesn't seem to be anyway for me to get firmware updates unless I go there. Once rooted am I able to use Market Enabler to fake a carrier and update my tablet?
Click to expand...
Click to collapse
From playing around, the requirements seem to imply that you *have to* upgrade via cellular data from a Docomo SIM card, and it can't be done via roaming, so yeah, it seems like you have to physically go to Japan to upgrade Your market enabler idea was a good one, but since you tried that (I'm assuming using the Docomo info), I guess the upgrade app is using a different source to check where you're at. Ultimately we need to somehow get hold of an update.zip (or other file) that can be run through the Recovery system (which does exist!).
2.) This is slightly off on a tangent but since I can't find much English material about this tablet anway I might as well ask here. Another one of my gripes about the tablet is it doesn't seem to handle video very well. even 720p video doesn't play smoothly on it. On most of the software I download, it seems hardware acceleration is not enabled? Is this a hardware issue, or is it blocked by the software. And if the latter would rooting the tablet help resolve this issue; or is there any other solution? From what I've read the OMAP processor in this thing should easily be able to handle 1080p video right?
Click to expand...
Click to collapse
Haven't tried 1080p, but after some tinkering I did get 720p playing. I use MX Player, and although they said it would download needed hardware decoders automatically, it didn't, and things improved a lot after I downloaded the MX Player ARMv7 codec. Video plays great, but to get sound, I had to run the sound through the software decoder (just tap the music note icon, and choose "Track #1 (S/W decoder)".
On the other hand, I found the hardware decoding often gets stuck (relaunching MX player just gives you a waiting indicator forever)... and the only way to fix it is a reboot. Since this happens quite often, it's incredibly annoying, and I'm hoping an upgrade will fix it. Let me know if this doesn't happen to you. Also have some very intermittent wifi issues, some things work fine (speedtest, etc) but apps like streaming radio, some work fine (spotify) and others don't work at all (di radio). Some things work fine for a while after a reboot.
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
Incidentally, here's what happens if I try update via recovery (with no update files). Maybe it will help someone. Googling most of the stuff came up with nothing. The ** in the middle somewhere is stuff I couldn't read, guess I should go back and do it again but this is from quite a while ago.
Code:
C_L1_043
2.6.35.7
V19R36D
=======================
SD Downloader
=======================
Device SW Downloading...
Don't remove
the SD Card & the Battery.
checking battery
eMMC SD mount complete.
microSD mount complete.
Firm name :
Firm name :
Target:
Check eMMC(SD).
Firm name :
Update GANG file not found
File open error!
**ddl Touch Firm Write start
Firm name :
/external_sd/I2C_HSSP_Bridge_Parallel.cyacd file not found
firm name :
/sdcard/I2C_HSSP_Bridge_Parallel.cyacd file not found
#sddl touch firm not found ret: 1
SKIP sddl launch firm write end ret: 1
SD : SdFgldfirmwrite -------
firm name :
BAC_H_19.enc =
firm name :
BAC_H_1.9.enc =
error
SKIP sddl fgic firm write end ret: 1
end
****************************
****************************
****
All firmware not found!
****
Interesting situation...
First off...Kinslayer81, thanks for posting this. I found the original in Japanese, and was not eager to try to translate it. Thanks for putting in the work.
For everyone (especially if you got this to work) - when I went through the step, I keep getting a "permissions denied" message. Whether it's the ERT4F01D batch file, or typing the commands in... I get "permissions denied".
Did you guys encounter this?
Glad it helped you On which step are you getting the error? Any strange output on any of the preceding steps?
Every step is important, to be done in the exact same order, e.g. loading google maps and pressing the 'my location' icon, etc.
Dakedo_Baby said:
First off...Kinslayer81, thanks for posting this. I found the original in Japanese, and was not eager to try to translate it. Thanks for putting in the work.
For everyone (especially if you got this to work) - when I went through the step, I keep getting a "permissions denied" message. Whether it's the ERT4F01D batch file, or typing the commands in... I get "permissions denied".
Did you guys encounter this?
Click to expand...
Click to collapse
Permission denied
Oh I know... I'm not new to the game. I've stalked these boards for a while now... This is my first tablet though.
I've tried running both the ERT4F01D batch... and the manual input.
I get it from the batch file, as soon as I tell it to "RUN"... "Permissions Denied"
From manual input - LINE 2: adb shell "ln -s /data/local.prop /data/local/calib.dat" = "Permissions Denied"
Like there's some additional admin privilege I don't have. Hmmmmm....
And here's an additional kicker... the tablet auto-reboots each and every time. I've tried it a number of times (started over from the top), same result each time.
Kinslayer81 said:
Glad it helped you On which step are you getting the error? Any strange output on any of the preceding steps?
Every step is important, to be done in the exact same order, e.g. loading google maps and pressing the 'my location' icon, etc.
Click to expand...
Click to collapse
I must admit, I don't have any great ideas.
So you can move the file in the first step no problem, and just the attempt to symlink gives you the error?
What is the output of "adb shell ls -la /data/local/".
When does the auto reboot occur?
Dakedo_Baby said:
Oh I know... I'm not new to the game. I've stalked these boards for a while now... This is my first tablet though.
I've tried running both the ERT4F01D batch... and the manual input.
I get it from the batch file, as soon as I tell it to "RUN"... "Permissions Denied"
From manual input - LINE 2: adb shell "ln -s /data/local.prop /data/local/calib.dat" = "Permissions Denied"
Like there's some additional admin privilege I don't have. Hmmmmm....
And here's an additional kicker... the tablet auto-reboots each and every time. I've tried it a number of times (started over from the top), same result each time.
Click to expand...
Click to collapse
I'm stumped too...
Well... this is getting a little interesting...
LS command - no problem (included image)
Decided to have another shot at it... and I was able to get a little further. Still encountered a problem
Now, the INSMOD command failed... "Operation not permitted"
Kinslayer81 said:
I must admit, I don't have any great ideas.
So you can move the file in the first step no problem, and just the attempt to symlink gives you the error?
What is the output of "adb shell ls -la /data/local/".
When does the auto reboot occur?
Click to expand...
Click to collapse
file system set to READ-only...
My file systems are set to Read-only... that explains quite a bit....
Dakedo_Baby said:
Well... this is getting a little interesting...
LS command - no problem (included image)
Decided to have another shot at it... and I was able to get a little further. Still encountered a problem
Now, the INSMOD command failed... "Operation not permitted"
Click to expand...
Click to collapse
Dakedo_Baby said:
My file systems are set to Read-only... that explains quite a bit....
Click to expand...
Click to collapse
Do you mind me asking, how did you set your file system to read-write? I have the same error as you were seeing but it's not allowing me to remount as read-write...
Can you confirm what command you used please?
thanks
Sorry again for late reply
Dakedo_Baby, I've looked at your stuff a few times and it's not obvious to me where things are going wrong. I again need some more info to try get a better idea of what's going on:
1) Before the first reboot, let me know the output of: adb shell "cat /data/local.prop"
2) After the reboot, let me know the output of: adb shell id
As for the file systems, well, /data should be already mounted rw, and /system should be mounted ro until you remount it. You can see how each is mounted with just "adb mount".
histrix said:
Do you mind me asking, how did you set your file system to read-write? I have the same error as you were seeing but it's not allowing me to remount as read-write...
Can you confirm what command you used please?
thanks
Click to expand...
Click to collapse
The command to remount the /system partition as read-write is: adb shell "mount -o rw,remount /system /system"
Of course, you should only be executing that step as part of the given sequence and in the correct order. You won't be able to execute the command until after your first reboot in the instructions, after which adb should still be running as root.
Any good Custom ICS roms you guys recommend after rooting the Arrows Tab?
ICS..Hurray!!!
Just found this out in Fujitsu site:
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/index.html
There is a 4.0.3 download available. Click the 3rd Button (Green) downloads the zip package.
The 2nd link has howto from PC.
Still not sure if this will work, but trying out.
Also may lose root..and whatever else..So keeping my fingers crossed.
Google translation link
http://translate.google.com/transla...update/nttdocomo/f-01d/update1/top/index.html
Will post how it goes.
I made a new thread for this, since it's a different topic and you'll lose root too
http://forum.xda-developers.com/showthread.php?p=32200671
insmod lsm-disabler.so to remount /system rw
Back to the original topic... what I maybe didn't notice before is that the stock kernel blocks even root users from remounting /system as rw. So in case you ever need rw access to /system again, obviously you'll first have to be root, and afterwards you'll need to "insmod lsm-disabler.so" (as per the original instructions) before you can "busybox mount -o remount,rw /system" (or run any root app that remounts the system partition).
locked F-01d
Kinslayer81 said:
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Click to expand...
Click to collapse
thanks for the rooting tutorial but mine is also locked to ntt DOCOMO,,,ANY WAY TO UNLOCK IT
how to unlock the network
please help me how to unlock this tablet i got this tablet from my japan friend but it is network locked please help me to unlock this
So I have been having this issue lately that I cant seem to figure out.
In CWM 4, I could create a backup, move the files to my computer, then I run the following script to put that backup onto another galaxy tab.
@echo off
set devicename=%1
echo Copying the Images
adb -s %devicename% shell mount /data
adb -s %devicename% shell "mkdir -p /data/media/clockworkmod/backup/current"
adb -s %devicename% shell sync
adb -s %devicename% push boot.img /data/media/clockworkmod/backup/current/boot.img
adb -s %devicename% shell sync
adb -s %devicename% push cache.img /data/media/clockworkmod/backup/current/cache.img
adb -s %devicename% push data.img /data/media/clockworkmod/backup/current/data.img
adb -s %devicename% push system.img /data/media/clockworkmod/backup/current/system.img
adb -s %devicename% shell sync
echo Producing new MD5 Hash
adb -s %devicename% shell "cd /data/media/clockworkmod/backup/current ; md5sum *img > nandroid.md5"
rem adb shell mount /system
rem echo "Getting MAC Address"
rem adb shell grep mac /system/etc/wifi/nvram_net.txt
rem adb shell umount /system
rem adb -s %devicename% reboot
echo You can Restore now
Click to expand...
Click to collapse
I could then restore that backup on the second tablet with very little issues. I would get some stale data in various apps but for the most part, it worked.
Since installing CM10 Jelly Bean, I had been getting the rolling recovery screen until I updated to CWM6. I had both the Rolling Recovery issue, as well as the Rolling Wake-Up issue. I have been able to resolve both of those but one thing continues to plague me.
I knew I had to modify the script to reflect the new file names of the backup.
@echo off
set devicename=%1
echo Copying the Images
adb -s %devicename% shell mount /data
adb -s %devicename% shell "mkdir -p /data/media/clockworkmod/backup/current"
adb -s %devicename% shell sync
adb -s %devicename% push boot.img /data/media/clockworkmod/backup/current/boot.img
adb -s %devicename% shell sync
adb -s %devicename% push cache.ext4.dup /data/media/clockworkmod/backup/current/cache.ext4.dup
adb -s %devicename% push data.ext4.dup /data/media/clockworkmod/backup/current/data.ext4.dup
adb -s %devicename% push system.ext4.dup /data/media/clockworkmod/backup/current/system.ext4.dup
adb -s %devicename% shell sync
echo Producing new MD5 Hash
adb -s %devicename% shell "cd /data/media/clockworkmod/backup/current ; md5sum *img > nandroid.md5"
rem adb shell mount /system
rem echo "Getting MAC Address"
rem adb shell grep mac /system/etc/wifi/nvram_net.txt
rem adb shell umount /system
rem adb -s %devicename% reboot
echo You can Restore now
Click to expand...
Click to collapse
Any backups I create in CWM6 will not restore on the secondary tablet. Both run CWM6, Both run the same bootloader, both are identical in every way. But when I try and restore, I get:
CWM-based Recovery v6.0.1.5
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while restoring /system!
Click to expand...
Click to collapse
I have to restore an "image" to several hundred Galaxy Tablets and I need the system to be pretty much completely customized; as far as homescreen placement of apps, background, USB debugging, locked apps, etc.
Can anyone explain why I could back up one tablet "image" and restore to another on CWM4 but not on CWM6? Is there something wrong with the script I'm running to move the files? Specifically the portion about Producing a new MD5 Hash. Would TWRP be a better option here? I use that recovery on my HTC One S.
Or better yet, give me some kind of Rom Kitchen for the Galaxy Tab 10.1 wifi?? I'm not smart enough to build a rom from scratch, but then again, this was all jargon to me 5 years ago.
I am very appreciative of any advice the community can provide. I've been using this forum for years and can pretty much give credit to XDA for every piece of mobile development knowledge I do have, little as it may be.
cmw 6 probably doesnt have system.img
it's probably system.tar
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, it will also let member do things manually instead of relying on update ZIP's all the time. Besides of explaining how to use a simple program such a quick ADB Pusher, i will also explain in depth the commands of ADB through the actual command line interface, so here we go:
First of all we will start with The command line ADB, the quick adb pusher tutorial is further down the post.
Before we start explaining some of the code what is used in ADB, it is important you know what it is, it is called the Android-Debug-Bridge.
In order to even get ADB to wokr you need to follow these procedures:
Settings -> Developers options -> USB-de bugging
Then check that box, it will make you feel like a boss.
Now once you have done that your android device, is now setup for both development and ADB. Next you are going to plug your device into your computer, via a usb cable.
Once you have done that you need to go to the directory of your ADB interface, this is where you have the android SDK installed too, on a linux or mac based system this could be:
Code:
cd /home/yourusername/android-sdk-mac/tools
Once you have the ADB interface loaded into your terminal, if you type help it will show something similar to this:
Code:
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
Now that you have ADB running here are some simple commands on how to use it:
How identify that your device is being recognised by ADB:
Code:
adb devices
Once this has been typed it should show something like this:
Code:
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT26GW507639 device
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>
If there is a line what says "HT26GW507639" with "device" at the end your devices is successfully recognised by ADB!
How to pull data from your device:
Code:
adb -s [yourdeviceADBNUMBERHERE] pull /system /the directory you want it saved too
This command will pull all the files from your devices system directory, to the directory you told it to be saved too.
I did the pull command on a PC and I was able to get all the data from following directories on my Desire C:
/data
/system
How to push data to your device:
Code:
adb -s [yourdeviceserialnumberhere] push /system/app/whatever.apk
This command will push the files you wish to your phone, though this command.
The most basic ADB commands
ADB push, as explained before this command is used to send files to your device
Code:
adb push
ADB pull, as explained before it pulls files from your phone, and makes a copy of them.
Code:
adb pull
ADB Install and example of this code would be "adb install c:\users\app.apk"
Code:
adb install c:\users\app.apk
ADB Shell, this command begins a shell connection to the device on the other end.
Code:
adb shell
ADB reboot, it does what it says
Code:
adb reboot
ADB reboot recovery, this also does what it says
Code:
adb reboot recovery
ADB reboot bootloader, this also does what is says, like the ones above.
Code:
adb reboot bootloader
ADB remount, this remounts the devices file system for editing etc...
Code:
adb remount
ADB Shell commands:
cd, this command changes directories in your devices filesystem.
Code:
cd /system/app
is, this command listes all of the file present in the directory you are at.
Code:
is /system/app
rm, this command removes file from your device.
rm /system/app/whatever.apkcp, this command copies files, and is very similar to the cat command below.
Code:
cp /system/app/whatever.apk /sdcard/whatever.apk
cat, this command is also used to copy files to your device.
Code:
cat /system/app/whatever.apk > /sdcard/whatever.apk
exit, this command exits the ADB shell.
Code:
exit
If any of you are having any problems, read the FAQ first before posting a question in this thread, happy pushing!
If you think any other commands should me added to this section, PM me about it.
As explained above, the quick ADB pusher is an interface over the code based ADB. I will be a much easier approach for new user of android to get to grips to, that is why I am including it.
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, so here we go:
First of all you want to download the quick adb pusher program, this is in both this thread and the revolution Rom thread on XDA, the link for the program is listed below:
Quick ADB Pusher
Now you want to make sure your phone is plugged into your computer, but do not put it into USB storage mode. Make sure your USB de-bugging option is enabled it is located at:
Settings --> Developer options --> USB De-bugging
Now you will start the quick ADB pusher program, once it has started it should detect your phone. If it does not then post a comment in the thread below and we will resolve the issue.
Watch the video below to clarify a few things, such as how to copy system apps etc...
Again I hope this tutorial helps some people out, remember to read the FAQ first before posting,, to prevent the same questions being asked time and time again.
FAQ
Do you guys want a guide on how to build roms for your device?
Sent from my HTC Desire C using xda premium
russell664 said:
Do you guys want a guide on how to build roms for your device?
Sent from my HTC Desire C using xda premium
Click to expand...
Click to collapse
Yes please I think it would be very interesting.
And thanks for your time in doing this :good:
AW: [GUIDE][HOWTO] How to push files using ADB Desire V
Me too
Sent from my HTC Desire V using xda premium
I will when I have time guys, if you want more guides and stuff, surely you can smash the thanks button right in the face for me. To show your support, and that you appreciate my work.
Creating our own custom roms
Yup. It really would be a great tutorial for newbies to get started to make things, which once they could only appreciate. I am myself good at programming and algorithms, but Android development is quite alien to me. I consider myself a potential developer, if only would I get a kick start at ROM making. Also we could be able to support unknown or local market devices. I think that would be really beneficial for the entire Android community to see new budding developers with their innovations. :angel:
Hit thanks if you agree.
russell664 said:
As explained above, the quick ADB pusher is an interface over the code based ADB. I will be a much easier approach for new user of android to get to grips to, that is why I am including it.
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, so here we go:
First of all you want to download the quick adb pusher program, this is in both this thread and the revolution Rom thread on XDA, the link for the program is listed below:
Quick ADB Pusher
Now you want to make sure your phone is plugged into your computer, but do not put it into USB storage mode. Make sure your USB de-bugging option is enabled it is located at:
Settings --> Developer options --> USB De-bugging
Now you will start the quick ADB pusher program, once it has started it should detect your phone. If it does not then post a comment in the thread below and we will resolve the issue.
Watch the video below to clarify a few things, such as how to copy system apps etc...
Again I hope this tutorial helps some people out, remember to read the FAQ first before posting,, to prevent the same questions being asked time and time again.
Click to expand...
Click to collapse
It told me my devices wasn't rooted?
When trying to push a file to my internal storage on my Moto X does the file need to be located in a specific location? I am trying to root my device and need to push a file to my device. I am very new to this, and have adb working and my device showing up when i run "adb devices". I have a folder on my desktop titled "android" which contains adb, fastboot, sdk, and eclipse. Do I need to save the files I want to push to the root of this folder on my desktop? Thanks for the help!
stavebomb said:
When trying to push a file to my internal storage on my Moto X does the file need to be located in a specific location? I am trying to root my device and need to push a file to my device. I am very new to this, and have adb working and my device showing up when i run "adb devices". I have a folder on my desktop titled "android" which contains adb, fastboot, sdk, and eclipse. Do I need to save the files I want to push to the root of this folder on my desktop? Thanks for the help!
Click to expand...
Click to collapse
So push whole folder by
Code:
adb push <path on PC> <path on Moto X>
How to push this command
Please help me:
http://forum.xda-developers.com/showthread.php?t=2708466
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
on my LG G2 (D802 ver 20B without root indian version)
My tablet is stuck in the recovery mode on a permanent loop. Please help
I'm just learning to code and honestly as of 6 months ago I didn't even know how to turn a computer on although I practice and take classes I'm petrified I'm going to screw up my computer. Anyway, my tablet is stuck in the recovery mode on a permanent loop so I can't put it in debug development mode. Please help me fix it. I can't afford a new one and I use it for work when I'm at a job site. I downloaded the Android Suite bundle zip (the one that said recommended) also the sdk tools zip, the quick adb pusher and the lollipop image file, lollipop rom file. I've tried every one of the commands from your site and many many other sites and it's not fixing my tablet. I know you guys don't like stupid questions but I'm feeling like a moron because I can't figure it out. Could someone please please help me fix me tablet.
russell664 said:
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, it will also let member do things manually instead of relying on update ZIP's all the time. Besides of explaining how to use a simple program such a quick ADB Pusher, i will also explain in depth the commands of ADB through the actual command line interface, so here we go:
First of all we will start with The command line ADB, the quick adb pusher tutorial is further down the post.
Before we start explaining some of the code what is used in ADB, it is important you know what it is, it is called the Android-Debug-Bridge.
In order to even get ADB to wokr you need to follow these procedures:
Settings -> Developers options -> USB-de bugging
Then check that box, it will make you feel like a boss.
Now once you have done that your android device, is now setup for both development and ADB. Next you are going to plug your device into your computer, via a usb cable.
Once you have done that you need to go to the directory of your ADB interface, this is where you have the android SDK installed too, on a linux or mac based system this could be:
Code:
cd /home/yourusername/android-sdk-mac/tools
Once you have the ADB interface loaded into your terminal, if you type help it will show something similar to this:
Code:
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
Now that you have ADB running here are some simple commands on how to use it:
How identify that your device is being recognised by ADB:
Code:
adb devices
Once this has been typed it should show something like this:
Code:
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT26GW507639 device
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>
If there is a line what says "HT26GW507639" with "device" at the end your devices is successfully recognised by ADB!
How to pull data from your device:
Code:
adb -s [yourdeviceADBNUMBERHERE] pull /system /the directory you want it saved too
This command will pull all the files from your devices system directory, to the directory you told it to be saved too.
I did the pull command on a PC and I was able to get all the data from following directories on my Desire C:
/data
/system
How to push data to your device:
Code:
adb -s [yourdeviceserialnumberhere] push /system/app/whatever.apk
This command will push the files you wish to your phone, though this command.
The most basic ADB commands
ADB push, as explained before this command is used to send files to your device
Code:
adb push
ADB pull, as explained before it pulls files from your phone, and makes a copy of them.
Code:
adb pull
ADB Install and example of this code would be "adb install c:\users\app.apk"
Code:
adb install c:\users\app.apk
ADB Shell, this command begins a shell connection to the device on the other end.
Code:
adb shell
ADB reboot, it does what it says
Code:
adb reboot
ADB reboot recovery, this also does what it says
Code:
adb reboot recovery
ADB reboot bootloader, this also does what is says, like the ones above.
Code:
adb reboot bootloader
ADB remount, this remounts the devices file system for editing etc...
Code:
adb remount
ADB Shell commands:
cd, this command changes directories in your devices filesystem.
Code:
cd /system/app
is, this command listes all of the file present in the directory you are at.
Code:
is /system/app
rm, this command removes file from your device.
rm /system/app/whatever.apkcp, this command copies files, and is very similar to the cat command below.
Code:
cp /system/app/whatever.apk /sdcard/whatever.apk
cat, this command is also used to copy files to your device.
Code:
cat /system/app/whatever.apk > /sdcard/whatever.apk
exit, this command exits the ADB shell.
Code:
exit
If any of you are having any problems, read the FAQ first before posting a question in this thread, happy pushing!
If you think any other commands should me added to this section, PM me about it.
Click to expand...
Click to collapse
I Want to Thank Russell664. I followed your instructions and my tablet works again.
Thank you very much. You do not know how appreciative I am for your help. I hate feeling so stupid about these things. Your detailed guide was so informative and so so helpful. Debbie from Handyman-Girl
:good:
russell664 said:
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, it will also let member do things manually instead of relying on update ZIP's all the time. Besides of explaining how to use a simple program such a quick ADB Pusher, i will also explain in depth the commands of ADB through the actual command line interface, so here we go:
First of all we will start with The command line ADB, the quick adb pusher tutorial is further down the post.
Before we start explaining some of the code what is used in ADB, it is important you know what it is, it is called the Android-Debug-Bridge.
In order to even get ADB to wokr you need to follow these procedures:
Settings -> Developers options -> USB-de bugging
Then check that box, it will make you feel like a boss.
Now once you have done that your android device, is now setup for both development and ADB. Next you are going to plug your device into your computer, via a usb cable.
Once you have done that you need to go to the directory of your ADB interface, this is where you have the android SDK installed too, on a linux or mac based system this could be:
Code:
cd /home/yourusername/android-sdk-mac/tools
Once you have the ADB interface loaded into your terminal, if you type help it will show something similar to this:
Code:
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
Now that you have ADB running here are some simple commands on how to use it:
How identify that your device is being recognised by ADB:
Code:
adb devices
Once this has been typed it should show something like this:
Code:
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT26GW507639 device
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>
If there is a line what says "HT26GW507639" with "device" at the end your devices is successfully recognised by ADB!
How to pull data from your device:
Code:
adb -s [yourdeviceADBNUMBERHERE] pull /system /the directory you want it saved too
This command will pull all the files from your devices system directory, to the directory you told it to be saved too.
I did the pull command on a PC and I was able to get all the data from following directories on my Desire C:
/data
/system
How to push data to your device:
Code:
adb -s [yourdeviceserialnumberhere] push /system/app/whatever.apk
This command will push the files you wish to your phone, though this command.
The most basic ADB commands
ADB push, as explained before this command is used to send files to your device
Code:
adb push
ADB pull, as explained before it pulls files from your phone, and makes a copy of them.
Code:
adb pull
ADB Install and example of this code would be "adb install c:\users\app.apk"
Code:
adb install c:\users\app.apk
ADB Shell, this command begins a shell connection to the device on the other end.
Code:
adb shell
ADB reboot, it does what it says
Code:
adb reboot
ADB reboot recovery, this also does what it says
Code:
adb reboot recovery
ADB reboot bootloader, this also does what is says, like the ones above.
Code:
adb reboot bootloader
ADB remount, this remounts the devices file system for editing etc...
Code:
adb remount
ADB Shell commands:
cd, this command changes directories in your devices filesystem.
Code:
cd /system/app
is, this command listes all of the file present in the directory you are at.
Code:
is /system/app
rm, this command removes file from your device.
rm /system/app/whatever.apkcp, this command copies files, and is very similar to the cat command below.
Code:
cp /system/app/whatever.apk /sdcard/whatever.apk
cat, this command is also used to copy files to your device.
Code:
cat /system/app/whatever.apk > /sdcard/whatever.apk
exit, this command exits the ADB shell.
Code:
exit
If any of you are having any problems, read the FAQ first before posting a question in this thread, happy pushing!
If you think any other commands should me added to this section, PM me about it.
Click to expand...
Click to collapse
Hello
There's a way for making a backup with RAW extension that can be flashed with fastboot in asus fonepad (i don't know about others)
See this: http://forum.xda-developers.com/showthread.php?t=1818321
Back up of the whole memory block (via adb)
Connect the phone in ADB mode and unlock the screen.
Open one Cygwin Terminal and enter (replace mmcblk0 if needed):
Code:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
You will see the cursor blinking at the left. Now the phone is waiting to send the block over the network.
Open another Cygwin terminal and type:
Code:
adb forward tcp:5555 tcp:5555
cd /path/to/store/the/backup
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
You will see how the image size is growing until it finishes. Now you have the whole phone backed up in raw format. You can see the contents of the GPT partition with gptfdisk tool, available for windows, linux and such. See official website and sourceforge to get it. You can do it the same from ClockWorkMod Recovery but you have to mount first the /system partition since the busybox included with clockworkmod does not come with netcat and you have to use the one from the system partition.
With further linux tools you could edit or extract single partitions from the whole block.
Click to expand...
Click to collapse
But it's for rooted devices only. how can i make a backup with busybox non-root?
I made a backup using the following guide here and now I need to restore from it. I would reply directly in the thread however I don't have permission to at the moment.
My issue is that on my phone I don't have enough space to store both a backup and the phone image and it doesn't appear that CWM can restore from a .raw file.
Is it possible to basically reverse the operation and setup this on my Mac
Code:
adb forward tcp:5555 tcp:5555
sudo nc -l -p 5555 -e dd if=/path/to/backup
and then on my phone:
Code:
adb forward tcp:5555 tcp:5555
cd /dev/block/mmcblk0
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
I get the feeling however (going with my limited understanding of Unix), this will just transfer the .raw file back and it will just possibly brick the phone. (Edit: going back and looking, maybe using …dd of=/dev/block/mmcblk0 and then using netcat to provide the file to write will work?)
I have Googled extensively and another option I have come upon is using gdisk to extract the individual partitions from the backup but this sounds fairly laborious to me.
Alternatively is it possible just to turn the .raw into tars which CWM can restore natively?
Thanks, and apologies if this is in the wrong place.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Moto G (XT1033), Cyanogenmod 11 M6