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.
Related
Hi, you can see my question.
I've try wipe, but only data works. And no change.
I've try to réinstall the custom rom, you can see result.
Ttry to flash stock rom with odin, odin failed.
and try to réinitialise with smart switch ( he say me i havent tow slot for sim, i know). And ... nothing change.
The device has been already root, and i've already change for this custom rom with no problem.
Thanks for your help.
Edit: with format data after wipe data and after reboot on twrp, no red line, i've install the rom. good : i've the rom, bad : the problem is come back.
Just for to be sur, this screenshoot is just a example. Other installation make me the same error.
This rom work really good and other people haven't any problems.
Send me the kernel and I disable /data ecncrypting for you
DThrawn said:
Hi, you can see my question.
I've try wipe, but only data works. And no change.
I've try to réinstall the custom rom, you can see result.
Ttry to flash stock rom with odin, odin failed.
and try to réinitialise with smart switch ( he say me i havent tow slot for sim, i know). And ... nothing change.
The device has been already root, and i've already change for this custom rom with no problem.
Thanks for your help.
Edit: with format data after wipe data and after reboot on twrp, no red line, i've install the rom. good : i've the rom, bad : the problem is come back.
Click to expand...
Click to collapse
do't worry it is normal i explain you
when you format with twr the data is readable
and the first time starting system Samsung encrypt the file so txr can't mount again data
but don't care about it
DThrawn said:
Edit: with format data after wipe data and after reboot on twrp, no red line, i've install the rom. good : i've the rom, bad : the problem is come back.
Click to expand...
Click to collapse
It's all because kernel has encrypted /data and data encrypts after a reboot. Some changes in the kernel solve your problem. Data will mount always after some changes in the kernel
maxx35000 said:
do't worry it is normal i explain you
when you format with twr the data is readable
and the first time starting system Samsung encrypt the file so txr can't mount again data
but don't care about it
Click to expand...
Click to collapse
Forgetten said:
It's all because kernel has encrypted /data and data encrypts after a reboot. Some changes in the kernel solve your problem. Data will mount always after some changes in the kernel
Click to expand...
Click to collapse
Ok, I understand more why it's all my recovery is down. my device work good also with what you said i'm more quiet.
But why reinitialisation with switch, let the same problem. The kernel is not reinitialised to ?
I've try to modify selinux permissions before to install a sound mod and create an folder init.d. Is it possible the problem stay cause that?
DThrawn said:
Ok, I understand more why it's all my recovery is down. my device work good also with what you said i'm more quiet.
But why reinitialisation with switch, let the same problem. The kernel is not reinitialised to ?
I've try to modify selinux permissions before to install a sound mod and create an folder init.d. Is it possible the problem stay cause that?
Click to expand...
Click to collapse
I don't sure about that but you should mount your /data using patched kernel. Send it to pm and I patch them to mount data fully
Forgetten said:
I don't sure about that but you should mount your /data using patched kernel. Send it to pm and I patch them to mount data fully
Click to expand...
Click to collapse
I'm a old beginner, I don't know where is the kernel and I don't know if it's sur to give mine cause i don't know what information of my device is in.
I appreciate your help but i can't give anything what a I don't know.
DThrawn said:
I'm a old beginner, I don't know where is the kernel and I don't know if it's sur to give mine cause i don't know what information of my device is in.
I appreciate your help but i can't give anything what a I don't know.
Click to expand...
Click to collapse
OK. Say. Which ROM do you use?
Forgetten said:
OK. Say. Which ROM do you use?
Click to expand...
Click to collapse
I use the evo-grace V1.2 J7 2016, but I ve never had problem before trying install sound mod with modification of selinux permission.
Unmount data always but not important, but some install, wipe or backup impossible it's new.
Flash before formatting data.
https://www.androidfilehost.com/?fid=24591000424951049
ashyx said:
Flash before formatting data.
https://www.androidfilehost.com/?fid=24591000424951049
Click to expand...
Click to collapse
Thanks, work realy fine. no red line at all.
Also i lose root and the problem come back when i try to reinstall the rom evo-grace, cause she's rooted and she has its own no encrypted file, i think.
DThrawn said:
Thanks, work realy fine. no red line at all.
Also i lose root and the problem come back when i try to reinstall the rom evo-grace, cause she's rooted and she has its own no encrypted file, i think.
Click to expand...
Click to collapse
When you flash anything that modifies or replaces the boot partition you need to reflash the patch afterwards or the data partition will be re-encrypted.
ashyx said:
When you flash anything that modifies or replaces the boot partition you need to reflash the patch afterwards or the data partition will re-encrypted.
Click to expand...
Click to collapse
Yes, i've can make some backup and install like that. It's help me. And now i've install permanetly the rom of max35000, , he have make some good modification. Problem solved with help of you to.
Thanks for have take a time for look that.
Forgetten said:
Send me the kernel and I disable /data ecncrypting for you
Click to expand...
Click to collapse
Hi my bro
Please help me
How can i make disablr / data ecncrypting ??
I have j710f frp on with pattern
Can i open it without losing data ??
---------- Post added at 10:09 PM ---------- Previous post was at 10:00 PM ----------
How can i make a kenel to disable data ecncrypting ??
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
Hi,
Finally I had time to finish my work on Xcover 4. I couldn't disable ForceEncryption by any flashable tool so I prepared 2 version of firmware (Oreo and Pie), both prerooted (Magisk) and free from Force Encryption. Everything except boot.img left untouched, both ROMs are BTU so no brand.
Just flash it with Odin 3.13.3. I recommend to flash CSC_BTU instead of HOME_CSC_BTU. HOME BTU should work as well but then probably You gonna have to format data with TWRP. CSC_BTU is already tested and there are no problems with Encryption.
After flashing just install Lastest Magisk Manager. SafetyNet Passed.
Oreo: G390FXXU4BSB3_BTU_G390FBTU4BSC1_Patched_By_Chamelleon
Code:
https://mega.nz/#!ONoFTIhD!rBOhDR0j874zpyeLiDVwfwOcodRi5OhdxyF0ZTRMslE
PIE: G390FXXU4CSF9_BTU_G390FBTU4CSFA_Patched_by_Chamelleon
Code:
https://mega.nz/#!XBhnRCCY!_IOOtXcLsGZQfVY17JD4YxxzaAWJqy2NoxVSrsJRs5M
If You need TWRP (not necessary to flash this ROMs) flash this version:
TWRP: TWRP-3.1.1_SM-G390F_by_nemo-nemo
Code:
https://mega.nz/#!DIo1SSBT!w4dPPAF3BEcfQmsy7mANO33Lb5Gj4jzDkrrPfbH56uo
Working on both versions, Oreo and Pie. I didn't test backup and recovery options but flashing is working on both. ADB and MTP are not working.
To remove Security Log Agent notifications use SecurityLogAgent Disable. It will disable this annoying app completely.
Hello!
Can you explain because i would like only to root my phone in oreo 8.1 without losing apps and data. Is it possible with your method?
thank you for your answer.
Would anyone happen to know if I can use TWRP for SM-G390F's on SM-G390W's? (the only differences I know of between them are the supported LTE frequencies)
You can try to flash it, just backup your data and if something goes wrong just flash it with back with stock firmware.
Updated main thread
Hi mates
very interesting matter. Will like to make it from a ubuntu 18.04 system? Did someone had tried it ?
Yea, it's a normal ROM so you can flash it with Heimdal.
Chamelleon said:
Yea, it's a normal ROM so you can flash it with Heimdal.
Click to expand...
Click to collapse
thank you C for this fast answer .
Here is the second point :
IS this rom free from google , I mean enough
And the third
any visible amelioration from the XCOV 2 Model in battery standing . I do not care about photos for my purpose .
Only memory, increased by SD, and lasting time
It's completely stock rom without any modifications except integrated Magisk and disabled force encryption. Rest is untouched.
I don't understand what file I should use to flash with Odin.. in the link you posted sends to a download of a zip file of almost 2gb in which there are many files, so from those files which one should I set in Odin?
Flash it like any other stock ROM:
BL file in BL
AP file in AP
CP file in CP
CSC_BTU file in CSC
Everything works great:]
Thanks man.
Hi Chamelleon and thanks for all the effort you've made already!
I successfully flashed the Pie variant of the two ROMs and got it to work. However, turned out that in an app that I'm developing, for some reason, when my device is equipped with G390FXXU4CSF9_BTU_G390FBTU4CSFA, the app doesn't behave in the same way as when G390FXXU4CSF9_ G390FXEO4CSFA has been installed. That's why I would like to be able to root the XEO-version of the firmware. Moreover, there will be many other non-rooted devices equipped with the XEO-version using the app in the near future.
Having flashed my device with G390FXXU4CSF9_ G390FXEO4CSFA, I tried installing the version of TWRP you have provided but I can't figure out how to install Magisk from there. By default, TWRP can't find the Magisk zip-file that I push onto the device. I tried formatting data, as per this post. The post lead me to believe that the files could be found after formatting but even though there were now plenty of TWRP-related folders, I couldn't find the zip. And as ADB and MTP don't seem to work in recovery mode, I'm unable to get the zip file on board after formatting. Booting to system doesn't work either after allowing modifications for TWRP, which might be due to dm-verity preventing boot, but franky I don't understand much of that topic.
You mentioned that you couldn't disable Force Encryption with any flashable tool. Is that the reason why TWRP (or any other tool) couldn't reach the zip file for Magisk?
This is the first time I've attempted rooting a phone so my knowledge regarding the topic is pretty basic.
So I suppose preparing a prerooted and Force Encryption free version of the firmware might be a possibility? I have no idea how to patch a ROM though. Any advice on how to proceed?
Hi, I had no time to play with this during Christmas. If you send me your boot.img I can modify it for you. If You just flash magisk with TWRP it will root your phone but after first reboot whole data partition will be encrypted again and you wont be able to flash anything with twrp or modify data partition without full wipe. For some unknown reason this and probably more Samsung models have different structure of files responsible for encryption and because of this none of pre-made patches are working. Only manual kernel modification can safe from encryption, at least for now.
I'm not a developer so I don't know how to prepare patch for this to allow anyone to flash it, I just found few lines of code in kernel You need to modify to disable encryption.
Chamelleon said:
Hi, I had no time to play with this during Christmas. If you send me your boot.img I can modify it for you. If You just flash magisk with TWRP it will root your phone but after first reboot whole data partition will be encrypted again and you wont be able to flash anything with twrp or modify data partition without full wipe. For some unknown reason this and probably more Samsung models have different structure of files responsible for encryption and because of this none of pre-made patches are working. Only manual kernel modification can safe from encryption, at least for now.
I'm not a developer so I don't know how to prepare patch for this to allow anyone to flash it, I just found few lines of code in kernel You need to modify to disable encryption.
Click to expand...
Click to collapse
Hi, I really appreciate the help!
I sent the boot.img to your paypal donation email. Let me know if you want me to send it to you some other way.
How to flash firmware on linux?
I know that i have to use heimdall but how to load these files into the program because filenames say basically nothing to me.
Thanks in advance.
Also does it delete user data?
SpurguX said:
Hi, I really appreciate the help!
I sent the boot.img to your paypal donation email. Let me know if you want me to send it to you some other way.
Click to expand...
Click to collapse
1. Flash clean ROM, same as boot you send me)
2. Enable OEM Unlock in Developer settings
3. Flash patched boot with Odin as AP/PDA.
4. Install Magisk Manager app
5. Install TWRP and format data partition, option where you need to type "YES"
6. Reboot system and then back to TWRP. If you can mount data and there are no errors it's done.
AndroidBroker said:
How to flash firmware on linux?
I know that i have to use heimdall but how to load these files into the program because filenames say basically nothing to me.
Thanks in advance.
Also does it delete user data?
Click to expand...
Click to collapse
Sorry but I never had a chance to use Heimdall. You can't dirty flash this because when your phone is encrypted and you can't replace kernel corrupting data.
But do I lose my data(Apps settings etc.)?
I'm OK with setting everything up back ,but it would be cool if it kept data.
(I'm going to use other computer that has windows on it btw, and I'm going to flash it with odin)
If your data partition is encrypted you gonna corrupt it by changing kernel. It means You wont be able to access, so yes, you will loose it.
What you mean by encryption some option in the Android or what?
If that's what you mean I haven't set up anything like this
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.
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