Alcatel 1B Stock ROM / SIM unlock / etc.... - Alcatel 1 ROMs, Kernels, Recoveries, & Other Devel

ALCATEL 1B MEGATHREAD
( veken/seoul/TCL L7)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
STOCK ROM
Download
How to flash
TWRP
-Developement is halted due to technical challenges
SIM UNLOCK / CARRIER UNLOCK
Download STOCK ROM from above
Extract it and install Hex editor
Open file radiokiller.xml in hex editor
Copy line with partition "simlock"
Paste it into the file rawprogram0.xml
Flash rawprogram0 with QFIL and use loader.bin as firehose
Unlock succesful
ALCATEL MOBILE UPGRADE REGION LOCK BYPASS
Alcatel Mobile Upgrade is region locked and wont let you update to the latest version outside of RU
To bypass this, edit traceability.bin from the stock rom above. Change IMEIHERE with random numbers (or your imei) and then change GOD-5002F-2BALCZ12 to any region you like... for example GOD-5002F-2AARU12 and copy traceability line from radiokiller.xml to rawprogram0, then flash with QFIL
UNLOCKING BOOTLOADER / ROOTING
For now, it is not possible... However mentions of secret key is spread all around the phone partitions (mainly abl file)
So if you have any experience editing bootloaders you can unlock....
DISCLAIMER
IM NOT RESPONSIBLE FOR DAMAGED DEVICES BECAUSE U DIDNT FOLLOW THE INSTRUCTIONS

yo if you can give me a stock recovery.img i can build TWRP

notnoelchannel said:
yo if you can give me a stock recovery.img i can build TWRP
Click to expand...
Click to collapse
Stock recovery img is in the stock rom (click the download button). I already had one guy do it for me but he had problems compiling, but you can try. Also we cant unlock the bootloader (yet)

Hello. When i write this room i have a bootloop. I have alcatel 1b 5002h. Anybody have a clear rom for this device? On alcatel webside they dont have the files for this model. Anybody help me?

viper9595 said:
Hello. When i write this room i have a bootloop. I have alcatel 1b 5002h. Anybody have a clear rom for this device? On alcatel webside they dont have the files for this model. Anybody help me?
Click to expand...
Click to collapse
5002h model isnt compatible, due to it having different components than other variants. If you want to fix it, dm me on telegram. t.me/xinux360 or message me here on xda
edit: It actually is compatible

deleted, posted second reply by mistake

Hi I'm Liberia but my phone is not working here

KashiNEC said:
SIM UNLOCK
Click to expand...
Click to collapse
I need my sim card unlock

Leovace Cassell said:
I need my sim card unlock
Click to expand...
Click to collapse
Which model is it and what carrier is it locked to? You can find the model number under the battery. It should be 5002.-..........

Leovace Cassell said:
I need my sim card unlock
Click to expand...
Click to collapse
Also this only works if the phone is carrier locked. For example if it was sold by ATaT and you will try to insert a T-Mobile sim it wont work.... This will not magically remove pin code from the simcard

I am overwhelmed with the many types of models referenced by system within the firmware included with the device. If you access the following paths from an example MiXplorer file explorer, you will understand what I mean.
1- Go to /system/media/video
There you will notice multimedia related to what appears to be part of a promotion for various device models: TCL L7 5102P, Optus X Sight, Smart P11, TELSTRA Essential Plus 3, Alcatel 1B
All of them relatively similar, just a search on the web for each of them and the specifications will vary, they are almost related.
2- Go to /system/aio_custom/resources
there you will notice a sea of directories with information on Alcatel 1B models and maybe other models mentioned above. You can see for yourself there will be around 764 folders for quite a while, some with alphanumeric names I will cite some examples as there are too many:
5002A, 5002B, 5002D, 5002E, 5002F, 5002H...

Something that I have noticed in common within the various models mentioned in the 1st directory is that there is no reference to unlocking the bootloader, much less TWRP or any custom Rom. TCL has taken security on these devices seriously by limiting and hiding many things, mainly disabling OEM unlocking.

Due to technical limitations, and no further interest from other developers, im stopping any developement for this phone...

I have an Alcatel 1B (2022) 5031g and i can't understand why when I boot into fastboot mode with
Code:
adb reboot bootloader
and try
Code:
fastboot devices
nothing shows up. It's a new phone. Can someone help?

