ADB unauthorized when phone shutted off - Xiaomi Poco F1 Questions & Answers

Hello,
I have specific problem.
I was on the stock rom 10.3.6... with root and twrp installed. So I wanted to update to Miui 11 and I uninstall Magisk and done the update through the twrp.
So, in order to back magisk I wanna to go to twrp via fastboot and PC. But I am constantly getting message "ADB devices unauthorized". Anyway... this is only happening when phone is shutted off(in order to go to fastboot mode). When phone is turned on everything is fine and I can se device via adb command prompt. I tried any written solution on internet but nothing could solve the problem. When I connect turned on phone I regularly get the question to authorize phone and I click ok. And while phone is turned on everything is fine and I have accsess to internal and external memory of phone.
Is there any possible solution to solve this stuck ? Is there some other way to boot into twrp besides fastboot ? For now I would skip installing magisk via stock recovery or without twrp access.
Thanks infront !

This is how its susposed to work. Device should be online when turned on, and not when off. This is first time i heard someone try to connect device wiht adb via fastboot.

EugenStanis said:
This is how its susposed to work. Device should be online when turned on, and not when off. This is first time i heard someone try to connect device wiht adb via fastboot.
Click to expand...
Click to collapse
Thank you for reply.
I think that the reguar way for boot into twrp via pc is that your phone is turned off. Than you connect with pc and start adb commands. I dont understand, really.
Ok, how can I boot into twrp without pc if dfe is not flashed ?

visinacgile said:
Thank you for reply.
I think that the reguar way for boot into twrp via pc is that your phone is turned off. Than you connect with pc and start adb commands. I dont understand, really.
Ok, how can I boot into twrp without pc if dfe is not flashed ?
Click to expand...
Click to collapse
You use fastboot instead of adb commands when phone is off. Put your phone in fastboot mode and type commands like fastboot boot (drop your twrp image here) and hit enter

EugenStanis said:
You use fastboot instead of adb commands when phone is off. Put your phone in fastboot mode and type commands like fastboot boot (drop your twrp image here) and hit enter
Click to expand...
Click to collapse
Yes. My mistake... huge. Thank you. I forget tottaly.
Should I delete this thread ?

visinacgile said:
Yes. My mistake... huge. Thank you. I forget tottaly.
Should I delete this thread ?
Click to expand...
Click to collapse
No problem. Leave it like it is for other users :highfive:

Related

[Q] Can I use ADB while the phone is in bootloop??

hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!

[Q] DNA stuck in boot loop, Supercharged Hatka DNA ROM (1 Litecoin bounty for help)

Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Esploded said:
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Click to expand...
Click to collapse
Do you have adb? If you do the command is adb reboot recovery. Need to know more it just cycles? If so then try to push both power button and and both volumes until it has lights flashing at the bottom and reboots dont let go until it reboots. Other then that I am not sure. I tried to boot to recovery the manual way and it doesnt work. Which is why i Always use that to reboot recovery. Wait, I figured it out. Hold down volume power dont let go until bootloader comes up then let go of both. use volume down and select recovery and bam!
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
jhr5474 said:
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
Click to expand...
Click to collapse
I'll give the fastboot utility a shot, hopefully it works. Thank you
Esploded said:
I'll give the fastboot utility a shot, hopefully it works. Thank you
Click to expand...
Click to collapse
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
jhr5474 said:
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
Click to expand...
Click to collapse
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Esploded said:
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Click to expand...
Click to collapse
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
jhr5474 said:
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
Click to expand...
Click to collapse
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Esploded said:
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Click to expand...
Click to collapse
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
sdamark said:
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
Click to expand...
Click to collapse
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Esploded said:
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Click to expand...
Click to collapse
No, If you have twrp use adb push and push a rom to your phone and then flash it and your fine.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
If you can get into your rom, go to settings..power and at the bottom disable fastboot
Esploded said:
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
Click to expand...
Click to collapse
1. Charge your phone (about 24 hours).
2. Let him rest (about 24 hours) without turning on.
3. Connect device to PC with original wire (Win7 preferred).
There is possibility that your BB will recognize phone.

Need help with bricked Redmi Note 3 Pro (Kenzo/Snapdragon)

Dear Community,
I got my Note 3 Pro Snapdragon Version today and I tried unlocking the bootloader, installing root and TWRP.
Unfortunately after I installed TWRP, WiFi didnt work anymore so I wanted to go back to where I was before.
i tried flashing the GlobalRom with the MiFlash Tool but somehow I'm now stuck with a bootloop.
The phone starts up and shows the MI Logo but doesnt go on. I tried booting TWRP temporarily via fastboot commands so that I can try to flash flashable zip files
but it doesnt let me execute "fastboot boot xyz.img" anymore because my device is locked.
I would really love to hear any solutions or ideas. I dont want any root or something anymore. If someone has an idea Im very happy!!!
thanks a lot in advance and tell me if you need any more infos
Paul/shisaya24
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Alex3oe said:
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Click to expand...
Click to collapse
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
search miui forum for unbrick, there is 2 or 3 method without opening your device
exp: http://en.miui.com/forum.php?mod=viewthread&tid=257227
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
shisaya24 said:
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
Click to expand...
Click to collapse
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Dharani_V said:
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Click to expand...
Click to collapse
Can I do the test point thing myself or is it risky?
What kind of service center? A general mobile phone repair shop or a Xiaomi special one?
shisaya24 said:
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
Click to expand...
Click to collapse
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
I will try that this evening when I am at home again and report. Thanks
Alex3oe said:
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
Click to expand...
Click to collapse
Unfortunately this doesnt work. Phone reboots and shows MI Logo but red light doesnt blink and MiFlash doesnt recognize any devices.
Do you have another idea? :/
How did you unlock the bootloader, via official permission or that unofficial hack?
Sent from my Moto G using Tapatalk
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
shisaya24 said:
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
Click to expand...
Click to collapse
Only options you have right now are:
1) using test points method which is a but cumbersome and voids warranty if you care about that.
2) go to a xiaomi service center of you have any nearby.
It is hard bricked.
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
shisaya24 said:
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
Click to expand...
Click to collapse
Apparently, no! Whenever using unofficial methods, read precautions carefully and you missed all as I can see. Wait if someone can help you out.
apply official unlock. then unlock your device from fastboot mode.
asaharaSK said:
apply official unlock. then unlock your device from fastboot mode.
Click to expand...
Click to collapse
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
shisaya24 said:
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
Click to expand...
Click to collapse
Does anyone know this?
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
smiley1960 said:
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
Click to expand...
Click to collapse
out of sheer desperation I tried MiPhone again and after a few tries, MiPhone started updating the OS. My phone now works again and I have an unlock code as well.

Fastboot mode disappeared in 10 seconds...How to solve

When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Smart Sujoy said:
When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Click to expand...
Click to collapse
Your computer is unable to detect the phone in fastboot mode. Uninstall and reinstall the fastboot drivers, the proper ones. If successfully detected it should not be rebooting.
Cheers
ArK96 said:
Your computer is unable to detect the phone in fastboot mode. Uninstall and reinstall the fastboot drivers, the proper ones. If successfully detected it should not be rebooting.
Cheers
Click to expand...
Click to collapse
I just try this...but nothing happened...
Smart Sujoy said:
I just try this...but nothing happened...
Click to expand...
Click to collapse
That ten seconds when phone is turned on in fastboot and connected to computer quickly type this command in command prompt without the quotes
" fastboot devices "​If a device with device number shows up fastboot drivers are installed correctly or else if nothing shows up fastboot drivers are not installed properly..so check them.
Smart Sujoy said:
When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Click to expand...
Click to collapse
i actually watched this video, to unlock my bootloader
https://youtu.be/dDRC-J-cLlE
Smart Sujoy said:
When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Click to expand...
Click to collapse
Im having this issue now on my redmi note 4x.
Do you have a solution? Thanks
Man, you need adb bootloader interface installed properly.
Open device manager, and you'll see something popping out when you connect your device to pc on fastboot mode, there you can see what's wrong. So all you need is update that wrong driver (the one that popped out once you connect your device in fastboot mode) and install redmi note 4x driver, just ignore your disappearing fastboot mode in your device, keep install it. You should have your redmi note 4x driver prepared btw, you can google it.
Good luck!
use USB2 port, do not use USB3
Smart Sujoy said:
When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Click to expand...
Click to collapse
Update your redmi note 4 driver in PC through a software called driver booster.... It's free
AtheistZ said:
Update your redmi note 4 driver in PC through a software called driver booster.... It's free
Click to expand...
Click to collapse
NO ADS!!!!
and2nckiko said:
Im having this issue now on my redmi note 4x.
Do you have a solution? Thanks
Click to expand...
Click to collapse
That is because your computer does not make any connection with your phone. Are you sure that you have all drivers installed. You can install fastboot drivers with mi flash tool but before that write this command in an admin cmd - bcdedit /set TESTSIGNING OFF and reboot. Now you can now install the fastboot driver from mi flash tool and try your luck
ArK96 said:
That ten seconds when phone is turned on in fastboot and connected to computer quickly type this command in command prompt without the quotes
" fastboot devices "​If a device with device number shows up fastboot drivers are installed correctly or else if nothing shows up fastboot drivers are not installed properly..so check them.
Click to expand...
Click to collapse
Bro my bootloader is already unlocked but my phone still restarts after 10 second i did not connected to any usb still it restarts i updated magisk today and now nothing is working in my phone no call incomming and outgoing audio is fully disabled when i turn on audio in any app it crashes or freezes i tried to factory data reset my phone but nothing works plzz help me broo
Leeeop90 said:
Bro my bootloader is already unlocked but my phone still restarts after 10 second i did not connected to any usb still it restarts i updated magisk today and now nothing is working in my phone no call incomming and outgoing audio is fully disabled when i turn on audio in any app it crashes or freezes i tried to factory data reset my phone but nothing works plzz help me broo
Click to expand...
Click to collapse
My root is also lost
JustExperimentingRedmi said:
That is because your computer does not make any connection with your phone. Are you sure that you have all drivers installed. You can install fastboot drivers with mi flash tool but before that write this command in an admin cmd - bcdedit /set TESTSIGNING OFF and reboot. Now you can now install the fastboot driver from mi flash tool and try your luck
Click to expand...
Click to collapse
So drivers are needed for fastboot flashing a xiaomi phone?
Why I didn't need drivers to use fastboot with other phone manufacturers?
In these phones (oppo, op) the phone stays in fastboot mode until you exit or shut it down.
I think xiaomi did a bad move with this.
───────
EDIT: It works in debian without any additional drivers.
Fastboot recognizes the xiaomi phone with "fastboot devices" command.
So it was as you said.

