Database Info

[HELP] Black Screen Even after Restoring to stock firmware & Cannot relock Bootloader

[HELP] Black Screen Even after Restoring to stock firmware & Cannot relock Bootloader
My phone - Moto G XT1033 Asia Dual Sim
I updated my phone to 5.0.2 official via OTA.. And then unlocked by bootloader...
Everything was working fine, after few days, phone suddenly stopped working.
I restarted my phone and after that, every time after moto boot animation, it always gets stuck at a black screen, showing nothing
I tried all the tutorial of Reverting back to stock firmware.. I tried flashing following files via both fastboot and mfastboot... Everything gets flashed successfully without any error.
First I tried 5.1. file named - XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml
Then 5.0.2, ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml
Then 4.4, ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF.xml
Still same problem persists.. Phone does not starts after moto boot animation and stucks at a black screen..
I tried to downgrade to 4.3, tried to flash this file fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar, but it always show prevalidation of firmware failed.
Screenshots of my bootloader and the blackscreen have been included....
Also I tried relocking my bootloader several times.. But after flashing a stock firmware, there comes a screen where is it written locked and when I reboot to the bootloader, it still shows unlocked..
This is how my bootloader looks right now http://postimg.org/image/4w8zrwgrp/
Bootloader Unlocked Warning http://postimg.org/image/o76nd4qux/
Moto boot animation works perfectly http://postimg.org/image/m3w85gr21/
And then this black screen comes and phone stucks here. http://postimg.org/image/5775d1ji1/
Fastboot results in Cmd after flashing Stock 5.0.2 http://postimg.org/image/a6ksy5nyv/
http://postimg.org/image/uf86jvn9z/
http://postimg.org/image/5zzyitod3/
Please please please help me now... I have been asking since a long time.. And have described my problem clearly this time..

Is there anyone who can help me

Somebody please help me

Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
happiy91 said:
Today I tried restoring to the stock firmware 5.1.1 ( Moto g XT1033 Asia Retail, which my phone had before going dead). I flashed all the files correctly with mfastboot... Everything went right...
Click to expand...
Click to collapse
Post a full console log of your fastboot commands and the corresponding output.
happiy91 said:
I have unloacked bootloader.. And I think since before going dead usb debugging was not on,, I am unable to flash custom recoveries.
Click to expand...
Click to collapse
USB debugging affects only Android and is not required for flashing custom recoveries.

Finally. Somebody replied.. Thanks a lot..
I will just upload the console output and other things in detail tomorow morning..

_that said:
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
Post a full console log of your fastboot commands and the corresponding output.
USB debugging affects only Android and is not required for flashing custom recoveries.
Click to expand...
Click to collapse
I have updated the details.. PLease check it now.. And help me please

