Redmi 6 Pro - Device won't stay on fastboot mode, recovery stuck at boot logo - Xiaomi Redmi 6 Pro Questions & Answers

I newly installed PE ( based A12 ) with orangefox recovery, but now whenever I go to the recovery it never gets past the orangefox logo. My device was not rooted, and from what I've read it looks like this was caused because the recovery was not " FBE ". Then I tried flashing TWRP, but the device won't stay on fastboot mode, with or without the USB connected, I would put it on fastboot (tried from both cmd and volume down + power button) and it will stay on fastboot for a few seconds (about 30 seconds) then shut down.
I tried different ports and reinstalled platform tools and appropriate drivers, those did not fix the problem, so I thought this might be because of some app that I might have installed, so I reset the phone, and now it does not have a ROM. The device is still not booting into recovery or staying in fastboot.
Some other info on the device-
- I had an unlocked bootloader before doing this and also had no problems with the recovery.
- I also did a clean install for the ROM.
- The device had no problems in getting detected on the PC. I also had USB debugging enabled.

Update: I've fixed it.

how did you fix it?

i'm having same problem since yesterday.
please help me fix this issue

So firstly, the device not being recognised when I typed ' adb devices ' and shutting down after a few seconds of being on fastboot with usb attached.
To fix this, I had to go to ' device manager ' on my pc and then connect the phone via USB ( in my case the phone was only in fastboot for a few seconds before it shut down and I also did not have any rom installed, and could not go into recovery ), then in device manager, the device name would be shown ( under portable devices ), right click > update driver > browse for drivers your computer.
doing this fixed the problem where the device was not staying in fastboot.
Then I had to fix where the device won't load into recovery and will be stuck on the start screen forever ( I had orange fox recovery installed )
To fix this, I went to fastboot on my device and then I had to type the following command: fastboot -w ( This command erases everything from the device )
After doing these, everything was pretty much done, all I had to do next was go to fastboot, install a recovery and flash a rom.

Dynamo01 said:
So firstly, the device not being recognised when I typed ' adb devices ' and shutting down after a few seconds of being on fastboot with usb attached.
To fix this, I had to go to ' device manager ' on my pc and then connect the phone via USB ( in my case the phone was only in fastboot for a few seconds before it shut down and I also did not have any rom installed, and could not go into recovery ), then in device manager, the device name would be shown ( under portable devices ), right click > update driver > browse for drivers your computer.
doing this fixed the problem where the device was not staying in fastboot.
Then I had to fix where the device won't load into recovery and will be stuck on the start screen forever ( I had orange fox recovery installed )
To fix this, I went to fastboot on my device and then I had to type the following command: fastboot -w ( This command erases everything from the device )
After doing these, everything was pretty much done, all I had to do next was go to fastboot, install a recovery and flash a rom.
Click to expand...
Click to collapse
thanks bro. fastboot -w fixed everything

Related

[RECOVERIES & ROOT] Yureka custom recoveries & Root without Changing Stock Recovery

[RECOVERIES & ROOT] Yureka custom recoveries & Root without Changing Stock Recovery
Note : This tutorial is for YU Yureka based on CM11 (KK 4.4.4) 32bit architecture
and
do it on your own risk, I will not be responsible if you brick your phone
Here is the detailed guide and collection of stock and all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Put your phone into FASTBOOT mode by following anyone from below methods :
Method 1 (easiest)
-------------------
a. Power down phone
b. Plug USB cable to your PC
c. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
Method 2
---------
a. While your phone is Power On, plug USB Data Cable with PC and Phone (USB Debuging must be Enable)
b. Open Command Prompt on your PC (with Administartor rights) and type the following command
adb -s 0x1ebf devices
You will get results something like that :
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
3a289c2 device
*Note : If you get "authorization message" then look on your mobile screen and authorize your PC and run the command again.
c. Now note down the device no. (for e.g. in above "3a289c2") and type the following command
adb -s 3a289c2 reboot bootloader
[*Note replace the device id with your id (here 3a289c2), that you got in last command]
Now your phone must be booted into fastboot mode. A screen with "Fastboot Mode" should be appear on your phone.
3. Device drivers will get installed by windows (please wait for the driver installation to complete)
4. After driver installation is done go to the folder where you have extracted the package
5. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
(*Note : to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here")
6. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
7. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
8. Now your bootloader is now unlocked.
*Note : if you want to re-lock your bootloader again (for warranty on any other reason), again boot into fastboot mode and this time type the following command and enter
fastboot -i 0x1ebf oem lock
Step Three
Boot your phone into recovery (temporarily or permanently) and root your phone
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot CWM_6.0.5.1_recovery-yu.img
*Note 1 : if you want to flash the custom recovery permanently then us the following command
fastboot -i 0x1ebf flash CWM_6.0.5.1_recovery-yu.img
*Note 2 : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above commands you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
3. Done ! You loaded custom recovery temporarily, if command used with "boot" hence to root your phone, proceed to next section (step 5).
or
If you flashed recovery permanently, using command with "flash" then boot your phone into recovery. To do so, you have Two options
i) type the following command and press enter : adb -s 3a289c2 reboot recovery
or
ii) power off your phone, after then press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
Now to root your phone proceed with next section (step 5).
Root your phone
5. To gain root access, flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
6. Choose reboot phone and enjoy rooted phone with stock or custom recovery !
Special Note 1
I didn't tested, but came to know that root doesn't effect OTA update on Yureka.
You can get OTA updates with root but after the OTA update is flashed you will loose root access. To keep it or to avoid this please go to System Settings -> Developer Options -> UNTICK -"Update CM Recovery" (update recovery while installing system updates)
Even though if someone want to go back to Stock recovery, then download the official stock recovery (link no. 6 above) and flash it using command in fastboot mode (second command in step 2 under head "STEP THREE")
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
6. YU Yureka Official Stock Recovery http://d-h.st/tQ1k
Special Note 2
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command
aabidhashmi said:
Here is is collection of all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Power down phone
3. Plug USB cable to your PC
4. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
5. Device drivers will get installed by windows (please wait for the driver installation to complete)
6. After driver installation is done go to the folder where you have extracted the package
7. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
* to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here"
8. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
9. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
10. Now your bootloader is now unlocked.
Step Three
Root your phone without changing your stock recovery
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot recovery CWM_6.0.5.1_recovery-yu.img
*Note : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above command you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
Done ! You flashed custom recovery temporarily.
3. Now press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
4. To gain root access flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
5. Choose reboot phone and enjoy rooted phone without changing stock recovery !
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
Special Note
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command
Click to expand...
Click to collapse
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking
aashking said:
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking
Click to expand...
Click to collapse
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.
aabidhashmi said:
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.
Click to expand...
Click to collapse
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking
arjunsingh1000 said:
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking
Click to expand...
Click to collapse
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...
aabidhashmi said:
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...
Click to expand...
Click to collapse
Great mate cheers just checked and tried that ota updates are available and work.. On stock recovery... Locked bootloader and with root..
Achieved this by downgrading to the very first cm11 firmware and got then rooted it and locked the bootloader then I just booted it and got the incremental update .. Downloaded and flashed .. Works perfectly.. Root not lost due to the untick in dev options..
Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk
I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.
aabidhashmi said:
Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Well I guess you are on the latest build XN0PHQ I guess? Another beta update was made but not rolled out it is um XNPH08P I know its a little late but just in case you don't know..
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
jitendragarg said:
I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.
Click to expand...
Click to collapse
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.
arjunsingh1000 said:
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.
Click to expand...
Click to collapse
I tried this method but phone does not get detected in fastboot mode at all. I have drivers installed for all different modes I connect my phone as. No luck at all.
Also, weird thing is, I have an option to directly go to fastboot mode from the power menu.
Jitendra Garg
Your driver's are not installed
As there is no special drivers setup, so connect your PC with Internet then plug your phone and let Windows install drivers automatically.
Sent from my AO5510 using Tapatalk

