Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
adb is not designed to be usable in bootloader mode. You need fastboot for that. If you have the fastboot.exe program in the same folder as your adb stuff, try this:
fastboot devices
If it reads, then all you need to do is fastboot flash the various .img files back to the tablet. There are tool kits that do this for you, but I prefer doing it manually as there are less chances of things messing up and if they do, you're more likely to know at what step which could be useful for further troubleshooting if need be. It is important to download the correct img files due to differences between the generations and wifi / data enabled ones. There is a flash-all script that you can find in the download of the factory images, which might make it easier, but you can just manually flash the separate files as sometimes you don't need to bother with them all (like the bootloader) though if the script works, then it'll be fine and might make it easier if you are not familiar with the commands.
If you don't have fastboot at all, just grab it from here: http://forum.xda-developers.com/showthread.php?t=2317790
Nexus img files: https://developers.google.com/android/nexus/images
Hit me up on Hangouts if you need more direction.
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
You won't get adb in bootloader mode.
You have to use the fastboot command.
Please tell the OS on your computer.
Use the tool in my signature as an environment.
Download 7zip, and install that.
Then go here and download the proper image for your device.
It would either be "Factory Images "nakasi" for Nexus 7 (Wi-Fi)" or "Factory Images "nakasig" for Nexus 7 (Mobile)".
Grab the 4.4.2 version.
Extract the downloaded file with 7zip into the "Work" folder in the tool form my signature.
Then extract that "nakasig-kot49h-factory-83d93b5f.tar" file with 7zip.
Then go into the folder that came out of that, and extract the "image-nakasig-kot49h.zip" into the Work folder.
And enter the following commands while in bootloader.
Code:
fastboot oem unlock
fastboot erase userdata
fastboot erase system
fastboot erase recovery
fastboot erase cache
cd nakasig-kot49h
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Make SURE you grab the correct image for your device. Wifi or Mobile.
I also assume that you know the .img files should be in the Work folder before you type thse commands into my tool.
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
NecroGi said:
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
Click to expand...
Click to collapse
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
https://code.google.com/p/adb-fastboot-install/
es0tericcha0s said:
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
Click to expand...
Click to collapse
It's actually working fine now (in the sense that the computer can now read it). The Virtual Machine also works just as good, but for some reason the toolkit I'm using won't properly return the tablet to the stock image using the SkipSoft Android ToolKit, so I'm going to have to try and find another way.
Thanks for your guys' help.
Welcome to my tutorial !
You can find others tutorials related to the Cube i6 :
Install windows 10
Install Android 4.4.4 (Stock & RemixOS)
I received the magnificent AllDoCube i6 Air 3G last week, and i've been struggling since to get updates,
firmware flashing and all of that working, I searched the whole web and the drivers/Firmwares are nowhere to find,
but on some chinese proxy-needed sites sometimes, or baidu which is a pain in the a** to download from.
So I decided to share the ways to update this tablet at all costs (heh, no worries, -NORMALLY- it wont brick)
Disclamer: This process might contain ROM hacking, this is for advanced users.
THIS TUTORIAL HAS BEEN TESTED ON i632GB1537XXXXXXX MODEL, AND WORKS ON IT,
WHEREAS IT HAS BEEN REPORTED THAT i632GB1522XXXXXXX MODEL BRICKED UPON DOING IT,
SO PLASE DO IT CAREFULLY, IF THE INSTALL VERSION IS 202 YOU SHOULD THINK ABOUT IT BEFORE TRIYING AS IT COULD BRICK!
Software included may be subject to copyright.
Flash your device at your own risk. Developer is not responsible for what you do on your device.
What you need:
Cube i6 Air (3G or Wifi)
Flash Drive (256Mo +)
OTG cable
USB Hub (3 Ports recommended)
EFI BIOS Firmware
DOWNLOAD THE FIRMWARE BEFORE STARTING SO EVERYTHING IS AVAILABLE WHEN YOU DO IT
https://drive.google.com/folderview?id=0B8YPw4HjmqNCZktOZy1OTEN2ZVE&usp=sharing
Get on the drive, go to your device folder, select the wanted version inside BIOS folder
What to do :
1.) Start by plugging the usb drive into your computer, and format it to FAT32 using any formatting tool
2.) Now you need to uncompress the downloaded firmware :
you will find a "Firmware_X.X.X" folder inside, take all of its content, and extract it to your freshly formatted drive.
here's what looks like the root of your usb:
3.) Your USB Drive is ready, now just plug the OTG cable to your tablet, plug your HUB onto that OTG
and fill it with your keyboard and the USB Drive just created.
4.) Press power button until you see the screen backlight, when you see it repeatidely smash "Esc" key on the connected keyboard.
You will see the bios 6 square configuration screen.
Hit "Boot Manager" and select your USB in the list.
5.) The tablet should now boot from your USB, booting to a UEFI Shell. Depending on your device, it might be either 64 or IA32.
Now you just let startup.nsh script do the firmware flashing init, it should drive you to a flashing BIOS screen.
6.) Follow instructions on screen and let the tool flash your BIOS automatically.
Once done, the tablet will shut down.
Congrats! You successfully updated your BIOS !
It is my first tutorial, i will post some photos of steps in the future so come back, the guide will be better soon !
Regards,
Max.
Hi,
I have bought the Cube i6 Air 3G a week ago and i'm still waiting for it to arrive.
Have you update the win 8.1 to win 10?
Does everything works correctly?
Regards
re
Hi, I successfully updated the BIOS as of now,
I changed the bootloader animation to nexus one on Cube ROM.
I also manager to boot on Android x86 but it had too many drivers issues.
Still, 4.4.4 stock cube is working and i reflashed to a new partition scheme of 9Go
and i'm currently testing some win10 pen drives for install, will keep you updated.
Édit: oh you were asking about thé tablet? Weil jack has default, charging takes hours, glass is plastic, firmware is pain but hell this is a goodamn good tablet for its price !
regards,
Max
stalker2106 said:
i'm currently testing some win10 pen drives for install, will keep you updated.
Click to expand...
Click to collapse
I achieved installing Win10 x32 Pro on Cube i6 Through hacking WinPE installation environnement, but now i'm struggling finding the drivers. touchscreen, battery and vital things like hd graphics are not working as of now. Will post a tutorial on how to install Win10 in given time when i'll get out of this mess!
My tablet has arrived yesterday.
From what the little i've used it, it has good performance especially in android.
A lot faster compared to my last android tablet (Cube U39GT).
Something i didn't like was the size of the icons and text in android, my next step is to root and change the dpi.
Regarding windows 10, i found in a chinese tablets blog with win 8 and 10 drivers.
I haven't tested it, but as soon as i find it again, i will let you know where to download them from.
You haven't tried the normal win 10 upgrade? From the microsoft icon?
gtbr said:
My tablet has arrived yesterday.
From what the little i've used it, it has good performance especially in android.
A lot faster compared to my last android tablet (Cube U39GT).
Something i didn't like was the size of the icons and text in android, my next step is to root and change the dpi.
Regarding windows 10, i found in a chinese tablets blog with win 8 and 10 drivers.
I haven't tested it, but as soon as i find it again, i will let you know where to download them from.
You haven't tried the normal win 10 upgrade? From the microsoft icon?
Click to expand...
Click to collapse
I did not try anything as i like "stock" versions of my windows, but tonight i got it working all the way !
My cube i6 is running perfectly windows 10 and oh my god what a paradise it is ! The tablet experience got way better onto that version.
Can you try to update from the icon you are talking about ? i'd be curious if it works. anyway, i'm currently writing+uploading for the win10
tutorial for this tablet, so you'll be able to flash it late tonight, or tomorrow.
EDIT: The dpi is correct in android, only the status bar icons and some other are not in correct dpi but that is KitKat issue I guess. still interested in resolving that though. I'm currently hacking android lollipop ROM also, i'll keep you tuned on that. For rooting, i used KingRoot, it worked, but after a reboot, it tells me "root" is wrecked, so i guess there is some investigation to do there, but I was mainly focused on getting windows 10 ENGLISH STOCK version running to share it with you guys.
EDIT2: Still uploading, but tutorial is here: http://forum.xda-developers.com/android/help/guide-how-to-install-windows-10-t3252042 and it should work on any Z37xx powered device. Enjoy !
Hello,
I'm using this tablet from 2 days now. great !
But, i got wifi problem after sleep : wifi chip cut and never found network anymore.
has to reboot, and all goes right.
same in win and android.
Did you hear about this ? many poeple complain about this.
Any trick or advice ? Is this bios correct this ? Is your bios work on i6 3g dual-boot ? (there is 2 bios for dual boot ?...)
Thanks !
Hi,
I've also have the same problem with the wifi.
I usualy disconnect the wifi and reconnect it, but sometimes it doesnt work and have to reboot the tablet.
I've not noticed it in windows but maybe it's because i'm using the tablet a lot more in android.
I've tryed to update to win 10 using the microsoft icon, but i got an error and was unable to complete the upgrade.
gtbr said:
Hi,
I've also have the same problem with the wifi.
I usualy disconnect the wifi and reconnect it, but sometimes it doesnt work and have to reboot the tablet.
I've not noticed it in windows but maybe it's because i'm using the tablet a lot more in android.
I've tryed to update to win 10 using the microsoft icon, but i got an error and was unable to complete the upgrade.
Click to expand...
Click to collapse
Hello, i have such a tablet for now about 6 Months and it is awesome so far (i often use win8.1).
My Tablet has also DUAL Boot with Android 4 and win 8.1 Bing.
I tried to upgrade to win10 but i also got a message that the partition can not be resized by windows. So i cant upgrade to win 10 with the normal tool from microsoft.
Is there any Solution yet to get this to work?
Anyway, i tried to boot from usb (win8.1 / ubuntu / gparted) but it is not working at all. When i try to boot true windows Advanced Boot Options, the BIOS says that there is no USB device.
When i use the EFI Shell to mount the USB Stick i can see that the BIOS has recognized the USB Stick.
I think that is all very strange, but i will try to update the BIOS soon. The serialnumber is not the same as from @stalker2106 but i will try it.
I hope there is a way to get win 10 working, but Ubuntu would be even better for performance.
Greetings from Germany.
tysonpower said:
Hello, i have such a tablet for now about 6 Months and it is awesome so far (i often use win8.1).
My Tablet has also DUAL Boot with Android 4 and win 8.1 Bing.
I tried to upgrade to win10 but i also got a message that the partition can not be resized by windows. So i cant upgrade to win 10 with the normal tool from microsoft.
Is there any Solution yet to get this to work?
Anyway, i tried to boot from usb (win8.1 / ubuntu / gparted) but it is not working at all. When i try to boot true windows Advanced Boot Options, the BIOS says that there is no USB device.
When i use the EFI Shell to mount the USB Stick i can see that the BIOS has recognized the USB Stick.
I think that is all very strange, but i will try to update the BIOS soon. The serialnumber is not the same as from @stalker2106 but i will try it.
I hope there is a way to get win 10 working, but Ubuntu would be even better for performance.
Greetings from Germany.
Click to expand...
Click to collapse
Check windows 10 Post, there is no need to update BIOS to fix this error, your USB has to be in GPT partition style, check answer on the other thread
But usually the bios update should work, as it did on my tablet. But why bother taking risk if you can get it working without it
Hi,
I have sucessfully updated to win10
I have bios 203 in my cube and serial i632gb1510xxxxxxxxxxx, does anybody have tried to update to 206 on such setup ?
What are the chances that I will brick my device ?
I have downloaded latest Cube i6 roms from cube site (may 2015) . There are two bios-es which have to be installed in chronological order.
Shall I do it first, and then try to update to 206 ?
Edit: I was not patient and tried it on my own.I have successfully updated bios and tablet has started to both android and windows
I will perform some functional tests afterwards.
Actual steps :
I have first downgraded bios to 201(provided here )
Flashed bios1 from link provided
Flashed bios2 from link provided
Flashed bios 206 from guide in first post
Edit2:
I have tested basic functionalities like : Gyro-sensors, WIFI, GPS, 3G network and yet everything works like charm.
Maybe a placebo, however I have the feel that android runs like two times faster
I do suggest to update the windows, however I take no responsibility if you will brick your device. Even if the setup is like mine, neither if it differs
Regards
Why do you first downgrade to 201?
What do you mean with bios1 and bios2?
Many thanks and question
Hello Stalker,
I am new here and i want to
thank you for the instructions!
I bought a cube i6 from china.
It is the 'i6 air remix',
So it should have only Android on it.
When it arrived. it didn't function.
The only think that happens is booting to theEFI-shell.
I could switch between Android and Windows in the boot settings.
But Android did not boot.
I have updated the bios with your instructions
now firmware 2.0.6 is installed.
But still i can not boot Android.
I found a few flash tools and android for the cube i6 .
But i don’t know what is the right version flash tool I have to use.
Maybe you have advise or the right android and flash tool in your google drive download area?
Kind regards and many thanks in advance.
jan-netherlands said:
Hello Stalker,
I am new here and i want to
thank you for the instructions!
I bought a cube i6 from china.
It is the 'i6 air remix',
So it should have only Android on it.
When it arrived. it didn't function.
The only think that happens is booting to theEFI-shell.
I could switch between Android and Windows in the boot settings.
But Android did not boot.
I have updated the bios with your instructions
now firmware 2.0.6 is installed.
But still i can not boot Android.
I found a few flash tools and android for the cube i6 .
But i don’t know what is the right version flash tool I have to use.
Maybe you have advise or the right android and flash tool in your google drive download area?
Kind regards and many thanks in advance.
Click to expand...
Click to collapse
The truth is, the 206 BIOS provided is hacked off i6 remix repository from cube, so i guess there is no big deal flashing it on your device as it works on regular i6.
Moreover, you can use any version of the flash tool as long as you flash a correct rom for your device, which i would suggest to download from official cube repository or geekbuying or so.
Android Geecbuying
Hello Stalker,
Ok. Thank you!
I will try Geecbuying.
Hopefully the windows drivers will function.
There isn't a way to flash from USB I suppose?
Greetings
Hi, well, actually, you should flash over USB with à windows computer. MFT by Intel is recommended. I shall make some tutorial about Android installation and partition resizing.
flash and resize partitions
That is super. When you want to do so.
I was indeed wondering or there would be one android partition on the tablet or two partitions (one for android, one for windows).
I also questioned myself how to see that there are partitions.
In earlier times when I was working with a pc, i use F-disk or partition-magic for this kind of work.
But on the tablet I do not have a clue...
So if you could make me wiser on this, I would be very thankful.
Maybe you could boot on some gparted liveusb? Or inside efi shell some commands could help
bluefish007 said:
Why do you first downgrade to 201?
What do you mean with bios1 and bios2?
Click to expand...
Click to collapse
no particular reason, I just wanted to know, which version of bios is in the latest firmware provided by geekbuying
Additional condition in my decision mechanism was that my serial did not match mentioned ones in w10 thread from stalker, so somehow I have used sleepy sloopy logic and tried to minimalize the risk (I know it have no rational reason and logic behind it at all)
Therefore, I tried the ones from geekbuying repository, to be sure to have latest provided from "official source".
greetings
thermoska said:
no particular reason, I just wanted to know, which version of bios is in the latest firmware provided by geekbuying
Additional condition in my decision mechanism was that my serial did not match mentioned ones in w10 thread from stalker, so somehow I have used sleepy sloopy logic and tried to minimalize the risk (I know it have no rational reason and logic behind it at all)
Therefore, I tried the ones from geekbuying repository, to be sure to have latest provided from "official source".
greetings
Click to expand...
Click to collapse
Ok thanks for the answer! So i can upgrade from 203 at 206 at one part or what do you think?
Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
H4ck3rz said:
Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
Click to expand...
Click to collapse
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Update: I decided I to work on this last night and from the beginning I had problems. TL;DR - adb and fastboot are already part of the developer mode system on my Chromebook Plus. So the need to follow those guides isn't necessary for me.
I was not, however, able to do anything to my Nexus 6 from my Chromebook. Since the Plus only has USB Type-C ports, I bought a USB Type-C to Micro USB cord, but the Nexus wasn't being recognized properly. adb devices returned "????????????" devices, and I didn't get anything with fastboot. I can only surmise that it is the cord, because on my windows laptop, adb and fastboot work flawlessly while my Nexus 6 was connected with the included sync cable.
I'll post again if have more info to share. Sorry I couldn't be of more help.
Rk
rkwarner2 said:
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Click to expand...
Click to collapse
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
i3uu said:
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
Click to expand...
Click to collapse
can you please help me. when I enter 'sudo adb devices' the device is seen. but it says unauthorized. Can you help me with a a step by step write up. I want to flash Android P on to my Pixel 2 XL.
Thanks
This Oneplus X seems to be more difficult than my previous attempts for installing TWRP and custom ROM. I keep getting stuck and nothing returning once in fastboot and executing command "fastboot devices". I just keep getting "< waiting for device >" .
I think I have ADB installed right because while the Oneplus X is on and in normal mode (developer settings enabled with OEM unlocking and USB debugging enabled also) ADB connects. The USB drivers look to work fine because I can see the device (including SD card storage) and transfer files. in ADB and typing in ADB devices, I see the device.
When I run adb reboot bootloader and execute fastboot devices using command.com with administrator privilege, it just returns another prompt. It doens't show any device. I get the same results with Powershell with administrator privelge.
I'm already on my 2nd machine trying to do this although it's a windows 10 also just w/o updates for six months (was off and on the side of office). I had the same issues on my newer machine and thought it's the windows 10 machine I'm using. Researching the internet and here, I see others mention it though I didn't see any solution. I don't have a Linux machine (never really used it though had redhat installed eons ago somewhere). I guess I can do a refresh of my 2nd/older machine and not do any updates to see if that may help with any driver conflict though I don't see any indicators since adb can see the device. I thought trying to install TWRP via sideloader may work but I don't see tutorials and commands via that way.
Also I'm using ADB 1.4.3 in the 2nd windows machine. I had the Minimal ADB and Fastboot version on the other machine.
Anything else I can try?
P.S. The Onyx seems to be harder than putting android on my old HP touchpad! Putting a Tmobile rom on a AT&T Galaxy S4 and custom rom on a Oneplus 2 seemed much easier than the Onyx though unsure why. Onyx and the Oneplus 2 were comparable manufacturing years iirc.
On the 2nd machine, i did a windows 10 reset to basically refresh it (like a fresh install). I started over again and managed to get past the fastboot device problem and it's showing it now. I think the prior problem was the device and driver and even with a re-install, can't seem to get past it. The only difference I did with ADB install was not opting to install google drivers.
I got the bootloader unlocked and the recovery.img file done. Basically I'm following the direction from this page - https://www.technobuzz.net/root-oneplus-x-install-twrp-recovery/ - which seems to be aligned with most youtube and I think same as old pages here.
Now where I'm stuck is when executing "fastboot boot recovery.img" I get the failed (remote : dtb not found) and can't seem to find a solution to this one. Some sites say something about the partition?
Thoughts? hopefully this machine is not too old/dead for some comments/guidance unless I'm posting on the wrong section.
well to share back here and for closure.. looks like the recovery image i used on the site above must be for a different OOS. doing some further searches here and different terms and jumping to another thread from a search result thread (lol), i read that i needed a specific twrp for oos 3.1.4. (odd since recovery is supposed to be independent of ROM version, but that seemed to have work). guess persistence pays after all.
it really did heavily matter having the device recognized properly by windows 10. once i got past the blank fastboot device command execution, i got the another issue due to the phone not knowing how to boot into the recovery version i was trying to install, at least that's how another poster in another thread explained it. hence the right twrp had to be used for oos 3.1.4