Develop Bugs

[ROM][James][Nora] Unofficial Lineage OS 15.1 for Moto E5 Play (beta v1.01)

LineageOS 15.1 (Beta v1.01) originally for Moto E5 Play (james) working on Moto E5 (Nora)
Very Important!!!!
I've just found the way to boot sucessfully LOS 15.1 on nora_row, the ROM was originally made by @MotoJunkie01, so I'm not taking this ROM as mine, I've mentioned that I'm not a dev, I just love to share what I found, I hope this won't cause any problem and it will be useful for you guys.
Previously I've shared how to root Moto E5 (Nora) because there wasn't any specific info for that variant, TWRP and Root Guide was only for Play/Plus, and then after some attemps, I finally found a way to use TWRP and how to flash LOS 15.1
Disclaimer
I'm not responsible for any dead SD cards/phones
If your phone turns into a nuclear bomb
If your dog/cat complain about you
Advertisment
The ROM is working almost fine but "Keep in mind that I have XT1944-2" also it is a beta ROM and if my previous guide of root didn't work properly, you shouldn't try to install it, because it may result on a brick or something else, as always is mentioned, try by your own risk.
BUGS
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
You tell me
Requirements
1. The most important and obviously, unlocked bootloader, a computer, and just basic knowldge
2. Stock ROM zip, in case of something is wrong and because you'll need to extract boot.img, here are the links and a guide to recover your phone in case of brick: https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
3. TWRP recovery. You can get it here: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
4. You may wonder how to install TWRP, I must admit that it's not possible on Nora (causes brick) but searching here in XDA I've found that you can boot into TWRP without installing and also if you make a backup it will work in case of emergency
5. Platform tools folder that contains fastboot and adb drivers (your boot.img must be extracted here): https://www.dropbox.com/s/c3c8rev5e40gy5b/platform-tools-latest-windows.zip?dl=0
6. Remember to put the ROM and Gapps on your SD:
ROM: https://drive.google.com/open?id=1F2rC7zIZPqod3vMC1t22uhNYMQbf56K6
Gapps: https://drive.google.com/drive/folders/1rHf5XIs7XK3kWFFLekjrK0ub_bKnSlUI
Instructions
1. First of all boot into bootloader or fastboot (power & volume down) and connect your phone to your PC
2. At this point it is supposed that you have downloaded platform tools folder and all necessary zips (stock ROM, LOS, gapps), then inside the folder press Shift+Right Click, and select "open CMD window here" for Windows 7, on Windows 8 and up just click "Archive", then when CMD it's open, type: fastboot boot twrp_james.img Your phone automatically will reboot into TWRP.
3. The recovery will delay 1 or 2 minutes to start and it will ask us for our key to decrypt data. Just press cancel, because we don't have that key, and that option is not working and swipe to allow modifications. Don't mount anything, what it is already mounted is fine, only you can mount SD Card, in case that is not mounted, if you don't have a SD Card you wouldn't be able to make a backup
4. Go to backup section, and choose SD Card to put your backup there, remember that the Backup couldn't be saved on Internal Storage because the ROM will wipe Internal Storage and System, then if you choose all the partitions nothing wrong would happen, but if you are not pretty sure, just skip data and cache
5. The time that TWRP will took to backup depends on the things that you have on your system (Ignore red letters that show some errors)
6. Then go to Wipe section and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting and then go to reboot section and choose bootloader because remember that TWRP is not installed and we nned to reboot the recovery, then use again CMD to boot into TWRP
7. Then we are again on TWRP, then press Install, select SD Card and look for the ROM zip and Gapps and swipe to flash, it's very fast the installation, wait until it finish and reboot your device into bootloader, It will be with red letters, but don't be affraid.
8. Another important thing, that ROM, contains boot.img from Moto E5 Play, that's what I told you, that you will need to use boot.img from stock ROM, then go to Platform Tools Folder and again open CMD (Shift+Left Click for W7) and type: fastboot flash boot boot.img Wait until it finish and type fastboot reboot
9. And that's all, first boot will delay, be patience. Additionally I couldn't find a way to skip force encrypt, so the phone will be encrypted and it will reboot, sometimes if you reboot the ROM it would reboot again, it's normal, As this ROM it's unnofficial it will show tha your device is uncertified but you can hide that notifications and use your phone normally.
Magisk, Xposed and Substratum work, but choose carefully what are you going to install because some modules will cause problems or a bootloop, if you need some help write your comments and experiences. YouTube for some reason open but didn't shows anything.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to @Deivid_21 for sharing working gapps
Thanks to the entire LineageOS team;

This is great news. Slowly but surely, development for the entire Moto E5 series is growing. Great work on this OP.

MotoJunkie01 said:
This is great news. Slowly but surely, development for the entire Moto E5 series is growing. Great work on this OP.
Click to expand...
Click to collapse
Yeah thank you, but I was unable to find a no verity kernel for E5, Play and Plus have got it, but this one not, then thanks for sharing a LOS 15.1 it's cool just the only bug was the camera but because of that encryption the ROM became laggy, I wish I could have a good computer to compile but well it seems to hard, anyway i hope more coming ROMS because it's sad that LOS 16 it's already released and we hardly have got just one but it's appreciated the time and effort for this one

Fersho said:
Yeah thank you, but I was unable to find a no verity kernel for E5, Play and Plus have got it, but this one not, then thanks for sharing a LOS 15.1 it's cool just the only bug was the camera but because of that encryption the ROM became laggy, I wish I could have a good computer to compile but well it seems to hard, anyway i hope more coming ROMS because it's sad that LOS 16 it's already released and we hardly have got just one but it's appreciated the time and effort for this one
Click to expand...
Click to collapse
Yeah that's my dilemma as well. I have neither the time nor regular access to a high quality machine to compile. I have a port for Lineage 16.0 for the E5 Play which boots and functions somewhat. When I can smooth some things out and get it a bit more stable, I'll post it as well.
You should post a no-verity kernel for the E5 for others to use. It would be appreciated I'm sure.

