yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] SubwayChamp:
In one of the links time ago posted there was a backup for twrp with two files; lk.bin and boot.emmc but they are for restore through twrp so I will try to made one that matches for your device that is mt6755M this M is slightly more difficult to find but we´ll see. I don´t know if you try to flash twrp in the two ways, also let try it through sugar tool.

Let me download the rom for nougat, I will try to decompile and see if it´s really for your device, this site that you mentioned it seems to be a fake.

This link to the PDF is the only that works http://www.flash3c.com/wp-content/t...ade_Step-by-step_Guidance_Global_20160816.pdf download and read it and try to search the SDCARD version firmware that is mentioned here SVN1004, it´s needed to find a zip that contains inside META-INF folder cause the scripts to flash a stock rom through the stock recovery.

Despite this you can try with some zip rom that you have and put it in your sdcard and try an update from sdcard through stock recovery and see what happens.

Respect to the TCL both model it´s dangerous to try to flash it onto your device cause you would brick it completely with files from other device. TCL was the first distribution for China from Alcatel but it´s not the same exactly atleast that we can know. Although this, the file from this device if you find it, that you can try to flash without many risk is the system image only from stock rom. But if you find some custom recovery for this model it has to work too onto your device doing it some changes, let me know if you find.

Also here https://www.facebook.com/notes/andr...k-firmware-fl02-flash-plus-2/523807954479889/ there are some files to try.

Effectively, the link to custom updates is a fake, there are images for nexus devices.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
There is many files here and they talking about different rom versions but I don’t know which one could help if there is one.

https://xdaforums.com/general/devic...flash-plus-2-5-5-fhd-helio-p10-t3398513/page2

There is someone who has EU Version and he flashed the ph rom but his phone died . There is TWRP files. They talking about different roms for v1 , v2 ...... v6!!
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Now I found this thread exactly.

I´ve now more clear somethings, there are two versions 2 and 3GB and also that if the firmware doesn´t match exactly then it fails to flash and that if some scatter fails then you have to exchange for other and try again.

In this link there is a rom https://drive.google.com/file/d/0BwAGh1drb91SbzkxY05qQ19fdUE/view try it.

In the post #16 there from this threads is a link to twrp that is working for other users although it seems to be the same but it have to be flashed with scatter-txt from the post #17

In the post #29 there is a link to alcatel setup exe, it could be better.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Mine has 3gb ram with 32gb rom.

I have a Scatter file for 32GB.

I will try this and hope it will help and will retry again if it doesn’t help with the scatter which I have
[Android Q&A, Help & Troubleshooting] DamianGong:
Sorry for the late response, as I was competing an esports here in our area. [MENTION=9122901]EFAYSAL[/MENTION] the unit I have is the 1GB ram variant, this unit was intended for tinkering purposes(As this was given by a friend of mine) and for backup purposes. The unit just freeze and went to bootloop without the consent of oem unlock and usb debugging, and that is very challenging for me :/ I am using the ROM from https://www.youtube.com/watch?v=d8zPGPJ_uZY&feature=youtu.be I wonder why what is the mismatch regarding the ROM that was given from the youtube video, since I rooted the unit using THIS rom.
[Android Q&A, Help & Troubleshooting] DamianGong:
However, this is just my opinion, can we do OTA update/adb update on this unit?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Plz, read my post #107 on the previous page, there are some actions that you also can try, don´t jump/ignore nothing.
[Android Q&A, Help & Troubleshooting] DamianGong:
Just like flashing through stock recovery eh? I'll keep you posted regarding this. :fingers-crossed:
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I get missmatch error.

The Alcatel upgrade exe says It is a wrong model version when I select FL02 or 9095.

I try to flash v2 and v6 rom but no luck (missmatch error in system.img).
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Did you untick it these options simlock and md3img? and Did you try update through sdcard? or adb sideload through your stock recovery?
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I try to flash whole rom except preloader , lk, lk2 ,md3img and simlock.

