Develop Bugs

Micromax a65 rooted!!

MICROMAX A65 ROOTED!!
[Sorry Guys!!!!]
As my father always says creating something is much less difficult that maintaining it,well this happened once again for me!!!.
I found maintaining this thread difficult I am officially announcing that you may stop expecting updates on this thread.Hats off to sssomnath474 to giving a new life to it!!!And it looks more informative as well!!
To add salt to injury A65 which my wife was holding is having issues with front speaker.Even after its trip back from the service centre gurus,it again managed to holdon the issue.I have given up on the micromax guys as of now.
GUYS,PLEASE FOLLOW THE BELOW THREAD BY sssomnath474 HENCEFORTH
http://forum.xda-developers.com/showthread.php?t=2501464
Recent activities as on 07 Aug 2013
--------------------------------------------------------------------------------------
1.Unlocked boot image and rooted it.
2.Install CWM.
3.Flashed firmware
4.sssomnath474 installed xloud,beats,bravia and confirmed it is working.
5.sssomnath474 also made few modification with UOT and came up with update.zip.
6.Right now we have unlocked V4 boot img which according to sssomnath474 has battery life updation.
7.I am studing as much time i can extract for an OC kernel and sssomnath474 is working on a rom.
8.As update by sssomnath474 this boot.img can have a better battery backup
http://www.mediafire.com/download/opweg2nwd0hk5dw/new_boot.img
let me know if you guys have access issues with any of the links or any of the link appears to be dead
9.Added a user guide how to flash the firmware.Hope it helps
http://www.mediafire.com/download/h2q51j8ovn1m1pc/Flash_firmware_config.pptx
10.you can use windows 7(you have to boot it in test mode and run the research downloader in administrator)
Thanks to sssomnath474 for the info
11.you can use unlock root as confirmed by sssomnath474
Thanks to sssomnath474 for this info
12.LIST OF STOCK IMAGES/PAC FILES FOR ALL MICROMAX MODELS
http://www.moulnisky.com/index.php?dir=Micromax
Thanks to sssomnath474 for this info
13.Heard from sssomnath474 that somebody has bumped imei while flashing.If any of you is stuck with the same issue i would suggest a complete firware flash following this tutorial,ONLY difference in this case will be DONT use my modified boot.img just flash the pac file as it is.
14.WoW! guys never thought this thread will get mushroomed like this....thanks to sssomnath474 ,shubhamym21 ,J.E.abhishek kumar and others for keeping things rolling
15.Some of you are facing weird problems with sims as my quick scan through the posts suggested,any updates on this guys?
I made changes to OP what sssomnath474 suggested, i am saying again all you need to do in the research downloader is select the pac file,uncheck calibration.
16.pradipkunwar51 has reported issue with docomo sim after flashing,i believe shubhamym21 already found a solution to it.Will Update the OP as soon as he comes back with comments
17.Critical Update:Tutorial & Tool if you messed up your EMI
Tutorial can be found here : China spd adnroid phone imei change just one click
& here is the download link : Android SPD IMEI Writing Tool_R1.5.3001 - Download - 4shared - maroof azam
Thanks to shubhamym21 for sharing the link and tutorial
18.Moved all updates under this activity section for better clarity
19.Adding Bravia engine zip
http://forum.xda-developers.com/showpost.php?p=44487763&postcount=138
Thanks to sssomnath474 for the link
--------------------------------------------------------------------------------------
Finally rooted my Micromax A65.Follow the guide carefully to avoid mistakes.I am not responsible for any physical/logical damage to you and your device .
Thanks to authors and their posts
http://forum.xda-developers.com/showthread.php?t=2165554 ElectronikHeart(Guru of spreadtrum)
http://forum.xda-developers.com/showthread.php?p=42693514#post42693514 Yekdall (confirming me unlocking the boot.img is key)
http://forum.xda-developers.com/showthread.php?p=42776196#post42776196 Intex12345(calibartion tabs needs to be unckecked in RD)
http://whiteboard.ping.se/Android/Rooting (for unlocking the boot.img)
Foreground
A Chaina re-branned phone
A fastboot mode
A useless recovery mode
A locked boot.img (thats why even chmod or simply pushing a su will not root the phone)
A IMEI number(which if you mess up after flashing,you will not get any radio signals)
1)First Unlock the Boot IMG
Before you proceed I will strongly recommend to download the tutorial guide ppt that you will find in Recent Activity list at the top of this post
You need to tamper permission after extracting the boot.img for this.No worry guys i have already done that for you .Just download the below file
Unsecured Boot Image
Now a bit critical part,read carefully .This unlocked image needed to be flashed to your device.For that you need research download and firmware pac file.
Download this to files from the below links
PAC versions & Tools Download
(pac file,driver,research download all included)
Download this drivers and install,after successfull installtion you will have(under device manager)
1.ABD interface
2.two COM ports
3.two emulators
If any of this having yellow sign it will not work.
Open research download
click on first button and load pac file
click on second button change baudrate to 115200,in calibration tab uncheck all.
For BOOT_IMG option browse and select the unlockedboot.img that you downloaded now.
plugin the usb cable(DON'T plugin the phone now)
click on play button
PRESS & HOLD VOLUME UP KEY and insert the usb cable,don't release the key.
Download should starts within 3 secs.If it doesn't then check the drivers carefully or reply to this thread with failures.
Once done unplug your phone and remove battery for 3 second
Reinsert battery and restart your phone.
YES!! you have successfully unlocked the boot.img
2)WiseMen Backup!!
First thing you should do before any tweaking and twisting save your back!!.Install CMW using the below method straight away and save your back.
1.Download .andriod.zip,extract it and save it under C:\Users\<computer name>\<paste it here>
http://www.mediafire.com/download/ga5tk2h89m41ddk/.android.zip
2.From your phone got to application-->developer option-->enable usb debugging
3.Now plugin your phone through micro usb cable.
4.Download this zip ,extract and place in under c:/<paste it here>
http://www.mediafire.com/download/s2as5grqceqtqq3/Android_Multi_tool.zip
5.Open a command prompt type
Code:
cd C:\Android Multi tool
C:\Android Multi tool>fastboot devices
20080823 fastboot
Note:you will NOT be able to proceed further if this doesnt shows up.Double check the andriod.zip has adb_usb.ini file.
Now we will flash a custom recovery image in fastboot mode.
Code:
C:\Android Multi tool>fastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 10.487s]
writing 'recovery'...
OKAY [ 3.425s]
finished. total time: 13.918s
7.Reboot your phone.
8.Now got to CMW using Volume up + power button and do a backup.
3)Push superuser zip & ROOT!!!
This the easiest step among all of them.Download the below file,put it under sdcard and flash it through CMW.
http://www.mediafire.com/download/t55b6ebzvx9yf1f/update.zip
THAT'S IT you are rooted!!!
REMEMBER,PROBABILITY OF BRICKING IS MINIMUM AS I HAVE ALREADY DONE ALL THE TEST FOR YOU GUYS !!!.STILL IF ANYTHING GOES WRONG DONT PANIC,JUST FLASH A FIRMWARE AS MENTIONED ABOVE(point 1) EVENIF YOUR PHONE IS
TOTALLY DEAD .
----------------------------------------------------------------------------------------------
Please hit thanks if i you find this useful