MotoJunkie01 said:
Yeah that's my dilemma as well. I have neither the time nor regular access to a high quality machine to compile. I have a port for Lineage 16.0 for the E5 Play which boots and functions somewhat. When I can smooth some things out and get it a bit more stable, I'll post it as well.
You should post a no-verity kernel for the E5 for others to use. It would be appreciated I'm sure.
Click to expand...
Click to collapse
For real? I would really love to test Pie, pls upload it, then I'm trying to post a no-verity kernel but then how am I going to extract the necessary things? I had seen a tutorial to unpack boot.img but then I don't know how to disable dm vrity or where are the files located on Moto E5 Play/Plus kernel

Fersho said:
For real? I would really love to test Pie, pls upload it, then I'm trying to post a no-verity kernel but then how am I going to extract the necessary things? I had seen a tutorial to unpack boot.img but then I don't know how to disable dm vrity or where are the files located on Moto E5 Play/Plus kernel
Click to expand...
Click to collapse
Here is an easier method -- install the stock boot image on your device using either fastboot or TWRP. Then, in TWRP, install this boot image patch script -- https://drive.google.com/file/d/1oLrNL3OYhwlCCLOtLdQEQM4tGsIucsPQ/view?usp=drivesdk
It will unpack, patch, repack and flash the modified boot image back to your boot partition, disabling dm-verity. Then use TWRP to make a backup of your /boot partition. Using a file manager, rename the backup from boot.emmc.win to boot.img and you're done. You'll then have a no-verity kernel in boot.img format. The file can then be installed by other members using fastboot or TWRP.
Once you're done, you can simply use TWRP to reinstall or restore your previous ROM configuration.

MotoJunkie01 said:
Here is an easier method -- install the stock boot image on your device using either fastboot or TWRP. Then, in TWRP, install this boot image patch script -- https://drive.google.com/file/d/1oLrNL3OYhwlCCLOtLdQEQM4tGsIucsPQ/view?usp=drivesdk
It will unpack, patch, repack and flash the modified boot image back to your boot partition, disabling dm-verity. Then use TWRP to make a backup of your /boot partition. Using a file manager, rename the backup from boot.emmc.win to boot.img and you're done. You'll then have a no-verity kernel in boot.img format. The file can then be installed by other members using fastboot or TWRP.
Once you're done, you can simply use TWRP to reinstall or restore your previous ROM configuration.
Click to expand...
Click to collapse
It doesn't works, also using zip on LOS/Stock it doesn't boot

Fersho said:
It doesn't works, also using zip on LOS/Stock it doesn't boot
Click to expand...
Click to collapse
I will patch a boot image to disabled dm-verity for the Moto E5. I'll post soon as I get some free time.

MotoJunkie01 said:
I will patch a boot image to disabled dm-verity for the Moto E5. I'll post soon as I get some free time.
Click to expand...
Click to collapse
Thanks, but finally I removed encryption, but men, it was very hard for me and it took me like 3 or 4 hours, but well the procedure is a llitle bit confusing, and I couldn't create a boot.img just ported the ones already shared for Play/Plus and seemed to work "fine", If I got some time I would make another tutorial but I guess that it will be long

Here is a no-verity kernel for the xt1944-2 Moto E5
From Build No. OPP27.91-25
https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view?usp=drivesdk
In case anybody needs it.

MotoJunkie01 said:
Here is a no-verity kernel for the xt1944-2 Moto E5
From Build No. OPP27.91-25
https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view?usp=drivesdk
In case anybody needs it.
Click to expand...
Click to collapse
Thank You, Do you believe that I don't have XT1944-2 I have XT1944-4 I notice that when I've seen something in settings, then It's only flash the kernel and that's all?

Fersho said:
Thank You, Do you believe that I don't have XT1944-2 I have XT1944-4 I notice that when I've seen something in settings, then It's only flash the kernel and that's all?
Click to expand...
Click to collapse
I'll do a no-verity for xt1944-1 also. In fact, I'll try and cover all variants for which I have firmware access. You can try to boot the kernel for xt1944-2 prior to flashing it, by using:
fastboot boot no-verity_xt1944-2.boot.img
If it boots, you should be safe in flashing it to your /boot partition. In any event, I'll post some no-verity kernels for the Moto E5 variants.

so if i have the xt1944-3 can I use this tutorial? and what twrp recovery should I use..? or should i just wait

SeerePetrova said:
so if i have the xt1944-3 can I use this tutorial? and what twrp recovery should I use..? or should i just wait
Click to expand...
Click to collapse
Well I've only tested on XT1944-2/4 you should try by your own risk, then for TWRP use the one that is made for Moto E5 Play, then boot into TWRP using fastboot boot "twrp-james.img" don't try to install because it wont work

Any plans to get the remaining hardware working? I tried flashing factory Vendor image from the XT1921-1 retail firmware for the hell of it to see if that might change anything with the camera and flash, but it didn't. LOS logs a crash.
01-04 06:43:08.824 F/libc (622): CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found
01-04 06:43:08.825 F/libc (622): Fatal signal 6 (SIGABRT), code -6 in tid 622 (motorola.hardwa), pid 622 (motorola.hardwa)
01-04 06:43:09.162 F/DEBUG (712): pid: 622, tid: 622, name: motorola.hardwa >>> /vendor/bin/hw/[email protected] <<<
01-04 06:43:09.162 F/DEBUG (712): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-04 06:43:09.180 F/DEBUG (712): Abort message: 'CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found'
Click to expand...
Click to collapse
I might not have been looking in the right place but the imgtuner file name in /vendor/lib/hw is: [email protected]
If I had any idea how to fix this I would try.

