Database Develop

Kindle Fire HD Stuck on flash logo screen

I wanted to install Gapps to my Kindle since many of the apps including the web browser are coming up as unsupported. I have rooted my Kindle Fire HD 8.9 and installed TWRP. When I rebooted my kindle to enter the recover mode, it got stuck at logo screen.
At first, when it was logo was flashing if I plugged it in, ubuntu give an error message "unable to mount Jem PVT Prod 04". I discovered that holding the volume up button made the screen go blank but not off. You can plug the kindle in and Ubuntu will recognize the kindle and allow you to access the internal storage.
How can I fix and reboot the Kindle from Ubuntu?
I researched tons of solutions but most of them require Windows which I don't run or I tried the instruction and they don't work or our incomplete.

I received a fastboot cable from Amazon today. I'll see how it works. Any advice would be appreciated.

Okay, I fixed the problem with the Fastboot Cable. Here's the steps that I did to fix it. It was loading Twrp or the bootloader so I reinstall them. I have Android SDK on my computer and my Kindle is rooted.
Step 1.
The correct twrp was difficult to find. This forum offered a site to go to but I found the site was corrupted and the website was trying to download a virus.
I found the twrp and bootload file here.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet/
I placed the files in my android/sdk/platform-tools. (kfhd8-freedom-boot-8.4.3.img & kfhd8-twrp-2.6.0.0-recovery.img)
I typed into terminal "fastboot -i 0x1949 getvar product" without parenthesis. At the waiting for device command, I plugged in the Kindle with the Fastboot cable and held the Volume up button to go into fastboot mode.
I opened the android/sdk/platform-tools and right click the mouse and hit open in terminal
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.3.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.6.0.0-recovery.img
fastboot -i 0x1949 reboot
From the reboot, hit the volume up to get into twrp.
At this point, I still could go into the kindle so I thought the operating system may be corrupted.
Step 2
In twrp, I backed up the system. and rebooted into twrp.
In twrp, I hit wipe and rebooted back into twrp.
I downloaded CyanogenMod and Gapps to my platform-tools folder again.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet
Step 3
I couldn't access the internal drive so I used ADB to put the files on my kindle.
Here's a video of the instructions I used.
youtu.be/NaK5OxUeDKM
Open the support document for Ubuntu instructions.
First, open terminal in the Platform Tools file and type ADB Devices. When I pushed the two files, his instructions say to use command sudo ./adb-linux push filename /sdcard/. This didn't work. I used "./adb push [filename /sdcard/." without the quotes and it worked.
Step 4
Enter twrp and install the CyanogenMod and Gapps. Reboot
This got my operating system up and running perfectly.
Now bad for a complete Noob.

Root Lenovo Tab 10 TB-X103F

Root Lenovo Tab 10 TB-X103F (Tested)
1. activate developer options on the Tablet
2. enable Bootloader-Unlock on the Tablet
3. download and install ADB und fastboot
4. latest usb driver on your PC
5. download TWRP TWRP-3.0.2_TB-X103F-beta.img
https://forum.xda-developers.com/showpost.php?p=70228684&postcount=65
6. download SuperSu zip file
Steps:
1.) boot to fastboot -> shutdown your device -> press on/off + "+" Volumekey → device restarts to fastboot mode
2.) connect to your pc via usb cable
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
4.) do the unlocking
"fastboot oem unlock-go"
5.) boot TWRP image file in the command line, showing the pathway to the .img file (if not in the same folder):
fastboot boot TWRP-3.0.2_TB-X103F-beta.img
6.) Put SuperSu zip file in the device memory and flash SuperSu zip with TWRP, then restart the device. Done!!!!

Stock recovery remains
RooterLeopold said:
Root Lenovo Tab 10 TB-X103F (Tested)
1. activate developer options on the Tablet
2. enable Bootloader-Unlock on the Tablet
3. download and install ADB und fastboot
4. latest usb driver on your PC
5. download TWRP TWRP-3.0.2_TB-X103F-beta.img
https://forum.xda-developers.com/showpost.php?p=70228684&postcount=65
6. download SuperSu zip file
Steps:
1.) boot to fastboot -> shutdown your device -> press on/off + "+" Volumekey → device restarts to fastboot mode
2.) connect to your pc via usb cable
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
4.) do the unlocking
"fastboot oem unlock-go"
5.) boot TWRP image file in the command line, showing the pathway to the file:
TWRP-3.0.2_TB-X103F-beta.img
6.) Put SuperSu zip file in the device memory and flash SuperSu zip with TWRP, then restart the device. Done!!!!
Click to expand...
Click to collapse
I have done all the steps but For some reason twrp is not installed and i still have the stock recovery. Please help