I didn’t try to Update through as card or adb yet.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Don´t exclude preloader when you use SPFlash tool, just the other files.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Got it!

I’ll try again
[Android Q&A, Help & Troubleshooting] EFAYSAL:
When I am looking in my SD card I find TWRP files for my device. I don’t remember that I did this but the creat date is the same day when I root my phone. Can those files help?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Probably you copied these files into sdcard, they are for restore through twrp.

And maybe you flashed successfully twrp but cause you couldn't boot into twrp then the boot stock overwritten.

You need a working twrp to can flash this backup
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I could boot into TWRP when I tried to root the device. And now I find the recovery file but when I try to flash it SPflash asks for authentication file then ask for preloader file then I get error “mismatch “

So if the phone can boot into fastboot mode then I can flash this recovery file.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
1- If I understood well you rebooted to twrp before?

2- If yes I suppose that inmediately you flashed supersu, I´m right? but without formatting data?

3- But you have now stock recovery?

4- and you can´t boot into fastboot?

Ok, if sometime you could boot into this twrp then this recovery works for your device.

To try to flash it through SPFlash tool most properly you have to put in the same folder;

- preloader

- Auth file

- scatter-txt and

- recovery

Additional you can put in the same folder where is SPFlash tool (inside) using the modded version v5.1636
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Yes

No . TEWRP couldn’t read SD card. Then I reflash it again but the device couldn’t boot since that time.

Yes

Yes

I try it but it is the same result without this method. I get the same error message “mismatch “

—————————————————————————

Something I have noticed:

My phone doesn’t accept any rom . The problem is with the system and boot files. Some roms has 2GB system file and it occurs error (look on attachment) .other roms has 800MB system file ,this file is able to flash.

If I try to flash whole files v2 boot.img can’t be flashed. If I replace it with boot file from V6 it is will flashed but the device can’t boot in. But if I flash boot from V6 with 800Mb system file it success and device shows flash logo but doesn’t boot and it has stuck recovery but couldn’t go in fastboot mode and doesn’t able to recognize on adb mode.

—————————————-

I found rom contains METAL-INF and system folder.. it is names as V6. What can I do ?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
2.- Now I understand how you get bricked. All you had to do at this point was format data through twrp to get access to your sdcard internal and/or external, unfortunately in youtube video the user didn´t prevent anyone to this, for this reason like you couldn´t format data the protection avoid to device to reboot.

Then no need to find other twrp cause this version it works for you, so you need to install it, try again with SPFlash tool in one way that you didn´t yet, combining files like scatter, auth and preloader; these three files would be needed yes or yes in order to flash it.

Try to flash some boot that matches and then see if you have a working fastboot inmediately to this.

Now your fastboot is not working again cause your bootloader it´s not properly working too.

Flash system of 2 GB, this is most properly for your device and the boot from the other rom, combining could works.

Provide a link to this rom with META-INF, to take a look on it.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I can’t flash the 2GB system files. I can flash 800MB and 1.3 GB

But not 2GB.

This is the link for V6 :

https://drive.google.com/file/d/0BwAGh1drb91SNlBSX1JVM1Rhc0E/view
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I try to flash the same rom that I previously used for rooting. Simlock , md3img and boot.img couldn’t be flashed. The system file is 1.3GB and it is able to be flashed.

When I press PWR on the flash logo shows on screen and it disappear for 1second and come back again . It never happened before. It is look like the unit try to boot this time.

All that I need to know now is why I couldn’t flash boot.img although it has previously succeeded with all the excluded files not just the boot file.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I couldn’t believe it.

I repeat this one more time and now I can put the device into fastboot mode.

I try to flash the same recovery file I have used it for rooting in fastboot mode and it’s faild With error that oem unlocked is false.

I’m sure that it was unlocked. May be it’s happening because I reflash the rom so it’s locked .

