Database Info

Brick - No fastboot - EDL only - Set active slot?

I have not one, but two bricks. I bought one to unbrick the other, but the reverse happened. Using the EDL tool from this forum, I made a full and then an all backup and tried to use it to unbrick the other. No success. Now I cannot enter fastboot on either device, but both will enter EDL. I think at least one will fastboot if I can switch the active a/b slot.
Can the active a/b slot be switched via a command in the edl mode? Or is there another way to switch the active slot on a brick without fastboot access? Thank you

I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA

noobstyle1337 said:
I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA
Click to expand...
Click to collapse
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?

There's no command to switch active slots that I know of and I've gone into the source on fh_loader.
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
The fact that you aren't getting a ZTE logo at all indicates that you do not have a mixed up slot a/b situation anyway. It probably means you need to fix your AOP files. Of course the original EDL tool doesn't really let you do that. If you have the US version you can use the tools I uploaded to target just the AOP files and try restoring them from your original backup... either the a or b slot one should work.
Make sure you keep your original ALL/FULL backups (both) from the EDL tool, they're probably 99% good and you'll be doing yourself a favor not to delete or modify them.
groundslug said:
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?
Click to expand...
Click to collapse

You can only change the slots if you are in Fastboot. You have doing it wrong ... if you have an A2020G you can flash the firmware ... if you have the A2020u version then you should ... flash the correct one
so in itself quite simple .... flash edl firmware and then unlock .. then you boot into the fastboot mode and then you have to use these lines
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then
fastboot --set-active=a
in any case you have to unlock to access the fastboot menu
then you should be able to boot
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
remember to flash Android 9 edl firmware because otherwise the unlock won't work
---------- Post added at 04:47 PM ---------- Previous post was at 04:39 PM ----------
also remember that some firmwares have to be in the flash folder or in the backup folder if it doesn't work

bobthenormal said:
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
Click to expand...
Click to collapse
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!

groundslug said:
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!
Click to expand...
Click to collapse
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.

bobthenormal said:
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.
Click to expand...
Click to collapse
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.

groundslug said:
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.
Click to expand...
Click to collapse
Just replying real quick since I have a min and I saw a few things you can try... 1. make sure you're installing twrp itself with the zip after you boot into it with fastboot, 2. use the two flags when you write vbmeta just in case (I forget them but one is dm verify and the other is no verity, should be in the original LOS16 thread) and 3. try the fix bootable partition tool from my tools after you install. the LOS16 image has a similar problem as all other images that it has a specific slot it works on (B I think) so if you end up installing and trying to boot it from the other slot it locks into a fast bootloop. Don't bother installing the addons until LOS is booting, so just do a reboot to system after you flash it, fix bootable. If it doesn't boot then it has to be something I'm not thinking of. Goodluck!

It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!

groundslug said:
It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!
Click to expand...
Click to collapse
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.

Rise55Chrom said:
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.
Click to expand...
Click to collapse
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!

groundslug said:
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!
Click to expand...
Click to collapse
Phenomenal! Best advice, I have received... Thank you so very much. You hit it right on the head. I'll be sure to fill ya in asap when I have the time to get after it. Appreciate you.

bobthenormal said:
EDL tool
Click to expand...
Click to collapse
Hello, where can I find this program? EDL tool

How root and unlock bootloader Motorola Moto E6s XT2053-2 (Fiji)

