adb access recovery - Galaxy Note 3 Q&A, Help & Troubleshooting

Has Samsung removed the ability to "adb shell" in recovery mode?
In recovery the only way the device is recognized is by sideload, and I can't access shell through that.
I could enter shell through recovery just fine with my SIII.
BTW...both stock 3e recoveries.

Related

[Q]Help: How to exit recovery mode?

Whe I try to install CM7, I installed recovery successful by change boot mode to "idme bootmode 0x5001", maybe I made some mastake when I copy log file, I can't update to CM7, now it's always come into recovery mode when I restart KF, I don't know how to exit recovery mode.
How can I change to normal mode? Thank you!
Is there any method to exit recovery mode?
yuhao51000 said:
Is there any method to exit recovery mode?
Click to expand...
Click to collapse
try:
fastboot oem idme bootmode 4000
fastboot reboot
That command will put it back to OS boot mode, not recovery mode. That worked for me when I flashed TWRP today.
If your stuck in clockwork, adb should work and you can type
adb shell
su
idme bootmode 4000
exit
exit
adb reboot
fastboot commands won't work while your in recovery, only while your in fastboot.
It works, now I installed CM7 successful, great thanks!
could this work on another device like the tf700?

[Q] adb shell from FireFireFire

Is it possible to get adb or any shell access from FireFireFire or TWRP?
adb and shell access
Yes. If you stuck in FFF mode (yellow triangle) or run TWRP you can to connect
device with USB cable and get adb access. "adb shell" will give you shell. to get
root access use ZergRush.
From FFF, you will only get fastboot access. If you boot into TWRP from FFF, you can get the adb shell.
lmntone said:
From FFF, you will only get fastboot access. If you boot into TWRP from FFF, you can get the adb shell.
Click to expand...
Click to collapse
Thanks. I indeed can access adb from TWRP.

[Solved] [CWM] Can't adb shell in CWM

Hi all.
I have this S4, screen broken, no digitizer, USB debug not enabled and can't mount with MTP for unknown reasons. The owner asked me to retrieve some saved stuff.
Ok, I installed CWM recovery via Heimdall and plugged in the usb, but can't connect to it with adb:
Code:
$ adb devices
List of devices attached
(none)
I believe CWM is running just fine, 'cause if I push vol- and then power it goes in sideload mode, and then ADB can see it:
Code:
$ adb devices
List of devices attached
1c1a1234 sideload
...but obviously, with the device in sideload mode, i can't adb pull from it.
Any suggestions?
Try Philz recovery for adb. I think I had issues in the past with cmw and twrp when using adb.
Lennyz1988 said:
Try Philz recovery for adb. I think I had issues in the past with cmw and twrp when using adb.
Click to expand...
Click to collapse
.....aaaand this one made the trick!
Misson accomplished and reputation honored! Thanks!

How to flash fastboot using adb shell ?

I did something stupid.
While attempting to install twrp on my zenfone 5 ( https://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263 ), I did
fastboot flash fastboot TWRP-2870_Zenfone5.img
to flash it. And ended up ruining my fastboot. How do I get fastboot back ?
I have adb shell with su. Can someone tell me how I can flash my driodboot.img using adb shell ?
Thanks.
sideload stock rom via stock recovery

adb unauthorized device and adb_keys not saved

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?

Categories

Resources