Related
I am trying recovery,but every time when i write fastboot oem unlock i gives me back with a message "waiting for devices",and just holds there....what should i do to make recovery....Thanks in fowards...
mimi12 said:
I am trying recovery,but every time when i write fastboot oem unlock i gives me back with a message "waiting for devices",and just holds there....what should i do to make recovery....Thanks in fowards...
Click to expand...
Click to collapse
Are you following any of the guides in the Development section?
Are you Mac or Windows or Linux?
Your post is a little hard to understand, but I think you're trying to push the clockwork recovery to your phone, is that correct, or are you just trying to get into normal recovery?
Assuming you're on the white screen that says fastboot mode at the top of it, then your problem is that you don't have the proper drivers on your computer to talk to the phone. You need to install the drivers from the SDK (or if on Windows you can use PDANet).
The best guide on there, AllGamer's, has full instructions on how to get the phone and the computer talking to each other properly.
May I ask why you want to oem unlock the phone? You're aware it's not necessary to do this to root the phone or flash clockwork recovery or even flash custom roms? There's nothing wrong with running unlocked (I do), but just be aware that the fastboot oem unlock command will totally WIPE ALL DATA off your phone, including your pics and music off the USB storage area.
My guide to rooting has you skip the oem unlock, but you can follow any guide and just skip that step to avoid wiping your phone.
Sorry for the short post.I run on Windows,i dont know what is clockwork recovery,i read something about it,but i didnt understand,i think that i need normal recovery.I installed sdk on my computer and i go to load drivers(browse....etc)and it cant "find" drivers,i installed pdanet also and i get the same message "waiting for devices",i installed some application and it started to freeze every 5-10min,i dont have that much data on him self,so its ok if recovery wipe all data,i will try that guides and will get back to you how it went,btw THANKS for everything....
This thread might help you out as well. http://forum.xda-developers.com/showthread.php?t=878786
Thank you for everything,i did it,i wipe out everything and now is working like new.......i had troubles with installing adb and fastboot drivers,but i managed to figure it out,and everything went smooth))One again thank you very,very,very,very,very,very,very,very,very,very much....
P.S -sorry if my english is bad...
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
Hello, first post on this forum, so yeah ^^ I am also kinda new to this. I have a gs3 which is rooted and all, but that is old, and methods has changed...
So i tried to root my shield tablet and it got stuck in a boot loop. I can not get it into the bootloader using adb tools, or fastboot, or atleast i knot know how to. I have ran the: adb reboot bootloader, without success. I have also tried the: adb devices command and i dont see my device there. I have installed mini adb drivers.
This happend when using this tool(windroid): http://forum.xda-developers.com/showthread.php?t=2499926
So im thinking that if there is a way to get out of this, that would be great. I really hope i have not bricked it... all i wanted to to was to get root so that i could connect a ps3 controller... :/
I tried to use the windroid program but the recovery did not install. so i did it manually following this tut http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
im am not complaining or anything, purly looking for help.
So, after trying i got it up and running. i did not flash any supersu.zip files, just installed it from the market. wen it asked me to reboot the device ended up like this. I am aware of the disclaimers and stuff. If i go to device manager on my computer i can se: SHIELD Tablet, with a yellow triangle. I also searched youtube and this forum to look for posts, but found none that could help.
image: https://www.dropbox.com/s/16y1icl89etg9q9/2015-04-18%2015.36.46.jpg?dl=0[/IMG]
**Update** I found out how to get into the bootloader manually, so ill continue trying...
I'm done
xswish said:
Hello, first post on this forum, so yeah ^^ I am also kinda new to this. I have a gs3 which is rooted and all, but that is old, and methods has changed...
So i tried to root my shield tablet and it got stuck in a boot loop. I can not get it into the bootloader using adb tools, or fastboot, or atleast i knot know how to. I have ran the: adb reboot bootloader, without success. I have also tried the: adb devices command and i dont see my device there. I have installed mini adb drivers.
This happend when using this tool(windroid): http://forum.xda-developers.com/showthread.php?t=2499926
So im thinking that if there is a way to get out of this, that would be great. I really hope i have not bricked it... all i wanted to to was to get root so that i could connect a ps3 controller... :/
I tried to use the windroid program but the recovery did not install. so i did it manually following this tut http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
im am not complaining or anything, purly looking for help.
So, after trying i got it up and running. i did not flash any supersu.zip files, just installed it from the market. wen it asked me to reboot the device ended up like this. I am aware of the disclaimers and stuff. If i go to device manager on my computer i can se: SHIELD Tablet, with a yellow triangle. I also searched youtube and this forum to look for posts, but found none that could help.
image: https://www.dropbox.com/s/16y1icl89etg9q9/2015-04-18%2015.36.46.jpg?dl=0[/IMG]
**Update** I found out how to get into the bootloader manually, so ill continue trying...
Click to expand...
Click to collapse
So, i fixed the problem by browsing back in the forums, did not know you could get into the bootoader by sing hw keys... lol
I fixed it by following this post: http://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
How do I install recovery on a soft bricked galaxy S7 edge. Sprint, that the boooafsr is still locked on. I can access recovery mode and device is recognized when i click apply update from adb, but it disabled updates from external sources. So they all fail. I didn't install recovery beforehand and now I'm in a quadary. Does anyone know if it's even possible to install recovery at this point? And if so, how?
ZiggyJapheth said:
How do I install recovery on a soft bricked galaxy S7 edge. Sprint, that the boooafsr is still locked on. I can access recovery mode and device is recognized when i click apply update from adb, but it disabled updates from external sources. So they all fail. I didn't install recovery beforehand and now I'm in a quadary. Does anyone know if it's even possible to install recovery at this point? And if so, how?
Click to expand...
Click to collapse
You are saying you want to install recovery, but you can reboot to recovery (?) if you mean that how you can recover your device see the exact build number in recovery screen, download the firmware file and flash it through Odin, tap on "reboot bootloader", this will lead you to Odin, also you can enter to it manually.
O
SubwayChamp said:
You are saying you want to install recovery, but you can reboot to recovery (?) if you mean that how you can recover your device see the exact build number in recovery screen, download the firmware file and flash it through Odin, tap on "reboot bootloader", this will lead you to Odin, also you can enter to it manually.
Click to expand...
Click to collapse
Ok, now we're talking. I can see you know what your speaking about. I meant to say, how can I install a recovery app , like TWRP or clockworkmid. Ok i can enter download mode easily enough by clicking the side and power buttons, however, the device isn't recognized by my moto E5 anymore. It's only recognized when i click apply update from adb....even tho when i try to sideload anything that way it ultimately aborts saying updates from external sources is disabled. So...back to Odin.its only runable from a windows OS....is there a version of Odin i can run on a Motorola and flash from it onto my softbricked Samsung Galaxy that's connected via otg cable? Thanks for all the time and insight by the way
ZiggyJapheth said:
Ok, now we're talking. I can see you know what your speaking about. I meant to say, how can I install a recovery app , like TWRP or clockworkmid. Ok i can enter download mode easily enough by clicking the side and power buttons, however, the device isn't recognized by my moto E5 anymore. It's only recognized when i click apply update from adb....even tho when i try to sideload anything that way it ultimately aborts saying updates from external sources is disabled. So...back to Odin.its only runable from a windows OS....is there a version of Odin i can run on a Motorola and flash from it onto my softbricked Samsung Galaxy that's connected via otg cable? Thanks for all the time and insight by the way
Click to expand...
Click to collapse
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
SubwayChamp said:
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
Click to expand...
Click to collapse
SubwayChamp said:
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
Click to expand...
Click to collapse
Yes that's exactly what I'm attempting. See, i had my Samsung Galaxy S7 edge which is soft bricked in recovery mode, while connected to a moto E5 play, which i used as a master device to send adb commands to my Samsung. I am trying to recover my Galaxy. I know that Odin only works on windows, and my inability to secure access to a PC is a major obstacle. The circumstances causing that are extremely varied and complicated, lol, however, impossible. So...i have other androids to serve as the master device or i can download zip files on to SD cards and try to apply updates from them through recovery mode,tho it says those options are disabled when i try. But those are my options, bro. Is there no way to run Odin or a android version of Odin to accomplish this? Can I somehow run a windows OS on an Android just for the purpose of running Odin 3 to flash firmware on my bricked Galaxy?
ZiggyJapheth said:
Yes that's exactly what I'm attempting. See, i had my Samsung Galaxy S7 edge which is soft bricked in recovery mode, while connected to a moto E5 play, which i used as a master device to send adb commands to my Samsung. I am trying to recover my Galaxy. I know that Odin only works on windows, and my inability to secure access to a PC is a major obstacle. The circumstances causing that are extremely varied and complicated, lol, however, impossible. So...i have other androids to serve as the master device or i can download zip files on to SD cards and try to apply updates from them through recovery mode,tho it says those options are disabled when i try. But those are my options, bro. Is there no way to run Odin or a android version of Odin to accomplish this? Can I somehow run a windows OS on an Android just for the purpose of running Odin 3 to flash firmware on my bricked Galaxy?
Click to expand...
Click to collapse
I know you can use other device as a master to serve some files but if the stock Samsung recovery doesn't allow updates this way then it is out of reach, but you should try it using ADB sideload not updates from external devices BUT only you could flash this way official updates not TWRP nor any custom zip, if you have some OTA update you should try it using an external SD Card if I don't remember bad your device has a slot for that.
Odin only can run in Windows PC, and its equivalent for Linux is Heimdall, there is not actually a version that completely support into Android.
Probably you could further investigate something like "Running Linux on Android devices", there were some Linux distros in Play Store that can boot, this way you could install Heimdall and get it a try using download mode, but this just theoretically, I didn't try it my self, fixing it through a PC sometimes is hard enough that not even think of this way.
SubwayChamp said:
I know you can use other device as a master to serve some files but if the stock Samsung recovery doesn't allow updates this way then it is out of reach, but you should try it using ADB sideload not updates from external devices BUT only you could flash this way official updates not TWRP nor any custom zip, if you have some OTA update you should try it using an external SD Card if I don't remember bad your device has a slot for that.
Odin only can run in Windows PC, and its equivalent for Linux is Heimdall, there is not actually a version that completely support into Android.
Probably you could further investigate something like "Running Linux on Android devices", there were some Linux distros in Play Store that can boot, this way you could install Heimdall and get it a try using download mode, but this just theoretically, I didn't try it my self, fixing it through a PC sometimes is hard enough that not even think of this way.
Click to expand...
Click to collapse
Nothing wrong at all with theory, as it forms the basis of every action. And I'm about to try that next. Check this out tho. That sideload thing that's entertwined with apply updates via adb. See I'll try to attach picture, but when in recovery i click apply updates via adb it asks to sideload files. That's the one way i can get the device to register . Abd even send files to the device. It's just that they don't install as it says updates from external sources is disabled. I feel you are correct tho, about Odin mode, i can put the phone in download mode but it just doesn't register on the otg apps, maybe because it must be Odin. So yeah i gotta find a way to run Odin on Android. Listen they do have a version of Odin that runs on Android , called mobile Odin...but i think it only flashes to the device that it's on....not to other devices....
ZiggyJapheth said:
Nothing wrong at all with theory, as it forms the basis of every action. And I'm about to try that next. Check this out tho. That sideload thing that's entertwined with apply updates via adb. See I'll try to attach picture, but when in recovery i click apply updates via adb it asks to sideload files.
Click to expand...
Click to collapse
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
ZiggyJapheth said:
That's the one way i can get the device to register . Abd even send files to the device. It's just that they don't install as it says updates from external sources is disabled. I feel you are correct tho, about Odin mode, i can put the phone in download mode but it just doesn't register on the otg apps, maybe because it must be Odin.
Click to expand...
Click to collapse
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
ZiggyJapheth said:
So yeah i gotta find a way to run Odin on Android. Listen they do have a version of Odin that runs on Android , called mobile Odin...but i think it only flashes to the device that it's on....not to other devices....
Click to expand...
Click to collapse
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
K
SubwayChamp said:
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
Click to expand...
Click to collapse
Ok, thanks so much,I'm about to download mobile Odin first , altho i think i tried that and it needed SuperSU permissions which the moto E5 isn't rooted...so looks like I'm about to research your other suggestions. It gives me a direction to experiment in. Again,thanks so much. Oh one last thing.. but it is sending files to the phone in sideload form. Because before it aborts, the phone I'm sending files from goes through a percentage until 100% of any given file is sent. And on the galaxy i see it received because it says installing this or that zip file before saying...updates fron external sources disabled and aborting mission. I'll be back. Thanks for the time bro
SubwayChamp said:
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
Click to expand...
Click to collapse
Hey everybody. I'm back from a long hiatus from rooting phones. I'm wanting to root my OP 8T, and adb is not seeing the phone when in recovery mode, so I can't even begin.
Win10, pretty sure drivers are up to date, adb up to date.
Computer and adb both see the phone when it's powered on normally, but I have to choose usb mode every time I plug it in. I suspect the adb not seeing it in recovery mode may have something to do with this, but I'm just guessing. I'm not sure how to overcome this. I know plenty of people have rooted this phone, so I don't get it.
Would be happy for any input on this issue. Idk where to go from here, and it's really frustrating, bc I'm excited to switch to this phone.
TIA
Have you tried checking Windows update when the phone is plugged in and in recovery mode? Do you have the Google fastboot drivers? Qualcomm drivers? OnePlus drivers? Are you using CMD or PowerShell for adb?
Zamkat said:
I'm wanting to root my OP 8T, and adb is not seeing the phone when in recovery mode, so I can't even begin.
Click to expand...
Click to collapse
yes, why should you? adb not available in recovery mode, expected behaviour.
Zamkat said:
I know plenty of people have rooted this phone, so I don't get it.
Click to expand...
Click to collapse
sure not from adb or recovery. did you mean fastboot? then boot phone into bootloader mode and install Android Bootloader Interface drivers.
alecxs said:
yes, why should you? adb not available in recovery mode, expected behaviour.
sure not from adb or recovery. did you mean fastboot? then boot phone into bootloader mode and install Android Bootloader Interface drivers.
Click to expand...
Click to collapse
It's been so long since I did this...I don't remember much about the procedure. I was just following the instructions. It said to turn it off, and then hold down and power to boot into fastboot mode. Then to connect it and type the reboot bootloader cmd.
I am using powershell.
These instructions aren't very good, I realize now. -_-
I guess I don't have the fastboot drivers...I'll try to get those and make another attempt. Thanks, I'll get back to you.
the driver is included in the same android_winusb.inf where the ADB driver is. you just need to disable windows driver signature enforcement before trying to install.
once you see device in 'fastboot devices' proceed with bootloader unlocking.
T-Mobile get Unlock Code to Submit to OnePlus for unlock token
This took me way too long to figure out so Hopefully this will make it quicker for someone: OnePlus Help Page Dr. Mario said: fastboot oem get_unlock_code (Found ten pages in at...
forum.xda-developers.com
Okay, well, this will make things difficult. Am I missing something here...???
Okay, hang on, I think I found the right instructions to install the sdkmanager... Ugh.
not sure what you are trying, but to run fastboot commands either navigate with cd into platform-tools directory from cmd.exe or in powershell type the path to file like this:
Code:
.\fastboot devices
Zamkat said:
Okay, hang on, I think I found the right instructions to install the sdkmanager... Ugh.
Click to expand...
Click to collapse
So, I followed these instructions exactly, and it's saying that sdkmanager is not a thing that exists.
Awesome. Super useful instructions. I never thought simply putting the tools needed to root my phone on my computer would be such a colossal pain in the ass.
I have never used sdkmanager and I don't know how that would involved in bootloader unlocking or rooting. It is also not mentioned anywhere in this device forum.
Zamkat said:
So, I followed these instructions exactly, and it's saying that sdkmanager is not a thing that exists.
Awesome. Super useful instructions. I never thought simply putting the tools needed to root my phone on my computer would be such a colossal pain in the ass.
Click to expand...
Click to collapse
Please go back to post #6. as we can see you're in folder "platform-tools" (left side of the cursor in your PowerShell window). This folder contains the files "adb.exe" and "fastboot.exe" and some more.
As a normal Windows user you would try to start these .exe files with a double click. Don't try it because it won't start anything. These .exe files are not executables, they are binaries. To run them you need to enter "adb" or "fastboot". That's all.
You need to use this: https://developer.android.com/studio/releases/platform-tools
And LineageOS have a great installation document: https://wiki.lineageos.org/adb_fastboot_guide
According to the instructions, I need to use the Sdk manager to install the fastboot drivers.
In order to get that, I apparently need the command line tools.
In order to get those enabled/installed in sdk, I need the Sdk manager...??? I'm so confused.
BillGoss said:
You need to use this: https://developer.android.com/studio/releases/platform-tools
And LineageOS have a great installation document: https://wiki.lineageos.org/adb_fastboot_guide
Click to expand...
Click to collapse
Holy ****, thank you.
Okay, I am in Fastboot mode, and I'm getting ready to install Twrp, but...it says my Device State is locked. Does that mean my bootloader is not unlocked? Because it is supposed to be.
alecxs said:
I have never used sdkmanager and I don't know how that would involved in bootloader unlocking or rooting.
Click to expand...
Click to collapse
The Platform Tools are part of the Android SDK. But Google offers them also as a single download, excluded from the Android SDK:
It's not wrong to install the whole SDK. But it's too much if only 2 binaries are being used.
how did you unlock the bootloader without fastboot?
alecxs said:
how did you unlock the bootloader without fastboot?
Click to expand...
Click to collapse
I'm an idiot. I need to do that still.
Device isn't being seen by adb in fastboot. Any suggestions?
Fyi, you shouldn't have posted the question in this forum but in the q&a forum https://forum.xda-developers.com/f/oneplus-8t-questions-answers.11583/
@BillGoss thread is moved soon, thx for reporting.
@Zamkat no device is seen by adb in fastboot.