Develop Bugs

ARM64 UEFI From RX130

This is a low-level backup comes from an ARM64 test machine made by Microsoft, codenamed Hapanero.
For the Lumia 950XL, since it also uses the Qualcomm Snapdragon MSM8994 SoC, the bottom layer can still operate but the display driver are not the same. Running on the Luumia950XL will damage the Amoled driver IC.
For the RX-130, please check the HW Build number of the model, the sticker is on the back of your device. Only EB2.X can be use this file, EB1.0 can't flash those file for the moment, and will causes an infinite boot loop. Before flashing, be sure to back up the original low-level 0-3 partition (DPP, MODEM_FSG, MODEM_FS1, MODEM_FS2) with Winhex. You need to restore the baseband after flash back to the ARM32.
After the flashing is completed, please restart your device. Please notice that the bottom layer does not have start-up vibration.
If you need to enter the Mass Storage mode, download the provided file into the SD card and extract the files in it to the root directory of the SD card. After the SD card is inserted into the device and the device is started, the system will automatically enter the menu.
After testing, due to the particularity of RX-130, it has no bricks at all, expect flash the android bootloader (how to unbrick the device in 9008 mode will public later).
Download link: (with Windows10 Mobile with build 14822 in ARM64)
HTML:
Bootloader backup image: https://pan.baidu.com/s/1d6UktLuIYuPk2qeq2eL3QA
PASSWORD: ylcg
Full system backup image(with certificate provided by imbushuo): https://pan.baidu.com/s/1EQ7OC9h3xSvVT8WzvUzdyA
PASSWORD: 96gk
SD card boot file(ARM64): https://pan.baidu.com/s/17DqccVMqJmLgAtMnlcXjrw
PASSWORD：kgo8
Thanks to imbushuo, JerryYin and other people make contribute to this project.
The ARM64 UEFI was originally uploaded by windowsbuildcollect.
备份最初由百度windowsbuildcollect吧发布

RX-130 Product Code: 059W1B4 , 059W1B6

Baidu
Very Nice :good:
But cannot use Baidu, please upload files on English site, Mega ect.

jbdxbl said:
(how to unbrick the device in 9008 mode will public later).
Click to expand...
Click to collapse
I.m waiting patiently, to see if i can unbrick lumia640 xl DS.

MazeAlpha6gb said:
Very Nice :good:
But cannot use Baidu, please upload files on English site, Mega ect.
Click to expand...
Click to collapse
https://drive.google.com/drive/folders/1bMG3d5mdfa_kLCT5KTbr5YxLmrxvEkKB

10+ eXYNOS BOOTLOADER REMOVED

First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing

link is restricted

Bro. Share file pls on your googledrive. We cantdownload it

Flar4eg said:
Bro. Share file pls on your googledrive. We cantdownload it
Click to expand...
Click to collapse
Excuse me, is that I uploaded the files to my google drive cloud and I detect a dll, or part of the flashtool as a virus, now I upload it again and put the link

https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI

multiuploader error: WinDNWApi.dll file could not be found.

Skyfall191299 said:
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Click to expand...
Click to collapse
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing

Skyfall191299 said:
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
Click to expand...
Click to collapse
getting error that el3mon_dram not found. can you help me?

Hello someone has the files ? The download link is inactive

The download link is inactive, please active or reupload please.

Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
good jod
im follwed to this instruction but all links not woriking
pla give me ur telegram or whtas app
and upload files to the new link plz

eldon301 said:
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Click to expand...
Click to collapse
how to create with hex bro ?

links not woriking

link isn't working please fix

akbarshoxdedamirzayev said:
how to create with hex bro ?
Click to expand...
Click to collapse
Find the exact firmware that’s currently in the device, extract sboot from the firmware. You need to find correct location of bl1 bl2 el3 and others, names correspond to which is cut. You need 5 files from sboot. Am stuck on the forth file failing and I still don’t understand how to find them. What I did was follow others with exactly the same problem to see and understand how they got there’s and then tried it on my sboot. I am failing on part4 don’t even know how to make a cfg but from what I understand e for exynos and the number after so mine is e7885. Still not sure like I said

http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip/file download link

Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
Can you check the addresses and lenghts of the partitions cut out of sboot?
I think you've made a mistake.
Can give me the precise partition details?
Are you 100% positive that this is valid at least for most devices of the same chipset?
I'd like to try to make an automated script or a tool of some sort.
Also when I was dividing my A515F U5 sboot I've spotted some long breaks in data which I assumed were empty blocks at the end of partitions.
What confused me about it is that I didn't find those where you said partitions are ending.
Can you demonstrate graphically your partitions in a linear projection?

It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares

eldon301 said:
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
Click to expand...
Click to collapse
I'd like to help

NonStickAtom785 said:
I'd like to help
Click to expand...
Click to collapse
Hello my friend I am try to get life back into a A750G, it’s completely hard bricked showing exynos usb in device manager. Can i direct message you or should I keep it in the forums. I was falling on part 4 off the files needed to create, I didn’t even know if my cfg file was correct but I tried my best at understanding the creation of the files. Plz help my brothers

HOWTO: Install developer image for 2019 shield tv pro !READ WARNING!

!!WARNING!!
1st
You cant boot the 2019 Pro with a magisk patched boot.img. If you try to run the install script with a patched image it will brick the device!!!
The script re-locks the bootloader so if you want to try using any modified .img files you need to flash them individually or modify the script.
2nd
After you unlock the BL AI upscaling is disabled. Even after the BL is re-locked. Flashing back to the normal firmware should fix this but I am not sure of that.
3rd
After flashing the "developer" firmware the fact is it is no different than the standard firmware right now.. If Nvidia provides a rooted image in the future plz pm me and I will update this post.. I am leaving this post up for anybody who like myself is looking for shield pro 2019 info and was wondering if it could be rooted taking steps similar to the 2017 here
So with that said..
I just switched from a firestick 4k as my streaming device of choice to a shield pro 2019. I tried the cheaper $160 version first but when I looked at the specs and tried to do anything to it the lack of usb ports and 8gb storage made upgrading to the $200 pro a no-brainer.
So far I have gotten a few nice tweaks installed and Ill go into that in another post.
Things you'll need
A windows or linux PC with adb-fastboot binaries SDK Platform Tools
A male to male usb cable (my laptop has a usb-c input but It wouldn't work to connect to the shield)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image HERE
SHIELD Family Windows USB Driver HERE
USB keyboard (or shield game controller possibly?)
First thing I did was enable USB debugging. Its the same process as other android devices. Device Preferences> About > then tap build info 10x. Then Device Preferences> Developer Options> enable usb debugging.
Now I made my own male to male usb cable by just splicing two old cables together matching the colors to each other. No special wiring is needed.
I used windows but it's easier to use linux if you can since windows required me installing a driver for fastboot to work.
To put the Shield into fastboot mode. Attach the usb cable to the usb port furthest from the hdmi port. And attach a usb keyboard to the usb next to the HDMI-out. Also keep the device connected to an HDMI display during the process. If you are using a pc that shares a screen with the shield tv then I suggest using chrome remote desktop to run the commands on the pc while the shield is using the display.
Windows 10: hold shift and right click in the platform tools folder
select open powershell here
type .\adb devices
type .\adb reboot bootloader
Linux you can just open a terminal and as long as adb is installed type adb devices then adb reboot bootloader
When it reboots there is an option to unlock the bootloader. You just select that and let it reboot again. You'll know it is unlocked because when it boots up with an unlocked bootloader a warning telling you the firmware cant be verified comes up for about 10 seconds.
To flash the firmware you need to get back into fastboot. Either go through the setup again quickly to enable usb debugging once more or there's another way to enter fastboot using a key combination (A+B on the shield controller, I don't know the combination on a keyboard).
Once its in fastboot again if you are using linux
unzip nv-recovery-image-shield-atv-2019-pro-8.2.0-dev_rooted.zip and cd into the directory containing the flash-all.sh script
and run it.
In windows 10 I needed to install the nvidia fastboot drivers before fastboot would detect it.
In device manager action> scan for hardware changes there should be a device with Fastboot in the name
You need to choose the option to update driver then select "have disk" and select the android_winusb.inf file and the device type should be Android Bootloader Interface.
Once fastboot drivers are installed open the file manager to the folder containing the flash-all.bat file, hold select and right click to open powershell in this location and type .\flash-all.bat
After the script runs the device will flash the dev firmware and lock the bootloader again.
I patched the boot.img with magisk but it wouldn't boot with it. I may try again tonight with different settings to get magisk to work.

EDIT: edited post to remove quote per op request lol. apparently after they posted the dev os firmware and i reported it to nvidia they never fixed it.. the dev os firmware on nvidia site for nstv pro 2019 model is exactly same as stock lolol
last i dled the dev os firmware it wasnt actually dev os firmware and was regular firmware.. once bl is relocked also u cant root it since it will no longer allow custom firmware..
this instruction us flawed to say the least

Thank you for start trying run magisk :good:
I didn't test patched boot-image, but when you can't boot, it maybe related to "vbmeta"
It seen nvidia don't like to provide root access to customers! because it remove vbmeta_skip.img from official 8.2.0-dev_rooted.zip package.
So may be you should try flash vbmeta_skip.img to achieve successful boot.
I attached vbmeta_skip.img from 8.1.0-dev_rooted.zip for you.
HTML:
fastboot flash vbmeta vbmeta_skip.img
I suggest keep testing on @Steel01 LOS releases. If we achieve an stable custom rom open-source, it's much much better than vendor release! I prefer freedom vs AI-Upscaling.
LOS releases: https://forum.xda-developers.com/showpost.php?p=83587703&postcount=458

mrhamed said:
Thank you for start trying run magisk :good:
I didn't test patched boot-image, but when you can't boot, it maybe related to "vbmeta"
It seen nvidia don't like to provide root access to customers! because it remove vbmeta_skip.img from official 8.2.0-dev_rooted.zip package.
So may be you should try flash vbmeta_skip.img to achieve successful boot.
I attached vbmeta_skip.img from 8.1.0-dev_rooted.zip for you.
fastboot flash vbmeta vbmeta_skip.img
I suggest keep testing on @Steel01 LOS releases. If we achieve an stable custom rom open-source, it's much much better than vendor release! I prefer freedom vs AI-Upscaling.
LOS releases: https://forum.xda-developers.com/showpost.php?p=83587703&postcount=458
Click to expand...
Click to collapse
yes, disabing vbmeta should be a given lol.. theres already root and steps have been discussed spread out in various threads already.. its just not a simple "flash this and youre rooted" so ppl keep asking about it lol

How To Guide How to root C21 with locked bootloader

GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
please note that I will make a proper procedure in this post shortly. but in the mean time, you WILL need linux to be able to root your phone, as windows process does not work.,
while using linux, need to change the commands to be python3 where it says python.
just abit snowed under at the moment, but will be done inthe next 48 hours

Hi, to complete what our friend previously said, we are at least three people to have used this tool and made it work. My phone REALME C21 is unlocked and rooted.
I used Windows, albeit it probably wasn't perfectly done.
The solution is to use the mtkclient tool produced on this github and follow each step of the guide on the github, under "Usage / Root the phone (tested with android 9-12)".
You must absolutely use the magisk App given on this github, the official one won't work, this is what prevented me previously to succeed. This magisk app has been patched for mediatek/realme phones.
Do not omit dumping steps, as it is your only way out if it doesn't work.
Also, for obscure reasons, I was unable to chain commands ; tool wouldn't work this way...
So each time I did and succeeded in doing one "mtk" command on the phone, I unplugged it, launched the next command, pushed vol up and vol down, and replugged it.
Maybe I missed something. (note that for the mtk tool to work, phone must be shutdown and then plugged the way I described or that it is described on the guide/tool itself)
Anyway, no guarantee for you here, but hey, it works .

Cherryblue said:
Hi, to complete what our friend previously said, we are at least three people to have used this tool and made it work. My phone REALME C21 is unlocked and rooted.
I used Windows, albeit it probably wasn't perfectly done.
The solution is to use the mtkclient tool produced on this github and follow each step of the guide on the github, under "Usage / Root the phone (tested with android 9-12)".
You must absolutely use the magisk App given on this github, the official one won't work, this is what prevented me previously to succeed. This magisk app has been patched for mediatek/realme phones.
Do not omit dumping steps, as it is your only way out if it doesn't work.
Also, for obscure reasons, I was unable to chain commands ; tool wouldn't work this way...
So each time I did and succeeded in doing one "mtk" command on the phone, I unplugged it, launched the next command, pushed vol up and vol down, and replugged it.
Maybe I missed something. (note that for the mtk tool to work, phone must be shutdown and then plugged the way I described or that it is described on the guide/tool itself)
Anyway, no guarantee for you here, but hey, it works .
Click to expand...
Click to collapse
Congrats
And i wanna point some thinks
Actually using windows for such job is a real pain, i used EndeavourOS.(Based on arch linux)
Magisk app actually not matter if you are on android 10, and actyally @smiley.raver used magisk app from original releases.
Therefore, i already asked differences here;
What is the benefit of pacthed magisk? · bkerler/mtkclient · Discussion #116
I used this tool today and my device was successfully rooted :-) However, I have a question in my mind; What is the differences of magisk app you provided and official magisk app? Why should we use...
github.com
I had not need to replug my phone for each command, but i dont exactly remember how i did, lol.

Does using this method it will erase data / formatting data?

Yes. At least, this is one of the steps in the github guide, and it probably would not work if you don't do it.

A12sma said:
Does using this method it will erase data / formatting data?
Click to expand...
Click to collapse
You should clear data, beacuse it bootloops without clearing data.
Before doing anything you can backup your files from recovery mode, adb can be run as root at recovery mode.

apokogies for not getting a more step by step guirde completed with a series of issues with my mental health..
Bootloader unlock can only be on Android 10 - as soon as you try upgrade to android 11 - fastboot stops working - . I have not yet found a work around for android 11 as of yet - but you can still use the mtkclient tool to flash files like you would fastboot.

do a full phone backup - with python mtk rl out or python mtk rf flash.bin - this will ensure that if you do something wrong, or wipe a partition or bootloop - you can always flash the out directory or the flash.bin file - I am using 2 at the moment - 1 as daily driver - the other i had to restore after screwing around with a few wrong files - but i keep the backup of python mtk r out - and have reflashed and bricked and reflashed it about 15 times in the last 24 hours trying to get fastboot to work with android 11

smiley.raver said:
do a full phone backup - with python mtk rl out or python mtk rf flash.bin - this will ensure that if you do something wrong, or wipe a partition or bootloop - you can always flash the out directory or the flash.bin file - I am using 2 at the moment - 1 as daily driver - the other i had to restore after screwing around with a few wrong files - but i keep the backup of python mtk r out - and have reflashed and bricked and reflashed it about 15 times in the last 24 hours trying to get fastboot to work with android 11
Click to expand...
Click to collapse
I am glad you finally become online after a long time
I have few think to say.

Trying to compile a twrp at same time.
Yeah it's been a rollercoaster of a ride the last few months. Had to put my dog down 2 days before Christmas. So this has been giving me a good distraction .
Found out a fair few things with this phone. Very weird and different to how it operates and upgrades/downgrades.
Been using a mix of sp flash tools, mtkclient and fastboot where applicable.
So what interedting things have happenef while I was away

