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
Related
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
TAGTRAUM said:
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
Click to expand...
Click to collapse
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Circaflex said:
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Click to expand...
Click to collapse
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
TAGTRAUM said:
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
Click to expand...
Click to collapse
Nope.. If adb doesn't work and volume buttons are broken, you're stuck. Get the buttons repaired.
rootSU said:
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Click to expand...
Click to collapse
No luck with running this commands in boot process
TAGTRAUM said:
No luck with running this commands in boot process
Click to expand...
Click to collapse
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
Adb should work from part way through the boot process and any mode. in custom recovery.
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
TAGTRAUM said:
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Tech said:
Try this
Click to expand...
Click to collapse
Will try, but decide to repair my Vol- button myself, i have no mind what can be broken in this part, watching video of N6 dissassembly, its pretty simple part indeed Walking w/o Vol- for a month, and this situation is frustrating me and other situations can happen, in certain cases i still need Vol- :cyclops:
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc. Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Sent from my Xiaomi Mi5 using Tapatalk
SilverMarcs said:
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc.
Click to expand...
Click to collapse
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
SilverMarcs said:
Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Click to expand...
Click to collapse
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
FrozenPie1 said:
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
Click to expand...
Click to collapse
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Sent from my Xiaomi Mi5 using Tapatalk
SilverMarcs said:
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Click to expand...
Click to collapse
It's not working on both Windows 10 Machines i have. I'll try to install Windows 7 on my Laptop (or in a VM) and look if that works when i'm home again
Edit: Well, now i'm totally confused... For some reason fastboot started working again this morning so i was able to flash TWRP again. Anyway thanks for the help
FrozenPie1 said:
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Click to expand...
Click to collapse
I too have the same problem..****
Install MiFlash on your PC and try again, the device will show up correctly on fastbook devices command. It was a USB drivers issue in my case.
Has anyone tried using adb fastboot on Samsung Galaxy Note 8 recently.
I have tried unsuccessfully to get the fastboot work using Windows and Macbook with the latest Samsung Samsung drivers for fastboot. Even installed the fastboot drivers from Android Development platform but still no luck beyond <waiting for device>.
I read on another forum that Samsung no longer allows fastboot to work with their devices. Is it correct?
Fastboot as I understand it is an extension of Android recovery.
If you have USB Debugging enabled on your device, you should be able to issue commands: adb reboot fastboot
Fastboot commands also work in bootloader.
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Prof_Shekhar said:
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Click to expand...
Click to collapse
The appropriate command to flash /boot would be:
Code:
fastboot flash boot <boot image>
I will try to keep it short. I installed PE on my mi 8 se and it was working fine then a OTA update arrived, i clicked install and it turned off and stuck on TWRP splash screen. there is no navigation or buttons, it doesn't turn off till the battery runs out. after charging it up again it shows the twrp screen. i can go to fastboot mode by pressing power+vol- but
Code:
fastboot devices
doesn't show any devices connected to my pc. my pc also doesn't recognizes the phone and marks it as "USB unknown" and updating it with android drives shows an error stating that its not compatible.
Code:
adb devices
shows my phone when in twrp screen but that's about it.
as it stands:
-
Code:
fastboot devices
doesn't recognize devices, i think because USB debugging was off but now i have no way of boot into my phone to turn it on
-
Code:
adb devices
recognizes my phone but i don't know what to do with it
-i read somewhere that pixel experience "FBE encrypts the phone so twrp is unable to access past encryption" but i don't know what that means
-currently my phone is a brick with twrp logo, so please HELP.
THANKS in advance for help.
siyyee said:
I will try to keep it short. I installed PE on my mi 8 se and it was working fine then a OTA update arrived, i clicked install and it turned off and stuck on TWRP splash screen. there is no navigation or buttons, it doesn't turn off till the battery runs out. after charging it up again it shows the twrp screen. i can go to fastboot mode by pressing power+vol- but
Code:
fastboot devices
doesn't show any devices connected to my pc. my pc also doesn't recognizes the phone and marks it as "USB unknown" and updating it with android drives shows an error stating that its not compatible.
Code:
adb devices
shows my phone when in twrp screen but that's about it.
as it stands:
-
Code:
fastboot devices
doesn't recognize devices, i think because USB debugging was off but now i have no way of boot into my phone to turn it on
-
Code:
adb devices
recognizes my phone but i don't know what to do with it
-i read somewhere that pixel experience "FBE encrypts the phone so twrp is unable to access past encryption" but i don't know what that means
-currently my phone is a brick with twrp logo, so please HELP.
THANKS in advance for help.
Click to expand...
Click to collapse
NOTES (Read First):
- Twrp can´t decrypt data in android 12, so you need to install updates or magisk via adb sideload. If you remove pin lock in android you can install updates normally, because data can be decrypted.
- Do a clean install if your coming from PE11 or PE12 Alpha. Don´t update. And follow instructions from "Install".
- This firmware and vendor included in rom is specific to this rom, don´t try to use them in other roms.
- This twrp will probably only work with this vendor and firmware, don´t use in other roms.
Install:
1 - Flash rom (this is needed to install proper vendor and firmware)
1 - Flash Recovery via adb (Download: https://drive.google.com/file/d/1Iqa4-sBwThUAAvJsFwl6oP-D4EzRcCyq/view)
2 - Reboot recovery
3 - Factory Reset and Format Data (backup sdcard before format)
4 - reboot recovery
5 - Flash ROM via adb sideload (Advanced -> ADB sideload)
6 - reboot system
Update:
1 - Reboot recovery
2 - Advanced -> ADB sideload
3 - Reboot system
beenmoov said:
NOTES (Read First):
- Twrp can´t decrypt data in android 12, so you need to install updates or magisk via adb sideload. If you remove pin lock in android you can install updates normally, because data can be decrypted.
- Do a clean install if your coming from PE11 or PE12 Alpha. Don´t update. And follow instructions from "Install".
- This firmware and vendor included in rom is specific to this rom, don´t try to use them in other roms.
- This twrp will probably only work with this vendor and firmware, don´t use in other roms.
Install:
1 - Flash rom (this is needed to install proper vendor and firmware)
1 - Flash Recovery via adb (Download: https://drive.google.com/file/d/1Iqa4-sBwThUAAvJsFwl6oP-D4EzRcCyq/view)
2 - Reboot recovery
3 - Factory Reset and Format Data (backup sdcard before format)
4 - reboot recovery
5 - Flash ROM via adb sideload (Advanced -> ADB sideload)
6 - reboot system
Update:
1 - Reboot recovery
2 - Advanced -> ADB sideload
3 - Reboot system
Click to expand...
Click to collapse
thanks for the response,
but as i mentioned in my post, fastboot doesn't recognized my device, the attached image is the output for
Code:
fastboot devices
i have no way to reboot phone to the os, its just either TWRP splash screen or fastboot mode by pressing power+vol-
thanks, hoping for further solution.
siyyee said:
thanks for the response,
but as i mentioned in my post, fastboot doesn't recognized my device, the attached image is the output for
Code:
fastboot devices
i have no way to reboot phone to the os, its just either TWRP splash screen or fastboot mode by pressing power+vol-
thanks, hoping for further solution.
Click to expand...
Click to collapse
Have you tried to reflash to miui with mi flash tools?
maybe changing the cable or installing drivers because if it's boot to bootloader you can Always do Something.
siyyee said:
thanks for the response,
but as i mentioned in my post, fastboot doesn't recognized my device, the attached image is the output for
Code:
fastboot devices
i have no way to reboot phone to the os, its just either TWRP splash screen or fastboot mode by pressing power+vol-
thanks, hoping for further solution.
Click to expand...
Click to collapse
you should install fastboot driver first so the computer can access your phone in fastboot mode. after that you can easily use fastboot command to reinstall twrp image. follow this guide: https://beebom.com/fastboot-not-detecting-device-windows-10/
hey guys,
sorry for late reponse but i managed to fix the problem, turns out the cable i was using was faulty so i changed it with the original one and wallah it recognized my device.
then i flashed stock rom and then xiaomi eu rom, now working great.
thanks for all the help.