That's because the above only boots TWRP to root but does not install it. To install TWRP, when in booted with TWRP, you need to transfer the TWRP img to the tablet storage and then install it while in TWRP.

it is important to show the pathway to the file TWRP-3.0.2_TB-X103F-beta.img in the command line, like:
C:\Users\Public\Documents\My Videos\TWRP-3.0.2_TB-X103F-beta.img

Sorry for this newbie question.
Which part of the above rooting steps is rooting my tablet, what is TWRP doing and why do I need to install the SuperSU app?
During my first try I didn't boot the TWRP image rather I flashed it. But that didn't help at all.
After booting the TWRP image I was able to flash the SuperSU app.
The stock recovery is still in use.
Thanks in advance.

Read the steps carefully and follow the steps, it is a tested successfull strategy. To get deep knowlege about the background processes, please read the threads elsewhere in Web.

Yow how do you enter Fastboot on the tablet and i haved tied avery button on the tablet and i dont see the fastboot option

Entering Fastboot on Lenovo TB-X103F tablet
ShottaDopey said:
Yow how do you enter Fastboot on the tablet and i haved tied avery button on the tablet and i dont see the fastboot option
Click to expand...
Click to collapse
Hi everyone. I just want to clarify something about this procedure There's a lot of people being confused on how to get into FASTBOOT on some things, and that's stopping them getting anywhere from the beginning.
The Lenovo TB-X103F tablet doesn't have a way of booting directly into FASTBOOT. Turning the tablet On while holding either volume key and the On button doesn't do it directly. . . . . Firstly, there's 3 buttons on the tablet, I call them VOL- VOL+ PWR (again, that's just to clarify things 100%)
here's what must be done (well it's this way on the 3 I have on my desk, so I assume all TB-X103F tablets are the same) . . . . .
1) Turn the tablet off completely.
2) Press & hold the VOL+ button (the middle of the 3 buttons).
3) Press & hold the PWR button, release the PWR button as soon as anything appears on screen - Keep holding VOL+ button.
4) After about 8 seconds the familiar green android lay down will appear. Then, your recovery menu will appear.
5) Release the VOL+ button anytime now.
6) Press either VOL button to select BOOTLOADER on the menu (Bootloader is the same as FASTBOOT on this menu, that's where the confusion lies for many users).
7) Got Bootloader selected? now press PWR and let the tablet reboot itself.
8) it will show the LENOVO logo, and appear to be stuck - it isn't It's in Fastboot mode.
9) Plug in your USB to PC cable, and it'll install appropriate drivers on the PC (hopefully eh?).
10) Once the drivers are installed, test it by getting a Command Prompt in your ADB/FASTBOOT folder on your PC . . . .
11) type the command FASTBOOT DEVICES It should show you that your device is connected, if it shows no devices then either it didn't install the drivers, or something
else is wrong (there's about 30 things that can have gone wrong here, too many to go through in this quick guide).
12) The tablet will stay in FASTBOOT/BOOTLOADER mode until you turn it off (or the battery goes flat lol). So stay calm, there's no rush
I've mentioned about there being no rush, because if you choose ADB connecting from the recovery menu, it disconnects automatically after about 5 minutes -
This is Important to know because it can disconnect while you're pushing/pulling files from the tablet, and cause really nasty problems. Bad design eh?
But we're in Fastboot mode, so nothing to worry about like that

Deleted

Successful root
It was hard, but I had finally had done it. I had figured it out it is easier just to go to the command prompt (I ran it under admin) and "cd C:/adb" (where you installed the adb fastboot software) while having the TWRP image file being placed there. I only wished that I had done it sooner. And for those who are new to the custom recovery it can be overwealming, but with patience and going through the files in the file explorer to find your main storage would lead you to the SuperSU file and successfully root your device.

