Hi,
I am having TWRP recovery, version - 3.0.2-0 (multirom)
Android Version - 5.1.1
OS - Cyanogen 12.1 - YOG4PAS1N0
1.
When I connect my phone via usb and try to run
Code:
adb devices
, I get -
Code:
List of devices attached
624225fe unauthorized
And after that when I try any command, I get error -
Code:
adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
No confirmation is being asked in my phone at this time.
When my device is on (not in recovery) and then when I connect it via usb then everything works fine (drivers already installed in my PC, android debugging enabled in my phone).
When I am in recovery then only it is throwing this error.
Also in the TWRP recovery there is an option of 'Terminal' in 'Advanced' and there I am able to run each command of adb and others.
How TWRP is not able to identify that permission has been granted already for adb.
Is it a TWRP version issue?
2.
when I am trying
Code:
adb pull /data/data/somefile
when my phone is on (not in recovery), its saying
Code:
error: device not found
.
Did not get this as I have already used this command many times before also.
Thanks.
Related
I'm trying to get 5.0.1 on my watch using the OTA zip file. I've enabled ADB debugging in developer settings, rebooted to the bootloader, gone into recovery mode, selected "apply update from ADB" and got to where it tells me to send the package using "adb sideload <filename>" At this point, I try
Code:
adb sideload 1eac9298ba2d5ae80ba4663518a9882791d23344.signed-platina-LWX48P-from-KNX01Q.1eac9298.zip
but after loading the file, I get "error: device not found"
I'm using an Acer PC with 64-bit Windows 8.1, and before rebooting, Device Manager shows a device under "ACER Device" named "ACER Composite ADB Interface" When I am in the bootloader, another device under "ACER Device" named "ACER Fastboot Interface" is shown. After going into recovery mode, nothing is shown.
Edit: So after more searching, I accidentally ended up on the G Watch R forum, where I found instructions that say you need to unlock and flash the 5.0.1 recovery first. Looks like I'm waiting for someone to post that now.
Bug in the current recovery disables adb in there.
So to work around, you need to root, flash the file to the device, use root privaleges to copy file to secure portion, and your golden. Luckily I already made a script that does that for you!
http://forum.xda-developers.com/g-watch/general/script-roots-updates-watch-to-5-0-1-t2970665
Hi all, trying to install CM on Nextbit Robin and I'm having trouble getting the TWRP recovery img flashed. I have working Fastboot & ADB tools installed. Robin driver is installed on PC. Device IS responding to Fastboot and ADB commands. Have unlocked Bootloader and in Fastboot mode now trying to flash recovery (TWRP) img. Have latest TWRP file etc but CMD screen on PC returns a "cannot load file" message. TWRP file located in same directory as Fastboot etc. (I'm working from Windows 10 environment.) Debugging enabled etc. on device. I've flashed CM many times on other Android devices - haven't encountered this issue before. Only issue I've noticed is that the command ADB Devices returns "List of devices" but nothing is listed - HOWEVER device IS responding to ADB commands and Fastboot commands. Thanks in advance for any help you can provide!
I have the exact same problem,
I'm trying to root a pixel (sailfish). I'm able to find the device in adb, but when I go into bootloader, the device isn't there. I'm mostly trying things on my Mac, which I used to successfully root a Nexus 7, but I also had the same issue on a Raspberry Pi. What's more is that I have a Verizon Pixel, which is detected in bootloader (but I can't root it since it's Verizon), and the problematic Pixel in bootloader isn't even registering as a connected USB device when I use the command, "system_profiler SPUSBDataType". Anyone have any advice?
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
jwoegerbauer said:
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
I’ve tried that. It doesn’t show anything.
I have spent months trying to figure out how to get TWRP flashed on my Pixel Phones (I have 2 of them). I have searched & read many links on this forum and can't find any firm details/directions on how to get TWRP on a pixel. From https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ it appears I should of installed TWRP on the factory image first, but I went to Lineage a couple years ago on Android 9 & this was not an option back then.
Both phones have the two latest version of Lineage OS, Both Devices are UNLOCKED, Both have Developer Options Enabled, and on my Windows PC I have the latest version of SDK tools & drivers installed.
Plugging into the PC is done with a a tested/good USB cable plugged into a USB 2 Port. Here is what I am seeing with LinageOS running:
adb devices shows List of Devices Attached
FA77LO302202 device
After executing - adb reboot bootloader
adb devices -> shows an empty list, hence doing a -> fastboot devices shows no devices.
Going to Recovery Mode in Bootloader list of devices shows:
FA76F0303478 unauthorized
In Recovery Mode -> Advanced -> Enable ADB list of devices shows:
FA76F0303478 recovery
I can Apply Update in Recovery Mode via Sideload, but that does not help me get TWRP flashed.
With no devices showing in the main bootloader via adb I can't get the phone into autoboot mode. Per the link at android.gadgethacks.com in order to put the Factory Image back on the phone, https://developers.google.com/android/images, I need to get the phone into autoboot mode.
Anyone have any ideas????
Come-on guys & gals. I'm sure someone can help me at XDA get my devices to fastboot.
Hi,
I am new in this topic and not a great geek ans please excuse mi for my aprroximative english ! but i am trying to convert an old cube tablet to a domotic tablet. So i have to flash the old rom to a newer like lineageos for example.
So the tablet is an U30GT C4H with android 4.2.2 and the original rom.
I connect the device to my Mac Os and with adb tools (from plateform tools find here) and terminal i wrote adb devices (tablet on) i see the device. OK
When i command fastboot devices, nothing, no line
When i command adb reboot-bootloader, the tablet take off and the screen keep black. With the terminal fastboot devices, no response, with adb devices command > List of devices attached but no more, no device.
With this tablet it is possible to start in recovery mode with power + audio down but with this option i have the android logo and no command. If i take power on no change.
If with adb command and tablet on, i write adb reboot recovery, the tablet restart and the screen see logo android and no command.
I know this kind of topic do not interese a lot of people but i would like use this cube for my house to command domotic (music, heaters etc..). More, i think it's a shame not to recycle this type of device for the planet !!!
Thanx
Fastboot only works if in your tablet's Android's Settings -> Developer options the option OEM unlock got enabled and tablet got restarted afterwards.
i don't see any option OEM in the menu developer
I found that the solution is use slideload protocol. I reseted the tablet and now i get recovery mode. Then i can connect the tablet to my Mac and use terminal with slideload lines. OK
But each time the process failed with rom i found on the net...
Is there an universal rom !!!
Any idea ?
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
jwoegerbauer said:
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
Click to expand...
Click to collapse
maybe the issue is the rom i doawnloaded ?
it is kasty-cube_u30gt_h-411-111-rooted4_4gb.zip
or
kasty-cube_u30gtc4-441-20131212-rooted4.zip
both failed.
Perhaps i have to unlock the bootloader as you said but i don't know
I'm pretty sure the 2 mentioned ROMs are a Custom ROM. Hence you can't use adb sideload method to flash them. To install a Custom ROM it's required that a Custom Recovery already got installed on device's Android.
I don't find any way to instal a recovery. I had arctools.zip but the app failed to acess to the SD disk or internal storage...
I just got a new F(x)tec Pro-1X and I want to root it. I'm following the instructions to use Magisk from the F(x)tec team which involves 1) installing Magisk, 2) connecting adb and authorizing, 3) adb pushing the Pro-1X boot.img, 4) Running Magisk and patching the boot.img, and 5) downloading the patched .img.
Then I run "adb reboot bootloader" which leads me to a screen where I can choose Recovery mode and then I get to an Android screen that says "No command". I believe it's here that I'm supposed to run "fastboot flash boot magisk_patched-25200_HsxJg.img"; however, when I run "adb devices", I get unauthorized, and trying to run fastboot anyway fails:
$ adb devices
List of devices attached
8ce396c8 unauthorized
$ fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
I found elsewhere that from this screen, I can hold the power button and press the volume up key and then release both and I see the Android recovery screen. Then I scroll down to Enter fastboot and press power to enter that and I see fastbootd, but I get the same "waiting for any device" output if I try the fastboot flash command here.
If I go back to recovery mode, and instead go to Apply update from ADB, I then see the following from adb devices, but I still can't run fastboot flash:
$ adb devices
List of devices attached
8ce396c8 sideload
I'm running the latest Android Studio and platform-tools on a Lenovo X270 running Fedora 37 and Linux kernel 6.0.17. I'm connecting using a USB-2 port without a hub and tried multiple USBC cords.
A commenter on the F(x)tec forums said that he could never get his Lenovo X250 to work and he had to buy a Raspberry Pi 3 model B.
Are there any alternatives or diagnostics I can run to help solve this "unauthorized" error?
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
ze7zez said:
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
Click to expand...
Click to collapse
Yes. That was required for steps 2-4 for pushing and pulling the image. When I did that, I had to authorize my laptop on my phone. There's no such dialog during recovery mode. Is there some way to pre-authorize recovery mode with my laptop, or otherwise disable this authorization?
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
ze7zez said:
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
Click to expand...
Click to collapse
Thanks, but none of that worked. My problem is authorizing during recovery mode, not during normal operations. It seems what I really need is to either modify /data/misc/adb/adb_keys on the device, or run adb disable-verity, or set ro.adb.secure=0, but I don't have permissions to do any of those.
It's interesting that another F(x)tec user says this works with a Raspberry Pi, and also says it does not work with his Lenovo X250 running Linux, which is similar to my laptop. This suggests there's some sort of limitation or additional security related to the Linux kernel 6.0.17 and/or Fedora, but I can't find what that is or how to diagnose it. I don't have SELinux running on my laptop.
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
MoHuToP said:
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
Click to expand...
Click to collapse
Doesn't work:
$ adb kill-server
$ sudo -i
# adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
# adb devices
List of devices attached
8ce396c8 device
# adb reboot bootloader
... Wait for recovery mode "no command" screen ...
# adb devices
List of devices attached
8ce396c8 unauthorized
# fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
For reference, attached are pictures of all the places where I try the commands and they fail.
I bought a Raspberry Pi 3 B and microSD, installed Raspbian, installed adb and fastboot, connected to phone (normal boot), authorized the Pi, ran adb reboot bootloader, entered recovery mode, phone goes to "No command" screen, but then I get a popup on my Raspberry Pi desktop that says:
Unable to open MTP device "001,013"
Clicked OK and ran adb devices, and I'm back to the "unauthorized" status and adb and fastboot don't work. Tried this in the Raspberry Pi as both a normal user and root (with adb kill-server in between).
Tried with another USB C cable and got a similar error, although it ended with "001,016".
Any ideas?
Resolved by running fastboot on the START screen! (And worked through my X270)