Please tell me what have I to do now? I am afraid if I do something wrong I will loose this so l’m waiting for your reply.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I Try to unlock oem and flash recovery.img
[Android Q&A, Help & Troubleshooting] SubwayChamp:
So strange, I didn´t receive any message from you, now I see.

I´m scared that yes, when you flashed other rom you relocked your bootloader and what is worst yet, disabled USB debugging.

Try in fastboot to know bootloader status fastboot oem device-info
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I get error

FAILED (remote : unknown command)

Same for .......device_info

I try fastboot flashing get_unlock_ability

Unlock_ability=0
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Sugar keep saying that the device is rooted

Adb doesn’t recognize the unit.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
in fastboot type first simply fastboot devices to see if fastboot is recognicing,

I will try to inject magisk to your boot, upload me the last boot that worked for you.

I checked the rom in the link provided, the v6-OK and it´s a stock rom but flashable through twrp not through stock recovery, if you get install this twrp then you can flasj it through twrp.

If fastboot recognice device then try to flash twrp in this mode, you need hardly to flash this recovery
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Fastboot recognizes the device successfully.

This file is the last known boot file when device was able to boot but it isn’t able to be flashed now.

Please tell me how. I try fastboot boot recovery.img but it is failed.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Try fastboot flash recovery recovery. Img and then immediately before to do nothing more reboot to recovery, if successful let me know
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I get red state

How can I go to recovery mode again ?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Manually, buttons pwr + vol up, but first power off
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Doesn’t work I got this

How can go into fastboot mode .should flash the recovery file from the last rom through SPFlash?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Now to have to

- Go to fastboot using pwr + vol down, flash recovery

- In recovery format data

- power off, go to SPFLASHTOOL and flash the rom
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I can’t access recovery mode now.

When I press PWR&VOL Up the image in post 138 shows. There is no more recovery mode or fastboot.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Then it's erased

Flash it first only this through SPFlash tool
[Android Q&A, Help & Troubleshooting] EFAYSAL:
All recovery files that I have, make the mobile in red state . I try them all.

1. Boot into fastboot

2. Fastboot flash recovery (recovery file path)

3. Turn device off

4.press PWR&VOL+

5. Flash logo appear like image in post138

6. Turn device off and flash recovery from the V6rom with preloader so I can get recovery mode again and boot into fastboot again to try another recovery file.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
After two days of waiting. I hope there’s something new we could do it! Or should I give up?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Tell me. what happened, did you try to flash the zip rom through your stock recovery?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Try after this twrp, if you have fastboot working or through SPFlash tool.

View attachment 4528608
[Android Q&A, Help & Troubleshooting] EFAYSAL:
SPflash: It isn’t able to flash.

Fastboot: after flash ,boot in red state.

Which zip rom?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Don´t forget if you try to flash through SPFlash tool rename it to recovery and in fastboot the command is fastboot flash recovery recovery.img it can´t be that in fastboot shouldn´t flash it, ever it flash it but happens that sometimes recovery doesn´t reboot to

Any of your stock roms, just to try and see what happen
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I have did this all. (Rename the file and same command in fastboot)

Unfortunately nothing new happened when I tried to flash the rom. If it could be flashed then it show FLASH logo on the screen and stuck on it.

I don’t understand what do you mean

Have you got anything about this?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Problem then is your bootloader was locked again and you have USB debbugging disabled so not even a command device-info doesn´t work.

I uploaded 2 boots image in previous post that you can´t flash it but these boots have the ability to enable adb in your device so your last hope is flash some of them through SPFlash tool.

If none of these can´t be flashed then upload me the latest boot that you can flash sucessfully.

Just to clear i suppose that you typed fastboot oem device-info with smal letters; fastboot not Fastboot
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Here you will find how I typed fastboot command.

Your two boot files still unavailable for flash.

The boot file which is able to flash you will find it on attachment. But the last file that I am sure it was able to boot up but now it couldn’t be flashed you find it in post 134.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
By now your fastboot is disable.

