Database Info

[Guide] How to get rid of force encryption/dm-verity on Huawei MediaPad T3 10 (AGS-W0

I was frustrated by the huawei encryption and decided to get rid of it once and for all.
At first I faced many bootloops but i finally figured out what was going on. Formatting user data through TWRP is not enough because after booting the device, encryption is still there. This happens because the kernel encrypts the device when booting up. Simply modifying the boot.img file to remove file encryption also doesn't work because you still boot into an already encrypted stock user data. So the answer was pretty obvious by now.
The trick is to format data using TWRP AND THEN boot to bootloader to flash a modified boot without encryption. So let's get to it.
How to create a modified boot.img without file encryption/dm-verity
1. Find and download your current firmware from Huawei Firmware Finder Dtabase (Team MT), or from a source that you trust. (Using a firmware with different cust version or a different update will most likely not work).
2. Download Huawei Update Extractor and use it to extract the stock boot.img file from UPDATE.APP
3. Download ASSAYYED_KITCHEN.
4. Place your stock boot.img file in the "WORK" folder of ASSAYYED_KITCHEN.
5. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 1st one (Unpacking Kernel).
6. The ASSAYYED options don't work for me so i did it manually. Go to your work folder and open the folder boot_unpacked\ramdisk.
7. You will see a file named "fstab.qcom", open it using WordPad.
8. Find the line:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,fileencryption
and delete ",fileencryption".It should now look like that:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check
9. (This step is optional,follow it only if you also want dm-verity removed) Use the same method to remove dm-verity.
Code:
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/product /product ext4 ro,barrier=1 wait, verify
(Just delete the ",verify" part.)
10. Save the file.
11. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 2nd one (Packing Kernel).
12. Follow the instructions below to properly flash your modified boot.img and get rid of encryption.
Removing file encryption/dm-verity from the device
1. Unlock your device.
2. Flash this TWRP on AGS-W09 or the appropriate custom recovery for your device.
3. Boot to TWRP and FORMAT user data (note that it is very important to format data and not just wipe it). •WARNING• this will delete all your data!
4. Go back to the reboot menu of TWRP and select reboot booloader (it's important to not allow your device to boot into system yet).
5. Using fastboot, flash your modified boot.img that you created earlier.
6. Reboot your device (you might get a bootloop on the first boot but force rebooting your device again by holding the power button will fix that).
7. After booting up, your device should not be encrypted anymore.
8. You can now use the root method that you like to root your device and internal storage should be visible on TWRP. TWRP backup should also work normally.
How to fix Magisk modules not showing up on Magisk Manager (! /data/adb/magisk_merge.img mount failed error)
I am not going to get into the technical staff you can find more info here
Edit: As of Magisk 19.0, the following method becomes obsolete. Magisk modules should now work as expected without issues. This method now concerns those who want to stick to an older version of Magisk
1. Download f2fsfix-2018.9.2.zip provided by VR25 on the thread above.
2. Download all the magisk modules that you need to flash and place them on your device.
3. Download the latest Magisk uninstaller along with the latest installer.
4. Boot to TWRP and flash Magisk uninstaller. (If you don't have Magisk already installed, skip this step)
5. Wipe Davlik Cache.
6. Install the latest Magisk.
7. Wipe Davlik Cache.
8. Flash the "f2fsfix-2018.9.2.zip" immediately followed by your modules.
9. Reboot (it should take more than usual).
10. Open Magisk Manager and check your Modules. Hopefully they'll show as installed and function correctly.
Note: This method should also work on similar devices. Just make sure you know how to recover your device in case something goes wrong.

I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!

TRS_80 said:
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
Click to expand...
Click to collapse
Glad it worked for you. Yes this is the downside. The device already comes with an encrypted userdata, so it needs to be formatted. So anything you do before that becomes obsolete. That's why this procedure is much more convenient when it happens after the unlock,when the userdata is wiped by the stock recovery to get a stock condition.

AGS-L09 LTE
I just followed your detailed guide to my tablet and finished all the processes perfectly.
Working..Twrp, Magisk, removed encryption & verify from boot.img and from Data successfully.
A big THANKS for your guide, links and trick all in one post!!!!.

Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again

mr_fingy said:
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
Click to expand...
Click to collapse
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device here. If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img

Thanostsak said:
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device . If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Click to expand...
Click to collapse
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again

mr_fingy said:
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
Click to expand...
Click to collapse
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.

Thanostsak said:
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Click to expand...
Click to collapse
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks

mr_fingy said:
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
Click to expand...
Click to collapse
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)

Thanostsak said:
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Click to expand...
Click to collapse
On it now before work
Extracted stock_boot_(IDremoved).img.gz which contains the img
Will run your guide against this img
---------- Post added at 09:20 AM ---------- Previous post was at 08:33 AM ----------
All done. Nice and easy
No issues other than sweaty palms on Huawei long boot screen after flash :silly:
No reboot loop and no Magisk errors
Much appreciated for the help

Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good

mr_fingy said:
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
Click to expand...
Click to collapse
Great! If you need anything feel free to ask.

Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)

TimYuan said:
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
Click to expand...
Click to collapse
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
VR25 said:
Those getting everything broken after a second reboot, try the following workaround...
After the first reboot (right after installing), remove </sbin/.core/img/f2fs*bla*bla/service.sh>, </data/adb/magisk_merge.img> and </cache/magisk_merge_.img>.
Note that after doing this, you'll only be able to install modules and update Magisk from TWRP.
Click to expand...
Click to collapse

Thanostsak said:
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
Click to expand...
Click to collapse
It works!!! You are my hero!

TimYuan said:
It works!!! You are my hero!
Click to expand...
Click to collapse
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.

Thanostsak said:
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Click to expand...
Click to collapse
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance

an-_-dro said:
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
Click to expand...
Click to collapse
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.

Thanostsak said:
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Click to expand...
Click to collapse
encryption is not a problem. since the first place already done with that data partition.
my problem is system partition, every time i made a change to system (for example deleting chrome.apk), something triggered that makes my system weird (magisk forceclose, all file manager become malfunction because system become read only). something lock my system partition if system change.
i thought change fstab.qcom <mnt_flags and options> ro,errors=panic to >> errors=continue (deleting ro/read only) will change my system behaviour, but it's not

[OTA] [DUMP] [BOOT] 10.0.15.0 original and magisk patched

original
boot_10.0.15.0.img
magisk patched
patched_boot_10.0.15.0.img

Thank you, but do you have 10.0.14.0 stock boot img?

Frano35 said:
Thank you, but do you have 10.0.14.0 stock boot img?
Click to expand...
Click to collapse
You can find it somewhere in the forums.

yashinodon said:
You can find it somewhere in the forums.
Click to expand...
Click to collapse
Yeah, I found it, but I rushed with my questions, found them 2 minutes later. My bad

thanks dude

psyriccio said:
original
boot_10.0.15.0.img
magisk patched
patched_boot_10.0.15.0.img
Click to expand...
Click to collapse
Any guides about how you got these boot images?

yashinodon said:
Any guides about how you got these boot images?
Click to expand...
Click to collapse
I updated the real device.
Unlocked the bootloader.
Booted into TWRP recovery (via fastboot).
Dumped the boot partition.
Patched image using Magisk Manager v20

psyriccio said:
I updated the real device.
Unlocked the bootloader.
Booted into TWRP recovery (via fastboot).
Dumped the boot partition.
Patched image using Magisk Manager v20
Click to expand...
Click to collapse
Never thought of this method. Thanks for sharing.

psyriccio said:
I updated the real device.
Unlocked the bootloader.
Booted into TWRP recovery (via fastboot).
Dumped the boot partition.
Patched image using Magisk Manager v20
Click to expand...
Click to collapse
may i ask what TWRP did you use and how did you decrypt the device?

barumbads said:
may i ask what TWRP did you use and how did you decrypt the device?
Click to expand...
Click to collapse
twrp-3.2.3-0-daisy.img
fastboot boot ./twrp-3.2.3-0.daisy.img
boot partition not crypted
I use OTG-connector with USB flash drive to store backup of boot partition

psyriccio said:
original
boot_10.0.15.0.img
magisk patched
patched_boot_10.0.15.0.img
Click to expand...
Click to collapse
Question, just to be sure... the boot_10.0.15.0.img you upload is about 64mb, last 10.0.14.0.img is 27mb or I am missing something or the original boot from 14 to 15 increased its size?
Thanks

sebadamus said:
Question, just to be sure... the boot_10.0.15.0.img you upload is about 64mb, last 10.0.14.0.img is 27mb or I am missing something or the original boot from 14 to 15 increased its size?
Click to expand...
Click to collapse
The partition is 64Mb. If you extract from the partition that's the size file you get.
If you decode the image you can find its actual size and truncate it. That's a bit nontrivial, but definitely possible.
If you get Magisk Manager to patch a file, it does this and you get a 27Mb file.
It does not hurt to flash "extra" data after the image so the only reason to truncate the image is to save space. My PC has 100Gb or more for various phone files, space is of no concern to me

a1291762 said:
The partition is 64Mb. If you extract from the partition that's the size file you get.
If you decode the image you can find its actual size and truncate it. That's a bit nontrivial, but definitely possible.
If you get Magisk Manager to patch a file, it does this and you get a 27Mb file.
Click to expand...
Click to collapse
Hi! I’m on Mi A2 lite and curious about the procedure to extract the boot.img. Can you explain it to me?
I know that there are 64 MB boot.img, which I believe are created by making a backup of the entire boot partition, using the TWRP via fastboot. Then these boot.img are reliable too, because they aren't modified in some way by the installation of the TWRP. Right? But I can't really know if the TWRP was used via fastboot or installed on the phone, so I think it's better to always use boot.img of about 30 MB.
Sorry for my bad English!

DekiS3 said:
Hi! I’m on Mi A2 lite and curious about the procedure to extract the boot.img. Can you explain it to me?
...
I think it's better to always use boot.img of about 30 MB.
Click to expand...
Click to collapse
A certain paranoia is warranted. I do not trust random boot.img files from the internet. I would rather patch my own image. Most people do not seem to care enough to take the time to do things themselves, and will happily use files someone has uploaded to simplify things.
I am a longtime Linux/Unix user so I know my way around a command line, partitions, filesystems, etc.
This phone has a large number of partitions, including one for the boot image. It's possible to identify the current (A/B) from fastboot or a running system. That let's me identify the current or other partition.
The dd command is a low-level command to read and write data. It's commonly used to make a raw backup of a disk or partition. To extract the boot image I tell dd to read from the boot partition and write to a file. I do a vanilla backup after installing the OTA but before reboot, which means the other boot partition. After installing Magisk, I backup the current boot partition (which will be the same one, since the OTA changes A/B).
Because it is a low-level tool, dd does not understand what it is copying. Either you tell it how much data to read, or it reads until it runs out of data. That's why my boot backups are 64Mb, it's how much data dd reads.
If you have root, you can run dd from the phone (I normally use adb for easier typing). Otherwise, you can run it from TWRP.
I think TWRP may have partition backup stuff that provides a GUI around dd but given my history, I'd rather use the dd tool I'm already familiar with.
If you want to see exactly what I do, see my Advanced OTA guide on this forum.
Hope that helps explain things for you.

a1291762 said:
The partition is 64Mb. If you extract from the partition that's the size file you get.
If you decode the image you can find its actual size and truncate it. That's a bit nontrivial, but definitely possible.
If you get Magisk Manager to patch a file, it does this and you get a 27Mb file.
It does not hurt to flash "extra" data after the image so the only reason to truncate the image is to save space. My PC has 100Gb or more for various phone files, space is of no concern to me
Click to expand...
Click to collapse
Hi, V10.0.16.0 patched boot image isn't already up. Can you please make it and upload it?? :angel:
Thanks!

benropo said:
Hi, V10.0.16.0 patched boot image isn't already up. Can you please make it and upload it?
Click to expand...
Click to collapse
I posted this on https://forum.xda-developers.com/mi-a2-lite/help/magisk-november-update-t4003283
https://yasmar.net/xda/patched_boot_10.0.16.0_201.img.gz
https://yasmar.net/xda/vanilla_boot_10.0.16.0.img.gz
As the name hopefully implies, this is patched with Magisk 20.1

By flashing this would my device be eligible to receive the stock OTA Android One release of Android 10 once it's released?
Thanks

ConsistentCarl said:
By flashing this would my device be eligible to receive the stock OTA Android One release of Android 10 once it's released?
Click to expand...
Click to collapse
The phone won't install an OTA while partitions are modified. Magisk and TWRP both require modifying the boot image. There are guides on how to get an OTA to work with one/the other/both installed.

Not sure if this came across, but I would like to wipe my custom ROM once Android 10 OTA is released--I don't want both. In theory couldn't I install this and that should do the tragic? Or do I need to take extra steps like re-locking the bootloader?
Thanks

ConsistentCarl said:
Not sure if this came across, but I would like to wipe my custom ROM once Android 10 OTA is released--I don't want both. In theory couldn't I install this and that should do the tragic? Or do I need to take extra steps like re-locking the bootloader?
Click to expand...
Click to collapse
It depends on what you modified to install the custom ROM... You need to revert all partitions to stock. The easiest way would be to just get the most current fastboot image and flash that. If you wait, the android 10 OTA is likely to be accompanied by a fastboot image so you could just flash that.
I think most custom ROMs get you to modify the vendor partition to disable encryption. Reverting that could encrypt automatically but I'm not sure... If you're intending to preserve data you'll probably need to backup and restore.

August Security Patch Rolling Out

[Global] Mi A2 Lite V11.0.10.0.QDLMIXM rolling out!

Wow. That's gotta be some kind of record for Xiaomi
Mine is only 13M though. Must be a tiny update.

Wow! First time ever that this Android One device is actually up to date security wise.
Yes, from July update only 13MB.

Maybe it was there before, but after updating I noticed a native screen recorder icon.
Updated: It is not native. I have a screen recorder app installed.

Direct share not yet available.

penahj said:
Maybe it was there before, but after updating I notice a native screen recorder icon
Click to expand...
Click to collapse
strange i dont have this one and never had screen recording option

Antho02 said:
strange i dont have this one and never had screen recording option
Click to expand...
Click to collapse
You are right. It's not a native app. I have a screen recordering app installed. Sorry for the wrong news.

Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex

Alibabara said:
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Click to expand...
Click to collapse
+1 I am also looking for this

Alibabara said:
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Click to expand...
Click to collapse
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way

Antho02 said:
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Click to expand...
Click to collapse
So you Flash the whole Rom (~1.2gb) and not just the Update?
I would like to find a way to Flash just the Update since your method is taking too long for me...
Best regards
Alex

If you only have Magisk, the standard process should work for you.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
If it's not working and you have somehow modified some other partition, it will be written to the logcat.
adb logcat | grep update_engine

My Problem is, even with magisk 'uninstalled' the Update App from xiaomi still says 'Installation failed: Installation Problem'
That even happens with totally Stock rom, no root and no twrp.
I dont know why. But is there any other way to Update manually without flashing the whole Big Rom file? Just the Update file...
There must be a reason why there is an update file in zip Format which is 13mb Big.
Best regards
Alex

Alibabara said:
My Problem is, even with magisk 'uninstalled' the Update App from xiaomi still says 'Installation failed: Installation Problem'
That even happens with totally Stock rom, no root and no twrp.
I dont know why. But is there any other way to Update manually without flashing the whole Big Rom file? Just the Update file...
There must be a reason why there is an update file in zip Format which is 13mb Big.
Best regards
Alex
Click to expand...
Click to collapse
Alex, You don't have to flash the whole big rom file, but you do have to download it though. You can get it from here: https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
You then have to extract the files that you need with payload_dumper which you get from here:
https://androidfilehost.com/?fid=818070582850510260
NB that is the Windows 64bit version so make sure that is the OS your pc is using.
You then have to find which partition it is that is causing the problem for which you have to use a1291762's advice:
Code:
adb logcat | grep update_engine
and read very carefully through the results because the offending entry will be difficult to spot amongst the dozens of others.
You then flash the partition mentioned in the logcat. For example if 'system' is mentioned in the logcat as having an incorrect hash (that is always the reason for the failures) you would have to extract 'system.img' with payload_dumper and run
Code:
fastboot flash system system.img
Then try the update again. If it works you will also probably have to reinstall Magisk from scratch again as flashing system will probably remove it.
Yes it is complicated - far too complicated, but the simple measure you call for - just flash an update file - has, to the best of my knowledge never been possible, so there must be some reason why that is so, but I don't know what it is.
Incidentally, the reason I am able to respond to this question is that I had a torrid time yesterday trying to update my A2 lite on which I had not one, but 3 errors. aboot hash incorrect, system hash incorrect, and before any of that the normal Magisk uninstall told me it had no images to restore and so had to be uninstalled completely. It took me hours and it wasn't that much fun.

Alibabara said:
There must be a reason why there is an update file in zip Format which is 13mb Big.
Click to expand...
Click to collapse
The update is only 13M because it contains only changes. But for that to work, your partitions must be unmodified.
The larger update zip has complete partitions so it can work even if you have changes. You may be able to do the recovery update method with that file...
The even larger fastboot image has every partition.

thanks everyone for the help!
I did it as you said viking777 and it worked.
It's sad, that for an 13mb update this procedure is necessary, but thats how it is..
So thanks again everyone for the help

Antho02 said:
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Click to expand...
Click to collapse
Can I do this with out installing TWRP as I haven't installed it already.

Aadil Gillani said:
Can I do this with out installing TWRP as I haven't installed it already.
Click to expand...
Click to collapse
sure, even more quick if u dont need twrp
flash last rom with xiaomi flash (save user data selected)
then boot patched.img and install magisk, less than 10 mins and no need to worries about uninstall magisk or any mod before

Antho02 said:
sure, even more quick if u dont need twrp
flash last rom with xiaomi flash (save user data selected)
then boot patched.img and install magisk, less than 10 mins and no need to worries about uninstall magisk or any mod before
Click to expand...
Click to collapse
I have some questions it would be a be a pleasure if you could answer.
Q1 will the modules remain or not ?
Q2 how to make make patched boot img I mean should I make my self using Magisk Manager app
Q3 Also which TWRP do you use and if it has any problems
Q4 should I use zip file or tgz for mi flash

Development TWRP for Moto G Stylus 2021 xt2115-1 (otg mouse necessary)

OTG adapter and mouse necessary
I am wondering if anyone can fix this recovery or possible port a new one with the files I have included. I am willing to test if you don't have a device to test on. My original post is here
Post in thread 'TWRP coming?'
TWRP coming?
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup...
forum.xda-developers.com
Here are the files and recovery backups.
Resolution is 1080x2400
Board is SM6150
Aarch64
Stock android 10
Please help anybody with the know how. Thanks. I'll buy anybody a pizza for doing this! Get it working right and I will definitely support.
External_sdcard says unknown filesystem but still functions to backup all partitions except /vendor, /system and /product individually. Allows /super backup.
/vendor and /system_root (permission denied)
touch screen not functioning in recovery
Flashing causes black screen after boot logo splash
I used AIK on windows 10 with notepad++
*EDIT*
added driver to /sbin in /ramdisk. updated recovery below.

Hey, do u have telegram? If so hit me up on there @rcc2002 username "Ritmo".. Im working on getting you help on this subject as soon as possible because I am so happy that you were able to create this. It does temporary boot. I didn't try flashing it but the problems that create the black screen I believe are Android security during boot, usually something to do with dmverity i think, the no touch screen working is usually a driver issue that just needs a proper driver being installed in the build. Or even pushed with a terminal cmd poss I've seen.. And the two errors coming up permission denied for system root is one I've seen before and is I believe very common. All mostly has to do with Android security and all the little annoying issues in building a permissive recovery I suppose. But anyway the dude I'm going to ask will basically tell you probably exactly what to do the second he sees or hears the errors and sees ur files.. what do the two zip files contain? And how did you build this exactly? Curious.. from common trees from scratch or a device tree builder? if you don't have telegram, just text me 856-896-7600..... ~RAY..

They contain most of kernel files and recovery and boot stock backup. Build.prop fstab and ueventd.rc. Also the device tree all pulled from the device root using root explorer. I ported this over from a different device that had the exact same specs. I used AIK for windows and modified the files to correlate with the moto g stylus 2021.

ID like to work on this also do you have someway to communicate? I may have found one of the kernel source codes you can try building with.

In all honesty I just need somebody to help me learn how to install touch drivers into the recovery. Then I will use avbtools to resize the file to its proper size. Just need the info. The rest of the recovery works. I've tested almost all of it. Haven't tested adb yet but I'm sure that won't be a problem if faulty.

Here is the block partitions I used to partly configure the recovery. It's a bit messy but I think it's OK. Not trying to type all this out. Pulled from device last night.

sosthenisRR said:
OTG adapter and mouse necessary
I am wondering if anyone can fix this recovery or possible port a new one with the files I have included. I am willing to test if you don't have a device to test on. My original post is here
Post in thread 'TWRP coming?'
TWRP coming?
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup...
forum.xda-developers.com
Here are the files and recovery backups.
Resolution is 1080x2400
Board is SM6150
Aarch64
Stock android 10
Please help anybody with the know how. Thanks. I'll buy anybody a pizza for doing this! Get it working right and I will definitely support.
External_sdcard says unknown filesystem but still functions to backup all partitions except /vendor, /system and /product individually. Allows /super backup.
/vendor and /system_root (permission denied)
touch screen not functioning in recovery
Flashing causes black screen after boot logo splash
I used AIK on windows 10 with notepad++
*EDIT*
added driver to /sbin in /ramdisk. updated recovery below.
Click to expand...
Click to collapse
Contact me on telegram, I could possibly help. @Electimon

is anyone working on twrp for the xt2131-1?

aaronj1993 said:
is anyone working on twrp for the xt2131-1?
Click to expand...
Click to collapse
No, also that's the 5G https://forum.xda-developers.com/f/moto-g-stylus-5g.12373/

ShayBox said:
No, also that's the 5G https://forum.xda-developers.com/f/moto-g-stylus-5g.12373/
Click to expand...
Click to collapse
yes I know but that's the next closest device.

I'm mid-level to flashing but new(ish) to XDA here. Since this device is so similar "can" you flash the 5G ROMS to the 2021 ? And it boot/work somewhat ? Referring to Lineage OS for the most part since these devices are still somewhat "new" .. Trying to find the best place to ask and this seems to be it so far. No posts much yet in 2022 ..

roiikka said:
I'm mid-level to flashing but new(ish) to XDA here. Since this device is so similar "can" you flash the 5G ROMS to the 2021 ? And it boot/work somewhat ? Referring to Lineage OS for the most part since these devices are still somewhat "new" .. Trying to find the best place to ask and this seems to be it so far. No posts much yet in 2022 ..
Click to expand...
Click to collapse
The Moto G Stylus 5G has a different SoC, so this most likely would not work.

I just upgraded to android 11 on my moto g stylus 2021 XT2115-1 but now I cannot figure out how to root it I can install magisk and patch the boot but it does not stick and keep root but it does show ramdisk as yes, so not sure what the deal is, it has been awhile but it looks like to achieve it we will have to get rid of dmverity and vbmeta at least. to be able to keep a root or roll back to droid 10.

Well I cannot help with twrp but I was able to upgrade to android 11 and get root with magisk rather easily check this post all credit goes to the poster. https://forum.xda-developers.com/t/root-question-for-moto-g-stylus-xt2115-1-2021.4259413/

toxinburn said:
Well I cannot help with twrp but I was able to upgrade to android 11 and get root with magisk rather easily check this post all credit goes to the poster. https://forum.xda-developers.com/t/root-question-for-moto-g-stylus-xt2115-1-2021.4259413/
Click to expand...
Click to collapse
However if someone can get twrp working I got orange fox but meh not my fav i prefer touch twrp please let me know or if i can find it someplace ill post it worst case I just reflash stock recovery and try again.

I can help with this if it hasn't been fixed already ?? Just did twrp for XT2215-4 and XT2211-2

so is this stable? // who knows which ROMs are safe to flash to this xt2115 -1

Terrible this isn't working, you guys throw the stylus in the trash and get new devices?

What's the new member thing about. I've been on xda for 10 years

sosthenisRR said:
OTG adapter and mouse necessary
I am wondering if anyone can fix this recovery or possible port a new one with the files I have included. I am willing to test if you don't have a device to test on. My original post is here
Post in thread 'TWRP coming?'
TWRP coming?
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup...
forum.xda-developers.com
Here are the files and recovery backups.
Resolution is 1080x2400
Board is SM6150
Aarch64
Stock android 10
Please help anybody with the know how. Thanks. I'll buy anybody a pizza for doing this! Get it working right and I will definitely support.
External_sdcard says unknown filesystem but still functions to backup all partitions except /vendor, /system and /product individually. Allows /super backup.
/vendor and /system_root (permission denied)
touch screen not functioning in recovery
Flashing causes black screen after boot logo splash
I used AIK on windows 10 with notepad++
*EDIT*
added driver to /sbin in /ramdisk. updated recovery below.
Click to expand...
Click to collapse
I have the xt2115-1 and am curious to know what ever came of this. Was a working TWRP ever accomplished? I am trying to install a custom rom on my phone, but I can't seem to move past a permission denied issue in fastboot and can't seem to locate a working TWRP. Any suggestions?

A buggy twrp for A60, but not sure for M40.

I have made and got a buggy twrp for A6060, which is the Chinese version of M40, based on android-11. It can startup but lacking mtp and usb. It can't decrypt the /data too so you should do some preparations before can use it. I am not sure whether it can be used on M40.
Usage in shorts:
① Magisk and root. You can find the guide in this forum so I will pass it.
② Using a file manager to access /system/vender/etc/fstab.qcom, in the part of /userdata delete the field of "fileencryption=ice" (usually sth. like this, not includes the quotation marks), same and quit.
③ Enter recovery and wipe data. Then use odin flash this recovery: Just zip it to .tar file then flash in the AP slot.
④ When startup, press VOLUMN UP ＆ POWER. If everything goes well, you will see the logo of twrp and enter it and can successfully access the files in /data. Then you can copy some gsi and have a try.
Click to expand...
Click to collapse
Hope it will be helpful and I really hope somebody can make it a ture and full device tree. That will definetely benefit both A60 and M40 users.
The twrp for A60: https://github.com/Jason-summer/Action-Recovery-builder
The source of the twrp: https://github.com/Jason-summer/device_samsung_a60q/tree/android-11
Sorry for my poor English if causing someone confused.

good job! Is it possible to flash a phone using this? (i have a60)

blankkk123 said:
good job! Is it possible to flash a phone using this? (i have a60)
Click to expand...
Click to collapse
It works for me. But you should decrypt your phone first before you try to flash sth. or you may found /data a pile of random code.

SummerElement said:
It works for me. But you should decrypt your phone first before you try to flash sth. or you may found /data a pile of random code.
Click to expand...
Click to collapse
If it's not difficult, can you please write instructions? I think this will help many who want to flash