Hi, this is my first post here.
I have a rooted Samsung S4 with a broken screen, that I can put in recovery mode and send commands with adb.
I would like to activate USB Debugging and I found on the forum the adb commands to do it.
I have a problem: when I restart the phone to exit the recovery mode and try "adb devices" I always find it "unauthorized".
I noticed that when I run in recovery mode "adb push adbkey.pub /data/misc/adb/adb_keys", the command seems to work. In fact, if I try immediately with "cat /data/misc/adb/ adb_keys" I see the content correctly.
But if I restart the phone still in recovery mode and I try again immediately "cat /data/misc/adb/adb_keys", the file is non-existent.
I guess this is not correct.
How can I try to solve?
Related
When i tried to Boot from recovery mode i got Error message with no command.. none of those option in recovery mode working. My phone is UN rooted running on official 4.3 Jellybean. Is this only i m getting? or because my phone is unrooted its locked?
Some Assist would be nice thank You
try using ADB commands:-
connect your phone using usb cable (with usb debugging enabled in developer options)
open command prompt (windows)
if you have ADB as environmental path then just type "adb reboot recovery"
else you need to navigate to the adb.exe and then type the upper command.
it worked for me
can u link where can i download ADB tool
i've attached the latest ADB version 1.0.31 (don't use older versions as they wont work on our device)
Hi folks!
I wanted to install Cyanogenmod as described in Cyanogenmod Wiki.
So I downloaded ioroot, rootet my phone via adb and used AutoRec to install TWRP (version 2.7.0.0).
Then I rebooted into recovery mode, wiped EVERYTHING and wanted to sideload the CM image via adb.
So in TWRP I selected Advanced/ADB Sideload and swipe to start sideload but all that happens is the notification "Starting ADB sideload feature...".
Consequently the phone is not recognized by adb on my PC.
What can I do to make the sideload feature work?
BTW: TWRP tells me that my devices doesnt appear to be rooted when I want to leave TWRP (reboot). Moreover when i want to enter TWRP again (by pressing POWER + VOLUE DOWN) I first get a screen that asks me if want to do a factory hard reset! Only if I agree (by pressing the power key) I get into TWRP.
Contrary when I enter the Download Mode (VOLUME UP when when connecting the powered off phone to the USB port) I am told that the phone is rooted. Moreover the LG Mobile Support Tool is able to detect the device and tells me that the installed software is up to date.
Thx!!
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Make sure you're in the proper folder in prompt and the device name will be sideload if you do, adb devices.
Sent from my LG-D800 using Tapatalk
meangreenie said:
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Click to expand...
Click to collapse
Thanks but this doesnt help either. Same error message "error: device not found"
boot into twrp, don't start sideload
try adb devices, if you get not find you need to change the usb drivers
when you have it working, type, adb push /sdcard/ rom.zip .. check the syntax on that command, but i think that's right from memory
My s4 display is broken, so, there's nothing that I can do with the phone. When I connect phone via usb, I'm able to browse through folders on my s4, but in adb, on "adb devices" command, none of devices is listed.
Phone is rooted with CM11 ROM installed.
When I connect phone in recovery mode on bootup, and open adb, all commands are working, and device is recognised.
Is there any way to enable usb debugging from recovery mod, so device would be recognised in adb when it boot up normally?
You could try this:
Run an ADB shell in ClockworkMod
Remount /system in readwrite mode.
Add this to /system/build.prop: persist.service.adb.enable=1
Save the file.
Warning: Some people reported that this causes their device to not boot anymore.
hi... i have sme problems...
adc say me that phone is "unauthorized"
can you say exactly tha command that i must use with adb?
Windows 10 Home on host computer, and ADB tools installed.
USB debug mode on and host computer allowed.
USB PTP mode.
LG Unified Driver installed.
I opened command prompt, locate adb platform-tools. Ran the following commands
Code:
adb reboot bootloader.
The phone rebooted to bootloader.
On the bootloader mode on the phone, I typed
Code:
fastboot reboot
The phone rebooted properly
Does it work right?
Currently the phone is not ready to unlock bootloader until there's no problem, especially speaker problem, found.
I tried flashing a recovery program (TWRP) in fastboot mode. The powershell said it was successful, but now the phone cannot get past the bootloader unlocked screen. It started to System twice, and I made sure to remove the security PIN and enable ADB debugging on this computer automatically. However, "fastboot devices" and "abd devices" commands do not return the device ID, but the phone does turn on when I attached the USB cable that's connected to my computer. I think it's trying to restart into recovery mode, but the recovery program (TWRP) did not install correctly. How can I get it to reboot to system again?
CurlyTemple said:
I tried flashing a recovery program (TWRP) in fastboot mode. The powershell said it was successful, but now the phone cannot get past the bootloader unlocked screen. It started to System twice, and I made sure to remove the security PIN and enable ADB debugging on this computer automatically. However, "fastboot devices" and "abd devices" commands do not return the device ID, but the phone does turn on when I attached the USB cable that's connected to my computer. I think it's trying to restart into recovery mode, but the recovery program (TWRP) did not install correctly. How can I get it to reboot to system again?
Click to expand...
Click to collapse
When I try to give a fastboot command, the powershell just returns
<waiting for device>
and then nothing happens.