weakNPCdotCom said:
Any plans to get the remaining hardware working? I tried flashing factory Vendor image from the XT1921-1 retail firmware for the hell of it to see if that might change anything with the camera and flash, but it didn't. LOS logs a crash.
I might not have been looking in the right place but the imgtuner file name in /vendor/lib/hw is: [email protected]
If I had any idea how to fix this I would try.
Click to expand...
Click to collapse
I was hoping the camera commits had been added to the GitHub repositories by now, but they have not as of this date. A manual fix can likely be accomplished by replacing the camlibs in the Lineage build with the camlibs from the stock build. Unfortunately, due to my work schedule, I don't get a lot of spare time for development, but if anybody wants to try, simply copying/replacing the camlibs from stock to Lineage should fix the camera.

MotoJunkie01 said:
I was hoping the camera commits had been added to the GitHub repositories by now, but they have not as of this date. A manual fix can likely be accomplished by replacing the camlibs in the Lineage build with the camlibs from the stock build. Unfortunately, due to my work schedule, I don't get a lot of spare time for development, but if anybody wants to try, simply copying/replacing the camlibs from stock to Lineage should fix the camera.
Click to expand...
Click to collapse
Im new to the android rom/firmware file structure. just want to make sure I understand. are you referring to the .so camera libraries in vendor/lib? or do you mean the actual /core/java/android/hardware framework files in the source?

Res Remix system-180818-arm-aonly-gapps.img
camera works good... flash too
apparently i still have force encrypt though and the phone can definitely get laggy

tbirdguy said:
Res Remix system-180818-arm-aonly-gapps.img
camera works good... flash too
apparently i still have force encrypt though and the phone can definitely get laggy
Click to expand...
Click to collapse
That's right, camera and flashlight are working on RR OS GSI Official, but that lag is horrible, well it's only while scrolling and system ui, but the rest of the apps are working fine, to disable encryption you must flash no verity kernel that it's attached on previous commentaries and also to edit fstab.qcom then you'll skip encryption, but it doesn't affect on performance because even you skipped encryption the device still laggy, also on Pie is the same, but some extra bugs like graphic glitches, anyway I couldn't find a way to fix that lag, even using apps like L Speed

Fersho said:
That's right, camera and flashlight are working on RR OS GSI Official, but that lag is horrible, well it's only while scrolling and system ui, but the rest of the apps are working fine, to disable encryption you must flash no verity kernel that it's attached on previous commentaries and also to edit fstab.qcom then you'll skip encryption, but it doesn't affect on performance because even you skipped encryption the device still laggy, also on Pie is the same, but some extra bugs like graphic glitches
Click to expand...
Click to collapse
Just FYI the no verity kernel results in a bootloop on the TMO XT1921-3

T-Virus - Infect your Nokia 8 with Project Treble (2019-07-02)

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research about modifying your android system before flashing this!
* YOU are choosing to make these modifications, and if you point the finger at
* me for messing up your device, I will laugh at you. Hard. A lot.
*/
(if you expected the Resident Evil references to stop, you just got gnomed)
What is this?
T-Virus (for treble-virus) is a tool that takes a stock Nokia 8 firmware and "infects" it with various parts from the Nokia 8 Sirocco firmware, generating a firmware bundle that is compilant with Project Treble and that can be flashed to a Nokia 8 using NOST.
Firmware Sources
The base of T-Virus is the stock Nokia 8 firmware image (5150 / April Security patch at the time of writing). When being run, the build script takes those files and replaces the partition table with the one from Nokia 8 Sirocco. This required for creating a vendor partition that the stock Nokia 8 does not have. The vendor image is taken from the Sirocco firmware as well. During the build, the vendor image is mounted as rw, and various files are copied over from the stock Nokia 8 system image, or get patched to properly support the minor hardware differences between the two phones. Those actions are defined through very basic scripts inside of the vendor folder in the repository.
The boot image is a modified version of my umbrella kernel, which has support for early mounting vendor. It also includes a TWRP build with full support for Project Treble.
SELinux Hell
Because Android does some very weird stuff with SELinux contexts, you cannot launch a service file when it has an unknown context. We have to fix that by force-setting the SELinux context manually, but due to how SELinux works, this is only possible on a Linux system without SELinux. This means, that you cannot build this on a distribution with SELinux (Fedora in my case). I fixed the problem by building the images in a Ubuntu VM.
How to build?
First you have to download the latest firmware image from https://tmsp.io/fs/xda/nb1/firmware, and the exdupe tool from https://www.quicklz.com/exdupe
Extract the firmware into a folder and then clone the repository, like this:
Code:
$ mkdir firmware
$ ./exdupe -R ~/Downloads/NB1-5150-0-00WW-B03.qlz firmware/
$ git clone https://github.com/resident-nokia/t-virus
$ cd t-virus
The build script has two options you have to set: a version and the path to the extracted firmware. This means you have to run it like this:
Code:
$ ./build.sh --version v0.1 --firmware ../firmware
Leave it running and when it asks you, enter your sudo password. This is required to mount the Android ext4 partitions and edit the files that are only accessable by the (Android) root user, and retain their permissions.
When the script has finished the flashable firmware image will be inside of the out folder. You can optionally package this as a .qlz file again using exdupe.
What works?
It boots
Data decryption in recovery
Flashing GSIs / OpenGApps in recovery
WiFi
Mobile Data
Bluetooth
Sound
Vibration
Calling
Hardware buttons
Fingerprint
Camera
GPS
NFC
SDCard
Multi SIM
4k Video
What doesn't work, or isn't tested
Haptic feedback for Hardware buttons
Bluetooth headphones don't get registered properly
Nokia OZO audio support is missing
Fingerprint sensor is reported as being on the back of the phone
There might be issues with USB transfer under Windows
VoLTE (untested)
How to install?
WARNING: This might not be useable as a daily driver. Continue only if you are able to troubleshoot things if neccessary (bootloops, bricking the phone, causing the alarm app to declare nuclear war)
You can download the latest release from the releases page on the repository. It is a .qlz firmware, so you will have to flash it through NOST. You will need a completely unlocked bootloader. When flashing, make sure to select the "Erase Userdata" option, not doing this will most certainly bootloop the phone.
After the installation completed, your phone will reboot into phh's AOSP GSI. If you want to use a different GSI (you most likely will), follow these steps:
Download your favorite GSI
Unpack every form of compression, so you end up with a .img file
Boot into recovery
Copy the .img to the internal storage of your phone, or to your SDCard
Select "Install" -> "Install .img", select the image file you copied and flash it to your system partition
Then install OpenGApps or any other modifications you like.
Wipe /data to allow the new system image to boot properly and then reboot
To update to a newer version without having to erase userdata, download the zipped vendor image from the release page, and flash the image inside in TWRP.
If you want to go back to stock, simply download the 5150-revert firmware and flash it with NOST, with the "Erase Userdata" option enabled. It will revert all changes T-Virus made to your phone. Firmwares from https://tmsp.io/fs/xda/nb1 will not work.
Links?
Repository: https://github.com/resident-nokia/t-virus
Download: https://github.com/resident-nokia/t-virus/releases
Reverting to stock: https://github.com/resident-nokia/t-virus/releases/tag/5150-revert
What if I have a bug?
Upload a proper bugreport. This means logcat and dmesg. If you don't know how to get them, google it. Also, describe the issue and provide steps to replicate it. Everything else will be ignored.
I don't daily drive this phone anymore. I am doing this just because it is an interesting technical challenge. I don't have as much motivation to fix bugs than someone who daily drives it.
I want to say thank you!
I usually don't do this, but since this involved a lot of work on my side, I would be grateful if you would want to say thank you by buying me a coffee (or two): https://paypal.me/thmsp