KashiNEC said:
ALCATEL 1B MEGATHREAD
( veken/seoul/TCL L7)
View attachment 5653599
STOCK ROM
Download
How to flash
TWRP
-Developement is halted due to technical challenges
SIM UNLOCK / CARRIER UNLOCK
Download STOCK ROM from above
Extract it and install Hex editor
Open file radiokiller.xml in hex editor
Copy line with partition "simlock"
Paste it into the file rawprogram0.xml
Flash rawprogram0 with QFIL and use loader.bin as firehose
Unlock succesful
ALCATEL MOBILE UPGRADE REGION LOCK BYPASS
Alcatel Mobile Upgrade is region locked and wont let you update to the latest version outside of RU
To bypass this, edit traceability.bin from the stock rom above. Change IMEIHERE with random numbers (or your imei) and then change GOD-5002F-2BALCZ12 to any region you like... for example GOD-5002F-2AARU12 and copy traceability line from radiokiller.xml to rawprogram0, then flash with QFIL
UNLOCKING BOOTLOADER / ROOTING
For now, it is not possible... However mentions of secret key is spread all around the phone partitions (mainly abl file)
So if you have any experience editing bootloaders you can unlock....
DISCLAIMER
IM NOT RESPONSIBLE FOR DAMAGED DEVICES BECAUSE U DIDNT FOLLOW THE INSTRUCTIONS
Click to expand...
Click to collapse
When I connect the phone at the last step I can not find a port in QFIL when the phone is connected. When you boot the phone to connect to QFIL what menu are you in? I get nothing when I hold vol up + down + power, but when I hold Vol up + power until logo and then let go of the power and continue to hold Vol up, the only menu I can get to seems to be Android recovery with reboot system now, apply update from sd, factory reset, clear cache partition, and power off.
This is a 2020 1b... what am I missing here? Thanks, for your time.

When I connect the phone at the last step I can not find a port in QFIL when the phone is connected. When you boot the phone to connect to QFIL what menu are you in? I get nothing when I hold vol up + down + power, but when I hold Vol up + power until logo and then let go of the power and continue to hold Vol up, the only menu I can get to seems to be Android recovery with reboot system now, apply update from sd, factory reset, clear cache partition, and power off.
This is a 2020 1b... what am I missing here? Thanks, for your time.

Related

Reinstall/Install MM/N on WiFi/LTE YOGA BOOK

This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you​
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507

[GUIDE] How to dump boot image and root Nokia 3.2 / 4.2