No body tested it yet ?

question
sayannayas said:
No body tested it yet ?
Click to expand...
Click to collapse
what if i flash it with fastboot
---------- Post added at 01:07 PM ---------- Previous post was at 12:48 PM ----------
beacuse i just flashed it with fastboot and its not booting
waiting for 10 mints

recovery.img error
sayannayas said:
MICROMAX A65 ROOTED!!
Finally rooted my Micromax A65.Follow the guide carefully to avoid mistakes.I am not responsible for any physcial/logical damage to you and your device .
Thanks to authors and their posts
http://forum.xda-developers.com/showthread.php?t=2165554 ElectronikHeart(Guru of spreadtrum)
http://forum.xda-developers.com/showthread.php?p=42693514#post42693514 Yekdall (confirming me unlocking the boot.img is key)
http://forum.xda-developers.com/showthread.php?p=42776196#post42776196 Intex12345(calibartion tabs needs to be unckecked in RD)
http://whiteboard.ping.se/Android/Rooting (for unlocking the boot.img)
Foreground
A Chaina rebranned phone
A fastboot mode
A useless recovery mode
A locked boot.img (thats why even chmod or simply pushing a su will not root the phone)
A IMEI number(which if you mess up after flashing,you will not get any radio signals)
1)))First Unlock the Boot IMG
You need to tamper permssion after extracting the boot.img for this.No worry guys i have already done that for you .Just download the below file
http://www.mediafire.com/download/1c6r9cu9iwc3769/boot.zip
Now a bit critical part,read carefully .This unlocked image needed to be NAND flashed to your device.For that you need research download and firmware pac file.
Download this to files from the below links
http://forum.gsmhosting.com/vbb/f811/guide-all-micromax-root-clockworkrecovery-1627895/
(pac file,driver,research download all included)
<IT WILL ONLY WORK IN 32 BIT WINDOWS XP,VM ALSO FINE>
Download this drivers and install,after successfull installtion you will have(under device manager)
1.ABD inteface
2.two COM ports
3.two emulators
If any of this having yellow sign it will not work.
Open research download
click on first button and load pac file
click on second button change baudrate to 115200,in calibaration tab uncheck all.
For BOOT_IMG option browse and select the unlockedboot.img that you downloaded now.
plugin the usb cable(DONT plugin the phone now)
click on play button
PRESS & HOLD VOLUME UP KEY and insert the usb cable,dont release the key.
Download should starts within 3 secs.If it doesnt then check the drivers carefully or reply to this thread with failuers.
Once done unplugg your phone and remove battery for 3 second
Reinsert battery and restart your phone.
YES!! you have sucessfully unlocked the boot.img
2)))WiseMen Backup!!
First thing you should do before any tweaking and twisting save your back!!.Install CMW using the below method straight away and save your back.
1.Download .andriod.zip,extract it and save it under C:\Users\<computer name>\<paste it here>
http://www.mediafire.com/download/ga5tk2h89m41ddk/.android.zip
2.From your phone got to application-->developer option-->enable usb debugging
3.Now plugin your phone through micro usb cable.
4.Download this zip ,extract and place in under c:/<paste it here>
http://www.mediafire.com/download/s2as5grqceqtqq3/Android_Multi_tool.zip
5.Open a command prompt type
Code:
cd C:\Android Multi tool
C:\Android Multi tool>fastboot devices
20080823 fastboot
Note:you will NOT be able to proceed further if this doesnt shows up.Double check the andriod.zip has adb_usb.ini file.
Now we will flash a custom recovery image in fastboot mode.REMEMBER,PROBABILITY OF BRICKING IS MINIMUM AS I HAVE ALREADY DONE ALL THE TEST FOR YOU GUYS !!!.STILL IF ANYTHING GOES WRONG DONT PANIC,JUST FLASH A FIRMWARE AS MENTIONED ABOVE(point 1) EVENIF YOUR PHONE IS TOTALLY DEAD .
Code:
C:\Android Multi tool>fastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 10.487s]
writing 'recovery'...
OKAY [ 3.425s]
finished. total time: 13.918s
7.Reboot your phone.
8.Now got to CMW using Volume up + power button and do a backup.
3))Push superuser zip & ROOT!!!
This the easiest step among all of them.Download the below file,put it under sdcard and flash it through CMW.
http://www.mediafire.com/download/t55b6ebzvx9yf1f/update.zip
THATS IT you are rooted!!!
REMEMBER,PROBABILITY OF BRICKING IS MINIMUM AS I HAVE ALREADY DONE ALL THE TEST FOR YOU GUYS !!!.STILL IF ANYTHING GOES WRONG DONT PANIC,JUST FLASH A FIRMWARE AS MENTIONED ABOVE(point 1) EVENIF YOUR PHONE IS
TOTALLY DEAD .
Please hit thanks if i you find this useful.:good:
Click to expand...
Click to collapse
finally i rooted my cellphone thank u guys n thank u xda