I flashed TWRP...now what? I can't find any instructions on how to reboot into TWRP. I got into some sort of Chinese menu (PWR + VOL-) but I'm pretty sure this is the device test menu.

So I did the "fastboot oem unlock-go" command and adb said ok but my tablet just went to a black screen and won't turn on now and I'm not sure why. I also heard the Windows USB disconnect sound when i did it.

Would this work with the TB-X104F running 8.1?

Since a few months my tablet is stuck with the 'password changed, wait....' message. I had hoped that I could overcome this with the steps mentioned here. But unfortunately not
I can't start it anymore, so I'm not sure if it is in developers mode or not. Also, plugging the device in my mac didn't let it download the drivers.
Too bad, because when it was working it was a great tablet, now it's just a expensive drawer filler

SynGamer said:
I flashed TWRP...now what? I can't find any instructions on how to reboot into TWRP. I got into some sort of Chinese menu (PWR + VOL-) but I'm pretty sure this is the device test menu.
Click to expand...
Click to collapse
its the vol+ not - you need to press with the power button

Steridroid said:
I have done all the steps but For some reason twrp is not installed and i still have the stock recovery. Please help
Click to expand...
Click to collapse
so what exactly do i have to type at the command prompt to run twrp?,ive put the twrp img file in the same folder as the adb stuff.

3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
fastboot shows notting

lenovo seems to have killed these tablets from the old lady next doors experience.. no wifi, no adb, no fastboot, no qualcomm, just unknown device, which loads NOTHING, no drivers work!!!

Twrp Testing for all versions of op7_pro

This thread is intended to get a fully working twrp for our new device sooner than later by more of us participating.
This is a testing thread so YES ANYTHING CAN GO WRONG. But most likely will not go wrong..
All test builds compiled by me are from @mauronofrio source code
https://github.com/mauronofrio/android_device_oneplus_guacamole_TWRP
This guide was copied and pasted from @mauronofrio Twrp thread.
Install guide:
Actually seems "fastboot boot twrp.img" is not working so we need to use another guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Now you should check which slot are you using with this command "fastboot getvar current-slot"
5. Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
6. Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
7. Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
8. First thing go in reboot menu and restore the old active slot
9. Now you can flash the installer (Actually you can do it using sideload, start sideload server from twrp advanced menu and from pc use this command "adb sideload twrpinstaller.zip")
If you are already rooted, you can skip all and directly flash the installer like a magisk module. Always remember that after you flashed the installer you will be unrooted.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/one...e-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
I need the following logs in order to find issues.
start a terminal window and enter below commands to get the logs
When TWRP boots enter below commands in terminal:
Code:
adb shell "getprop" > getprop.txt
adb pull /tmp/recovery.log
adb shell "dmesg" > dmesg.log
adb logcat > logcat.txt
and post the files here.
Links will be in post #2

Links to test builds
Test-0.2 f2fs filesystem
Twrp.img https://www.androidfilehost.com/?fid=1395089523397969888
Twrp installer https://www.androidfilehost.com/?fid=1395089523397969887
Test-0. 3 ext4 filesystem
Twrp.img https://www.androidfilehost.com/?fid=1395089523397969903
Installer https://www.androidfilehost.com/?fid=1395089523397969902

Under 6. Should we be using "fastboot flash recovery xxx.xxx" or the one from the post?
I might be able to test evening today.
Sent from my GM1911 using Tapatalk

vickyjusme said:
Under 6. Should we be using "fastboot flash recovery xxx.xxx" or the one from the post?
I might be able to test evening today.
Sent from my GM1911 using Tapatalk
Click to expand...
Click to collapse
fastboot flash boot twrp-test.img

Tried this method, but TWRP does not load. Stuck on this (image attached)
Reboot sticks to this screen again. Cannot access fastboot from here, but I can see my device from adb devices. Help me?
https://imgur.com/1s6dejl
Edit: start by power on+volume down loads fastboot.. Phew...

