Database Info

[A510/A511] [WIP] Stock ROM dumps - Get back to factory state

As we now have functional recovery options on our tablets, and people will inevitably mess things up with their device, we need to get a way to get your tablets back to factory condition. But I need your help with this!
What do you want?
Here's my idea: We have all seen various ZIPs floating around, most of them leaked from somewhere. The problem with these is that you can't use OTA updates, and I'm not sure what Acer Service Center thinks of custom ROM installs. What I want is to build a list of software that is officially distributed by Acer, is OTA-updateable, etc. For this reason, I want people that have not yet modified their tablets (except root) to provide image dumps of their /system, /boot, /flexrom, and /recovery partition. It's really easy to do, and you'll help yourself and others when they get into trouble.
Can I help?
Answer all of the following questions. If at one point the answer is "Sorry, you can't help", well... You can't help
Is your device unlocked and rooted? Yes - You can help! / No - You can still help, but you need to unlock and root your device.
Do you have the original Acer ROM installed on your device? Yes - You can help! / No - Sorry, you can't help
Have you received the latest OTA updates for your device? Yes - You can help! / No - You can help as well!
Have you removed any apps or files from the /system or /flexrom partition? Yes - Sorry, you can't help / No - You can help!
Have you installed a custom recovery image? Yes - You can still help, as long as everything else is still original / No - You can help!
Okay, so I can help, now what?
If you can and are willing to help (remember, it could save your own ass one day), follow the instructions below. If you get stuck or simply don't know where to start but are willing to help, let us know in this thread and I'm sure we can all help eachother out.
This will not gather any personal data from you. Personal data is stored on the /data partition, which we don't need, so: No worries!
Root your device, if you haven't already.
Connect your tablet to your computer via ADB
Type the following command: adb shell. You are now logged into your tablet. You can exit at any time by typing exit and hitting ENTER.
Type the following command: dd if=/dev/block/mmcblk0p2 of=/sdcard/boot.img. This will copy your /boot partition to a file called boot.img on your internal storage. This one will be fast, it only has about 8MB to copy.
This step can be skipped if you have a custom recovery! Type the following command: dd if=/dev/block/mmcblk0p1 of=/sdcard/recovery.img. This will copy your /recovery partition to a file called recovery.img on your internal storage. This one will be fast as well, it only has about 6MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img. This will copy your /system partition to a file called system.img on your internal storage. This one will take a bit longer, it has about 360MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img. This will copy your /flexrom partition to a file called flexrom.img on your internal storage. This one will take a bit longer as well, it has about 360MB to copy.
Type exit to exit the ADB shell. Copy the four .img files from your tablet (internal storage) to your computer. You might have to reboot your tablet if the files don't show up.
ZIP or RAR these files, and upload them somewhere. If you can't find a place to store them: send me a private message or reply in this thread and we'll arrange something else. If you have uploaded the files somewhere: again, send me a private message or reply in this thread.
So now what?
When I receive your files, I will package them into an update.zip that can be flashed from custom recoveries. This will then restore everything (including the custom recovery) to factory state, which can help you in getting your device back to stock.
What versions do you have already?
Acer_AV041_A510_1.044.00_WW_GEN1 (download links will follow shortly)
Acer_AV041_A510_1.098.00_EMEA_CUS1 (download links will follow shortly)
Acer_AV041_A510_1.099.00_EMEA_DE (download links will follow shortly)

The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.

i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB

What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.

scorpio16v said:
The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.
Click to expand...
Click to collapse
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.

scae said:
What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.
Click to expand...
Click to collapse
Then it's of no use, unless you have a backup of your pre-installed apps. Removing apps from the /system or /flexrom partition is not recommended, and you gain nothing by it: You only gain space on read-only filesystems which you won't use in 99% of situations, and you've now broken OTA's for yourself as well, as OTA's will only install when apps are present unless you start modifying OTA files.
The 'correct' way to get rid of pre-installed apps is simply freezing them, either from the settings menu or with an app like Titanium Backup. This will make it seem like they're not there (so they don't use resources at all), but the APKs don't get removed.
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.

skymario said:
i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB
Click to expand...
Click to collapse
Do you have ADB or the Android SDK installed?

NoThrills said:
Do you have ADB or the Android SDK installed?
Click to expand...
Click to collapse
I just learned ADB, n successful install ur CWM, later will try to dump my stock Rom to u.
My stock Rom version 1.073 ww gen1

does it matter if the system apps have been frozen or do they need to be unfrozen first?

I have flashed that remove stock recovery mod so the stock rom doesn't keep overwriting cwm on reboot. Does that disqualify me? If not I'll dump my rom for you when I get home.
I'm on this rom version:
ro.build.pandora.id=Acer_AV041_A510_RV28RC04_PA_CUS1
ro.build.flexrom.id=Acer_AV041_A510_1.076.00_PA_CUS1

