Database Develop

Solution for Android Kit Kat OTA update boot loop problems

To anyone who has had the issue of installing the OTA Kit Kat update and ended up with an error, followed by bootloop "No Command" screen, here's the fix and how to save your data. I was unable to successfully get the image flashed using adb sideload, but I will mention it as others apparently have.
When attempting to install over the air update on Nexus 7 2012, Wifi edition, about 25% into the install I received an error screen. Upon restarting device, the Nexus would load the Google splash screen, followed by a "No Command" screen. To those that have encountered this and are worried about losing your data, follow these instructions. I am using Ubuntu so you will have to do a little research on downloading the tools for Windows and how to use them. I have a ton of computers to work on and don't have much time to type out a long guide, and I have never used either of these tools on a Windows machine.
Download the factory image for Kit Kat from here: https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
Tools needed:
Drivers for your Nexus (Windows only)
Fastboot
ADB
Fastboot and adb are packed together in the Android SDK, or other sources have them. Using ubuntu, run "sudo apt-get install android-tools-fastboot" and "sudo apt-get install android-tools-adb" in your command line.
If you want to use adb sideload, check to make sure you device is recognized in "70-android.rules" or "51-android.rules" by running:
Code:
adb devices
If you get "?????????" then you better edit your android rules file by typing:
Code:
gksudo gedit /etc/udev/rules.d/70-android.rules
Note that your android file could use the number 51 or 99 also, so I would recommend performing this step 3 times with 70-android.rules, 51-android.rules, and 99-android.rules.
Add the following:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="adbusers" #regular/debug
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="adbusers" #fastboot
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="plugdev" #regular/debug
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="plugdev" #fastboot
Save this file and exit your editor. Now, extract your image you downloaded from Google. You should see a file named "image-nakasi-krt16s.zip." Copy this somewhere easily accessible, such as /home/<your username>/ANDROID.
Open command prompt and enter the following:
Code:
cd /home/<your username>/ANDROID
adb sideload image-nakasi-krt16s.zip
If all goes well, this should install and reboot. If not, you may get errors such as "E:signature verification failed" or something about unexpected files. I had about 4 different errors trying this, so continue reading to fix this using fastboot.
Extract all of the contents of the downloaded image file to the /ANDROID directory we created earlier.
Power off the device. Press and hold on to the Volume down and power key altogether until you see the bootloader screen. This screen is what we know as bootloader mode or fastboot mode. Connect the device to the PC via USB cable
Open your command prompt and head to the /ANDROID directory. In case you forgot:
Code:
cd /home/<your username>/ANDROID/
Next, run the following commands in order.
Code:
fastboot erase boot
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot erase system
Now we need to reflash the bootloader:
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
Reboot the bootloader:
Code:
fastboot reboot-bootloader
Flash the 4.4 Factory Image, type:
Code:
fastboot update image-nakasi-krt16s.zip
Now sit and wait while your tablet is updated. It will restart and your apps will be optimized. Good luck!