Ok. After the flashing we have a phone "infected" by the Project Treble. But what it gives to end-user? What is profit of this?

kosmatyj said:
Ok. After the flashing we have a phone "infected" by the Project Treble. But what it gives to end-user? What is profit of this?
Click to expand...
Click to collapse
The ability to install GSIs (Generic System Images). Basically everything from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development

Oh! Sounds pretty good! Thanks. Will think about it. Really expands posiibilities and needs to be tested.
---------- Post added at 10:54 ---------- Previous post was at 10:29 ----------
Q: Should Ihave an Android Pie be installed first or it can be flashed over ony ROM version (I currently have Nougat ROM installerd on my Nokia 8)?

kosmatyj said:
Q: Should Ihave an Android Pie be installed first or it can be flashed over ony ROM version (I currently have Nougat ROM installerd on my Nokia 8)?
Click to expand...
Click to collapse
It could work, since it is a modified firmware for reflashing, but just to be sure, update to Pie through OTA. That's what this has been tested with and you won't update your bootloader in the process which eliminates some possible incompatibilities.

What is password for t-virus-20190703.qlz? Should I flash the TV-20190703-vendor.zip before or t-virus-20190703.qlz is all I need?

kosmatyj said:
What is password for t-virus-20190703.qlz? Should I flash the TV-20190703-vendor.zip before or t-virus-20190703.qlz is all I need?
Click to expand...
Click to collapse
It's all in the instructions. There is no password on the qlz file. You can't extract it, you have to flash it using NOST. The zip is for updating from previous versions and not for the initial installation.

Oh, I understood. No need to unpack, just download and flash over NOST, right? Thanks ones more. It is new for me, that`s why I have so much questions.

kosmatyj said:
Oh, I understood. No need to unpack, just download and flash over NOST, right? Thanks ones more. It is new for me, that`s why I have so much questions.
Click to expand...
Click to collapse
Yes. Just follow the instructions in NOST and select the T-Virus .qlz when it asks you to. Also, make sure you select the "Erase Userdata" option in the drop down menu that appears after selecting the .qlz.

Thank you for this - hope you enjoy the couple of coffee's

Amazing work. Can the current Android Q GSI be used?

comatrices said:
Amazing work. Can the current Android Q GSI be used?
Click to expand...
Click to collapse
When I tried it it didn't boot. Your mileage may vary, but you probably have to wait until the source code for Q has been published and people can build real phh GSIs from it.

Hello! Author, don`t you planning to build the same but for Android 8.1? Your work is great anyway but would be just amazing to have an Oreo in this appearance. Thank you.

kosmatyj said:
Hello! Author, don`t you planning to build the same but for Android 8.1? Your work is great anyway but would be just amazing to have an Oreo in this appearance. Thank you.
Click to expand...
Click to collapse
Just flash an Oreo GSI? I know you can run Pie GSIs on Oreos vendor, so it should work fine the other way around.

Nah! Didn`t work. After "android" logo it drops into download mode. AOSP 32 (last version of A 8.1 GSI).

kosmatyj said:
Nah! Didn`t work. After "android" logo it drops into download mode. AOSP 32 (last version of A 8.1 GSI).
Click to expand...
Click to collapse
I am not exactly sure if I understand you correctly, but Nokia 8 is not an A-only device, it is an AB device. You need to flash the AB image of AOSP, not the A one.

Right, I did exactly like you said. system-arm64-ab-vanilla-nosu - image that I flashed couple minutes ago. Downloaded from here: https://github.com/phhusson/treble_experimentations/releases/tag/v32
I`m sorry about my English. I`m Russian.

kosmatyj said:
Right, I did exactly like you said. system-arm64-ab-vanilla-nosu - image that I flashed couple minutes ago. Downloaded from here: https://github.com/phhusson/treble_experimentations/releases/tag/v32
I`m sorry about my English. I`m Russian.
Click to expand...
Click to collapse
Ok, then it probably doesn't work the other way around (Oreo with Pie vendor). An Oreo-based T-Virus is unlikely to happen though, because Siroccos Oreo vendor has some problems (calls not going through properly), and I dont want to maintain two versions of it because, as said in the OP, I don't use my Nokia 8 anymore. It seems like Pie is all you can get with this for now, sorry.

