ADB reboot how can i do it? - EVO 4G Q&A, Help & Troubleshooting

HI , how can i do ADB Reboot for HTC EVO 4 for adb shell
Thanks

Uhh... adb shell reboot? that's it....

Or if you are already in the shell, reboot
Sent from my PC36100 using XDA App

It's just that easy

To clarify:
Code:
adb shell reboot
or
Code:
adb shell
reboot
or even
Code:
adb shell reboot recovery
That one will take you into the recovery environment.

SilverZero said:
To clarify:
Code:
adb shell reboot
or
Code:
adb shell
reboot
or even
Code:
adb shell reboot recovery
That one will take you into the recovery environment.
Click to expand...
Click to collapse
lol, you don't need the shell command to reboot
just
adb reboot
Click to expand...
Click to collapse
or, to get into recovery
adb reboot recovery
Click to expand...
Click to collapse

Oops, my mistake. I knew that, too.

timothydonohue said:
llol, you don't need the shell command to reboot
just
Quote:
adb reboot
or, to get into recovery
Quote:
adb reboot recovery
Click to expand...
Click to collapse
Which version of adb supports that? I'm using 1.0.20 and the command adb reboot just displays the command help.

good to know!

tdusen said:
Which version of adb supports that? I'm using 1.0.20 and the command adb reboot just displays the command help.
Click to expand...
Click to collapse
AFAIK, they all support it. the only reason i can think of that it wouldn't work would be if you haven't loaded the drivers for your device. does
Code:
adb devices
give you a response?
or, perhaps you need to update your sdk? i haven't had a problem with an android device yet, as long as i've kept the sdk updated, and my drivers functional.
of course, that means modifying my rules file on ubuntu, but i only have to do that once. had to do it for the nexus one, and for the evo, because the identifier tag is distinct for each...
on windows it needed drivers. on ubuntu it needed a rule made.

To answer my own question. ADB reboot did not work in version 1.0.20 that came with the android 1.5 sdk. I updated to the 2.2 SDK which includes ADB version 1.0.26. ADB reboot works with this version.

Related

Setting Up Adb on Mac *CLOSED*

I have my Evo rooted with DC 3.1.1 and I also have Nand Unlock via Toasts Way. But I did all of this using Windows. I already installed Android SDK for Mac. But every time I try to execute a command after I do the cd /android-sdk/tools. It just says -bash: adb: command not found. Can anyone give me a hand?
same issue for me
nitty917 said:
same issue for me
Click to expand...
Click to collapse
If you need help. PM Me.
Use ./adb instead of adb
BearCavalry said:
Use ./adb instead of adb
Click to expand...
Click to collapse
That wont help at all.

Help using ADB to push an app

Hi all, I am using a froyo rom based on richardtrips rom.
I'm trying to push a themed facebook apk. I have placed the apk in the tools folder.
This is what I did.. Boot to recovery, then open a cmd on my windows laptop. I then did the cd to go to my adb tools folder.
Then I typed
Code:
adb remount
This gave me an error saying error 0.
So I tried while the handset was booted normally. The remount was successful.
I then typed
Code:
adb push system/app/facebook.apk
This just gave me the help list with details of all the commands.
Can anyone tell me where I am going wrong?
how about
adb shell mount /system
adb push C:\Facebook.apk /system/app/
adb reboot
MasDroid said:
how about
adb shell mount /system
adb push C:\Facebook.apk /system/app/
adb reboot
Click to expand...
Click to collapse
This one seems to have worked. Thanks very much. I'm half sleeping and it was doing my head in
socktug said:
This one seems to have worked. Thanks very much. I'm half sleeping and it was doing my head in
Click to expand...
Click to collapse
No problem bud
It's pretty late here too and my eyes are half open and they feel as if they are burning lol.

adb files needed on sdcard?