I have messed up, I don't know where to turn. HTC One M8 softbricked in Bootloop.

I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img
ckpv5 said:
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Thank you for reply!
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now. It does not appear under the devices list. If I can just get adb talking with my phone everything else should be easy, I just can't figure out why it's not recognizing it.
Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
Click to expand...
Click to collapse
Gitnerd said:
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now.
Click to expand...
Click to collapse
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
Gitnerd said:
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!!
Click to expand...
Click to collapse
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img
ckpv5 said:
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Oh.. My..God..
You just saved my life, this whole time I thought fastboot utility in AndroidSDK was just a stripped version of ADB. I'm a moron!
I have TWRP up and running holy crap thank you so so so so much, you are seriously a life saver.
try this
Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
Click to expand...
Click to collapse
1) Reboot the phone using Power+Vol Up
2) The moment the screen goes dark to reboot and before the white HTC logo screen appears again (Should be around 10 seconds), press the volume down key.... Do not let go of vol down until you see the bootloader screen
3) If the bootloader doesn't appear, you either started pressing Vol Down too late, or let go of it too early. Just do the steps again until you get it right.
4) Once you are in the bootlader, select select fastboot by pressing power key.
5)you can flash either permanent or temporary a TWRP recovery once you are in fastboot.
6)Once you are in recovery mode, you can transfer any custom rom to memory or sd card, then install it from the place you chose.
7) you can flash RUU file at fatboot mode as well.

problem with fastboot twrp flashing

my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful
i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this
Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?
otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so
Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp
Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.
If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.
”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed(too many links)and "press any key to reboot" showing on my phone's fastboot screen
Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.

Can't fastboot files

I flashed a custom rom Long time ago. I want to update now because my phone has some weird glitches and updates are available. When I go into recovery i get into Mi recovery (not twrp which I used to have? don't know for sure)
I use FWUL since windows didn't work (usb debuggin enalbe and phone is unlocked). I want to flash TWRP. My device is recognized (both 'normal' and in fastboot). When I tried to flash new file it stops @ sending file fo or sometimes waiting for device (while fastboot devices 2sec before recognized my phone)
What I tried
- fastboot from phone itself and connect (same result)
-when in fastboot en give reboot command, it says rebooting but the phone doesn't restart
so it seems the fastboot doens't work?
any solutions?
thanks in advance

Xiaomi A2 lite : unable to flash a recovery

Hi, I want to move to a custom ROM on my A2 Lite. But before anything else, I need to backup my phone.
1st step : TWRP recovery.
On the PC, ADB driver is installed. Phone powered and connected, I have no problem to send ADB command to phone. "adb reboot bootloader" for example.
But once the phone is in fastboot (logo on screen), it is not recognized by PC (no driver) and I can"t send Fastboot command.
Any hint ?
Thanks.
Ok, I found a solution.
Downloading Google USB Driver but installation procedure is wrong, I should FORCE it and manually assigne the driver "Android Device / Bootloader" to be able to connect in Fastboot mode.
fastboot oem unlock
-> Reboot with the warning message but wipe all data. It's the only I found to unlock the bootloader :/
fastboot oem edl
-> Not the solution to flash the new ROM
fastboot boot twrp*.img
-> Way better to get the recovery flashed

Categories

Resources