I am having a REAL BUGGER of a time with my Xiaomi Redmi Note 3 Pro (Snapdragon)!
1. It is not recognized by ADB in Fastboot mode.
2. I suspect it shipped wit a vendor ROM, and I'm trying to flash latest Official MIUI Global Dev (Marshmallow) ROM, but I keep getting errors in MI Flash (screenshot attached).
3. I want to Flash TWRP, BUT ADB isn't working, AND I cannot get to the download page for the cracked bootloader.
4. Seriously considering Resurrection Remix ROM, instead, but most of the above issues still apply.
I am NOT new to custom recoveries, flashing ROMS, ADB etc, BUT I am dealing with a new PC (Windows 10 Home, 64 bit, like my old (dead) laptop), and I'm new to this device.
PLEASE HELP. (Quite frustrated)
Fastboot won't recognize adb commands you have to use fastboot.
What you can try is booting into emergency download mode and using my flash to flash it from there. I think it's " adb reboot edl" while the device is on with USB debugging or using the mi updater app ( tap the three dots I think).
I think that this is not the correct section for your question, and i dont know the procedure that you follow but try to follow this procedure:
-Connect the phone at pc with USB cable
-Make sure that debug mode and OEM unlock was abilitate in dev settings
-Copy twrp.img in adb folder
-Shut down the phone and press power botton and - vol buttons for enter in fastboot mode
-Run this commands by terminal open in adb folder
fastboot devices
-If fastboot recognize correctly the device run this command
fastboot fash recovery nameoftwrp.img
-After reboot the device with this command
fastboot reboot
When the phone reboot press immediatily vol + for enter in twrp
Good luck
GOT IT! FINALLY!
-I finally got ADB to connect, and was able to enter EDL through ADB.
-Re-downloaded ROM from web.
-Re-extracted.
-FLASHED SUCCESSFULLY!
-SETUP COMPLETED SUCCESSFULLY!
-YAY!
(I think the original download was corrupted, somehow.)
Hey friends i was able to unlock bootloader of my REDMI NOTE 3 OFFICIALLY.
I wan to root the device and install TWRP but for tat i have to connect my phone in fastboot mode.
The thing is phone is recognised as an adb device when it is on but after putting the phone in fastboot mode my laptop is not showing in cmd after " fastboot devices" command
plz help if anyne know how to fix this.
How are you putting it in fastboot mode?
did you already install correct driver in your pc?
you can try to instal latest mi pc suite which will help you to instal correct driver for your phone.
If you're already success unlocking with official way..then it's mean your fastboot driver already correct (if you're using the same computer when you're unlocking before)
Maybe i think you're missed something to put your phone into fastboot mode..
First way you can go into fastboot mode with ADB command while your phone already ON, just typing command "adb reboot bootloader" then enter..your phone will reboot into fastboot mode
Second way to go into fastboot mode firstly you must turn off your phone..just wait until that phone is truely OFF..
then press and hold volume down button..then followed with pressing and hold power button..your phone will booting into fastboot mode.
At first, I installed the Windows 10 drivers and the first time I put my phone in Fastboot & Rescue mode it showed up on the ADB and I could unlock the bootloader, then I wanted to install TWRP but now the device doesn't show up anymore in the bootloader mode... Any ideas? I also tried Ubuntu with no success But I can clearly see it in the device manager.
What does the command "fastboot devices", when in fastboot obviously, return?
Estatus del problema
Hi i have the same problem can you to resolve it???
m4xxi said:
At first, I installed the Windows 10 drivers and the first time I put my phone in Fastboot & Rescue mode it showed up on the ADB and I could unlock the bootloader, then I wanted to install TWRP but now the device doesn't show up anymore in the bootloader mode... Any ideas? I also tried Ubuntu with no success But I can clearly see it in the device manager.
Click to expand...
Click to collapse
hi there, I have a xiaomi device that only goes in fastboot mode. Putting out of fastboot results in a reboot and after that black screen.
-No way to flash with miflash because it needs your phone to be unlocked.
- i cant put the phone in edl because usb debugging needs to be on and i cant go in settings.
phone got detected by my pc when in fastboot mode
What to do now???
daveve said:
hi there, I have a xiaomi device that only goes in fastboot mode. Putting out of fastboot results in a reboot and after that black screen.
-No way to flash with miflash because it needs your phone to be unlocked.
- i cant put the phone in edl because usb debugging needs to be on and i cant go in settings.
phone got detected by my pc when in fastboot mode
What to do now???
Click to expand...
Click to collapse
I don't see any other way, my opinion is that you should unlock it.
HIT THANKS IF FOUND USEFUL
unlock is not possible because you need to put on usb debugging and oem unlock in developer settings but my phone dont start up.
Hi , tell me did you check if your device is recognised in ADB & fastboot command tool ?
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
Don't own this device but try: "adb reboot bootloader" instead and test fastboot commands from there (don't navigate to Fasboot from bootloader).
krugm0f0 said:
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Click to expand...
Click to collapse
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Zombnombs said:
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Click to expand...
Click to collapse
I am unable to send fastboot commands. Is not recognized by "fastboot devices". And this fastboot mode looks nothing like my previous phones. 2, X, 5T and Nord 5G. <waiting for device>
I want to do my "usual routine" with my new phones. Unlock, flash twrp or other recovery, and flash magisk for root.
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
nothing. only recovery mode
vol down+ power =recovery mode
vol up + power = normal boot
I finaly boot into fastboot mode with adb command only (adb reboot bootloader)
With buttons wont work.
But i can't enable Volte/Vowifi (thats why i wanted to boot there).
Can you send adb commands when in recovery mode ?
I'm trying to enable VoLTE too, but adb only detect phone when powered normaly, not when in recovery mode.
i don't know about adb but in fastboot you can.
I can't enable volte/vowifi in fastboot with this commands.
https://androplus.org/wp/wp-content/uploads/2021/08/onr12.jpg
Fastboot commands start with fastboot, those are adb commands.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
i am having the same issue can any one help
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
pls contact me in 9650930525 in this number and help me how u did it
drkanurag said:
i am having the same issue can any one help
Click to expand...
Click to collapse
pankspoo said:
On Android 12 OnePlus removed fastbootmode so no unlocking nothing.
But how did u booted in fastbootmode on oos 12 i can't understand
Click to expand...
Click to collapse
roldev said:
Downgrade to latest A11. Unlock via fastboot. Do what you want, then. All explained here or/and telegram group. Sorry, don't have time to do step by step guide now. Cheers.
Click to expand...
Click to collapse
Follow this guide to downgrade to A11 https://community.oneplus.com/thread/1596759
Then you should be able to access fastboot.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
Could you go into more detail on what you did in the entire process exactly? Did you use the drivers and adb install from the 15 sec installer? Did you simply uninstall them in the Windows Device Manager and click on "update drivers" to find the local drivers from the 15 sec installer? Which ones did you choose? Sorry, these might be dumb questions, but I'm admittedly very stupid when it comes to Windows and drivers in particular.
I did the exact thing I described above but I'm still just getting that message. Additionally, "fastboot devices" won't list anything and "fastboot oem unlock" will wait for the device for eternaty. "adb devices" on the other hand will list my device while not in Fastboot.