Database Users

Encryption doesn't work on rooted Moto G4?

Hi guys, this is my first post here
I have a Moto G4 that I rooted recently and flashed with good ROMs for testing, but in all ROMs, Encryption doesn't work.
In all times that I tried, I go on Settings > Encrypt and start, but always remaining 00:00 for a lot or hours and when I restart phone, I enter with password and display this error.
Decryption unsuccessful. The password you entered is correct but unfortunately your data is corrupt
Click to expand...
Click to collapse
Then I have a question, encryption doesn't work on rooted Moto G4? If yes, have other option to protect my data on rooted device?
Thanks.

joubertredrat said:
Hi guys, this is my first post here
I have a Moto G4 that I rooted recently and flashed with good ROMs for testing, but in all ROMs, Encryption doesn't work.
In all times that I tried, I go on Settings > Encrypt and start, but always remaining 00:00 for a lot or hours and when I restart phone, I enter with password and display this error.
Then I have a question, encryption doesn't work on rooted Moto G4? If yes, have other option to protect my data on rooted device?
Thanks.
Click to expand...
Click to collapse
In my knowledge, encryption will not work on rooted phones. But there is a workaround for this. You can root your phone after the phone is fully encrypted. To root your phone after it is encrypted, you can click adb sideload on TWRP and through the terminal on your pc, you can sideload phh's superuser. Reboot your phone and you have a working, encrypted phone with root installed. I didn't try this, but I think, it will work.

@stkpxl thanks for the help, but I have a question.
Will be possible to make encryption with SD card as extended internal storage? Thanks

@stkpxl I'm trying to flash LineageOS after flash Magisk but response error 7. What wrong about this? Thanks.

stkpxl said:
You flash Lineage before flashing Magisk.
Click to expand...
Click to collapse
I really trying, but isn't working, look my steps.
- Flash Stock ROM like this post http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/
- Run stock, setup first run, format sd and define as internal storage
- Flash recovery twrp-3.0.3-n4-athene_shreps.img
- Run twrp
- Install ElementalX-G4-1.04-LOS.zip
- Run stock, set password and encryption device
- Smartphone restart and stock encrypt device
- Run stock again, password working fine
- Run twrp, twrp ask for encrytion password, I put and enter on twrp normally
- Install lineage-14.1-20170313-nightly-athene-signed.zip without wipe
* Fail on this point
Code:
Installing zip file '/path/to/lineage-14.1-20170313-nightly-athene-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: <a big number>
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updata process ended with ERROR: 7
Error installing zip file /path/to/lineage-14.1-20170313-nightly-athene-signed.zip
Updating partition details...
...done
This problem display only If I encrypt device on stock ROM, when I flash without encrytion, twrp flash LineageOS normally.

Seems like full disc encryption is not working in general. Its reported https://jira.lineageos.org/browse/BUGBASH-253
I am also quite sure that this bug was already in cyanogenmod and also reported there.

tonymarschall- said:
Seems like full disc encryption is not working in general. Its reported https://jira.lineageos.org/browse/BUGBASH-253
I am also quite sure that this bug was already in cyanogenmod and also reported there.
Click to expand...
Click to collapse
Thanks for reply @tonymarschall
Are you know any custom ROM that encryption is working for me test here? Thanks

joubertredrat said:
Are you know any custom ROM that encryption is working for me test here? Thanks
Click to expand...
Click to collapse
No, I am sorry and searching by myself. I hope that one day it will be official supported. Maybe you can give the issue an upvote.

Hi guys.
A bug related about encryption fail was solved and encryption is working fine on lineage-14.1-20170501-nightly-athene-signed.zip
https://jira.lineageos.org/browse/BUGBASH-253

Foolproof way for OTA-update with Magisk installed

Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?

Tiemichael said:
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Click to expand...
Click to collapse
Hey!
Following the official Magisk procedure works, at least for me.
You just have to be careful to restore backup image before starting the OTA download and installing to second slot (After OTA) before rebooting.
Reading this thread:
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
I found there’s a lot of confusion (I was confused also and made a few mistakes), but my conclusions are:
- That method is to be used just ONCE in order to gain root, and not every month.
- Always try to use your own patched image if you have the opportunity
- You have to use “fastboot BOOT” and not “fastboot FLASH” when first rooting, otherwise you won’t be able to restore boot image and OTA will fail
- Follow official procedure as a cooking recipe
If you don’t want to root using a patched boot image, you can also use latest TWRP (As of now latest is recovery-3.2.1-2-oreo.img)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
And boot to TWRP image in order to install Magisk ZIP (did this yesterday and also worked), but the update via OTA method should be the same.
Best regards.

Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me