Need lil help with adb... reinstalled all drivers and reinstalled android sdk and install all tools/updates.. still giving me same no adb errors.. Im nand unlock with engineering bootloader.
wasd321 said:
Need lil help with adb... reinstalled all drivers and reinstalled android sdk and install all tools/updates.. still giving me same no adb errors.. Im nand unlock with engineering bootloader.
Click to expand...
Click to collapse
Your problem is that you're entering adb commands inside shell.
Once you see the # sign, after typing adb shell, that means that the adb commands will no longer work. So, your commands that begin with adb will NOT work if you see the # sign..
Also, for commands like adb devices and remount, they need to be run outside of shell or rather from your AndroidSDK\tools PATH directly.
This will work:
Code:
C:\android-sdk\tools:
adb remount
adb devices
adb shell
This won't work:
Code:
C:\android-sdk\tools:
# adb remount
# adb devices
# adb shell
Notice the # sign (this happens when you type adb shell), this means you're now root and now using shell -- you cannot run the adb commands inside shell, you have to instead use Linux commands, or specifically commands from BusyBox.
Just to clarify: Some commands can be sent outside of the shell, but they have to be preceded by "adb". For example:
Code:
adb reboot recovery
Others will only work inside of the shell, like ls, mv, cd, and so forth. Search for an adb command listing (you do have a Google phone, after all) and it may help to familiarize yourself with basic Linux terminal commands as well - a lot of them are accepted by adb.
SilverZero said:
Just to clarify: Some commands can be sent outside of the shell, but they have to be preceded by "adb". For example:
Code:
adb reboot recovery
Others will only work inside of the shell, like ls, mv, cd, and so forth. Search for an adb command listing (you do have a Google phone, after all) and it may help to familiarize yourself with basic Linux terminal commands as well - a lot of them are accepted by adb.
Click to expand...
Click to collapse
Yea, I was aware of this, just decided not to mention it. Thanks for pointing it out though.

[N2E] Nook 2nd Edition Touch - USB ADB Drivers

Attached are Modified ADB USB Drivers for, when available via uRamdisk, ADB shell access through USB/Command Prompt.
Run adbfix.bat and follow the instructions. Currently, for me at least, it will only install the "SingleAdbInterface" connection not the "CompositeAdbInterface" since ADB only currently works wireless.
Again, don't flame because this doesn't work yet...it will once an updated uRamdisk is released with Command Prompt.
Enjoy
Totally not DOS man. It is just Command Prompt.
Nburnes said:
Totally not DOS man. It is just Command Prompt.
Click to expand...
Click to collapse
you know what I mean I'm just that old.

[GUIDE][US WIFI & 3G] How To Root Your Xoom From 3.2 Stock [PC & Mac]