I have the very same issue after the 4.4 OTA. When I tried to connect, my nexus is only getting listed under the fastboot devices (Drivers installed by the WUG toolkit/in device manager can be seen as Google Nexus 7 BootLoader Interface) and I have no adb connection (probably I had USB debugging deactivated. Is there anything I can do or do you think I'm screwed and have to erase everything?
Update: just executing the fastboot steps worked just fine (without any ADB sideload), many thanks for this solution

Thank you for your very usefoul post greg but how does one go about doing the same procedure without Linux ?

Redzo said:
Thank you for your very usefoul post greg but how does one go about doing the same procedure without Linux ?
Click to expand...
Click to collapse
I did it using windows: I've installed the android sdk for windows and used the wugfresh toolkit to update my nexus 7 drivers - then booted into fastboot mode and executed the fasboot... commands listed

Yeah, there is really no need for the adb, and I had no luck with it. I was thinking fastboot would wipe my user data, but I just didn't run any commands that would wipe my data and it seemed to work fine. On Windows, I would just download the SDK and then get your tablet connected and the fastboot commands are all the same. The problem I have is I can never get Windows to work right with and of my Android gadgets and I am not as good with the Windows command line. But if you have trouble connecting to Windows, just go to the Ubuntu site and throw the live version on a flash drive, run the sudo apt-get android-tools-fastboot command, and you should be good to go.

Redzo said:
Thank you for your very usefoul post greg but how does one go about doing the same procedure without Linux ?
Click to expand...
Click to collapse
If you are still having issues, pm me and I would walk you through it.

greg_gorrell said:
If you are still having issues, pm me and I would walk you through it.
Click to expand...
Click to collapse
Thank you very much greg for your kind offer but i have managed to solve the issue

A bundle of thanks to @greg_gorrell! Always making things easy for us
I have successfully updated my Nexus 7 (2012) from 4.3. Though I will have to root the device again
I am curious though. Why the OTA update always fails on our rooted devices? Its been going on since 4.2.2 I think while previously we used to update to OTA just fine even when we had out devices rooted (personally done that). Any possible explanation for this issue?

abobobilly said:
A bundle of thanks to @greg_gorrell! Always making things easy for us
I have successfully updated my Nexus 7 (2012) from 4.3. Though I will have to root the device again
I am curious though. Why the OTA update always fails on our rooted devices? Its been going on since 4.2.2 I think while previously we used to update to OTA just fine even when we had out devices rooted (personally done that). Any possible explanation for this issue?
Click to expand...
Click to collapse
You're welcome! But I have been looking into it and it seems that it isn't just rooted tablets that cause the update to fail. On another site, I believe Android Police, I noticed some had completely stock devices that failed.

This sux...
I had same thing happen on my nexus 10 doing ota from 4.4 to 4.4.2 on my stock rooted N10.

notfaded1 said:
I had same thing happen on my nexus 10 doing ota from 4.4 to 4.4.2 on my stock rooted N10.
Click to expand...
Click to collapse
I am not able to do anything as my Nexus is in bootloop, it is constantly rebooting so I have no access to anything. Cannot get into recovery mode at all. Any help would be nice.

Was that caused by the rom update? And did you let it die and then try to boot into recovery immediately after charging?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

greg_gorrell said:
Was that caused by the rom update? And did you let it die and then try to boot into recovery immediately after charging?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After month keeping device disconnected from battery I recharged it and tried to get into recovery mode. It doesn't worked, still stuck in constant loop showing Google logo and ClockworkMod Recovery v6.0.4.3. I recorded video so you guys can see what exactly I mean.

PCFixYa said:
After month keeping device disconnected from battery I recharged it and tried to get into recovery mode. It doesn't worked, still stuck in constant loop showing Google logo and ClockworkMod Recovery v6.0.4.3. I recorded video so you guys can see what exactly I mean.
Click to expand...
Click to collapse
Just boot into Bootloader and reflash the the whole ROM. Start from there.

khaytsus said:
Just boot into Bootloader and reflash the the whole ROM. Start from there.
Click to expand...
Click to collapse
I cannot boot into anything! It is constant bootloop.

PCFixYa said:
I cannot boot into anything! It is constant bootloop.
Click to expand...
Click to collapse
Bootloop implies that it's trying to boot into the ROM, which means you're not trying to get into the Bootloader which is where you need to be.
Hold power until you see the Google logo, then press and hold Vol down. If it powers back off/reboots, let go of the Power button sooner but keep holding the volume button.

khaytsus said:
Bootloop implies that it's trying to boot into the ROM, which means you're not trying to get into the Bootloader which is where you need to be.
Hold power until you see the Google logo, then press and hold Vol down. If it powers back off/reboots, let go of the Power button sooner but keep holding the volume button.
Click to expand...
Click to collapse
It doesn't work, every action I tried ended up with this bootloop which you can see few posts above... Thanks for trying to help btw

[Q] Please help w/bootloader

Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:

TAGTRAUM said:
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
Click to expand...
Click to collapse
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?

Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader

Circaflex said:
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Click to expand...
Click to collapse
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??

TAGTRAUM said:
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
Click to expand...
Click to collapse
Nope.. If adb doesn't work and volume buttons are broken, you're stuck. Get the buttons repaired.

rootSU said:
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Click to expand...
Click to collapse
No luck with running this commands in boot process

TAGTRAUM said:
No luck with running this commands in boot process
Click to expand...
Click to collapse
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?

gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
Adb should work from part way through the boot process and any mode. in custom recovery.

gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB

TAGTRAUM said:
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979

Evolution_Tech said:
Try this
Click to expand...
Click to collapse
Will try, but decide to repair my Vol- button myself, i have no mind what can be broken in this part, watching video of N6 dissassembly, its pretty simple part indeed Walking w/o Vol- for a month, and this situation is frustrating me and other situations can happen, in certain cases i still need Vol- :cyclops:

I need some help unbricking my fire...

Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!

Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.

Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740

hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36

blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.

blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.

I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..

blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!

Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.

drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.

I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.

I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!

So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!

drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?

thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip

drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.

thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.

What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.

blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery

watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4

Question Stuck on the fastboot screen

Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.

Bump.

Bump.

Bump.

Xenomorphs said:
Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.
Click to expand...
Click to collapse
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot

qwertz512 said:
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot
Click to expand...
Click to collapse
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.

Xenomorphs said:
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.
Click to expand...
Click to collapse
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.

hakudayo said:
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.
Click to expand...
Click to collapse
Thank you so much. I'm going to try.

Xenomorphs said:
Thank you so much. I'm going to try.
Click to expand...
Click to collapse
No problem if you have any questions just ask me

Now I'm stuck with this same issue.,
Got into this while trying to boot TWRP OrangeFox-R12.1_3_A12_FBEv2-Unofficial-lime.zip on xiaomi A12 ROM

Question [Resolved] No connection with pc in fastboot mode.

Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002

Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)

Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.

Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!