sssomnath474 said:
what if i flash it with fastboot
---------- Post added at 01:07 PM ---------- Previous post was at 12:48 PM ----------
beacuse i just flashed it with fastboot and its not booting
waiting for 10 mints
Click to expand...
Click to collapse
You should not flash anything before you have unlocked the boot.img.It comes with a locked boot so flashing through fastboot may not work.
First thing that you should do now is stage up a windows xp with the drivers that i have linked here.connect your phone with research download and do a firmware flash.This will recovery your phone to its orginal state.Then follow my steps from the start(pls dont skip)

navi_5886 said:
i have done the same but when i go to recovery option it says cannot mount e:
Click to expand...
Click to collapse
you should have micro sd card,and it should be in fat32 formatted.Better if you backup your data in sdcard,format it with fat32 and then place only the update.zip

sayannayas said:
You should not flash anything before you have unlocked the boot.img.It comes with a locked boot so flashing through fastboot may not work.
First thing that you should do now is stage up a windows xp with the drivers that i have linked here.connect your phone with research download and do a firmware flash.This will recovery your phone to its orginal state.Then follow my steps from the start(pls dont skip)
Click to expand...
Click to collapse
ok downloading windows xp..good thing is i'm not scared
well do u have facebook id?

sssomnath474 said:
ok downloading windows xp..good thing is i'm not scared
well do u have facebook id?
Click to expand...
Click to collapse
Dont get me wrong but i think it is better to log your errors here as it might help others as well as me to correct the OP.
Once you have the setup use exact set of drivers and pac file that i linked in this thread.remember if you have a successful driver installation then you will have at least(under device manager)
2 new COM ports
2 emulators
I am working on capturing few snapshots or a demonstration guide,it will take time as i recently lost my bag-pack,will update with videos once i stage up.

