So I am trying to use the fastboot package on my samsung j600gt but it doesnt even redognize the device when I type fastboot devices.
adb devices works normaly.
After checking the device management on windows the usb drivers are up to date.
Also the bootlaoder was arrived by adb reboot bootloader . Any thougjt on what can be done to make fastboot work normally?.
Fastboot doesn't work on Samsung devices.
jwoegerbauer said:
Fastboot doesn't work on Samsung devices.
Click to expand...
Click to collapse
Samsung devices don´t have fastboot mode enabled, Samsung calls bootloader to its download mode, that´s different.
What are you trying to do?
SubwayChamp said:
Samsung devices don´t have fastboot mode enabled, Samsung calls bootloader to its download mode, that´s different.
What are you trying to do?
Click to expand...
Click to collapse
Hello. Was trying to flash the TWRP. As trough Odin it doesnt work due to rmm lockrenormal. Even after OEM unlock and the 7 days
Owyeqt said:
Hello. Was trying to flash the TWRP. As trough Odin it doesnt work due to rmm lockrenormal. Even after OEM unlock and the 7 days
Click to expand...
Click to collapse
No. in this state you can´t, first try to bypass that, there are some forums with some tricks.
Related
I was working on rooting my device, and had a working root successfully with Magisk. But then I wanted to remove it and relock my bootloader, that's when the trouble started.
I am able to boot the phone and it is working. I can boot to recovery (stock OEM not TWRP), can boot to bootloader, and can boot and use the Oxygen OS. But I cannot get fastboot to run to lock the bootloader. ADB devices comes up empty. These are the steps that I've tried:
-using it on my chromebook that was working with ADB before the unrooting mess
-installed fastboot and adb along with Oneplus USB drivers on a fresh Windows 8 copy
-2 different red OEM oneplus cables
My goal is to return completely to stock and a locked bootloader. Any help would be appreciated, it really seems to be a phone issue and not a driver issue. Thanks everyone!
Use the unbrick tool. That autolocks bootloader when it flashes stock.
NateDev said:
Use the unbrick tool. That autolocks bootloader when it flashes stock.
Click to expand...
Click to collapse
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
bam099 said:
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
Click to expand...
Click to collapse
Are you sure you have USB debugging checked in developer options?
Absolutely. Just checked again. I would normally say it was a driver issue, but it was working fine until I flashed a boot.img and also I used a windows pc and a Chromebook and chrome os pretty much comes ready to talk to android phones or of the box. I was wondering if adb could have been messed up during the flashing of boot images.
bam099 said:
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
Click to expand...
Click to collapse
No fastboot needed, it's done with the phone off.
NateDev said:
No fastboot needed, it's done with the phone off.
Click to expand...
Click to collapse
Even better! I will definitely try the tool and report back.
NateDev said:
No fastboot needed, it's done with the phone off.
Click to expand...
Click to collapse
This was correct and it worked. Phone is restored back to stock with a locked bootloader and everything is working as it should.
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both.
Oneplus 7 pro is running 10.3.0GM21AA
>fastboot devices
>adb devices
List of devices attached
966c8016 device
Trying to use fastboot to flash patched magisk img and install magisk.
Do you enter in fastboot in phone?
Sent from my GM1910 using Tapatalk
Yes tried from bootloader as well
fustyler said:
Yes tried from bootloader as well
Click to expand...
Click to collapse
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
redpoint73 said:
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
Click to expand...
Click to collapse
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
fustyler said:
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
Click to expand...
Click to collapse
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
redpoint73 said:
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
Click to expand...
Click to collapse
Have tried different cables and different machines both pc and mac
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
mnemesis said:
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
Click to expand...
Click to collapse
I ran adb reboot bootloader from pc to boot phone into fastboot.
In the bootloader it states device state is unlocked
However fastboot devices ran from pc still shows no device.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thanks this fixed it.
Issue fixed by billyt1's comment above. case closed.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Giri Prasad said:
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Click to expand...
Click to collapse
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
I have a similar problem. I tried to disable the signature. Installed a new Redmi Note 7 driver. The phone is recognized as an Android phone in the device manager. In Orangefox recovery it is recognized with ADB command. In fastboot it is not recognized. In Orangefox I can't format data. So my ROM is not booting up. So I want to flash fastboot ROM with Fastboot but in Fastboot device is not even recognized.
t
puyow18 said:
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry on the late reply. Pretty sure you can only do fastboot boot boot(recovery).img or\and boot_a or boot_b. Wont let you fastboot flash boot.img.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thank you so much!
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Thank you Thank you Thank you Thank you Thank you Thank you...I have been fooling with this all day
Hi, I already solved this issue (but this only works for xiaomi phone (Redmi Note 7 to be specified), for other brands I think need to download your devices flasher/driver tool)
For Xiaomi user only
1. Download Mi Unlock Tool (https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/) (Version 4.5.813.51)
2. Extract the files anywhere you like
3. Run MiUsbDriver.exe to install the driver
4. Try fastboot devices command
I hope this helps you guys. The Mi Unlock Tool also useful to unlock device locked bootloader.
For other devices maybe can follow this tutorial
Fixed: Fastboot not detecting your Android device
Fix the Fastboot not detecting your device. If your device is not detected by the Fastboot then these tricks will really help you.
www.qasimtricks.com
Hey there, I'm currently trying to get into fastboot mode on my Samsung Galaxy A20e (SM-A202F), but everytime I boot into Bootloader mode, I'm just getting kicked into download mode, can anyone help me?
Thanks in advance! :good:
GeoBaer said:
Hey there, I'm currently trying to get into fastboot mode on my Samsung Galaxy A20e (SM-A202F), but everytime I boot into Bootloader mode, I'm just getting kicked into download mode, can anyone help me?
Thanks in advance! :good:
Click to expand...
Click to collapse
Samsung devices do not use fastboot, absolutely none of them. There is only download mode(and emergency download mode), recovery mode, safe mode, system mode and a couple of other rarely used modes on some Samsung devices. None of their modes are compatible with fastboot. Trying to use fastboot on any kind of Samsung device is a waste of time. Samsung is compatible with ADB but not fastboot.
If you are trying to use fastboot to unlock the bootloader, that is not how it is done on Samsung devices. Typically, you need to enable the OEM unlock setting in developer options on the device.
If you are trying to flash some kind of custom file, you will have to use Odin or ADB, ADB will require the device to be rooted or you won't be able to flash/modify anything on the device.
Sent from my SM-S767VL using Tapatalk
Hey there,everyone! I have a small problem here .So I have this old Android phone (SAMSUNG GALAXY GRAND QUATTRO GT-I8552)that i wanted to use to experiment with rooting and flashing custom roms(I am new to this) I tried unlocking the bootloader. The problem is that my phone couldnt be recognized once I am in fastboot mode (it can be detected when it's in normal mode/adb devices).I tried it on my current phone( Vivo Y55s) and it could be recognized tho.Any ways to get my phone detected in fastboot mode? I tried installing the drivers but i think that i messed it up.
On Windows computer install "Android USB Driver" matching your phone what is based on Qualcomm Snapdragon chipset.
jwoegerbauer said:
On Windows computer install "Android USB Driver" matching your phone what is based on Qualcomm Snapdragon chipset.
Click to expand...
Click to collapse
I tried it but it still doesn't works.(i tried reinstalling the driver and it still doesn't work)
If you didn't unlock bootloader in a proper way, your phone won't connect to fastboot.
Make sure you follow the steps to unlock bootloader, it happened to me before when I wanted to get root.
Haresh2910 said:
Hey there,everyone! I have a small problem here .So I have this old Android phone (SAMSUNG GALAXY GRAND QUATTRO GT-I8552)that i wanted to use to experiment with rooting and flashing custom roms(I am new to this) I tried unlocking the bootloader. The problem is that my phone couldnt be recognized once I am in fastboot mode (it can be detected when it's in normal mode/adb devices).I tried it on my current phone( Vivo Y55s) and it could be recognized tho.Any ways to get my phone detected in fastboot mode? I tried installing the drivers but i think that i messed it up.
Click to expand...
Click to collapse
Retter_ said:
If you didn't unlock bootloader in a proper way, your phone won't connect to fastboot.
Make sure you follow the steps to unlock bootloader, it happened to me before when I wanted to get root.
Click to expand...
Click to collapse
But how do I unlock my phone's bootloader if i can't access my device through fastboot mode?
Edit : I haven't unlock the bootloader yet.
First of all, fastboot is not compatible with Samsung, Samsung does not have a fastboot mode. Samsung devices use download mode a.k.a. Odin mode.
If you do not have the OEM unlock setting, you will not be to unlock the bootloader by any other means. Not all Samsung devices have this setting. Basically, you're screwed, you won't be able to unlock bootloader on your device.
Click to expand...
Click to collapse
I found this in another thread.
The best thing I personally recommend is to get TWRP, flash it from Odin....
I don't know if you want to acquire root. Hope this helps.
Retter_ said:
I found this in another thread.
The best thing I personally recommend is to get TWRP, flash it from Odin....
I don't know if you want to acquire root. Hope this helps.
Click to expand...
Click to collapse
Sure, i will try that method first and let you know.
After entering recovery I realized that it has a "Reboot to bootloader" on my Samsung phone. And it doesn't reboot to Download mode, instead, it reboots to a "Fastboot mode". Does this Fastboot really work or it's better do not modify anything there?
ferreraiury05 said:
After entering recovery I realized that it has a "Reboot to bootloader" on my Samsung phone. And it doesn't reboot to Download mode, instead, it reboots to a "Fastboot mode". Does this Fastboot really work or it's better do not modify anything there?
Click to expand...
Click to collapse
It seems the A10? Which model is? At least type fastboot devices to see if it is listed in CMD, anyway locked as it is you couldn't do much.
ferreraiury05 said:
After entering recovery I realized that it has a "Reboot to bootloader" on my Samsung phone. And it doesn't reboot to Download mode, instead, it reboots to a "Fastboot mode". Does this Fastboot really work or it's better do not modify anything there?
Click to expand...
Click to collapse
As I has knew since I used HTC M7. ''Locked'' status , it means the phone can't flash any custom ROM. my phone is Samsung M20 . it don't show as your picture
SubwayChamp said:
It seems the A10? Which model is? At least type fastboot devices to see if it is listed in CMD, anyway locked as it is you couldn't do much.
Click to expand...
Click to collapse
No, it's a A015M. After looking for some help, I realized that it really doesn't work.
fellpanda said:
Using Samsung Android 11 default ROM - nothing modified. I'm trying to boot custom recovery (twrp) temporarily from PC console.
What I did to set up adb and fastboot:
OEM unlocked, usb debugging active, not rooted.
I installed latest ADB and Fastboot. Also installed Samsung USB drivers. Samsung doesn't provide fastboot drivers, and I've read on some thread that AOSP drivers are used for that. So, I'm using Google's Bootloader Interface installed via Device Manager, because plenty of guides suggest that online.
Problem:
I can use adb when phone's on. But when it comes to fastboot, I can get into it by 'adb reboot bootloader' and, i can see the device is listed using 'fastboot devices', but i can't really do anything at all other than that command.
I tried 'fastboot oem device-info', 'fastboot boot twrp.img'. I don't get any error messages. When I execute a command, the command just stays there on the terminal like it is busy executing. Waiting for over 15 minutes and there's no change.
Ex: When I executed the boot command, the console output was stuck at 'Sending boot.img', without any progress.
Click to expand...
Click to collapse
crownvn said:
As I has knew since I used HTC M7. ''Locked'' status , it means the phone can't flash any custom ROM. my phone is Samsung M20 . it don't show as your picture
Click to expand...
Click to collapse
That's not my device, it's from a YouTube video, because I couldn't take any picture until now. My device is listed as unlocked.
Samsung devices don't know of Fastboot mode but of Download ( aka ODIN ) mode, hence not any fastbbot command works.
xXx yYy said:
Samsung devices don't know of Fastboot mode but of Download ( aka ODIN ) mode, hence not any fastbbot command works.
Click to expand...
Click to collapse
ferreraiury05 said:
No, it's a A015M. After looking for some help, I realized that it really doesn't work.
Click to expand...
Click to collapse
I think fastboot is only there because it is a MTK device.
If it's a Samsung SM-A015M then it's not MTK, but Qualcomm based.
I have j7 2015 and i have twrp and i want to do "fastboot boot <magisk patched image>" but i can't do it because i can't get inside fastboot mode
Any soulotions please?
Sorry for bad English.
As said earlier here Samsung devices don't have a FASTBOOT mode
xXx yYy said:
As said earlier here Samsung devices don't have a FASTBOOT mode
Click to expand...
Click to collapse
Thanks so the only way to flash images only with modded TWRP or flashify
Abdullrahman_Dawaliby said:
Thanks so the only way to flash images only with modded TWRP or flashify
Click to expand...
Click to collapse
or odin
With fastboot it is possible to enable the UART serial interface for viewing kernel messages. Is it even possible to do that on Samsung devices, since fastboot is not available?