Hey bros. This might sound like a noob question but I just cannot get the phone to show up in command prompt. I booted the thing into fastboot, I have all of them adb goodies installed (alright not all of them, only the minimal installation) and I also have the Nokia driver installed but the thing simply refuses to show up. I type "fastboot devices" and I just get another line of text. Interestingly enough though I did manage to unlock the bootloader, even though when I typed "fastboot devices" I got nothing, just like the first time. When I try to flash TWRP I get the legendary "<waiting for device>" message. Although like I was saying, unlocking the bootloader worked just fine, which is strange
Brilliant99 said:
Hey bros. This might sound like a noob question but I just cannot get the phone to show up in command prompt. I booted the thing into fastboot, I have all of them adb goodies installed (alright not all of them, only the minimal installation) and I also have the Nokia driver installed but the thing simply refuses to show up. I type "fastboot devices" and I just get another line of text. Interestingly enough though I did manage to unlock the bootloader, even though when I typed "fastboot devices" I got nothing, just like the first time.
Click to expand...
Click to collapse
i think it's ok, it doesn't matter if other adb and fastboot commands work properly.
SkaboXD said:
i think it's ok, it doesn't matter if other adb and fastboot commands work properly.
Click to expand...
Click to collapse
Problem is, when I try to flash TWRP I get the legendary "<waiting for device>"
Brilliant99 said:
Problem is, when I try to flash TWRP I get the legendary "<waiting for device>"
Click to expand...
Click to collapse
I am sorry I forgot to mention that in the main post. Let me edit it
Brilliant99 said:
Problem is, when I try to flash TWRP I get the legendary "<waiting for device>"
Click to expand...
Click to collapse
try to install other adb. I recommend to install platform-tools as it have only 5mb. If that doesn't work, try to reinatall Nokia 3 driver.
SkaboXD said:
try to install other adb. I recommend to install platform-tools as it have only 5mb. If that doesn't work, try to reinatall Nokia 3 driver.
Click to expand...
Click to collapse
I did all of that too and it still doesn't work. I have Windows 10 if that helps. I also have another computer on Windows 8.1
Brilliant99 said:
I did all of that too and it still doesn't work. I have Windows 10 if that helps. I also have another computer on Windows 8.1
Click to expand...
Click to collapse
I also have access to macOS, but I doubt it's any useful
Brilliant99 said:
I did all of that too and it still doesn't work. I have Windows 10 if that helps. I also have another computer on Windows 8.1
Click to expand...
Click to collapse
maybe a stupid question, but did you enable usb debugging and usb file transfer (mtp)?
SkaboXD said:
maybe a stupid question, but did you enable usb debugging and usb file transfer (mtp)?
Click to expand...
Click to collapse
I enabled those too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
idk then, try on other system, I'm using Windows 7 and i never had problem with it.
Try this
fastboot.exe -i 0x2e04 [Your_Command]
i had same issued but it fixed after use that command
lordschleger said:
Try this
fastboot.exe -i 0x2e04 [Your_Command]
i had same issued but it fixed after use that command
Click to expand...
Click to collapse
Thank you , you saved me hours of problem solving
Related
i'm using nexus 5 toolkit and when i finish download the stock rom and starting to flast it
it get stuck, at first after trying send "bootloader"
then it's show error and return me to the main menu..? what to do?
i want to return stock rom and having like a new phone
tx for help
stop using a toolkit
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Zepius said:
stop using a toolkit
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
This...
But have a look at my "adb and fastboot. what is it?" thread. It will tell you how to ensure you have everything you need installed first. You cn get to it via the sticky roll-up link in my signature.
Zepius said:
stop using a toolkit
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
still have the same problem..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
harel013 said:
still have the same problem..
Click to expand...
Click to collapse
Red my thread. Ensure fastboot is set up correctly and test if fastboot can see your device please. We cant really troubleshoot unless you do this.
If fastboot CAN see your device, flash the images separately (manually)
eg
flash system, then flash cache, etc
harel013 said:
still have the same problem..
Click to expand...
Click to collapse
you clearly did not read the thread and links within the thread.
go read what rootsu told you to read now or you wont get anymore assistance.
rootSU said:
Red my thread. Ensure fastboot is set up correctly and test if fastboot can see your device please. We cant really troubleshoot unless you do this.
If fastboot CAN see your device, flash the images separately (manually)
eg
flash system, then flash cache, etc
Click to expand...
Click to collapse
alright, i did everything right.. fastboot is set up correctly and i see my device through the fastboot
and when i trying to flash image separately i still get that error
rebooting into bootloader...
FAILED (unknown status code)
finished. total time: 1.015s
Click to expand...
Click to collapse
i open the link in your signature and installed all the thing like adb in 15 sec and drivers.. tried to restart the pc also
dont know what now?
harel013 said:
alright, i did everything right.. fastboot is set up correctly and i see my device through the fastboot
and when i trying to flash image separately i still get that error
i open the link in your signature and installed all the thing like adb in 15 sec and drivers.. tried to restart the pc also
dont know what now?
Click to expand...
Click to collapse
Which image did you try to flash?
Please provide screenshot of image files in Windows explorer
Please provide screenshot of command prompt when you have executed the commands
rootSU said:
Which image did you try to flash?
Please provide screenshot of image files in Windows explorer
Please provide screenshot of command prompt when you have executed the commands
Click to expand...
Click to collapse
i feel very stupid... i think that was a problem in my usb port.. i just now replace the usb port and everything work fine!
very strange... although that the fastboot recognize the device in that "damge" usb port...
but now all work good! thx again! for you'r help! i'm sorry for confuse =\
No probs. Yep sending a file versus listing connected devices is very different
Sent from my Nexus 5 using Tapatalk
Nine posts. Junior member? The dangers of toolkits, writ large. Learn to walk. Toolkits are good if 6 have the knowledge to put it right. Get reading
#64268gkyJL#8653%dhjGUKVS357.
yea but i used it before in nexus 4 and i had no problems all worked just fine.. but you right i need to start learnig how to do all in my self..
So i'm trying to unlock my bootloader on my LG optimus 4x HD (p880) Running 4.0.3 ICS
I've installed my adb & fastboot.
But when i try to do commands from fastboot it says: Waiting for device...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried it on my pc (win7) linux & on another windows 7 in virtual machine...
Still fastboot wont recognize my device
Can't really find any solution
I tried:
- usb 2.0 / 3.0
- run CMD as administrator / run ternimal with sudo
- windows 7
- windows 7 clean installation
- linux (ubuntu & debian)
Can anyone please help me.. I want CM so badly
Your device must have "USB Debugging" enabled.
All drivers for your device must be installed and make sure your adb and fastboot files are not corrupted.
TheArc said:
Your device must have "USB Debugging" enabled.
All drivers for your device must be installed and make sure your adb and fastboot files are not corrupted.
Click to expand...
Click to collapse
USB debigging is enabled
@ryantju And what about the others. Make sure the drivers for your device are correctly installed.
TheArc said:
@ryantju And what about the others. Make sure the drivers for your device are correctly installed.
Click to expand...
Click to collapse
Yeah i did it all.
what i tried is to update my phone to JB v20b
and whenever my phone wants to get in recovery mode i get this screen:
ryantju said:
So i'm trying to unlock my bootloader on my LG optimus 4x HD (p880) Running 4.0.3 ICS
I've installed my adb & fastboot.
But when i try to do commands from fastboot it says: Waiting for device...
Tried it on my pc (win7) linux & on another windows 7 in virtual machine...
Still fastboot wont recognize my device
Can't really find any solution
I tried:
- usb 2.0 / 3.0
- run CMD as administrator / run ternimal with sudo
- windows 7
- windows 7 clean installation
- linux (ubuntu & debian)
Can anyone please help me.. I want CM so badly
Click to expand...
Click to collapse
Are you sure you have reboot your phone to bootloader mode...? If not type:
Code:
adb reboot-bootloader
root-expert said:
Are you sure you have reboot your phone to bootloader mode...? If not type:
Code:
adb reboot-bootloader
Click to expand...
Click to collapse
Doesn't work
some people are telling me to update to JB first.
but whenever i do that i get the notice error listed above
ryantju said:
Doesn't work
some people are telling me to update to JB first.
but whenever i do that i get the notice error listed above
Click to expand...
Click to collapse
Can you recognise your device with adb... If not try to reinstall your drivers...
root-expert said:
Can you recognise your device with adb... If not try to reinstall your drivers...
Click to expand...
Click to collapse
Yes adb sees my device and i tried reinstalling, using another computer & using linux nothing seem to work
ryantju said:
Yes adb sees my device and i tried reinstalling, using another computer & using linux nothing seem to work
Click to expand...
Click to collapse
When you type the command:
Code:
adb reboot bootloader
Does it actually reboots to bootloader... With this command should work...!
root-expert said:
When you type the command:
Code:
adb reboot bootloader
Does it actually reboots to bootloader... With this command should work...!
Click to expand...
Click to collapse
I don't know what i should see. The command works and it reboots but after that the fastboot commands still don't work
ryantju said:
I don't know what i should see. The command works and it reboots but after that the fastboot commands still don't work
Click to expand...
Click to collapse
What do you see on your screen...?
Also have you tried this command:
Code:
adb reboot oem-unlock
I think you have to have a JB version...
root-expert said:
What do you see on your screen...?
Also have you tried this command:
Code:
adb reboot oem-unlock
I think you have to have a JB version...
Click to expand...
Click to collapse
hmm well than i need to wait for an anwser from LG.
Thanks for the help
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
quantum94 said:
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
Click to expand...
Click to collapse
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
root-expert said:
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
Click to expand...
Click to collapse
nopes...on typing "fastboot code", it redirects me to the current directory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what to do?
Are you sure you are in fastboot mode?
root-expert said:
Are you sure you are in fastboot mode?
Click to expand...
Click to collapse
pretty sure...u can see the pic at:
What now!? :crying:
quantum94 said:
pretty sure...u can see the pic at:
What now!? :crying:
Click to expand...
Click to collapse
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
root-expert said:
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
Click to expand...
Click to collapse
sorry for the late reply....
I tried the same thing on different pc and it worked!
But i have another problem!
I installed cm11 nightly for my on my x plus from here:
http://get.cm/get/qG0
After that my imei has gone blank along with the baseband version.
I did a bit of research and found that by using ruu, u can get the imei back.
So for that i needed turn my s-on to s-off by the foll commands:
adb reboot
if i am not mistaken, while the phone is rebooting i am supposed to put the 2nd command:
adb wait-for-device push firewater /data/local/tmp
The problem here that I think is the phone reboots so fast that i guess the command fails to execute and i get an error saying :
error protocol fault (no status)
So, how to turn off fastboot or quickboot in cm11? There is absolutely no option in the phone. I tried battery settings,power settings, everything!
is there a way to disable fastboot/quickboot in bootloader mode?
plz help!
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Bencaill said:
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Click to expand...
Click to collapse
Hello, are you sure you have the boot.img also in the direcotry?
DallasCZ said:
Hello, are you sure you have the boot.img also in the direcotry?
Click to expand...
Click to collapse
yes, I am sure I have it
Bencaill said:
yes, I am sure I have it
Click to expand...
Click to collapse
i tried it again and it works well for me.
can you post a creen of the folder where you extracted the files?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you have to run the root.bat file, you cannot dir the boot.img
I know I have to run the bat file but you asked me a screen of the folder
I have this message:
strange... idunno for me its working well (windows 7 pro) and the boot.img is in the same directory... do you have some antivirus, anti spam apps running?
A other member of Frandroid forum has exactly the same issue. But he is running W8.1
That is really strange.
I am running win 8.1 as well
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
The problem seems to be resolved by using Windows 7 instead.
http://forum.frandroid.com/topic/223905-tuto-root-de-l-idol-3-55/?p=3417628
using win 7 is not a solution... there have to be a way how to do it, because there are thousands of users with win 8.1 who using fastboot and adb commands...
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
is your bootloader unlocked?
And I take it you've enabled Developer Options and USB Debugging?
After all my talk about the ease of communicating with Android devices from a Mac, I'm now unable to successfully issue fastboot commands when in the bootloader. I've tried using sudo, making sure to include arguments that address the device, etc. I can execute adb commands when the phone's system is booted, though. But fastboot commands either get me a "waiting for device" or nothing at all. I thought I was able to do this successfully yesterday, when I was just testing it out. Today, I was going to root by booting into TWRP and flashing SuperSU.
maigre said:
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
Click to expand...
Click to collapse
If it was a driver issue, my phone would not restart with the command, every drivers are OK
ractar28 said:
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
Click to expand...
Click to collapse
Your method worked !!!!!!!!!!!!!!! THX !!!!!
Hello All
I have had to reinstall stock(sm-g930f) due to an own stupid(again) mistake.
The OS is reinstalled and working and now I would like to flash Magisk through ADB. ADB recognises the phone by "adb devices" when in normal mode. When in fastboot (download mode) it does not recognise the phone. All it states is: List of devices attached
Can someone help me to overcome this, or if you have another suggestion to flash Magisk?
Edit:
after searching for a long time I read somewhere:
Do not put phone in download(fastboot) mode, only in charging mode when connected to the PC's motherboard USB port. Works flawless since, with having the relevant ADB drivers installed.
Adb is adb.
Fastboot is fastboot.
For adb, you need adb binaries.
For fastboot, you need fastboot binaries.
I have downloaded these and and haven't had any luck. Is there a detail how-to somewhere?
kiwigi said:
I have downloaded these and and haven't had any luck. Is there a detail how-to somewhere?
Click to expand...
Click to collapse
Try this:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
d
VD171 said:
Try this:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Click to expand...
Click to collapse
Thanks
Done that. PC is not recognising phone in download mode(fastboot)
kiwigi said:
d
Thanks
Done that. PC is not recognising phone in download mode(fastboot)
Click to expand...
Click to collapse
Probably because you didn't have drivers installed.
You need to find the specific drivers for your device model and install it.
Good luck.
VD171 said:
....
You need to find the specific drivers for your device model and install it.
..
Click to expand...
Click to collapse
I have searched for hours and all I have found seems not to be compatible with S7 sm-g930f. I have also followed this https://androidadbdriver.com/ specific to my mobile.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you really try to find ?
Here is the download for samsung usb drivers: https://developer.samsung.com/mobile/android-usb-driver.html
Install it and reboot.
If it doesn't work, probably you have any problem in your device manager.
I'm an user linux and I hate windows.
Good luck google'ing it.
Im having the same problem. i don't want to use the adb setup thing becuase its a virus so yeah.
kiwigi said:
Hello All
I have had to reinstall stock(sm-g930f) due to an own stupid(again) mistake.
The OS is reinstalled and working and now I would like to flash Magisk through ADB. ADB recognises the phone by "adb devices" when in normal mode. When in fastboot (download mode) it does not recognise the phone. All it states is: List of devices attached
Can someone help me to overcome this, or if you have another suggestion to flash Magisk?
Edit:
after searching for a long time I read somewhere:
Do not put phone in download(fastboot) mode, only in charging mode when connected to the PC's motherboard USB port. Works flawless since, with having the relevant ADB drivers installed.
Click to expand...
Click to collapse
THANK YOU!!! From a fellow Kiwi. I followed a tutorial for my Nokia G20 and they left this part out! Faaaaar out. You're my hero