I unlocked bootloader,rooted,installed cwm then backed up my stock rom.Could i restore my stock rom then be able to send you those fills
and return to total stock.

NoThrills said:
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.
Click to expand...
Click to collapse
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
i have a a511 too with Acer_AV041_A511_1.028.00.EMEA_DE and can help with testing or something else

I have Acer AV041_A510_1.079.00_PA_CA. (Canada)
I have not done a thing to it because it is a replacement for the Galaxy Note I bricked trying to upgrade from GB to ICS, too early.
I might try again if I was sure I could get back to where I am, using your process.
I assume that your Root link is comprehensive but I also need reassurance on how to ADB.
[email protected]
Sent from my A510

blgblade said:
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
Click to expand...
Click to collapse
No, as I understand, the only working methode to root the a511 is to bootloader unlock, flash the custom recovery and then the root.zip.
Maybe I'm wrong and there is another working way to root the device ?
The problem is simply, that we lost the stock recovery before we have a backup from it.
If we have another root way for a511, the backup of stock firmware is done in a few minutes and from this point we can test the a511 custom recovery from NoThrills.

To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
In theory: To test, one could simply overwrite the stock recovery with my Recovery (not the other ones, they will brick your device) and then when you reboot, your device will overwrite the recovery with the stock one again. So you really don't need a backup of the recovery partition.
As long as you don't let your device fully boot (so, stay in recovery) there's plenty of time to test if the recovery works or not. If it doesn't, simply reset your device and it will flash back the original recovery (again: provided there is a install-recovery.sh in your /system partition).
So again, if anyone is willing to test, let me know

NoThrills said:
To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
Click to expand...
Click to collapse
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.

NoThrills said:
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.
Click to expand...
Click to collapse
Ah damn, I did back them up via titanium but it doesn't seem to want to restore them - it just sits there say restoring app.

scorpio16v said:
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.
Click to expand...
Click to collapse
Yeah, I meant /system/etc... That's weird, I'd figure Acer would use the same system on the A511... Let me check one of the leaked ROMs...

Hello,
I have an stock Acer_AV041_A510_1.098.00_EMEA_CUS1, there we go for the files
Host file is not the stock version, it was edited by AdAway.
Can you make a version without recovery overwritting ?
I thinks a lot of people want to try some roms... just for testing...
Acer_AV041_A510_1.098.00_EMEA_CUS1 boot && system && flexroom:
http :// dl.free.fr/jDEmTNSD4
Have Fun

Hello,
I have the same rom without root or unlocked bootloader or moded recovery so if the above on does not make it I'll upload mine.
Sent from my A510 using xda app-developers app

