yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I have formatted whole flash and then flashed preloader,lk and lk2. Then I can flash whole stock rom except simlock.img and md3rom.img.

??????

I can see now flash logo on the screen. It is not a boot motion just logo. I mean there is no movement circle around flash logo.

The system.img file is from another rom I can’t flash the same system file in the rom.

What should i do now?

Thank you and thank you and thaaaaaank you
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Your device wants to revive.

But SPFlash tool is spending a time that looks that is really flashing, I mean, at least 1 or a little more time?

The third slot, did you try to load too authenticator file?

Is it so difficult to open back cover and disconnect a half minute the battery? so memory in the pins keep some kind of data.

What version of SPFlash tool are you using, try with one, just one version newer, I used in my last mt6757 (very similar to yours) the version v5,1728 and didn´t have the third slot for authenticator file, so maybe you can try with this version.

From here if nothing of this works then SPFlash tool has other feature 2 options that you can try:

- Instead od Download only you can try with "firmware upgrade"

- And like last resort it is the option "Format all" but this sometimes erase the imei, sometimes no.

If you can disconnect your battery or at least discharge completely, then charge to try to flash again maybe do some difference.
[Android Q&A, Help & Troubleshooting] DamianGong:
Tried the newest version of SPFlashtool. it says brom send da fail error. However, I tried the older version(1636) I tried to download the preloader bin only, and it says "Download ok" however, it disconnects and connects again. I have installed the newest vcom drivers. When tick(except the preloader) I get this mismatch error.

Also, I've tried to flash them 1 by 1, and here are the mismatch error as follows:

simlock.img

md3img

boot.img
[Android Q&A, Help & Troubleshooting] SubwayChamp:
But what is your case,

- you reach bootanimation or just stays in bootlogo

- and how you get this brick status,

- also do you have unlocked bootloader,

- you can enter to recovery, fastboot
[Android Q&A, Help & Troubleshooting] DamianGong:
I got to brick status when the android suddenly freezes and suddenly says system not responding. I pressed wait then suddenly it just restarted. After that, it just bootloop(Orange state). When I saw this, I followed the steps, now it doesn't boot anymore.

and it connects and disconnects (Boop sound, twice/2 seconds apart) I can't go recovery nor fastboot since the android itself just connects and disconnects.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I have those options also.

Is there anything kan help?
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Flashig process is real and I repeat it 3times bit same result.

I try it and it is same.

I am using 5.1636 and try (5.1640 ,5.1644 and 5.1728) but they didn’t work.

I am waiting to discharge the battery.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
It is the same thing after the battery has discharged and flash the rom again except md3img & simlock.
[Android Q&A, Help & Troubleshooting] DamianGong:
I believe we are able to proceed to fastboot, since i've tried the "reboot to bootloader, it says fastboot mode" The next thing we need to know is, how we can flash it through fastboot. It seems to be it is in CMD form.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
If your device is capable to reboot to fastboot then the syntax is relatively easy, I think there is no trouble with this, the other member flashed all partitions through these commands but device refuse to boot yet.

---------- Post added at 02:49 AM ---------- Previous post was at 02:45 AM ----------

Recently I see this, you have recovery stock intact.

put in the same folder than adb in your pc the zip where is your rom and apply option enable ADB in device and update through adb
[Android Q&A, Help & Troubleshooting] DamianGong:
Yes, I am already on the fastboot right now, and I am able to boot.img, however, I tried booting/flashing recovery, it says OEM is false. Tried the syntax "fastboot oem unlock" and pressed power up, its says "Unlock failed"
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Oh no, then your case is slightly different than of the other member, you have a locked bootloader and probably you ddidn´t have enabled before USB debugging and OEM unlock in developer settings so for this reason flash through fastboot probably doesn´t work for you.

In this case you have to use SPFlash tool or the official tool from Alcatel, you have some links to try it and report
[Android Q&A, Help & Troubleshooting] DamianGong:
Is it possible to unlock oem through SPflashtool? Since I am unable to boot it to tick usb debugging and oem unlock.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Flash this boot through SPFlash tool, unpack it and put in a folder with MT6755_Android_scatter.txt, this will enable adb and after that you have to flash again other partitions like system and userdata, try first through fastboot and if not through SPFlash tool, don´t reflash again other boot.img by now or this will disable again adb.