sayannayas said:
Dont get me wrong but i think it is better to log your errors here as it might help others as well as me to correct the OP.
Once you have the setup use exact set of drivers and pac file that i linked in this thread.remember if you have a successful driver installation then you will have at least(under device manager)
2 new COM ports
2 emulators
I am working on capturing few snapshots or a demonstration guide,it will take time as i recently lost my bag-pack,will update with videos once i stage up.
Click to expand...
Click to collapse
thankx bro..it will help more if you give screenshots

sayannayas said:
Dont get me wrong but i think it is better to log your errors here as it might help others as well as me to correct the OP.
Once you have the setup use exact set of drivers and pac file that i linked in this thread.remember if you have a successful driver installation then you will have at least(under device manager)
2 new COM ports
2 emulators
I am working on capturing few snapshots or a demonstration guide,it will take time as i recently lost my bag-pack,will update with videos once i stage up.
Click to expand...
Click to collapse
need a help do i only check boot_img or i check all files?

sssomnath474 said:
need a help do i only check boot_img or i check all files?
Click to expand...
Click to collapse
check all files in main page,but for boot_img browse a select the unlocked boot.img that i have linked in this thread.The idea is to flash the unlocked boot.img instead of stock boot.img. Uncheck all in calibration page.Keep baudrate 115200
Also download the ppt that i just added.It may help you. Don't give up,setting the drivers will take trails & errors but i guarantee you the success

sssomnath474 said:
need a help do i only check boot_img or i check all files?
Click to expand...
Click to collapse
sucsessfully flashed with origianal system file..and one thing more it worked in windows 7 64 bit too

sssomnath474 said:
sucsessfully flashed with origianal system file..and one thing more it worked in windows 7 64 bit too
Click to expand...
Click to collapse
Great news buddy.If you have used my unlocked boot.img while flashing then rest of the steps will be a breeze to you.Install CWM and take a full back up.Then flash the update.zip,thats it.

sayannayas said:
Great news buddy.If you have used my unlocked boot.img while flashing then rest of the steps will be a breeze to you.Install CWM and take a full back up.Then flash the update.zip,thats it.
Click to expand...
Click to collapse
well thankx for boot image and help device is rooted
but this can be done in other way to
1.you can use windows 7(u have to boot it in testmood and run the research downloader in adminstor)
2.just use unlock root
thats it
thankx man.pls give ur facebook id

sssomnath474 said:
well thankx for boot image and help device is rooted
but this can be done in other way to
1.you can use windows 7(u have to boot it in testmood and run the research downloader in adminstor)
2.just use unlock root
thats it
thankx man.pls give ur facebook id
Click to expand...
Click to collapse
Mentioned your updates in OP.Hope you dont mind

sayannayas said:
Mentioned your updates in OP.Hope you dont mind
Click to expand...
Click to collapse
ok ok
well making some customizing themes in UOT cooked kitchen.hope it will work

sssomnath474 said:
ok ok
well making some customizing themes in UOT cooked kitchen.hope it will work
Click to expand...
Click to collapse
Wow! that will be really nice...hope you will share those with us

sayannayas said:
Wow! that will be really nice...hope you will share those with us
Click to expand...
Click to collapse
check it out