If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
So after you unlock the bootloader successfully, you definitely want to install custom ROM, or at least root the phone, right?
Here's the guide about rooting Nokia 3.2 / 4.2.
This guide could probably work on Nokia 6.2 / 7.2 in the future.
Step 1: Unlock the bootloader
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
For Nokia 3.2, you'll need to read this as well: https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841
Step 2: Acknowledge current slot
You have two methods.
Method 1: After USB debugging enabled, execute this command:
Code:
adb shell getprop ro.boot.slot_suffix
Method 2: Under fastboot mode, execute this command:
Code:
fastboot getvar current-slot
We assume the current slot is b.
Step 3: Trigger the phone to EDL mode again
There's a hidden command in aboot known as "fastboot reboot-emergency".
However, normal fastboot binary doesn't have that command at all, so we need to compile a binary or hack the binary.
For Windows users, I've provided the fastboot binary that can use this command, and I renamed it to edl-fastboot.exe. You can download it on the attachment below.
For macOS/Linux distro users, I'm afraid you have to fork the source code, edit related content and compile yourself.
So with this special version of fastboot binary, we can boot the phone to EDL mode directly:
Code:
edl-fastboot.exe reboot-emergency
But wait, why didn't you mention this command when you released bootloader unlock guide?
That's because, if you attempt to use this command under locked bootloader, bootloader will response "Permission denied, auth needed. " and refuse to proceed the command.
I don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
Click to expand...
Click to collapse
Step 4: Use partition manager to dump the partition
If you've came so far when unlocking the bootloader, you have already know the great partition manager.
Still, we assume the COM port number is 8 (COM8).
When the partition list appears, find "boot_b" (or boot_a if the current slot is a), right click on it, choose "Manage Partition Data" and click "Read Data". Then fh_loader binary will dump the boot image to your PC.
For Windows users, it's located at
Code:
%AppData%\Qualcomm\QFIL\COMPORT_8
Where %AppData% is actually C:\Users\your_user_name\AppData\Roaming .
The filename looks like this: ReadData_emmc_Lun0_0x3a000_Len65536_DT_07_09_2019_13_55_54.bin
Now close the partition manager, your phone will exit EDL mode and boot normally.
If you're interested in dumping full eMMC storage, you may want to read this: https://forum.xda-developers.com/android/general/guide-how-to-dump-write-storage-t3949588
Step 5: Install Magisk Manager and patch the boot image you dumped
I think everyone who reading this guide knows where to download Magisk Manager.
Copy the boot image you dumped with QFIL to Download directory in your phone's internal storage, and rename it to boot.img for your convenience.
In case you don't know how to patch, read this guide: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Step 6: Flash patched boot image and reinstall Magisk for ensurance
After you pulled patched boot image from your phone, reboot your phone to fastboot mode, then execute these commands:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Note, temporarily boot method introduced back for old A/B devices like Nokia 7 Plus no longer works on Nokia 3.2 / 4.2 - it will boot your phone to Qualcomm 900E mode.
Once your phone booted to normal OS, open Magisk Manager, and reinstall Magisk and required runtime to make the root much more effective.
You may want to read this guide if you want to inherit root along with OTA update: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Extra info about custom rom:
I've tested PHH-Treble GSI on Nokia 4.2 and it made me disappointed.
The vendor compatibility is worse than FIH made Android Phones.
You may want to read this for more details: https://github.com/phhusson/treble_experimentations/wiki/Nokia-4.2
Next preview: Stock firmware reinstallation guide. Note, Nokia 3.2 / 4.2 are not made by FIH, so OST LA no longer works on both devices.
Special thanks:
@topjohnwu for Magisk
Wingtech for leaking prototype units
Reserved
not detected
my pc doesn't detect the phone when its in edl mode. before people start asking I unlocked the bootloader by enabling oem unlock in the phone settings.
I have a TA-1156 (a 3.2 variant) that has a different mainboard layout. For quite a while, I tried in vain to bring it into EDL mode - until I just tried the fastboot command "flash unlock" which worked.
I guess I should have tried that right away as I did have the OEM unlocking option in the developer setup.
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
I can enter EDL mode easily now with the patched fastboot exe. The correct driver is active and QFIL detects the phone. However, as soon as I follow the instructions by setting the programmer, and then try to start the partition manager, the phone stops responding.
After a while, I get a "sahara" error about no reply from the phone.
I wonder if someone has a stock boot.img of the Nokia 3.2 (build 00EEA) lying around ...
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JFDee said:
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
Click to expand...
Click to collapse
My guess was right. Now I'm able to reply to myself with a solution.
I tried a different prog_emmc_firehose_8937_ddr than the one provided by @hikari_calyx in the unlock thread
There is a programmer with the same name in this firmware:
sprout-015B-0-00WW-B01 .rar
It's provided by @bouyhy01 in his rooting thread.
The size of the programmer file is slightly different:
Code:
hikari_calyx: 428,936 bytes
Firmware: 428,944 bytes
Long story short: the different programmer worked in QFIL, so the partition manager worked as well, I got my own boot image, patched, flashed and had root - finally ... Thanks for all the research work, hikari_calyx and bouyhy01 !
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment prog_emmc_firehose_8937_ddr_from_fw.zip
.
JFDee said:
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
View attachment 4867461
Click to expand...
Click to collapse
I guess the only point can be connected to the ground, for example, the RF shield is grounded.
JFDee said:
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment 4869373
.
Click to expand...
Click to collapse
Thanks for info. Mine Nokia 3.2 is a prototype unit, so I don't know the situation of other versions of Nokia 3.2.
Hello, I have tried this manual for rooting Nokia 4.2 with last security update of 5th of November. After 5 step (flashing patched boot image) my phone try to reboot and then asked for factory reset (Can't load android system - Your data may be corrupt). After making factory reset there were no root at all.
What can i do next ?
PS. It's strange enough when i download boot_b image it was 63.4 Mb snd when i have patched it by Magisk manager - the size od magisk_patched.img became 10.2 Mb

Moto E6S XT-2053-1 Unlock Bootloader, Disable Verity, ROOT Magisk, TWRP

I am perfom this Sorry for my english, I am from Ukraine
Download archive!
We unpack. Install the adb and mtk preloader drivers, if they are not installed, restart the computer.
In the smart, turn on the developers menu, in it - "Allow OEM unlock" and "USB debugging" and connect the smart to the computer.
We drop valuable photo data from the smart to the computer for any, and, without disconnecting the smart from the PC, run the script (with the phone connected to the PC and loaded into the android phone. Reboot_to_fastboot_getvar current-slot.bat (not from the admin, just click twice).
Smart will look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
we allow - put a daw, ok. We are waiting for the smart to reboot into fastboot, when the barcode appears on the smart screen, before that we do not press anything in the script
I did the scripts step by step, after each operation in the script window, press enter to continue, and so on until each script is closed
We look at our current slot in the window and remember the letter - a or b:
In the script, press enter so that the smart reboots and the script closes.
Run flash_tool.exe, go to this tab and check the boxes, as in the screenshot:
So we consider the necessary versions of orig. files, so as not to download and sew a specific firmware version for this instruction.
(And best of all, all the checkboxes, except for system, vendor, userdata - they are not critical, if they are not removed, it will take up a lot of space on the computer up to +74 gb, but I did not put these checkboxes, there must be some risk and passion )
We press "Read Back" and only then we connect the switched off smart to the PC, we wait, at the end we disconnect the bodies, do not touch it: sveta:
Go to this tab, remove all checkboxes! And we only put on lk_ with the letter of a non-your slot that we looked at, for example, you had slot "a" - so we put a check on lk_b and vice versa :
Click "Download" and connect the switched off smart to the PC (it was already turned off: sveta
As it flashes, we close the USB flash drive window, disconnect and turn on the smart, after loading, we connect it to the PC again, we already run the script
Unlock_Moto_E6S.bat, wait until the body reboots into a fastboot (to the barcode on the screen) and only then press the input step by step to continue in the script until it is completely closed.
Everything, the bodies are unlocked. Now you can get an excellent and fast root from Magisk, try other firmware, unsubscribe which one is buggy, which one flies. I haven't tried yet. Now I will write how to flash orig. kernel with magisk root (attached magisk boot for xt2053-1 4/64 fw RETEU 288-60-6-29 https://mirrors.lolinet.com/firmware/moto/fiji/official/RETEU/
Additionally, there is a script in the folder to delete the message when loading that the bootloader is unlocked, it does not interfere much, but I deleted it. Since this is not important, I separated it from the main script, since I did not test it on different versions of the firmware, in theory it should work on all versions, you can try after unlock. Or throw off ROM_45 from your firmware, I'll remove it from it. I now have the latest firmware flashed, it is on the server, but for some reason it did not fly through the air. If you flash it, then you can safely delete the message from the bootloader with my script, there is a file from it)
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
severagent007 said:
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
Click to expand...
Click to collapse
dude!! followed all your steps and i now have a bootloader unlocked and rooted device. how did you figure out the lk and signature to unlock that??
proof attached below
Слава Украине!!!
can the mods move this to the moto e6s forum so we can spread the news?
luridphantom said:
can the mods move this to the moto e6s forum so we can spread the news?
Click to expand...
Click to collapse
I took the first firmware I got to try from here: https://4pda.to/forum/index.php?showtopic=892755
but the firmware itself is everywhere, for example here:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
DeveloperLuke Roms - Browse /GSIs at SourceForge.net
sourceforge.net
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You can try to sew any GSI arm64 a/b from anywhere you find and choose the one you like, because smart supports Project Treble.
If you like one and will look cool and work firmware, post links here!
Tested it and it worked! Thanks a lot!
Now looking for delevoping some roms to this device
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
refrigerador67 said:
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
Click to expand...
Click to collapse
did you use the auth file that comes with sp flash tool? without that your device wont boot properly
Yes, i used the correct download agent and auth file
interesting, i followed all his steps and had no problem rooting it. try backtracking with his scripts again?
Solved it, also me and a developer are working on a new, more simple and automated script. Still haven't figured out how to flash the lk via script.
When is done i will post a complete guide in the moto e6s forums on how to do it, i think it might work well, but i would have to test in a non-unlocked device
Can someone please make a video with explanation, I didn't understand very well what is done, so I won't touch anything, but I thank those who record a video explaining it to me (I'm Brazilian)
Here you have a more straight forward guide, note that is still in testing
[GUIDE] How to unlock bootloader on E6s
Hello, in this guide i will show you how to unlock the bootloader on Moto E6s ;) (Sadly for now this guide is Windows only) CAUTION You are doing this AT YOUR OWN RISK! I will NOT take responsibility if you brick your device! Also, remember to...
forum.xda-developers.com
Excuse my ignorance, do you think it is compatible for the XT2053-5 model?
cannot use fastboot flash boot magiskboot.img
sign failed
partition flash is not allowed
hey is the moto e6+ twrp work on e6s

Huawei P9 EVA-L09 FRP Bypass + Other models (free)

Its taken me a while to figure out a way to bypass the FRP (Factory Reset Protection) Lock on my Huawei EVA-L09 and do so while not bricking my device or installing shady software/roms so if this helps I hope you leave me a like and comment how long its taken you before you found this guide.
Its completely free as I refuse to pay money which I hope you appreciate as every other guide wants you to pay to unlock a device so no matter what level of skills you are this should help you to gain access to you're Huawei EVA-L09 and other models (I've also used this method on a Huawei P Smart (FIG) but this should also work on all the devices listed in the table below)
DeviceModelBootloaderHuawei P8 Lite (2015)ALEKirin 620Huawei Y6IICAMKirin 620Honor 5C / 7 LiteNEMKirin 65x (A)Honor 7XBNDKirin 65x (A)Honor 9 LiteLLDKirin 65x (A)Huawei MediaPad T5AGS2Kirin 65x (A)Huawei Nova 2PICKirin 65x (A)Huawei P10 LiteWASKirin 65x (A)Huawei P20 Lite / Nova 3eANEKirin 65x (A)Huawei P8 Lite (2017)PRAKirin 65x (A)Huawei P9 LiteVNSKirin 65x (A)Huawei Y9 (2018)FLAKirin 65x (A)Huawei MediaPad M5 LiteBAH2Kirin 65x (B)Huawei Nova 2i / Mate 10 LiteRNEKirin 65x (B)Huawei P Smart 2018FIGKirin 65x (B)Honor 6 PlusPEKirin 925Huawei P8GRAKirin 935Honor 8 Pro / V9DUKKirin 950Honor 8FRDKirin 950Huawei P9 StandartEVAKirin 950Honor 9STFKirin 960Huawei Mate 9 ProLONKirin 960Huawei Mate 9MHAKirin 960Huawei MediaPad M5CMRKirin 960Huawei Nova 2sHWIKirin 960Huawei P10VTRKirin 960
First download and extract the Android SDK Platform-Tools package for windows from -> https://developer.android.com/studio/command-line/adb
Next download drivers from -> https://adb.clockworkmod.com/ and run .exe file
Next go to -> https://github.com/mashed-potatoes/PotatoNV and read through the entire page and follow the steps to install HiSuite, test point drivers and latest version of PotatoNV and find out where you're test point are on you're device and learn how to use the tool
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open PotatoNV and click disable FBlock and choose you're bootloader (refer to list on GitHub Repo) in my case for the Huawei EVA-L09 it was the Kirin 950 and follow the repo instructions to ground you're test point while inserting you're USB, now the target device field should show you're device then click start! and If you've followed the steps correctly then congrats you've generated a new bootloader code and got the following display.
Click to expand...
Click to collapse
From the display write down the "New Unlock Code" + "Build number" for later
Click to expand...
Click to collapse
Now we need the firmware to flash
Go to -> http://huawei-firmware.com/phone-list/ to find you're compatible firmware
Click to expand...
Click to collapse
My build number was "EVA-L09C02B363" so on the site I searched for that build number but found nothing so I removed 1 character from the end "EVA-L09C02B36" and found 2 results for "Huawei P9 EVA-L09C02B361 Firmware"
If you cant find a result keep removing 1 character from the end of you're build number until you can find the closet build to yours and Download it
Boot phone into fastboot mode
In the Android SDK Platform-Tools package folder hold In "CTRL + Shift" and Right click in the folder and click the option "open PowerShell window here"
In PowerShell type the following command "./fastboot oem unlock YOUR_CODE_HERE"
Press the volume key to select unlock bootloader on you're phone and press the power button (Now you've unlocked you're bootloader)
Download the firmware and extract the files and move the entire Dload folder to an SDcard (rename the SDcard SDcard) and insert it into you're device
Now boot the phone with both volume buttons pressed down and power button and let it install the new firmware
Click to expand...
Click to collapse
I personally had an error at 99% of install doing it this way so I had to manually flash each partition if you have the same issue then follow the steps
Download the tool Huaweiupdateextract tool -> https://www.leakite.com/flash-huawei-ota-update-without-sdcard/
Click to expand...
Click to collapse
And click "click", now browse for the update.app file inside the Dload folder and right click on the files and click extract all and save them into the Android SDK Platform-Tools package folder you extracted earlier
Boot phone into fastboot mode
Click to expand...
Click to collapse
Now you need to manually flash every .img file you extracted to the corresponding partition, all the .img files are saved in CAPSLOCK and the corresponding partition you need to flash to is the file name in all lowercase minus the .img part so for example the file RECOVERY.img needs to be flashed to the recovery partition and USERDATA.img to userdata and so on
In the same Powershell Window from earlier type "./fastboot flash *partition" "PARTITION.img" and replace partition with every img you extracted, example for USERDATA.img: "./fastboot flash userdata USERDATA.img"
Some flash's may fail, just move on to the next
Then type "./fastboot reboot"
Click to expand...
Click to collapse
And now skip through everything and access you're phone, I then personally booted my phone into Erecovery and clicked Install firmware and recovery and signed into my wifi after downloading I opened my phone and inserted my sim card (in my case it was lyca mobile and after the phone accepts the sim you will be prompted to take the system update, I flashed build EVA-L09C02B361 to my device but now I can update to my original build number EVA-L09C02B363.
Hopefully if you followed everything correctly you've just bypassed FRP.
You're welcome as someone who dosent have a lot to spend on tech I really value this sort of information and hopefully this full guide can help even a beginner gain access to there bricked phone.
Let me know if this helps!
doesn't work on Huawei Y6II CAM-L21 ..
kalinx said:
doesn't work on Huawei Y6II CAM-L21 ..
Click to expand...
Click to collapse
Did you ground the test point while clicking start?
brokeboy said:
Did you ground the test point while clicking start?
Click to expand...
Click to collapse
yes, in many ways i try it but this doesn't work too
kalinx said:
yes, in many ways i try it but this doesn't work too
Click to expand...
Click to collapse
Can you run it without Fblock and then run again with it ticked?
Yes I was struggling with it yesterday all day, in many ways. Now I get off. I will buy Sony Xperia M4 aqua with very easy root, I get unlock code from Sony website. Damn you HUAWEI! :/
kalinx said:
Yes I was struggling with it yesterday all day, in many ways. Now I get off. I will buy Sony Xperia M4 aqua with very easy root, I get unlock code from Sony website. Damn you HUAWEI! :/
Click to expand...
Click to collapse
Can you explain every step you did before to get to that point, also what's wrong with you're device?
Can this process work on Honor 10 col l29? He has kirin 970. Thank you.
levis36 said:
Can this process work on Honor 10 col l29? He has kirin 970. Thank you.
Click to expand...
Click to collapse
If its not on the list then it isn't supported but I believe if you look through the repo maybe someone forked it or there might be an alternative... I typed in honor in the questions and found this but there could be more
I solved it by changing the motherboard. I bought a phone with a broken display, 4 €, I changed the card and it did not have a lock on the screen and I entered the settings, return to the factory settings and everything goes ok. The new motherboard has emui 10.0.0 4 / 64gb and the old one was emui 8.1 which I failed to unlock I don't know the specifications it had. I would have liked to unlock the other one can have 6 / 128g.
levis36 said:
I solved it by changing the motherboard. I bought a phone with a broken display, 4 €, I changed the card and it did not have a lock on the screen and I entered the settings, return to the factory settings and everything goes ok. The new motherboard has emui 10.0.0 4 / 64gb and the old one was emui 8.1 which I failed to unlock I don't know the specifications it had. I would have liked to unlock the other one can have 6 / 128g.
Click to expand...
Click to collapse
Well done, that's good way to get past it... What phone did you take the motherboard from? Did you not find any info on how to use the bootloader unlocker with you're Honor 10 COL-L29 (Kirin 970)?
I tried 3 methods and none of them worked, they were all restricted, I got to a point and I couldn't move on.
Hi, I have a mate 9 with FRP and Bootloader locked, and when I try to unlock bootloader via fastboot, I have a warning telling that FRP needs to be unlocked first. Do you have any suggestiong?
Well, I did it at last After I have done this here and got no FRP bypass, I continued to google because this is weird, being able to run ADB/Fastboot commands, but unable to remove damn FRP. I have found this tool and it worked:
Download Huawei FRP and ID remove Tool For PC
Download Huawei FRP and ID remove Tool For PC if you want to bypass FRP lock google account from Huawei/Honor mobile
huaweiflash.com
So I can now thank the author for this guide, although unclear in some parts, then it has led finally to success. I have spent a couple of hours yesterday trying that bypass from the device (each and every method to start Youtube/Chrome/Maps/Google vie Talkback is already blocked as of now). Then a couple of hours for this guide. I could have purchased me an open phone instead of cracking this one but I wanted to play with some Huawei without having to pay anything.
There were unclear point in the guide, I elaborate
- to start fastboot mode: keep Volume down pressed and connect USB cable.
- you don't need specifically powershell, command line works as well
- the reflash is done from 32GB FAT32 formatted card named SDCARD which contained the unpacked folder dload with firmware files (SDCARD:/dload/<files>)
---initial comment---
EVA-L09 here.
Well, the procedure as described does not remove FRP lock.
PotatoNV worked, oem unlock command went through as well, but... Fastboot screen shows "FRP Lock" in green before the "oem unlock" command run; after the command and subsequent lowlevel reset; and after reflash.
The device asks the Google account after boot the same way as before the unlock/reflash.
Maybe the cumbersome way how you reflashed the phone is instrumental to enable FRP bypass (I have found exactly the same software build and my phone updated normally to 100% from SD card).
I have a P9 EVA-L09 device that has FRP locked. i try this method without PC and its work for me

How To Guide TCL 20 5G Unlock and Root

Warning:
This isn't my method and I haven't tested it myself, Im just posting it in case it helps someone.
Procedure was taken from this article, so beware of auto-translation to english.
Even if it uses the MTKroot application and this phone is Qualcomm, it looks legit as it installs the Qualcomm drivers during the process.
All credits go to the original author (thanks a lot!), just pasting this here in case the site goes offline in the future.
I don't take any responsability and I won't be supporting any bricked phones.
Test it under your own risk!
How to Root on TCL 20 5G Phone​
In the tutorial below you can find an automatic process to root the TCL 20 5G smartphones, through which you will get access to the root in a few minutes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Problems finding the boot.img file?, check
this.
What is it to do root?
Superuser or root is the usual name assigned to user accounts that have all rights in all forms of access, both monousual and multi-user.
Rooting a device is a method that makes it easier for the user of a computer with Android to gain privileged access to the system in a similar way to administrative permissions in Linux or Unix systems, allowing to cross any system barriers as well as software that could be established by the manufacturer or network operator.
Benefits of rooting for your TCL 20 5G
Remove all types of Bloatware simply and delete potentially useless system applications.
Being able to get extra storage space.
Customize system in-depth adjustments, such as releasing TCL 20 5G, repairing the IMEI of our TCL 20 5G and MAC steering, overclock among many possibilities.
Use programs designed only for those cell phones that have superuser permits.
Adapting or creating new partitions in memory (Watch out, doing this can be extremely dangerous to device integrity).
Create bakups or backups of the partition system or export the rom.
Precautions and warnings that we must always keep in mind
The mobile device shall cease the coverage of the guarantee granted by the manufacturer.
Risk that harmful applications can get permission from Superuser.
Threat of damage or deterioration of data during the procedure, therefore I recommend you in any case to back up before starting the root.
The Firmware of your TCL 20 5G may be harmed, it is recommended to be sure to be able to obtain a valid copy of the firmware if necessary.
Support for OTA upgrades will end up cancelled.
Conditions of the procedure
PC with Windows XP system or subsequent, architectures 32/64bits.
USB to Micro USB data cable.
Download to your computer the latest version of MTKroot v2.5.5 tool for your TCL 20 5G.
Download the original firmware for your terminal from where you will have to extract the boot component if possible from the manufacturer's online technical service.
If you fail to find an original TCL 20 5G firmware as an alternative you can also dispose of the boot component directly from your phone easily by taking the steps of this tutorial.
Settings to be made on the TCL 20 5G phone
The first thing we will have to do, obviously, will be to configure the necessary adjustments for the process, which basically consist of activating USB debugging and unlocking OEM.
These configurations are included in the development menu, which you must have unlocked in advance by pressing 7 times continuously on top of;
Configuration-"Downer information - version of the software or compilation number.
How to root the mobile phone TCL 20 5G easily​
First of all you must unzip the contents of the package previously downloaded to the Windows computer desktop and then run MTKroot v2.5.5.
Run MTKroot v2.5.5 for TCL 20 5G
Click Drivers - Qualcomm and complete the installation of the respective drivers.
Install Qualcomm drivers for TCL 20 5G
Take these exact same steps to implement the installation of ADB drivers.
Note: The MTKroot v2.5.5 tool incorporates all the updated drivers that are required by TCL 20 5G.
Then connect your team TCL 20 5G to the computer using a USB data cable and click on USB restart.
Click on the top left in No boot. - Load, add the boot.img file and then click Process patch.
Automatically the Magisk Manager application will be started on your TCL 20 5G, make the indications that will be on your screen to patch the boot.
Then you have to click on ADB Test and when you can read the message - Recognized Device you must press the Go to Fastboot button.
TCL 20 5G Restart USB . Test ADB . Fastboot
Wait for the meantime the TCL 20 5G restart with bootloader mode, then click the Test Fastboot button.
Again wait until the message comes out - Device found to be able to proceed to the next step.
​Release the bootloader from TCL 20 5G cell phones​In the next step you must unlock the bootloader to your TCL 20 5G, which you will do in a completely automated way.
Although remember that you must omit that operation if you had done it before.
Click on Test Bootloader to ensure your status is assured.
Check to bootloader TCL 20 5G
If you want to open the bootloader to TCL 20 5G simply click Unlock Bootloader -. Accept and then complete the suggestions that will be on the 20 5G TCL screen.
Remember to press the button upload the volume to unlock.
Unlock bootloader on TCL 20 5G
Note: When you release the bootloader, your smartphone will be resected to the default state.
Consider it appropriate to create a backup or simply copy all the files, contacts, photos and other data within an external memory.
After releasing the bootloader the next step will be to complete the process and finally leave your phone with the corresponding root privileges.
Head to the top of the left of the software and choose the rooting option, then click the Root button at the bottom.
Select Root TCL 20 5G
In less than 5 seconds the device will be rooted, so the word "OK" projected in the terminal and in the MTKroot v2.5.5.
Later click the Exit button to return your TCL 20 5G cell phone will restart the Android system.
Once the TCL 20 5G restarts completely, click Apps - Install Magisk and make sure you if the Magisk Manager app is effectively on your phone desk.
In order for the Magisk Manager application to be able to function properly, you must first connect TCL 20 5G to the Internet, either by wi-fi or mobile data.
To finish the tutorial you just click on Check Root - then accept and nothing else.
Test Root TCL 20 5G
Note: In case the Magisk Manager App fails to install at the first, click the Uninstall button, wait two seconds and again do once you click on the Magisk Instant button.
Summary Steps
Summary of the Rootear TCL 20 5G steps
Start MTKroot v2.5.5 utility and connect your TCL 20 5G to your PC.
Restart your TCL 20 5G in fastboot mode by clicking on the Go to Fastboot button - Test Fastboot.
If necessary, unlock the bootloader by clicking Liberate Bootloader.
Finally select the root wing option and press the Root button.
I thought MTKRoot only worked on mediatek chipsets. These phones have Qualcomm cpus and gpus.
We dont have file boot.img to do it
Comment edited since information in it was not useful to the thread
The situation looks like this: someone is messaging me about tcl-t810s, which is the model of my phone, and they need rom tcl-t810s, but they are giving me tcl-t767h rom instead. Could you please clarify what you meant by that? Perhaps, you could provide more information about what you are trying to achieve and why you are suggesting the rom for a different phone model. This could help us determine if the tcl-t767h rom is compatible with my tcl-t810s model and if it could solve the problem you are looking for.
DoctorBooty said:
^
Click to expand...
Click to collapse
Profesornauk said:
The situation looks like this: someone is messaging me about tcl-t810s, which is the model of my phone, and they need rom tcl-t810s, but they are giving me tcl-t767h rom instead. Could you please clarify what you meant by that? Perhaps, you could provide more information about what you are trying to achieve and why you are suggesting the rom for a different phone model. This could help us determine if the tcl-t767h rom is compatible with my tcl-t810s model and if it could solve the problem you are looking for.
Click to expand...
Click to collapse
I see, I wasn't aware that they were different models. I apologize. I'll delete my previous comment
DoctorBooty said:
I see, I wasn't aware that they were different models. I apologize. I'll delete my previous comment
Click to expand...
Click to collapse
Do you have contact with Gabby or did he tell you how to access the boot.img on TCL? That would be some clue
Profesornauk said:
Do you have contact with Gabby or did he tell you how to access the boot.img on TCL? That would be some clue
Click to expand...
Click to collapse
The files were in a paid site. Gaby happened to have a subscription in that site and she shared it after I requested it. I can't remember the site's name but it only had those files regarding TCL models
link to the latest version of MTKroot v2.5.5 tool is no longer valid, need an updated link if possible
update: found this link, seems to be legit MTKroot v2.7b (2022): https://drive.google.com/u/0/uc?id=1wnXGGca-uznK1bgG4WLSREnZ_nQXuEsY&export=download
Androiderz said:
link to the latest version of MTKroot v2.5.5 tool is no longer valid, need an updated link if possible
update: found this link, seems to be legit MTKroot v2.7b (2022): https://drive.google.com/u/0/uc?id=1wnXGGca-uznK1bgG4WLSREnZ_nQXuEsY&export=download
Click to expand...
Click to collapse
broken links

Categories

Resources