Hey, I just bought an S7 Edge SM-G950U, the att&t version, SM-G950A. I heard some say that it's not possible to unlock its bootloader, but the OEM unlock option turned out to be available in developer options. However, I'm having a hard time properly installing its drivers, whichever adb driver I use, the driver still shows a yellow warning and the error is that the device can't be started. The device shows up with adb devices when the device is on, but it doesn't neither with fastboot devices nor adb devices when it's in download mode. I'm trying to install TWRP, the hero 2 version. Any help would be appreciated. Thanks in advance
If you in Windows Device Manager find any device with yellow mark right on the device, then the driver installed for it isn't suitable: uninstall it, get Samsung USB Driver and install it.
Samsung devices don't know of a Fastboot mode: there it's called Download mode. You can't run any Fastboot command in this mode.
ADB operates on Android OS, not on device's bootloader, hence it's not working when running the device in Download mode.
Thanks for the prompt reply. I used a different laptop and managed to install the drivers properly, no warnings. However, the result is the same. You mention how I can't run fastboot commands in Download mode, where can I run them? Only Odin is working in that mode now, but I gotta try to unlock the bootloader. A lot of people are saying that this model can't be unlocked, even though the OEM unlock checkbook in the Developer settings is there. Any advice is appreciated
Up
Gearninja said:
Up
Click to expand...
Click to collapse
Down
Related
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
madbat99 said:
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
Click to expand...
Click to collapse
Few other thoughts:
- try a different cable; a cable that works for charging and adb communication may not work with fastboot
- avoid external hubs if possible
- be sure to reboot both devices after switching drivers if communication isn't immediately established
Marc_Xperia said:
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
When you say you booted to fastboot what do you mean ?
Did use adb and your phone was recognized and then you issued adb command or what method are you using ....
You need to ensure you establish USB debugging connection first & grant authorization ...once link with authorization has been established run adb ...from adb check if recognized run command to boot to fastboot
So start from the top && go down
ARE YOU CERTAIN YOU USED CORRECT METHOD TO TURN OFF DRIVER VERIFICATION ON WINDOWS 10 && YOUR DRIVER ACTUALLY INSTALLED
Last noteworthy point ... when unlocking my motoE4 I had to boot to bootloader ONLY to use fastboot NOT "FASTBOOT"
Hold power + volume button
Excellent troubleshooting from our community. OP has not come back yet to confirm, ask another question, or simply a thanks. (Maybe he got it) Hopefully he gets it sorted.
Maybe the junior members underestimate just how quick and helpful our little community can be.
@Marc_Xperia Do not forget to install AndroidBootloaderInterface Driver Software. *android_winusb.inf*
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Marc_Xperia said:
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Click to expand...
Click to collapse
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
KevMetal said:
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
Click to expand...
Click to collapse
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Marc_Xperia said:
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Click to expand...
Click to collapse
Why select meta mode ? When you are in bootloader you use your volume keys to navigate between meta, recovery& factory reset & meta and you use your power key to select different modes ...what do you want to do in meta mode ?
When you are in bootloader you are essentially in fastboot mode too so it isn't necessary to choose any of the other options unless you are trying to get into recovery which is pointless if you haven't flashed custom recovery yet ..
I Succeded. I Booted into Bootloader with ADB and took a look at Device Manager to install the Driver Properly.
i followed this guide https://forum.xda-developers.com/moto-e4/how-to/guide-unlock-moto-e4-bootloader-unique-t3654275.
Thank you for all of your Replys.
Moto e4 magisk manger trying to instal magisk hide props config says install failed
happymedium22026 said:
Moto e4 magisk manger trying to instal magisk hide props config says install failed
Click to expand...
Click to collapse
Download manually and flash inside recovery yourself
Safety net says the response is invalid does that affect ny device being rooted
happymedium22026 said:
Safety net says the response is invalid does that affect ny device being rooted
Click to expand...
Click to collapse
No it doesn't. That's an error in magisk manager when you hide the manager app itself. Just use a different safetynet checker app if you want to check safetynet.
Why are you posting this stuff in this thread?
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Did you follow funkwizard's guide in the guides/news/discussion forum? It's stickied at the top.
Anyhow, if you followed the guide, he provides this link (https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view?usp=drivesdk) for the OP6T drivers that need it be installed.
He then provides this link (https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view?usp=drivesdk) to update your ADB/fastboot to the latest version.
Complete both of those steps and your phone SHOULD be recognized in fastboot. Good luck.
I have read his complete thread and im still stuck with the same problem. I deinstalled all phone related driver and only installed the one from the thread, opened the command prompt via admin and under device manager is still the yellow triangle beside the android device. I tried to install the driver manually via the google universal driver, but windows never found any compatible drivers.
And just to be certain, do you have USB Debugging enabled in developer options?
Pain-N-Panic said:
And just to be certain, do you have USB Debugging enabled in developer options?
Click to expand...
Click to collapse
Yupp, but i have to say that i had to tap it four to five times until the confirmation window popped up.
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Bartuc666 said:
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Click to expand...
Click to collapse
Thanks for the try, but still no change.
lubal21 said:
Thanks for the try, but still no change.
Click to expand...
Click to collapse
forget all the other tips, install the Google USB drivers with the batch file by entering Y on every question. select install driver in the device manager by selecting manually install. in the list presented select on the left Google Inc and on the right the fastboot driver. finish setup and fastboot should work now
lubal21 said:
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Click to expand...
Click to collapse
Probably this shall help:
How to Fix OnePlus Device not showing in Fastboot Mode
In this detailed guide, we will show you the steps to fix the OnePlus Device not showing in the Fastboot Mode on Windows 10 PC.
www.droidwin.com
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
might be a long shot but i read somewhere else that a person had to type
fastboot -i 0x2e17 < zip/file here >
sorry ; all i know to try.
good luck
maybe @IronRoo can help.
I had the same issue but installed the driver from here and it worked.
https://essentialsupport1493251565....015490828-Windows-Drivers-for-Essential-Phone
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
Connect in fastboot mode and then restart phone with plugged in condition, see if it gives any driver notification.. if dosent then connect the pbone as media device it would show driver disk, you may install driver from there.
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
If non of the above work uninstall all phone drivers & or any other phone connection software that installs phone drivers also eg Samsung Kies/Connect then reinstall Essential drivers, though haven't read about conflicts in recent years ....(Also try different USB ports pref on direct to mother board, people have suggested in the past)
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
AOSP100 said:
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
Click to expand...
Click to collapse
Update: Replacing the Google drivers (ADB, bootloader, etc) with Samsung ones in device manager broke everything so I had to reinstall the Samsung USB drivers, and uninstall platform-tools and the Google drivers through Android Studio
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
ninjasinabag said:
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
Click to expand...
Click to collapse
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
AOSP100 said:
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
Click to expand...
Click to collapse
Yeah, sadly the a205u will probably never get root or custom ROMs. We have an extremely small chance since Samsung promised two major updates for the A20.
Either way, https://forum.xda-developers.com/android/software/tool-universal-fastboot-adb-tool-t3475832/amp/
Has the fastboot drivers if you haven't tried that one yet.
.
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
sujan smash said:
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
zgfg said:
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
Click to expand...
Click to collapse
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
sujan smash said:
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
Click to expand...
Click to collapse
Everything looks correctly set but you could still try another PC and USB cable
zgfg said:
Everything looks correctly set but you could still try another PC and USB cable
Click to expand...
Click to collapse
Well i did that too, tried it on my laptop too no luck there also,
As ive mentioned in the first thread ,
It is detecting redmi note 10 in fastboot mode on the same pc with same cable and everything, but not redmi k20, so its not abt PC drivers its something to do with my phone
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
zgfg said:
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
Click to expand...
Click to collapse
Yep it sucks, Thanks Anyways