need pac file...!!!!
sssomnath474 said:
thankx bro..it will help more if you give screenshots
Click to expand...
Click to collapse
can anyone upload only pac file for mmx a65 !!!!! please......!!!!""

sssomnath474 said:
check it out
Click to expand...
Click to collapse
WOW looking nice...waiting for the release
Also if you are maintaining your own a65 thread for customs roms,suggest you to cross link with mine(vice versa) and keep track for both the threads

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.

[ANDROID 10]Galaxy A80 Root➕Unlock Bootloader➕Flash Official Firmware (13 March 2020)

WARNING: You can't downgrade anymore once you flashed U4/S4 March update !
https://samfrew.com/model/SM-A805F/
SM-A8050
SM-A805F
SM-A805N you can't unlock bootloader on this variant! (R1Q_KOR_SINGLE.pit)
You will need:
-Odin v3.14.1
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
-Galaxy A80 Latest USB Driver
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
You want to download latest firmware directly from server? (fast download)
Samfirm 0.4.1 or Frija 1.4.2
https://samfirmtool.com/samfirm-v0-4-1
https://github.com/wssyncmldm/frija/releases
Frija not working ? install both vcredist_x00 for your device !
(Check your windows settings to know which version to install).
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
-https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
-https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-A805F) and your CSC : (mine is LUX).
(All CSC's and models on Samfrew: https://samfrew.com/model/SM-A805F/).
-Download and extract SM-A805XX_1_00000000000000_xxxxxxxxxx_fac.zip
On your device:
If you want to unlock bootloader:
-Go to Settings then to About phone and find your build number.
-Tap on your build number 6 times until you see “You’re now a developer”.
-Go in Developer options > enable OEM unlocking.
-Connect the device to your PC.
-Power off your device with POWER and volume DOWN and directly hold volume UP and DOWN together!
-Device will boot in DOWNLOAD MODE.
-Long press volume UP to unlock the bootloader. This will wipe your data and automatically reboot your device!
If you dont want to unlock bootloader:.
-Download and extract Odin and open it as administrator.
Still in DOWNLOAD MODE:
-Click on BL and select BL_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on AP and select AP_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
-Click on CP and select CP_A805FXXXU4AXXX_CP14483800_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on START and wait for installation, when done you can unplug your device.
ROOT​Your KNOX status will be tripped if you follow this tutorial...​What's knox ? : https://www.google.com/search?q=samsung+knox+explained
-Download the latest stock firmware for your Samsung Galaxy A80 with Samfirm/Frija app (faster) or Samfrew/Sammobile website (way slower).
https://samfrew.com/model/SM-A805F/
-Extract the SM-A805XX_1_EXAMPLE_0000000000_fac.zip file with 7zip or any other unzipper.
-Copy the (AP_A805XXXXU1XXXX_CL00000000_QB00000000_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5) file and transfer it to your internal storage.
-Download and install Magisk Manager APK https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
-Open Magisk Manager and go to Install > Install > Select and Patch a file.
-Navigate through the storage and select the extracted AP file.
The firmware will be patched and will be found in Internal Storage/Download/magisk_patched.tar.
-Transfer the patched file to your PC.
-Turn OFF your device and boot into DOWNLOAD MODE.
-In Odin, click on AP and select the patched tar file, Uncheck “Auto Reboot” and click on Install.
The tool will flash Magisk V20 on your Samsung Galaxy A80.
To boot in recovery or boot the system with Magisk installed:
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery

My storage was reduced from 128gb to 32gb after doing this. Is there a fix?

any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned

haanz85 said:
any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned
Click to expand...
Click to collapse
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.

Nazato said:
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.
Click to expand...
Click to collapse
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..

Could you please be more detailed in this steps?? I got this problems too. plz help.

hosheaxu said:
Could you please be more detailed in this steps?? I got this problems too. plz help.
Click to expand...
Click to collapse
read carefully every step bro. after flashing magisk patched then setup phone from beginning without setup google acount just skip, then check again by activating developer menu & usb debugging on. at the end reset from about menu..then phone's should reboot, after that install magisk manager then follow until finished process. & now after reboot u already got rooted beloved phone . congrats

haanz85 said:
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..
Click to expand...
Click to collapse
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.

Nazato said:
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.
Click to expand...
Click to collapse
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed

haanz85 said:
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed
Click to expand...
Click to collapse
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.

Nazato said:
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
yeah it's possible for sensitive pricing from first launching. in my country first launching price going around $705 then after few month until approaching new device release info to be released in February. on new years then the price going down until just left $549,50 then i decided to bought it :victory:
maybe many people's thinking like me, wait & see before grab this phone's :laugh:

Nazato said:
I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.

tin2404 said:
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.
Click to expand...
Click to collapse
but what about this device? are u still make exception from regular ongoing development.. until now there's no famous developer that saw it for builds known roms out there although this doll already succesfully rooted, but none of them build us twrp with fully support & maybe one or two working cust roms

Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3

BK said:
Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3
Click to expand...
Click to collapse
Is This only for france devices?

android 10
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks

uae.coool said:
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks
Click to expand...
Click to collapse
go right ahead I'm rooted on Android 10 right now just follow the instructions again

i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help

uae.coool said:
i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help
Click to expand...
Click to collapse
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE

Nazato said:
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE
Click to expand...
Click to collapse
ok thanks will try it now
other things is losing the memory showing 32gb after the root and when wipe no root ???
and one more things please how to install TWRP i tried many time but stack in the samaung logo ???
thanks again

How To Guide [Guide] Xiaomi Mi Pad 5 MIUI12/13 ROOT Step-by-step - Pass SafetyNet, Widevine L1

Everything you do, you do at your own risk. I'm not responsible for all damages, this can also lead to loss of warranty.
Hi,
Probably many of you know how to do a Magisk install without TWRP, but this guide is for people who don't know and don't want to mess things up.
I will try to show you step by step how to do it.
Many thanks to:
kdrag0n
topjohnwu
Leave them a nice feedback
!!! Before we start make sure your device is unlocked, if you don't know how to do it below is link to official Xiaomi guide !!!
https://c.mi.com/thread-2262302-1-0.html
Requirement
Xiaomi Mi Flash ver. =>3-14-0 - Needed to install all adb drivers Download
ADB & Fastboot tools - Could be the one built into Mi Flash tool I'll use this to make it simple
Magisk =>24.2 - This software is base of our rooting process Download
SafetyNet Fix => 2.2.1 (Zygisk) - Needed to backdoor SafetyNet fail check, at the moment it is only working method for Mi Pad 5 Download Make sure you download the Zygisk version!
Boot.img - You can download from official MIUI website full flashable rom and separate boot.img file from there, or use my if your Miui version is China 13.0.5, EEA 13.0.3, Global 13.0.1
China 13.0.5​EEA 13.0.3​Global 13.0.1​​​Installation
To make it easier, Green color mean what you need to do on Tablet, Orange on PC
Unzip Mi Flash tool
Open folder and run XiaoMiFlash.exe, if window "Driver" won't pop-up click on the Driver tab and then "Install" button and close all windows.
Connect your tablet to computer, when your tablet ask how you want use USB, choose File Transfer/Android Auto
Copy to internal storage Magisk-v****.apk, safetynet-fix-v****.zip and boot.img
Open File Manager on your tablet find a folder where you copied all files, and install Magisk
Open Magisk app, and click on Install in section Magisk, then select "Select and Path a File", after that find your boot.img file and click on it
Click "LET'S GO" button on the right side and wait until process will be finished
On your computer in the tablet's storage window, go to the file specified in the application probably /Download/magisk_patched-*****
Copy this file to a subfolder of Mi Flash on your computer, exactly to MiFlash2020-3-14-0\Source\ThirdParty\Google\Android and change the name of this file to boot.img
Open PowerShell/Windows Terminal in this folder (Hold Shift + Right click -> Open PowerShell window here)
Make sure your tablet have enabled USB debugging in Developer options Setting -> Additional settings -> Developer options -> USB debugging
Turn off your tablet, then hold down Power and VOL- until the screen lights up, then release power button, if Fastboot appears, everything went fine
Go back to your Terminal window and type to check if your computer see your tablet
Code:
./fastboot.exe devices
If you see answer "******** fastboot" it mean there is communication between PC and Tablet
Next type this command to flash patched boot image
Code:
./fastboot.exe flash boot boot.img
Next type this command to reboot your device
Code:
./fastboot.exe reboot
Restart can take a longer time than normal
Open Magisk app and check status of Magisk, if you see for exaple "Installed 24.2 (24200)" everything went fine
Open Settings in right corner of app and in section App click on Hide the Magisk app then type name for hidden app, it will ask to install new app so do it
Open again Magisk app and open Settings in section Magisk enable Zygisk (Beta) and Enforce DenyList
Click on Configure DenyList than click on three dots in right corner and uncheck Show system apps
Search for all the apps in the list below and check them. It is important to click on their name to see all modules, once you have done this click on the box to activate all of them
Code:
Google
Google Assistant (I have two)
Google Pay
Google Play services
Google Play Store
After that reboot your tablet, and open again Magisk app
On the bottom click on Modules
Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
After that reboot your device one more time
After reboot open Android Settings go to Apps and Unhide system services than find and clear all data of Google Play services and Google Play Store
Reboot tablet last time
If you have reached this point it means that everything has gone correctly, probably for about 3 hours you will still not be able to install Netflix and some banking applications but after this time everything will be back to normal, this is because Google's servers have detected that Magisk has been installed but that the application has been changed and Zygisk has been enabled so at the next check it notices that everything is Ok and gives access back.
Quick explaination what happend here:
Magisk has been installed and device is Rooted
The application has been changed and hidden
Zygisk has been activated and hidden from Google services
SafetyNet-fix was installed, which restores the functionality of SafetyNet and Widevine L1, which is blocked after the installation of Magisk and unlocked Bootloader

Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01

Nux01 said:
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Click to expand...
Click to collapse
Hi Nux01,
1. Unfortunately yes, TWRP isn't supported for Pad 5 yet.
2. It won't work, TWRP app is only making a request to TWRP custom recovery, until it doesn't exist you can't even install custom ROM
3. It is, but i didn't test it yet on Pad 5, and I don't know if it will work with new decides because last release is from 20.07.2020.
https://github.com/francescotescari/XiaoMiToolV2/releases
4. Yes, you need Xiaomi account, also your device has to be logged in, and registered to unlock, Xiaomi made complete guide how to do this, link is on the top of this post.

Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01

Nux01 said:
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Click to expand...
Click to collapse
I mean it's quite old release so it may not work with current unlock bootloader process on new devices like a Xiaomi 12, Xiaomi Pad 5 etc. I can't promise it won't brick your device, only confirmed method is by official Xiaomi tool.

Thank you
I'll wait a little bit before rooting my tablet.
Have a nice day.

Followed the instruction, worked like a charm. Although I had unknown "chinese sings" errors with the driver install it worked. By the way there is a newer version of the flashing tool.
Thanks for the effort of writing this down!

Hello,
I just managed to unlock the bootloader of my tablet "Pad 5".
I tried under Mac and Linux with Xiaomitool V2 without success (error 20036 and 20045).
I also tried with VirtualBox who did not recognize the tablet.
I succeeded with VMware and Windows 7 by testing different drivers and it worked.
I just root the tablet with Magisk.
On the other hand, is there the equivalent of TWRP to make a complete system backup. Apart from Titanium and MyBackup.
Thanks for your help.

thanks dude.
didn't try this yet, just wondering.
can't i just flash recovery and then flash magisk.apk?
thanks

Can i update ota to 13.0.2 after rooted? Just update and root again?

Cpanel10x said:
Can i update ota to 13.0.2 after rooted? Just update and root again?
Click to expand...
Click to collapse
You can update, but after that you need root again but with boot.img from 13.0.2

How to get the boot.img 13.0.2? I checked the 3GB Firmware and only found vendor_boot.img. Is it the same thing?

Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5

Thomas Brown 99 said:
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Click to expand...
Click to collapse
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...

Thanks for this awesome guide. Do you have some suggest about the magisk modules to install?

thanks, it just worked perfectly and your step by step guide is very handy and helpful. thanks so so much.

vjsaini00 said:
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Click to expand...
Click to collapse
Today evening, I'll add more boot.img

kisielec said:
Today evening, I'll add more boot.img
Click to expand...
Click to collapse
eagerly waiting, Thanks

Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
24. Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
25. After that reboot your device one more time
Click to expand...
Click to collapse
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?

cysmaster said:
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
Click to expand...
Click to collapse
I also have this module installed without problems, as there is no recovey for Pad5, it is a good idea to install in magisk the module Magisk Bootloop Protector, which serves exactly to prevent what you are afraid that happen with your tablet

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