Hi All,
I wonder if any of you , who use stock Oreo 8.0 rooted, have updated Magisk to the latest v22? If you have done so, would you mind sharing how it went?
TIA
Most software comes with an event log for each update. This record shows what was changed, deleted, or added, if there was nothing told specifically about your phone, or OS, then it is probably the same as it's former stable version.
check here: Magisk 22 Changelog
Related
Hi,
What about this device ?
All I could find was "Galaxy XCover 4s SM-G398F/FN Pie 9.0 using Magisk"
All I want to do is install Magisk or LOS but LOS was I think not yet supported (quick search) and old boot.img
device info;
Samsung Galaxy XCover 4s SM-G398F/FN/DS​
One UI 2.0
Android 10
Knox 3.5 API lvl 31 TIMA 4.1.0
Kernel 4.4.177-18237086
Build QP1A.190711.020.G398FNXXS5BTD2
Security software version
- ASKS v3.1 release 20200120
- ADP v3.0 release 20191001
- SMR may-2020 release 1
Android patch level May 1 2020
I haven't updated the rom on the device because this would only makes it harder for me...
Can it run TWRP or any custom recovery unsigned I am willing to experiment with boot.img on my device because without root this phone is useless for me (side load without flashing, like I always do). Have too much phones here for testing but most of them are slow to the snail due to outdated SoC and latest OS/kernel.
let me know I can dump boot.img and we can have fun experiments.
Not sure if this device is able to downgrade rom using odin or if Knox has ARP.
Any hits on next step? Don't feel like wasting lots of time phone is for RE and testing. Nothing special.
How to Patch Stock Boot Image (IMG) using Magisk Manager and root
Once you are sure that you are done with the backup stuff, please proceed to the tutorial below on "How to Patch Stock Boot Image (IMG) using Magisk Manager."
droidfeats.com
As you said there is no lineage os. Just check if your phone supports project treble by downloading treble check app. If supported, you can install variety of andorid 11 roms
Tab E said:
As you said there is no lineage os. Just check if your phone supports project treble by downloading treble check app. If supported, you can install variety of andorid 11 roms
Click to expand...
Click to collapse
Yay just what I needed. System-as-root: supported.
Thanks for that, yeah just got some time to check it out so well, thats neat.
Hello Guys,
I Just wanted to know how I root my pixel 3 with android 12 just guide mn or is there already a thread than give me a link but plz for android 12
Rooting Android 12 works exactly the same as Android 11 on the Pixel 3.
Since there were no obvious guides, I just wrote one for the Pixel 3. Here you go.
Thanks for help
Can u tell me is there any twrp for android 12
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Hmm so how we install custom roms
rocketrazr1999 said:
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Click to expand...
Click to collapse
Update... Android 12 can be rooted using Magisk Canary
I was able to take an OTA update to Android 12 on my BL unlocked, rooted, custom kerneled Pixel 3! I started the update accidentally by hitting that pop up reminder and after a minute of thinking what to do (i did not want to lose my data!!!), I held down the power button to force it to reboot during the update. I have had this work to stop an OTA update and restore it perfectly to previous state. Anyway, it did NOT work this time, and it updated to A12 perfectly! No loss of data, no loss of custom kernel, but i did of course lose root. Also.... when i checked the update version in settings, it wanted to update AGAIN, from Oct 21 to Feb 22 (which is just an Emergency Dialer patch). My phone still shows Oct 21 security patch in settings, but shows the Feb 22 firmware (...016.C1), which suggests the patch was only a tiny fix to the 911 Dialer and did not affect anything else. So this time i let it update, which i started to think was stuck or looping after waiting about an hour, but finally i checked the progress and it was done, requesting a reboot! So i rebooted it and behold, its now running final security update to the Pixel 3, and all i need to do now is root with Magisk and install SafetyNet Fix. Which is the ONLY thing i can think of as to how it was able to do a factory OTA update while rooted and BL unlocked! The SafetyNet Fix patch may be so good that it bypasses the Google security measure that refuses to allow OTA updates on rooted, unlocked Pixel 3s. Yup, on a GOOGLE PIXEL! I used to have to unroot and install the factory kernel to do an OTA sideload on my old Essential in order to update and not lose data, but i was told that you could not update to new Android versions without losing your data on the P3, so Ii just figured my Sept 21 A11 firmware was the final update until a phone upgrade. Anyway, just wanted to pass on the good news that you CAN perform a factory OTA update from A11 to A12 on the Pixel 3 WHILE rooted and unlocked and with a custom kernel, but I of course have to recommend you do so on your own, and if anyone has an unused or non-daily driver P3 that want to confirm this good news, please do so and help convince the disbelievers ! The ONLY thing i would recommend is that you have the latest "Android 12" version of SafetyNet Fix installed with the switches on in Magisk, which is what i had. Its the only thing i can think of that would allow Google's Safety Net to bypass the security restrictions. OK then, hope a few of you give it a try to show im not a nutcase, lol.
Question kind of related to this... Was the P3 kernel updated in Android 12 to fix that race condition that causes freezes if using systemless hosts? With A11 I always had to make sure I installed a custom kernel before Magisk and enabling systemless hosts to keep my P3 from freezing.
I've been having some problems updating my LE2110 rooted and w/ Magisk One Plus 9 5G phone. Model is LE2110 and the build number I am on is Oxygen OS 11.2.9.9.LE25AA.
Here's my process to updated:
On my phone options, when I go to settings - systems - system updates - check for updates - it finds a new version LE2115_11_C.44_202201182115. However it cannot instal it do to an 'installation problem'.
So I tried using Oxygen Updater App and from there I can download the LE2115_11.C.44 patch locally. I then go back to settings - system - system updates - setting icon on top right - then local upgrade. From here I can see my downloaded update locally, I'll install that and do not reset. I then go to Magisk and click install - install to inactive slot (after OTA). This is advised to do so it keeps my root during reboot. I then reboot and I see that the update hasn't actually installed.
Any ideas on how to get this phone updated? This might be a problem that I have a LE2110 chinese phone and am running Oxygen OS. It's a work phone, so important for me to keep it up to date. Am I doing something wrong in the process? Thank you so much.
Title says all, would like to know if latest T-Mobile rom is 12?
nujackk said:
Title says all, would like to know if latest T-Mobile rom is 12?
Click to expand...
Click to collapse
I have the Na global op9 and yup it's still on A11 by internal system update. Can get A12 through oxygen updater but don't want OnePlus's Bs version of merged oos.
Ok , haven't used my 9 in almost yr. So just wanted to update to latest 11 firmware before loading custom ROM. Don't want 12 for a while.
Updated to 12 today. I would avoid as long a possible. TMobile bloats it even more and disables the ability to disable apps that you could previously (Google pay, a bunch of TMobile B's and some system apps like clock, messages, etc).
Update, you can disable apps via abd if you need. =)
So I downloaded the latest firmware image (WW-31.0810.1226.154-1.1.213-2303) and copied it to the root of the phone and rebooted, but instead of detecting the update file as usual and prompting to update, nothing happened. Phone currently has the last month's update to Android 13 (WW-33.0210.0210.200) and is rooted/bootloader unlocked.
Is the current month update meant for Android 12 only? Now I notice the version number is less than the one I have, and the changelog just says it has the Google security patch for May.