Hi all. Just to make it clear. The procedure for the Nokia 8 is:
1. Unlock Bootloader
2. Do "critical unlock" (fastboot flashing unlock_critical)
3. Flash "t-virus-20190703.qlz" with NOST?
Did i miss something? Whats with Security Enabled Linux?

just4me12 said:
Hi all. Just to make it clear. The procedure for the Nokia 8 is:
1. Unlock Bootloader
2. Do "critical unlock" (fastboot flashing unlock_critical)
3. Flash "t-virus-20190703.qlz" with NOST?
Did i missed something? Whats with Security Enabled Linux?
Click to expand...
Click to collapse
That's right. Don't forget to add "erase data" option while flashing t virus with NOST otherwise you'll end up in a bootloop.

[GUIDE] LineageOS 17.1 ROM for Galaxy A50 Android 10 Q

The phone must be installed TWRP Recovery. Use at your own risk, I'm not responsible for bricking your device.
Installation Instructions:
1. Enter TWRP Recovery Mode: Turn power off; Press and hold Volume Up key + Power key, when samsung logo appears release power key only, keep pressing volume up until TWRP recovery appears
2. Select Wipe - Format Data - type "yes" and confirm
3. Copy GSI ROM to your phone
4. Install - Install Image - select lineage-17.1-20200413-UNOFFICIAL-treble_arm64_bvN.img - select System Image and Confirm to flash.
5. Select Reboot - System ( boot without magisk )
6. Setup the Phone
7. INSTALL GAPPS: Enter TWRP Recovery Mode
8. Copy GAPPS zip file from PC to Phone
9. Select Wipe - Advanced Wipe - select "System" - Repair or Change File System - Resize File System - Confirm to Resize.
10. Select Install - select open_gapps-arm64-10.0-nano-20200408.zip and Confirm Flash
11. Reboot - System
12. ROOTING: Enter TWRP Recovery Mode
13. Copy magisk manager apk from pc to phone
14. Reboot to Recovery ( boot with magisk )
15. Connect the phone to internet
16. Install magisk manager
Done!
Download:
LineageOS 17.1 ROM
Open Gapps
WATCH VIDEO HOW TO INSTALL IT: https://youtu.be/u9gDx6VEORo

Thanks. So this is GSI? Bugs?

Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN

Hello everyone
iam in the Process of considering to put LOS on my device.
But the i saw the remarks from InFam0us-1985
Is it therefor not adviceable to use this on a Samsung Galaxy A505FN because this is exactly what i have
Saludos from Spain

DId i Brick my Samsung Galaxy A505FN?
Hello one Question:
"did i Brick my device if for some reason after Trying to flash TWRP it fell back in to OEM-locked and i’ am now in a Boot Loop, ore is the any Hope?
I used Heimdal and at first it did the Job but then it would not start again as expected.
After some attempts to flash it Properly it suddenly fell back in to OEM-Locked!
Pleas if you now some advice it be greatly aprichiatet
My device is a Samsung Galaxy A505FN (Spain)

I found a way to Unbrick my device
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans

hans2020 said:
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
Click to expand...
Click to collapse
AFAIA, OEM locked you can always flash stock?

