i am using the le x526 and today i flashed the twrp recovery after which it got stuck in boot loop and doesn't come out.
Also the MTP is enabled in twrp recovery mode but still it is not detected in the computer. Its not even detected in adb devices but is listed as a device in the device manager i tried to update the drivers as well but it didn't help how do i restore it or at least make it work.
If you have a backup of your system partition, try restoring just that, it worked for me
do you have twrp installed?
[solved]
Phone was not detected in adb in recovery mode. Later I toggled on and off the adb sideload after which the phone was detected in recovery mode.
Then I transferred the new ROM and kernel to my phone using adb push method.
It's working great now
Related
Hi, I am remotely helping my friend to recover data from his phone. His phone is broken and usb debugging is disabled. So I asked him to reboot to recovery (for adb support )which he cant as the phone is restarting (confirmed this from windows 7 autoplay ) , he was able to boot to fastboot. Now how to reboot to recovery, he is unable to remember which recovery he is on. He is on CyanogenMod lollipop. How to reboot to recovery. Thanks
Finally did booted to recovery but adb says unauthorized. Anyway mtp is listing the folders
Hello, I have this problem since rebooting using adb. IDK what could go wrong. Any ideas?
Thanks
I'm stuck at an issue that I've never seen before and need some assistance. I flashed invictrix 8.1.0 not to long ago and then installed an updated version of the rom through the rom's updater. It went through the automated flashing of the updated version and now I'm stuck in a recovery that seems to be stock, but it's not the stock version I am accustomed to seeing. I can not do anything in this recovery. I have used adb to do things before, but now adb and fastboot seem to get stuck at waiting for device errors or error:device not found even though adb devices and fastboot devices brings up the phone being connected. I now can no longer boot into the phone as I did a hard reset while my phone was operational.
Have you tried booting straight into fastboot mode by holding down Power+Vol Up until it reboots? And then see if you can use fastboot on your PC to flash TWRP again.
Also, all those error messages. Did you at some point reformat the cache partition as f2fs? It's supposed to be ext4..
I can boot into fastboot. The computer recognizes the phone through fastboot devices and adb devices. However, issuing a command through fastboot results in a waiting for device message. Maybe I need to find a more suitable adb. The one I’ve been using is the 15 second adb that only installs the google driver and the adb. I never formatted anything. I’m not sure what to do at this point.
I would use an unbrick guide and start from scratch.
Is there one you'd recommend ? I'm using this one :
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Yes, I also used it in the past and everything was ok.
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
Hi,
I'll start by saying this is the first time i've tried putting a custom rom on a phone.
I unlocked the device, enabled usb debugging and installed twrp. I was able to get into recovery mode and wiped the correct partitions.
I was then unable to install pixel experience? I was unsure how to put the rom on the phone. It was not coming up on my pc when connected.
I then disabled MTP and rebooted the phone. It went straight to fastboot and no matter how many times i reflash twrp, or what button combinations i push, i'm stuck in fastboot.
Can anyone help?!
Thanks in advance!
A helpless noob