Also EFAYSAL flash this boot and try to boot.
[Android Q&A, Help & Troubleshooting] DamianGong:
After flashing, it says image mismatch error :(
[Android Q&A, Help & Troubleshooting] DamianGong:
This is the screenshot of the error as follows, I have managed to replace the boot.img you have sent(and backed up the replaced one)
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Upload me the last boot.img from your rom stock, maybe this is not the version that you are using.
[Android Q&A, Help & Troubleshooting] DamianGong:
Here is the file. Also, other buttons get the same error, same as efaysal(simlock and etc)
[Android Q&A, Help & Troubleshooting] SubwayChamp:
View attachment 4521794

View attachment 4521795
[Android Q&A, Help & Troubleshooting] DamianGong:
Tried both, still no luck :( I'm getting hopeless as I didn't know it got bricked without oem unlocked and usb debugging, and with this error
[Android Q&A, Help & Troubleshooting] SubwayChamp:
To flash through SPFlash tool you don´t need enable both features, this tool is a recursive method so no matter.

I hoped this boot can enable adb to have fastboot enable to flash with it.

You can´t flash this original boot nor any one through SPFlash tool?
[Android Q&A, Help & Troubleshooting] DamianGong:
Nope, either on fastboot, it says failed partition table doesn't exists. This is the only unit I am having trouble, I have my previous o+31.z and I brick/unbrick - flash a new rom numerous time.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Yes, this a particular device extremely difficult to revive, I unbricked many mtk devices and ever I say that they are almost unbrickeable but.....

Like I mentioned before I dislike that fastboot work for you cause you didn´t enable before USB debugging, OEM unlock and you have your bootloader locked.

Did you try to enter to fastboot and unlock it? What says in cmd window if you type fastboot devices try this to see if pc is recognicing although I don´t mind but...
[Android Q&A, Help & Troubleshooting] DamianGong:
Before this scenario, the unit works fine, suddenly "System is not responding" and I pressed wait. Then freezes, and it went bootloop(orange state). At somepoint, my PC recognizes the android in fastboot, however, I tried flashing twrp, it says it is locked. When I tried to unlock, it says, "Unlock failed" probably the worst thing happened to me :(
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Type first in cmd fastboot oem device info to get more details

Also you tried to flash twrp through fastboot or SPFlash tool? and what was the result?
[Android Q&A, Help & Troubleshooting] DamianGong:
Although, I have the access to "Android recovery" which still gives me hope. :/
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Try formatting data through stock recovery, something is avoiding that you can boot normally
[Android Q&A, Help & Troubleshooting] DamianGong:
I have sent a private message regarding this since I am having a habit of reading the first page
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Keep it here, maybe this can help others or others can help us. If you go to notifications and quoted posts is more easy to can clear the count again to 0.

You have to be sure that your device is totally off when you are trying with SPFlash tool and then from here connect to pc, sometimes works only vol up and at same moment connect it.

You can flash other partitions through SPFlash tool? and don´t jump nothing, What was it say in cmd when you typed fastboot oem device-info (this is the correct way, not the last)
[Android Q&A, Help & Troubleshooting] DamianGong:
Here's what it says.
[Android Q&A, Help & Troubleshooting] DamianGong:
This is what it says when I tried fastboot oem unlock.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
But with fastboot devices command it recogniced it?

What windos version are you using? I think W10 will work better
[Android Q&A, Help & Troubleshooting] DamianGong:
I am using windows 7 64 bit, I have tried windows 10 regarding this, still no luck. Same as before, I rooted Flash plus 2 here in windows 7
[Android Q&A, Help & Troubleshooting] SubwayChamp:
You say that you rooted and also try to installing twrp but with locked bootloader?

After to root it or try to, did you reboot it or was when you didn´t boot anymore?
[Android Q&A, Help & Troubleshooting] DamianGong:
I rooted the unit before, and it went smooth. Somehow the unit just suddenly says "System unit not responding" and just restarted, and went to bootloop. What I did is format + download all(from the rom before) now some rom(like boot.img) went mismatch error, and yes, before it went bootloop, oem isn't unlocked, so as usb debugging .:confused:
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Then you did bad elections, bootloader locked, root, format + download.

Search the right rom, this had to solved flashing it again through the official tool from Alcatel
[Android Q&A, Help & Troubleshooting] DamianGong:
Haven't tried this, I'm gonna find the official tool for the meantime as my last resort, I will keep up posted regarding the process.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
In one of the first posts I linked a zip, if I don't remember bad is inside, also there is other tool that you can try; sugar mtk tool
[Android Q&A, Help & Troubleshooting] DamianGong:
Oh yeah, I have downloaded one of your files on the first post and I have that sugar tool, although I don't have any background regarding that, I might try it as well
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I don’t think so. For me ,It doesn’t go in fastboot mood mode. It just reboot in same logo and “fastboot device” doesn’t give any result.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I get same error message of DamianGong.
[Android Q&A, Help & Troubleshooting] DamianGong:
Lucky for you, you have ticked the usb debugging, as well as OEM unlock. Mine wasn't.

---------- Post added at 04:00 PM ---------- Previous post was at 03:28 PM ----------

Since I wasn't able to flash twrp(recovery img, since oem is unlock) is there any way to fix this perhaps? It got bricked when OEM and usb debugging was UNTICKED(not applied) I believe this phone is good as RIP, since I am only have access to stock recovery and fastboot(though it won't let me flash twrp - oem lock/false)
[Android Q&A, Help & Troubleshooting] SubwayChamp:
And the other boot uploaded don´t accept to be flashed?

---------- Post added at 04:41 PM ---------- Previous post was at 04:36 PM ----------

In your case you haven´t fastboot enabled but for SPFlash tool and the official tool no matter that you don´t ticked these options in developer settings, they have to work same way.

You didn´t tell me if after to try to root you can reboot to system or it looks that it rooted but didn´t boot anymore.

Try in your stock recovery first;

- Mounting system

- Format data and then try to reboot.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Unfortunately no.

I try the fastboot mode but the phone doesn’t go in fastboot mode. It just turned off.

When I try to transfer files in adb mode “Apply update from ADB” the pc doesn’t recognize the unit although I have installed FLASH PLUS 2 USB DRIVER (ADB driver included),VCOM DRIVER and MT65xx Android Phone but the last one doesn’t able to start.
[Android Q&A, Help & Troubleshooting] DamianGong:
At the stock recovery, I pressed mount/system and it says system mounted.

After that, I pressed wipe data/factory reset

after a moment, it went ok, and i pressed reboot. Still stuck on the "Flash" logo. Also, before(at the spflashtool) boot.img, simlock.img, and mdimg3 won't work(img hdr mismatch)
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Both try this twrp if it can be flash it and boot into maybe we can try other ways.

View attachment 4522722
[Android Q&A, Help & Troubleshooting] DamianGong:
In regarding this, do I have to rename it as "recovery.img" on fastboot or spflashtool? Also,, if flashing it through spflashtool, can we use the scatter txt from the rom?
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I got this
[Android Q&A, Help & Troubleshooting] DamianGong:
Do you have access to fastboot through stock recovery? Let's see if there's any luck.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Rename it to recovery for SPFlash tool and put it beside scatter file in a folder.

And for fastboot rename it twrp so you can try;

fastboot boot twrp. Img (to try to boot directly to twrp) and then you can install it from the same recovery
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Unfortunately no. When I select it the unit turned off nothing else.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
When you try a single image in flash tool put it only with scatter-txt in a separate folder, not with all the other files and go to the file "logs", search in SPFlash tool where is allocated and delete this file, also try with other version of SPFlash tool.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I did that then I got error message about invalid preloader.

When I put preloader file in same folder I got the same previous error message about mismatch in post 79. I tried to flash preloader file then recovery.img and got error “ missmatch”.

This applies for TWRP and the other three boot files in your previous posts.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Don't put preloader in the same folder, only recovery (rename it so) and scatter file
[Android Q&A, Help & Troubleshooting] EFAYSAL:
First time I try this without preloader file. I rename the TWRP file to recovery.img and put it with scatter file in same folder just those two files but I got the error message in attachment “invalid preloader”.

Look to the image there is no preloader file in the folder. And I try it with and without the authentication file.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Can I do something with “Apply update from SD card” in stock recovery?
[Android Q&A, Help & Troubleshooting] DamianGong:
In my case(fastboot) oem unlock false. Same on efaysal(spflashtool) status preloader invalid, even though I have twrp and scatter on the same folder and nothing else.

---------- Post added at 01:40 AM ---------- Previous post was at 01:37 AM ----------

Happened to me as well. :/ Now we're on the same boat. Since there's no available technician in our area, I've been fixing my units myself(other units than this MTK)
[Android Q&A, Help & Troubleshooting] SubwayChamp:
That is only for updates through OTA cause we need META-INF (folder) to get works, if you find some OTA zip out there for your device maybe we can adapt it to flash the rom stock. I can try from other device but I´m not sure it works.

---------- Post added at 01:53 AM ---------- Previous post was at 01:46 AM ----------

But you couldn´t reboot to fastboot, no?

If this twrp doesn´t work it could be that just it doesn´t match with your device, I´ll made other to try.

By software just we are trying to find a solution but it looks that the display drivers need to be change them (flex cable to lcd), I hope no.
[Android Q&A, Help & Troubleshooting] DamianGong:
Is there other way to boot twrp without usb debugging and oem locked? Since the unit itself went to bootloop without those options. It happened suddenly without noticing
[Android Q&A, Help & Troubleshooting] SubwayChamp:
That unit itself goes to bootloop just means that it´s trying to reboot but something is avoiding this.

To boot to twrp you don´t need to check these options in developer settings, the problem is that you can´t flash it yet.

You have a working fastboot or not?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Here are some files https://www.androidinfotech.com/2016/12/root-alcatel-flash-plus-2-marshmallow-twrp.html

You can try with this adb/fastboot and here is a twrp.

Also here are some files to enable fastboot (must have to flash with the tool only this files lk.bin) and to install the rom with the proper version of SPFlash tool that have to work https://youtu.be/d8zPGPJ_uZY

Additional, a comment from a youtuber that can help;

"you can get back ur phone life again..you just flash again stock rom on spft but untick simlock and md3img .. and flash﻿"
[Android Q&A, Help & Troubleshooting] DamianGong:
Tried and this what happened
[Android Q&A, Help & Troubleshooting] SubwayChamp:
You have the zip "flash plus2 1006 rooting"

You are I guess in the folder 3 from the zip but upper you can see other folder "New folder twrp 3.1.0" it seems to be the new twrp, extract this folder as it is and use scatter and also auth file and flash this twrp (rename it) recovery using SPFlash tool v5,1636 that is in the link of youtube.

Before power off completely holding pwr by 10 seconds.
[Android Q&A, Help & Troubleshooting] DamianGong:
The rom that I was using was from the youtube, also the version of SPflashtool. However, this is the error I've got
[Android Q&A, Help & Troubleshooting] SubwayChamp:
There are two links of youtube, in one of the first post is linked this zip mentioned, and in this folder is twrp, follow the last stated, there are two recoveries from the zip flash plus2 rooting, you tried to flash which is in the folder 3 but inside the folder 3 there is other folder with the name mentioned in my last post, you have to rename this twrp for recovery and use the two files that you find inside. And use the version of SPFlash tool that is in the last youtube link, 2 post before, this version must be v5,1636
[Android Q&A, Help & Troubleshooting] DamianGong:
Here's what I did(SPflashtool 1636)

1: the lastest twrp from folder 3 was renamed recovery.img and I got the error

2. Tried the twrp(latest) and renamed recovery.img and I got the error

So I have formatted it again and tried to flash the stock room without simlock and md3img, apparently boot.img won't flash as imghdr mismatch error occurs.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Can I try it too? Anyway I'm out of home now. I have an idea, may be we can help each other if we readback the rom of our devices and exchange files, can this help us or at least one of us?

I tried also this file before and got same error. Then I put preloader file in the folder and got the same error of other files. “Missmatch”
[Android Q&A, Help & Troubleshooting] SubwayChamp:
In the last link from youtube https://youtu.be/d8zPGPJ_uZY there is a rom optimized according the youtuber, this rom (FP2-V6-OPT) have to be used with the version of SPFlash tool that is lInked too there and some user in a comment refer that at time to flash the rom it has to be unticked the options simlock and md3img

Better both you uninstall all the drivers and install all that you´ll find in this link, and use when you are trying fastboot a clean folder.

If someone or both have a working fastboot you can try to install this twrp that is in the folder indicated trough fastboot and don´t jump or ignore any detail to revive your device, both emmc or motherboard is working, is not dead. This tutorial from youtube worked in many user so something is doing wrong.

In the folder of SPFlash tool is the mt6755_auth file, this have to be used too ever
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Oh , this is the video that I hade tried to flash my phone with. Every time I try to flash a rom with new idea I do it with this rom. And the rom that let my device go into “Flash” logo is this one but without system file because it could not be flashed.

What about read back the rom and sharing rom files?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
This video have a lot of comments, some users refer that the step 23 and 24 are wrong sequences and the order had to be 24 and then 23 and this bricked some devices.

But try other rom but untick it these options simlocj and md3img, you refer before that these files were unabled to be flashed and the users refer that they have to be unticked.

Yes, better is to share both what versions are trying and also interchange some files from one to another folder
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Yes there is wrong between 23&24 and I have noticed that and did it by right way.

DamianeGong

Good ,so I will upload my rom and share it here ASAP.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
@DamianeGong

What’s your phone version? Mine is ”2HLCEU2” =(international).
[Android Q&A, Help & Troubleshooting] SubwayChamp:
[MENTION=9122901]EFAYSAL[/MENTION] [MENTION=9220654]DamianGong[/MENTION]

I found this site; http://www.flash3c.com/support/flash-plus-2/download-resources/

Here are various roms.

In the last link there is a PDF file "SD ROM Upgrade Step-by-step Guidance" indicating how update via stock recovery download it and read carefully.

It seems that some of these roms can work for update.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
It is the official website of flash but all links are broken I hade contact with support but they never answered mig.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I have found a custom update (firmware)for flash plus 2 here but I don’t know if they would help.

http://guideroot.net/alcatel-flash-plus-2-download-firmware-android-8-0/

And there is a blog that says that Alcatel flash plus 2 has the same motherboard of TCL 550 & TCL 562 but I could not found rom for those models also.