when i type adb reboot bootloader i receive the following message:"error:device not found".
Related
I have a galaxy light I an attempting to abd sideload a zip via recovery. I am able to boot into recovery, when I "adb devices" nothing appears that is all fine. The recovery has an option for adb update, I select this. It shows up as use "adb sideload <filename>" via usb. At that point "adb devices" shows the device "<serial number> sideload", I then attemptto "adb sideload <filename>" filename is a zip file in the correct directory. I then get a list of adb commands as if "adb sideload" is not a recognized command. I am using the latest adb version of 1.0.29. note: when i recheck "adb devices" it will now come back as "<serial no> host". the "adb sideload <filename>" prompt is still on the recovery screen. Does anyone know why my sideload cmd is not working? thanks
bg.
solved
no more problems reinstalled platform and tools.
bg
Hi All,
I am a newbie here. I issue following "adb shell getprop" adb command to retrieve device properties. This just hang out no output printed on the terminal or no prompt appears.
I then kill it at send "adb shell getprop ro.build.version.release" but it also just hang out.
I am working on ubuntu12.04. adb devices list one device which is connected.
Please help, how can I read device properties from adb (such as OS, model, manufacturer etc..)
My device is not rooted.
Many thanks!
IUA
Hey,
Having problems for entering ADB codes. How do you enter something like $ fastboot oem lock. Thanks
try
"adb shell" press enter
"su" press enter
now you have the "$" at start of the command
Sent from my GT-P3100 using XDA Free mobile app
You type that command in a command line on your computer if you have adb and fastboot installed and your phone is plugged via usb.
$ is basically a sign for command line in linux, your line starts with $ for a normal user and # for root.
To sum up, if you see something starting with $, that means it is a command.
Search the forums for more info about installing adb and fastboot if you didn't already.
Hi all,
I have a Huawei P7 mini (Ascend G6-L11, P7MiniV100R001C432B370, CUSTC186D005) and I'm trying to unlock the bootloader in order to install TWRP.
Having enabled "Developer options" and "USB debugging", I can access the device via adb.
However, after "adb reboot-bootloader", issuing the command "fastboot devices" only outputs:
Code:
no permissions fastboot
The screen reads:
FASTBOOT&RESCUE MODE [...] PHONE Locked
"lsusb" reports the device as:
Code:
Bus 002 Device 015: ID 18d1:d00d Google Inc.
Probably that explains why an additional "adb oem unlock <code>" just outputs:
Code:
< waiting for device >
Is there anybody who has an idea where I may have taken the wrong turn?
Thanks!
Needs "sudo" on host
yeolesourpuss said:
Hi all,
However, after "adb reboot-bootloader", issuing the command "fastboot devices" only outputs:
Code:
no permissions fastboot
Click to expand...
Click to collapse
Apparently, fastboot needs to be run as root (sudo) on the (Linux) host to work.
Alternatively and better, udev should be configured to allow access (source: askubuntu).
I'm trying to do an OTA update on my rooted Pixel 5 via TWRP - on Linux. My steps are:
* adb reboot bootloader (see below)
* fastboot boot twrp-3.6.2_11-0-redfin.img
* Advanced / ADB Sideload
* adb sideload redfin_2209_ota-tp1a.220905.004-c1e785e0.zip
I then get
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
(I cannot get the TWRP install to "stick" no matter what type of install I perform. I end up with something that says "No command" and doesn't respond to the volume keys.)
HELP! And yes, I've searched and tried, tried and searched...
Enable the USB debugging option, which is found under settings- Developer options and then click to enable the USB Debugging option and reboot phone.
Make sure your phone is connected with USB-cable that came with phone with PC.
Run ADB commands
Code:
adb devices
adb sideload
adb devices
What is the output of these commands?
Well, what a disaster that was! The sideload actually started to work so I stupidly cancelled it and now I have to do a fresh install.
Oh, what joy! NOT
I have no idea why is worked this time and not in that past. I'll try again when the November update is available.