I’ am not sure if thats True
InFam0us-1985 said:
AFAIA, OEM locked you can always flash stock?
Click to expand...
Click to collapse
All i know in case of my Samsung Galaxy A50 it is Possible!
To lift the OEM-Lock mode again.
i do not know if that is true for every Device.
Ultimately i was successful to install full Root-access!
I had great difficulty tho to use Heimdall ore any tool on Linux so i ended up using Odin in a VirtuelBox with WinXPpro
but do to no support of Long file names i had to trick there, to to make it work.
I just shorten the Names of every .tar to the first 2 letters.
I was able to successfully flash TWRP with Heimdall but not the Android ROM for my Phone.
I still wonder how to make it work!
There was one Thing i Noticed when Using Odin it seams in the Process he flashes vbmeta.img twice.
That impossible with Heimdall it creates a error message.
Well if anyone - that passes here - knows how to flash a Android 10 ROM of a Samsung Galaxy A50 using Heimdall let me know i tried very very hard to no avail.
I was surprised to learn there is no Good Tool for Linux-user doing this Task.
i only found Old Tutorials!
Is it truly possible that Heimdall dose not support modern Phone-flashing anymore properly?
As of now if a Linux-user ask me about Rooting i would advice him/her to do it in a VritualBox with windows installed.
If you have a License of a Windows Version Higher then XP good otherwise you have to Shorten File names if the very long to make it work.
I scarcely use windows anymore that why i only have a old WinXPpro legally in my Possession.
Unbelievable that the Linux-Community should not have a modern Flash Tool!???
Saludos
Hans
---------- Post added at 12:38 PM ---------- Previous post was at 12:18 PM ----------
Hello to @everyone
I had great difficulty to do this as a Linux User using Heimdall and eventually had to give up (after trying for 3 full days)!
I ended up doing it using Windows out of a VirtualBox!
It was Possible tho to successfully flash TWRP using Heimdall!
It also showed Success when Flashing Android 10 Version for my Phone but would not work.
Using the same Firmware with Odin it worked just fine.
When i compared the Flash-Protocol of Odin with what i did i only Noticed that Odin would flash vbmeta.img twice in the Process something that cant be done with Heimdall as it produces the duplicate error.
I wonder if this is the Reason it would not work.
I was also surprised to Learn, that there is virtual now Tutorial out there using Heimdall on a Modern Phone (last 12 Month ore less).
Is it truly Possible that There is now good solution for Linux Users?
I also Looked in to Fastboot and ADB and other Tools for Linux Platform and they all seam to be outdated!
Also all this Tools could not accomplish the task at hand.
Now if its me and anyone knows how to make it Work on Heimdall let me know as it is a Pretty good tool after all and by now i know it well. I would gladly start to make a tutorial and provide it here for free if i know how to make it work.
I have a txt file where i made a complete Protocol of all i tried if someone is curious ill send it to you.
Saludos Hans
##################################################################
I send some more Details of my Challenge in hope someone my know what it is i have to change!
My Device:
Samsung Galaxy A505FN
I created a .txt file protocol of all i did, i gladly provide it if someone ants to see it.
I analyzed the Whole Firmware-archive and the Pit file of my Phone to eventually find the Problem.
Note:
The Firmware was the correct one as it worked just fine using Odin!!
Analyzing all this, i only noticed two things:
First:
There are 3 seemingly identical files in the Archive and two so called
fota.zip files witch are not Identical
(one in the AP-Packet and one in the CSC-Packet)
Those where:
– cache.img one in the AP-Packet and one in the BL-Packet
– vbmeta.img one in the AP-Packet and one in the BL-Packet
– product.img one in the AP-Packet and one in the BL-Packet
Second:
Once i used Odin to finally flash successfully i noticed that in the Flash-protocol of Odin it seams Odin flashes the vbmeta.img twice in the process!?
Heimdall would not allow me to do so giving me the “Duplicate Error message”
Furthermore i tried one more thing in my desperation to make it work:
i thort: “maybe the order in wish the files a flashed chronologically matters”
So i did exactly that, trying to flash in the same chronological sequence as Odin did.
Note:
Every time i flashed, Heimdall would successfully finish the process but the Phone would not start with android
no matter what i tried.
ALSO i did successfully flash TWRP to my Phone using Heimdall
SO Heimdall works just fine on my system!
I spend a Long Time searching the Internet for a workable Tutorial or glue’s as to what is missing and how i could make it work.
I really want to succeed doing this, as i want to provide my folks offer her in Germany and also English and Spanish speaking Linux-Community with a Tutorial to do this!
I did also drop this Question and Challenge i face in some other Forums no useful answer returned so far
The latest Governmental Abuses and infringement on Peoples Privacy using Corona as excuse, makes it abundantly clear how important this kind a work is!
As for now i think, the only true option for a Linux-User is to run Odin from a Virtual-Box Windows installation, given
you have a legal copy in you're possession and have higher then Windows XP
(else you must change the Filenames of the .tar archives as WIndows XP and lower did not support excessively long filenames.)
Also you have to Install you're Phone USB drivers and have them up and running properly!
Internet access to you're VB makes it all more comfortable, but you can also use Shared folders with the Host-System to do the job.
Note:
I did indeed tried the "WINE-plugin-environment" (Windows 10) under Linux. i could not get it to work.
It was to much messing around make it recognize the USB-connection to the Phone!
I could not get it to work, I don't know if you can?
I guess that would be a nice way for Linux-users if it could be made to work!
What do you guys think, can this be solved?
Pleas let me know if you know the answer to my Challenge!
You're help is not only needed but would be greatly appreciated
Sincerely yours
Hans from Germany

well I Found this from 2017;
Yes you can do fastboot and adb cmd in Linux but you have to install adb and fastboot drivers to Linux by using
1) sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
2) sudo apt-get install android-tools-adb android-tools-fastboot
That's it you get your fastboot and adb cmd’s all the cmds are same just as windows just you need to add sudo in front if not in root
Click to expand...
Click to collapse
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/

Well i do know
Of course i know how to Install a Software on Linux and i did indeed installed those Two
But both of them would not even Detect my device jet Heimdall and Odin had no problem doing that.
Anyhow i might go about and try those Two harder.
And no Iam not confused
thank you anyway
Saludos Hans
InFam0us-1985 said:
well I Found this from 2017;
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Click to expand...
Click to collapse

I cant call or receive call and send and receive messages via sim
Please help
I cannot call and receive calls
Cannot send and receive messages ,one time passwords, through message
Cannot login through whatssapp .
volte is not enabled
And no option for it to enable
I am from India using jio sim card .
Please help.
If any custom rom is used in my SM-A505F i cant do calls or receive calls nor send or receive messages.
country id : INS
Original firmware of A50 : Atb6

Will this image work with the SM-A505G version?

USB File Transfer Does Not Work
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?

OmariCelestine said:
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
Click to expand...
Click to collapse
This is what you get with a GSI, finger print wont work either.

InFam0us-1985 said:
This is what you get with a GSI, finger print wont work either.
Click to expand...
Click to collapse
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.

OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
Try with a custom kernel

the project is down? Because I love LineageOs, but the A50 is abandoned :/
---------- Post added at 06:06 AM ---------- Previous post was at 05:57 AM ----------
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
you need to run into Twrp and it work. But only in TWRP

hey man, the project is being upgraded? Tanks for your time

InFam0us-1985 said:
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Click to expand...
Click to collapse
Got the same problem here. i guess i'm staying on the stock firmware

I have installed lineage-17.1-20210212-UNOFFICIAL-treble_arm64_bvS.
Fingerprint and MTP working.

How to install Gsi on S20 fe 5G (HavocOS,PixelExperience+,Aosp,Lineage and more!!!)

