Anyone knows the command in adb to boot the phone into download mode? I broke the volume flex cable and it's softbricked now
Sent from my MT11i using XDA
I'm pretty sure its "reboot download" just like through a terminal emulator from the phone (root required).
#su
#reboot download
adb shell
$ su
#reboot download
There is no need for su if you have a #
Montoyatok said:
Anyone knows the command in adb to boot the phone into download mode? I broke the volume flex cable and it's softbricked now
Sent from my MT11i using XDA
Click to expand...
Click to collapse
from computer,
adb reboot download
adb reboot recovery
works 100%, no TerminalE required.
Thanks guys
Sent from my MT11i using XDA
bsuhas said:
from computer,
adb reboot download
adb reboot recovery
works 100%, no TerminalE required.
Click to expand...
Click to collapse
:victory: OMG!!! Bless You!!! :victory:
I knew there had to be a better way then pulling out the rest of my thinning hair!!!
Samsung Galaxy S II (SCH-R760) US Cellular
bsuhas said:
from computer,
adb reboot download
adb reboot recovery
works 100%, no TerminalE required.
Click to expand...
Click to collapse
Sorry but it Reboot in Normal Mode
chlebta said:
Sorry but it Reboot in Normal Mode
Click to expand...
Click to collapse
I think I'm also experiencing the same thing, and could really use someone's help.
I have a Sprint Galaxy S3 and have rooted it. My display is broken, so would try to use the how-to to create a headless backup.
When I try to reboot it into download mode, it seems to never come back. I believe it's waiting for a keypress on the phone, or scrolling through a menu to select the right option so it can continue to boot. Can anyone with a working display confirm this for me?
I rooted it a while ago, so don't remember what's on the screen.
When I try to reboot in recovery mode, I'm also unable to select the proper menu option to continue to boot into recovery mode.
Is it always necessary to boot into download mode first, or only if you want to download something? In other words, if I only want to reboot into recovery, can I skip the download mode boot first?
Ideas greatly appreciated!
Thanks,
Alex
You don't need to enter download mode first. From command prompt enter adb reboot recovery and your good to go
thanks this saved a lot of hours
bsuhas said:
from computer,
adb reboot download
adb reboot recovery
works 100%, no TerminalE required.
Click to expand...
Click to collapse
can you help me too ?
even i broke my volume flex nd am hard bricked
so when i try to turn it on it just stays on google logo my device is nexus 6 ?
am not so familiar with adb so pls can you help me ?
Hi
My android screen lost it's touch and it's stuck waiting for "Enter"
So I'm trying to use ADB to get there
My question is how to enter the "Enter" command ?
EDIT:
TNX, no need to reply, the problem is solved
ggossamer said:
I think I'm also experiencing the same thing, and could really use someone's help.
I have a Sprint Galaxy S3 and have rooted it. My display is broken, so would try to use the how-to to create a headless backup.
When I try to reboot it into download mode, it seems to never come back. I believe it's waiting for a keypress on the phone, or scrolling through a menu to select the right option so it can continue to boot. Can anyone with a working display confirm this for me?
I rooted it a while ago, so don't remember what's on the screen.
When I try to reboot in recovery mode, I'm also unable to select the proper menu option to continue to boot into recovery mode.
Is it always necessary to boot into download mode first, or only if you want to download something? In other words, if I only want to reboot into recovery, can I skip the download mode boot first?
Ideas greatly appreciated!
Thanks,
Alex
Click to expand...
Click to collapse
I also installed custom rom AOSPrime. and then for going back to stock, i needed to enter download mode. None of the commands worked. i made a backup of everything in twrp except system and data. so i restored that back, and then voila, the LG logo was back but didnt boot(obvious). Now i could easily go by the vol up and then usb connection process to goto download mode.
the default stock settings enable the download mode to work.
if anyone needs the backup, mine may be of other region, but it could surely bring back the lg logo and stuff.
quote me and i will post the link
ggossamer : before download mode you need to confirm download mode with volume+ or you can cancel the thing with vol- , IIRC .
For your other questions, I think, recovery with a broken screen might be difficult, maybe use ADB
Samsung Grand prime download mode
I have a Samsung grand prime and I can not reach download mode to use the Odin 3.07 to flash the md5, even when I used adb services command "adb reboot download" it rebooted in normal mode. Any help please?
Thanks
Related
What buttons do I need to press to get this phone into recovery mode. Absolutely nothing comes up when I try to google it or search for this phone it's driving me nuts. I've got it into download mode no problem but recovery I can't find a process on.
I know there are multiple threads that tell you how, but after you flash CMW and are turning your phone on you want to hold down the power button, volume up, and the home button. When the Samsung logo comes up, let go of the power button but hold down the others. That will take you into recovery.
adb reboot recovery
yyhd said:
adb reboot recovery
Click to expand...
Click to collapse
Is this in a terminal on a computer or in terminal emulator? On the phone I've been using:
su
reboot recovery
binglejellsx2 said:
Is this in a terminal on a computer or in terminal emulator? On the phone I've been using:
su
reboot recovery
Click to expand...
Click to collapse
That's using adb on a computer attached to your phone. adb is part of the Android SDK.
Thanks. I'm not big on the command-line stuff. I just copy/paste the lines when instructed to do so.
If you're rooted, you can also use an app like Quick Boot.
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
callison.168 said:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
Click to expand...
Click to collapse
It seems your boot.img file either corrupted or missing.
Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.
Did you check http://forum.xda-developers.com/showthread.php?t=895545 ?
Odin should be your last resort, if nothing really works for you.
If you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 .
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
Download your rom of choice (stock, custom)
Flash Cwm via fastboot if you haven't already
Boot into recovery.
Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)
Use cwm to flash this zip.
Sent from my Nexus S using xda premium
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9866675
http://forum.xda-developers.com/showthread.php?t=884093
These threads should be a complete solution to your issue.
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and it just says < waiting for device >.
Here's a pic of the screen that I'm on with my phone when i enter the command.
http://imgur.com/Pey3W
If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.
How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
callison.168 said:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
Click to expand...
Click to collapse
So you already tried "fastboot devices" while in fastboot mode?
Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.
EDIT: Go here to download the correct OTA http://forum.xda-developers.com/showthread.php?t=1056062
Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.
If there is a wipe option in the stock recovery then do that first.
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.
callison.168 said:
Also, I can't get the phone to boot at all, like I can't turn on the phone so I can't access the sdcard in the traditional way.
Click to expand...
Click to collapse
If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.
Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).
In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).
irishrally said:
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
Click to expand...
Click to collapse
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
krohnjw said:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
Click to expand...
Click to collapse
He said he can access stock recovery and has connected with adb, unless I read wrong.
irishrally said:
He said he can access stock recovery and has connected with adb, unless I read wrong.
Click to expand...
Click to collapse
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.
If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
Go to the stock recovery like you have done before and type the adb command I wrote above.
Thanks is all I can say. Okay so when I type in the command, this is what I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.
by the way...if we can get this working, I'll post a picture of me holding the fixed phone!
My home button has stopped working and was wondering how I would boot into odin mode (download mode) to flash twrp etc.
i am no expert but you can use adb to get into download mode !!
http://forum.xda-developers.com/showthread.php?t=1695552
likhon02 said:
i am no expert but you can use adb to get into download mode !!
http://forum.xda-developers.com/showthread.php?t=1695552
Click to expand...
Click to collapse
Thanks, but it didnt work. I think i need Root to do this no? But thank you for trying and looking ouut.
Cant get my phone to connect to my computer now.
to use adb you don't need root just read the entire thread carefully..if you are still having issues knock me facebook.com/abokashm.
likhon02 said:
to use adb you don't need root just read the entire thread carefully..if you are still having issues knock me facebook.com/abokashm.
Click to expand...
Click to collapse
Hello, I also cannot use adb to boot to download mode. To be honest, I am not quite sure what is download mode. Is it similar to fastboot mode? My S6 cannot boot, it just says that there is no home app available, and than just error after error. Cannot use it at all. So I tried to boot to download mode, no success with buttons combination (home+volume down+power). so I installed adb and fastboot. ADB doesnt see my phone, and fastboot does, but I do not know what is command for it. I would like to use Odin to flash new rom, maybe that will fix the phone, but cannot use it if I cannot go to download mode. So any help is welcome.
repair home button
http://www.etradesupply.com/blog/how-to-tear-down-samsung-galaxy-s6-in-10-steps/
Hello Everyone,
I hope you are doing good, Cant run my S7 G930T mobile.
I have upgraded OS via Odin, it passed but phone is not getting work.
Sometimes it doesn't open recovery boot and gets stuck at Recovery Booting.....
Sometimes it restart from the installing applications screen.
If you have any files for binary 11 (B) or anything i need to do before flashing OS via Odin.
Please help me
I'd be very thankful to you.
Thanks!
[email protected]
sabeel43 said:
Hello Everyone,
I hope you are doing good, Cant run my S7 G930T mobile.
I have upgraded OS via Odin, it passed but phone is not getting work.
Sometimes it doesn't open recovery boot and gets stuck at Recovery Booting.....
Sometimes it restart from the installing applications screen.
If you have any files for binary 11 (B) or anything i need to do before flashing OS via Odin.
Please help me
I'd be very thankful to you.
Thanks!
[email protected]
Click to expand...
Click to collapse
Can you be more specific about your booting issues?
Is the device boot looping? How far through the booting process do you get before failure? and what happens after failure?
Can you get your phone into recovery mode or download mode?
ReboundGuy said:
Can you be more specific about your booting issues?
Is the device boot looping? How far through the booting process do you get before failure? and what happens after failure?
Can you get your phone into recovery mode or download mode?
Click to expand...
Click to collapse
Sometimes it gets ON normally and after some time it reboots itself and then it keeps doing it again and again, and sometimes it gets on and goes straight to the recovery mode, and yes i can get my phone into download mode too.
If you have precious data you want to keep, then you should create a back up of your phone, if you haven't already done so.
If you're unconcerned about data or have created a backup, then you could factory restore from recovery mode.
Alternatively, if you haven't got the latest version of Odin, then you could try downloading the latest Odin software and attempt another flash.
Another thing you could try, is to sideload the update via adb. You will of course need the latest adb software which is easy to find. You can follow this xda guide here (https://www.xda-developers.com/install-adb-windows-macos-linux/), or if you prefer it you could download Android Studio from here (https://developer.android.com/studio).
To sideload the update you will have to:
1. Boot phone into recovery mode. Hold the volume up, home, and power buttons, and then let go of the power button when it power on.2. When in recovery mode, select the option, "Apply update from ADB."3. With your phone plugged into the computer, open the cmd/terminal and type "adb devices". The cmd should start up adb and display something like:List of devices attached[device id] sideload4. Navigate to the folder that contains the update file. It needs to be a .zip file.5. Type in the command, "adb sideload [file name]".
To make things easy you can set up adb so you can run its commands from any directory, the steps for this are covered at the end of the xda guide I have linked.
ReboundGuy said:
If you have precious data you want to keep, then you should create a back up of your phone, if you haven't already done so.
If you're unconcerned about data or have created a backup, then you could factory restore from recovery mode.
Alternatively, if you haven't got the latest version of Odin, then you could try downloading the latest Odin software and attempt another flash.
Another thing you could try, is to sideload the update via adb. You will of course need the latest adb software which is easy to find. You can follow this xda guide here (https://www.xda-developers.com/install-adb-windows-macos-linux/), or if you prefer it you could download Android Studio from here (https://developer.android.com/studio).
To sideload the update you will have to:
1. Boot phone into recovery mode. Hold the volume up, home, and power buttons, and then let go of the power button when it power on.2. When in recovery mode, select the option, "Apply update from ADB."3. With your phone plugged into the computer, open the cmd/terminal and type "adb devices". The cmd should start up adb and display something like:List of devices attached[device id] sideload4. Navigate to the folder that contains the update file. It needs to be a .zip file.5. Type in the command, "adb sideload [file name]".
To make things easy you can set up adb so you can run its commands from any directory, the steps for this are covered at the end of the xda guide I have linked.
Click to expand...
Click to collapse
I tried to update from ADB but it said, unauthorized access!
and I also think it is a hardware issue
Can you start in safe mode?
ReboundGuy said:
Can you start in safe mode?
Click to expand...
Click to collapse
Yes if it boots normally and then i can go safe mode too.
Just so you know, I'm running out of ideas. Can you try the other suggestion that I mentioned above?
The one where I suggested flashing through Odin again?
I'm kind of assuming that USB Debugging and OEM Unlock were turned on as well.
ReboundGuy said:
Just so you know, I'm running out of ideas. Can you try the other suggestion that I mentioned above?
The one where I suggested flashing through Odin again?
I'm kind of assuming that USB Debugging and OEM Unlock were turned on as well.
Click to expand...
Click to collapse
now Its not turning on , not even on charging
Ikes! Are you able to try and downgrade to your original stock firmware? Seems like the issues began with trying to update.
where can I download original stock firmware from the internet? Can you provide me the link kindly? Last time I used Frija (desktop app) to download firmware.
Pretty much everyone on xda (including me) uses this website for firmware: https://www.sammobile.com
You have to create a free account but it's worth it for all the firmware they have available.
I believe you already know this, but I'm just going to cover the bases anyway, make sure to download firmware for your specific model G930T.
I try Using Magisk and patched Boot Img,
Now I dont access recovery my phone reboot again and again,
My phone now Empity Battery Now,
I cant connect to recovery
I try Charge And Hold Power and Volume up but is not work
I try Charge And Hold Power and Volume Down but is not work
I try Charge Hold Power , Volume up and down but is not work
Sorry my bad english
Please Help me
Re-flash Stock ROM.
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
Thanks i try a flash room but i cant connect to recovery
Flashing Stock ROM doesn't require a Custom Recovery nor default Stock Recovery: it's achieved by means of ADB
Code:
adb devices
adb reboot sideload
adb sideload <PATH-ON-PC-TO-STOCK_ROM.ZIP>
This device reboot in 5 second again and again, turn on it self stuck in logo and reboot again
I dont sent this command
error : No devices / emulator foundin adb
please help me please
flick233 said:
This device reboot in 5 second again and again, turn on it self stuck in logo and reboot again
I dont sent this command
error : No devices / emulator foundin adb
please help me please
Click to expand...
Click to collapse
Was ur problem solved? If not this is my watsapp no +254705980548 Remote services available.