Related
ADB COMMANDS
This is just a simple guide on how to open up and run adb commands from your windows based operating system.
Open up run by simultaneously pressing the windows flag key and r.
In the window that pops up type cmd. Now command prompt is open
type the commands each followed by the enter key: cd\
cd androidsdk/tools
Now your in your in your androidsdk/tools folder. You can do several things in here but i'll start with some basics each
of the following commands is to be followed by the enter key
adb devices (this lets you know what devices are attached to the computer in usbdebugging)
How to get your logcat (this will put your logcat in txt format in your sdk tools folder)
adb logcat > logcat.txt
copy an app from your phone to your computer
adb pull /system/app/whatever.apk C:\ateam (replace whatever.apk with the app your pulling also replace ateam with the
folder your placing the app in
Install an app from your computer on your phone
adb install whatever.apk (put an apk in your sdk tools and replace"whatever" with the name of the apk and it will install it)
also you can add either -r or -s to reinstall or install on the sdcard for instance: adb install -r Rosie.apk
this command will reinstall the new rosie from your tools file and still keep the same user data as before.
-r for reinstall
-s for sdcard (gotta test this)
Push an app from your computer to your phones filesystem (in some cases also installs)
adb remount
adb push whatever.apk /system/app (put an apk in your sdk tools and replace "whatever" with the name of the apk and this
will push it to your system app folder. You can change the destination as well for example: You want to push Launcher2.apk
to your data/app folder: adb remount
adb push Launcher2.apk /data/app )
Remove an app from your phone
adb remount
adb shell
cd /system/app (this will change your disk to system/app you may also change to another folder as well)
ls -a ( a list will show of all the apps inside your system app folder)
rm whatever.* (replace the whatever.* with the name of a apk you want to remove )
Flash a recovery image to your phone
First pace the recovery image in your sdcard root and rename it to recovery (so the full name will now be recovery.img)
adb shell
flash_image recovery /sdcard/recovery.img (wait till this# sign shows up again before you type the next command)
reboot recovery
get your current battery level
adb shell cat /sys/class/power_supply/battery/capacity
get your current rom build
adb shell getprop ro.build.description
Reboot into fastboot ruu
adb shell reboot oem-78
How to run the ruu via adb
First thing first start the ruu give it permissions and so fourth
When it gets to the part where it says "Follow the instructons below..."
Move the ruu window out of the way and start your task manager
Go to processes right click on ARUWizard.exe and choose open file location
A new window will open scroll till you see ROM.zip
Copy and paste Rom.zip to your desktop
Once you have copied it to your desktop shutdown the ruu and task manager
Click start menu then click computer
A window will open up click the c drive
now click create new folder and name it test
put the rom.zip in the test folder
plug your phone in and open command prompt and type
Code:
adb devices
adb shell reboot oem-78
fastboot devices
fastboot getvar boot-mode
fastboot erase cache
fastboot flashzip C:\test\rom.zip
fastboot devices
fastboot getvar boot-mode
fastboot reboot
Very useful man thanks for the guide. I also think newbies would use this guide as its in the right catagory and not in some G1 section or Mt3g section.
Edit** isnt this already in the tuorials section?
sandboxlove said:
i think its a great idea, we need a more compilied list to refer to
add more!!!!
Click to expand...
Click to collapse
I'm going to try to add one everyday. tomorrows lesson how to run the ruu from adb
Powers16 said:
Very useful man thanks for the guide. I also think newbies would use this guide as its in the right catagory and not in some G1 section or Mt3g section.
Edit** isnt this already in the tuorials section?
Click to expand...
Click to collapse
Where? Pagelink
http://forum.xda-developers.com/showthread.php?p=5799939#post5799939
but its a less in depth reference so i hope this gets added into the tutorial section as here are no in depth tuts about adb in there..
also to remove apk
adb shell rm /system/ (then put in either app or media or what ever folder name /whatever.apk
Papa Smurf151 said:
also to remove apk
adb shell rm -r /system/ (then put in either app or media or what ever folder name /whatever.apk
Click to expand...
Click to collapse
rm -r is a recursive deletion and can have a lot of unwanted and harmful side-effects if used incorrectly. To just remove apks, a simple rm works just fine. If they typed the wrong directory, file name, whatever, a recursive deletion would clear the entire folder... Not really something you'd want.
This is great, I will be coming back for more.
Thanks a lot
DevinXtreme said:
rm -r is a recursive deletion and can have a lot of unwanted and harmful side-effects if used incorrectly. To just remove apks, a simple rm works just fine. If they typed the wrong directory, file name, whatever, a recursive deletion would clear the entire folder... Not really something you'd want.
Click to expand...
Click to collapse
thanks...i knew that but wasnt paying attention. I just copied and pasted from my adb notepad file. i edited my post and removed the -r
DevinXtreme said:
rm -r is a recursive deletion and can have a lot of unwanted and harmful side-effects if used incorrectly. To just remove apks, a simple rm works just fine. If they typed the wrong directory, file name, whatever, a recursive deletion would clear the entire folder... Not really something you'd want.
Click to expand...
Click to collapse
LOL, yeah, I've done that
Might want to also include a note that says when using linux or mac shell you replace the "adb" with "./adb" (I believe that is correct or at least what I do now when reading the windows cmd guides)
tejasrichard said:
LOL, yeah, I've done that
Click to expand...
Click to collapse
I wiped out 16 years of source code with it once....I got fired.
Kcarpenter said:
I wiped out 16 years of source code with it once....I got fired.
Click to expand...
Click to collapse
Oh damn that's crucial man. Hope they had backups
Screwin around
So I was screwin around with adb tryin to learn this stuff and I stumbled across this by just typing adb after cd'ing in. Hopefully its useful. Mind you I am a total noob to android/linux and this was a total accident. I am sure you all know about it though. Useful info though
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>cd\
C:\>cd android-sdk-windows
C:\android-sdk-windows>adb
Android Debug Bridge version 1.0.26
-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 environment 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] [-s] <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)
('-s' means install on SD card instead of internal storage)
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 bootloade or recovery program
adb reboot-bootloader - reboots the device into the bootloader
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 u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
C:\android-sdk-windows>
Hi, I'm abcdfv, and I approve this thread.
abcdfv said:
Hi, I'm abcdfv, and I approve this thread.
Click to expand...
Click to collapse
LOL Thanks
I've always been an advocator of EVERYONE learning the ADB basics at least.
updated with run the run the ruu via adb commands
I'm trying to flash my recovery image. I need help. What is the first comand I type at C:\Windows\System32> normally I type cd:\android-sdk-windows\tools
then i adb remount, then adb shell. When I do that now I get "remount failed: Invalid argument" I'm not TOTALLY clueless, although it may turn out that I am after this. any help would be great. I am booted in recovery, but since my recovery image is gone, its just an exclamation in a triangle. if i adb devices, i can see my phone and it says i'm in recovery. Thanks.
I need some serious help with this.....do you need to download anything on your computer?? can you explain all the stuff you need to do leading up to what you type into command prompt...anyone..i need help..i flashed darchstar froyo build and the recovery is all messed up..i cant flash anything..so i need to push a new recovery img.but i don't know anything about adb shell or anything .....please........ive never had to push anything..everyone always just puts flashable zips out for you...HELP
I am running on a Mac (OSX Lion) and have installed android-sdk-macosx.
I am trying to connect to a Kindle Fire 6.2.2
However, this is as far as I can get:
Code:
bash-3.2# ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
bash-3.2#
As you can see, no devices show up.
I have tried switching cables, USB ports, reboot the device and my machine... banging my head against the wall.
Nothing works.
I have read about 29 pages of posts through this forum, and Googled it.
No dice.
Any suggestions?
would not use the sdk at all - if you use the mac/linux version of kfu you save a lot of time and space - you don't need to use kfu if you don't like to - but all commands you'll ever need are in the tools folder of kfu - it also includes drivers and setup scripts - maybe give it a try:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
mkdir ~/.android
echo 0x1949 >> ~/.android/adb_usb.ini
ADB needs this entry to see the Kindle Fire no matter what OS you're on.
right - there is also a installation script for this included in the pack - install.sh if i remember right
took the advice above and it's still not working for me. i have the same exact problem. when i try to run install_drivers.sh i get:
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
When I run KFU i get:
/Users/donaldclark/kfu/run.sh: line 84: seq: command not found
please help
as far as i know (don't own a mac) you have to call the commands with
./ from terminal window - eg ./run.sh
I also got the same error message at line 84 running the install script in OSX 10.6.8
-E
it's from eratosthene - give him a pm - i'm shure he can help you
http://forum.xda-developers.com/member.php?u=1616763
Try remove the usb driver from your device and re-install gain.
I use Kindle_Fire_Utility_MacLinux_0.9.2 3 with adb.mac
and its located right inside my root directory (not under users) step before.
I went to the files and I opened file called
install_drivers.sh
I did deleted everything behind -p and just dragged
the adb_usb.ini (its located in drivers) into that install_drivers.sh script and I hit save.
thats how it looks like
mkdir -p /Kindle_Fire_Utility_MacLinux_0.9.2 3/drivers/adb_usb.ini/adb_usb.ini
Than I just run adb.mac and all is operational
my kindle was rooted with burittoroot2
If you need those files send me a pm I have them in my dropbox.
somboonr said:
Try remove the usb driver from your device and re-install gain.
Click to expand...
Click to collapse
there is no uninstalling drivers like in windows.
line 84 SOLUTION
Incarnate609 said:
took the advice above and it's still not working for me. i have the same exact problem. when i try to run install_drivers.sh i get:
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
When I run KFU i get:
/Users/donaldclark/kfu/run.sh: line 84: seq: command not found
please help
Click to expand...
Click to collapse
Regarding the "run.sh: line 84: seq: command not found", I found out that the "seq" command is not recognized with MAC OS... so I did a search and replace, replacing "seq" with "jot -". Now it works.
Reference: Search google for seq and mac
What worked for me.
I had the same problem after updated the sdk on my MacBook Mac OSX 10.6.8
cd to the tools directory (where android program is located)
run:
./android update usb
./android update adb
then edit the ~/.android/adb_usb.ini file and add 0x1949 as the last line (your previous adb_usb.ini file is overwritten by the above commands).
So I was trying earlier to use ADB while trying to add WIFI to one of the ROMs.. I guess I mistyped something and now it is giving me this error..
How can I fix this? It's not really irking me but sometimes I just want to push a file through ADB and I don't want to keep having this error..
Code:
C:\adt-bundle-windows\sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb devices
List of devices attached
003cf8f9ded1abcc device
C:\adt-bundle-windows\sdk\platform-tools>adb root
adbd cannot run as root in production builds
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\adt-bundle-windows\sdk\platform-tools>adb root
adbd cannot run as root in production builds
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>
For some reason if I delete the whole adt-bundle-windows and extract it again from the .zip file.. It mounts but keeps getting the error
Code:
C:\adt-bundle-windows\sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
I'll be going to sleep soon, so if you need me to do something, I might not get back to you till morning.
Thanks for helping me!
You need an insecure kernel to have root in adb. Or root your phone.
klin1344 said:
You need an insecure kernel to have root in adb. Or root your phone.
Click to expand...
Click to collapse
i'm using franco.kernel - test 5.. and i am rooted? i can use supersu, ti backup, root explorer
Sent from my Nexus 4 using Tapatalk 2
Bump, any help on this?
Bumping this. I am having the same issue. Rooted on the latest stock andriod. Custom kernel as well.
You need an insecure boot.img
Either download the one on this post or enable root over adb if you are running CyanogenMod or AOKP.
Use the set of commands in the sticky.
Doesn't need an insecure kernel.
I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.
ess.boyer said:
I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.
Click to expand...
Click to collapse
This worked for me. I was pulling my hair out trying to get the system rw. adb root, did the trick. Make sure you set the phone in to root for adb in Settings/Developer option/Root Access
You are the f'ing man.
What is "adb kill-server".
ess.boyer said:
I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.
Click to expand...
Click to collapse
@ess.boyer;35057736 , thanks in advance , boss I am new user of android. I use Lenovo A789(ICS 4.0.4, MKT6577 from China) .I have rooted by mobile with SP_Flash_Tool_v3.1222.00 . Now I have remount problem. I want to solve it. What is "adb kill-server" . How can I get"adb kill-server"
and how can I able "adb remount" to write to the filesystem . Please help.
GUYS GUYS
i had this problem with Cyanogen and my kernel is Googy max
ye ADB ROOT command will work. But you can use adbd insecure APP and you don't need adb root command any more
what do i do with the img file??
I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.
When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.
So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.
After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.
I realized that the script ran by VegaTools did this "amazing" thing:
adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync
So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.
Ok, my situation now is:
I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -
So, I cannot get into the device to fix the permissions, and cannot do anything else.
Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device
Before that, only the emulator one appeared.
Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?
I am using adb on windows.
Thanks a lot for any help, in advance.
Eduardo
EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots
No one can help me?
eclaro said:
I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.
When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.
So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.
After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.
I realized that the script ran by VegaTools did this "amazing" thing:
adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync
So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.
Ok, my situation now is:
I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -
So, I cannot get into the device to fix the permissions, and cannot do anything else.
Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device
Before that, only the emulator one appeared.
Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?
I am using adb on windows.
Thanks a lot for any help, in advance.
Eduardo
EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots
Click to expand...
Click to collapse
Please, any help?
OBSOLETE! There are now better ways to root using a proper kernel and TWRP. Please follow this guide instead
http://forum.xda-developers.com/z3-tablet-compact/general/adb-fastboot-drivers-tutorial-t2980529
I am working on root for the stock rom on SGP611 with unlocked bootloader.
So far I have managed to get R/W access to /system and make permanent changes. I have installed an su binary but it is not working properly which I believe is because of selinux restrictions. I can become root in ADB and mount /system writable but apps requiring root fails.
I have not tried to build a custom recovery so installing normal flashable zips is not possible.
This is what I did so far:
Get the firmware files using PC Companion
Extract the kernel using Flashtool and split it into kernel, ramdisk and dtb
Extract the ramdisk
Replace adbd with an insecure version
Change fstab.qcom som /system is mounted rw
Reassemble the boot.img using mkbootimg
Code:
mkbootimg --cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0xb7 ehci-hcd.park=3 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" \
--base 0x00000000 --kernel kernel_S1-SW-LIVE-9C84-PID1-0006-MMC.elf.Image --ramdisk ramdisk-insecure.img.gz \
--ramdisk_offset 0x02000000 -o boot.img --dt kernel_S1-SW-LIVE-9C84-PID1-0006-MMC.elf.3 --tags_offset 0x01E00000
Unlock bootloader (I selected Z3 on the Sony unlock web page). YOUR DATA WILL BE WIPED SO MAKE A BACKUP FIRST! DRM keys will be removed which may affect funtionality and can affect the second hand value of your tablet. You have been warned!
Boot the insecure image with fastboot
Code:
fastboot-toolkit.exe boot \temp\insecure-kernel\z3tc-sgp611-insecure.img
Tablet boots but screen is not working.
Connect with ADB with root and /system rw. Now it is possible to push files to /system
Attached is my modified kernel image. I have not tried to flash it but only booted it from fastboot.
I am now asking for help installing a proper su (su daemon?) and tips for building a custom recovery.
Please feel free to move this thread to a development forum but I am not allowed to post there.
I can only hope that you can break through and get this thing rooted. Remember that there are developer's that can give you a hand. I wish I knew how. By the way will this work with SGP621 4G LTE they are the same except for cell capability. I just want to thank you for trying
Instructions for rooting Z3TC with unlocked bootloader
Root for unlocked bootloader
Sony Z3 Tablet Compact Wifi SGP611 firmware 23.0.1.A.0.167
Step by step installation:
Make sure that you have ADB installed and it is working before you proceed. Your PC should be authorized (connect once and press ok on the tablet.)
Reboot to fastboot and unlock bootloader. Follow the instructions here
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
and select Xperia Z3 if Tablet Compact is not available.
WARNING! YOUR DATA WILL BE WIPED WHEN UNLOCKING THE BOOTLOADER. MAKE SURE THAT YOU HAVE A BACKUP. DRM keys will be removed which may affect functionality and can affect the second hand value of your tablet. You have been warned!
Boot the included kernel image. This will not flash a new kernel, only load it to RAM and boot it
Code:
fastboot boot z3tc-sgp611-insecure.img
Wait for the tablet to boot. NOTHING WILL BE SHOWN ON SCREEN, THE DISPLAY IS
DARK.
Run the following commands to push files to the tablet:
Code:
adb push UPDATE-SuperSU-v2.16.zip /tmp
adb push busybox /tmp
adb push install-supersu.sh /tmp
Start an ADB shell. You should get a root prompt #
Code:
adb shell
In ADB shell, run the script to install supersu. A number of error messages
about missing files will be shown but it is normal.
Code:
# cd /tmp
# /system/bin/sh install-supersu.sh
Reboot tablet and enjoy root!
Code:
# reboot
When booting z3tc-sgp611-insecure.img only mass storage usb device is on USB port, no debug! How to solve?
SGP621, 23.0.1.A.0.167
Code:
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot boot z3tc-sgp611-insecure.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.333s]
booting...
OKAY [ 0.048s]
finished. total time: 0.385s
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb devices
List of devices attached
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb push UPDATE-SuperSU-v2.16.zip /tmp
error: device not found
error: device not found
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb devices
List of devices attached
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb devices
List of devices attached
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb kill-server
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
alex9x said:
When booting z3tc-sgp611-insecure.img only mass storage usb device is on USB port, no debug! How to solve?
Click to expand...
Click to collapse
I have SGP611 16GB Wifi version and I do not know if SGP621 uses the exact same kernel.
It sound like a missing driver issue. Is ADB enabled in developer settings? Is ADB working ok when you boot normally?
Check Device Manager in Windows and see if there are any missing drivers (question marks). I had to replace the android_winusb.inf file for the ADB driver to get it to recognize the Z3TC (or maybe that was for Fastboot...).
ejdan said:
I have SGP611 16GB Wifi version and I do not know if SGP621 uses the exact same kernel.
It sound like a missing driver issue. Is ADB enabled in developer settings? Is ADB working ok when you boot normally?
Check Device Manager in Windows and see if there are any missing drivers (question marks). I had to replace the android_winusb.inf file for the ADB driver to get it to recognize the Z3TC (or maybe that was for Fastboot...).
Click to expand...
Click to collapse
All drivers installed, but only SD card appear in device manager. Seems like ADB disabled in booted firmware.
When normal boot - Sony sa0111 ADB Interface Driver (USB\VID_0FCE&PID_51C0&REV_0232&MI_01 ) appear and all OK. But before connection it ask to allow my pc connection and display RSA keys. One time press allow, and then no any questions, adb devices show my serial in list.
When powering UP - Android ADB Interface (USB\VID_0FCE&PID_0DDE&REV_0100) appearing, then booting z3tc-sgp611-insecure.img -
USB Mass Storage Device (USB\VID_0FCE&PID_E1C0&REV_0232) appears in a 7-10 seconds, and no more devices.
right on guys you're getting there. thank you
alex9x said:
When powering UP - Android ADB Interface (USB\VID_0FCE&PID_0DDE&REV_0100) appearing, then booting z3tc-sgp611-insecure.img -
USB Mass Storage Device (USB\VID_0FCE&PID_E1C0&REV_0232) appears in a 7-10 seconds, and no more devices.
Click to expand...
Click to collapse
Do you have any lockscreen security enabled? Maybe ADB is disabled when the device is locked. Try disabling PIN/pattern lock before booting the insecure kernel.
ejdan said:
Do you have any lockscreen security enabled? Maybe ADB is disabled when the device is locked. Try disabling PIN/pattern lock before booting the insecure kernel.
Click to expand...
Click to collapse
no any locks... I know this...
usb sd device is the same like when charging.... seems like when insecure kernel boots - it just enter charger mode... when booting insecure image, need any pressing key?
alex9x said:
When powering UP - Android ADB Interface (USB\VID_0FCE&PID_0DDE&REV_0100) appearing, then booting z3tc-sgp611-insecure.img -
USB Mass Storage Device (USB\VID_0FCE&PID_E1C0&REV_0232) appears in a 7-10 seconds, and no more devices.
Click to expand...
Click to collapse
Also I have my tablet set to MTP mode. Maybe it makes a difference.
Settings -> Xperia connections -> USB connection -> USB connection mode (translated from Swedish so it may not be the exact wording in English.)
ejdan said:
Also I have my tablet set to MTP mode. Maybe it makes a difference.
Settings -> Xperia connections -> USB connection -> USB connection mode (translated from Swedish so it may not be the exact wording in English.)
Click to expand...
Click to collapse
Yes, mode is MTP. When booting insecure - mass storage device NOT connect SD or internal flash, just disk without any access.
Maybe you make other steps or settings? that may affect...
alex9x said:
Yes, mode is MTP. When booting insecure - mass storage device NOT connect SD or internal flash, just disk without any access.
Maybe you make other steps or settings? that may affect...
Click to expand...
Click to collapse
Ok, then I do not know. The kernel I used is for SGP611 so maybe you need a different kernel.
ejdan said:
I have SGP611 16GB Wifi version and I do not know if SGP621 uses the exact same kernel.
Click to expand...
Click to collapse
i don't understand this.
i have the 32GB wifi only version and it says model number SGP621. What exactly is the SGP611 ?
Just a thought. Make sure you have the updated version of adb.exe installed. Previous versions will not work with KK. You will get no devices when doing "adb devices". If your tab is running, and adb debugging is enabled, and you can't get it to display devices (and no security notice on the tab), update your adb.exe
Also, when you push SU and the apk, you may want to do a chmod . Here's an example I used on the A700 tabs from my bat file, note your directories may need to be changed, but you get the general idea;
Code:
adb remount
adb push su /system/xbin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell chmod 6755 /system/xbin/su
adb shell chmod 0755 /system/xbin/busybox
adb shell chmod 0644 /system/app/Superuser.apk
cls
echo Installing busybox
adb shell /system/xbin/busybox --install -s /system/xbin
Just some info.
a user said:
i don't understand this.
i have the 32GB wifi only version and it says model number SGP621. What exactly is the SGP611 ?
Click to expand...
Click to collapse
SGP611 is 16GB wifi only version. I think the kernel, ramdisk and system should be the same for 16GB and 32GB versions but LTE version may be different.
According to Sony kernel docs the SGP611 and SGP612 uses the same config and SGP621/SGP641 is a different config.
Xperia Z3 Tablet Compact SGP621/SGP641 => shinano_scorpion_defconfig
Xperia Z3 Tablet Compact SGP611/SGP612 => shinano_scorpion_windy_defconfig
Click to expand...
Click to collapse
In Sweden 3 versions are available from the Sony online store:
16 GB Wi-Fi® SGP611NB
32 GB Wi-Fi® SGP612NB
LTE/4G 16 GB SGP621NB
Moscow Desire said:
Just a thought. Make sure you have the updated version of adb.exe installed. Previous versions will not work with KK. You will get no devices when doing "adb devices". If your tab is running, and adb debugging is enabled, and you can't get it to display devices (and no security notice on the tab), update your adb.exe
Also, when you push SU and the apk, you may want to do a chmod . Here's an example I used on the A700 tabs from my bat file, note your directories may need to be changed, but you get the general idea;
Code:
adb remount
adb push su /system/xbin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell chmod 6755 /system/xbin/su
adb shell chmod 0755 /system/xbin/busybox
adb shell chmod 0644 /system/app/Superuser.apk
cls
echo Installing busybox
adb shell /system/xbin/busybox --install -s /system/xbin
Just some info.
Click to expand...
Click to collapse
chmod is not enough for KitKat because of SELinux. Take a look at the update script from superuser 2.16 and the chcon command to change file SELinux security context.
ejdan said:
chmod is not enough for KitKat because of SELinux. Take a look at the update script from superuser 2.16 and the chcon command to change file SELinux security context.
Click to expand...
Click to collapse
Thanks for the info. KK is new for me since coming off the Iconia tabs.
Your very much welcomed Ejdan, I will try your rooting method when i get home tonight and i will report back if i have success because i have been trying to root this tablet now for nearly two weeks, I tried all the rooting methods, apks and recoveries as they all failed but now we have hope
ejdan said:
SGP611 is 16GB wifi only version. I think the kernel, ramdisk and system should be the same for 16GB and 32GB versions but LTE version may be different.
According to Sony kernel docs the SGP611 and SGP612 uses the same config and SGP621/SGP641 is a different config.
In Sweden 3 versions are available from the Sony online store:
16 GB Wi-Fi® SGP611NB
32 GB Wi-Fi® SGP612NB
LTE/4G 16 GB SGP621NB
Click to expand...
Click to collapse
I reassamble boot.img from downloaded firmware (from sony site, with flashtool) with correct kernel and dt_image from original firmware - the same result! the same usb storage unknown device.
611 have "SoMC Scorpion WINDY"
621 have "SoMC Scorpion ROW"
flashtool log while manipulations...
Code:
24/032/2014 23:32:52 - INFO - Device disconnected
24/033/2014 23:33:08 - INFO - Device connected in fastboot mode
24/033/2014 23:33:32 - INFO - Device disconnected
24/033/2014 23:33:41 - INFO - Device connected with USB debugging off
24/033/2014 23:33:41 - INFO - For 2011 devices line, be sure you are not in MTP mode
24/034/2014 23:34:06 - INFO - List of connected devices (Device Id) :
24/034/2014 23:34:06 - INFO - - USB\VID_0FCE&PID_E1C0\[my_serial] Driver installed : true
24/034/2014 23:34:06 - INFO - List of ADB devices :
24/034/2014 23:34:06 - INFO - - none
24/034/2014 23:34:06 - INFO - List of fastboot devices :
24/034/2014 23:34:06 - INFO - - none
What may be problem? Maybe another settings in tablet?
Moscow Desire said:
Just a thought. Make sure you have the updated version of adb.exe installed. Previous versions will not work with KK. You will get no devices when doing "adb devices". If your tab is running, and adb debugging is enabled, and you can't get it to display devices (and no security notice on the tab), update your adb.exe
Click to expand...
Click to collapse
adb.exe downloaded from site yesterday, this is not adb error - no adb device in device manager, seems that adbd not started on tablet or just asking for permission in a black screen... but when booting normal - adb device OK and no any permission/RSAkey questions.
Normal boot:
Code:
25/035/2014 00:35:28 - INFO - List of connected devices (Device Id) :
25/035/2014 00:35:28 - INFO - - USB\VID_0FCE&PID_51C0&MI_00\7&13ECB37&0&0000 Driver installed : true
25/035/2014 00:35:28 - INFO - - USB\VID_0FCE&PID_51C0&MI_01\7&13ECB37&0&0001 Driver installed : true
25/035/2014 00:35:28 - INFO - - USB\VID_0FCE&PID_51C0\C[serial]N Driver installed : true
25/035/2014 00:35:28 - INFO - List of ADB devices :
25/035/2014 00:35:28 - INFO - - C[serial]N
25/035/2014 00:35:28 - INFO - List of fastboot devices :
25/035/2014 00:35:28 - INFO - - none