First You Need an unlocked bootloader there are many guides to unlock the bootloader on Samsung devices I recommend this one Unlock Guide
Once you have an unlocked bootloader we can proceed
1: Flash Twrp if you don't have it already: Snapdragon Twrp Or Exynos Twrp Download The Twrp For your device Model And Also Download Vbmeta Disabled, Reboot Into Download Mode By Pressing Volume Up And Volume Down When Booting The device
Download Odin and Samsung Drivers On your Computer Odin And Samsung Drivers
After You have Odin And Samsung Drivers, Open Odin and On the AP Section Select The Twrp You downloaded And On the Userdata Section Select The Vbmeta Disabled You Downloaded , GO TO OPTIONS AND DISABLE AUTO REBOOT!!!, Press The Start Button and once it Finishes, You Should Press The Power Button And Volume Down And When It Starts To Reboot Press The Volume UP And Power Button If you Did it right you Should Boot Into Twrp
2:
On Twrp Go to Wipe > Format Data > Type Yes (This will WIPE ALL DATA ON THE DEVICE!!!)
Then Go to Reboot > Recovery
After It reboots Go to Reboot > Fastboot
Download Adb On your Computer Adb Download And extract it into a folder, Then Press Shift On your Keyboard And Right Click At the same time Select The "Open Command Prompt Here" Option, You should see A command Prompt
Now You need To Download The Gsi You want to flash, (You can Find Many Gsi In the s20 fe Gsi's Group Here) Or you can Also Check Treble Gsi's Group
(Roms Based on Older PHH Patches than v303 Will not work)
Once You have the Gsi you want to flash Copy it into the adb folder And Also RENAME THE FILE to sys.img
Now On the Command Prompt You can Run > fastboot flash system sys.img
(If You Cant Get Your Drivers Working i recommend Trying ubuntu Because it has Drivers Pre Installed)
If you Dont get any errors then you are Good Reboot your device and you should see the gsi is installed
Fixing Rounded Corners:
Reboot Into Twrp And Open Adb On your computer
Download The Overlay and place it in the adb folder
Run ( adb shell mount /dev/block/dm-1 /vendor )
Then Run ( adb shell rm /vendor/overlay/framework-res__auto_generated_rro_vendor.apk )
Then ( adb push treble-overlay-samsung-rq8.apk /vendor/overlay )
Bootloop Problems:
You may have a bootloop If you are using A newer Vendor
This Was Tested On the one Ui 3.0 Vendor I Recommend Downgrading to 3.0 Vendor If you can
!!! I am not sure if its working on one UI 3.1 Vendor !!!
(Vendor is the one UI version you have)
Magisk:
To flash magisk you need some special Instructions, !!!Without them flashing magisk will result in a bootloop!!!
They are a bit complicated and you can find them Here (I don't recommend Using Magisk With Gsi's)
Issues?
Current issues are: 60fps Video Recording, Fingerprint Sensor And MTP
Fingerprint Might be fixed On android 12!!!
IF YOU ENCOUNTER PROBLEMS JOIN THE S20 FE HELP GROUP Here
(THIS WAS ALL TESTED ON SNAPDRAGON I AM NOT SURE IF IT WORKS ON EXYNOS)

I haven't clicked to look but is the magisk for GSIs that thing where you have to reboot from recovery to activate root ?
I suppose if it is the phone still wouldn't pass SafetyNet would it ?

3mel said:
I haven't clicked to look but is the magisk for GSIs that thing where you have to reboot from recovery to activate root ?
I suppose if it is the phone still wouldn't pass SafetyNet would it ?
Click to expand...
Click to collapse
no, you can fix magisk but its a bit hard, And yes you can pass safetynet with magisk, Some roms like pe+ Can pass safetynet without it tho

If only the fingerprint sensor worked on GSI ROMS. I would have definitely went for it.
S20 FE 5G rooted on android 11 (one ui 3.0)

Kolyei said:
If only the fingerprint sensor worked on GSI ROMS. I would have definitely went for it.
S20 FE 5G rooted on android 11 (one ui 3.0)
Click to expand...
Click to collapse
that's down to Samsung doing the bare minimum to qualify for treble compatibility, same as the vendor layers of most OEMs. only Sony went the extra mile to actually make sure their hardware would work apparently.

3mel said:
that's down to Samsung doing the bare minimum to qualify for treble compatibility, same as the vendor layers of most OEMs. only Sony went the extra mile to actually make sure their hardware would work apparently.
Click to expand...
Click to collapse
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.

Doomer231 said:
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Click to expand...
Click to collapse
any hardware OEMs add has supposed to have been functional for the last 3 years. they control their vendor layers which should work seamlessly with the OS layer. I'm paraphrasing the xda page that introduces treble and Phhuson.
OEMs have little interest in making treble work as it does nothing for them (they think). if google support was the reason 60fps would work for video recording but it doesn't.

Doomer231 said:
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Click to expand...
Click to collapse
it was android 11 that broke it lol, on a10 it was fine

QUESTION for the GSI users out there...
do you have any of the screen juddering while trying to scroll or touch screen dead spots that occasionally happen ? any ghost touch issues, I suppose with the caveat of if you had them before ?

3mel said:
QUESTION for the GSI users out there...
do you have any of the screen juddering while trying to scroll or touch screen dead spots that occasionally happen ? any ghost touch issues, I suppose with the caveat of if you had them before ?
Click to expand...
Click to collapse
i never had any issues in one ui and i also dont on gsi

Does doing this guide trip Knox on the phone?

pOLLYpOCKET said:
Does doing this guide trip Knox on the phone?
Click to expand...
Click to collapse
yes, if you unlock your bootloader it trips knox

how can i found vbmate file for fold 2 ?

rowihel2012 said:
how can i found vbmate file for fold 2 ?
Click to expand...
Click to collapse
Do not install a gsi on the fold, it will be horrible as stock android has bad support for folding devices

overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)

luisf0202 said:
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
Click to expand...
Click to collapse
sounds like a question for the mighty phhuson and friends

luisf0202 said:
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
Click to expand...
Click to collapse
try this instead adb shell rm /vendor/overlay/framework-res__auto_generated_rro_vendor.apk

For me fixing round corners disabled nav buttons and when choosing gestures as nav keys only swipe up for home gesture works back button is broken

are you using a 3rd party launcher ? navigation gestures are or were supposedly broken on 3rd party launchers regardless of which rom you're running.

no, im using quick step. But even with gestures disabled i dont have any buttons

Teclast M40 Pro Discoveries