Sorry, I don't know how to fix your black screen issue. However I've seen others reporting a similar problem (but didn't read the threads). And I've read that downgrading your bootloader can brick your device. You also said that flashing the ROMs worked without errors, but you didn't provide a log of your fastboot commands and the output that you got.

_that said:
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
Post a full console log of your fastboot commands and the corresponding output.
USB debugging affects only Android and is not required for flashing custom recoveries.
Click to expand...
Click to collapse
_that said:
Sorry, I don't know how to fix your black screen issue. However I've seen others reporting a similar problem (but didn't read the threads). And I've read that downgrading your bootloader can brick your device. You also said that flashing the ROMs worked without errors, but you didn't provide a log of your fastboot commands and the output that you got.
Click to expand...
Click to collapse
My phone is not bricked... Output of fastboot commmands in Command prompt have been already included in the post.. I have included the screenshots..

flash custom recoery and rom

if you by any chance downgraded the bootloader (fastboot flash motobot......) in your previous flash attempts there is a chance you have hard bricked your device.
and there is no point locking/unlocking bootloader (fastboot oem unlock/lock) once its unlocked. the only reason you are able to flash stuff you have is because the bootloader is unlocked. and i'm not sure how well you can lock a bootloader thats unlocked.
incase you have hard bricked your device refer; https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788

[Q] [HELP] Unable to succesfully install ANY recovery

After trying for over three hours, reading what seems like all threads on the whole of xda and some other sites... i am ready to eat my phone. Ok, must get myself together :-/ . Here we go.
Specs:
Moto G 4g on dutch carrier (vodafone), XT1039
Situation:
Came from completely stock lollipop system, then succesfully unlocked phone via motorola website using the fastboot proces. Intending to install custom rom, first need a recovery. I am now stuck at this step. When booting i now get a screen "warning bootloader unlocked" before the moto splash begins, this is normal as far as i understand.
Problem:
Unable to boot into recovery. Directly after flashing any recovery (with fastboot) and choosing "recovery" from the bootloader i get the message "boot up failed"
After restarting the phone and choosing "recovery" from the bootloader i get the android on its back picture stating "no command"
Already tried:
installed the android sdk, fastboot and mfastboot.
Am able to send commands to phone with (m)fastboot. Flashing works.
I flashed: openrecovery twrp 2850 xt1032, clockwork 6047 falcon, philz touch 6587 falcon, twrp 2870 falcon m stock, twrp 2801 titan v2 and twrp 2860 xt1032
all give exact same result
"fastboot boot NAME of IMAGE"
"fastboot erase userdata & cache"
"fastboot erase recovery"
did the above things in any imaginable combination
I hope someone has some fresh suggestions for me? Thanks for your time.

Bro as far as I know the recovery is not installed u should install twrp from this thread the one on the official site gave me soft brick
Now about the dead android with no command shows that you are on stock recovery and u have booted into it successfully to go further into stock u have to press power and volume up at the same time (like u lock ur phone) but it won't help in installing anything try the recovery I linked (first format your phone complete data and cache wipe from stock recovery not necessary actually) install it through fastboot command and let me know if it worked (with thanks button) BTW what's ur bl ver

thanks for your fast response faizxy, as stated i already tried the one from that thread (i did not use the identical interpunction to describe it but to be clear it is twrp-2.8.7.0.-falcon_M_STOCK.img)
Where do i find my bootloader version? It is the one that came with the device, factory issue...

Some extra info, that might anwser faiz' question: when i boot the bootloader it shows:
"AP Fastboot Flash Mode (S) 41.1A (sha-80481ae, 2015-04-10 14:30:28)

Hope you guys will forgive me for bumping a bit soon, but I really hope some one has a solution! Tomorrow I have time to tinker some more

Have you tried at least one recovery that is actually for your phone (peregrine)?

_that said:
Have you tried at least one recovery that is actually for your phone (peregrine)?
Click to expand...
Click to collapse
Ah. I guess not. Did not know that there where recovery's specifically for the peregrine/xt1039. I searched for "moto g" but apparently is wrong model. DOH!
Thanks for helping out! My problem is solved.
For future reference; finding working pergerine recovery was quite difficult; most mirrors are down. I found one here: https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine and then under header "installing recovery.." under step 2 the download link (i avoid deeplinking)
This one seems to work for me. Now lets find a nice custom rom!
The ones listed here http://forum.xda-developers.com/moto-g/4g-development/progress-twrp-2-7-1-0-source-t2807585 dont work for me. One gives black screen, the other one shows an unlock slider which is unresponsive.

Hi,
Try this one... With encryption abilities or without, your choice...
http://forum.xda-developers.com/showthread.php?t=2996266

RCT6973W43 ROM needed

I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo

kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Hey bro, I've used these guys. Good luck
https://www.needrom.com
Sent from my HTC One M9 using Tapatalk

No RCA I might need to find a similar tablet and dump the firmware

kapicarules said:
No RCA I might need to find a similar tablet and dump the firmware
Click to expand...
Click to collapse
It's been a while since I played with RCA devices, which version of Android is it running?

NepoRood said:
It's been a while since I played with RCA devices, which version of Android is it running?
Click to expand...
Click to collapse
Android 6.0

kapicarules said:
Android 6.0
Click to expand...
Click to collapse
Sorry, not on the Chinese site we used for Viking and Maven firmware, it may show up eventually though...

link me to that chinese website

kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet

DMon04 said:
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet
Click to expand...
Click to collapse
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...

Getting anywhere on this?
darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.

BA_Flash_GOD said:
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.
Click to expand...
Click to collapse
Unfortunately I did not. Mine is still a brick sitting on a shelf, been playing with GSI/Treble for oneplus 6 lately.

darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.

Isrgish said:
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.

darkvoxels said:
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.
Click to expand...
Click to collapse
Thanks for the reply.
How did you do a record the screen? Is there such an option while in fastboot?
Thank You,

darkvoxels said:
... using my phone to record the screen so see the instructions, then I went back watched the video to see what they were ...
Click to expand...
Click to collapse
Can you please tell me how you recorded the screen while in fastboot?
Thanks

I managed to get the bootloader unlocked on my Alco RCA Voyager III and just never got around to finding recovery or anything for it, this device a lost cause or am I just missing something? I don't think I can pull off making a recovery or rom yet but I can give it a shot if no one else is bothering with this device now a days.

@Trolldizzle How did you get it unlocked?
Thanks

@Isrgish I used fastboot flashing unlock command if I remember correctly, been a little bit since I did the unlock but I am like 90% sure that was the command.

i had get link here : findrom.info/rca-rct6973w43
you can try

Here you can find thr ROM. http://detonnot.com/3Xt3

[GUIDE] [ELI5] [Root] [TWRP] [Moto E5] Root and TWRP for Moto E5 Play Explained

Explain It like I'm 5 - TWRP and Root for Moto E5 Play (and other E5 variants)
Step-by-Step explanation of the Root procedure found in @CodyF86 TWRP and Root thread for the Moto E5 Play
Because there are some entry-level users out there, I wanted to break down the steps for those of us who might not have as much experience in working with phones.
12/02/18 - THREAD UPDATE!
PLEASE READ BEFORE CONTINUING
Procedure should be safe for all E5 devices.
DO NOT FLASH ANY NO-VERITY KERNELS LISTED IN XDA
Expand for details...
This guide was originally written for James specific devices.
HOWEVER.. many have asked if this will work on their specific devices, and after answering questions and doing some brief research, I am convinced that this procedure SHOULD BE safe for ALL Moto E5 devices.
BEWARE.. The TWRP port provided for this procedure is not fully ported for the E5. I have confirmed flashing zip or image files, and making/restoring backups of boot, system and data are successful with James. These basic features of TWRP will work on all E5 phones, BUT this TWRP build will cause your phone to be identified as a PERRY device when checked by ROMs or flashable zips that do assert checks on the device name or id.
Prerequisites
ADB and Fastboot installed on PC
Motorola USB Drivers installed for your device
TWRP and fstab files from E5 Play Root / Recovery thread.
Latest Magisk
DISCLAIMER
Unlocking your bootloader is not for the faint of heart. Unlocking your device and installing your own software might cause the device to stop working, disable important features and functionality, and even make the device unsafe to the point of causing you harm. Neither Motorola, nor your wireless carrier or retailer from whom you purchased the device, will be responsible for such damage, so please do not unlock or load any software unless you know what you are doing.
You have only yourself to blame. Unless you have a Developer Edition device, once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader.
The law still applies. You still need to operate your device in compliance with all applicable laws, rules and regulations prescribed by the FCC, and any other governmental agency for that matter. Your wireless carrier may prohibit unlocked devices from operating on their network.
Steps from Stock Device
1 - Unlock Bootloader
Procedure
Enable Developer Options on your Device (Settings -> About Device -> Software -> Tap Build No. until Dev. Options are enabled.
Enable USB Debugging under Developer Options.
Enable OEM Unlock under Dev Options
Follow the Motorola Bootloader Unlock Prodecure on Motorola's Customer Support Portal
2 - Flash TWRP
DISCLAIMER
This process will overwrite your recovery partition. It is wise to make a complete nandroid backup of your device prior to performing any of the steps below.
Procedure
Download Magisk zip package, TWRP 3.2.1 E5 Play and fstab.qcom files from the E5 Play Root Recovery thread.
Put these 3 files in your adb/fastboot directory on your pc
With your phone on and booted to android, connect to your PC using your USB cable.
Open Command Prompt and cd to your ADB/Fastboot directory
run "adb devices" to make sure your device is connected to adb (you will need to approve the initial connection on your device)
manually copy twrp_james.img to your phone's external sd card or
Code:
adb push twrp_james.img /sdcard/
run "adb reboot bootloader" to reboot to fastboot mode
boot directly to TWRP with
Code:
fastboot boot twrp_james.img
make a full backup and store the backup on your phone's external sd card or transfer to your PC.
in TWRP, Reboot->Reboot Bootloader
When back in fastboot mode, flash TWRP to your recovery partition.
Code:
fastboot flash recovery twrp_james.img
fastboot reboot recovery
your phone should reboot to TWRP now on your recovery partition.
3 - Disable Force-Encryption and Root device with Magisk
Procedure
while in TWRP, run the following in your ADB terminal
Code:
adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
adb push fstab.qcom /vendor/etc/fstab.qcom
from TWRP menu: Wipe-> Format Data
copy magisk zip to newly formatted data partition
Code:
adb push Magisk-v17.2.zip /sdcard/
From TWRP, Install Magisk zip
You now are rooted and have TWRP on your Recovery partition. After rebooting to Android, make sure you install the latest Magisk Manager first thing.

Great tutorial. Worked like a charm on my James.

Thanks for posting this. Ive been rooting and messing with phones for years but never really got comfortable with adb and fastboot commands and the other post makes no mention of unlocking the bootloader even though it was obvious i needed to. I considered doing it this way same way i unlocked my e4 Qualcomm but wasn't 100% sure that was what was needed until i read this. Very easy to follow guide that ensures i didn't miss anything.

AesopRock127 said:
Thanks for posting this. Ive been rooting and messing with phones for years but never really got comfortable with adb and fastboot commands and the other post makes no mention of unlocking the bootloader even though it was obvious i needed to. I considered doing it this way same way i unlocked my e4 Qualcomm but wasn't 100% sure that was what was needed until i read this. Very easy to follow guide that ensures i didn't miss anything.
Click to expand...
Click to collapse
My pleasure. Thank you very much. I'm happy to help.

Working like a charm on my Moto E5 PLAY XT1920-16
HI,
After a few attempts i've managed to root my Moto E5 PLAY XT1920-16. I did not flashed twrp_james.img (boot error) just boot directly to TWRP (fastboot boot twrp_james.img) and followed the instructions from step 3. Flashed boot logo from here to "hide" N/A, Bad Key message.

Thanks for this, as it's easy to understand and follow - especially the ADB in TWRP for FSTAB which I previously messed up and got into all sorts of horrible boot loops / errors and had to run away and hide for 36 hours as my wife threatened to chop off something if she heard me scream "B*******" one more time.
No drama this time, it just worked :laugh:

Will this work on a regular E5?

diaconu.silviu said:
HI,
After a few attempts i've managed to root my Moto E5 PLAY XT1920-16. I did not flashed twrp_james.img (boot error) just boot directly to TWRP (fastboot boot twrp_james.img) and followed the instructions from step 3. Flashed boot logo from here to "hide" N/A, Bad Key message.
Click to expand...
Click to collapse
Thanks for this! I've been trying to figure out how to hide the N/A forever on this phone

bubba1601 said:
Thanks for this, as it's easy to understand and follow - especially the ADB in TWRP for FSTAB which I previously messed up and got into all sorts of horrible boot loops / errors and had to run away and hide for 36 hours as my wife threatened to chop off something if she heard me scream "B*******" one more time.
No drama this time, it just worked :laugh:
Click to expand...
Click to collapse
Awesome lol. Thanks for your comment

Slavois said:
Will this work on a regular E5?
Click to expand...
Click to collapse
TWRP version excluded, yes, it should. First make sure you get a TWRP image that is compatible with E5 model you are working with. I wouldn't use the twrp_james.img file linked in this thread if you dont have a james device. I dont know if the regular E5 is james, nora or rhannah. You should have information related to this on your fastboot screen.
If I recall correctly, the fstab.qcom file linked in this thread, which is needed to disable encryption, should work on your phone. There was another member who used it on their E5 Plus without issue.

weakNPCdotCom said:
TWRP version excluded, yes, it should. First make sure you get a TWRP image that is compatible with E5 model you are working with. I wouldn't use the twrp_james.img file linked in this thread if you dont have a james device. I dont know if the regular E5 is james, nora or rhannah. You should have information related to this on your fastboot screen.
If I recall correctly, the fstab.qcom file linked in this thread, which is needed to disable encryption, should work on your phone. There was another member who used it on their E5 Plus without issue.
Click to expand...
Click to collapse
Also a warning about twrp.....
I'm using the XT1920-15 E5 play (PETTYL) and the alleged twrp version for that device (not available here on XDA) doesn't work on that device.
The James version works on PETTYL.
There's two or three E5 play and plus twrp versions floating around here, just a heads up for users to be cautious.....

bubba1601 said:
There's two or three E5 play and plus twrp versions floating around here, just a heads up for users to be cautious.....
Click to expand...
Click to collapse
I would love a TWRP build for this phone that supports backups for all the major partitions and not just basic system/data/cache
Would also be nice if it could wipe lock screen security.
If I knew how to port twrp I would build some

Error msg.
When I run this command I get the following message below. I used both command prompt and powershell. Powershell gives me that error message while command prompt just goes through, but it doesnt give me any confirmation. What must I do?
PS C:\Users\Lit\Desktop\Moto E5 play root> adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
Error msg:
At line:1 char:19
+ adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
+ ~
Missing argument in parameter list.
+ CategoryInfo : ParserError: ) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingArgument

Im using moto e5 play for TMobile xt1921-3 and was wondering if someone can point me in the right direction for twrp installation? And the proper img file? The one I flashed, twrp_james.img, stuck for like a day but now its gone?? Wat am i doin wrong?

Swagnutz34 said:
Im using moto e5 play for TMobile xt1921-3 and was wondering if someone can point me in the right direction for twrp installation? And the proper img file? The one I flashed, twrp_james.img, stuck for like a day but now its gone?? Wat am i doin wrong?
Click to expand...
Click to collapse
If you follow these directions in the op exactly you will be fine and twrp will stick after you boot. The twrp linked here in the op is the one. I used it and I have same exact device as you, same model and all. From my experience tinkering with it you gotta decrypt for twrp to stay. Otherwise if you wanna stay encryted you just use fastboot and fastboot boot twrp.img from your computer every time you use recovery. Hope that helps.
Sent from my XT1921-3

SM210 said:
If you follow these directions in the op exactly you will be fine and twrp will stick after you boot. The twrp linked here in the op is the one. I used it and I have same exact device as you, same model and all. From my experience tinkering with it you gotta decrypt for twrp to stay. Otherwise if you wanna stay encryted you just use fastboot and fastboot boot twrp.img from your computer every time you use recovery. Hope that helps.
Click to expand...
Click to collapse
I got twrp to stick but cant back up data? N magisk flashed no problem....here are some screenshots. Im tryin to flash lineage rom n im gettin no where lol. Sorry im a noob!

Swagnutz34 said:
I got twrp to stick but cant back up data? N magisk flashed no problem....here are some screenshots. Im tryin to flash lineage rom n im gettin no where lol. Sorry im a noob!
Click to expand...
Click to collapse
As 1st post states: see my screenshot attached from the original post... Follow that exactly
then flash magisk 17.2 zip in twrp recovery and reboot and you then can see your data partition in recovery and twrp will hold perminately.
Hope that helps. Always read up alot , I always try to. As specially these days. TONS of new things to learn. Hope that helps. Cheers.
Sent from my james using XDA Labs

for some reason i can flash the hannah twrp 3.2.3 for my moto e5 plus and i can boot intp twp recovery. i made a back up and now its just stuck on the start up loop. and when i get to the adb part of this tutorial i cant push none of the files using the sideload option in twrp so i can decrypt twrp.

Failed at 'fastboot reboot recovery' with the following:
rebooting into recovery FAILED (remote: 'Unknown command')
Continued from step 3 after bring it back to TWRP as [email protected] suggested. However, did not get root. Any suggestions what to try next? The device is XT1921-2.
Thanks!

Hi! I have the xt1920-18 version and TWRP doesn't recognize touch. In case anyone else has this problem, I used the mouse with OTG and it works perfect.Hi! I have the xt1920-18 version and TWRP doesn't recognize touch. In case anyone else has this problem, I used the mouse with OTG and it works perfectly.

[Guide]Alcatel Idol 5 6060C Bootloader Unlock and TWRP[/Guide]

New From A-TEAM: lehmancurtis147​
ALCATEL IDOL 5 : 6060C​ACCESS FASTBOOT
UNLOCK BOOTLOADER
INSTALL TWRP
Special thanks to the mVirus Team for the reboot tool.
Ok, here we go!!!
Start fastboot:
1.*Unpack and launch the boot mode tool.
2.*Power off your 6060C.
3.*While holding vol- plug in device to PC.
4.*While continuing to hold vol- press power until the device starts and release power (not vol-).
5.*Once you see fastboot at the bottom of the device you can release vol-.
Unlock Bootloader:
Now that you are in fastboot mode, we need to unlock the bootloader.
Code:
fastboot oem unlock
Install Custom Recovery:
I forgot to mention I also built a working TWRP.img for this device.
1.*Unzip the recovery.zip.
2.*To install it.
Code:
fastboot flash recovery recovery.img
3.*then...
Code:
fastboot oem reboot-recovery
4.*Welcome to team win recovery!
DOWNLOADS:
This is the boot-mode tool:
https://androidforums.com/attachments/mtk-bootmode-tool-zip.153347/
twrp link:
https://drive.google.com/file/d/1teI23ASm2IbIy_r4xV0jlzz_TzS3cvTc/view?usp=sharing
NOTE:
Unless you remove verity (and a handful of other annonyances) you will loose twrp. Luckily, I've already built a replacement system.img to solve this. Once its working right I'll share it.
I have the system image working, but it's huge. Probably why system and vendor were split in android 8. It's a 4.6 gigabyte image so as soon as I decide the best way to host it I will post it.
In the mean time, the way to keep updated is our telegram group.
A-Team General Discussion
Anything Alcatel, AIO ToolKit, Android, CricketRom
https://t.me/Android_General_Chat

Recoveries
!!!ANNOUNCEMENT!!!
New Recovery Options Available​
I now have managed to build a fully functional Pitch Black Recovery Image and and Orange Fox Recovery Image (the later is built from mostly 9.0 branch) and will be making them available soon if I see that anyone is actually interested.

The recovery image files are compiled from source and not a Frankenstein type. So I can address any recovery issues (within the scope of reason).

Thanks for the thread!! I don't have this device but to my amazement, this utility booted my Alcatel 3t 8 tablet into fastboot mode and I was bootloader unlocked in seconds! I can't thank you enough. This tool should be shared around. It may just be the key to unlocking the bootloader on a plethora of 2018+ MTK devices.

mickeybeats said:
Thanks for the thread!! I don't have this device but to my amazement, this utility booted my Alcatel 3t 8 tablet into fastboot mode and I was bootloader unlocked in seconds! I can't thank you enough. This tool should be shared around. It may just be the key to unlocking the bootloader on a plethora of 2018+ MTK devices.
Click to expand...
Click to collapse
Hi mickeybeats, I happen to have the Alcatel 3t 8 as well! I've been looking for a copy of the stock ROM/firmware everywhere and I'm unable to find it. Is it possible that you have a copy/know where I could download it? My tablet starting throwing up the feared "System UI has stopped" error and it seems reflashing stock ROM is the only way to fix it

I can confirm that the bootloader thing works for the 6058D model (MTK 6753)

For stock ROMs on Alcatel mtk devices, you need Sugar-mtk from Alcatel. It goes through the reflash process and as a bonus you can grab the firmware file from inside the flash tools program folders. The files don't use human readable formatting for the names but they end in either .bin or .mbn. A once over with a hexeditor should be enough to get a general idea of what they are. All the ones I've delt with had the boot.img label with a b at the beginning of the name and r for recovery, but gets a bit scattered from there.

stevegsames said:
I can confirm that the bootloader thing works for the 6058D model (MTK 6753)
Click to expand...
Click to collapse
Post your boot.img if you don't already have a custom recovery and I will build one for yours.

lehmancurtis said:
Post your boot.img if you don't already have a custom recovery and I will build one for yours.
Click to expand...
Click to collapse
I did make one, thank you though. If anyone's interested, here it is:
Idol 5 6058D TWRP
So, I recently revisited this phone and saw that there was a new exploit to access the bootloader. I tried it and it worked. After some time of trial and error, I was able to dump the stock recovery. With this, I started to port TWRP to it. This...
forum.xda-developers.com

stevegsames said:
I did make one, thank you though. If anyone's interested, here it is:
Idol 5 6058D TWRP
So, I recently revisited this phone and saw that there was a new exploit to access the bootloader. I tried it and it worked. After some time of trial and error, I was able to dump the stock recovery. With this, I started to port TWRP to it. This...
forum.xda-developers.com
Click to expand...
Click to collapse
Good to hear.

Hi all!
Is there anything similar to 'boot-mode too'l for Linux machines?
What would be a proper command-foo for this task?
The usual method with adb/fastboot obviously doesn't work with
Alcatel IDOL 5 (6058D/MT6753).
To install TWRP on Alcatel Idol 5, you first need to unlock the bootloader.The process is a bit more involved for this device than it is on most others.
Click to expand...
Click to collapse
Thanks!

elocnix said:
Hi all!
Is there anything similar to 'boot-mode too'l for Linux machines?
What would be a proper command-foo for this task?
The usual method with adb/fastboot obviously doesn't work with
Alcatel IDOL 5 (6058D/MT6753).
Thanks!
Click to expand...
Click to collapse
I don't know if it will work with wine. But you should be able to run it from a VM.

Don't be a idiot like me and accidently flash the recovery image on the Alcatel 3T 8. it will permanently brick the device and sugar-mtk will not restore .