Try to flash this boot through SPFlash tool to enable this option

View attachment 4530908
[Android Q&A, Help & Troubleshooting] EFAYSAL:
I didn’t receive any notification about ur reply.

Mismatch error occurs when I try to flash it through SPflash tool.

Flashing through fastboot ==> red state.

But how do you say that the fastboot is disable although files can be flashed through this mode?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
No, by now you can´t through fastboot. I suppose that when you type fastboot devices not even detects it.

That you have to get now is one of the last hope to solve this, and is try to flash twrp through ever SPFlash tool, and then try to restore some partitions or that some rom can be flashed ever through SPFlash tool.

I provided you a boot that have the adb connection enable but you say that you can´flash it, I don´t know what other files you put it in the same folder with this boot, remember that it requires ever the auth and scatter files and maybe also preloader to put it with any file that you´ll go to flash through SPFlash tool
[Android Q&A, Help & Troubleshooting] EFAYSAL:
Fastboot detects the phone and i can flash files through it. But if I type fastboot boot xxxxxx this command return failed oem unlocked is false.

I have typed that adb doesn’t recognize the phone.

I have a question: when I want the phone to go into recovery mode I have to press and hold PWR & VOL+ . Then I have multi choices (fastboot, adb mode ,.......)

So if I flash TWRP recovery file (fastboot flash recovery twrp.img/recovery.img) when the phone restart should it boot on TWRP recovery or I have to do the same thing I have did for Android recovery mode?

This command fastboot boot recovery.img occurs error because oem is locked. I think this command will put the device to boot on TWRP recovery .

I have done exactly like what you said for how to flash boot file through SPFLASH tool. Mismatch error on SPflash and red state after fastboot flashing so they both says this file isn’t suitable to the device. Is it right?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
It seems that your partition file turns unstable, so supposedly if your bootloader is really locked again you shouldn´t be able to flash anything onto device using this method but yes using SPFlash tool.

If you sucesfully flash recovery using fastboot using command fastboot flash recovery twrp.img you can avoid the next command fastboot boot twrp.img if it refuses to boot into recovery and simply exit from terminal, disconnect device, I´m saying after to flash if sucessfully the recovery, then to disconnecting device you have to power off and next reboot to recovery using combination keys pwr + vol up, it mean, disconnect and next press this two buttons and device have to pass through two states, first device turns off (continue holding buttons) and then device pass to recovery state

You have to first try in fastboot command fastboot devices then if pc recognices fastboot flash recovery twrp.img but if it´s not sucesfull then no sense to try to boot in it.

It has sense that the latest recovery that I uploaded for you don´t work and for this it isn´t able to be flashed but the first recovery that you flashed before from youtube tutorial it´s so strange that this recovery can´t be flash it anymore.

I recommend that when you will go to try to flash something using SPFlash tool put inside in a folder apart only the files that you will use and not all the files cause it´s not enough unticking the files that you won´t go to use, it means that if you´ll go to flash recovery put inside only 3 files; auth, scatter and recovery and maybe it´s needed preloader and a second attempt.
[Android Q&A, Help & Troubleshooting] EFAYSAL:
New try:

1. Format whole flash through SPflash.

2 Flashing V6 rom (YouTube file) without boot.img through SPflash.

3. successful Flashing of boot.img from V6 rom through fastboot.

it doesn’t show red state on screen.

The mobile shows flash logo and powered by android then it is flashing and the same screen comeback without the “red state “ lines. Is it mean something?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Then it seems that the flash was sucesfully, try to reboot to recovery and format data, there is something that it´s avoiding that device can reboot
[Android Q&A, Help & Troubleshooting] EFAYSAL:
It reboot to recovery and select wipe data/factory reset

All done

Reboot system now

