Related
Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Now, [Get new sdk (1.5r3) to work]
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r3+
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - Here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
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 r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-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
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 jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l 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
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 specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP 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.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> - Example: adb pull /data/app_s/Stock.apk
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.
-------bump------
Good guide, pretty simple... Ill bookmark this, so I can send people that needs help here.
i have attached a zip that has the files i use to get basic use like for doing root to stock to upgrading 2.1-2.2 and other small things.
extract to C:\fastboot
in C:\fastboot you will find a "cmd" batch file. just run it and it should be ready for you to type in adb commands or fastboot. just make sure your in debug mode by doing all in the first post for installing drivers and all that.
U seriously bumped this thread? Lmfao
help?
i was trying adb and i got!
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
K:\>adb devices
List of devices attached
HT07YHL02294 offline
HT07YHL02294 device
K:\>adb remount
error: more than one device and emulator
Click to expand...
Click to collapse
ADB
i have this message Permission Denied what should i do?
thank you D200P13 soo much. i got it working thanks to your files
X10 adb issues
Can't get it to work for my X10.
ADB does not see my X10 when connected, have tried all mentioned above several times, no luck.
USB drivers seem not to install.
Do i need something special for my X10 to connect via ADB ?
p2dewit said:
Can't get it to work for my X10.
ADB does not see my X10 when connected, have tried all mentioned above several times, no luck.
USB drivers seem not to install.
Do i need something special for my X10 to connect via ADB ?
Click to expand...
Click to collapse
Turn telephone i debug mode.
when i type adb it says that it's an unrecognized command.
That's because you haven't navigated to the folder where the adb file is located...
Sent from my Nexus One using XDA App
danger-rat said:
That's because you haven't navigated to the folder where the adb file is located...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Isn't it in the android-sdk-windows folder?
EDIT
nvm found it. it's in another folder....thanks
when i run adb shell, it doesn't give me a # it gives me $. what do i do?
What are you trying to do?
Sent from my Nexus One using XDA App
Trying to flash a rom on my phone (x10) and was making sure adb is working properly before i do anything. When flashing the new rom there's some bugs that require adb to fix. From my understanding "$" means i don't have su access. Thanks for the help btw. Sorry for bothering you. Just taking proper precautions.
EDIT
Sorry again. Found my answer. I forgot to unlock my device to accept superuser permissions. Thanks for your help
to check ur phone is detected by adb....
i type "adb shell" in cmd,and according 2 u i should show #.....but it shows $ to me......why?
To check connection, type "adb devices"
"adb shell" will allow you to work remotely on your device. If the $ doesn't change to #, then you don't have root access.
Sent from my Nexus One using XDA App
If your just trying to set up adb to riot your device, I put this together to make things much easier...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
Where is the Mac Specific version. Everything you posted is for windows mate!
I wanted to ask this in the actual thread but 10 post limit...
Anyway,
I can't get any GPS lock on my I9000, Onemsomic's ICS RC3.1, JVU modem.
I tried changing the NetworkLocation.apk by following this post http://forum.xda-developers.com/showthread.php?p=21351809#post21351809
but since I have absolutely no idea how to use ADB I couldn't do the "change mode to 0644" step.
Someone help a noob?
Thanks.
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
AurosGamma said:
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
Click to expand...
Click to collapse
I get a "device not found" error after adb remount. What should I do?
hadar.shamir said:
I get a "device not found" error after adb remount. What should I do?
Click to expand...
Click to collapse
Well I have been looking here and there, and I found that adb doesn't work directly on the phone, you must use adb from your pc. So, this is what you should do from now on:
Install Java SDK
Install Android SDK
Turn on "USB Debugging" in your SGS settings
Connect the Device to the PC
And finally, use the following commands (from the PC):
Code:
// Go to the folder where you put the *.apk
cd C:\users\exampleuser\Documents\ // or /home/exampleuser/Documents/ if you're using linux
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note:
The text after the double-slash ( // ), must not be written in the console, they are just comments
You need to install the SDK's because there it is where the adb tool (and tools needed by adb) is found, so, good luck!
all is good until the last step whats going on?
[email protected]:/tmp/share$ tar xvf motoshare.tgz
adb
busybox
pwn
su
Superuser.apk
[email protected]:/tmp/share$ sudo chown root:root pwn
[email protected]:/tmp/share$ sudo chmod 6755 pwn
[email protected]:/tmp/share$ /tmp/share/adb shell /storage/rfs0/pwn
bash: /tmp/share/adb: No such file or directory
[email protected]:/tmp/share$
Please give me the response for the terminal command:
ls -l /tmp/share/adb
re jb root
[email protected]:/tmp/share$ ls -l /tmp/share/adb
-rwsr-sr-x 1 jody jody 204436 Feb 11 11:49 /tmp/share/adb
jodybgoode said:
[email protected]:/tmp/share$ ls -l /tmp/share/adb
-rwsr-sr-x 1 jody jody 204436 Feb 11 11:49 /tmp/share/adb
Click to expand...
Click to collapse
I will get back to you after I talk with Dan. Unless another set of eyes knows the solution.
Sent from my MB886 using xda app-developers app
Try running the last command as simply "adb shell /storage/rfs0/pwn"
(i.e. without the prefix /tmp/share/)
Help confused
djrbliss said:
As promised, this post describes how to root the Atrix HD Jelly Bean build. This should also work on other Motorola 4.1.2 builds (Razr/Razr Maxx, Razr HD, Razr M, etc.).
The exploit requires setting up a special Samba share and mounting this share on your phone using the File Manager app. I apologize that this process may seem involved for some of you, and request that members of this community help each other out if some of you are having problems completing the procedure. I'm not able to provide individual tech support to every user who wants to root this phone.
The following instructions require a working Linux installation. The following instructions are for Ubuntu. If you don't want to install Ubuntu permanently on your machine, I suggest using a LiveCD installation. Instructions on setting this up are described here:
https://help.ubuntu.com/community/LiveCD#How-To_LiveCD_Ubuntu
Once you're booted into Ubuntu, open a terminal. Create a new directory for your Samba share:
Code:
mkdir /tmp/share
Next, install the samba package:
Code:
sudo apt-get install samba
Edit the configuration file for samba:
Code:
sudo gedit /etc/samba/smb.conf
Add the following lines to the end of the configuration file and save your changes:
Code:
[share]
path = /tmp/share
available = yes
valid users = guest
read only = yes
browsable = yes
public = yes
Close the text editor once you've saved your changes.
Next, create a user for the Samba share by typing in the terminal:
Code:
sudo useradd guest -m -G users
Set a password for the new user. Remember this password:
Code:
sudo passwd guest
Provide a password here and press enter. You won't see the characters you're typing, so be careful.
Next, set a password on the share. Use the same password you just provided:
Code:
sudo smbpasswd -a guest
Type the password you created before and press enter.
Next, restart the Samba server:
Code:
sudo restart smbd
Finally, download and prepare the required files to the Samba share:
Code:
cd /tmp/share
wget [url]http://vulnfactory.org/public/motoshare.tgz[/url]
tar xvf motoshare.tgz
sudo chown root:root pwn
sudo chmod 6755 pwn
At this point, you'll need to know the IP address of your Linux host, which you can get by running "ifconfig" from your terminal (it should be of the form "192.168.x.x").
Next, move over to your Android device. Ensure you have enabled USB Debugging Mode (under Settings -> Development Settings). Ensure your device is connected via Wifi.
Open the "File Manager" app, and select "Remote storage". Click "Add storage", and fill in fields as follows:
Code:
Host IP address: [your Linux machine's IP address]
Domain name: WORKGROUP
Shared folder name: share
User: guest
Password: [the password you created above]
At this point, the phone will mount your Linux share. To complete the process, plug in your phone via USB to your Linux machine, and type the following in your Linux terminal:
Code:
sudo /tmp/share/adb kill-server
sudo /tmp/share/adb shell /storage/rfs0/pwn
If it's successful, this should print "[+] Rooting complete!".
Finally, install Supersu by typing the following in the terminal:
Code:
sudo /tmp/share/adb install /tmp/share/eu.chainfire.supersu.apk
Congratulations, enjoy your rooted device.
I can't stress this enough: I can't provide individualized tech support for everyone on this forum. Please help each other.
TTLayland has been successfully rooted using this technique and has volunteered to help. If you get stuck and can't find support on these forums, feel free to email him at ttlayland (at) gmail (dot) com.
Paypal:
http://goo.gl/zBGb0
Click to expand...
Click to collapse
Got this error:
[email protected]:/tmp/share$ sudo /tmp/share/adb shell /storage/rfs0/pwn
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
mount: Operation not permitted
sh: can't create /system/xbin/busybox: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
sh: busybox: not found
cp: /system/bin/su: Read-only file system
Unable to chown /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
[+] Rooting complete!
[email protected]:/tmp/share$
Then it says: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" when opening SuperSU
PLEASE HELP HERE OR MY EMAIL! : [email protected]
Thanks in advanced
progrockguy said:
Try running the last command as simply "adb shell /storage/rfs0/pwn"
(i.e. without the prefix /tmp/share/)
Click to expand...
Click to collapse
progrockguy said:
Try running the last command as simply "adb shell /storage/rfs0/pwn"
(i.e. without the prefix /tmp/share/)
Click to expand...
Click to collapse
that worked kinda. well it says rooting complete but when i update superuser or root checker says root fail
Please Help: error: device offline
I am getting the following error
[email protected]:/tmp/share$ sudo /tmp/share/adb kill-server
[email protected]:/tmp/share$ sudo /tmp/share/adb shell /storage/rfs0/pwn
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
[email protected]:/tmp/share$
I am running the LiveCD in VMware Workstation
Sorry for the duplicate posts
worked perfectly after i used a 32 bit live disk
jodybgoode said:
worked perfectly after i used a 32 bit live disk[/QUOTE
Did you use Ubuntu and which version?
do you have a link to the CD?
Did you boot a machine or you used VMware or Virtualbox?
Click to expand...
Click to collapse
Why would anyone even attempt to use a VM for this simple root method? You could've been rooted already if you had just followed the instructions.
Same problem here. I couldn't get past the adb kill-server command. It would tell me there is no such directory. If any one can get past this can someone please tell me what they did to get past it.
Black_halo said:
Same problem here. I couldn't get past the adb kill-server command. It would tell me there is no such directory. If any one can get past this can someone please tell me what they did to get past it.
Click to expand...
Click to collapse
I am stuck, I have tried so many machine to no luck
Please someone help
Start over and just copy and paste each single line and hit enter do not copy multiple code lines .
ATRIX HD running BATAKANG 1.10
sickkside13 said:
Start over and just copy and paste each single line and hit enter do not copy multiple code lines .
ATRIX HD running BATAKANG 1.10
Click to expand...
Click to collapse
I did, no luck
Dammz man idk what else to tell you yesterday i spend all day trying to root too but just when i was about to give up i got everything g working
ATRIX HD running BATAKANG 1.10
sickkside13 said:
Dammz man idk what else to tell you yesterday i spend all day trying to root too but just when i was about to give up i got everything g working
ATRIX HD running BATAKANG 1.10
Click to expand...
Click to collapse
hehehehe
Does the root method have anything to do with having android sdk and ndk on your system? Im thinking thats what it is now. Would i have to have linux sdk to run with terminal root or windows sdk?
Black_halo said:
Does the root method have anything to do with having android sdk and ndk on your system? Im thinking thats what it is now. Would i have to have linux sdk to run with terminal root or windows sdk?
Click to expand...
Click to collapse
No, you don't need the Android SDK/NDK, since I included a copy of ADB in the tarball file that you extracted to /tmp/share.
What's the output of "ls -l /tmp/share/adb" on your Linux machine?
I had to re-flash official JB firmware in RSD Lite before the exploit would work. Before that, the Exploit would return "Root Complete", but there was no root access (though I could su to # in adb). I run Ubuntu 12.04 x64 at work already with Windows in VirtualBox.
RSD Lite doesn't seem to want to complete a flash in the Windows VMs I run in VirtualBox at work, so I waited until I got home and used my Windows 8 Pro machine to RSD the phone with the official JB firmware. I run Ubuntu 12.04 in a VirtualBox on that machine already, so after the RSD flash, I ran the exploit from that VM - BINGO - worked on the first try.
Failing other options, you might want to try re-flashing JB in RSD Lite and running the exploit on a fresh device.
I used the firmware in this thread (To fix the issue the thread is about):
http://forum.xda-developers.com/showthread.php?t=2057078
If you decide to try that, Be SURE to get the firmware zip AND THE XML and replace the XML before flashing!!
Question 1: Is this normal, if yes, then how can i find my CID?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Question 2: S-OFF or HTCDev unlock?
Question 3: If S-OFF, which method is easier/better revolutionary or moonshine?
Asad_612 said:
Question 1: Is this normal, if yes, then how can i find my CID?
View attachment 2091535
Question 2: S-OFF or HTCDev unlock?
Question 3: If S-OFF, which method is easier/better revolutionary or moonshine?
Click to expand...
Click to collapse
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal preference. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
bobsie41 said:
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal preference. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
Click to expand...
Click to collapse
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
randykzc said:
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That is only if you do it with the instructions on HTCDEV. With S-OFf you can relock and it will show LOCKED.
fastboot oem readcid
randykzc said:
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
There is an ADB command to change it to 'locked' instead of 'relocked'. It's mentioned in revone's thread:
http://forum.xda-developers.com/showthread.php?t=2314582
I used revone to S-OFF and it was quite easy.
Code:
./revone -l
bobsie41 said:
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal prefierence. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
Click to expand...
Click to collapse
1. I saw other devices pictures which showed CID in bootloader mode, and also my previous HTC OneX had such information available.
2. I'be read somewhere users having issues with S-Off with HTC one. Previously I had Inc S and I S-Off it using revolutionary.
Thanks.
Asad_612 said:
1. I saw other devices pictures which showed CID in bootloader mode, and also my previous HTC OneX had such information available.
2. I'be read somewhere users having issues with S-Off with HTC one. Previously I had Inc S and I S-Off it using revolutionary.
3. Can you provide me the link of renove S-Off?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2314582
TarekElsakka said:
There is an ADB command to change it to 'locked' instead of 'relocked'. It's mentioned in revone's thread:
http://forum.xda-developers.com/showthread.php?t=2314582
I used revone to S-OFF and it was quite easy.
Code:
./revone -l
Click to expand...
Click to collapse
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Asad_612 said:
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Click to expand...
Click to collapse
Uncheck in settings/energy/fastboot and close (at the bottom). That may help.
gee2012 said:
Uncheck in settings/energy/fastboot and close (at the bottom). That may help.
Click to expand...
Click to collapse
unchecked, but still the same error :/
Asad_612 said:
unchecked, but still the same error :/
Click to expand...
Click to collapse
Is usb debugging enabled and is HTC Sync manager not running?
gee2012 said:
Is usb debugging enabled and is HTC Sync manager not running?
Click to expand...
Click to collapse
usb debuggin enabled and sync manager updated and running as well...still device not connected error
Asad_612 said:
usb debuggin enabled and sync manager updated and running as well...still device not connected error
Click to expand...
Click to collapse
You have to close sync manager (best is to uninstall except the drivers).
gee2012 said:
You have to close sync manager (best is to uninstall except the drivers).
Click to expand...
Click to collapse
Tried that too, still nothing ... is there any shortcup sort of adb files?
I dont know if there is an issue with my adb files or something else...cause i can start adb shell, but im having problem with it detecting my device...
Asad_612 said:
Tried that too, still nothing ... is there any shortcup sort of adb files?
I dont know if there is an issue with my adb files or something else...cause i can start adb shell, but im having problem with it detecting my device...
Click to expand...
Click to collapse
There is a problem with your drivers somehow, go to device manager in windows and delete the phone from the list. Reboot the pc and try again.
Asad_612 said:
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Click to expand...
Click to collapse
"adb push" command is not shell command!
you need type: adb push revone /data/local/tmp/ before you entered into shell by "adb shell".
1) adb push revone /data/local/tmp/
2) adb shell
3) and so on..
tash2013 said:
"adb push" command is not shell command!
you need type: adb push revone /data/local/tmp/ before you entered into shell by "adb shell".
1) adb push revone /data/local/tmp/
2) adb shell
3) and so on..
Click to expand...
Click to collapse
yea i figured that, but still got error, see this:
Code:
C:\fastboot>adb push revone /data/local/tmp/
2048 KB/s (648208 bytes in 0.309s)
C:\fastboot>cd /data/local/tmp
The system cannot find the path specified.
C:\fastboot>adb shell chmod 755 /data/local/tmp/revone
C:\fastboot>adb shell
[email protected]:/ $ busybox df -h
busybox df -h
/system/bin/sh: busybox: not found
127|[email protected]:/ $
Asad_612 said:
yea i figured that, but still got error, see this:
Code:
C:\fastboot>adb push revone /data/local/tmp/
2048 KB/s (648208 bytes in 0.309s)
C:\fastboot>cd /data/local/tmp
The system cannot find the path specified.
C:\fastboot>adb shell chmod 755 /data/local/tmp/revone
C:\fastboot>adb shell
[email protected]:/ $ busybox df -h
busybox df -h
/system/bin/sh: busybox: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
"C:\fastboot>cd /data/local/tmp" What is it??? You need here to specify a way to yours adb.exe file.
if youer adb.exe in c:\fastboot folder you need
1) c:\fastboot> adb shell
2) [email protected]:/ $ cd /data/local/tmp
3) [email protected]:/ $ chmod 755 revone
4) and so on ..regarding s-off thread
tash2013 said:
"C:\fastboot>cd /data/local/tmp" What is it??? You need here to specify a way to yours adb.exe file.
if youer adb.exe in c:\fastboot folder you need
1) c:\fastboot> adb shell
2) [email protected]:/ $ cd /data/local/tmp
3) [email protected]:/ $ chmod 755 revone
4) and so on ..regarding s-off thread
Click to expand...
Click to collapse
My adb files are in c:\fastboot folder, i followed the process and this is the result, its still not detecting the device:
Code:
C:\fastboot>
C:\fastboot>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/revone
chmod 755 /data/local/tmp/revone
[email protected]:/data/local/tmp $ adb devices
adb devices
List of devices attached
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
251|[email protected]:/data/local/tmp $
I had some trouble getting S-OFF using HBOOT 1.57, and I finally got it. Here is what I did in hopes someone may find it useful:
Before you Begin:
If you get stuck at the white HTC Logo when booting or you get "Process com.htc.dialer isn't responding" at any point in this guide, or even before it, you are likely missing your Radio. (I don't know exactly how this happens, but it apparently does sometimes.) I had this problem once, and flashing the latest radio from here in recovery fixed it.
Steps:
Flash this ROM. (Other ROMs may work, but this one gave me no trouble at all)
Flash this Kernel. <-- Important! Firewater will fail if you don't do this!
Follow the Firewater Instructions to obtain S-OFF. It should work the very first time. (Use the "normal, rooted device method" set of instructions.)
You should now be S-OFF! After this, you can proceed to flash your favorite ROMs Kernels, and HBOOTs. If you would like to downgrade to HBOOT 1.44 (I did), you can find the files here.
Please post if this works for you or if you need help. Thanks to all the developers who made this possible!
Thank you very so much
thank you very much you helped me save my htc was like brick but since I got resurrect from your guide
Branchys said:
thank you very much you helped me save my htc was like brick but since I got resurrect from your guide
Click to expand...
Click to collapse
Awesome! Glad I could help.
Question
Pew446 said:
I had some trouble getting S-OFF using HBOOT 1.57, and I finally got it. Here is what I did in hopes someone may find it useful:
Before you Begin:
If you get stuck at the white HTC Logo when booting or you get "Process com.htc.dialer isn't responding" at any point in this guide, or even before it, you are likely missing your Radio. (I don't know exactly how this happens, but it apparently does sometimes.) I had this problem once, and flashing the latest radio from here in recovery fixed it.
Steps:
Flash this ROM. (Other ROMs may work, but this one gave me no trouble at all)
Flash this Kernel. <-- Important! Firewater will fail if you don't do this!
Follow the Firewater Instructions to obtain S-OFF. It should work the very first time. (Use the "normal, rooted device method" set of instructions.)
You should now be S-OFF! After this, you can proceed to flash your favorite ROMs Kernels, and HBOOTs. If you would like to downgrade to HBOOT 1.44 (I did), you can find the files here.
Please post if this works for you or if you need help. Thanks to all the developers who made this possible!
Click to expand...
Click to collapse
Hi, what specific ROM and Kernel version did you use to get Firewater to work? I have flashed rom Bad_Boyz_Sprint_ONE_Sense_6_v1.0 and Kernel ElementalX-sprint-m7-13.1 but USB debugging is not working and Firewater is not working properly, I am guessing its a kernel issue. I leave everything on default while installing Kernel thru TWRP. Can you confirm? I appreciate the help
DanielGalan said:
Hi, what specific ROM and Kernel version did you use to get Firewater to work? I have flashed rom Bad_Boyz_Sprint_ONE_Sense_6_v1.0 and Kernel ElementalX-sprint-m7-13.1 but USB debugging is not working and Firewater is not working properly, I am guessing its a kernel issue. I leave everything on default while installing Kernel thru TWRP. Can you confirm? I appreciate the help
Click to expand...
Click to collapse
Did you check if your fastboot drivers are working?
StormyNight said:
Did you check if your fastboot drivers are working?
Click to expand...
Click to collapse
Yes, I did fastboot devices and I got the device listed there. Although I could see that in the phone it does not appear the 4 bars of USB debugging. I had it checked in the Dev Options. When I do the same with the stock 4.4.2 I do get those 4 bars and the indication that the USB debugging is active.
DanielGalan said:
Yes, I did fastboot devices and I got the device listed there. Although I could see that in the phone it does not appear the 4 bars of USB debugging. I had it checked in the Dev Options. When I do the same with the stock 4.4.2 I do get those 4 bars and the indication that the USB debugging is active.
Click to expand...
Click to collapse
Does fastboot devices work in the bootloader?
StormyNight said:
Does fastboot devices work in the bootloader?
Click to expand...
Click to collapse
Yes it gets recognized. But when I turn on the phone and try to run the firewater commands it does nothing. No error nor the prompt of the disclaimer. I thought I better asked you and see if you have any idea of what could be wrong.
DanielGalan said:
Yes it gets recognized. But when I turn on the phone and try to run the firewater commands it does nothing. No error nor the prompt of the disclaimer. I thought I better asked you and see if you have any idea of what could be wrong.
Click to expand...
Click to collapse
firewater, I believe runs with the phone booted into android, not fastboot.
Aldo101t said:
firewater, I believe runs with the phone booted into android, not fastboot.
Click to expand...
Click to collapse
Yeah. I just booted to fastboot to check the drivers. When I push the firewater file I get success. Its just the last command that does no action.
DanielGalan said:
Yeah. I just booted to fastboot to check the drivers. When I push the firewater file I get success. Its just the last command that does no action.
Click to expand...
Click to collapse
Verify if the file access permissions changed.. it might be that chmod isn't working.
StormyNight said:
Verify if the file access permissions changed.. it might be that chmod isn't working.
Click to expand...
Click to collapse
Hi. I meant adb devices. And I was wondering how do I check the file permissions. Can I try to copy firewater with a root file manager ? Thank you
This is what I get in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
5927 KB/s (4522136 bytes in 0.745s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
After this, there is no action from firewater. I should get a warning prompt, but I don't.
DanielGalan said:
Hi. I meant adb devices. And I was wondering how do I check the file permissions. Can I try to copy firewater with a root file manager ? Thank you
This is what I get in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
5927 KB/s (4522136 bytes in 0.745s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
After this, there is no action from firewater. I should get a warning prompt, but I don't.
Click to expand...
Click to collapse
Are you doing adb reboot before doing adb wait-for-device? Also make sure that your device has no lock mechanism enabled (pattern lock etc).
StormyNight said:
Are you doing adb reboot before doing adb wait-for-device? Also make sure that your device has no lock mechanism enabled (pattern lock etc).
Click to expand...
Click to collapse
I do, this is what I found weird. Screenshot 1 is stock rom 4.4.2 and it says USB debugging enabled. Screenshot 2&3 is Bad_Boyz_Sprint_ONE_Sense_6_v1.0 ROM with its default kernel, it shows no USB debugging enabled even when its selected
DanielGalan said:
I do, this is what I found weird. Screenshot 1 is stock rom 4.4.2 and it says USB debugging enabled. Screenshot 2&3 is Bad_Boyz_Sprint_ONE_Sense_6_v1.0 ROM with its default kernel, it shows no USB debugging enabled even when its selected
Click to expand...
Click to collapse
No idea :S You might want to uncheck Verify apps over USB in Screenshot 3 btw.
StormyNight said:
No idea :S You might want to uncheck Verify apps over USB in Screenshot 3 btw.
Click to expand...
Click to collapse
I tried but no luck. Is there any other ROM I could try firewater with? I was thinking maybe the Venom.
DanielGalan said:
I tried but no luck. Is there any other ROM I could try firewater with? I was thinking maybe the Venom.
Click to expand...
Click to collapse
Try following the instructions on this post.
StormyNight said:
Try following the instructions on this post.
Click to expand...
Click to collapse
Thank you for bearing with me.
I did as indicated on that post, but still having issues with firewater. This is what I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA34MS906354 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
4533 KB/s (4522136 bytes in 0.974s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
There is no action after this
DanielGalan said:
Thank you for bearing with me.
I did as indicated on that post, but still having issues with firewater. This is what I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA34MS906354 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
4533 KB/s (4522136 bytes in 0.974s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
There is no action after this
Click to expand...
Click to collapse
Try flashing an older release of CyanogenMod - I'd try Snapshot M8.
StormyNight said:
Try flashing an older release of CyanogenMod - I'd try Snapshot M8.
Click to expand...
Click to collapse
Hi, I tried but I had the same results, the commands are accepted but there is no action after the last one . I'm gonna do a last attempt on my other computer and see if it works.