smiley.raver said:
do a full phone backup - with python mtk rl out or python mtk rf flash.bin - this will ensure that if you do something wrong, or wipe a partition or bootloop - you can always flash the out directory or the flash.bin file - I am using 2 at the moment - 1 as daily driver - the other i had to restore after screwing around with a few wrong files - but i keep the backup of python mtk r out - and have reflashed and bricked and reflashed it about 15 times in the last 24 hours trying to get fastboot to work with android 11
Click to expand...
Click to collapse
Oh also if upgrading to android 11 make sure you have the correct firmware forthe correct region otherwise you get boot loop freezes and all sorts of wonderful $hit

Cherryblue said:
Yes. At least, this is one of the steps in the github guide, and it probably would not work if you don't do it.
Click to expand...
Click to collapse
As with any phone, unlocking bootloader erases all data. This is just android, you are always advised to backup all data prior to preform a bootloader unlock

Cherryblue said:
Hi, to complete what our friend previously said, we are at least three people to have used this tool and made it work. My phone REALME C21 is unlocked and rooted.
I used Windows, albeit it probably wasn't perfectly done.
The solution is to use the mtkclient tool produced on this github and follow each step of the guide on the github, under "Usage / Root the phone (tested with android 9-12)".
You must absolutely use the magisk App given on this github, the official one won't work, this is what prevented me previously to succeed. This magisk app has been patched for mediatek/realme phones.
Do not omit dumping steps, as it is your only way out if it doesn't work.
Also, for obscure reasons, I was unable to chain commands ; tool wouldn't work this way...
So each time I did and succeeded in doing one "mtk" command on the phone, I unplugged it, launched the next command, pushed vol up and vol down, and replugged it.
Maybe I missed something. (note that for the mtk tool to work, phone must be shutdown and then plugged the way I described or that it is described on the guide/tool itself)
Anyway, no guarantee for you here, but hey, it works .
Click to expand...
Click to collapse
Just to clarify, the magical app is not patched as such, it is an alpha branch, which encorporates extra coding/coding that is removed from the normal magisk, and. Can still be used on other phones as well, (it is hard to understand what most changes are as I can not read (assumption Chinese) that magisk alpha is mainly change logged as .
But yes that was one of the issues I faced being that didn't use the magisk alpha app originally.
Under Linux I didn't have to unplug each command. But under windows yes you need to run the command and then plug the phone in under Brom/download mode. You don't have to restart the phone after each command. Just need to unplug and run next command and then plug phone in

smiley.raver said:
Trying to compile a twrp at same time.
Yeah it's been a rollercoaster of a ride the last few months. Had to put my dog down 2 days before Christmas. So this has been giving me a good distraction .
Found out a fair few things with this phone. Very weird and different to how it operates and upgrades/downgrades.
Been using a mix of sp flash tools, mtkclient and fastboot where applicable.
So what interedting things have happenef while I was away
Click to expand...
Click to collapse
We have TWRP, please get in touch with me from telegram.
I had sent you my telegram profile link from privatebmessage

MrMiyamo said:
We have TWRP, please get in touch with me from telegram.
I had sent you my telegram profile link from privatebmessage
Click to expand...
Click to collapse
Ok. Is it working. Because the ones I found were t working and setup for different phone.
Will jump on telegram tonight. Just busy today

smiley.raver said:
Ok. Is it working. Because the ones I found were t working and setup for different phone.
Will jump on telegram tonight. Just busy today
Click to expand...
Click to collapse
We have working twrp for RUI1, but not fully tested.
Booting and decryption works though.
I didn't install the android 11 update on my phone in time,
And I can't find the RUI2 firmware anywhere right now.
(Sofware update center does not show RUI2 update anymore)
So if you have RUI2, we can build twrp for it.
I am looking forward for your message on telegram

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%.