My first post here on the forums but been a member here for more than a year.
Been using a Samsung A205w ( A20) for well over a year now and went from LineageOS 16 to 17 and now working on LineageOS 18.
Grab the latest firmware using Frija and patched Magisk to the AP file and flashed to unit. The phone boots find and Magisk works as expected.
Then install Android Q recovery with Odlin and TWRP comes up as expected. Install LineageOS 18 with NikGapps and it boots to a black screen.
If I flash Magisk.zip ( 21.2 ) using TWRP before LineageOS 18 and NikGapps it will boot without issue but Magisk will not work.
Any pointers for my first post?
Thanks Sam
Related
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
HighOnLinux said:
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
Click to expand...
Click to collapse
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Flashed uninstall magisk and than magisk 17 and all worked well.
dracoboss said:
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Click to expand...
Click to collapse
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Got the same problems as described here. Then I downloaded the latest Magisk uninstaller and Magisk 17 from the Magisk thread. The next step was to flash the uninstaller and afterwards Magisk 17 and the device booted well.
Running 17.1 and still getting the same thing with safety net check as before
The response is invalid
HighOnLinux said:
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Click to expand...
Click to collapse
Yeah that's what I did and everything is fine... For now lol. Thanks
From Magisk 17.0 to Magisk 17.1, install it automatically. SafetyNet test successful
it's better and more secure deinstall first magisk manager clearing cache and data, install magisk 17.1 from twrp and if magisk manager doesnt be installed, install the apk
Hello I come from this thread and downloaded the patched magisk boot image for stable android 10 BA but it break the wifi (iirc it mean it's for AA which have different firmwares). I already asked in the thread if there are a patched img for BA but I ask here in case someone already have a rooted stable BA Android 10 terminal because I really need root.
Thx
https://forum.xda-developers.com/showpost.php?p=80643311&postcount=158
You can also fastboot boot TWRP (unofficial built -70), then just flash Magisk and it will patch boot.img automatically, and obtain root.
Credit to @hotz3nplotz over in the Xperia 1 section that tested Magisk 20 back in October.
Use Magisk manager to patch the boot image (not the in place upgrade), and then flash via fastboot. Tested with I3223 running 14.28_R6A.
I just rooted my samsung s10 G973F / DS via Magisk (not without some bootloop issue and a couple of times I had to flash the stock firmware and then the patched one).
I would try to include havoc custom rom which has great reviews for wanting twrp first.
So that the March 2021 update for Android 11 support is out, but I need a guide, in fact I wonder if I flash the twrp 3.5.2. from odin, do i need to reinstall magisk from recovery twrp or is my root safe?
Thanks to who will answer me!
Giulia
Have the exact same question in mind. Hopefully someone will respond soon
hi
i have a poco x3 pro, rooted (magisk) and running LineageOS 18.1
Now i get my first OTA and wonder how to retain root, after upgrading.
with my Mi A1 it was
* restore boot image from within magisk manager
* install OTA
* reinstall magisk after OTA in magisk manager in second partition
* reboot
as far as i see X3 Pro has no A/B scheme
I'm using TWRP and Magisk flashed as zip by TWRP. This way a proper addon script is installed and Magisk survives OTA. The same goes for gapps.
If you install Magisk by flashing prepared boot.img, then you have to repeat this procedure after each OTA update.
You don't have to restore original boot.img before OTA. LineageOS is not an incremental update, it is full system, which overwrites boot.img, regardless of what it contains.
thanks for answering. i did my first install this way:
install LOS via lineageos recovery, add gapps, add magisk, reboot
i now installed the OTA from inside Lineagos. root lost. i checked for the existance of /system/addon.d/99-magisk.sh and the script was (and still is) there. do i need to download OTA and afterwards install the update from recovery?
Maybe it is a problem of LineageOS recovery. I'm using official TWRP. You probably have to install Magisk again. I think you can switch to TWRP at any time, it is compatible with Lineageos.
worked, thanks for pointing me into the correct direction!
the steps so far:
1* reinstall magisk (by patching boot.img from the OTA and booting into that and reinstall magisk)
2* download the next OTA
3* install twrp (i used the path through play-store)
4* start the installation of OTA (from inside android)
5* poco reboots into twrp
6* unlock with my password/pin
7* twrp does some magic/installs OTA
8* boot into system
9* everything is fine
from now on it should work from step 4
merry xmas!