Last time I checked it was a chore to unlock the bootloader is that still the case these days? Its why I haven't yet done it on my HDX 8.9" running 14.3.2.4_user_324002120
Montisaquadeis said:
Last time I checked it was a chore to unlock the bootloader is that still the case these days? Its why I haven't yet done it on my HDX 8.9" running 14.3.2.4_user_324002120
Click to expand...
Click to collapse
Wow - that's an old build! If you have used adb, have a host PC or laptop, can install device drivers and are comfortable following directions unlocking is relatively easy. At present the task remains a largely manual affair. However, the rewards are rich with a nice suite of custom ROMs including several Nougat based options. It will be like having a new device!
I have both a laptop and desktop both are running Windows 10
Montisaquadeis said:
I have both a laptop and desktop both are running Windows 10
Click to expand...
Click to collapse
Assume the device is rooted given OTA updates appear blocked. If accurate read and execute step #2 only (skip #1) from this post. The links in that post are dead; you can download the files from here. Be sure to grab the Apollo variants of both files. Life gets ugly fast if you run with the Thor variants.
The above procedure will NOT unlock the bootloader but will put into place the necessary prerequisites for doing so.
Davey126 said:
Assume the device is rooted given OTA updates appear blocked. If accurate read and execute step #2 only (skip #1) from this post. The links in that post are dead; you can download the files from here. Be sure to grab the Apollo variants of both files. Life gets ugly fast if you run with the Thor variants.
The above procedure will NOT unlock the bootloader but will put into place the necessary prerequisites for doing so.
Click to expand...
Click to collapse
The thread on TWRP says it requires an unlocked bootloader. So wouldn't that cause issues since I am NOT unlocked yet?
Montisaquadeis said:
The thread on TWRP says it requires an unlocked bootloader. So wouldn't that cause issues since I am NOT unlocked yet?
Click to expand...
Click to collapse
Nope - TWRP can be flashed on a locked device with a vulnerable bootloader. Having access to a custom recovery can be a huge benefit should something go wrong during subsequent steps.
I understand why the OP included that caveat. Makes sense if you don't have someone guiding you through the unlock procedure.
Davey126 said:
Nope - TWRP can be flashed on a locked device with a vulnerable bootloader. Having access to a custom recovery can be a huge benefit should something go wrong during subsequent steps.
I understand why the OP included that caveat. Makes sense if you don't have someone guiding you through the unlock procedure.
Click to expand...
Click to collapse
Hows the 1-click bootloader unlock working these days?
AKA
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
It was linked to in the post you linked to.
Ok so far I have done both TWRP which is indeed working and aboot and that is it.
Montisaquadeis said:
Hows the 1-click bootloader unlock working these days?
AKA
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
It was linked to in the post you linked to.
Ok so far I have done both TWRP which is indeed working and aboot and that is it.
Click to expand...
Click to collapse
Congrats! You have gotten through the riskiest part of unlocking the bootloader. From this point forward there is little you can do to hurt your HDX aside from sustained contact with a blow torch or direct engagement with an A1 Abrams battle tank (bit of an overreach but you get the point).
Unfortunately, 1-Click is still not ready for prime time. The author has the best of intentions but a severe lack of bandwidth to complete.
That said, manual unlocking is relatively easy:
1) Download/install this package on one of your Windows machines which scores drivers that have proven reliable with every HDX device I (and others) have encountered. Yep, seems illogical but it works better than all of the other alternatives (drivers) that have been bounced around for the past 4 years. You can remove the package after unlocking your device.
2) Install Minimal ADB and Fastboot (here) on the same machine
3) Verify you can launch the ADB/Fastboot command window via the icon that should have been added to your Windows desktop.
4) Boot into TWRP and tether your device using a reliable USB cable. You should receive some audible/visual feedback from Windows that it recognizes the device.
5) Launch the minimal ADB/Fastboot window, type "adb devices" and press <return>. Response should be the device identifier followed by the word 'device'. If successful type "adb reboot bootloader" followed by <return>. After a few moments the device will boot into fastboot. Type "fastboot devices" and press <return>. If successful response should be similar that noted above. Finally, type "fastboot reboot" to boot into FireOS. If any of the previous commands fail simply untether and long press power button (8-20 sec) to turn off your device. It can then be restarted in the usual fashion.
If you have difficulty with any of the items in step #5 please detail your observations and I will help you through remedial steps. Otherwise, bounce back and we will go through the remaining few steps to complete the unlock process.
Sorry for parceling this out in small chunks. Experience has taught this is the best approach rather than penning a long novel in a single post.
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is what came up when I went to do adb reboot bootloader.
Montisaquadeis said:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is what came up when I went to do adb reboot bootloader.
Click to expand...
Click to collapse
Hum - something seems wrong. That command should not have failed if the previous "adb devices" returned the expected response. Let's take a different approach to the fastboot connectivity test:
- untether device
- boot into TWRP
- tap 'reboot' followed by 'bootloader'
- you may be prompted for a confirmation swipe; go ahead and do that
You should now see a gray "Kindle fire" logo followed by the word "fastboot" in brackets. Retether device; hopefully a ready prompt will appear. If so continue with fastboot connectivity test as documented in previous post.
If a ready prompt does not appear or the test fails you'll need to use Windows device manager to identify your device and update the device driver to "Mot Composite ADB Interface". This can be a tedious process if you haven't gone through it before. Bounce back if you need assistance.
Ok fastboot devices is not bringing anything up so it doesn't seem to have worked.
Oh in Device Manager its coming up as Kindle Fire HDX under both Universal Serial Bus devices and Portable Devices.
basically
adb devices brings up the device id but it says unautherized to the right of the id.
Montisaquadeis said:
Ok fastboot devices is not bringing anything up so it doesn't seem to have worked.
Oh in Device Manager its coming up as Kindle Fire HDX under both Universal Serial Bus devices and Portable Devices.
basically
adb devices brings up the device id but it says unautherized to the right of the id.
Click to expand...
Click to collapse
Boot into FireOS, tether and respond to any prompts. Hopefully one asks you to approve the connection to your Windows box (be sure to check the 'always' box if presented). Then repeat adb connectivity test.
Note: You may have to enable adb under developer options in settings. Might find this article helpful (found it on a quick Google search; haven't verified contents but seems to be ok; I haven't used FireOS v4 in a couple years).
Note #2: I'm happy to keep going but don't want to you to feel obligated/stressed by the barriers being thrown up. Feel free to bail at any time.
Davey126 said:
Boot into FireOS, tether and respond to any prompts. Hopefully one asks you to approve the connection to your Windows box (be sure to check the 'always' box if presented). Then repeat adb connectivity test.
Note: You may have to enable adb under developer options in settings. Might find this article helpful (found it on a quick Google search; haven't verified contents but seems to be ok; I haven't used FireOS v4 in a couple years).
Note #2: I'm happy to keep going but don't want to you to feel obligated/stressed by the barriers being thrown up. Feel free to bail at any time.
Click to expand...
Click to collapse
Ok FireOS comes up with device next to the id while TWRP says unautherized so I have no idea what is going on here personally.
Montisaquadeis said:
Ok FireOS comes up with device next to the id while TWRP says unautherized so I have no idea what is going on here personally.
Click to expand...
Click to collapse
Not going to worry about it now as it doesn't reflect an immediate barrier. You have established/verified ADB communications (good!) but still need to verify fastboot communication.
Path forward:
- Boot back into TWRP and then reboot to the bootloader/fastboot (there are more direct methods but the TWRP->Fastboot two step is the easiest for now). As before there should be a 'fastboot' in brackets but no 'ready' prompt.
- Tether device; if ready appears you're good! More likely nothing will happen. At that point you need to launch Windows device manager and change the device driver used to communicate with the HDX as detailed in a previous post. In short, locate the device (most likely shown with a yellow explanation mark); right click -> update driver; select 'Browse my computer...'; select 'Let me pick...'; locate and select 'Mot Composite ADB Interface'. If you still do not get a ready prompt after performing the above repeat the first two steps until device is retethered. Hopefully that will do it.
- Once you have a ready prompt issue the command 'Fastboot devices' to verify fastboot communications are possible. Then reboot your device.
I realize the above seems kludgy and obviously frustrating. It is without a doubt the most difficult part of unlocking the device. Once fastboot communications have been verified it's all down hill.
Davey126 said:
Not going to worry about it now as it doesn't reflect an immediate barrier. You have established/verified ADB communications (good!) but still need to verify fastboot communication.
Path forward:
- Boot back into TWRP and then reboot to the bootloader/fastboot (there are more direct methods but the TWRP->Fastboot two step is the easiest for now). As before there should be a 'fastboot' in brackets but no 'ready' prompt.
- Tether device; if ready appears you're good! More likely nothing will happen. At that point you need to launch Windows device manager and change the device driver used to communicate with the HDX as detailed in a previous post. In short, locate the device (most likely shown with a yellow explanation mark); right click -> update driver; select 'Browse my computer...'; select 'Let me pick...'; locate and select 'Mot Composite ADB Interface'. If you still do not get a ready prompt after performing the above repeat the first two steps until device is retethered. Hopefully that will do it.
- Once you have a ready prompt issue the command 'Fastboot devices' to verify fastboot communications are possible. Then reboot your device.
I realize the above seems kludgy and obviously frustrating. It is without a doubt the most difficult part of unlocking the device. Once fastboot communications have been verified it's all down hill.
Click to expand...
Click to collapse
As I said Kindle Fire HDX is listed TWICE in Device Manager when tryinng to do the fastboot. Its listed under both Portable Devices and Universal Serial Bus devices and neither have a yellow exclamation mark so I havw no clue which one to change over to the other driver. Ontop of that its 11pm here so I will check back tomorrow.
Montisaquadeis said:
As I said Kindle Fire HDX is listed TWICE in Device Manager when tryinng to do the fastboot. Its listed under both Portable Devices and Universal Serial Bus devices and neither have a yellow exclamation mark so I havw no clue which one to change over to the other driver. Ontop of that its 11pm here so I will check back tomorrow.
Click to expand...
Click to collapse
You want to work the entry listed under Portable Devices. I'm in the same timezone; also winding down for the evening.
Hi Davey, I'm responding in this thread as you requested yesterday.
Before I start trying to install TWRP, does it matter that I have Safestrap currently installed? Or should it be removed first? @Yousucks2 said the following in my other thread:
"But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device"
Also, I am running a custom Rom of kindle fire for thor. I was on kit Kat 4.4 but felt like trying out Amazon again. Not sure if that matters at all in this process.
leeismyname said:
Hi Davey, I'm responding in this thread as you requested yesterday.
Before I start trying to install TWRP, does it matter that I have Safestrap currently installed? Or should it be removed first? @Yousucks2 said the following in my other thread:
"But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device"
Also, I am running a custom Rom of kindle fire for thor. I was on kit Kat 4.4 but felt like trying out Amazon again. Not sure if that matters at all in this process.
Click to expand...
Click to collapse
Reasonable questions; responses:
- SafeStrap v4 and TWRP can coexist on the same device; no need to uninstall the former which is not a true recovery (it lives in the system partition and will be wiped out when you install a custom ROM)
- No issue running FireOS while navigating the bootloader unlock procedure
As previously noted be sure to use the Thor builds on your HDX 7. Recovering from an inadvertent Apollo flash make passing a kidney stone look appealing.
Ok I have changed the driver over to MOT composite ADB device V2 since I had 2 listed aka Version 2 and version 1.3. I now have the ready prompt and when I do fastboot devices I get the device id and fastboot to the right. So I tlooks like I am good to go with fastboot now
Montisaquadeis said:
Ok I have changed the driver over to MOT composite ADB device V2 since I had 2 listed aka Version 2 and version 1.3. I now have the ready prompt and when I do fastboot devices I get the device id and fastboot to the right. So I tlooks like I am good to go with fastboot now
Click to expand...
Click to collapse
Excellent! Next steps:
- Complete the 3rd bullet in the prerequisite section of this post. Pay careful attention to where the extracted batch file resides; move as needed. Most likely the directory will be "C:\Program Files (x86)\Minimal ADB and Fastboot" but you will need to confirm. Obviously referring to the Win 10 box.
- Perform steps #1 and #3 in the "Code generation and unlock" section. When complete it is quite possible the bootloader will be fully unlocked. However, if the procedure stalls we will have to take one more (easy) step to complete the procedure.
IMPORTANT: Step 2 in the "Code generation and unlock" section has already been performed (as directed earlier in this thread)! No need to repeat as this is the riskiest part of the unlock procedure.
Bounce back when complete. There are a couple clean-up steps that should be done before flashing a custom ROM. I can also provide guidance on which ROM to install if you don't already have one in mind.
Related
I hope this is useful information. It took me a bit to figure it out due to a lot of conflicting information, since the procedure has changed, perhaps several times, since the first version of Android. Also, I'll probably forget myself.
Please note that I've performed these steps on Linux (Specifically Arch Linux). Others have pointed out that if you have issues executing step 7 from Windows, you may need to follow this post.
1. Install Android Studio, or otherwise obtain the latest versions of the adb and fastboot programs. I think Windows users also need to install a USB driver, but I run Linux, so I am not sure about that procedure.
2. Gain access to the developer options on the tablet. Go to the settings, and find the "about tablet" section. Scroll down to the "Software version" section and tap on that several times until it says that you are now a developer. Feel special.
3. Go to the new "Developer options" setting. Select "OEM unlocking." Also, I selected "USB debugging" as a straightforward way to reboot into the boot loader.
4. Connect to the computer on which you've installed adb and fastboot.
5. Type 'adb devices' to see your device listed. The tablet will ask you if you're sure you want to allow the computer access to it. Answer in the affirmative, and save that option.
6. Type 'adb reboot-bootloader' to do just that.
7. After you see the innards of your 'droid, type 'fastboot flashing unlock' . On Linux, you may need root permissions to do this. The tablet will ask you to confirm (select with up/down volume, and accept with the power button), and will then erase all of your data! I didn't worry about this as I'm all on Google services, and so they can be restored easily enough.
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Click to expand...
Click to collapse
you are then able to flash another (custom) recovery, which would let you install unsigned zip-files, e.g. in order to get root.
Unfortunately, there is no recovery port by now.
I don't know if one could use the source code on Lenovo's website to port one, if not we would probably need an image dump directly from the device (if I'm not mistaken you need root to dump the recovery image).
I really would like to have root, but it still seems far away unless there's an experienced developer somewhere who owns the device.
I've already thought of starting a bounty thread...maybe enough people are willing to contribute so that developers might feel attracted.
Hello,
Do you think it would be possible to install Windows 10 on our android yoga book?
Thanks,
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
AndyVerne said:
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
Click to expand...
Click to collapse
can you tell me how to deal with it? I met the same problem.
Vsplorer said:
can you tell me how to deal with it? I met the same problem.
Click to expand...
Click to collapse
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
AndyVerne said:
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
Click to expand...
Click to collapse
can you tell me where to download the exe？ thanks a lot！
Vsplorer said:
can you tell me where to download the exe？ thanks a lot！
Click to expand...
Click to collapse
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
AndyVerne said:
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
thanks！
Missing Something?
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
jasonccheng said:
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
Click to expand...
Click to collapse
See this post:
https://forum.xda-developers.com/yoga-book/help/missing-usb-driver-cherry-trail-tablet-t3537008
Same here with Linux... The adb devices command shows the device but the flash command ends in 'waiting for device' and thats it. Damn
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
zamzenos said:
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
Click to expand...
Click to collapse
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
danjac said:
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
Click to expand...
Click to collapse
Let me start at the top:
1. My comments on Lenovo are no reflection on the useful tools you have provided us here, for which I have thanked you more than once. So no need to be defensive on that score.
2. If the unlock warning had its source in Android itself, we could expect the warning to bear its logo. I assume it bears the Intel logo because Intel is the author of it. In itself, this is of no importance. What is profoundly irritating is the fact that the security warning is followed by a completely unjustfied 5 second suspension. This is a penalty. Perhaps many do not mind this interference with their use of their devices, but I do. I'm not used to that kind of treatment and I don't take kindly to it.
3. My opinion of Lenovo has always been low, especially since their attempts some years ago to spike their devices with spyware. I regard Lenovo as an exploitative bottom feeder, supplying workaday gear and screwing their customers every way they can for an extra buck or two. I offered the YB to several of my friends. All turned their noses up at the mention of the manufacturer. Don't blame them.
4. If you do want to be of further assistance here, perhaps you can use your obvious technical skills and knowhow to work out how we can replace the Intel penalty with something more benign. I have tried, but can't find where the Intel warning is hidden.
I have downloaded and extracted the apk of the system app remover you mentioned. But until I can get rid of the Intel warning I won't bother to re-root the YB and test if it will clear the junk.
#carepack: at the moment, you must buy the stock firmware (and won't it be expensive!). All part of lenny's screw.
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
carepack said:
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
Click to expand...
Click to collapse
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
zamzenos said:
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
Click to expand...
Click to collapse
According to this:
http://www.androidpolice.com/2016/1...views-cite-software-issues-incredible-design/
We'll receive the nougat Update.
Greetings
Hello, all!
I've been running Nexus v4.0.5 on my Thor device for a couple of years, but I'm more than ready for an upgrade. An upgrade to CM 14.1/LineageOS, to be exact.
At this point, I have a rooted Thor device with Safestrap v4.0.1 installed; Nexus v4.0.5 is installed in the STOCK ROM slot.
From what I understand, I need to unlock my boot loader, install TWRP, and then... something. Can anyone tell me how to go about unlocking my bootloader, installing TWRP, and doing everything else necessary to get CM 14.1 installed?
Oh, and if you're wondering exactly what I've done to this device thus far, check out this guide I made a few years ago. I've done all the steps outlined therein.
Thanks!
Rvby1 said:
Hello, all!
I've been running Nexus v4.0.5 on my Thor device for a couple of years, but I'm more than ready for an upgrade. An upgrade to CM 14.1/LineageOS, to be exact.
At this point, I have a rooted Thor device with Safestrap v4.0.1 installed; Nexus v4.0.5 is installed in the STOCK ROM slot.
From what I understand, I need to unlock my boot loader, install TWRP, and then... something. Can anyone tell me how to go about unlocking my bootloader, installing TWRP, and doing everything else necessary to get CM 14.1 installed?
Oh, and if you're wondering exactly what I've done to this device thus far, check out this guide I made a few years ago. I've done all the steps outlined therein.
Thanks!
Click to expand...
Click to collapse
See below; same steps apply. You do not need to remove SafeStrap or Nexus. Note all data will be lost; be sure to backup any important content.
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post72472618
Davey126 said:
See below; same steps apply. You do not need to remove SafeStrap or Nexus. Note all data will be lost; be sure to backup any important content.
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post72472618
Click to expand...
Click to collapse
I've gotten to the point where I need to upgrade TWRP to the latest version, but I can't seem to get fastboot to recognize the TWRP file.
I'm using the command
fastboot -i 0x1949 flash recovery thor-twrp-3.1.1-1
thor-twrp-3.1.1-1 is in platform-tools, and that's the directory I'm running these commands in.
Do you know what I'm doing wrong?
Thanks!
Rvby1 said:
I've gotten to the point where I need to upgrade TWRP to the latest version, but I can't seem to get fastboot to recognize the TWRP file.
I'm using the command
fastboot -i 0x1949 flash recovery thor-twrp-3.1.1-1
thor-twrp-3.1.1-1 is in platform-tools, and that's the directory I'm running these commands in.
Do you know what I'm doing wrong?
Thanks!
Click to expand...
Click to collapse
File ID appears to be incorrect; should be: thor-twrp-3.1.1-1.img
Davey126 said:
File ID appears to be incorrect; should be: thor-twrp-3.1.1-1.img
Click to expand...
Click to collapse
Hah, yeah, that's it. Totally forgot about file extensions.
So, I've gotten TWRP flashed, and I've flashed LineageOS and GAPPS according to the instructions here. When I try to boot up, though, I get stuck on the "Welcome to your Kindle Fire HDX" screen; it gives me the option to restore data from a previous device or start fresh. Since I don't have an internet connection on my device, I can't do anything related to my prior devices. And clicking on the start fresh option crashes the start-up program and sends be back to the language selection screen (which pops up just before the "Welcome to your Kindle Fire HDX" screen).
Now, before I flashed GAPPS, I didn't have this problem. The "Welcome to your Kindle Fire HDX" screen didn't show up, so I was able to set-up the OS and use it.
I've tried wiping the device, restarting, and reflashing LineageOS and GAPPS (both in a queue and one after another).
Any idea what's going on?
Rvby1 said:
Hah, yeah, that's it. Totally forgot about file extensions.
So, I've gotten TWRP flashed, and I've flashed LineageOS and GAPPS according to the instructions here. When I try to boot up, though, I get stuck on the "Welcome to your Kindle Fire HDX" screen; it gives me the option to restore data from a previous device or start fresh. Since I don't have an internet connection on my device, I can't do anything related to my prior devices. And clicking on the start fresh option crashes the start-up program and sends be back to the language selection screen (which pops up just before the "Welcome to your Kindle Fire HDX" screen).
Now, before I flashed GAPPS, I didn't have this problem. The "Welcome to your Kindle Fire HDX" screen didn't show up, so I was able to set-up the OS and use it.
I've tried wiping the device, restarting, and reflashing LineageOS and GAPPS (both in a queue and one after another).
Any idea what's going on?
Click to expand...
Click to collapse
- insure bootloader is unlocked; unlock again if uncertain
- be sure to wipe system & data partitions before flashing LinOS
- ROM and GAaps (7.1/arm/nano) should be flashed in one operation
- if still no joy downgrade to TWRP 3.0.0-1 then try again
- as a last resort flash Fire Nexus KTU84Q (just one file), boot and allow ROM to initialize, then return to TWRP and reflash LinOS + GAaps
The above may seem a bit random but there's a reason behind each suggestion and the order in which they are presented.
Davey126 said:
- insure bootloader is unlocked; unlock again if uncertain
- be sure to wipe system & data partitions before flashing LinOS
- ROM and GAaps (7.1/arm/nano) should be flashed in one operation
- if still no joy downgrade to TWRP 3.0.0-1 then try again
- as a last resort flash Fire Nexus KTU84Q (just one file), boot and allow ROM to initialize, then return to TWRP and reflash LinOS + GAaps
The above may seem a bit random but there's a reason behind each suggestion and the order in which they are presented.
Click to expand...
Click to collapse
So, I can't seem to get fastboot to run unlock because fastboot isn't recognizing my kindle as a device. When I go to Device Manager, my Kindle is under Portable Devices, and if I browse for drivers on my computer, I only get "MTB USB Device."
Any advice?
Rvby1 said:
So, I can't seem to get fastboot to run unlock because fastboot isn't recognizing my kindle as a device. When I go to Device Manager, my Kindle is under Portable Devices, and if I browse for drivers on my computer, I only get "MTB USB Device."
Click to expand...
Click to collapse
- download drivers from this post (prequisite section); unzip as needed
- open windows device manager
- tether device in fastboot mode
- take note of entries added; delete those devices
- remove tether and reattach (might have to reboot one/both devices)
- when Windows prompts for drivers direct it to those downloaded
Davey126 said:
- download drivers from this post (prequisite section); unzip as needed
- open windows device manager
- tether device in fastboot mode
- take note of entries added; delete those devices
- remove tether and reattach (might have to reboot one/both devices)
- when Windows prompts for drivers direct it to those downloaded
Click to expand...
Click to collapse
So, I can't seem to get into fastboot mode. I don't have a factory cable, and none of the commands listed here activate fastboot mode.
What should I do?
Sorry for my ignorance!
Rvby1 said:
So, I can't seem to get into fastboot mode. I don't have a factory cable, and none of the commands listed here activate fastboot mode.
What should I do?
Sorry for my ignorance!
Click to expand...
Click to collapse
We are all ignorant about 99.99% percent of the world around us with unique 'points of light' distinguishing various individuals; never apologize for being ignorant!
Possible solution:
- boot into TWRP (turn off tablet then restart by pressing <power>+<vol-down> together; release first logo appears)
- tether device to host PC (assumes Windows)
- tap Reboot
- tab Bootloader
Above sequence should place your tablet in 'fastboot mode'. If the word 'Ready' appears on the tablet screen the correct drivers are installed on the PC. If not follow previously posted procedure for updating drivers.
Davey126 said:
We are all ignorant about 99.99% percent of the world around us with unique 'points of light' distinguishing various individuals; never apologize for being ignorant!
Possible solution:
- boot into TWRP (turn off tablet then restart by pressing <power>+<vol-down> together; release first logo appears)
- tether device to host PC (assumes Windows)
- tap Reboot
- tab Bootloader
Above sequence should place your tablet in 'fastboot mode'. If the word 'Ready' appears on the tablet screen the correct drivers are installed on the PC. If not follow previously posted procedure for updating drivers.
Click to expand...
Click to collapse
True, true! Thanks for your kind words, Davey!
And thanks for your help with this, too!
I was able to boot into fast mode, and I went through the unlock process again. With that done, I tried to reflash LineageOS and GAPPS, but I ran into the same issue I did before. So I did a bit of googling (which I didn't exactly think to do before :C), and apparently this is a known issue for CM operating systems.
Here's the fix.
Swipe down (a few hundred times) to get the notification tray. Go to settings. Turn on wifi. Problem (probably) solved.
Thanks again for all your help, Davey! I wouldn't have gotten Nexus running back in the day without ya, and I wouldn't be running LineageOS right now if you hadn't been my savior a second time around. And in addition to my thanks, sorry for not googling first! It would have saved both of us a bit of trouble, haha.
Rvby1 said:
True, true! Thanks for your kind words, Davey!
And thanks for your help with this, too!
I was able to boot into fast mode, and I went through the unlock process again. With that done, I tried to reflash LineageOS and GAPPS, but I ran into the same issue I did before. So I did a bit of googling (which I didn't exactly think to do before :C), and apparently this is a known issue for CM operating systems.
Here's the fix.
Swipe down (a few hundred times) to get the notification tray. Go to settings. Turn on wifi. Problem (probably) solved.
Thanks again for all your help, Davey! I wouldn't have gotten Nexus running back in the day without ya, and I wouldn't be running LineageOS right now if you hadn't been my savior a second time around. And in addition to my thanks, sorry for not googling first! It would have saved both of us a bit of trouble, haha.
Click to expand...
Click to collapse
Hey - glad you got it working and left a solution that hopefully will help others who encounter the same issue. Enjoy your rejuvenated device!
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Really desperate here.. :/
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Yousucks2 said:
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Click to expand...
Click to collapse
You are in a world of hurt. It's possible (likely) the device can be recovered but not without considerable effort and (probably) many failed attempts. Such assistance is beyond what can reasonably be provided via the forums. You can browse through HDX threads to get the gist of what needs to happen. If you are a technology/Android noob it will probably be easier to pick up a refurb at an auction site. Good luck.
PM for support is normally ignored
joltpodcast03 said:
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Click to expand...
Click to collapse
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
draxie said:
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
Click to expand...
Click to collapse
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Do your homework...
joltpodcast03 said:
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Click to expand...
Click to collapse
As I said, if fastboot works, it's fixable (in other words, it's not a brick).
BUT, you'll have to find one of the million guides on how to setup and
use fastboot all by yourself. That's not something I'm willing to spend
time on. Sorry...
As for cables, unless the device is a soft-brick, you don't need a special
cable, but it's preferable to use your factory cable not random junk.
BUT, seeing that you have MacOS, my 1-Click tool _should_ work for you.
Then, all you need to do is click through a web-UI. If you want to do that
instead, you'll have to wait though, because I need to iron out a wrink or
two, and haven't had the time the last week or so...
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Yousucks2 said:
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Click to expand...
Click to collapse
Technically not ADB if working in fastboot but guidance is still 100% relevant.
fastboot commands?
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
For some reason I can't upload a picture of the various files in the partition.
Side note: could I theoretically put CM 12 or anything else on one of the partitions instead of the stock ROM?
Praxxer1 said:
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Davey126 said:
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
Ah. I wish I had seen that thread before I started the process! You may be right about the compatible boot. I couldn't find the original aboot_vuln.mbn file mentioned in the thread I was following, but managed to find aboot.img file and flashed that hoping it was the same. I could have sworn though, that the device stopped working the second after I clicked the unlock.bat file (executed outside the fastboot screen), but could be wrong.
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Thank you for your time, I'll keep reading through the thread you linked.
Praxxer1 said:
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Click to expand...
Click to collapse
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Davey126 said:
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Click to expand...
Click to collapse
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Praxxer1 said:
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Click to expand...
Click to collapse
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Davey126 said:
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Click to expand...
Click to collapse
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Praxxer1 said:
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Click to expand...
Click to collapse
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
1-Click is your friend
Davey126 said:
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
Click to expand...
Click to collapse
Right... the symptoms described are the normal state of affairs
after 'fastboot erase aboot' and 'unlock.bat' does no such thing.
The post linked above and/or my original "Bulk mode" post both
have the necessary instructions to recover. Alternatively, 1-Click
can handle this, assuming access to either MacOS or Linux (for
the time being).
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