Keeping phone to stock and not rooting for only one OTA in more than a month? I think its not worth it!!
I always root my phone and when OTA arrives i just flash twrp version of it and root it again ?

Siebenmik said:
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Click to expand...
Click to collapse
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?

I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..

_mysiak_ said:
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
Click to expand...
Click to collapse
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?

Tiemichael said:
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Click to expand...
Click to collapse
Yes, exactly. I didn't have any issue with OTA installation yet.

Tiemichael said:
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
Click to expand...
Click to collapse
I forgot saying that using restore image in magisk didn't work. Even though I didn't flash the patched boot.

https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where to enable secured startup?

Skeuomorphic said:
Where to enable secured startup?
Click to expand...
Click to collapse
create a pattern from security setting and it will prompt to enable secure startup.. just press yes..

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Finally a different answer, I have secure boot disabled maybe this is the reason ending into bootloop for past 3 montly security updates. Will try this for May update.

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....

Tiemichael said:
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Click to expand...
Click to collapse
Settings->Security & Location->Screen lock->Pattern

This what was working for me just now:
Detailed steps performed 20.4.2018:
Backup Titanium
Backup Magisk Modules
Switch on Secured Booting (e.g. Pin) => not same a normal pin!
Open Magisk
Uninstall Magisk​
Restore Images​
Start OTA update
Downlowd​
Step1​
Step2​
Go Back to Magisk
Install to 2nd slot​
Reboot​
It was working ... very easy!

I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.

I didn't update my phone for a very long time, then I decided to finally go for the latest MIUI on my Mi Max and basically I flashed full new ROM via fastboot & MiPhone.
You can see detailed description here: https://forum.xda-developers.com/showpost.php?p=78050983&postcount=41
I think it should work with other Xiaomi phones too but please correct me if I'm wrong
The only difference is that I had SuperSu before, but maybe with Magisk it's the same to do - also correct me if i'm wrong

quetzalcoatl2435 said:
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
Click to expand...
Click to collapse
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
H.A.L. 9000 said:
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse

freekarol said:
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Click to expand...
Click to collapse
Yeah, but you need a PC for this. If I need access to a PC every time there's an OTA update, might as well download and flash a full ROM. ?
Official Magisk OTA guide works anytime anywhere, no PC needed.

Question about custom recoveries and bootloader relocking

Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?

Tsun_Pooka said:
So my question is, can you lock the bootloader with TWRP installed and still access the system?
Click to expand...
Click to collapse
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).

Tsun_Pooka said:
Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?
Click to expand...
Click to collapse
How you unlock the bootloader?

bozka1 said:
Unfortunately, it's impossible... If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
Thanks for the tips! By the way, what is dload? If it's a website, I cant find it (the fact that dload is short of "download" doesn't really help). I am now in need of that full-stock ROM.

Tsun_Pooka said:
By the way, what is dload?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/help/formatting-dload-method-t3815949/page2

Whew. I got the bootloader AND FRP locked on me, and now I don't have a usable system. So now, I have to rely on eRecovery to download a 3GBs package and hope all things go well...the problem is, I'd need to find a place that offers fast WiFi...my internet is terrible.
EDIT: Got the system back up thanks to eRecovery. I'm not sure if I want to root or install a custom recovery on the Lite. I've realized even more that I should cherish my older phone, my Samsung Galaxy Win. At least this one isn't complicated or protected by Fort KNOX.

When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.

usman400 said:
When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.
Click to expand...
Click to collapse
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.

Tsun_Pooka said:
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.
Click to expand...
Click to collapse
I am certainly not up to what u r indicating so cant suggest a solution, earlier in my reply, I was only
indicating my experience with custom ROMs. I havent yet come across a single custom ROM for mate 10
lite that has no problems. Earlier Galaxy S4 Mini, there was custom ROM which was awsome, not a single issue
But for mate 10 lite camera problem is most common. Stock camera app often doesnt work or partially
works, restart of the app etc. You can install open camera, but it does not give u best shots, and filters.
Other issues are already discussed in every custom ROM thread, so I had to come back to Stock ROM
with magisk to remove any system apps that I dont need plus other goodies that magisk offers u (modules)

Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?