**THIS IS FOR US WIFI & 3G XOOM**​
This guide in no way implies or expresses any warranties.
What you choose to do with your equipment is your sole responsibilty.​
________________________________________________________________________________________​
SUMMARY
You must already be running Honeycomb 3.2 on your Xoom **DO NOT USE WITH HC 3.2.1. IT HAS BEEN REPORTED TO CAUSE WIFI FAILURES** USE THIS TO ROOT HC 3.2 AND THEN UPDATE TO 3.2.1 USING THIS METHOD.​
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be performing steps in ADB. If you are not familiar with this, read HERE first.​
You will need Xoom USB drivers and Fastboot​
You will need the WIFI boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)​
OR You will need the 3G Verizon boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)​
You will need Superuser.apk and su binary to enable functioning root​
**Before you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development -->USB Debugging**​
PROCEDURE
Download and unzip files. Place rootboot.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.​
Type; adb reboot bootloader​
Type; fastboot oem unlock - and follow the steps on your xoom's screen (You have to accept the terms by pressing the volume down key, and then select 'accept' by pressing the volume up key.)​
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.​
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)​
Type; fastboot flash boot rootboot.img (for WiFi)​
OR Type; fastboot flash boot 3Grootboot.img (for 3G Verizon)​
Type; fastboot reboot ​
Allow the xoom to boot completely - your xoom should be in normal operating mode for the remainder of the process.​
In the command window on your PC type; adb remount​
Type; adb push su /system/bin​
Type; adb shell​
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)​
Type; chmod 4755 /system/bin/su ​
Type; exit​
Type; adb push Superuser.apk /system/app​
Thats it...your done!! Unplug the xoom and reboot. Your xoom is now stock rooted. You can now flash ClockworkMod, other kernels and roms. To verify root, download a root user app from the market and run it. You should be prompted to allow superuser permissions.​
Mac Only Procedure​
You will need fastboot for mac - download HERE​
Open a terminal (located in the utilities folder)
Navigate to your sdk/platform-tools folder
Type; ./adb devices - (look for the xoom serial number to show its connected.)
Type; ./adb reboot bootloader
Type; chmod 755 fastboot
Type; ./fastboot oem unlock
Type; adb reboot bootloader
Type; ./fastboot flash boot rootboot.img
Type; ./fastboot reboot
Type; ./adb remount
Type; ./adb push su /system/bin
Type; ./adb shell
Type; chmod 4755 /system/bin/su
Type; exit
Type; ./adb push Superuser.apk /system/app
Disconnect and reboot xoom. Download a root app and test.​
If you found this helpfull press the THANKS button.​
Excellent write-up, I'll try this when I get a chance.
Been trying to downgrade and then get to the rooted, stock 3.2 using a couple routes shown here. They seem to create an issue with CWM not sticking...
Works great!
I just flashed back to 3.01, re-locked the WiFi Xoom (USA), OTA'd to 3.1 and followed that with the OTA to 3.2. I then unlocked and went thru your rooting procedure and it worked great. All tests indicate a successful root. Thanks for the practical guide!
thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?
_delice_doluca_ said:
thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?
Click to expand...
Click to collapse
It is only a boot partition with rooted stock 3.2 kernel.
Sent from my HD2
[*]In the command window on your PC type; adb remount​[*]Type; adb push su /system/bin​[*]Type; adb shell​[*]Type; ln -s /system/bin/su /system/xbin/su ​[*]Type; chmod 4755 /system/bin/su ​[*]Type; exit​[*]Type; adb push Superuser.apk /system/app​
Click to expand...
Click to collapse
when I type adb remount after completely boot, I've got error device not found !!! any idea??
Hussain Isa said:
when I type adb remount after completely boot, I've got error device not found !!! any idea??
Click to expand...
Click to collapse
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.
Wow that was easy... Why cant all android devices be this open and straightforward? Im sooo pissed at HTC with the EVO 3D. Cant wait for the Galaxy S2 to come out
Mad respect to Motorola for getting this one right
And last but not least, Thanks so much to the OP for the great writeup!
jase33 said:
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.
Click to expand...
Click to collapse
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App
Hussain Isa said:
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Are you certain you have unlocked the bootloader?
Sent from my HD2
jase33 said:
Are you certain you have unlocked the bootloader?
Click to expand...
Click to collapse
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App
Hussain Isa said:
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App
Click to expand...
Click to collapse
If you get an error please post exactly what it says.
Sent from my Xoom
Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.
droidx1978z4 said:
Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.
Click to expand...
Click to collapse
Glad to here it! And thanks for pointing that out....I will clarify that in the op for others.
Sent from my HD2
thanks jase33 my problem was with the driver, I re-install it & now rooted
Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
WOW! Thanks jase33 that was painless.
Everything worked great, just as you said it would.
fwempa said:
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like you worked it out.
Sent from my HD2
Where did you get fastboot for Linux. I just get my self a xoom today, I'm planning to root it but my laptop is running ubuntu
Sent from my Nexus One using XDA App
fwempa said:
Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Reinstall the driver, that will solve your problem
Sent from my Xoom using XDA Premium App

Categories

Resources