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
Related
Hi guys, i need some help, i wanted to convert my A2 in 6X, and i need to enter edl mode to do this. Because i couldn't enter edl via fastboot or adb (i had unlocked bootloader ad twrp recovery installed) i tried to relock bootloader (maybe this was the error), now i'm stuck at message that says that system is corrupt and devices wouldn't boot, i can only access fastboot, tried to boot twrp via fastboot but didn't work, fastboot getvar unlocked return no, now i'm trying to follow the guide to unbrick from ARB but phone should be in edl mine is in fastboot, please help me, any suggestion is accepted! Thanks
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
use option 5 then select the second option
it will boot the device into edl mode.
if you have issues with it not letting you enter it with this then try to unlock the bootloader again.
Daha3ker said:
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
use option 5 then select the second option
it will boot the device into edl mode.
if you have issues with it not letting you enter it with this then try to unlock the bootloader again.
Click to expand...
Click to collapse
already did it, didn't work, unlocking bootloader gave me error: oem unlock is not allowed.
i menage to enter edl mode using test point method, after that i flashed latest rom, and phone booted up, but i turned off to reassable it, and when i tried to reboot it it went to edl mode and i cannot exit edl mode, my pc see it like QUALCOMM9008 and if i try to flash with miflash it does the flash but i can't bot it after flashing success. i'm trying now to download an older fastboot rom
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
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
Hi,
I'm stuck with my phone: it still loopbooting every 5seconds, black screen, only retrolight.
Bootloader is unlocked. I wanted to install twrp, but fastboot says partition recovery not existing.
After reboot, i'm stuck with this mod.
Try to press volume - to go again in fastboot : phone is detected by computer, then disconnected because it's rebooting.
Do you have a solution to try for me?
Or what are EDL point? I've tried to make an ELD cable but did not work either.
How long is your bootloader keeps active? If it's about 5 - 10 seconds, you can try paste the command to flash stock recovery. I attached it if it's possible to do so (from the latest global). And by the way - THERE IS STILL NO ANY CUSTOM RECOVERY for our device, sadly. Actually there is some, but only mouse works.
The commands to paste:
fastboot flash boot twrp.img
KastenTop said:
twrp.img
Click to expand...
Click to collapse
Boot.img in this case, doesn't make much difference
Sorry but my bootloader don't stay active long enough. I just ear usb detection from PC , then one seconde later, usb disconnection sound.
Phone is still loop booting.
Can you try then pasting "fastboot oem edl" (emergency download mode). The screen should turn black
After that flash with Xiaomi Flash tool
I'm unable to enter in FastBoot mode.
Phone booting black, and every 5 seconds , reboot.
If i push "volume down " button, i hear it vibrate, but nothing. Reboot and not detected by fastboot.exe
I think i have, with all manipulation , relocked the bootloader.
My only way, will to find a way to boot in EDL mode.
Test points, which are unknown so far. You have to disassemble the phone, tho. And you can try to find these points yourself, at your own risk obviously. If you will succeed, pls tell me. We need to know the test points.
I was exactly in same trouble, use This guide that solve the issue.
How to use MTK Bypass to backup or flash secure boot MTK
This is a step by step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little
forum.hovatek.com
Press mobile three buttons and connect cable to pc to enter brom mode. Because mtk models don't have test point. So don't need to open mobile.
proxynet said:
I'm unable to enter in FastBoot mode.
Phone booting black, and every 5 seconds , reboot.
If i push "volume down " button, i hear it vibrate, but nothing. Reboot and not detected by fastboot.exe
I think i have, with all manipulation , relocked the bootloader.
My only way, will to find a way to boot in EDL mode.
Click to expand...
Click to collapse
EDL mode in Xiaomi mediatek are called BROM mode. Don't need to disarm the mobile.
Thanks !
I tried, it works like a charm !
You're the best man
Zaiserr2 said:
EDL mode in Xiaomi mediatek are called BROM mode. Don't need to disarm the mobile.
Click to expand...
Click to collapse
nice tip!!!! this is a very helpfull guide for solve hard brick on mtk devices. i have decided never modding this phone, excep root when i need a full backup with migrate. because is much mure complicated than snapdragons. but your post is very very helpfull for who want to try anyway
Hi,
Sequence of steps:
1. Extracted the boot.img from payload.bin and flashed it to the phone. At this point I was able to get into Fastboot
2. While in Fastboot I went into advanced and wiped the "System Settings", and that's when the trouble started - now the phone is stuck into a boot loop forever, I do however get the options to "Power Off" and "Restart"
3. But none of the options above in Step 2 is able to bring me back to Fastboot (and hence into fastbootd either)
Question: How can I get the phone into Fastboot Mode - have tried MSM Tool v4 as well, but that doesn't even recognize the phone
Edit - This seems to have been resolved now, think I had to press Vol Down + Power instead of Vol Up + Power
Was able to enter into Fastbootd as well, will try to proceed with unbricking the phone with a fresh mind tomorrow
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
VoltaGe86 said:
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
Click to expand...
Click to collapse
Thats right, "fastboot boot <file_name>" loads temporarily your custom recovery of choice. After rebooting your phone, the custome recovery is gone.
Otherwise, the command "fastboot flash <file_name> recovery" flashs permamently your custom recovery of choice to your device.
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Zekedw said:
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Click to expand...
Click to collapse
I have exactly the same issue, on a nord 2
How about vol+/vol-&power all together? When stuck that gives me some screen that allows start, recovery (the one where you can enter advanced settings I expect from your description) and bootloader booting.