I've been attempting to root my Samsung S6 (T-Mobile variant), but have been unable to flash the firmware. I've read through several guides on rooting Android devices and can't figure out what I'm doing wrong.
For additional context, this is the guide I've been following:
Specs:
Phone: Samsung S6 T-Mobile variant (SM-G920T)Version: Android 7.0Root kit: Magisk v23.0Steps I've taken so far:
Performed a full factory reset
Unlocked the Developer Options menu
Enabled OEM Unlock and USB Debugging
Installed Magisk on the phone
Downloaded and unzipped the adb, fastboot, and twrp files to my computer
Connected my phone to my computer via USB cable
Opened the device in Download mode while connected to my computer
Where I'm getting stuck:
When I open the Terminal and access the platform-tools folder in my directory, the commands "fastboot devices" and "adb devices" are not recognized.
Potential issues:
My computer is running a Linux Ubuntu distro that might not recognize these specific commands. I tried looking up equivalents and running them as "sudo" but with no change.The bootloader should be unlocked (since I can access fastboot/download mode), but the *#*#7378423#*#* code doesn't return results when I enter it into the phone app. (The phone does not have an SD card, nor has it been connected to the internet since it was factory reset.)While in download mode, my phone doesn't appear to establish MTP connection when linked to my computer.I didn't find any other posts for this particular problem, but I'm hoping there's a clever person out there with an answer. I'm running out of ideas. Any advice for next steps is appreciated.
An unrelated side note...
This is my first post on XDA (or any forum like it for that matter). If I've done something incorrectly I hope you can forgive me just this once, and if your sensibilities I truly have offended, just drop me a line in the comments to tell me how I can do better in the future. Thank you.
Related
Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
ChazzMatt said:
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
Click to expand...
Click to collapse
Thanks man. Will try this method too.
ahm259 said:
Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
Click to expand...
Click to collapse
Have you tried just connecting to your pc, enable 'Transfer Files'/mtp mode, and using PhotoRec to scan it as attached storage? The video should not have been anywhere you would need root to access, so this should work. I personally haven't used PhotoRec on a phone in several years, but in the past it worked great. It's free software from CGSecurity (often bundled with TesDisk).
http://www.cgsecurity.org/wiki/Phot...data_from_my_phone.2Fdisk.2Fusb_key.2F..._.3F
Just remember, everytime you use the device you risk rendering the video totally unrecoverable. At best you'll get the whole thing back. More than likely if you're lucky, you'll only get part of it and it will be enough that video software can recognize and play what's left. (based on my own experience). It just depends on how large the video was (data-wise) and how many blocks were overwritten by other data.
I installed hisuite which is easily able to access all my device data. Installed adb universal which created c:/abd in my pc or don't know what created that. Installed minimal abd fast boot . Now the problem is, i go to c:/adb and open command line and keep getting "waiting for devices" then goto x86/minimal adb.... Again same thing. Even installed android sdk without even knowing what I'm doing. Now I'm feeling like dumb (probably I'm) and about about to give up. What I'm missing??
What are you trying to do and what commands are you issuing?
I'm assuming at the very least you have phone connected with debugging enabled.
Just trying to follow commands of "Unlock Bootloader, Even without code! by hackintosh5". But first I'm doing some simple commands like "fastboot reboot recovery" or "fastboot devices" but no luck. I must be doing something terribly wrong. At least show me a guide article, cause when i search i get extremely confused.
Some more info.
-usb debugging enabled, and pc authorized (maybe)
-hisuite is able to read everything so i must GUESS i have installed correct driver (tho i have no idea what it is)
Ok, to use the fastboot commands, the phone must be in fastboot mode. This is achieved by when phone is off , hold Vol - and connect phone to PC via USB.
Then try the above commands.
It finally worked, thanks a lot brother :laugh:
Hi guys,
I've got a real head-scratcher over here. I followed every guide to a T, but I can't get my computer to detect my device in fastboot.
I installed the Xperia companion. I tried to manually install the Google USB drivers, and the sony OEM drivers. Still, no matter what, when I enter, what is supposedly fastboot, it never shows up. When the phone is on ADB devices shows it just fine. I am at a total loss!
To enter fastboot, I am shutting down the phone, pressing the volume up button, and plugging it in, then I get a black screen and a blue LED, which supposedly is correct? I've personally never seen anything like this before. Device manager does detect it as an unknown Android device, however, if I try to apply any drivers to it Windows simply informs me I already have the latest ones installed.
Thanks
SOLUTION: It was a driver issue after all. Windows 10 would not detect any drivers, nor let me install any drivers manually from files, however, it did let me select built-in drivers from my computer. YMMV, but If you are running into this issue try this:
1) Put your phone into bootloader mode.
2) Open device manager.
3) Right-click the device called "Android" with the yellow question mark, and select "update driver."
4) Click the "Browse my computer" option.
5) Click "Let me pick."
Note: There are several categories here, I suggest you try them all: portable devices, android devices, and in my case, Samsung devices. In one of the categories, you will find Google listed as a manufacturer.
6) In one of the categories, you will find Google listed as a manufacturer (in my case it was under the "Samsung Devices" category).
7) Select Google and then select the newest fastboot driver listed (in my case it was dated 2016), and install that driver.
8) Go back to PowerShell and run "fastboot devices." With a little luck, it will work!
Previous steps:
Edit: I had the thought of trying
Code:
adb reboot fastboot
and that got me into fastbootd, and then my PC detected it, however, the phone did not accept the unlock command.
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I rebooted into the bootloader from here, got the same black screen, blue LED as above, and my phone is still not detected by fastboot.
Make sure you open cmd window in fastboot folder...i hope this is help
Sony fastboot mode is different I think. It was odd to me but doesn't show anything on screen when I went to fastboot to flash US firmware
mehdi_s82 said:
Sony fastboot mode is different I think. It was odd to me but doesn't show anything on screen when I went to fastboot to flash US firmware
Click to expand...
Click to collapse
I live in Boston and got the the XQ-AT51 (despite the fact that B&H was originally selling the 52... so in a few months I'm going to have to flip this phone ), do I have to reflash a stock firmware before I can unlock the bootloader? I do have it from XperiFirm.
Edit: This was dumb of me as you can't flash anything onto the phone unless the bootloader is already unlocked.
Edit: I don't want to double post, but I managed to solve the problem, and added the solution to the OP.
THANK YOU VERY MUCH FOR THIS GUIDE. I was struggling for hours on end with the "Unable to open fastboot HAL" error message, but followed the steps outlined in your guide a little differently than you, since I'm on windows 7. I believe that the root cause of my issue was that I actually used the down volume button instead of the volume up, believing that it was weird for the screen to show nothing except for the blue notification LED.
Here is what I did just in case for people who might encounter the same issue in the future. Be warned though that I'm not an english native so the options won't be accurately translated but I'll try to do my best nonetheless.
1) Put your phone into bootloader mode (volume UP + power button, not down.) Don't be afraid if nothing shows up, it's actually normal
2) Open device manager
3) Right-click the device called "Android" with the yellow question mark, and select "update driver."
4)ISelect "Look for drivers on my computer (manual install option)
5)Select "Choose from a list of drivers installed on this computer"
6)Scroll down through the manufacturers and such until you find "sony sa0200"
7)Install it
Normally everything should be working fine with fastboot. What a relief
I have a similar problem, but my device manager does not show any android device from the bootloader. I've tried multiple cables and everything works fine in adb mode.
EDIT: Nevermind. It ended up being multiple bad cables. They all worked in ADB/booted but not in Fastboot/bootloader. Tried one more it it worked completely
I have same issue with my Poco X3 Pro, the device working fine and is recognized as ADB composite when i'm under MIUI, but when i launch the device in fastboot mode, the ADB composite disappear and a generic "android" device appear and i'm not able to install any drivers, no qualcomm, no xiami, no generic google usb, nothing.
Following the tips above, nothing work. I'm under windows 7.
Any tips?
Thx everyone for pointing me to the right direction. Flashing latest twrp was the final step. Recovery is back to now .
There are several devices, all EU, all with the same problem, are seen by adb but are not seen in the bootloader by a computer. If you run the adb reboot fastboot command in the adb, you will get into a strange half-repair half-fastboot mode, and the flash oem unlock command works there, but it falls out with an error. At the same time, everything is enabled in the development settings. If you run the adb reboot bootloader command through the adb, we get into the standard bootloader, but the computer does not react to this in any way, firewood from the site off the vanka is downloaded. Vanka 8ya is lying around, connects without any problems. I thought well, there is a forum member Mamay72 he has India and he unlocked the bootloader. I took advantage of the restoration of the brick, installed the firmware India, now tel India. But nothing has changed, oddly enough, the firmware has become DA, but NFC works. And it also does not seem to be a computer (there is no connection sound at all, nor any device in the dispatcher. There are thoughts at least where to dig while I monitor 4pda, but it's also deaf there
An update to Android 12 has been released. Everything seems to be fine. Random reboots appeared.
I tried a full reset of nothing, then downloaded the OTA via adb sideload in the hope that it helps, but to no avail.
And it's sad that the bootloader is locked
device verizon.
Screenshot shows adb sideload error
Who knows what can be done, please tell me.
-------------------------------
After 3 long days of agonizing and torturing Google support, no help from them
Found the adb rescue install file.zip command, in their source code
Because I had coral-ota-sp1a.210812.015 firmware, I needed verizon firmware, for me coral-ota-sp1a.210812.016.a1-37be0022 didn't work, it didn't start
But with this coral-ota-sp1a.211105.002.a1-0939d2dd everything is fine
The main thing is to have the usb cable intact. And the pc connector usb 2.0
1. Go into bootloader
2. Select Rescue mode
3. type in the following words at the command line
adb rescue install file_name.zip
All should go through without errors
May help someone
Sorry for my English.