Hello,
There is any way for unlocking bootloader and rooting the device Motorola Moto E6s XT2053-2 (Fiji) ?
I can allow oem unlock on develop settings. But fastboot says oem unlock doesn't exist and I can't flash anything.
:-(
Thank you very much

try to downgrade for the fist version of fiji firmware and put this command via fastboot
fastboot flashing unlock_critical
it worked with E6+

raphable said:
try to downgrade for the fist version of fiji firmware and put this command via fastboot
fastboot flashing unlock_critical
it worked with E6+
Click to expand...
Click to collapse
how did you downgrade with unlocked bootloader?

VD171 said:
how did you downgrade with unlocked bootloader?
Click to expand...
Click to collapse
install flash tool, and download the oldest rom for fiji from lolinet mirrors, then, extract the rom and power off your device, open flash tool and select the scatter file from the stock, press the download button. In the device, press volume down and connect to the computer, then, if flashed successfully, go to fastboot and run the command

raphable said:
install flash tool, and download the oldest rom for fiji from lolinet mirrors, then, extract the rom and power off your device, open flash tool and select the scatter file from the stock, press the download button. In the device, press volume down and connect to the computer, then, if flashed successfully, go to fastboot and run the command
Click to expand...
Click to collapse
which DA file did you use? also my oldest rom is 288.13, pretty much factory stock for my phone region but fastboot commands are still disabled

VD171 said:
Hello,
There is any way for unlocking bootloader and rooting the device Motorola Moto E6s XT2053-2 (Fiji) ?
I can allow oem unlock on develop settings. But fastboot says oem unlock doesn't exist and I can't flash anything.
:-(
Thank you very much
Click to expand...
Click to collapse
Here is instruction for e6 plus, i think for e6s it might work. I want try this later.
Stock firmwares can take here

Mortyk said:
Here is instruction for e6 plus, i think for e6s it might work. I want try this later.
Stock firmwares can take here
Click to expand...
Click to collapse
Thanks, I will try this !

VD171 said:
Thanks, I will try this !
Click to expand...
Click to collapse
Link to fitmware little incorrect.
I pasted link for 2053-2, but in my phone show 2053-1.
Here is for 2053-1.
Waiting for your report on the successful operation.

VD171 said:
Thanks, I will try this !
Click to expand...
Click to collapse
So you try unlock the phone or no?

well i tried rooting it by flashing an empty vbmeta and a patched boot.img and soft bricked my device because there's no way to unlock the bootloader with the current fw
gonna need to reflash my preloader but the DA isn't letting me flash anything to that partition

luridphantom said:
well i tried rooting it by flashing an empty vbmeta and a patched boot.img and soft bricked my device because there's no way to unlock the bootloader with the current fw
gonna need to reflash my preloader but the DA isn't letting me flash anything to that partition
Click to expand...
Click to collapse
If you try to flash any modified/patched partition to an unlocked device, certainly you will brick it.

VD171 said:
If you try to flash any modified/patched partition to an unlocked device, certainly you will brick it.
Click to expand...
Click to collapse
it's been a while and i've unbricked my device and now am trying to unlock the bootloader
anybody know how to enter brom mode on these fijis? if thats possible, this tool can unlock bootloaders by patching the seccfg partition: https://github.com/bkerler/mtkclient

luridphantom said:
it's been a while and i've unbricked my device and now am trying to unlock the bootloader
anybody know how to enter brom mode on these fijis? if thats possible, this tool can unlock bootloaders by patching the seccfg partition: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
You can't.

I tested it, but it gave an error: Preloader - [LIB]: Status: Handshake failed, retrying...

br.rafael.venancio said:
I tested it, but it gave an error: Preloader - [LIB]: Status: Handshake failed, retrying...
Click to expand...
Click to collapse
yea i can enter meta mode so far but nothing else. even the usual volume down and usb plug in that works in spft doesn't work for mtkclient. must be some authentication required to enter brom for flashing

luridphantom said:
yea i can enter meta mode so far but nothing else. even the usual volume down and usb plug in that works in spft doesn't work for mtkclient. must be some authentication required to enter brom for flashing
Click to expand...
Click to collapse
You can't.

Hi! I am Ukraine bad english. I am unlock (not pay dongle, just pc) this smart moto e6s 4/64 (and this very simple for 2/32) Now, i am try in hex edit lk for remove 5 sec and message, flash lk from e6plus no try. info for edit lk for remove 5 sec and message? help. and help how root. (also i am unlock meizu m3 max, not pay dongle, just pc, flash preloader, reset pin frp work)

severagent007 said:
Hi! I am Ukraine bad english. I am unlock (not pay dongle, just pc) this smart moto e6s 4/64 (and this very simple for 2/32) Now, i am try in hex edit lk for remove 5 sec and message, flash lk from e6plus no try. info for edit lk for remove 5 sec and message? help. and help how root. (also i am unlock meizu m3 max, not pay dongle, just pc, flash preloader, reset pin frp work)
Click to expand...
Click to collapse
you used a pay dongle or what free tool to unlock? mtkclient doesnt work for me but i know the dongles can unlock the e6s
to root, go to lolinet and find your firmware version there, unzip and extract boot.img and patch with magisk. flash with fastboot

luridphantom said:
you used a pay dongle or what free tool to unlock? mtkclient doesnt work for me but i know the dongles can unlock the e6s
to root, go to lolinet and find your firmware version there, unzip and extract boot.img and patch with magisk. flash with fastboot
Click to expand...
Click to collapse
its very simple) from fastboot anl 29.137 firmware. Thanks i am try patch boot. fastboot still not flash any part but spft now flash editing lk vbmeta/ vbmeta i flash empty and lk with remove mess orange state. But i am dont flash twrp - i am dont know adress partition - in scatter not find him. Now i am search why its did

severagent007 said:
its very simple) from fastboot anl 29.137 firmware. Thanks i am try patch boot. fastboot still not flash any part but spft now flash editing lk vbmeta/ vbmeta i flash empty and lk with remove mess orange state. But i am dont flash twrp - i am dont know adress partition - in scatter not find him. Now i am search why its did
Click to expand...
Click to collapse
ok i will try when i get home. maybe i cant downgrade to that version and they removed it like with the e6
posted the lolinet link in the other thread. the scatter file is in there