vukis said:
Tried this method, but TWRP does not load. Stuck on this (image attached)
Reboot sticks to this screen again. Cannot access fastboot from here, but I can see my device from adb devices. Help me?
https://imgur.com/1s6dejl
Edit: start by power on+volume down loads fastboot.. Phew...
Click to expand...
Click to collapse
Where are the logs. Please don't test and not provide logs. But thanks for informing test 0.3 doesn't work.
Just wondering how long you waited.

[RECOVERY][TB-X606F/TB-X606FA][UNOFFICIAL] TWRP 3.7.x for Lenovo Tab M10 FHD Plus

This version of TWRP works on the Lenovo TB-X606FA, TB-X606F and TB-X606X.
Warning: this TWRP will not work for any of the Tab M10 variants with Qualcomm SOCs. For the TB-X505F, see this thread. For the TB-X605F/L, see this thread.
Code:
#include <std_disclaimer.h>
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Encryption
This device was released with Android 9 using full disk encryption (FDE). But we now have Android 13 GSIs for this tablet - and Android 13 does not support FDE. Android 13 only supports file-based encryption (FBE).
If you are using a ROM/GSI that uses FBE, you must use the twrp with -fbe in the name. If you use the wrong one, twrp will not be able to decrypt the data partition.
If you don't know if you're using FBE or FDE, then run this command while Android is running: adb shell getprop ro.crypto.type. If it returns "block", then your device is FDE. If it returns "file", it's FBE.
Installation
With a stock ROM, it is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
If Windows 10/11 does not recognise your tablet in fastboot mode, then see post #2.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download the latest magisk.apk to your SDcard or OTG device. Change the filetype from "apk" to "zip".
get a copy of the vbmeta.img file from the stock ROM. It should be located in one of the subdirectories of LMSA's c:\ProgramData\LMSA\Download\RomFiles directory (after you download it using the LMSA rescue (power-off mode). This is only required the first time you flash TWRP, or the first time after you re-flash the whole stock ROM.
if your bootloader is already unlocked, go to step 5. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot flashing unlock
follow the instructions on the tablet, then reboot to Android.
note: if fastboot reports <waiting for device>, then you need to install the Mediatek USB drivers. Go to developer.android.com/studio/run/oem-usb, then find the link to Mediatek (MTK) and follow the installation instructions.
note: after unlocking, tablet will take a while to come back up - because it has to do a factory reset and encrypt data again.
flash the TWRP image:
Code:
adb reboot bootloader
fastboot flash recovery twrp_X606FA_11.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
backup the stock boot, system and vendor partitions in TWRP, if you don't have backups already
load Magisk:
In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the "Reboot System" button
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
2023-03-27 - add TWRP 3.7.0 for FBE ROMs/GSIs (Android 13+) only
2022-02-06 - added separate download for TB-X606F
2021-12-16 - TWRP 3.6.0 updates
- support for Android 12 decryption (keymaster)
2021-07-05 - TWRP 3.5.2 updates
- corrected display of Cyrillic (and other non-ASCII characters) in file names on external drives (utf8)
2021-03-10 - TWRP 3.5.1 updates
- cherrypicked update 1995 to force splash screen to display on boot
- orientation is now landscape (for tablets)
- updated install instructions to reflect new Magisk apk (v22).
2021-02-02 - fix blank screen on boot - don't need to press power button anymore to wake screen up
2021-01-24 - TWRP 3.5.0_10-0: initial release
Downloads (FDE)
This will work with stock ROMs and most pre-A13 ROMs/GSIs.
TWRP 3.6.0_11-0 for X606FA: twrp-X606FA_11.img
TWRP 3.6.0_11-0 for X606F: twrp-X606F_11.img
Downloads (FBE)
This will not work with stock ROMs or most pre-A13 ROMs/GSIs. This is for ROMs/GSIs that use FBE to encrypt. Android 13+ only supports FBE.
TWRP 3.7.0_12-1 for X606FA with FBE encryption: twrp-X606F_12.1.fbe.img
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-12.1
https://github.com/Yahoo-Mike/recovery_device_lenovo_X606FA/tree/android-12.1-fbe
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Created 2021-01-24
Last Updated 2023-03-27 (FBE support)

