I want to clarify that it all happened while the phone was on, I wasn't fiddling with fastboot etc.
everything happened a few months ago: I can't remember if it was switched off or released, if I was using it or if it was on standby; the fact is that immediately afterwards my thea did not want to boot any more (it remained on the motorola logo) and not even in twrp (again it remained on the twrp logo), but fastboot worked. I remember having made a few attempts, and that sometimes the fastboot was blocked and the phone didn't turn off, and that I had to remove the battery.
Now I've got it back, and now:
system doesn't boot, but the fastboot mode works fine and doesn't crash anymore. The twrp instead, remains at the initial screen, but from adb is recognized as recovery, and I can use some commands.
What can I do?
thanks for the answers, always if there will be any
ok, i've resolved with this: https://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075
I have a Red Magic 3 and im having issues.
Its in fastboot but when i go to boot to recovery it just goes to fast boot. i got to boot it to android and the same thing. Fastboot i can see it with fastboot devices but i cant in adb devices. When i plug it in with fastboot its not in device manager but when i put it into EDL mode it shows in device manager. Tried putting twrp on it and it just goes back to fastboot and relocks the bootloader. I used the recovery tool and its giving me this error.
Any idea on what could be doing this? Or how i can fix this?
Wont let me post a link to a picture. But its saying reset EDL mode and download failed. I got my firewalls all disabled. Running windows 10 pro.
Help me please
Hello XDA members,
I am facing a weird issue on my MI 8. Stucked on fastboot mode. Actually i flashed a wrong device rom via twrp. Didnt flashed and got an error this rom is for violet devices. Done.
Then i tried to mount the storage. Nothing showed on my computer. Then i restarted the device. After restart it never came back to MIUI. Stuck at fastboot. Flashed fastboot mode rom. It give success. But nothing run. Still get back to fastboot mode. Please help. Either i damaged the internal storage or there is something else?
Please help
My phone has been rooted for over a year but today the battery ran out and when I pluged the phone in it just shows the white razer powered by android logo and sits there forever I have been able to boot into fastboot mode but cant get it to show up on adb. I checed that this cable works for adb with another phone. I also tried the "wipe userdata" option but it didn't work. Any ideas on how get out of this?
oops
Download the newest factory image (link) and reflash it.
Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?
you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.
hey guys follow this youtube
managed to unbrick my phone
smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..
This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!
the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus