Hello friends, I tried to install the twrp for my xiaomi redmi note 9, but unfortunately the file was damaged and now my cell phone does not enter fastboot mode and does not turn on either, I connect it to the pc and it activates the adb mode, I execute the commands:
adb reboot recovery
adb reboot-bootloader
and the cell phone restarts but still does not work.
Could you help me how to solve the problem.
Note: I tried to repair the recovery by shell mode but it didn't work for me. (I don't understand the issue well)
I appreciate your help.
Related
Hi, I've a P20 pro with bootloader unlocked
I was trying to get Magisk on EMUI 9 . Restarting device then boot normaly with all my apps but no magisk and no root, when I wish to enter again a fastboot mode the phone has restart in normal mode, same thing with eRecovery,
I try with adb , buttons and nothing, only normal mode (system)
update: ADB works, with tool ALL IN ONE can enter sideload file manager
update2: finally I can enter fastboot mode with keys only when usb is connected
Hi everyone I need some serious help. I unlocked my bootloader just fine then booted into TWRP using the command
Code:
fastboot boot twrp-3.3.1-0-jasmine_sprout.img
after that used the ADB sideload button in TWRP. I used this command
Code:
adb sideload twrp-installer-3.3.1-0-jasmine_sprout.zip
which didn't work and then I eventually advanced wiped my device. The reason it didn't work ios because my xiaomi mi a2 isn't recognized as a ADB device, it only get recognized as a fastboot device. It is now stuck in a boot loop and can only boot into recovery. Any help would be appreciated.
Mactroiy said:
Hi everyone I need some serious help. I unlocked my bootloader just fine then booted into TWRP using the command
Code:
fastboot boot twrp-3.3.1-0-jasmine_sprout.img
after that used the ADB sideload button in TWRP. I used this command
Code:
adb sideload twrp-installer-3.3.1-0-jasmine_sprout.zip
which didn't work and then I eventually advanced wiped my device. The reason it didn't work ios because my xiaomi mi a2 isn't recognized as a ADB device, it only get recognized as a fastboot device. It is now stuck in a boot loop and can only boot into recovery. Any help would be appreciated.
Click to expand...
Click to collapse
Hello Mac,
Are you running the commands from the adb directory? Example, adb devices which typically would show your xiaomi mi a2 device.
Is the Android USB driver showing as adb in device manager?
I have the very same device, it is a little tricky since it has an a and b partition and you have to be precise when installing a custom ROM. Here's a how to that may be of help to you, it definitely helped me a lot.
Good luck!
[ADB | FASTBOOT | LINUX COMMANDS] BootLoader, Kernel, Recovery, ROM, Root, Backup
Mactroiy said:
.... then I eventually advanced wiped my device...
Click to expand...
Click to collapse
What did you wipe? If anything except Dalvik Cache and/or Cache, then most probably you'll have to reflash stock ROM in fastboot.
Mactroiy said:
The reason it didn't work is because my xiaomi mi a2 isn't recognized as a ADB device, it only get recognized as a fastboot device. It is now stuck in a boot loop and can only boot into recovery. Any help would be appreciated.
Click to expand...
Click to collapse
If "Android Portable Device" drivers are installed correctly (and PC has USB2.0 slot and/or USB 3.x slot compatible with MiA2, which happens not so often), still ADB (if I am not mistaken) sees connected phone if it is
1) booted normally, USB Debugging is On, MTP is On, and ADB with this PC have been validated in phone (and still ADB has limited functionality depending on kernel), or
2) booted into TWRP
You can check ADB connection using "adb devices -l",
- if command shows nothing, then either drivers not installed or USB port is failing or nothing compatible booted in phone,
- if command shows unauthorized transport id, then you have not approved ADB in phone
If phone is in fastboot mode, then, with drivers installed and USB port being compatible, "fastboot devices" shhould show attached phone, and if it is fully unlocked, stock fastboot ROM can be reflashed
Kinda noob here
Alcatel tru 5065n metropcs
LG journey L322DL tracfone
the Alcatel cant boot. Stuck at logo. Recognized by fastboot but not accepting any commands with error. I could get into edl/qdl mode but cannot qdl flash anything. I get the errors from this post
[GUIDE] unbrick and flash Official ROM in EDL on linux
hi, i'm with issues here... the device - xiaomi redmi note 5A (ugg) - is dead. i'm managed for put it in edl mode, just blink the led, and this is what i receive in terminal: $ ./qdl --debug --storage ufs --include...
forum.xda-developers.com
For the LG I cannot unlock anything at all. Debug and oem from the dev menu is active. I only get into adb sideload mode through computer commands. From sideload, Cancelling it takes me to recovery mode menu but without adb access...???
Thanks. I have an fpga, havent touched it yet. will that help? maybe learning opportunity?
Hi guys.
When enter Command "adb reboot boatloader" in cmd my device automatically restarted and can,t enter fastboot mode for enter other Commands.
My device is unlocked Mi lock and All drivers installed Successfully, But this problem does not allow the device to complete the root operation.
I changed the ROM of the device several times, but the problem is still not solved.
Friends, please help me if you know any tips in this regard.
hossein_0513 said:
Hi guys.
When enter Command "adb reboot boatloader" in cmd my device automatically restarted and can,t enter fastboot mode for enter other Commands.
My device is unlocked Mi lock and All drivers installed Successfully, But this problem does not allow the device to complete the root operation.
I changed the ROM of the device several times, but the problem is still not solved.
Friends, please help me if you know any tips in this regard.
Click to expand...
Click to collapse
What exactly is the problem?
hossein_0513 said:
Hi guys.
When enter Command "adb reboot boatloader" in cmd my device automatically restarted and can,t enter fastboot mode for enter other Commands.
My device is unlocked Mi lock and All drivers installed Successfully, But this problem does not allow the device to complete the root operation.
I changed the ROM of the device several times, but the problem is still not solved.
Friends, please help me if you know any tips in this regard.
Click to expand...
Click to collapse
Try using volume down + power BTN combination
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!