Sharp Aquos S2 stucked in Download mode

Hi:
My unlocked bootloader SS2 phone got stucked in Download Mode after successfully installed/flashed AICP ROM
It booted once and when i rebooted to enter recovery got stucked. Tried pushing buttons combos but still stucked in Dmode.
Have no access to fastboot from Windows but can get limited access to fastboot in Debian: can flash several twrp recoveries, can flash
AICP ROM again but can not get fastboot oem commands working.
Can't enter to recovery because phone never turn off.
Tried also to come back to Nougat but can't enter recovery to flash ss2_old_bootloader.
I do not know what to do.
Any help?
Also have this problem... any help?
have u try to connect into computer, use adb, and use this command :
Code:
fastboot reboot
what's the result with that?
No connection.
But i have reinstalled OST Treble ROM and phone now working.
gsausalito said:
Hi:
My unlocked bootloader SS2 phone got stucked in Download Mode after successfully installed/flashed AICP ROM
It booted once and when i rebooted to enter recovery got stucked. Tried pushing buttons combos but still stucked in Dmode.
Have no access to fastboot from Windows but can get limited access to fastboot in Debian: can flash several twrp recoveries, can flash
AICP ROM again but can not get fastboot oem commands working.
Can't enter to recovery because phone never turn off.
Tried also to come back to Nougat but can't enter recovery to flash ss2_old_bootloader.
I do not know what to do.
Any help?
Click to expand...
Click to collapse
I also have problem after flashing to AICP and sometimes phone (after power off) stuck in Download mode.
Just enter:
fastboot --set-active=a reboot
rgr1 said:
I also have problem after flashing to AICP and sometimes phone (after power off) stuck in Download mode.
Just enter:
fastboot --set-active=a reboot
Click to expand...
Click to collapse
I have the same problem. I tried to follow your advice, but fastboot in my PC doesn't recognize the parameter (all I get is fastboot help page).
Regards.
EDIT: reinstalled treble v3.1 via OST and it fixed the download mode issue.
thanks!
hi,
got the same problem, stuck at download mode but phones can`t to pc via usb so I am unable to use fastreboot.
Any other suggestions how to fix it ?
internety1 said:
hi,
got the same problem, stuck at download mode but phones can`t to pc via usb so I am unable to use fastreboot.
Any other suggestions how to fix it ?
Click to expand...
Click to collapse
in my xperience is connect your phone to the PC then open cmd ... make sure in folder of adb and fastboot .exe stored ...
type:
Code:
fastboot continue
longu said:
I have the same problem. I tried to follow your advice, but fastboot in my PC doesn't recognize the parameter (all I get is fastboot help page).
Regards.
EDIT: reinstalled treble v3.1 via OST and it fixed the download mode issue.
Click to expand...
Click to collapse
Maybe use other fastboot.
Sometimes you must enter:
Code:
fastboot --set-active=_a reboot
("_a" instead of "a")
BTW. My Aquos sometimes stuck in download mode after installing AICP.
I fixed this by entering:
Code:
adb shell
bootctl mark-boot-successful
Hello, i have the same exact problem. I tried to use adb program to fix this problem, but my laptop couldn't recognize my device. Any other solutions would be helpful. Thanks for your attention! (I'm a beginner in technology, so please forgive me)

Categories

Resources