Related
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
itenos said:
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
Click to expand...
Click to collapse
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
With that said:
If you want to keep your data, make a backup using Hisuite.
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Just stumbled over your reply, didn't get an email notification from XDA. Thank you so much. Let's see if I can follow your instructions.
irony_delerium said:
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
Click to expand...
Click to collapse
Yes, I still have the code
irony_delerium said:
With that said:
If you want to keep your data, make a backup using Hisuite.
Click to expand...
Click to collapse
Done
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Click to expand...
Click to collapse
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
irony_delerium said:
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Click to expand...
Click to collapse
I don't think that I modified any other partitions, at least not willingly. I even left the system in read-only state. Don't know if phh.su did something by itself?
irony_delerium said:
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Click to expand...
Click to collapse
Will continue to do the above after your kind confirmation of my last questions. Thanks again
itenos said:
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
Click to expand...
Click to collapse
The order shouldn't be particularly relevant, just that it's safest to reflash all of them:
- boot because phhsu may have modified the boot image to add su to it
- recovery and recovery2 because you loaded TWRP. recovery2 is specified because it's used to be recommended to flash to erecovery as well as normal recovery.
- system because I'm pretty sure that's the biggest thing modified Hy phhsu, and any other system changes you may have made.
Theoretically, other modified partitions won't matter since the upgrade to 8.0 replaces most (all, I think) of them anyway, but if you have to go through update steps through EMUI 5 first before it'll give you 8, then it's safest that they aren't modified. I mentioned other partitions because, with root & TWRP, you technically could have modified any and all of them.
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically.
Click to expand...
Click to collapse
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
itenos said:
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
Click to expand...
Click to collapse
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
irony_delerium said:
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
Click to expand...
Click to collapse
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
itenos said:
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
Click to expand...
Click to collapse
Easy way:
Unlock phone, if you haven't yet again.
Download and flash TWRP from here: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353 (has decryption support) (flash to recovery_ramdisk as Huawei decided to split recovery partition into different parts)
Boot to TWRP, input pin (if you set a pin, else it will decrypt automatically)
Download Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Transfer Magisk to phone.
Flash Magisk zip in TWRP.
Reboot and you're done.
You might have to tinker around with Magisk Hide and hide apps if your banking apps still detect root.
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
itenos said:
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
Click to expand...
Click to collapse
The erecovery method won't work unless you can change the DNS settings on the network being used - it hijacks some of the requests to Huawei's servers to force the update. (And even then it's a bit finicky; I have yet to successfully use it, all things considered.)
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
itenos said:
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
Click to expand...
Click to collapse
The reason recovery boot is needed for Pie is because Huawei removed the ramdisk - in Pie, it's system as root with no way of forcing a ramdisk except by a recovery boot. So as a workaround, Magisk takes over recovery.
The installation instructions for it on Pie are pretty much the same as Oreo, except:
* Patch recovery_ramdisk, not ramdisk. Latest stable Magisk should work (18.1, iirc, has the patches to support recovery boot.)
* When booting, go to recovery. Magisk will start from there and take over the startup process.
irony_delerium said:
The installation instructions for it on Pie are pretty much the same as Oreo, except:
Click to expand...
Click to collapse
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
itenos said:
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
Click to expand...
Click to collapse
TWRP on this case, don't bother.
Extract your stock recovery from your firmware's update.app file, patch with Magisk Manager, and flash the patched image. When you want to flash an ota, put the stock recovery back.
Hello!
I run Samsung's official FW build R16NW.G930XXS3ERL7, latest Magisk, and some root apps (incl. Xposed Framework, e.g. AFWall+, Firefds Kit [set to fake device status to "Official", but the info further below - above the charging status "DC 9 V; 1.67 A" - nevertheless shows "RATED"], MinMinGuard, XPrivacyLua). From time to time, apps get force-closed and my device gets slow.
Now I wonder if it would help to flash the latest available official FW from Samsung for my device right over the existing one. We call this "dirty-flash", right?
Would you agree that this works or would you rather wipe everything (after backing up essential data, of course) and do a clean flash?
The latter would give me the opportunity to clean up unneeded stuff.
How should I backup the device's many settings and the individual apps' settings? I do not like the available cloud services from Google or Samsung to backup settings and I heard that restoring apps' settings later via e.g. TitaniumBackup (I have the paid pro version) could cause severe problems. Any alternatives (for restoring device's and apps' settings?
In any case, I would first do a binary backup via TWRP to be able to revert everything if nothing works after flashing.
Do you have any other hints for me?
Thank you so much!
PS: Sorry if this is the wrong place/forum for my questions. In that case, I would like to politely ask the moderators to move my post to where it fits better (and might attract more attention/replies )
Dirty flashing usually refers to flashing in TWRP over top the existing install without wiping.
But if you flash via Odin, depending what you flash, it will either be a full wipe and load. Or it will update the same way an OTA update applies.
Also from memory if you flash AP in Odin it's going to blow away your TWRP and restore it to stock recovery, so make sure you copy your TWRP backup off the device before continuing.
If just going official Samsung to another official Samsung FW, then TitaniumBackup should work fine.
Thanks for your reply!
Am I right that I can flash TWRP via Odin immediately after having flashed the new Samsung firmware also via Odin?
Which of the CSC files is the one that should be flashed via Odin (AP) so as not to loose settings etc.? If my recollection is correct, there are usually 2 flavours of the CSC file in the firmware package, one of them to flash with wiping everything, the other to fish as if it was an update (like OTA). Right?
Can a custom kernel also be flashed via Odin? Which first: kernel, then new firmware, then TWRP or in another order?
Thanks once more for your hints!
7wells said:
Thanks for your reply!
Am I right that I can flash TWRP via Odin immediately after having flashed the new Samsung firmware also via Odin?
Which of the CSC files is the one that should be flashed via Odin (AP) so as not to loose settings etc.? If my recollection is correct, there are usually 2 flavours of the CSC file in the firmware package, one of them to flash with wiping everything, the other to fish as if it was an update (like OTA). Right?
Can a custom kernel also be flashed via Odin? Which first: kernel, then new firmware, then TWRP or in another order?
Thanks once more for your hints!
Click to expand...
Click to collapse
HOME_CSC won't wipe anything, if you flash just CSC it will wipe all your data. Flash kernel in twrp.
1st - New firmware, 2nd - TWRP, 3rd - kernel.
Thank you so much!
Hello!
I am on an older version of Android 11 and I would like to install the latest Android 11 OTA without losing root and TWRP.
I know that I could just manually flash the lasted Android 11 firmware, then re-install TWRP and Magisk, but this would mean losing all data and having to reinstall apps, restore backups, etc...
So I was wondering if there were a quicker way to install OTA updates without losing data and root.
I know that there are many articles on the subject but they all refer to a previous version of TWRP and Magisk. Because TWRP 3.6.0 sports a completely revamped codebase I would like to know what is the latest recommended method if any.
This is my system info:
Android 11 sargo-rq1a.201105.002-factory-2433e0c0
Magisk v23
TWRP 3.6.0-11_0
Japan region
PS I do not intend to update to Android 12 yet
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
reyqn said:
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
Click to expand...
Click to collapse
The flashall script will still remove TWRP and root though, right?
blksith0 said:
The flashall script will still remove TWRP and root though, right?
Click to expand...
Click to collapse
Yeah it does, you have to reflash them after
It's annoying that we can't choose the OTA android installs, it has to be the latest one. On some phones you can choose a local file, but I didn't find a way to do so with a pixel 3a.
If you were able to do this, in theory you could just flash the magisk module for twrp retention and preflash magisk on the unactive partition after installing the ota but before rebooting. Then just reboot and you keep everything.
I'm not ready to update to android 12 either (gravitybox, twrp), but I'll try then...
LastStarDust said:
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
Click to expand...
Click to collapse
I don't understand. Just flash the Full Factory OTA zip in TWRP. That won't remove any data. And you can just check the box to "Automatically flash TWRP after zip" so that you'll keep whatever TWRP you're using. Then you just have to reboot recovery (so that you're on the updated slot) and flash the Magisk APK in TWRP. Reboot and profit.
P.S. This post belongs in Q&A.
Captain_Throwback said:
I don't understand. Just flash the Full Factory OTA zip in TWRP
Click to expand...
Click to collapse
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
reyqn said:
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
Click to expand...
Click to collapse
That 'recommendation' is specific to incremental OTAs. Also, it not generally being supported isn't the same as it not being recommended.
TWRP will install the zip to the inactive slot, and then when you reboot, the device will automatically boot into the updated slot.
Thanks for the precisions, I'll know for the next time. TWRP really is awesome
hi everyone, i flashed pixel 3a to android 12 and now my imei is 004400.... and no service ..... what should i do?
I'm try to root that new firmware. No method working now. Not work patching boot.img with magisk and flash in AP Not work flash empty Vbmeta with boot img patched with Magisk. Not work to flash twrp-3.7.0_12 by Afaneh92, multidisabler, FORMAT with YES on data partition. Nothing work. After all that...restart, restart, restart. the phone not boot.
What version of Magisk are you using and where did you download it from? Flashing Magisk 25.2 in TWRP should work fine.
Kernel Sources aren't released yet. So there is no way to root it yet. Stick to the Jan Patch for now.
V0latyle said:
What version of Magisk are you using and where did you download it from? Flashing Magisk 25.2 in TWRP should work fine.
Click to expand...
Click to collapse
In this 3 days I flashed Magisk 25.2, Magisk Canary to try, not of this is working correct at all. There is no meaning what I flash and which order. Just restart.
JazonX said:
Kernel Sources aren't released yet. So there is no way to root it yet. Stick to the Jan Patch for now.
Click to expand...
Click to collapse
Ok, but how to downgrade the bootloader, because ODIN not flash the older firmware, issue some error. Patched one ODIN too.
Vishnarov said:
Ok, but how to downgrade the bootloader, because ODIN not flash the older firmware, issue some error. Patched one ODIN too.
Click to expand...
Click to collapse
bootloader downgrade is not possible
Run stock firmware clean for now; until a solution is made. I'm sure @afaneh92 will come up with something after the kernel sources are out.
JazonX said:
Run stock firmware clean for now; until a solution is made. I'm sure @afaneh92 will come up with something after the kernel sources are out.
Click to expand...
Click to collapse
I will. I have no choice
Vishnarov said:
I will. I have no choice
Click to expand...
Click to collapse
Patch ap file with magisk and Flash via odin like normal whole firmware
Just Installed 5.1 on my S22U (S908E) and prepared a ROM as usual. Magisk 25.2,TWRP,Decryption everything works as it is on 5.0 ROM
I have no reason to believe anything will be different on S908B
Even Magisk 25.2 works on S23Ultra too. (I have my pre-rooted ROM already with magisk 25.2 for S23U) just needs manual patch but that's only for S23U, not needed for S22U, even TWRP works pretty fine and yet we don't have kernel source. OneUI 5.1 is no much different than 5.0
dr.ketan said:
Just Installed 5.1 on my S22U (S908E) and prepared a ROM as usual. Magisk 25.2,TWRP,Decryption everything works as it is on 5.0 ROM
I have no reason to believe anything will be different on S908B
Even Magisk 25.2 works on S23Ultra too. (I have my pre-rooted ROM already with magisk 25.2 for S23U) just needs manual patch but that's only for S23U, not needed for S22U, even TWRP works pretty fine and yet we don't have kernel source. OneUI 5.1 is no much different than 5.0
Click to expand...
Click to collapse
Thanks for this confirmation, So I assume only a permissive kernel is missing and that's only required for System R/W ?
Regardless of that, the existing TWRP, Magisk works to get a rooted 5.1 ?
JazonX said:
Thanks for this confirmation, So I assume only a permissive kernel is missing and that's only required for System R/W ?
Regardless of that, the existing TWRP, Magisk works to get a rooted 5.1 ?
Click to expand...
Click to collapse
Yes if you planning to run multidisabler or system-rw script, you must needed to flash permissive kernel and that's what probably OP is missing.
Alternatively, flash system-rw custom ROMs
dr.ketan said:
Just Installed 5.1 on my S22U (S908E) and prepared a ROM as usual. Magisk 25.2,TWRP,Decryption everything works as it is on 5.0 ROM
I have no reason to believe anything will be different on S908B
Even Magisk 25.2 works on S23Ultra too. (I have my pre-rooted ROM already with magisk 25.2 for S23U) just needs manual patch but that's only for S23U, not needed for S22U, even TWRP works pretty fine and yet we don't have kernel source. OneUI 5.1 is no much different than 5.0
Click to expand...
Click to collapse
I wonder how is happen this, but obvious is truth as soon as you say that , because Im not new in flash processes and Im doing what is do in previous firmware when rooted the stock ROM, the same flash and everything , but the things is going to wrong way , just infinite reboot. Flashed new firmware 5 times with Odin and tried everything. Last I must to try to flash AP Magisk patched and whole firmware with it just like Be_Cruel said above .
Vishnarov said:
I wonder how is happen this, but obvious is truth as soon as you say that , because Im not new in flash processes and Im doing what is do in previous firmware when rooted the stock ROM, the same flash and everything , but the things is going to wrong way , just infinite reboot. Flashed new firmware 5 times with Odin and tried everything. Last I must to try to flash AP Magisk patched and whole firmware with it just like Be_Cruel said above .
Click to expand...
Click to collapse
If you are flashing TWRP and run multidisabler OR run system-rw script, you will have bootloop because this requires custom kernel which is not available yet for OneUI 5.1
Magisk Patching AP will 100% work (without TWRP), do this
Patch AP file with magisk
Flash patched AP file with other BL CP and CSC file (use CSC* instead of HOME_CSC as this will auto format device) and all should be good
dr.ketan said:
If you are flashing TWRP and run multidisabler OR run system-rw script, you will have bootloop because this requires custom kernel which is not available yet for OneUI 5.1
Magisk Patching AP will 100% work (without TWRP), do this
Patch AP file with magisk
Flash patched AP file with other BL CP and CSC file (use CSC* instead of HOME_CSC as this will auto format device) and all should be good
Click to expand...
Click to collapse
One of the things what I does was to flash clean firmware, ,TWRP with Vbmeta, multidisabler, format Data with YES, and flashed Magisk after that. Again bootloop.
Can I flash clean firmware, Vbmera with TWRP and Magisk without multidisabler and format data ?
Lastly I should do what you said to flash magisk patched AP with all firmware.
Vishnarov said:
One of the things what I does was to flash clean firmware, ,TWRP with Vbmeta, multidisabler, format Data with YES, and flashed Magisk after that. Again bootloop.
Can I flash clean firmware, Vbmera with TWRP and Magisk without multidisabler and format data ?
Lastly I should do what you said to flash magisk patched AP with all firmware.
Click to expand...
Click to collapse
TWRP without multidisabler have limitation, you won't able to make data backup nor can store other backup to Int storage
You have following optios before permissive kernel available for 5.1
- Flash TWRP without multidisabler or system-rw script (Limites TWRP use, No system-rw)
- Patch Magisk with AP and flash as said above (No TWRP)
- Go with custom ROM which support full TWRP+system-RW
Ok, I will try, but to mention for the last you said...No old ROM (not yours nor enything else) want to begin to install with the newest bootloader. TWRP issue a warning that want the older bootloader to install your ROM, for instance...Something as "You must be to S908BXXS2BWA2 formware to install this.
Vishnarov said:
Ok, I will try, but to mention for the last you said...No old ROM (not yours nor enything else) want to begin to install with the newest bootloader. TWRP issue a warning that want the older bootloader to install your ROM, for instance...Something as "You must be to S908BXXS2BWA2 formware to install this.
Click to expand...
Click to collapse
My OneUI 5.1 Full rom for S908E is available, for S908B it is under internal testing, will be public soon
dr.ketan said:
My OneUI 5.1 Full rom for S908E is available, for S908B it is under internal testing, will be public soon
Click to expand...
Click to collapse
When you ROM be done, will try. I tried to flash magisk patched AP with all the rest firmware , nothing, again reboot. Tried
GSI ROM ,again reboot, reboot. I can not figure out what is happening. Work just stock firmware
@
dr.ketan said:
My OneUI 5.1 Full rom for S908E is available, for S908B it is under internal testing, will be public soon
Click to expand...
Click to collapse
hello Dr.ketan
i have been using your roms Note 3, Now I had been to US An d purchased Galaxy S22 Ultra and returned to India Last week tried inserting Jio sim, to my shock 5G don't work on it, tried searching solution but in vain, couldn't find anywhere ! any help from you side will appreciated .
Thank-you
Regards
Hello,
I have a rooted (Magisk) A53 with TWRP. For a week, I get a notification asking me to update to security patch level of May 1st, 2023. I thought that with unlocked bootloaders, OTA wasn't possible, but whatever. My question is if it's possible to perform the update without losing TWRP and Magisk, and also if it's possible to keep all user data and installed apps. I have little time to spare after work and really don't want to go again through the process of resetting my phone.
Thanks.
No, it is not possible to update via FOTA in your rooted device. However, you can flash the latest stock firmware via Odin without any data loss. Download the latest firmware available for your device/CSC, patch the AP tar via the Magisk app and flash via Odin the BL, CP, AP, HOME_CSC and the Magisk patched tar in Download Mode.
Jahus said:
Hello,
I have a rooted (Magisk) A53 with TWRP. For a week, I get a notification asking me to update to security patch level of May 1st, 2023. I thought that with unlocked bootloaders, OTA wasn't possible, but whatever. My question is if it's possible to perform the update without losing TWRP and Magisk, and also if it's possible to keep all user data and installed apps. I have little time to spare after work and really don't want to go again through the process of resetting my phone.
Thanks.
Click to expand...
Click to collapse
you can install 7-zip zstd, then download your stock firmware, unpack AP with 7zip, then unpack super.img.lz then super.img until you have the system.img, you transfer system.img to your phone ( for example /sdcard) and select install and twrp and click images, and select your system.img and set it to system image, flash. Wipe cache and dalvik.
The easiest way is to update via smart switch and than reflash twrp and magisk. This has worked for me, the only thing is that I use orangefox instead of twrp because its much better.