Then it is the same
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Now you´ll go to try a thing slightly different; do you remember the backup of boot and lk.bin inside a zip in one of the links provided that are for restore through twrp? and if I don´t remember bad you had these files in your internal memory inside the twrp folder or made sure that you can copy these folder atleast to an ext sdcard by now and put it onto your device.

Pay attention what we´ll try;

You´ll go to flash twrp in your boot partition, not in your recovery partition.

Try first through fastboot if your device is detected typing; fastboot flash boot twrp.img then if sucessfull type fastboot reboot your device has to reboot to recovery.

If not sucessfull through fastboot then you´ll go to try through SPFlash tool, for this create a folder in c: drive, rename it just Alcatel by i.e. put inside auth, scatter, preloader and rename to your twrp.img like boot to try to flash it in the boot partition and execute the tool

Try al the twrp that you have
[Android Q&A, Help & Troubleshooting] EFAYSAL:
First of all , I will thank you for all.

I will travel away for five days. When I come back we will do it.

I do not know which file do you mean. Who has uploded it you or I?
[Android Q&A, Help & Troubleshooting] SubwayChamp:
This backup from twrp you have to put it in your internal memory or in your sdcard if you get boot into recovery through this method then try to restore it.

View attachment 4532252
[Android Q&A, Help & Troubleshooting] SubwayChamp:
You can recover your account or password just enter to the Google site there is an option. When FRP is activated in device then you usually can´t bind other account but it happens that sometimes installing again the stock rom and formatting data Google can allow you to associate a second account (not as primary) it means that it ever will remember the first account as it was registered in this device; this is a simple and legal trick. I can´t explain nothing related to bypass a FRP protection for ethical reasons and never had this issue although not ever is a case related to stolen device, sometimes the last user simply erase her/him data to protect it from a new user when once device was simply sold not even lost or stolen; it´s a fault from the last owner.
[Android Q&A, Help & Troubleshooting] riko7456:
Can you help me,,,???

i don't have twrp installed,,,

unlock bootloader via fastboot, but i cant check it,,,

maybe just adb,,,,

i need flashable rom if you have,,,

maybe i can flash it via adb,,,
[Android Q&A, Help & Troubleshooting] SubwayChamp:
In all this thread there are lot of links that I provided to OP, you tried something of these?

And now what is the status of your device;

How did it happen?

When you try to power on pass at least bootlogo and stay to bootanimation?

Can you enter to recovery? fastboot? did you unlocked bootloader?
[Android Q&A, Help & Troubleshooting] riko7456:
First of all, thank you for your attention

I am the secondhand user. I dont know my phone has been modified or not.

many ways to root fl02, but my phone does not boot normally. I do not even know where the mistake is, whether the fault is in me or the first user.

when I press power on, bootlogo and orange state appear.

I can enter recovery. when I choose "reboot to bootloader", my phone is switched off.

i think i cant enter to fastboot.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
In the post #4 there are some files that could be useful, download them and show what contain. Sometime ago I try to help to OP but probably yours is not exactly the same situation, I hope that you´re not hardbricked.

The usual way to unbrick is flashing the official rom though official tool Alcatel Mobile Upgrade; do you have the tool? and Do you have the official firmware?
[Android Q&A, Help & Troubleshooting] mrkjrmy:
Help on red state

I'm from PH. I have succeeded flashing all files except for simlock,md3img,boot. And now it's booting and I can go to reboot to bootloader but I can't unlock the oem. It already went hard bricked but luckily flashed the other files. I've tried to use

fastboot flash boot recovery.img and fastboot flash recovery recovery.img and it wen't red state. Any help?
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] pincakez:
i see official builds are coming up right now but no LOS official build till now

so it's coming this days ?
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] dfkt_:
All Android 8.1 ROMs still have the exact same bugs. Just because dotOS or crDroid chose to already go for 'official' status doesn't mean they're any more stable than Lineage. It just undermines what 'official' should stand for - a ROM where everything works. I'd rather that development took its time and the 'official' status really meant something.