Related
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Edit : Nougat running on my op3.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.
anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.
dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....
Thanks! Will try and let you know
abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.
Hey there,
I have been really annoyed since i installed OOS 4.0.0. First because it took ages the first time to get it right, and then because i had to start from scratch with every little 30MB update AGAIN.
I didn't find any reliable source to what happens in the folowing cases, thus this thread :
1- Flashing official recovery + updating through android
=> Will it work/DM-Verity error appear ?
2- Flash official recovery and sideload OTA/Full ZIP
=> Is /data getting wiped ? Same question about DM-Verity
3-Flash full Zip in latest eng.stk TWRP followed with supersu
Has anyone explored these solutions ?
Thanks in advance
EDIT: Working way for updating:
1: Dirty flash full ROM in latest modified TWRP
2: Flash SuperSU WITHOUT booting into system
3: Wipe dalvik/cache
4: reboot to system.
For explanation about what triggers DM-Verity check out post 19
DM verity is triggered by the firmware. You can't avoid it unless you want to run old firmware
It is not an error nor a bug - it is a notification. There is no impact to performance
2x4 said:
DM verity is triggered by the firmware. You can't avoid it unless you want to run old firmware
It is not an error nor a bug - it is a notification. There is no impact to performance
Click to expand...
Click to collapse
I do know that. I simply try to find the best way to update without hassle and without getting the DM-Verity message.
Nobody07 said:
I do know that. I simply try to find the best way to update without hassle and without getting the DM-Verity message.
Click to expand...
Click to collapse
update everything (ROM/TWRP), flash old (non-4.x) firmware
FYI you're fixing an aesthetic issues and there may be more bugs from using the old firmware.
2x4 said:
update everything (ROM/TWRP), flash old (non-4.x) firmware
FYI you're fixing an aesthetic issues and there may be more bugs from using the old firmware.
Click to expand...
Click to collapse
I don't have the issue right now with a 4.x firmware ... You are not helping... My guess is using OnePlus recovery and updating through android there wont be a DM Verity message. Do you know if this is true ? If not you aren't telling me anything i do not know.
Nobody07 said:
I don't have the issue right now with a 4.x firmware ... You are not helping... My guess is using OnePlus recovery and updating through android there wont be a DM Verity message. Do you know if this is true ? If not you aren't telling me anything i do not know.
Click to expand...
Click to collapse
if you use stock recovery you won't get the dm-verity notice either.
not sure why you mentioned eng.stk TWRP if you're not trying to run TWRP.
2x4 said:
if you use stock recovery you won't get the dm-verity notice either.
not sure why you mentioned eng.stk TWRP if you're not trying to run TWRP.
Click to expand...
Click to collapse
Thank you for answering, but seriously, did you even read the first post ?
So i can flash OnePlus firmware, update android within the system and then flash twrp again. With no DM Verity appearing ?
Nobody07 said:
Thank you for answering, but seriously, did you even read the first post ?
So i can flash OnePlus firmware, update android within the system and then flash twrp again. With no DM Verity appearing ?
Click to expand...
Click to collapse
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
2x4 said:
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
Click to expand...
Click to collapse
That's were you are wrong...
I currently have twrp and no dm-verity.
Nobody07 said:
That's were you are wrong...
I currently have twrp and no dm-verity.
Click to expand...
Click to collapse
because you are on pre-nougat ROM and/or firmware
2x4 said:
because you are on pre-nougat ROM and/or firmware
Click to expand...
Click to collapse
Im getting tired of you ignoring what i say.
I'm on OOS 4.0.1. I did a clean sideload through OnePlus recovery, and flashed twrp/root afterwards. No DM-Verity. I DID NOT flash an old firmware.
it's a compilation of things not just one thing, the firmware thing is just the easy way out, if you decrypt the phone data (just wipe it) and rooted then re encrypted it, you wont get the dm verity issue...
so simply, sideload or flash the full rom , if you sideloaded immediately fastboot TWRP (the latest official or modified) , then immediately flash SuperSU... reboot to system, no dm verity will appear.
---------- Post added at 09:46 PM ---------- Previous post was at 09:45 PM ----------
2x4 said:
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
Click to expand...
Click to collapse
not true, i have the latest 4.0.2 firmware and TWRP and no DM verity .
theduke7 said:
it's a compilation of things not just one thing, the firmware thing is just the easy way out, if you decrypt the phone data (just wipe it) and rooted then re encrypted it, you wont get the dm verity issue...
so simply, sideload or flash the full rom , if you sideloaded immediately fastboot TWRP (the latest official or modified) , then immediately flash SuperSU... reboot to system, no dm verity will appear.
Click to expand...
Click to collapse
What you are saying is i can flash full ROM through twrp, followed by supersu, reboot, and i wont get dm-verity nor loose any data?
Nobody07 said:
What you are saying is i can flash full ROM through twrp, followed by supersu, reboot, and i wont get dm-verity nor loose any data?
Click to expand...
Click to collapse
yes , idid exactly that updating from 4.0.1 to 4.0.2, dirty flashed the full rom , then immediately SuperSU, and then TWRP again just to be sure...and Viola
2x4 said:
because you are on pre-nougat ROM and/or firmware
Click to expand...
Click to collapse
Did a clean flash (beta 10) with the stock recovery, flashed TWRP with SuperSU afterwards.
No dm-verity.
After dirty flashing beta11 full zip + SuperSU through TWRP the dm-verity screen is still NOT there.
Btw, this has been already discussed weeks ago.
Do your homework.
dm verity is a fail safe present in system boot.img . Nothing related to firmware. Don't know from where people getting all this hoax
cpt.macp said:
dm verity is a fail safe present in system boot.img . Nothing related to firmware. Don't know from where people getting all this hoax
Click to expand...
Click to collapse
BC whether it's a band-aid or fixes the issue, if u flash an old fw outside of nougat with trwp, it gits rid of the nag
Bradl79 said:
BC whether it's a band-aid or fixes the issue, if u flash an old fw outside of nougat with trwp, it gits rid of the nag
Click to expand...
Click to collapse
it's the worst way to "fix" the issue, you're using an old firmware that's more than likely have incompatibility issues with the OOS updated rom, so unless you're using a custom rom (not OOS or OOS based) where it doesn't matter what firmware you use it's not a recommended practice.
Neither flashing twrp, nor OOS would trigger dm-verity (unless you already have that message)
If you however boot into system, dm-verity will be triggered. The idea is to patch that before it gets triggered.
Flashing SuperSU patches DM verity. Which is great if you want root access. Again this patch won't work if you already have dm-verity warning. Once you flash the ROM, do not boot into system. Flash SuperSU 2.79 or above and verity will be patched. You will also see a line "patching dm-verity" in SuperSU installation process. Now verity message won't appear.
If you don't want root, there is a no-verity zip that you can flash which will have the same effect. I use SuperSU so I don't have any links to this but Google is your best friend.
- if you already have verity
- if you forgot patching verity, booted into system and now warning screen has appeared.
Now here is where things get tricky. Boot to fastboot, connect phone and type
fastboot format userdata
Remember the above step will wipe internal storage completely
Reboot to recovery
Format data (not wipe but format. This step is very important)
Flash OOS
Flash SuperSU
Reboot to system. Now there will be no dm-verity warning
@ungeeked great detailed explanation that should put an end to all chatter TBH your reply should be pinned in this section for some while and titled DM-Verity explained.
I just noticed my p2 has been encrypted and I think it happened after nougat update. Can others confirm? Is it nougat feature or something??
In MM is the same.
I think the stock roms have forced encryption enabled by default. It will reencrypt the phone if it was decrypted.
my p2 was encrypted since beginning with MM and same for Nougat
I cant access to twrp anymore . How to remove encryption?
kataeb said:
I cant access to twrp anymore . How to remove encryption?
Click to expand...
Click to collapse
Use latest unofficial twrp-3.1.0-0 i already fix that bugs, see in my treats
I updated with unofficial twrp but still asking for a code, it is encrypted
kataeb said:
I updated with unofficial twrp but still asking for a code, it is encrypted
Click to expand...
Click to collapse
You must remember last your pin code otherwise twrp can't decrypted
Hi, my p2 didn't ask me any code but is still encrypted.
How can I decrypted it ?
When I am in settings security, there is encryption shown, but no any option to decrypt it.
How can I fix it ? My bootloader is unlocked, but when I flash rom, I have a message after the bootanimation to reset for decrypt my phone, but it doesn't work.
Any idea or Decrypted & Insecure boot.img with adb fix ?
gui3gui said:
Hi, my p2 didn't ask me any code but is still encrypted.
How can I decrypted it ?
When I am in settings security, there is encryption shown, but no any option to decrypt it.
How can I fix it ? My bootloader is unlocked, but when I flash rom, I have a message after the bootanimation to reset for decrypt my phone, but it doesn't work.
Any idea or Decrypted & Insecure boot.img with adb fix ?
Click to expand...
Click to collapse
Happened to me too while using a custom rom and then switching to another rom :silly: There is a way to do it.. Got to TWRP change System and Cache to Ext 4 using the repair/ change file partition, doing it to data wont work because its encrypted.. But doing so with cache and system should erase and reset it.. Oh and format data after that. Then you can flash a rom.. There is also an adb command too ---- fastboot format userdata ... And then ---- fastboot reboot
Ok I will try this. Thanks for your help.
Envoyé de mon HUAWEI NXT-AL10 en utilisant Tapatalk
It's working perfectly. Thanks a lot !
A while back, I did get root on my phone with adb and fastboot. Since then I took the OTA update to Oreo 8.1. I lost root and trying to get it back so I can put a custom room on?
I tried to do the systemless 8.1 root, but once in twrp I could not find any files to flash. I downloaded the files to phone but could not find them on internal storage in twrp. I'm sure I'm missing something
ken2736 said:
A while back, I did get root on my phone with adb and fastboot. Since then I took the OTA update to Oreo 8.1. I lost root and trying to get it back so I can put a custom room on?
I tried to do the systemless 8.1 root, but once in twrp I could not find any files to flash. I downloaded the files to phone but could not find them on internal storage in twrp. I'm sure I'm missing something
Click to expand...
Click to collapse
You don't need root to flash a custom rom if you are asking that you just need a TWRP, If you are trying to flash root on stock rom.
there is guides in this section that make it simple and for custom roms steps are in the OP of the rom threads
I will keep reading. Tried twrp last night using the "all in one tool". I could not find the zip files. When I got to twrp, I couldn't get past pattern screen. So I clicked "read only", maybe that's why I couldn't find the files?
ken2736 said:
I will keep reading. Tried twrp last night using the "all in one tool". I could not find the zip files. When I got to twrp, I couldn't get past pattern screen. So I clicked "read only", maybe that's why I couldn't find the files?
Click to expand...
Click to collapse
Yes your data in encrypted so password needs to be entered to decrypt data in twrp to see your files
So I need to make sure I set my security to none or swipe correct?
ken2736 said:
So I need to make sure I set my security to none or swipe correct?
Click to expand...
Click to collapse
Yes, If you are on stock rom use the latest TWRP 3.2.1-0 you can use a password with that version and it'll successfully decrypt
Is there any way to install magisk on a gsi by flashing a zip file in twrp.
Any help appreciated.
Seconding this question.
I made Magisk work with stock firmware, but I want a custom rom.
Successfully flashed base AOSP on it, and rooted (with the IMEI fix posted in other threads).
But now the Magisk app says its not installed. The phone is still rooted.
I need to fix this in order to access Magisk settings, like hidding Magisk so I can install/run apps that detect it.
sargeta said:
Seconding this question.
I made Magisk work with stock firmware, but I want a custom rom.
Successfully flashed base AOSP on it, and rooted (with the IMEI fix posted in other threads).
But now the Magisk app says its not installed. The phone is still rooted.
I need to fix this in order to access Magisk settings, like hidding Magisk so I can install/run apps that detect it.
Click to expand...
Click to collapse
custom rom? or a custom gsi. if you found custom rom please link me to it. but for gsi's you can just patch the AP file with magisk flash that with other files then flash twrp then flash the gsi of your choice and once you install magisk manager you should have root.
@Captain_cookie_200 I see your signature: "Galaxy A32 4G (SM-A325F) [Rooted with Magisk, Running Custom GSI] "
were you able to install magisk on a gsi on the a32 4g ? if so, how?
dronkit said:
@Captain_cookie_200 I see your signature: "Galaxy A32 4G (SM-A325F) [Rooted with Magisk, Running Custom GSI] "
were you able to install magisk on a gsi on the a32 4g ? if so, how?
Click to expand...
Click to collapse
just root it as you would on one ui?
i copied my firmware's ap file to phone. opened magisk. chose to select and patch a file. selected the ap file i copied. Now once its done patching it'll show a new file located at your downloads folder. something like magisk_patchex-26000-somwthingsomething.tar
copy that back to the pc. Now put BL Cp and CSC in their respective slots. Put the new patched file you copied from phone to pc in ap slot. start flash. once done. flash twrp and stuff again and once you install a gsi again it shld be rooted this time.
people think magisk modifies system. but in reality it only touches boot and other things. its a systemless root solution as it says. Although these days i dropped magisk for KernelSU and thats what I use now. I'll update my signature
Also the method i wrote above will wipe your data. backup important stuff before doing it.
If you dont want data loss you can Use HOME_CSC instead of CSC file in csc slot. And if u were using a gsi previously. do not let it boot into one ui. otherwise it might encrypt and destroy all your data.
Captain_cookie_200 said:
just root it as you would on one ui?
i copied my firmware's ap file to phone. opened magisk. chose to select and patch a file. selected the ap file i copied. Now once its done patching it'll show a new file located at your downloads folder. something like magisk_patchex-26000-somwthingsomething.tar
copy that back to the pc. Now put BL Cp and CSC in their respective slots. Put the new patched file you copied from phone to pc in ap slot. start flash. once done. flash twrp and stuff again and once you install a gsi again it shld be rooted this time.
people think magisk modifies system. but in reality it only touches boot and other things. its a systemless root solution as it says. Although these days i dropped magisk for KernelSU and thats what I use now. I'll update my signature
Also the method i wrote above will wipe your data. backup important stuff before doing it.
If you dont want data loss you can Use HOME_CSC instead of CSC file in csc slot. And if u were using a gsi previously. do not let it boot into one ui. otherwise it might encrypt and destroy all your data.
Click to expand...
Click to collapse
so basically you root the stock, then install the GSI?
yeah, I tried that yesterday and got bootlooped when I tried to boot the GSI for the first time
but today I realize it was data corruption on the memory card i was using
gonna try again. Thanks!