I been trying for days to get my HTC Flyer with Honeycomb rooted via the GUIDE but I am stuck at step 1.
"If you are not on an appropriate gingerbread version, eg. if you have upgraded to honeycomb then downgrade by using an appropriate RUU; to identify your RUU see: here"
(downgrade to Gingerbread) but I get stuck at the "Fastboot getvar cid" stage to find out which RUU I have. When I have the Flyer in Fastboot mode and connect the cable, I get an error when it trys to install the "Android 1.0" driver.
I have uninstalled, rebooted, reinstalled, repeatedly. I just tried another link that suggested to try installing PDANet for Android to get around this problem. Now when I run Fastboot, rather than just "waiting for connection", I get an error that says "getvar:cid FAILED (status malformed (1 bytes)) finished.
*** Update***
I just tried a different HP Laptop with Windows 7 installed & I had the exact same error regarding the Android 1.0 driver as soon as I plugged in the Flyer when it was in Fastboot mode. Is there some other setting other than Fastboot off I need to do on the Flyer itself? Any other suggestions would be GREATLY appreciated.
Please help!! I am at my wits end here.
thanks,
sPk
still need help
I am still struggling here.
By pointing the Android 1.0 driver installer to the PDANet directory, it found a ADB driver and installed it. But I still get the "malformed error" when I try to use "Fastboot getvar cid" command to find RUU version. Is there another way to get the RUU version??
I think the driver is communicating with the Flyer as I was able to get Flyer to respond to the serialno command.
I have OTA update and want to root/Rom with HBoot 1.11.00011.
If I can't get the RUU version, is there a most likely suspected RUU for a WiFi only Flyer that I just got from Buy.com for US market.
thanks in advance for your help.
sPk
You have the android sdk installed right?
Andriod SDK
Gumby63 said:
You have the android sdk installed right?
Click to expand...
Click to collapse
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
windsurfsail said:
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
Click to expand...
Click to collapse
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
SDK
Gumby63 said:
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
Click to expand...
Click to collapse
I was able to get the Android SDK & Java installed properly. I uninstalled the driver in the Device Manager and then pointed the driver install to Android SDK/Tools and it indicated that the driver was already installed. I tried Fastboot command for the zilllionth time and still got the same malformed error. So I uninstalled driver & deleted it this time and tried to re-install but now it doesn't find the driver files (because I deleted them). I can re-install SDK or just point it to the PDANet directory again.
Is the correct driver for Fastboot the the Android ADB? It is the only one I have been able to get to load when I plug in the Flyer in Fastboot mode.
thanks,
sPk
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
hboot & fastboot confusion
globatron said:
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
Click to expand...
Click to collapse
DOH!
Globatron, thanks for the clarification. In all my reading of threads, I never saw any definition of hboot & fastboot. Since it wasn't working, I installed the other drivers in an effort to fix what was apparently a driver issue.
Is "fastboot mode" just having the "Fast boot" box checked under the Power settings?
thanks again!
sPk
Fastboot mode
After searching in the forums for a while, I found a description on how to get into "fastboot mode". I have added below in case someone else is new enough not to know.
I ran the command & it finally worked. Being in the right mode was key.
sooo, I now have the cidnum= BS_US001 but looking through the list of the RUU's files, I still don't see any reference to this CID. Another stupid question: How do I find which of the list of 25 RUU files is correct for my WiFi Flyer?
UPDATE: Found out how to find RUU file from link.
http://forum.xda-developers.com/showpost.php?p=18508220&postcount=2
modelid: PG4140000 (Wifi Flyer)
RUU_Flyer_BrightstarUS_WWE_X.XX.1540.XX
cidnum: BS_US001
cidnum: HTC__055
sPk
----------------------------------------------------------
You need to be in fastboot mode. Two ways to get there.
Get into boot then select fastboot
Or
While booted in android connect to PC then enter "adb reboot bootloader" (assuming you know adb a little)
Once in fastboot you need to enter the commands in a cmd terminal on your PC just like adb
What I learned, that may help you...
I had a surprisingly difficult time getting my OTA Honeycomb US WiFi Flyer S-Off'ed, Rooted & uploading a new ROM. I did get it done but there were some basic things I should have known or done. Thanks to Globatron & all who post on this board.
1: Before you start, make sure your PC's drivers are 100% working. I had Windows driver problems that caused other problems. Make sure that your tablet is properly recognized by the PC when the tablet is in Fastboot/Hboot modes, and in regular Android mode.
2: I didn't understand the difference between Hboot & Fastboot. This small thing made all the difference and was one of my major issues. Because I had the tablet in Hboot not Fastboot, the Fastboot commands didn't work and I couldn't get my RUU version
3: Pay attention to the phone's settings. Especially USB Debug mode, Fastboot mode.
4: After I had finally downgraded to Gingerbread. I couldn't figure out why Revolutionary wouldn't recognize my tablet. The simple answer was when I had downgraded to Gingerbread, all my phone settings were back to stock also so I had go in and change the USB Debug and Fastboot modes. It would be helpful to add a reminder in the GUIDE to make sure that these settings are changed before running Revolutionary.
5: Not really related but I had a problem when I wanted to backup my newly Rooted/ROM'ed phone. I had previously purchased the Titanium Backup Pro and I installed it on the Flyer but it wasn't listed in the Apps menu but was listed in the Manage Apps. Because Google-Play/Android Marketplace only copied over the paid apps to my newly upgraded Flyer, it didn't copy the free version of Titanium Backup. You must load both the free version & the paid Pro version for it to work.
I hope this helps someone who runs into any of the same issues I had.
thanks,
sPk
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
markbencze said:
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
Click to expand...
Click to collapse
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
wbexpress said:
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
Click to expand...
Click to collapse
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
markbencze said:
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Click to expand...
Click to collapse
Sure. Usually I am able to get into the bootloader(if adb devices recognized what's going on) where I get the LG logo and the words on the top left say "Welcome to Fastboot Mode". I put in adb reboot bootloader, which does get me there. Then, I put in fastboot oem unlock and that's when it hangs on waiting for device.
dillonorden said:
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
Click to expand...
Click to collapse
Exactly. I guess the "misery loves company" thing is operative here. If you do figure it out, PM me, I will do the same.
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
markbencze said:
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
Click to expand...
Click to collapse
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
wbexpress said:
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
Click to expand...
Click to collapse
Just follow the instructions in the "how to root..." thread. it goes step by step and I believe there is a video tutorial as well. You'll need to do a quick search for this.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
wbexpress said:
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
Click to expand...
Click to collapse
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
jkyoho said:
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
Click to expand...
Click to collapse
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
wbexpress said:
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
Click to expand...
Click to collapse
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Lorddyyy ive been trying this crap all day i have the same driver issue but it won't let me select the one i want it just says there are no drivers available in this folder! GRRRRR
---------- Post added at 08:37 PM ---------- Previous post was at 08:00 PM ----------
omg i think i got it! http://forum.xda-developers.com/lg-v10/help/phone-adb-fastboot-t3247732 went here and did what duece said above but choose choose from a list!> then i hit select all devices> the box said populating but i just clicked install from disk and changed it to the unzipped file folder that had the driver in it until i found this file android_winusb and selected it!> then low abd behold the box populated with the driver info and it became a samsung adb device! finalllyyyyyy!!!!!!!!!!! i'm so happy Ive been trying to root this damn thing all day!
jkyoho said:
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
Click to expand...
Click to collapse
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
wbexpress said:
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
Click to expand...
Click to collapse
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
jkyoho said:
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
Click to expand...
Click to collapse
Positive. The code I am putting in is twrp-2.8.7.1-h901.img. That's what most things I've read say to do. The other thing I have been thinking about is that KlicKit is supposed to have everything pre-loaded, and even it won't do it. KlicKit gets me into fastboot, then something really quick happens and the command prompt screen closes. What driver system do you use? I've installed a number of them, then deleted them as well, just to try to make sure there are no conflicts. However, I now have two devices in device manager: "android device.lge mobile adb interface" and "portable devices/v10. Does one need to go, maybe?
Power off your phone , hold volumn down and connect usb to PC.
Do you see "LOCK STATE - UNLOCKED" ?
if yes, type "fastboot.exe flash recovery twrp-2.8.7.1-h901.img "
Hi,
I've been trying to follow instructions to flash Lineage OS* on my Samsung Galaxy S3 (i9300) currently running Android 4.3. Would appreciate any help.
I followed the Lineage wiki tutorial to download platform tools (ADB and fastboot).
I'm following detailed instructions from how-to-geek [link removed], as the ones on getdroidtips seem garbled. I've downloaded all of the relevant software to my PC, except for SU, and I have enabled developer mode and USB debugging.
Running the adb devices command shows my phone as a device, but when i try 'fastboot oem unlock', fastboot doesn't work at all. Initially fastboot wasn't recognised as a command, as Windows virus blocker prevented the fastboot.exe from being unzipped, so i manually moved that file over. Now the command prompt just says 'waiting for device' forever.
Any ideas?
Thanks
Hello
Hello there, You don't need to unlock the bootloader as this model is already unlocked. The SHV-E210S has to be unlocked. So you just need to flash Chainfires SuperSU through Odin and install custom recovery.
https://forum.xda-developers.com/ga...2012-cf-root-6-4-supersu-cwm5-5-t1695238/amp/
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!
Once I reboot to bootloader and connect to PC, the command "fastboot devices" does not recognize the device, so when I try to unlock it. it says "waiting for device". I've enabled both OEM unlocking and USB debugging.
The phone shows "fastboot_unlock_verify ok"
"The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously. "
EDIT: Solved it by using the correct platform-tools
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
7tyjupiter said:
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
Click to expand...
Click to collapse
I used the ones from here - https://www.getdroidtips.com/download-adb/#How-to-Install-Android-SDK-and-Platform-Tools
Solved.
I downloaded the platform tools 30.0.5 and reinstall it. Then i reinstall the adb bootloader driver right at the moment when the Nord2 is in the fastboot mode.
cheers
I have no developer options for reboot, bootloader, recovery.
platform tools 30.0.5, where?
Try after reboot into bootloader "fastboot devices". Is the Nord 2 recognized?
For me the correct command was "fastboot flashing unlock".
Hier is the link for the Platform tools 30.0.5
adb - platform tools v30.0.5.zip | by abdyasar for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
F4t16u3 said:
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
Click to expand...
Click to collapse
Mine does not show up.... -.-