Alcatel TCL A502DL/A501DL root/custom recovery/custom roms?

Is there any way to get root/custom recovery/custom roms on the A502DL or A501DL? If so, how?

lehmancurtis said:
Use the boot mode tool from here for the a501dl. It definitely is unlockable! You can grab the TWRP.img I compiled for the a501dl from this link.
Click to expand...
Click to collapse
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.

lmgnsa said:
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
Click to expand...
Click to collapse
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.

lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me

@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!

fliproc said:
@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!
Click to expand...
Click to collapse
Use a tool that controls bootmode. Mtk-mode-selector

lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Please help, it says "waiting port" forever

Thanks for the reply! I tried this tool, along with adb commands, etc., and I just can't even get fastboot. This would be an AWESOME phone, if not for this dumb crap!! The phone I had before this one is a Z717VL, and it sucks as well. They are both Tracfone phones that were given to me by my wife. I think I'll just get a Galaxy S8 or so and just root it instead. All other phones that I had on Verizon in the past have been super easy... just a One-Click-Root. Thanks everyone for your time and help!

lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Are you sure the method you thought of works? The bootmode tool you linked cannot get the A501DL to fastboot mode, it just says "waiting port" forever.

@lehmancurtis I feel like you might be lying about whether or not your method works, as the boot mode tool does not work. @lmgnsa did it work for you?

I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.