Teclast M40 Pro Discoveries​Various helpful points of knowledge to unlock your bootloader, to root, and use your tablet.
Problem: Where can I obtain the official firmware?
Solution: Teclast Website
Usage: type M1A3 in search
Problem How can I unpack "pac" files?
Solution: Build C utility divinebird / pacextractor
Solution: Download pre built Linux executable pacextractor.zip
Usage: >./pacextractor Firmware.pac
Bash:
git clone https://github.com/divinebird/pacextractor
cd pacextractor
make
Problem: I need tools to flash my device
Solution: Download the latest SPD Upgrade Flash Tool SPD_Upgrade_Tool
Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools
Solution: Download and install 2010 Visual C++ Distribution
Problem: I want to unlock my bootloader. (Window and Linux kit)
Solution: Download TeclastM40Pro_Unisoc_UnlockTools.zip
Usage: Read readme file.
Problem: How can I remove the dm_verify warning on boot up after unlocking the bootloader?
Untested Solution: digitally sign the vbmeta partition and write it back. See [Tutorial] How to create a custom signed vbmeta.img
Problem: I want to root my device.
Solution: Modify boot.img with Magisk, then sign.
Usage: Upload to your device's download directory, the current boot.img read from your device, or from the same version firmware. Then install Magisk app from here. Use Magisk to patch the boot.img. Sign the partition. Then flash back the signed magisk version of boot.img to "boot_a" partition. Guide to flashing single partition at Hovatek Website
Problem: I need to emergency flash my device?
Solution: Currently only from Windows, use SPD Upgrade Tools to reflash firmware.
Usage: From the tablet powered off, or if boot looping. Hold down the power-button and volume-down for five seconds, release the power-button, and keep the volume-down button still held for another five seconds, then release or release if the detected earlier. Windows and SPD tools should then detect your device to flash.
Problem: I want to improve my Telcast M40 Pro
Solution: List of suggested apps below;
FDroid App Store F-Droid Website
Aurora > via FDroid. App store allowing the direct download from Google Playstore, without your own account.
Lawnchair > via FDroid. Fast open source sophisticated launcher.
AdAway > via FDroid. Removes adverts whilst using apps.
TrackerControl > via FDroid. Manages apps access to internet, and blocks spyware and trackers.
.

Problem: I want root mode without the effort of hacking a rom partition.
Solution: For those with World version Teclast M40 Pro device, here is a signed rooted boot partition I created. Read the readme file inside the zip. You will require an unlocked device, windows setup with USB drivers for Teclast, the complete firmware from Teclast website, and SPD Update Tools installed. If you're successful, then on rooting you will need to install Magisk app to get root active. Magisk will reboot once to finalise.
Download : TeclastM40Pro_ROW__v1p0_signedboot_magiskrooted.zip
Download : TeclastM40Pro_ROW__v1p2_signedboot_magiskrooted.zip

SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?

laurorual said:
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
Click to expand...
Click to collapse
Sorry for replying late. I got no indication of the response. To the problem, I can only suggest getting a different version of SPD or m aking sure your computer system is properly updated. I hope you've already solved the issue!
Maybe you're experiencing, "Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools" See above for solution.

I've noticed a new ROM for world edition, "M40 Pro(M1A3)_Android 11.0_ROW V1.02_20220525", but not getting any system update options for OTA. People flashing their systems may want the latest firmware!

Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Is there any way to install Magisk modules?
Thanks for your post, it helped me a lot to unlock my tablet.
Edit: My version is the M1A1 firmware V1.03_20210804
Edit 2: Finally, when updating my tablet with the root file that is in the post, it did not allow me to install any Magisk module, the solution is to download version 24.3, and update automatically, without changing to a higher version of Magisk

Glad you worked it out Miny !!! Sorry the warning emails for new posts have been going to a gmail account I no longer use.
Also your hardware maybe different and require it's own unique firmware and boot images. It seems the cracking in similar though.

Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?

Hi there.
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked?
Thanks in advance

rubsbcn said:
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked? Thanks in advance
Click to expand...
Click to collapse
To tell you the truth, not sure. Most SoC are impossible or near impossible to brick. They usually allow for an injection or have a read only boot section. Other words you could test. Also research difference in hardware between models, and that may indlicate if something may not work. The kernel/drivers are the improtant aspect.

jorkusjorkus said:
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Click to expand...
Click to collapse
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical

minyfriki said:
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Click to expand...
Click to collapse
What I found works, is when using SPD Research Tool, load up the firmware.pac and then go into settings and click "Select All Files" and again to unselect, which leaves the default required items.
Then manually change BOOT to the Magisk img. Then click on all VBMETA types, and UBOOT_LOADER (may not be required though). Then flash.
You should get bootable tablet (no looping). Warning: UserData partition is written over.
I'll share my Magisk image for v1.2

e8hffff said:
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I'm using the same version as you on the same OS. After some research it seems like unlock_bootloader was removed in this commit from 2018. From what I can tell, unlock_critical does something else (unlock_bootloader runs
Code:
fb_queue_download("unlock_message", data, sz); fb_queue_command("flashing unlock_bootloader", "unlocking bootloader");
while unlock_critical runs
Code:
do_oem_command("flashing", "unlock_critical" and doesn't take the signature argument);
)
I'll see if I can compile the older version with the needed command.
What about my other questions?

Issue: Android not starting. I had the infinite restart when plugged in the usb. I tried to reload the installation package (succeeded), but didn't fixed the issue. Battery was not charging yet. When I started the Teclast M40 pro, the logo showed up, but the tablet turned off again.
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.

dougcwb said:
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
Click to expand...
Click to collapse
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!

e8hffff said:
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
Click to expand...
Click to collapse
I did the installation package process that the Teclast sent me. The last thing they told me to do was keep trying to install the package (wft?). Well, I just open the tablet, unplugged the battery for a while and after that it worked.
Maybe this resolved 2 things:
1-the battery was not properly connected in the first place, so when I plugged the 5 pin to the board it connected as it should.
2- Maybe there is a "memory" in the board attached to the battery that was bricked (or something like that) when I pulled off the plug, this memory was reseted.
BTW, when the tablet came to life again, the battery was at 87%.