Windows 10/11 does not recognise tablet in fastboot mode
If your tablet is recognised by ADB but not by fastboot in Windows, you might need to get the latest versions of fastboot and the Mediatek usb drivers.
1. use the latest fastboot version
Make sure you are using the latest version of fastboot. There were major changes to fastboot for Android 10.
If you are using PowerShell, make sure it's picking up the fastboot you expect: fastboot --version. If not, use ./fastboot from the directory with the executable.
2. update device drivers
Try the latest Mediatek (MTK) drivers from Install OEM USB drivers. When they are loaded, they appear in Device Manager as "Kedacom USB Device/Android ADB Interface".
If Windows complains that the drivers are unsigned and refuses to load them, then do this as Administrator in Windows:
bcdedit /set testsigning on
reboot Windows
install the drivers
bcdedit /set testsigning off
In Windows 11, you might also need to turn off Secure Boot in your PC's BIOS to get the bcdedit command to work.

So I have the ZA5W0097US, would you suggest this wouldn't work?

ldeveraux said:
So I have the ZA5W0097US, would you suggest this wouldn't work?
Click to expand...
Click to collapse
That looks like a TB_X606F. This TWRP might work. We won't know for sure until someone tries.
Remember, the screen will be blank when TWRP boots up. You'll just have to click the power button twice to wake it up. I'll try and fix that over the next few days.
If you decide to try this TWRP and it doesn't work, please let me know what happens. And when you're booted into Android, can you tell me what the results of these ADB commands are?
Code:
adb shell getprop ro.hardware
adb shell getprop ro.boot.hardware

New version is now available in the first post.
The blank screen issue is mostly fixed...mostly. The screen is still blank on boot when decrypting data, but then it wakes up. No need to press the power button anymore.