williamhancock328` said:
I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.
Click to expand...
Click to collapse
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.

Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool

mickeybeats said:
Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool
Click to expand...
Click to collapse
I have already installed the MTK VCOM drivers multiple times, I don't know why it still doesn't work.

T
lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
lmgnsa said:
To keep recovery from being replace several files need to be disable (various approaches are effective i.e. removed, replace, or renamed). Magisk usually handles this task, but sometimes there are exceptions. But, you need to address that before flashing gsi's for multiple reason and none are fun to deal with. Yes, this is A only and does not use A/B update method (at least not entirely as a few partitions are making use of the A/B partition labels). I've not been doing much with this particular device since mine was cracked and the usb port messed up when I got it, so nature took its course before I was able to achieve a fully stable custom setup.
Click to expand...
Click to collapse

sj78 said:
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.
Click to expand...
Click to collapse
It sometime takes a few tries to get the phone and tool to do what its supposed to, but if you get the waiting message start over until the program reboots the device. It will work, it's just not a perfect process.

lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
You need to modify a few files. It's almost just like the 5059 devices and you can look up the 5041c thread to see what needs edited. Use the fstab.mt6739 from the 5041c.

Here's the tool. I think some of the links to it got messed up. Make sure you turn on developer options and check that oem unlock is ticked as well as adb usb options. Once in fastboot, issue the following
Code:
fastboot oem unlock-go
Follow the instructions on the device. Then boot into system and complete setup so that you can turn on developer options again since your device was just reset. Boot to fastboot once again and issue these.
Code:
fastboot flash recovery ./recovery.img
Code:
fastboot oem reboot-recovery
That should be the custom recovery you just installed. It will be replace on reboot if steps are not taken. I was in the process of working this issue when my beat up a501dl succumbed to its varied and multiple impact injuries. If I can find the time to repair it I will finish where I left off, but in the mean time I will help as much as I can.

Regular drivers are built into the phone but you may need vcom drivers. I'm going to attempt to repair mine enough to reset and flash again. I'll probably have to nav my screen via commands, but I will attempt to capture the process and show you.

I've got a A501DL, I enabled usb debugging and oem unlock, seems like the A501DL in fastboot does not talk with the pc, i've installed so many driver things its crazy butat fastboot when typing fastboot reboot bootloader, it reboots the phone but it skips fastboot and turns on to my home screen, I used volume up and power, I get in fast boot butthe device isnt being detected by windows 10 64 bit. Also in fast boot there is only
reboot system now
wipe data/factory reset
wipe cache partition
power off
im going nut that fastboot isnt working with this device.

Unbrick your Realme C12

What is a brick?​If there is no usual way to recover your mobile, then it is called brick in my opinion. That means if you can't able to go to recovery and fastboot mode or the device is just blank with no sign of life.
When brick happens?​It will happen because of locking bootloader with custom images or just because of Mediatek/Realme strange behaviour.
What we have to do if brick happens?​Simply we have to flash stock firmware with Smart Phone Flash Tool(aka SPFlash Tool). With only SPFlash Tool we can't do anything, since we don't have permission for it. But with the advent of MTK-bypass, we can have full control over our device. If we don't have this MTK-bypass, then we have search for costly alternative's.
You can't flash only if your eMMC is damaged, which is the worst case because oppo phones are prone to eMMC failure.
Click to expand...
Click to collapse
Where to get firmware to flash?​Download decrypted .ofp firmware from https://drive.google.com/file/d/1SOmRxix9_UtjOLLanXPYxf4YK1NrA_RW/view
Thanks to @bx2_nero for it.
What is the procedure for using MTK-bypass and SPFlashTool?​MTK-bypass is a Python script and it needs different USB ways for working. So with these two in place, we can get our work done.
Linux Users​For Linux we have to use FireISO or patched kernels for working of MTK-bypass.
Use the Linux guide by @bx2_nero at https://forum.xda-developers.com/t/...our-realme-6-6i-india-6s-linux-method.4251077
Windows Users​For Windows we have to use libusb32 filter for MTK-bypass working.
Use the guide by @daeSundae at https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
MTK-bypass Official instructions​See Github ReadMe at https://github.com/MTK-bypass/bypass_utility and XDA support thread at https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377/
Credits​xyzz / xyz`: GitHub | XDA
chaosmaster / k4y0z: GitHub | XDA
Dinolek: GitHub | XDA
References​- https://forum.hovatek.com/thread-37957.html
- https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/
- https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
- https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
- https://forum.xda-developers.com/t/...ash-tool-authentication.4236881/post-84627359

MTKClient
After MTK-bypass got success, @viperbjk who is a reverse engineer came up with a FOSS replacement of SP Flash Tool.
MTKClient combines MTK-bypass and SP Flash Tool together and with many improvements and new features.
Ability to flash partitions without Scatter file
Ability to Readback partitions without specifying address and length
Ability to Format partitions without specifying address and length
Run multiple commands without reconnecting the device
Flash protected partitions(opporeserve2, special_preload, my_custom and cdt_engineering) with locked bootloader
Unlock bootloader without need of in-depth test/Deep testing app from Realme
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
www.github.com

Reserved

I need help, my C12 is stuck on fastboot mode. This happened after flashing a GSI using TWRP and flashing the image in the Super (System and Vendor) partition.
I tried rebooting to recovery mode by executing fastboot reboot recovery but it says that bootloader is not known.
I also tried to flash a GSI (taught it might fix the problem) using fastboot flash system system.img but it says that no partition named system exists.
Please suggest what I should do.

Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip

DFM23 said:
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
Click to expand...
Click to collapse
What is the present state of the device? Can you able to boot to fastboot mode?

HemanthJabalpuri said:
What is the present state of the device? Can you able to boot to fastboot mode?
Click to expand...
Click to collapse
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.

How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.

youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
Use latest platform tools

youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
HemanthJabalpuri said:
Use latest platform tools
Click to expand...
Click to collapse
Sir I've finally able to reboot to recovery. I've tried flashing the OZIP file for my model but after some time it says Installation failed. When I was still using custom recovery, I wasn't able to mount System and Vendor. My bootloader is also unlocked sir.
Should I lock my bootloader sir?

youcancallmekhen said:
Should I lock my bootloader sir?
Click to expand...
Click to collapse
Don't lock bootloader.
Download this https://drive.google.com/file/d/1jLdDz7M0G_KPDn4jXjTeuFnO1C-MFaBs/view (It is from A.87 UI 1.0 Stock ROM)
Extract above 7z file and flash ONLY super partition from it and TWRP from https://androidfilehost.com/?fid=7161016148664807816 with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery TWRP.img
fastboot reboot recovery
Now enable 'Skip Treble Compatibility error' in TWRP settings and flash stock ROM .ozip in TWRP.
Thanks

HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
Oh my, thank you so much sir. You have no idea how much you are helping me sir! My parents will be so happy, and we won't waste money… Thank you so much sir…
I'll update you sir after doing these, thank you sir! ♥

HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
I don't have much data left today sir, so I will download this later. Thank you very much again sir, you're my hero!

DFM23 said:
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
Click to expand...
Click to collapse
Follow the guide and you can get your mobile back to life.
Thanks

HemanthJabalpuri said:
Follow the guide and you can get your mobile back to life.
Thanks
Click to expand...
Click to collapse
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11

DFM23 said:
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
Click to expand...
Click to collapse
Yes, both use same firmware.

I tried the guide but when I click download on sp flash tool it would stay in red bar for 1 min or more then message will appear saying STATUS_EXT_RAM_EXCEPTION. I have read a same comment here in xda about realme c12 I dont know if its only on realme c12.

Thanks for your works sir, you are super awesome!

I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?

Bhuprab said:
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Click to expand...
Click to collapse
Since your device is Qualcomm, I don't know. In any device, we have to flash stock rom (or atleast the partitions that are modified) to get device in working state.
You may get better help at https://forum.xda-developers.com/f/realme-x2-pro-questions-answers.9439/
Thanks

How To Guide Unlock the bootloader and install GSI ROM

So if anyone is interested in booting a GSI Image Here is the guide: also thanks to @Dollscythe I just updated it as he forget to write me a step for flashing the vbmeta.img..
1. you need to download the firmware file for your model
2. you need to open it with your zipping software of choice (i use 7zip) And after it unzips you need to unzip AP file to get to the recovery.img.lz4
3. you extract the recovery.img and you patch it to enable fastbootd https://github.com/Johx22/Patch-Recovery you will also find the info how to patch it on the link, it is easy if you know how to follow it) - Currently is NOT working, the dev said to me that he will fix this once his exams are over. (If you know how to Decompress the Iz4.img to get just the .img it will probably work - didn't try tho.
4. this step will wipe your device so make sure to back up (unlocking the bootloader) And it will also trigger your Knox!
To unlock the bootloader you need to go to settings, about phone - software info and press on the build number like 7times to enable developer options. After that go to developer options and enable OEM unlock.
Turn off the phone, put the USB C cable into the phone (but not into the computer yet!) Then hold the volume + and volume - button at the same time and put the cable into the phone.
When you are in the download mod you will see the instructions on how to unlock the bootloader.
5. Boot into the system and do the first time setup (make sure to connect to wifi, but skip any prompts to register or login to accounts)
6. double check if the oem unlock toggle is still on, then reboot to download mode
7. you need to flash the patched bootloader using odin - you flash your patched recovery in AP window in Odin. Then you immediately boot into the recovery (you gotta boot to your new recovery immediately after the flash is complete, make sure to hold the key combination for recovery immediately after pressing start in odin to get it right. otherwise, the system will wipe your newly flashed recovery and you'll have to do step 7 again)
8. You will now notice that your recovery has a new option: fastbootd mode (yes there's a d in there, it's not a typo, it stands for fastbootdynamic mode) 9. once you're in, your device now officially supports fastboot. you just do "fastboot flash system *the_name_of_the_system_image_you_downloaded.img", RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group) and once that is done flashing just exit fastbootd mode back to the recovery, then format data and then then reboot for system images, i recommend pixel experience https://github.com/ponces/treble_bu...4-ab-vndklite-12.1-20220518-UNOFFICIAL.img.xz 10. you'll be greeted by a google bootlogo and thats a success.
Good luck!

Bucika said:
RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group)
Click to expand...
Click to collapse
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.

