Related
Team Win Recovery Project 3.1.1-0
This has been tested and working great on MHA-L29 international dual sim model. It will work probably on all mate 9 devices, however I added a list of supported devices below which can be checked.
WARNING #1: Unlocking BL and flashing a custom recovery voids your warranty. Please make sure to contact your carrier/seller if your phone is still under warranty after unlocking the bootloader.
WARNING #2: Make sure you have enabled OEM unlock and unlocked bootloader before trying to flash this. How you can successful root and install TWRP will be described below.
WARNING #3: I have not yet fully tested the problems of dm-verity v2.0 introduced in Nougat. So as long as you don't need to modify /system, keep it read only. If you want to edit something inside system, make a backup until I can tell you more about it.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
HOW-TO INSTALL
0. Make sure you enabled OEM unlock in settings, if you haven't please do that now by tipping 10 times on build number (to activate developer options), than open developer options and go to OEM unlock, enable it
1. Have an unlocked bootloader is required! (In my case, I called huawei and received the unlock code 12 hours later)
2. Download the TWRP recovery from the download section below
3. Make sure you got fastboot drivers installed (I will describe this below in how to unlock your bootloader)
4. Open the adb/fastboot application on your pc and go to the directory where your TWRP img file is downloaded
5. Boot your phone into download mode (First method: fastboot reboot-bootloader while connected to pc. Second method: power off your phone, hit power on and volume down until it boots to download mode)
6. Check again if there is written: unlocked phone!
7. If yes type now into your adb/fastboot terminal: fastboot flash recovery twrp-3.1.1-0-hi3660.img
8. Type: fastboot reboot
9. Now boot into recovery by pressing: power+volume up+volume down at the same time
10. Enjoy twrp
HOW-TO UNLOCK BOOTLOADER
1. Call Huawei in the HiCare app, request the bootloader unlock code there (I had to give my email, IMEI, serial number etc) or register yourself here on this link and get the code immediately!
2. You will receive an email maybe a few days or hours later with the unlock code, when you got it you can go on here
3. Install minimal adb and fastboot drivers from here: ADB and Fastboot drivers
4. Plug in your phone and make sure all huawei drivers got installed
5. Enable developer options in settings as described above.
6. Enable OEM unlock, enable USB debugging (both in developer options)
7. Open the adb tool you installed recently
8. Type fastboot devices (now a device number should show up)
9. Type fastboot reboot-bootloader (your phone will now boot into bootloader, if not, you haven't set up drivers or adb/fastboot correctly)
10. This step will wipe all your data! Type: fastboot oem unlock xxxxxxxxxxxxxxxx (xx is for your unlock code)
11. Ones it's done type: fastboot reboot. Your phone will reboot and you have an unlocked bootloader!
12. You can now go on installing TWRP on your device
HOW-TO ROOT YOUR MATE 9
0. Backup, just in case
1. Have an unlocked bootloader and TWRP installed from above
2. We will use this root method: Phh's superuser
3. Download latest official phh superuser zip r310 version
4. Put the zip on your external sd card of your phone (since we can't access /data in twrp)
5. Boot into twrp and flash the downloaded file
6. Install latest Material phh apk: Release post
7. Now you are rooted, congrats!
SUPPORTED DEVICES
MHA-L29 devices
MHA-L09 devices
MHA-AL00 devices
MHA-TL01 devices
LON-L29 devices
LON-AL00 devices
DOWNLOAD
Download v3.1.1-0
TELEGRAM CHAT
Click on the Invite link
CHANGES
v3.0.2-0 - First unofficial release
v3.0.2-1 - Added mount options for vendor, version and product. Adjusted partition table sizes. Changed brightness
v3.0.3-0 - Switched to Android 7.1 branch, got usb storage working (at least something)
v3.0.3-1 - MTP fully working (thanks to @Laststandingdroid's helps), included FBE in boardconfig for future decrypt support, some other cleanups
v3.1.0-0 - Official update to the latest TWRP version
v3.1.0-1 - Kernel update for loop support
v3.1.1-0 - Official TWRP update to latest version, Kernel updated, source updated, small changes in MTP
FEATURES
Latest stock kernel included
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
Full SELinux support
Built in android 7.1 tree
KNOWN ISSUES
Encryption is not supported yet!
Aroma is broken, seems on all other Huawei phones (as mate 8 and p9) as well
CONTACT & SUPPORT
You can find TeamWin on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: TWRP source code (7.1 branch)
Device tree (International): generic_a15 (master branch)
CREDITS
TWRP master @jcadduono
Creator of Mate 8 TWRP for source tree
CONTRIBUTIONS
Gerrit for TWRP: Omni gerrit
Gerrit for officially supported devices: TWRP gerrit
XDA:DevDB Information
TWRP Huawei Mate 9, Tool/Utility for the Huawei Mate 9
Contributors
Tkkg1994
Source Code: https://github.com/Tkkg1994/android_device_hi3660
Version Information
Status: Stable
Current Stable Version: 3.1.1-0
Stable Release Date: 2017-09-27
Current Beta Version: 3.0.3-1
Beta Release Date: 2016-12-28
Created 2016-12-09
Last Updated 2017-10-23
Reserved
Reserved
Great work! You got not only TWRP but root too!?
I will try it out later today!
duraaraa said:
Great work! You got not only TWRP but root too!?
I will try it out later today!
Click to expand...
Click to collapse
Yes. I could also disable force encryption as well.
I will probably be able to make a custom rom with aroma options etc in the near future.
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
Yes. I could also disable force encryption as well.
I will probably be able to make a custom rom with aroma options etc in the near future.
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
You literally just made my night. Thank you so much! :highfive:
Can I get root by SuperSU instead of Phh?
5[Strogino] said:
Can I get root by SuperSU instead of Phh?
Click to expand...
Click to collapse
I don't think so, but you could try and tell us.
opasha said:
You literally just made my night. Thank you so much! :highfive:
Click to expand...
Click to collapse
No problem, enjoy!
5[Strogino] said:
Can I get root by SuperSU instead of Phh?
Click to expand...
Click to collapse
I'm not a big fan of SuperSU, but you can always try with a backup (haven't tested yet)
will this method work on MHA-L29C636 variant?
thank you.
will this method work on MHA-AL00C00B135 variant?
OnimushaPooh said:
will this method work on MHA-L29C636 variant?
thank you.
Click to expand...
Click to collapse
sseedd21 said:
will this method work on MHA-AL00C00B135 variant?
Click to expand...
Click to collapse
Test and report back. If yes I will add it to working list of devices. But they should work
this mount data partition?
Tkkg1994 said:
Test and report back. If yes I will add it to working list of devices. But they should work
Click to expand...
Click to collapse
yeah, just emailed to huawei for bootloader unlock code.
BadWolfYe said:
this mount data partition?
Click to expand...
Click to collapse
If you decrypt your data. Yes
OnimushaPooh said:
yeah, just emailed to huawei for bootloader unlock code.
Click to expand...
Click to collapse
Better call them, will be much faster than with email
Sent from my SuperMan powered SM-G930F
Guys, one question : the unlock code is officially offered by Huawei everywhere? I wrote them an email (Huawei Romania) and they replied they can't offer the unlocking code that being in contradiction with the Huawei's security policy.
albireox said:
Guys, one question : the unlock code is officially offered by Huawei everywhere? I wrote them an email (Huawei Romania) and they replied they can't offer the unlocking code that being in contradiction with the Huawei's security policy.
Click to expand...
Click to collapse
I called huawei directly. Told them my IMEI, serial number and email address, a day later I had the code. So they have to release it for sure
Thank you, really !
Tanks @Tkkg1994 and @duraaraa for the work !
Tkkg1994 said:
I called huawei directly. Told them my IMEI, serial number and email address, a day later I had the code. So they have to release it for sure
Click to expand...
Click to collapse
You rooted N with phh? 0.0
Sent from my FRD-L09 using Tapatalk
---------- Post added at 10:06 PM ---------- Previous post was at 09:53 PM ----------
@Tkkg1994 may i use ur mall in OP to setup on my twrp? also nice share forgot about phh superuser only used he's su for magisk
also all i know is that chainfire's su patches DM verity properly
LastStandingDroid said:
You rooted N with phh? 0.0
Sent from my FRD-L09 using Tapatalk
---------- Post added at 10:06 PM ---------- Previous post was at 09:53 PM ----------
@Tkkg1994 may i use ur mall in OP to setup on my twrp? also nice share forgot about phh superuser only used he's su for magisk
also all i know is that chainfire's su patches DM verity properly
Click to expand...
Click to collapse
Yes I rooted N with phh and this even successful
Dm-verity is patch in phh as well so no issues here
Yes sure go ahead!
I need to get something straight, as I didn't quite get it. So the options for someone who'd like to root his S10 are 3:
1) Rooting with Topjohnwu method: This will get you root on the stock rom, but will keep the default recovery which is pretty much useless if one wanted to flash a custom rom.
2) Rooting with a prepatched version of TWRP and then, if desired, flash any custom rom (compatible with the TWRP version installed). This method is said to be less stable that the previous one.
3) Install TWRP after rooting with john wu method and then using it to flash custom rom.
First of all, is all this correct?
If so, then one has to choose between rooting safely, but keeping his phone stock, or rooting and then installing twrp and then flash whatever he desires.
Hopefully, somebody will be so kind to clarify this that is an unusually complicated situation about rooting this phone! I already regret passing my perfectly rooted S9 to my son
Thanks for whatever help you'll be willing to provide.
Cheers
I would say you summoned it up nicely.
The advantage of stock Magisk root is you can e.g. use Substratum, Magisk modules and update monthly security releases by yourself but, of course, no Custom ROMs.
The advantage of TWRP Magisk root is clearly the Custom ROM possibility but here you cannot update the monthly security releases by yourself and are dependent on the ROM creator to release the security updates.
I had been using Topjohnwu Magisk root on stock rom since released mainly to use Substratum/ some Magisk Modules and did the AP-patching everytime the monthly security was released.
However, doing the November security AP-patching something went wrong and I ended in boot-loop. So thought, as I had to reflash anyway I would try TWRP/ Custom ROM - I went with yash92Duster's lightrom / geiti94's magisk TWRP both which I find very stable.
Norup58 said:
I would say you summoned it up nicely.
The advantage of stock Magisk root is you can e.g. use Substratum, Magisk modules and update monthly security releases by yourself but, of course, no Custom ROMs.
The advantage of TWRP Magisk root is clearly the Custom ROM possibility but here you cannot update the monthly security releases by yourself and are dependent on the ROM creator to release the security updates.
I had been using Topjohnwu Magisk root on stock rom since released mainly to use Substratum/ some Magisk Modules and did the AP-patching everytime the monthly security was released.
However, doing the November security AP-patching something went wrong and I ended in boot-loop. So thought, as I had to reflash anyway I would try TWRP/ Custom ROM - I went with yash92Duster's lightrom / geiti94's magisk TWRP both which I find very stable.
Click to expand...
Click to collapse
One more doubt, if I may ask : once rooted the safe way, if I wanted to install twrp I would need to find the build that is compatible with the already patched firmware on my phone? And then only the roms that are exactly for the same build?
This is the most complicated rooting process that I have ever faced. And I've been rooting my phones and tablets since a very long time
Thanks
Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Below Method is no longer supported if you choose to use the unstable method below you do so on your own
This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
Before Starting This Process Get A USB2 Mini Hub You Are Most Likely Going Too Need It
EXTREME SYNDICATE ROOT METHOD
OEM Toggle Does Nothing On US Model Phones
This root method breaks things and most likely will not be able to be used as a daily driver
You can be on any version bootloader. This will update you to V9 bootloader
This method will work if you are on Android 10 or Android 9 Pie but will put you on Android 8 Oreo. There is no root for Android 10 or Android 9 Pie
You will not be able to use magisk
You will not be able to flash full custom rom like Lineage or any other AOSP roms however GSI system images can be used
You cannot flash custom boot images or recovery images such as regular TWRP
Odin does not work on some later computers with USB 3.1 chip controllers the only work around is using a USB 2.0 mini hub
It is your responsibility to make sure you can use adb properly
Root will break things such as safetynet so deal with it
Disclaimer:
The Extreme Syndicate team and it's affiliates are not responsible for your actions or your device if any issues are to arise. You flash this and utilize these files at your own risk. You have been warned!
Notes:
- Safestrap recovery is now available with working MTP while in Safestrap
- This does NOT trip KNOX so don't ask.
- Bootloader is of course still locked.
- This uses some partitions from combo firmware which means 80% battery.
- Each variant will have its own post in its own download section. Download the right stuff!
* Variants this should work on are: N960U/U1/W, G965U/U1/W, G960U/U1/W. If you do not have one of these variants then this forum is not for you!
- Initial files/method will leave you on Oreo stock root.
- It works on latest rev's from rev1 up to the most recent revs.
- As of the initial first release, all variants have an issue with MTP not working except while in Safestrap
- S9 and S9+ also might have some issues with the selfie cam.
- Note 9 @elliwigy
- S9+ @klabit87
- S9 @jrkruse
- Telegram Support Group for All 3: https://t.me/joinchat/DxwvAlhtzHjg4EI9973BGQ
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed as a zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Downloads S9 Files:
Safestrap_S9_Cmd_Line.7z
Download S9+ Files:
Safestrap_S9_Plus_Cmd_Line.7z
Download Note9 Files: -- Only For Bit 8 Or Lower
Safestrap_N9_Cmd_Line_Bit8.7z
Instructions to Inject Safestrap:
1. Download and unzip Safestrap_S9__Cmd_Line.7z for your device
2. Plug phone into computer and run Safestrap.exe
3. Follow instructions on screen to enable USB Debugging
4. Then from there the process will be mostly automatic just follow prompts on screen
5. When done flashing BootSwap file you need to hold the buttons to boot to recovery but since we swapped boot and recovery images it will boot system.
Instructions For Flash Rom:
1. Download below files and copy files for rom to phone system img and vendor img and odm zip
Downloads S9 Files:
Stock_Rom_G960.7z
GSI_Rom_G960.7z
Download S9+ Files:
Stock_Rom_G965.7z
GSI_Rom_G965.7z
2. In safestrap flash system img then vendor img and odm zip .
3. Choose data wipe and advance and check data
4.. Now reboot system you will have to hold buttons to reboot to recovery until you see safestrap splash then click continue. You must do this on every reboot. If you do not it will reboot to stock recovery. If it reboots to stock recovery just reboot system and hold buttons to reboot to recovery again.
5. When rom is booted up your computer will not recognize the phone for mtp file transfer. Adb does still work so you can transfer stuff that way (you need to switch to ptp transfer method in the dropdown) or use USB adapter and use a thumb drive.
6. Biometrics do not work so don’t try to setup fingerprint or face recognition.
The GSI rom mtp works GSI rom is rooted already just flash phhsupersu.apk found in GSI_Rom zip
If using other GSI roms you have too choose A_Only ones and will probably need to flash the Sh_Remover.zip found in the GSI_Rom zip
ShoutOuts:
@elliwigy For the method and help and everything else
@klabit87 - Ditto
@me2151 - Ditto
@gsm-CHEN - Ditto
@mweinbach - For always posting my achievements on the XDA News portal as well as giving me someone to troll sometimes when bored.
@ShaDisNX255 - He was our best tester, give him credits for testing out GSI as well!
@everyone else I am forgetting!
ENJOY!
Mine
Wow, this is actually pretty good. S9 Snapdragon + treble enabled device? Man, this is going to change everything! I hope something good comes out of this
Does it work on the U/U1 variants of the S9+ as well?
krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified
krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It’s confirmed working on both SM-G960U/U1 and SM-G965U/U1
Sent from some device I modified
Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.
Argyrus said:
Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.
Click to expand...
Click to collapse
You cannot trip knox on a locked bootloader
Sent from some device I modified
jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?
Argyrus said:
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?
Click to expand...
Click to collapse
Did you not read la couple post above yoir question
Sent from some device I modified
jrkruse said:
Did you not read la couple post above yoir question
Sent from some device I modified
Click to expand...
Click to collapse
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.
Argyrus said:
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.
Click to expand...
Click to collapse
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified
jrkruse said:
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified
Click to expand...
Click to collapse
Awesome, sorry for any confusion.
jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
jrkruse said:
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified
Click to expand...
Click to collapse
That means I can have root and have Samsung pay? God damn that makes me wet
Dhdeanha said:
That means I can have root and have Samsung pay? God damn that makes me wet
Click to expand...
Click to collapse
As of right now it's still detecting su binaries. So Samsung Pay probably may not work.
On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?
elguy said:
On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?
Click to expand...
Click to collapse
Don't worry about it. It will work on it, it's been proven to work exactly on Android 9, Dec 2019 security patch.
Wow! that's exciting, I can't wait until this releases. Looks like I'm not updating my phone anymore until then. Especially exciting if it works on Android 9 December 2019 security patch
the question is how likely this will be patched in Samsung's next update and how much time this may cause them to delay their next security patch.
Extreme Syndicate Root for S9 is live!!
Hi
I just successfully rooted my OnePlus Nord CE 5G, but I didn't use a custom recovery to do it. I still miss the features of custom recoveries, essentially the low-level backups.
I searched the Internet for TWRP and OrangeFox, I like both and have used them on previous devices. However, I couldn't find anything for this phone.
Does anyone know how to get that working on Nord CE? Or if there is any low-risk way of trying random recovery builds in the phone, and be able to re-flash the stock recovery if it goes wrong?
Did you make any progress on this?
diegolag said:
Did you make any progress on this?
Click to expand...
Click to collapse
None at all. I was waiting for answers here.
I guess that
- nobody really has specific knowledge about this on Nord CE
and
- the people who have generic knowledge about whether it's risky or not to flash random recoveries and recover with stock recoveries... those people aren't reading this thread.
I personally can't try anything risky, I am already relying on this phone as my main professional tool... and personal gadget.
pgorod said:
None at all. I was waiting for answers here.
I guess that
- nobody really has specific knowledge about this on Nord CE
and
- the people who have generic knowledge about whether it's risky or not to flash random recoveries and recover with stock recoveries... those people aren't reading this thread.
I personally can't try anything risky, I am already relying on this phone as my main professional tool... and personal gadget.
Click to expand...
Click to collapse
Well, then you have not bricked your phone as I did trying to root it without making a backup first
Good to know, I haven't found a solution yet
Right now orangefox android 11 tree is not released (if yes , i dont know), but twrp has. And already custom twrp compiled for ce but needs development and testing.
Right now I need storage on my personal pc , this weekend i will insert new ssd for development on CE (4. SSD ) . First target to see stable twrp (hope it will be official maybe) and then we can compile some roms kernels etc. But i will compile only gapps inbuild roms .
And second news, trying miui cam port to CE . Hope it will work . OxygenOS cam software is trash for me.
Here is the link to the TWRP thread:
[RECOVERY] [11] [ALPHA] TeamWin Recovery Project (ebba) (2021-09-09)
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Bricked mine too, but a repair request with 1+ was my way out. Without costs btw.
Doesn't solve the no backup issue ofcourse.
!PdK said:
Bricked mine too, but a repair request with 1+ was my way out. Without costs btw.
Doesn't solve the no backup issue ofcourse.
Click to expand...
Click to collapse
Can you please tell us exactly how you bricked it? Was it by installing the new TWRP available in the thread I linked?
Yes, by flashing incorrect TWRP to device and trying to update afterwards. Ended in booting into crashdump all the time.
Now discovered the a/b slots could have been the issue.
!PdK said:
Yes, by flashing incorrect TWRP to device and trying to update afterwards. Ended in booting into crashdump all the time.
Now discovered the a/b slots could have been the issue.
Click to expand...
Click to collapse
Did you tried latest msm? Should be fixed.
Already had it fixed by 1plus service request and now updated to 11.11 fw
Hi all, i have a build OrangeFox 11, but need testers.
Yes twrp recovery is available for nord ce 5g
I updated my s9 ultra to Android 13 a few weeks early. Then I tried to get the root back following the below thread.
Root Guide for Galaxy Tab S8/S8+/S8Ultra
See post #3 for in depth guide ! ->insert usual general disclaimer of liability Required: Odin3_v3.14.1 flash tool Samsung USB Driver installed Frija or something else, to download stock files 7zip or similar 1: Unlock bootloader (will wipe...
forum.xda-developers.com
On that day, the newest magisk version was 25.0, I followed all the steps in the above thread but the device was still bricked (boot loop).
I searched the error log and figured out that this was due to something called "avb flag":
Samsung system init check fstab avb flag cause boot loop · Issue #6141 · topjohnwu/Magisk
Device: Samsung Tab S7 Plus (T976B) Android version: 12 Magisk version name: 25.2 Magisk version code: 25201 For some reason, samsung decided to make their /system/bin/init check for avb flags in f...
github.com
Since I don't have much time on this, I simply did a factory reset and kept using the tab without root.
I am actually not sure whether the "avb flag" is the root cause. The only thing I am sure of is using magisk 25.0 and s8ultra android 13 ROM leads to a boot loop.
Today, I found that magisk is now updated to 25.3, and nobody here mentioned the boot loop.
So, I want to know whether magisk 25.3 is working well with the newest ROM. If it works OK, I will give it another try.
I have a Tab S8 Ultra which was on Android 12 / OneUI 4.1 rooted / Magisk. I just finished updating it to Android 13 (image SM-X906B_2_20221208191241_81t9w4gald_fac) without any dramas. I did a factory reset before flashing the patched AP, not sure if that helped avoid any potential bricks or you were just unlucky.
I'm only on Magisk 25.2 though - I don't see the 25.3 that you mention anywhere. So make sure you're downloading from topjohnwu's GitHub page, not some other sketchy place. That might be a factor.
FerretallicA said:
I have a Tab S8 Ultra which was on Android 12 / OneUI 4.1 rooted / Magisk. I just finished updating it to Android 13 (image SM-X906B_2_20221208191241_81t9w4gald_fac) without any dramas. I did a factory reset before flashing the patched AP, not sure if that helped avoid any potential bricks or you were just unlucky.
I'm only on Magisk 25.2 though - I don't see the 25.3 that you mention anywhere. So make sure you're downloading from topjohnwu's GitHub page, not some other sketchy place. That might be a factor.
Click to expand...
Click to collapse
Well, I think “25.3” is a typo. I always download the magisk APK from github. I also tried a factory reset.
May the issue is already fixed in a way. I'll try it again some time.