Related
So I go into cmd and into the sdk/tools directory and typed in adb devices. It shows my phone HT03xxxxxx offline. Am I missing something here?
I just wanted to reboot in recovery through there and its telling me that the device is offline.
I flashed fresh 2.1.2 and the su fix update if that means anything.
Edit--
I did a nandroid and flashed back to 2.1.1
Went into cmd and ran adb shell with no problem...
I just did a wipe and will reflash 2.1.2 and try it again
Dave2582 said:
So I go into cmd and into the sdk/tools directory and typed in adb devices. It shows my phone HT03xxxxxx offline. Am I missing something here?
I just wanted to reboot in recovery through there and its telling me that the device is offline.
I flashed fresh 2.1.2 and the su fix update if that means anything.
Click to expand...
Click to collapse
Are you using Windows or Linux? Either way; you should kill the adb server and try again. In Linux to do this:
sudo su ./adb kill-server
sudo su ./adb start-server
Then try running your adb commands again. (e.g. adb devices, adb shell)
To kill the server in windows:
adb kill-server
Click to expand...
Click to collapse
Then unplug your phone and plug it back in and see if that changes anything.
The Windows command to reboot into recovery via adb is:
adb reboot recovery
Click to expand...
Click to collapse
pseudoremora said:
Are you using Windows or Linux? Either way; you should kill the adb server and try again. In Linux to do this:
sudo su ./adb kill-server
sudo su ./adb start-server
Then try running your adb commands again. (e.g. adb devices, adb shell)
To kill the server in windows:
Then unplug your phone and plug it back in and see if that changes anything.
The Windows command to reboot into recovery via adb is:
Click to expand...
Click to collapse
I had 2.1.1, and flashed 2.1.2 with no wipe. I didn't reboot, but flashed the su fix zip file, and then I rebooted. Maybe that's why I didn't achieve any adb commands.
I did a data/factory wipe, then flashed 2.1.2. I rebooted and set my google account up. After it was up and running, I booted in recovery manually. I flashed the su fix and rebooted. Now I'm all set. I went into cmd and got my shell back. Now I'm all set. Just a pain in the ass and redownload all my apps again.
Thanks for your help though.
Hey guys im new here and new to android too. my android sdk doesnt seem to work anymore. when i typed adb shell, it will show daemon starts successfully. it worked flawlessly previously. however when i tried using adb command like adb devices all these, it will shows "adb not found" what does this mean? i open the command prompt at the tools folder and have tried to reinstall my samsung I9000 driver but still it doesnt work. Is it cos of the path i set is wrong or wad? Im using window 7 and the folder name of tat android sdk is called "android" on my desktop. can anyone help me with this??? thanks. i need the adb to work in order to install some game and root. thanks in advance
Reinstall SDK
i tried reinstalling driver and sdk and the result is still the same. any other suggestion?
Not sure if it helps, but I had problems installing i9000 drivers until I installed Kies. Kies installed all the drivers perfectly.
you have to restart the adb daemon as root, eg:
sudo ./adb kill-server
sudo ./adb start-server
edit: just read that you are using windows ... so run the command without he "sudo" but under the admin-user ...
I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!
Ok, so if you can see your phone through adb, then you are definitely on the right track. Unfortunately, I'm not really familiar with OS X anymore so I'm not quite sure how to do it. Just sit tight for now until someone who does use a Mac, or has more of a clue then I do can help you out.
But seriously, don't pull your hair out. It won't stay on your head forever ya know...
Edit: oops, just saw this is JI6 (Froyo) not JF6, so I can't help you, but here is a general overview:
from terminal inside Android sdk main directory:
tools/adb devices -> list all devices connected that ADB can see
tools/adb shell -> gets a normal user shell on your phone
tools/adb reboot recovery -> reboots into recovery mode, suitable for update.zip root method
--------------------------------
Place the root update.zip on internal sdcard.
from terminal inside Android sdk directory:
tools/adb reboot recovery
Select the update software option, and you will be done.
laxwillsch said:
I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!
Click to expand...
Click to collapse
Start simple:
If you open a terminal on the mac, and go to your android SDK tools folder; what happens when you type ADB shell?
Or if you type any of the ADB push commands?
You need to give more detail around what you are seeing for us to help you.
Ok so if I am in terminal and i type in my /android-sdk-mac_x86/tools nothing happens and it just says /android-sdk-mac_x86/tools is a directory. But if I type the same but with /tools/abd it opens the abd command lines, like how to write code. Then when I try to "adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin"
it says "-bash: adb: command not found"
however when I type laxwillsch$ /android-sdk-mac_x86/tools/adb shell
it does give me the drop down $
but when I then try to write the next line of code "chmod 0755 rageagainstthecage-arm5.bin"
it says "chmod: rageagainstthecage-arm5.bin: No such file or directory"
I am stumped I am beginning to think i need to buy a pc as I am very interested in android development and want to learn more, but it seems all the tutorials are run assuming you are on a PC
EDIT** I have downloaded the android SDK started pack, and the 2.2 root pack and they are all in my /android-sdk-mac_x86/tools folder that is directly on my Macintosh HD for simplicity
Do you know how to change directories (cd command)?
The problem is that you are trying to work in one directory, but all your tools are in another.
So change directories to the tools directory:
cd /android-sdk-mac_x86/tools/
now run your adb commands - you may have to type ./adb to tell your mac to look in the current directory for the adb command (that is what ./ means "start here")
Also, try to understand what is happening so you can more easily troubleshoot: chmod is a command to change permissions, and you are running it on the phone. If you can't push the file to the phone, then you can change it's permisssions. I guess you never got rageagainstthecage on the phone, so there is no way to chmod it.
If you can't do this on a mac, a PC is not easier. I use both, and like both, but you need to learn basic commands first - they apply to the mac terminal and the windows cmd prompt.
Getting root means moving in and out of the phone - adb shell - puts you in a terminal on the phone. So you really need to understand cd (change directory); pwd (present working directory - shows you where you are); cp (copy); and know your current path - what the ./ does.
I hope this helps, not trying to sound condescending - maybe practice a linux terminal tutorial would help
Thanks so much, I am at school right now and cant test out all that but you are really helping me understand all this! I will post tonight and let you know how it goes. again thank you
ok so i dont have my usb cable with me but I was playing around with the commands that you suggested and ureka! i finally got to a point where it says "h70-33-65-19:tools laxwillsch$" thats a first! and when i type pwd it shows "/android-sdk-mac_x86/tools" so that means I am working out of the right directory right? and from here I enable usb debugging connect my phone then just copy and paste the codes from the thread correct?
yes, it sounds like you are on the right track. But take it nice and slow when you follow the steps. It is very important that the commands are entered exactly as you see them.
Also, one step tells you to wait for something to run and kick you out of ADB - wait just like it says - takes about 45 seconds but feels like forever.
If you are in the tools directory - just by typing "adb" no quotes will give you whole page of adb commands - if you get a "command not found", then you need to add the ./ and make it ./adb
Hope this helps and again, read the commands step by step a couple times first so you understand what is happening.
In a nutsell, you push the rage file;
change its permissions, run it;
get kicked out of ADB and then open a new ADB shell;
you are now root;
remount the system partition to give you write access when it reboots;
reboot;
push over some files;
change permissions on files you pushed;
reboot;
Some things to know - SU is a command for gaining root access; when you use SU your prompt changes (in adb shell) from $ to #
If you are succesful you should see the SuperUser app listed in your apps.
Done and Done just rooted successfully couldnt have done it without you! thanks so much
Note: I would have posted this in the developement forum as I've tried following both threads. (These: http://forum.xda-developers.com/showthread.php?t=2271909 and http://forum.xda-developers.com/showthread.php?t=2128848). Everything works okay as far as CMD entries etc, and it boots up in fastboot, at which point KF First Aide says <waiting for device>, and the Kindle is just sitting on the fastboot logo. No errors or anything, it just sits there.
Holding power on the Kindle shuts it down, and it will boot up normally. But it doesn't look like flashing back to 7.2.3 is working, because it stills shows up as 7.4.6. (It is already rooted as well.)
Not really sure how to proceed from here, I'm trying to install CM10.2 on it ultimately.
Edit: Also, I did already make backups.
Sounds like the fastboot drivers aren't installing, once you see the fastboot logo, check the device manager for a device with a yellow triangle, if there is one its probably called tate-pvt or something like jem or otter2 then use the drivers in my signature by right clicking the device, hitting update drivers, and pointing it to where you extracted my drivers and once the the device is I stalled it should continue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Sounds like the fastboot drivers aren't installing, once you see the fastboot logo, check the device manager for a device with a yellow triangle, if there is one its probably called tate-pvt or something like jem or otter2 then use the drivers in my signature by right clicking the device, hitting update drivers, and pointing it to where you extracted my drivers and once the the device is I stalled it should continue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Looks like that was it, it's working now. Now to install PAC Man ROM.
Thanks!
Okay new problem.
"6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done."
I'm at this issue, and when I run adb it opens a cmd window which does something(lots of text scrolls), and then goes away(cmd then closes.). So I can't type the command in. Any ideas?
Well adb is a command line tool, so if you want to use it you need to run it from a command prompt...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Halo_003 said:
Okay new problem.
"6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done."
I'm at this issue, and when I run adb it opens a cmd window which does something(lots of text scrolls), and then goes away(cmd then closes.). So I can't type the command in. Any ideas?
Click to expand...
Click to collapse
You need to actually type command in your run box to open a dos prompt. THEN you can do the adb commands. Don't just try an adb command from your windows run box. It will run adb without modifiers, give you the help screen and then quit because windows thinks the program ran and completed.
NapalmDawn said:
You need to actually type command in your run box to open a dos prompt. THEN you can do the adb commands. Don't just try an adb command from your windows run box. It will run adb without modifiers, give you the help screen and then quit because windows thinks the program ran and completed.
Click to expand...
Click to collapse
Okay so here's what I didreplace *'s with h.)
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_36_38_376_zps0b71405b.jpg
Once in cmd, type adb and hit enter. Binary version looks good.
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_36_49_904_zps374e53f3.jpg
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_36_46_102_zpsaa0f7ff7.jpg
But then when trying sideload it doesn't work.
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_38_20_363_zps989da0dd.jpg
Am I doing it wrong?
Any ideas on how to get it working?
Halo_003 said:
Any ideas on how to get it working?
Click to expand...
Click to collapse
Stunts write up should get you there http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Halo_003 said:
Any ideas on how to get it working?
Click to expand...
Click to collapse
I got the chance to check out your DOS screenies.
There is no such command called sideload in some ADB versions. Here are the basic ADB commands.
3. Basic ADB commands
ADB push (sends files to your phone) -- adb push c:\example.apk /sdcard/example.apk
ADB pull (Receives files from your phone) -- adb pull /system/app/example.apk c:\example.apk
ADB install (installs application) -- adb install c:\example.apk
adb shell (Begins shell connection with phone)
adb reboot (reboots phone)
adb reboot recovery (reboots phone into recovery)
adb reboot bootloader (reboots the phone into bootloader/the white screen)
adb remount (remounts the system)
4. Commands to run while in ADB Shell
cd (changes directories) -- cd /system/app
ls (lists all files in the directory) -- cd /system/app
rm (removes files) -- rm /system/app/example.apk
cp (copies files) similar to cat -- cp /system/app/example.apk /sdcard/example.apk
cat (copies files) -- cat /system/app/example.apk > /sdcard/example.apk
exit (exits shell) -- exit
Click to expand...
Click to collapse
You have to make sure the ADB you have knows what the sideload command is.
Yep thank you guys! I got it working with that like LE gave me. Much appreciated!
LinearEquation said:
Stunts write up should get you there http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Click to expand...
Click to collapse
Ah yes! That was it! I wasn't doing the cd command so that's the issue I was having. Thank you!
Hi
I've been at this for a few hours now and I'm just getting nowhere. I know this is a common issue but I assure you I have read every other thread and tried everything I have seen.
I have a HTC One M7 on the UK network Three with CWM recovery. Previously it was running Android Revolution HD, I tried to install the other Android Revolution HD Google Edition and right at the very end when I was asked to install Superuser is where I started running into problems. As it stands, my device is in a bootloop. If I'm careful I can time it right and boot into bootloader. From here, trying to enter recovery just puts me back into a bootloop.
All my HTC Drivers are installed fresh as of today. If I run erase cache, get var or anything along those lines all I get is <waiting for device>. When plugged in the device displays in Device Manager with the following details. I'm on Windows 8.1.I can't post a screenshot so it's text.
Unknown USB device (device failed enumeration)
Device status: Windows stopped because this device has reported problems (code 43)
I can't even find a RUU for my device, if it would even help at this point. Here's a transcript of my bootloader info.
*** TAMPERED ***
*** RELOCKED ***
M7_ UL PVT SHIP S-OFF RH
CID-H3G_001
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Where do I go from here? Bootloader factory reset does nothing, trying to flash a ROM doesn't work because the device isn't recognised, etc. I'm totally lost. The only suggestion I've even found is that I might have more luck in Windows 7, but I only have one system which will take 8-9 hours to back up to an external HD and unless it was a 90%+ shot I want reinstalling Windows 7 to be an absolute last ditch attempt.
Is there anything I'm missing?
Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk
Harish_Kumar said:
Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've never used Linux but I'll make a live usb stick and try to work it out.
toyfights said:
I've never used Linux but I'll make a live usb stick and try to work it out.
Click to expand...
Click to collapse
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
toyfights said:
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
Click to expand...
Click to collapse
Cool
Sent from my HTC One using Tapatalk
Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.