At what point in the boot process does ADB detect the device? Phone is soft-bricked and I'm trying to get it into recovery mode through an adb shell.
treygrizzard26 said:
At what point in the boot process does ADB detect the device? Phone is soft-bricked and I'm trying to get it into recovery mode through an adb shell.
Click to expand...
Click to collapse
You most likely won't be able to get recovery mode if you can't access it with the button combo. Best bet would be to flash a kernel with Heimdall/Odin.
Go check out my adb portable in the developers section. It will wait until it sees your phone and boot it into recovery/download mode.
Or you can issue this command to do the same thing:
Code:
adb wait-for-device reboot recovery
Sent from my SGH-I777 using xda premium
Related
When I first got the phone, I had download mode and the stock recovery. Well, I rooted it, and attempted to flash CM7. After that, I got stuck in a bootloop, so I flashed with Odin3 One-Click. After Odin3 One-Click, I no longer have download mode or recovery. When I use the 3-button combo for the recovery, it just boots into Android. When I do the Volume Button up and down, and put the USB cable in, it just goes to the charging screen. Not sure what to do, and am a bit frustrated.
Jig to get back in dl mode and flash either GB bootloaders or just GB. You probably flashed 2.1.
Yes, it did. And that's what I had before. So, is buying a jig the only option now?
You can make one, but to my knowledge ya.
Okay. I'll see what I can do when I get home. I'll check back with any progress, thanks for your help!
Wait Second thought. If you can root it (one of the 1 click methods) you can use terminal Emulator.
su (accept SU)
reboot download -or- reboot recovery
you can just make your own jig. i was stuck the same place you where with the bootloop earlier this week. i made a jig at work in 5 mins with $1 worth of parts.
my problem was that i had a rogers captivate and didnt know that it had to be flashed differently to get cwm to work
I have a captivate in my hand which is the same as urs 2.1 update 1 and it does not go to DL or Recovery with the buttons so i have a home made jig for the DL.
Ill say is u cannot make a jig or don't wanna nuy one just root ur phone with one click and DL terminal emu and command it reboot download and u are in download mode.
adb reboot download
no su needed. no root needed.
use the easy adb setup in my sig, then run adb, and type 'adb reboot download' or 'adb reboot recovery' ( no quotes ' ' )
TRusselo said:
adb reboot download
no su needed. no root needed.
use the easy adb setup in my sig, then run adb, and type 'adb reboot download' or 'adb reboot recovery' ( no quotes ' ' )
Click to expand...
Click to collapse
Easier to root Imo. Smaller dl. But you are right.
Sent from my ICS powered Captivate using Tapatalk
adb reboot download doesn't work I thought... Or am I wrong?
b-eock said:
adb reboot download doesn't work I thought... Or am I wrong?
Click to expand...
Click to collapse
Should. He is on 2.1. Unless google effed something, it should work. (it did back in the day)
Sent from my ICS powered Captivate using Tapatalk
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
TAGTRAUM said:
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
Click to expand...
Click to collapse
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Circaflex said:
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Click to expand...
Click to collapse
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
TAGTRAUM said:
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
Click to expand...
Click to collapse
Nope.. If adb doesn't work and volume buttons are broken, you're stuck. Get the buttons repaired.
rootSU said:
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Click to expand...
Click to collapse
No luck with running this commands in boot process
TAGTRAUM said:
No luck with running this commands in boot process
Click to expand...
Click to collapse
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
Adb should work from part way through the boot process and any mode. in custom recovery.
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
TAGTRAUM said:
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Tech said:
Try this
Click to expand...
Click to collapse
Will try, but decide to repair my Vol- button myself, i have no mind what can be broken in this part, watching video of N6 dissassembly, its pretty simple part indeed Walking w/o Vol- for a month, and this situation is frustrating me and other situations can happen, in certain cases i still need Vol- :cyclops:
Im trying to flash back to stock rom but the device is not responding, i already have try on mfastboot and on fastboot but it just say "waiting for device" when i try some comand, i have motorola drivers, i've tryed a program called PDAnet too, i have usb debug on, can someone help-me?
are you using Windows 7/8/10 ?
did you boot into bootloader mode?
(adb debug mode is for adb and bootloader mode is for fastboot)
interaction is: adb reboot bootloader (when device is on and adb debug is on)
zitronenmelissa said:
are you using Windows 7/8/10 ?
did you boot into bootloader mode?
(adb debug mode is for adb and bootloader mode is for fastboot)
interaction is: adb reboot bootloader (when device is on and adb debug is on)
Click to expand...
Click to collapse
i have tryed all, but no response, i give it up and install other custom rom but thanks for trying help
Hi, I would know if while the phone is in UI recovery mode it is possible to run adb commands.
At the moment I get the message: ADB Android Device Unauthorized.
I don't have unlocked bootloader or root privilegies.
Thanks
ultrasound1991 said:
Hi, I would know if while the phone is in UI recovery mode it is possible to run adb commands.
At the moment I get the message: ADB Android Device Unauthorized.
I don't have unlocked bootloader or root privilegies.
Thanks
Click to expand...
Click to collapse
Not in stock recovery, by normal means.
Okay. So I was playing around in the stock recovery on my Tab A8 SM-X200 and stumbled upon something I have never seen before on any Samsung device. Usually there are no ADB commands that work in the stock recovery except the adb sideload command that you use to flash an update.zip file. Well if you select the option to update using ADB you can enter into another recovery mode by using adb reboot-rescue. this command only works while you are in the stock recovery and only while you are using the update using ADB option. It will reboot into a different recovery mode called rescue mode. You have no options and cant seem to do anything in this mode but ADB is fully active and the screen says "Waiting for rescue commands" I havent figured out any of the commands nor could I do anything but reboot from this mode but i tried it on the Tab S3 and Tab S6 as well as the A7 from the previous year and this seems to be the only device that has this rescue mode. Just wanted to share my find and hopefully someone will figure out how to use it.