Database Users

Cannot install magisk v12.0[SOLVED]

So I installed magisk v12 via normal procedure; downloaded then installed from recovery, and the phone didn't boot after. Did not even get past the samsung j5 logo to the bootanimation. I've tried uninstalling SuperSu and then install magisk but didn't help. I "updated" the same rom I was using already and I can use my phone but I would like to install magisk. Anyone?
Phone:J500FN (2015)
Rom: Resurrection remix 5.8.3

Weird, never had problems installing Magisk, even on secondary roms (multirom) when all other fail.
Wipe system, and install the ROM then Magisk, in case that doesn't work make a clean install (wipe system, data, dalvik, cache) and install only the ROM and Magisk (no gapps), if everything is working then install gapps the rest (apps, restore backups etc...)
Your Magisk could be corrupted, try download again and install.

American_Jesus said:
Weird, never had problems installing Magisk, even on secondary roms (multirom) when all other fail.
Wipe system, and install the ROM then Magisk, in case that doesn't work make a clean install (wipe system, data, dalvik, cache) and install only the ROM and Magisk (no gapps), if everything is working then install gapps the rest (apps, restore backups etc...)
Your Magisk could be corrupted, try download again and install.
Click to expand...
Click to collapse
Wiping system will have no effect. Magisk nor supersu Install anything to system.
Restore the untouched boot.img then install Magisk only.
That should be all that is required.

ashyx said:
Wiping system will have no effect. Magisk nor supersu Install anything to system.
Restore the untouched boot.img then install Magisk only.
That should be all that is required.
Click to expand...
Click to collapse
I said to wipe system in case of something installed on system before causing the bootloop (BusyBox, viper4android, etc...). Wasn't referring to Magisk or SuperSu.
That's way I said to install Magisk before gapps, to leave system untouched so it can diagnose the problem.

American_Jesus said:
I said to wipe system in case of something installed on system before causing the bootloop (BusyBox, viper4android, etc...). Wasn't referring to Magisk or SuperSu.
That's way I said to install Magisk before gapps, to leave system untouched so it can diagnose the problem.
Click to expand...
Click to collapse
Well considering he stated that it wouldn't boot directly after installing Magisk, we can deduce that it was likely Magisk that caused the issue.

ashyx said:
Well considering he stated that it wouldn't boot directly after installing Magisk, we can deduce that it was likely Magisk that caused the issue.
Click to expand...
Click to collapse
I can't deduce anything, that's way I recommend to remove any modifications before install.
If you want to debug a problem start removing the variants.

Thanks guys! Problem solved. System wipe didn't do it. It was easier for me to clean install than restore the boot.img at the moment so that fixed it this time. Thank you again. ???

Want to encrypt data, can I still disable magisk module via TWRP?

Hi, thanks for all the information here.
Thanks to the guides, I was able to downgrade, backup TA, upgrade, build personal kernel, install twrp, working android pay.... everything is good. But:
I have tested out some modules for Magisk, two I wanted to use boot me in a boot loop/stuck on boot.
I can fix this using TWRP, I just use mount_magisk stored in my download on internal storage.
Then I disable the 'bad' module, by typing in the terminal: /magisk/<module folder>/disable
BUT!
This only works because my data is decrypted.
I want to encrypt my data.
It is true we still don't have a TWRP that supports our encryption?
If I encrypt, is there anyway to disable a bad magisk module?
I think magisk is stored in the boot, correct? So it is not in data, so it does not matter if data is encrypted or not?
I hope someone can clear up some of my worries.
Thanks

While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.

ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
Ok, so if I wanted to recover my system, I could just reflash boot (my kernel)?
I would have to install magisk again but that is ok.
But would I even be able to install magisk if my data is encrypted?
I think v12 can be installed if no access to /data, but v13 not?
Thanks

ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.

voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
I don't have an encrypted partition. Could anybody with encrypted partition try it?

voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
Yes it does say that, but it is talking about fw version 34.1.A.1.198 - which is marshmallow right?
From what I understand TWRP was fine with XC's encryption in marshmallow, but with nougat it doesn't work.
So I think (that version of) TWRP will not work. (but I have not tested myself, but I read a post somewhere saying it didn't)

Root for 8.0 Oreo

Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.

It was released a few days ago, just go with custom or wait for working solution

1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore

No-verity didn't work for me but remove encryption.zip did.

this didn't work for me, it resulted in a bootloop
ric69 said:
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
Click to expand...
Click to collapse

fre78 said:
this didn't work for me, it resulted in a bootloop
Click to expand...
Click to collapse
Sorry for you. check Mount system or data or enable MTP. Internal storage was probably still at 0
I rebooted more than 10times it's ok here

zainbfaisal said:
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
Click to expand...
Click to collapse
sir may i ask how come ur able to have twrp .
how dd u install twrp on android 8.0 UK firmware?
thanks for help

What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me

OREO stock keeps encrypting DATA partition
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)

fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate

NewbieFTW said:
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
Click to expand...
Click to collapse
Can anyone confirm that magisk should be installed in twrp before encryption disabler?

skydivider said:
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
Click to expand...
Click to collapse
Magisk removes the encryption disabler .zip for some reason.

Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse

zainbfaisal said:
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
Click to expand...
Click to collapse
I'm sorry then, I don't know what to say. It worked for me.

I needed reinstal magisk after boot for root, but worked for me...

fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
When this happend to me, i hit format data and typed yes, when i mount on TWRP i can see my storage again

I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?

miguelan.ruiz said:
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
Click to expand...
Click to collapse
Samsung Pay will, at the moment, probably never work again because it trips Knox.
For Samsung Health the fix is still the same: install a build.prop editor and change the value of RO.Config.Tima from 1 to 0.

not for me
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
doesn't work for me

Apparently there are 2 kind of users here.
One part did manage to install stock Oreo (BTU? other CSC?) , with root (magisk? superSu?) and a working TWRP (3.2.1?) which is not read-only on our beloved S7 Edge (SM-G935F)
The other part did not manage to setup this particular config.
It would be nice to have a detailed step-by-step guide from scratch by someone who managed to do it, so we can reproduce it.

ONEPLUS 5 updating issues , stuck in OOS 5.0 after updating it from OOS 4.1.5

Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?

Akarsh Adithya.K said:
Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?
Click to expand...
Click to collapse
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?

strongst said:
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?
Click to expand...
Click to collapse
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section

Akarsh Adithya.K said:
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section
Click to expand...
Click to collapse
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.

strongst said:
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.
Click to expand...
Click to collapse
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too

Akarsh Adithya.K said:
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too
Click to expand...
Click to collapse
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?

strongst said:
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?
Click to expand...
Click to collapse
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS

Akarsh Adithya.K said:
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS
Click to expand...
Click to collapse
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.

strongst said:
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.
Click to expand...
Click to collapse
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img

Akarsh Adithya.K said:
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img
Click to expand...
Click to collapse
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.

strongst said:
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.
Click to expand...
Click to collapse
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4

Akarsh Adithya.K said:
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4
Click to expand...
Click to collapse
To help others mark this thread as [SOLVED] in the the title :good:

strongst said:
To help others mark this thread as [SOLVED] in the the title :good:
Click to expand...
Click to collapse
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2

Akarsh Adithya.K said:
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2
Click to expand...
Click to collapse
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.

strongst said:
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.
Click to expand...
Click to collapse
Again , thank you soo much man .
Turns out enabling that vendor portion after flash rom for no verity and magisk will cause no trouble
and now i m on OOS 5.1.5!!(uninstalling Magisk before flashing new update was important to).
Now that
how do i mark this thread as Solved.

[STOCK PIE (march)] Will I get my data wiped if I hotboot TWRP?

Hello, I've been trying to root my phone, I followed a guide that tell me to
Code:
fastboot flash twrp.img
and got all my data wiped for some reason. LATER, i found out that you souldn't be doing that, instead you should be doing
Code:
fastboot boot twrp.img
But by then, I got everything on my phone deleted (i flashed an original rom from MI forums and restored a manual backup of data and some apps i had, but still I lost like a day setting up everything).
My questions are, if I hotboot TWRP will I get my data wiped again? (my bootloader is still unlocked so no danger there)
If not, can I backup my data normally using TWRP GUI on hotboot?
Also, once I've installed magisk, will I stop receiving OTAs?
Thanks

No, you won't get data wiped if you boot twrp. I'm doing this periodically and everithing is ok.
Probably you flashed twrp wrong. It should be
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
You can receive ota's with magisk. Prior to installing ota, you should uninstall/"restore partitions" with magisk but not reboot. After ota is installed, you install magisk into secondary partition (with magisk manager) and reboot.

BlackChimaera said:
No, you won't get data wiped if you boot twrp. I'm doing this periodically and everithing is ok.
Probably you flashed twrp wrong. It should be
You can receive ota's with magisk. Prior to installing ota, you should uninstall/"restore partitions" with magisk but not reboot. After ota is installed, you install magisk into secondary partition (with magisk manager) and reboot.
Click to expand...
Click to collapse
But isn't HIGHLY recommended to NOT flash the recovery?

I'm not flashing it too, just "fastboot boot" it when I need it.

BlackChimaera said:
I'm not flashing it too, just "fastboot boot" it when I need it.
Click to expand...
Click to collapse
I hotbooted TWRP and made a backup, after rebooting from TWRP, the phone boots slowly and hangs at the lock screen. Any ideas what could have triggered this?
The only "abnormal"thing i did was to rename the media folder in "data" so TWRP could include it into the backup. After that I renamed the folder to "media" again, and rebooted.
There was a "mediadrm" folder, but I don't remember if it was already there or not.

Why do you want to include media folder into backup? It has only mount points to sdcards. Do you want to include sdcard content into backup? Where is backup stored? On the same sdcard which content you backing up?

BlackChimaera said:
Why do you want to include media folder into backup? It has only mount points to sdcards. Do you want to include sdcard content into backup? Where is backup stored? On the same sdcard which content you backing up?
Click to expand...
Click to collapse
Media folder has internal storage. Anyway, i was able to boot again by flashing to latest stock rom and then restoring "data" from my backup.
Enviado desde mi Mi A1 mediante Tapatalk

BlackChimaera said:
No, you won't get data wiped if you boot twrp. I'm doing this periodically and everithing is ok.
Probably you flashed twrp wrong. It should be
You can receive ota's with magisk. Prior to installing ota, you should uninstall/"restore partitions" with magisk but not reboot. After ota is installed, you install magisk into secondary partition (with magisk manager) and reboot.
Click to expand...
Click to collapse
On Mi A1, TWRP can't be flashed from fastboot, because it doesn't have /recovery