Tsun_Pooka said:
Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?
Click to expand...
Click to collapse
Flash the stock erecovery whenever i root my phone i always stick with stock recovery not custom recovery(TWRP)
Theres another method to flash the stock recovery but... This is my method on how to flash stock recovery(erecovery)
PC ONLY!!! and MAKE SURE TO HAVE UNLOCKED BOOTLOADER AND FRP!!!
1.Download MultiTool from https://pro-teammt.ru/en/multi-tool-huawei-honor/
2.Make sure to install Huawei driver from the MultiTool
3.Download This File i provided Here https://mega.nz/#!nZxl2AwZ!6qRIIRbLK4Ub80dPMae4HQQ7e-O49_f2BZ8PhbuZTYM
4.Go to MultiTool and go to recovey Section an select file that you download earlier
5.Make sure to CONNECT USB CABLE TO YOR PC now Reboot your device into Bootloader mode by PRESSING VOLUME DOWN BUTTON and CONNECT THE CABLE TO YOUR PHONE
6.Now on the MultiTool click on Flash Recovery_Ramdisk andlet it flash...,
7.Now You Have The Stock Recovery Installed Now You Can Install Offical Firmware Update On Your Phone
8.All Done
I Hope I Help You

I will follow your guide later today or tomorrow! Thank you for the help!

Tsun_Pooka said:
I will follow your guide later today or tomorrow! Thank you for the help!
Click to expand...
Click to collapse
Np

LoneWolfz said:
Np
Click to expand...
Click to collapse
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
Code:
Software install failed!
Failed to check the update files
Please download the package again
> Reboot system now
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...

Tsun_Pooka said:
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...
Click to expand...
Click to collapse
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it

bozka1 said:
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
But can you unlock the bootloader later on with the same code if you wanted or is this it?

Deathecho said:
But can you unlock the bootloader later on with the same code if you wanted or is this it?
Click to expand...
Click to collapse
Yes you can use the same unlock code again.

LoneWolfz said:
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it
Click to expand...
Click to collapse
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.

Tsun_Pooka said:
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.
Click to expand...
Click to collapse
Np

[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!

From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !

Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number

I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch

Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!

Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-

It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse

Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.

finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed

Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well

Magisk 23 to 24 ruined

Hi!
I had Magisk v23 working fine with Magisk hide but then I upgraded to v24. Magisk app successfully installed and shows Magisk not present. And when I try to DirectInstall Magisk, I get verification failed error. Attached both screenshots.
Now, I have installed and confirm TWRP is working but do not know how to make Magisk working again and it seems it gonna be a wipe. Any help appreciated.

[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html

Issue is that on my other phone, Sony Xperia XZ Premium G8142, the same in-app upgrade weas successful with out any issues. I lost Magisk Hide but an extension recovered that function. But it all went haywire on this S8

xabu said:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
This guide expects me to know what ROM I have. Thing is, I do not know what my device really is. It's running a ROM that I do not recognize (My post: https://forum.xda-developers.com/t/...l-and-odin-cannot-flash.4372669/post-86069051). I do not have the sources for it so I cannot acquire the required two files. Ramdisk is Yes as per my screenshot but I cannot follow the rest of the guide without the files.

try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .

xabu said:
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
Click to expand...
Click to collapse
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.

Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!

Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Maybe only European ?

xabu said:
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Click to expand...
Click to collapse
I just TWRP it. It went smoothly. I love a new ROM but need to know what device is it.
Download mode say it is SM-G950N
Android say it is SM-950FD
Both SIM slots have the same IMEI number. This part is beyond my understanding.
I have Odin and know the basics. Just need to find a ROM I can go for: What official I should flash first and what custom. Any recommendation?

As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.

xabu said:
Maybe only European ?
Click to expand...
Click to collapse
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Just found out:The "famous" secret codes only work on stock based ROMs ¯\_( ͡❛ ͜ʖ ͡❛)_/¯

xabu said:
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
Click to expand...
Click to collapse
I have been trying to make the total backup but I do not see any boot.img:
And I do not see the file in the Device/TWRP/Backups:
Again, I must be missing something obvious. And as per the Magisk guide, I need the boot.img

magisk 24 is ****, it's bricking MediaTek powered Samsung phones

Boot.img from TWRP backup
In clockworkmod kernel and recovery are backed up as IMGs. But in TWRP it is boot.emmc.win Anybody know how to convert jt to boot.img? Help will be really appereciated. Sent from my HTC One X using xda app-developers app
forum.xda-developers.com
I must tell you that my custom rom for the s7 gives me the boot.img as the first file as soon as i open the zip.
the boot.img can also be reached by downloading the right stock rom for your phone. In that case it is the best practice to patch the whole
AP file by using Magisk.