One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website

jdg007 said:
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
Click to expand...
Click to collapse
The purpose of XDA "Developers" was actually to share knowledge between developers, you know, people who actually know how the most basic stuff works. It's open up for the public, sure, but most of the stuff you can find here are not meant for the average noob that doesn't know how to unlock a bootloader.
The instructions are pretty clear for people who can use a google search. Don't expect everything to be spoon fed, put in a little effort.
There's a difference between saying "OMG this is too complicated why don't you explain it with a video or why don't you tell me step by step on how to flash custom firmware on my phone" and saying "Hey I'm stuck in step 3, I don't understand the part here. This is what I've tried so far..."
I bet for the most part, the first person would be ignored while the second person would more likely get a response.

That means to offend you in any way or whatever I just wished people would give more explanations on what they post because you know I don't make no sense on how you patch the recovery I'm new at this it's my it's my fault I do know how to unlock bootloaders not bootleggers and I do know how to install TWRP and Flash zip balls but as when it comes to patching something the only thing I know how to pack is using magisk That's the boot image I'm sorry hope Hope you can help me out

If you don't mind email me a copy of that recovery image that you got Text I sure would appreciate it Just looking forward For your reply

Thanks @Bucika, here's a guide that might be a bit more noob friendly. Also a big thanks to @Dollscythe for their help.
Files can be found here.
These are the latest GSIs.
1. Unlock bootloader by opening developer options and flipping the "unlock bootloader" switch.
2. Boot into download mode (press and hold vol + and - while plugging into computer).
Press and hold vol + to enter unlock mode. Accept and click enter. Your phone will reset.
3. Using Odin, flash fastbootd through AP. (recovery.img).
4. Press and hold volume + key as the phone reboots, as when you restart again it will reverse this step. You should be in recovery now.
Click on fastboot.
5. Get fastboot working on your computer. Test connection by using the command "fastboot devices" to see if your device is there.
6. Run the command fastboot flash system [name of gsi file]. (without square brackets)
7. When you're done, run ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. Go back to recovery and wipe your phone.
9. Go back into fastboot, flash magisk file if you would like root: fastboot flash boot magisk
10. Wipe again, reboot.
11. Once you are fully booted in, open settings > phh settings (first entry) > misc settings > then scroll down until you find "force fps"
Change that to the @120fps option.
Hope this helps! Note that this is unofficial and WiFi hotspot doesn't work, Samsung Health has issues too. I couldn't get my watch 4 working with GSI.
This will blow your Knox bit fuse!

Ivan Fuentes Hagar said:
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
Click to expand...
Click to collapse
I find myself in a bootloop too after this step, how did you get out of the bootloop?
edit, answer to my own question in case it helps someone in the future: plug phone into a pc and then hold `volume up + volume down` buttons to enter download mode.
edit 2 if after flashing a GSI rom your device wont boot, plug it into power and wait a few minutes.

I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?

ActuallyJammy said:
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
Click to expand...
Click to collapse
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12

TringQuack said:
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
Click to expand...
Click to collapse
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.

ActuallyJammy said:
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
Click to expand...
Click to collapse
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13

TringQuack said:
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
Click to expand...
Click to collapse
Could you give me a GSI rom with a patch and similar to PE?

@TringQuack What's your current state with A53?
Running GSI? Stock?

ThugMaster said:
@TringQuack What's your current state with A53?
Running GSI? Stock?
Click to expand...
Click to collapse
Stock

@TringQuack How do I know if the build is compatible with A13?