[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

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

In context of Oneplus 7 can anyone good soul explain me:

In context of Oneplus 7 can anyone good soul explain me:
1. What exactly are we doing when we r using twrp?
2. What exactly we are doing when rooting?
3. Can we root without twrp?
4. Can we twrp without root
5. What is this active inactive slot
Pls could someone explain to me as a starting point

Hi,
More simply for you if you watch video on Youtube to have all your answers commented and explained...

sunandoghosh said:
In context of Oneplus 7 can anyone good soul explain me:
1. What exactly are we doing when we r using twrp?
2. What exactly we are doing when rooting?
3. Can we root without twrp?
4. Can we twrp without root
5. What is this active inactive slot
Pls could someone explain to me as a starting point
Click to expand...
Click to collapse
Well, let's answer each part:
1. When we use twrp, we're just using a different image file, which will load every custom config made by twrp team, so that we're able to do more things like install .zip or .img files into some defined partition of the device (that's just one example of the capabilities of twrp)
2. Actually the act of rooting is not the same as installing an root manager. Rooting, means we are giving the user, the capability of doing stuffs a common user couldn't. Like, installing apps as a system app, uninstalling system apps etc. I don't have all the knowledge on that matters, but I think that when you flash a root.zip file, you are adding a new binary file with some settings which will create the sudo(admin) user. When we use the root manager, we are just seeing an UI to manage which app will actually get the permission of root.
3. Yes, surely we can. All you need is to push the boot.img from your device with some adb commands(you can find it easily on XDA), install the Magisk Manager, and use the install button to patch boot image. After the process, you will se a patched_boot.img on your device storage, just put it on your PC, boot to fastboot, and fastboot boot the patched boot.img, now you can install the real magisk using the Magisk manager. There's a better tutorial here on XDA for that
4. Yes, twrp is 100% independent of root, the point is that, you will still need unlocking the BL. Also, I don't see a point to use twrp but not root, because you will not be able to do many things, like use some bank apps, play some games, use netflix etc...
5. Now the android is split in 2 slots, A and B. Imagine that when you buy the device, you have the same build (e.g. oos 10.0.5) on both slots, but you'll boot only to slot A. When you install an update, it will be installed on slot B, so that you will be forced to boot to slot B next time and all next boots (this can be reversed I think, using TWRP). So, the active slot is the one you're using, the other is inactive. When you install any kind of OTA, it will always be installed to the inactive slot, and the one you are using, will be kept as it was before the update. Remember it does not change your storage.
I don't know if that's all, and if anything's wrong, pls tell me

How To Guide Installing a custom recovery, and disabling encryption in the system.

Hello everyone.
If you want to have a recovery with the ability to backup/restore, this instruction is for you.
Here are recovery, while they do not know how to encryption of data section (I hope we will have such ones sometime).Yes, recovery already patched by magisk 25.2
Download the patch, copy it to the SD card (if you have it) or to a USB flash drive, for firmware by otg.
We set the recovery in fastboot mode with the command:
fastboot flash boot (recovery name).img
We load into the recovery, flash the patch, and make FORMAT DATA.
Attention!!!This will delete all your settings and installed programs, including deleting everything from the internal memory.
After that, we boot into the system, configure and "rejoice", now the recovery will see data and, accordingly, internal memory.
And yes, if you have a security thing, this procedure disables the encryption of your data
COMPLETELY, THAT IS, COMPLETELY.
Oh, I forgot, although I think it's clear by the name of the recovery, they (recovery) are designed for firmware on Android 12.
Download files:
RECOVERY

Guys, one jamb got out here, my system has been transferred to RW, and I checked the script on such a system. As it turned out, the script does not work on the stock system. So, in order for it to work normally, you need to first transfer the system to RW

Any chance to explain step by step?

reosm said:
Any chance to explain step by step?
Click to expand...
Click to collapse
What exactly?
In the post everything is written as to put.

There are 2 img in the recovery file, which one will be loaded before or after

reosm said:
There are 2 img in the recovery file, which one will be loaded before or after
Click to expand...
Click to collapse
one is TWRP recovery and the other is Orange Fox recovery, choose which one you want to use, just flash one of them.

Hey does twrp/orangefox actually work on this phone. I've heard that those are currently under development. And does flashing these .img require wipe data or can they work with sd card or OTG?

Soma Das said:
Hey does twrp/orangefox actually work on this phone. I've heard that those are currently under development. And does flashing these .img require wipe data or can they work with sd card or OTG?
Click to expand...
Click to collapse
Recovery can work with both sd and otg. While they cannot decrypt the data, but if you transfer the system to RW, and flash the patch to disable encryption in the system, then everyone will see the recovery.

Who has a system in RO, you can use these, checked, it also works
[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Universal Disable Force Encryption for RO and RW "NEO STABLE"
Disable Force Encryption NEO Do you all know what DFE is? no? Anyway. Basically, your device has an encrypted data section "/data" by default. Let's look at the advantages of google's solution that we will lose after disabling encryption: -...
forum.xda-developers.com

arraki said:
Recovery can work with both sd and otg. While they cannot decrypt the data, but if you transfer the system to RW, and flash the patch to disable encryption in the system, then everyone will see the recovery.
Click to expand...
Click to collapse
Can it backup anything such as boot.img, vendor etc?

Soma Das said:
Can it backup anything such as boot.img, vendor etc?
Click to expand...
Click to collapse
Probably you can, but why. A backup of the datа section is enough for normal recovery. Of course, you can also make a backup of the super section if you changed something in it.

arraki said:
Probably you can, but why. A backup of the datа section is enough for normal recovery. Of course, you can also make a backup of the super section if you changed something in it.
Click to expand...
Click to collapse
Do I need to flash disable dm Verity?

Soma Das said:
Do I need to flash disable dm Verity?
Click to expand...
Click to collapse
In the first post, everything is written.

does it work for Mediatek cpu install on the Note 11 pro plus 5g?

Christ_soyo said:
does it work for Mediatek cpu install on the Note 11 pro plus 5g?
Click to expand...
Click to collapse
MediaTek chip on is Redmi note 11 pro. It wilont work and you will get soft brick.

Christ_soyo said:
does it work for Mediatek cpu install on the Note 11 pro plus 5g?
Click to expand...
Click to collapse
What exactly works?

Do we need to unlock the bootloader firtst before we flash the recovery, right?

derjango said:
Do we need to unlock the bootloader firtst before we flash the recovery, right?
Click to expand...
Click to collapse
Of course

After using this patch my device doesn't know how to be case sensitive, which makes some apps have weird errors with read and write functions

nimade2333 said:
After using this patch my device doesn't know how to be case sensitive, which makes some apps have weird errors with read and write functions
Click to expand...
Click to collapse
This is clearly not because of the patch, I have put it on for a long time, and there are no problems. Yes, and he only disables encryption in the system, how can he influence this.