Related
Dear All,
I bought a Mi max 2 months ago, after using it some,i decided to change my rom.
What i did:
1)Unlock phone via mi
2)Usb debugger
3)TWRP
4)Supersu rooted
Everything was fine.
I downloaded a rom and flash it in fastboot mode and BUM! total darkness.
After some research , I managed to reach my phone via MiFlash.
Mi Flash now sees my phone as a port device Qualcomm....
I downloaded a correct rom.
So what is my problem !
In EDL mode,I start flashing, 2-3 seconds it flashes than it says `can not see port`(I downloaded all drivers,disable/able driver enfor...sth)
And phone turns in NULL mode, no connection any more from pc to phone.
If i disattached/attached battery and connect again to PC in EDL mode, i can reach it for a few seconds and than again losing connection.
I need my phone to keep connected to my pc untill i will finish flashing.
It is complicated, i am not even sure if it is possible or i damaged my motherboard.
What can i do???
Thanks in advance
i did a big mistake..i flashed redmi 6 pro rom to my a2 lite ..now nothing is happening...edl mode/fastboot mode is not accessing.i also show my phone to a service center. thaaaay just **** me they breaak my fingerprint reader.......help me to boot my phone i have to brought a back-part with finger print reader.please help me
absigma said:
i did a big mistake..i flashed redmi 6 pro rom to my a2 lite ..now nothing is happening...edl mode/fastboot mode is not accessing.i also show my phone to a service center. thaaaay just **** me they breaak my fingerprint reader.......help me to boot my phone i have to brought a back-part with finger print reader.please help me
Click to expand...
Click to collapse
Flash a proper stock rom, if you have a Mi A2 Lite phone through EDL mode this will revert a normal brick.
EDL mode is ever accesed, it might happen that device doesn´t start any kind of transfering data process through EDL, this means that your device is hard bricked in a way that motherboard can´t receive data so it´s damaged at hardware level but to prove this you have to first install the proper Qualcomm HS-USB qdloader 9008 drivers and see how is detected through device manager, it could be detected as Diagnostics 9006 with a warning symbol and then you have to update drivers, restart pc and re-start the process.
If then of bypass properly all the failures that XiaoMi flash tool can produce doesn´t work then the damaged was more serious.
If you unlocked previously (I guess you did it) then you can enter to EDL from a power off by holding both volume buttons at same time that you connect with pc -you have to first start the app and load the image- if device enters to EDL mode but the tool is not recognicing it the led light will stay on BUT if you entered correctly to EDL mode and also the tool is properly recognicing it (so the drivers were well updated) then the led light will flash intermitently.
At time to connect to pc in the mentioned steps you have not to receive any vibration just a sound from your pc.
In few words search in Google : test point mi a2 lite and do it
SubwayChamp said:
Flash a proper stock rom, if you have a Mi A2 Lite phone through EDL mode this will revert a normal brick.
EDL mode is ever accesed, it might happen that device doesn´t start any kind of transfering data process through EDL, this means that your device is hard bricked in a way that motherboard can´t receive data so it´s damaged at hardware level but to prove this you have to first install the proper Qualcomm HS-USB qdloader 9008 drivers and see how is detected through device manager, it could be detected as Diagnostics 9006 with a warning symbol and then you have to update drivers, restart pc and re-start the process.
If then of bypass properly all the failures that XiaoMi flash tool can produce doesn´t work then the damaged was more serious.
If you unlocked previously (I guess you did it) then you can enter to EDL from a power off by holding both volume buttons at same time that you connect with pc -you have to first start the app and load the image- if device enters to EDL mode but the tool is not recognicing it the led light will stay on BUT if you entered correctly to EDL mode and also the tool is properly recognicing it (so the drivers were well updated) then the led light will flash intermitently.
At time to connect to pc in the mentioned steps you have not to receive any vibration just a sound from your pc.
Click to expand...
Click to collapse
i cant access fastboot but it is connecting to edl mode but not getting flash.when its connect a sounds on pc but when not properly not in edl the notification light blinking.please help me.
Os_Herdz said:
In few words search in Google : test point mi a2 lite and do it
Click to expand...
Click to collapse
tnx bro but i know testpoint and i used that when my phones bootloader locked
SubwayChamp said:
Flash a proper stock rom, if you have a Mi A2 Lite phone through EDL mode this will revert a normal brick.
EDL mode is ever accesed, it might happen that device doesn´t start any kind of transfering data process through EDL, this means that your device is hard bricked in a way that motherboard can´t receive data so it´s damaged at hardware level but to prove this you have to first install the proper Qualcomm HS-USB qdloader 9008 drivers and see how is detected through device manager, it could be detected as Diagnostics 9006 with a warning symbol and then you have to update drivers, restart pc and re-start the process.
If then of bypass properly all the failures that XiaoMi flash tool can produce doesn´t work then the damaged was more serious.
If you unlocked previously (I guess you did it) then you can enter to EDL from a power off by holding both volume buttons at same time that you connect with pc -you have to first start the app and load the image- if device enters to EDL mode but the tool is not recognicing it the led light will stay on BUT if you entered correctly to EDL mode and also the tool is properly recognicing it (so the drivers were well updated) then the led light will flash intermitently.
At time to connect to pc in the mentioned steps you have not to receive any vibration just a sound from your pc.
Click to expand...
Click to collapse
now showing in mi flash as COM6 but when try to flash is says ''cannot read from COM6" help me
absigma said:
now showing in mi flash as COM6 but when try to flash is says ''cannot read from COM6" help me
Click to expand...
Click to collapse
How is detected under device manager? qualcomm-HS-USB qdloader 9008? Also what about behaviour of led light, it stays on all the time or it blinks?
Edit: Now I read your previous post, Led light has to blink, this is correctly connected, see under device manager how it is detected.
SubwayChamp said:
How is detected under device manager? qualcomm-HS-USB qdloader 9008? Also what about behaviour of led light, it stays on all the time or it blinks?
Click to expand...
Click to collapse
connected as qualcomm-HS-USB qdloader 9008 in device manager & the notification light is off when not in edl mode that time notification light blinks
absigma said:
connected as qualcomm-HS-USB qdloader 9008 in device manager & the notification light is off when not in edl mode that time notification light blinks
Click to expand...
Click to collapse
Ok, Behaviour changes depending on what rom you actually are, it´s mean that now you have flashed some partitions from Miui rom (led light will stay off) at least it´s being detected.
Things that you can try:
- Move the rom to the same folder where XiaoMi flash is.
- Rename the folder as short as better like "xiaomi" without quotes.
- Put your Windows in "Test Mode", restart to changes take effects.
- Switch to other version of the tool, it worked for me latest from here https://xiaomifirmware.com/downloads/miflashpro/
- Try with other rom version.
absigma said:
connected as qualcomm-HS-USB qdloader 9008 in device manager & the notification light is off when not in edl mode that time notification light blinks
Click to expand...
Click to collapse
i mconnect the battery now qualcomm-HS-USB qdloader 9008 in device manager & notification is blinking
absigma said:
i mconnect the battery now qualcomm-HS-USB qdloader 9008 in device manager & notification is blinking
Click to expand...
Click to collapse
Don't worry about led behaviour, your device will turn a bit weird cause you flashed a wrong firmware, the important here is that it's recognised by pc. What about the steps, tried?
So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.
Hi I recently try to flash a Stock Android One to my Xiaomi Mi a2 lite (Global Version of Redmi 6 pro).
I used Mi flashtool and I download a Fastboot Image file that matches my device model but my phone is bricked
the notification light is blinking when ever I push the power button. And I cannot know when my phone is charging there are no display that my phone is charging and when I press the Volume down and Power button I cannot access the Fastboot mode so I just simply attached my phone to the Computer and I shocked when I heared of a sound that my device was read by the computer but the phone is dead that time so I use the Miflash tool and It detect my phone but when I use powershell and command fastboot devices it doesnt recognized or detecting my phone.
So I decided to flash the rom to my phone because it can detect it, but Its taking too long to flash, 1500 seconds has passed but the flashing is not finish so I decided to unplug my phone but the xiaomi flash tool is still flashing so I thought that the app is corrupted so I just exit the app and open it again and do the flashing again but 2000 seconds has passed and still its the same thing I unplug the phone and the flashing still continue so I decided to stop it.
After some time I try to plug my device again but the computer dont recognized the phone anymore, the connected device sound has not triggered and the miflash tool has not recognized my phone anymore and the blinking notification light is not present too.
Please anyone help me I need this phone to attend my Online Classes please.
Similar situation here. Tried to flash Magisk. Stuck on a boot loop. Then I tried to flash Global a2 lite ROM.
Now my phone is stuck in EDL mode with 900E Drivers I see random numbers in MiFlash. When I install 9008 drivers I see the COM10 and the same random numbers on the device info in the MiFlash tool.
Taking like 30 minutes to flash and never ends. If someone has the Auto unbrick Mi a2 Lite software
please post it here so we can try to flash with this one.
Hey all,
So i've unlocked by bootloader, flashed a custom recovery to then proceed with LineageOS flashing. However it went completely wrong as on reboot i'm stuck with the bootloader unlocked warning and then a blackscreen.
I still have access to fastboot mode however it's impossible to flash a customer recovery ("No Such Partition") and also impossible to directly "fastboot boot recovery.img" as the phone simply reboots on the warning and then blackscreen.
The only solution seems to get the device to qualcomm EDL mode and reflash all with the MSM tool (which I have as well as all the drivers) however I cannot get my Oneplus 9 pro to EDL mode...
I've tried all the fastboot commands (fastboot oem EDL, fastboot reboot EDL, none of them work) as well as the combination volume UP + volume DOWN + plugging the cable (it just boots the fastboot mode.
Honestly would greatly appreciate any help as it is the first time in a decade I hard bricked a phone like this as it seems all the partitions are broken.
Make sure you have it unplugged when you do the button combos, as it will just start to boot while it's plugged in. Also, if you can reach fastboot, you can almost definitely reach EDL. Try unplugging and holding power+vol up for a bit which forces it to completely power off. Then try getting into EDL through the normal button combo/plugging. This is what I had to do since once it got into the booting/no-booting cycle I couldn't get to EDL.
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Good advice above.
Last time I couldn't reach EDL with my previous phone, it turned out to be an issue with the drivers I had installed. I uninstalled all Android-related drivers including some generic thing that showed up in device manager when plugging in the phone, then reinstalled the latest Qualcomm drivers.
Also possibly try a different USB cable if you have one. My OP9P didn't show up when the cable it came with was plugged into my USB-C port for some reason, but it worked fine with a generic Type-A to C cable I had sitting around.
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Tornadeur said:
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Click to expand...
Click to collapse
I can fix it bro pm me telegram .. @Hunar71
Hunar999 said:
I can fix it bro pm me telegram .. @Hunar71
Click to expand...
Click to collapse
Can you help me too, I have exactly the same problem…
If you use Windows, you need to see "QDLOADER 9008" in Device Manager > Portable Devices.
When you got this it will work, 100% .
It worked for me a few days ago. My laptop runs on Windows 11 x64. And only have usb 3.0. NO usb 2.0.
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Alberhasky said:
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Click to expand...
Click to collapse
Yeah make sure it's exactly the same name of that driver - worked for me on oneplus 9
If you have access to fastboot still. Try switching slots. Then going into EDL
For anyone looking for help, please DM me.
djsubterrain said:
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Click to expand...
Click to collapse
Thanks a lot man. Saved my Day. First 9Pro successfully restored ;-) Thank you and merry Christmas to all.
Guys I do not need to use the MSM Tool Anywhere until I reach the step where my device is being successfully detected as "QDLOADER 9008" in my windows device manager correct?
Or does the MSM Application need to be running when I reboot to EDL mode?
I am following this guide.
Please help
I always have phone powered off, and while holding both volume keys I plug it into USB cord(that is already plugged to pc) and then click on enum(button in msm screen) until it says connected then hurry and click start. Once it starts I can let go of volume keys.. Also more than likely u will need to click the box to "use lite firehose" or "Sahara communicaion" will keep failing.
make sure you have oneplus 9 pro drivers and " qaulcomm incorporated - Ports" Driver) and ("qaulcomm communications inc-Net" Driver) so your phone in edl which will be already most likely be running before you plug it in. just hold down both volume buttons and plug in to the usb port to your pc and release once plugged in and start the msm tool and hit enum it should say connect provided that you have all the necessary drivers above so the pc usb port will be able to communicate/recognize you device. its never usually A 1 and done type of thing. everytime i brick my phone its always the 100th try before i get a com port connected and the software communicating successfully, so just be patient and take your time. you will get it back up and running,
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
can't get into edl mode
how can I get oneplus 9 pro into edl mode while it's refusing to turn off? keep in mind that I can't use adb. but was able get fastboot devices command to work and I did not use any third party roms, didn't unlock the bootloader, and do not have...
forum.xda-developers.com
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
Well you have a corrupted boot.img or you would not be trying to edl. Also you probably are holding down multiple buttons to power off to your phone and your either not remembering or forgot that these combination of buttons are booting you into other modes fastboot, recovery or system.