I just got my TB-X606F (it's actually finishing setup right now) and I'm going to try flashing this TWRP onto it. I *think* the only difference between the "F" and "FA" version is that the "FA" comes with some sort of Alexa capability.
Both adb commands output "mt8768".

TB-X606F/ZA5T0300US (the manual also says TB-X606X) confirmed TWRP and Magisk are working. Had a hell of a time with getting fastboot to work on my main machine so I used a virtual machine to do everything with fastboot.

sirp0p0 said:
TB-X606F/ZA5T0300US (the manual also says TB-X606X) confirmed TWRP and Magisk are working. Had a hell of a time with getting fastboot to work on my main machine so I used a virtual machine to do everything with fastboot.
Click to expand...
Click to collapse
Cool. I'll update the OP.
Maybe check you have the latest version of fastboot on your main machine. There were some major changes for Android 10.

Good call. My adb and fastboot were both way out of date.

I also have the TB-X606F and was able to get this working 100%. I thought it was going to wipe my system so I backed everything up beforehand, but no wipe. Just replaced recovery with TWRP and here I am. Thanks a ton, great to have another TWRP recovery device!

ldeveraux said:
... I thought it was going to wipe my system so I backed everything up beforehand, but no wipe.
Click to expand...
Click to collapse
It will only wipe if you are unlocking the bootloader for the first time.
Thanks for the feedback.

Tried this process and ran into an issue. Flashed TWRP Okay, flash vbmeta ok, rebooted to twrp, but could not find magisk on sdcard for some reason. Not tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet

snickle said:
Tried this process and ran into an issue. Flashed TWRP Okay, flash vbmeta ok, rebooted to twrp, but could not find magisk on sdcard for some reason. Not tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
Click to expand...
Click to collapse
Rebooteed to bootloader flashed twrp and vbmenta. REbooted to recovery and twrp came up. Installed magisk zip and rebooted. No root and stock recovery comes up instaead of TWRP.
THoughts?
Also still no fastboot commands available when tablet booted, just from bootloader.
Tried completely reflashing stock image, still no change.

snickle said:
...rebooted to twrp, but could not find magisk on sdcard for some reason.
Click to expand...
Click to collapse
You have to download Magisk-v21.4.zip and push it to /external_sd/.
If you did that, can you see your other files in /external_sd/ ?
snickle said:
...tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
Click to expand...
Click to collapse
Make sure you have the latest adb and fastboot from Google. There were some major changes to fastboot for Android 10.
Also make sure you have the latest USB drivers from Lenovo.

I have the latest adb and drivers. fastboot commands used to work.
I rebooted to bootloader and flashed thre patched boot image made with the canary version of magisk and got root.
I then reflashed twrp and vbmeta and things seem to be working. Except for fastboot commands whlle booted.

snickle said:
I have the latest adb and drivers. fastboot commands used to work.
Click to expand...
Click to collapse
For Windows, the latest fastboot --version is 31.0.0-7110759
snickle said:
...things seem to be working. Except for fastboot commands whlle booted.
Click to expand...
Click to collapse
If you are using Windows 10, check that the "Android Bootloader Interface" driver is loaded in Device Manager when the tablet is in fastboot mode. See this post.
And when you say "except for fastboot commands while booted", do you mean "while the tablet is booted in fastboot mode" or "while the tablet is booted in twrp recovery or Android system"?

Yahoo Mike said:
For Windows, the latest fastboot --version is 31.0.0-7110759
If you are using Windows 10, check that the "Android Bootloader Interface" driver is loaded in Device Manager when the tablet is in fastboot mode. See this post.
And when you say "except for fastboot commands while booted", do you mean "while the tablet is booted in fastboot mode" or "while the tablet is booted in twrp recovery or Android system"?
Click to expand...
Click to collapse
Latest ADB and drivers loaded.
Fastboot commands work while in fastboot mode, but do not work when booted to system any more.

snickle said:
Fastboot commands work while in fastboot mode, but do not work when booted to system any more.
Click to expand...
Click to collapse
That's ok. That's how it's supposed to work.
ADB only works when your device is in recovery or system. It won't work when you're in fastboot or EDL mode.
Fastboot only works when your device is in fastboot mode. It won't work when you're in EDL, recovery or system.
The fastboot utility is an interface to the Android bootloader. When your device is in fastboot mode, you can use this utility to configure (some of) the bootloader and partition images. That's about it. I'm oversimplifying again, but...once the bootloader has passed on execution to EDL or a kernel (recovery or system), the fastboot utility can't work because the bootloader process is no longer running.
Unhelpfully fastboot just displays the "waiting for device" message, rather than something like "waiting for device to enter fastboot mode".
I hope that helps explain what's going on.

Twrp is working as expected no issues I have found, except for the need to press the power button s few times after booting into recovery to get twrp screen.

Hello! I need a bit of help... I have a TB-606F, 4GB/64GB version
I'm stuck on step 5. I've unlocked the bootloader, flashing TWRP and vbmeta seems successful, but then I cannot reboot into recovery. Using the fastboot reboot command I get "fastboot: usage: unknown reboot target recovery". If I try to reboot using volume up + volume down + power it eventually boots to Android.
Any thoughts are much appreciated!

Question Problem with adb devices command on fastboot

I succeeded in unlocking my phone's bootloader.
I enabled usb debugging.
The problem is when the phone is on, my pc can detect this device when I entered 'adb devices' in powershell/ cmd.
But when I entered fastboot, my pc is unable to detect the device whenever I entered 'adb devices' in powershell/ cmd.
It baffles me because I have never encountered this problem before. I had successfully installed twrp recovery on other phones in the past.
On device manager, it shows Android Phone -- Android Bootloader Interface when I connect the phone in fastboot mode. When I boot it, under Universal Serial Bus devices, it shows Redmi Note 11.
I used Google's SDK Platform Tools from here by following this method to install it.
I'm using windows 10 x64 21H2 with latest update.
My phone is spesn.
How do I fix this problem in order to be able to install TWRP recovery?

Have you tried using "fastboot devices" while in fastboot mode, instead of the adb one?

Vagelis1608 said:
Have you tried using "fastboot devices" while in fastboot mode, instead of the adb one?
Click to expand...
Click to collapse
Entering "fastboot devices" detects my device.
But when I entered "fastboot flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img", I get this error:
D:\Data\Library\desktop\Spesn>fastboot flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
Sending 'recovery' (131072 KB) OKAY [ 3.973s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Click to expand...
Click to collapse
Edit:
I fixed it by following this guide and managed to install twrp properly.
Thank you @Vagelis1608 for your help earlier.

Yeah, on AB devices you need to boot the recovery and flash it through there.
Good to see you figured it out though.

redmi note 11 doesnt have recovery partition,you need to use command fastboot flash boot ...