When is type in command line adb devices it lists my device but as soon as i try a fastboot command it says <waiting for device> for hours and does not work
ACFH said:
adb devices
adb reboot bootloader
Wait for phone reboot then type
fastboot devices
Click to expand...
Click to collapse
When i do the thing you've said i get stuck with a screen with fastboot mode on the top left corner
Right click on task bar at bottom not tap any app click task manager stop adb then open command window shift+right click then type
Fastboot OEM unlock
Put recovery into adb and FASTBOOT folder then rename to TWRP.img type in
Fastboot flash TWRP.img then boot into TWRP
---------- Post added at 12:52 PM ---------- Previous post was at 12:51 PM ----------
Danyaelgaina said:
Right click on task bar at bottom not tap any app click task manager stop adb then open command window shift+right click then type
Fastboot OEM unlock
Put recovery into adb and FASTBOOT folder then rename to TWRP.img type in
Fastboot flash TWRP.img then boot into TWRP
Click to expand...
Click to collapse
Remember to boot into fastboot and enable adb in developer options
ACFH said:
Yeah. Its fastboot screen. Now you can try any fastboot command. After that, "fastboot reboot" will bring you to system.
Edit: be carefull with fastboot command or you will brick your phone
Click to expand...
Click to collapse
When I try any fastboot command when it's on this screen it says <waiting for device> and when on this screen i type adb devices it shows my device but fastboot commands do not work.
It could be about drivers. Try reinstalling adb with this tool: https://forum.xda-developers.com/showthread.php?t=2588979
Now you install adb correctly. But you might still stuck at waiting for device. You need to setup windows for detecting android to do that go to this link : http://www.codeshuffle.in/2016/12/kenzo-fastboot-adb-connection-fix.html?m=1
This is how I fixed mine. Hope it will work for you
Device Manager shows when phone in fastboot mode
[IMG="This is what device manager shows in fastboot mode"
https://mail.google.com/mail/u/0/?u...&attid=0.1&disp=safe&realattid=f_j2o9k1gg0&zw
Related
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
KrisM22 said:
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
Click to expand...
Click to collapse
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
kuisma said:
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
Click to expand...
Click to collapse
Thanks! Please pardon my ignorance... I did:
Code:
adb devices
pause
adb reboot-bootloader
pause
fastboot reboot
After adb reboot-bootloader my phone changed from the recovery screen to the white tmo logo screen and hung.
fastboot reboot still says waiting for device...
EDIT Okay, I think I've figured out that, from power off, volup+power=recovery screen , and voldn+power=fastboot screen(white with tmo logo).
But I can't do anything from that fastboot screen. The computer recognizes it when I USB plug it, but it still says waiting for device.
EDIT: It appears I have a driver for adb, but no driver for fastboot, or just plugging the powered off phone in to usb.
fixed.
<deleted>
Hey guys sooooooo,
This is what happened will try to be as detailed as possible.
Prime started acting up so decided to flash new rom.
Switched from CWM to TWRP some time ago placed new
rom on ext sd booted in TWRP and like second nature wiped
device like I do on my phone.
Here is the problem I then realized i had TWRP 2.1 which does
not read ext sd cards
Now I am stuck not being able to do anything so being the good
XDA'er i spend hours searching and attempted to flash CWM now
I have NOOOOOOO recovery my Prime hangs at boot screen I believe
I can access Fast boot but not familiar with ADB so before I move forward
And F*%^ things up more HELP
pdotc said:
Hey guys sooooooo,
This is what happened will try to be as detailed as possible.
Prime started acting up so decided to flash new rom.
Switched from CWM to TWRP some time ago placed new
rom on ext sd booted in TWRP and like second nature wiped
device like I do on my phone.
Here is the problem I then realized i had TWRP 2.1 which does
not read ext sd cards
Now I am stuck not being able to do anything so being the good
XDA'er i spend hours searching and attempted to flash CWM now
I have NOOOOOOO recovery my Prime hangs at boot screen I believe
I can access Fast boot but not familiar with ADB so before I move forward
And F*%^ things up more HELP
Click to expand...
Click to collapse
If you have your twrp 2.1 on pc, do fastboot install (see the twrp page for details) then adb push a rom to the prime and install it... you should be okay then....
Gage_Hero said:
If you have your twrp 2.1 on pc, do fastboot install (see the twrp page for details) then adb push a rom to the prime and install it... you should be okay then....
Click to expand...
Click to collapse
my device is not showing up in ADB i tried naked drivers anything else I can do?
pdotc said:
my device is not showing up in ADB i tried naked drivers anything else I can do?
Click to expand...
Click to collapse
When you plug the device into the pc, is it recovery or fastboot mode? Not sure it will show up if it is in a bootloop. Also if you are in recovery, you should be running adb from within the folder the exe file is in... basically open the folder, press and hold shift then rightclick and select open command prompt here then type adb devices and see what you get.
Gage_Hero said:
When you plug the device into the pc, is it recovery or fastboot mode? Not sure it will show up if it is in a bootloop. Also if you are in recovery, you should be running adb from within the folder the exe file is in... basically open the folder, press and hold shift then rightclick and select open command prompt here then type adb devices and see what you get.
Click to expand...
Click to collapse
I cannot access recovery, I can access the fastboot menu i hear the windows sound. When I check my devices in Win7 it shows fastboot there but when I ADB it says no device.
pdotc said:
I cannot access recovery, I can access the fastboot menu i hear the windows sound. When I check my devices in Win7 it shows fastboot there but when I ADB it says no device.
Click to expand...
Click to collapse
The adb commands won't work in fastboot... you need to use the fastboot commands.
From: http://www.teamw.in/project/twrp2/93
Put the attached file in your nvflashpack folder where you see the fastboot.exe, this way you don't need to type paths. In the same window press and hold shift, rightclick in the window and select open command prompt here. Make sure the prime is already in fastboot mode.... now, copy the command below and rightclick in the command window and select paste (avoids typing mistakes) press enter and with any luck you should be able to boot to twrp recovery...
You will need adb and fastboot for this method. Download the above file, check the md5, rename to twrp.img and put the file in the same directory as your fastboot binary (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0b05 flash recovery twrp.img
If you use the attached file you don't need the modified bootloader, you will have an older version of twrp but the whole point is to get you running first...
After you do this, boot into recovery, connect the prime to the PC and with the rom in the same folder as adb.exe, open a command window like before. Type adb devices, you should see the prime... then do adb push /the name of your rom.zip/ sdcard/
For the name of the rom, I usually right click the file, go to properties and copy the name.. (no spelling mistakes) again, right click in command window and paste and be sure to put .zip at the end. This should take about 5 minutes to complete. Then in recovery, go to install and you should be able to flash the rom....
Gage_Hero said:
The adb commands won't work in fastboot... you need to use the fastboot commands.
From: http://www.teamw.in/project/twrp2/93
Put the attached file in your nvflashpack folder where you see the fastboot.exe, this way you don't need to type paths. In the same window press and hold shift, rightclick in the window and select open command prompt here. Make sure the prime is already in fastboot mode.... now, copy the command below and rightclick in the command window and select paste (avoids typing mistakes) press enter and with any luck you should be able to boot to twrp recovery...
You will need adb and fastboot for this method. Download the above file, check the md5, rename to twrp.img and put the file in the same directory as your fastboot binary (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0b05 flash recovery twrp.img
If you use the attached file you don't need the modified bootloader, you will have an older version of twrp but the whole point is to get you running first...
After you do this, boot into recovery, connect the prime to the PC and with the rom in the same folder as adb.exe, open a command window like before. Type adb devices, you should see the prime... then do adb push /the name of your rom.zip/ sdcard/
For the name of the rom, I usually right click the file, go to properties and copy the name.. (no spelling mistakes) again, right click in command window and paste and be sure to put .zip at the end. This should take about 5 minutes to complete. Then in recovery, go to install and you should be able to flash the rom....
Click to expand...
Click to collapse
Ok 1st I want to thank you for your help.
sorry to be a noob at this ADB thing can you tell me a step by step on how get to that fastboot cus i get no where when I type it in?
pdotc said:
Ok 1st I want to thank you for your help.
sorry to be a noob at this ADB thing can you tell me a step by step on how get to that fastboot cus i get no where when I type it in?
Click to expand...
Click to collapse
C:\android-sdk\platform-tools> fastboot -i 0x0b05 flash recovery twrp.img
error: cannot load 'twrp.img'
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools> fastboot devices
00000 fastboot
C:\android-sdk\platform-tools>
pdotc said:
C:\android-sdk\platform-tools> fastboot devices
00000 fastboot
C:\android-sdk\platform-tools>
Click to expand...
Click to collapse
You will need adb and fastboot for this method. Download the above file, check the md5, rename to twrp.img and put the file in the same directory as your fastboot binary (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0b05 flash recovery twrp.img
You need to rename the file see the red text above. I would download nvflash from here.... http://androidroot.mobi/t3_nvflash/ the windows zip file.... unzip it and from within the window get your command prompt.... make sure you have the twrp file I attached earlier in the same folder... then copy fastboot -i 0x0b05 flash recovery twrp.img and rightclick and paste into the command filed press enter..... it should install twrp....
now if I have misunderstood and you don't know how to get the prime into fastboot hold volume down and power, when you see the white text in the top left corner, press volume up then volume up to select fastboot of course the prime will be connected to the pc before this...
btw we were all noobs at one point... this is our school....
Gage_Hero said:
You will need adb and fastboot for this method. Download the above file, check the md5, rename to twrp.img and put the file in the same directory as your fastboot binary (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0b05 flash recovery twrp.img
You need to rename the file see the red text above. I would download nvflash from here.... http://androidroot.mobi/t3_nvflash/ the windows zip file.... unzip it and from within the window get your command prompt.... make sure you have the twrp file I attached earlier in the same folder... then copy fastboot -i 0x0b05 flash recovery twrp.img and rightclick and paste into the command filed press enter..... it should install twrp....
now if I have misunderstood and you don't know how to get the prime into fastboot hold volume down and power, when you see the white text in the top left corner, press volume up then volume up to select fastboot of course the prime will be connected to the pc before this...
btw we were all noobs at one point... this is our school....
Click to expand...
Click to collapse
sent to Asus they want $220 to fix smh now trying to decide on paying or calling it a loss and buying the infinty.
If you can get to fastboot, then it's not a loss and it's recoverable.
Did you already send to Asus?
Sent from my vivow using Tapatalk 2
my phone is on 1.53, s-off and unlocked. im trying to relock it, but its not responding to adb commands. i reboot into fastboot and it shows fastboot usb, but when i type in any commands it just gets stuck at waiting for device.
any ideas?
What command are you using?
ADB commands works in booted android.
Fastboot commands works in fastboot-USB mode.
To relock the bootloader, type "fastboot oem lock"
mnomaanw said:
What command are you using?
ADB commands works in booted android.
Fastboot commands works in fastboot-USB mode.
To relock the bootloader, type "fastboot oem lock"
Click to expand...
Click to collapse
so im in fastboot usb mode. i typed in fastboot devices and its blank.
i do remeber typing adb reboot bootloader when the phone was booted and it rebooted into bootloader mode fine.
i pulled the rom.zip from ruu and renamed it pg86img.zip. did the update and its still saying unlocked??
debug mode is active. but adb devices doesnt want to detect the device. any ideas what's wrong?
Does enabling OEM Unlock from developer options (Android 5.1.1) unlocks the bootloader?
If yes then can I directly flash a custom recovery after enabling OEM Unlock?
ayu321 said:
Does enabling OEM Unlock from developer options (Android 5.1.1) unlocks the bootloader?
If yes then can I directly flash a custom recovery after enabling OEM Unlock?
Click to expand...
Click to collapse
No, it only gives you permission to unlock bootloader.
You will need to unlock bootloader using adb.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and your phone will reboot normally.
Augustoandro said:
No, it only gives you permission to unlock bootloader.
You will need to unlock bootloader using adb.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and your phone will reboot normally.
Click to expand...
Click to collapse
thnx for the reply augustonandro ! but i think im doing something wrong , whenever i type the command adb reboot bootloader my device(Galaxy J200G) restarts instead of rebooting to bootloader . So I just went to my stock recovery and chose option "reboot to bootloader" but still it restarted instead of rebooting to bootloader.
Am I doing something wrong?
ayu321 said:
thnx for the reply augustonandro ! but i think im doing something wrong , whenever i type the command adb reboot bootloader my device(Galaxy J200G) restarts instead of rebooting to bootloader . So I just went to my stock recovery and chose option "reboot to bootloader" but still it restarted instead of rebooting to bootloader.
Am I doing something wrong?
Click to expand...
Click to collapse
Try "adb reboot download" command
If u try
Setting>Developer Option>
Now search
OEM Unlock and enable
Ashwinrg said:
Try "adb reboot download" command
Click to expand...
Click to collapse
this command reboots to download mode not bootloader
guys i just found out this thread:https://forum.xda-developers.com/galaxy-j2/development/dev-samsung-galaxy-j2-lte-t3258147 and it says that just enable OEM Unlock and your bootloader will be unlocked. Is it true?
No, as explained above. That just allows the bootloader to be unlocked via ADB/fastboot (unless the bootloader is locked down like many ZTE phones).
Have you tried "adb reboot-bootloader"?
HI...I know after so many years....But i am having some problem considering my nokia 5 phone....In developer option the OEM unlock is greyed out and i cannot unlock it at all(i cannot toggle it on)....Any possible way i can turn it on....Let me know....Thanks in advance
Thebisboss said:
HI...I know after so many years....But i am having some problem considering my nokia 5 phone....In developer option the OEM unlock is greyed out and i cannot unlock it at all(i cannot toggle it on)....Any possible way i can turn it on....Let me know....Thanks in advance
Click to expand...
Click to collapse
It might already be unlocked
HI to all
I got my phone back from service, latest version installed (DN2103_11_A.14 EU).
I will flash TWRP and root, so do I need A.14 vbmeta or can I just use vbmeta from same post I will download TWRP?
If I need A.14 vbmeta, does anyone have it?
Thanks
There is no difference, the same one can be used for all versions.
you can use the vbmeta from TWRP Thread.
Zombnombs said:
There is no difference, the same one can be used for all versions.
Click to expand...
Click to collapse
HI and thank you.
HofaTheRipper said:
you can use the vbmeta from TWRP Thread.
Click to expand...
Click to collapse
HI and thank you.
How do you enter fastboot mode? There is no option from power button, and when I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit.
In recovery there is no "Advanced" option to reboot to fastboot.
krugm0f0 said:
I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit
Click to expand...
Click to collapse
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Zombnombs said:
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Click to expand...
Click to collapse
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
krugm0f0 said:
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
Click to expand...
Click to collapse
Seems like you just don't have the right drivers installed. Sure it looks different but that doesn't mean it has to work differently.
Windows can get the drivers automatically for you, connect in fastboot mode, then check for updates in windows, then they should either get installed or show up in optional updates as Mediatek ADB something.