Hello everyone this a little guide for rooting your Galaxy S9 and S9+ (EXYNOS) with Magisk Official
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quote:
READ THIS BEFORE ROOTING DEVICE
- In any case i'm not reponsable of the beginning of the 3rd World War if you find a way to build a time machine with this guide ! So keep your plans of the time machine in a secure place.
- Any of below said method to root will trip knox and void warranty forever.
- Root process needs wipe data so make backup of important data (including Internal Device storage) before proceed.
- As of now you will lose Samsung Pay and Secure folder forever if you root once, even unrooting won't help. (hope in future we can get it working on tripped knox device). Also you may not able to run some banking apps, you can use Magisk Hide
- OTA likely won't work once you root device.
- To unroot device completely, simply flash Samsung stock firmware, Remember, Unrooting won't revokes warranty nor you will be able to use Secure folder/Samsung Pay. Once rooted, these feature gone for you unless some magic happen in future and may find a way to use it.
Click to expand...
Click to collapse
Magisk hide 17.1 isn't working SafetyNet Fail
Take a look at the pictures at the end of this thread.
If your coming from my another thread about the Magisk 16.3 modified
1.Do a /data backup in TWRP
2.Wipe with TWRP
3.Use odin to update to the latest firmware from samsung
4.Root with this guide and restore.
Click to expand...
Click to collapse
How to proceed
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (if you don't have this option it means that your S9 is incompatible)
3.Download TWRP for S9 or S9+
4.Switch Off device
5.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
6.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
7.Select TWRP (tar image) with AP tab of Odin and Start
8.Once Successfully flashed, you will see 'Passed' in Odin tab
9.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
10.Select to allow modification
11.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
12.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
13.Flash no-verity-opt-encrypt-samsung-1.0 and then Magisk (you can also flash a kernel or xposed)
14.Once flash successfully finish, Reboot to System
14.1 Sometimes the manager doesn't install, you need to just install the manager with the link.
15.Open settings - Developer option - Look for OEM Unlock option. It will automaticaly change to unticked after some reboot don't panic! at the disco it's normal.
16.MAKE A BACKUP IN CASE OF BOOTLOADER RELOCK.
Enjoy ! You have your Galaxy S9 or S9+ watched by the organisation rooted.
Q&A:
Hey F10, why my magisk app isn't appearing or crashing when i lunch it ?
You have to delete the related folders of magisk at this path: /data/app
Hello dev, my phone is bootlooping after the flash help me plz.
You missed the dm-verity flash, just flash it.
Hi i tried to flash a kernel and i lost the root. I don't have any backup what should i do ?
Some kernel when flashing re enable the encryption of the / partition so the only way to go back is the backup. Without that you good to wipe and reflash magisk (and loosing all your data).
Does the magisk 17.2 (Beta) works on my Snine ?
Ya it's works.
Links:
Magisk 17.1 official:
[url]https://androidfilehost.com/?fid=962187416754474353[/URL]
Magisk Manager:
https://github.com/topjohnwu/Magisk/releases/download/manager-v5.9.1/MagiskManager-v5.9.1.apk
Xposed Oreo S9:
[url]https://forum.xda-developers.com/showthread.php?t=3034811[/URL]
Twrp S9:
[url]https://twrp.me/samsung/samsunggalaxys9.html[/URL]
Twrp S9+:
[url]https://twrp.me/samsung/samsunggalaxys9plus.html[/URL]
After doing this pc wont recognized phone any idea why?
yehuda2525 said:
After doing this pc wont recognized phone any idea why?
Click to expand...
Click to collapse
Check your driver.
update magisk manager
hi , i have already root my device thanks to you but with 16.3 modified version . so to update it do i need to install the 17.1 directly or i need to uninstalle it and install the new one ? thanx for the help:good:
edit : i did all this but nothing workes .
when i install it directly , after the reboot i found magisk but it crash.
i have uninstall it and reinstall but now there is no icon of it ?
ponthere said:
hi , i have already root my device thanks to you but with 16.3 modified version . so to update it do i need to install the 17.1 directly or i need to uninstalle it and install the new one ? thanx for the help:good:
edit : i did all this but nothing workes .
when i install it directly , after the reboot i found magisk but it crash.
i have uninstall it and reinstall but now there is no icon of it ?
Click to expand...
Click to collapse
Sometimes the manager disappear, you just need to reinstall it.
https://github.com/topjohnwu/Magisk/releases/download/manager-v5.9.1/MagiskManager-v5.9.1.apk
I did it but installation fail !!
Is it possible to install Magisk without TWRP on the S9+ ?
When I try to patch the boot image I get "Repackaging boot image.... ! Installation fail" The Magisk log file everything seems to work then it ends with " Cleaning up.... ! Installation failed" . I can probably patch the boot.img of the S9+ with my S7 Edge. Any idea if this would work?
yahavrave said:
Is it possible to install Magisk without TWRP on the S9+ ?
When I try to patch the boot image I get "Repackaging boot image.... ! Installation fail" The Magisk log file everything seems to work then it ends with " Cleaning up.... ! Installation failed" . I can probably patch the boot.img of the S9+ with my S7 Edge. Any idea if this would work?
Click to expand...
Click to collapse
Update with latest firmware from Samsung.
Not sure what you mean @frauchgu10. I have the latest OTA installed.
yahavrave said:
Not sure what you mean @frauchgu10. I have the latest OTA installed.
Click to expand...
Click to collapse
I don't know why but maybe this version is incompatible with this method. I will maybe do some test about that.
Maybe.. But do you think it wil work if I patched the latest boot image (for the S9+) on another phone (S7 Edge). What will happen if I try to flash it via Odin ?
Everything went smooth! Recovery installed, and rooted.
Thanks!
frauchgu10 said:
I don't know why but maybe this version is incompatible with this method. I will maybe do some test about that.
Click to expand...
Click to collapse
hi there,
im unable to root after the august 1 security patch running stock rom G965FXXU2BRGA_G965FOXM2BRG8_ILO on galaxy s9+
my phone lags then freezes permanently after flashing magisk and booting up . i haven't experienced this before the update
any ideas?
im thinking the update probably broke "No Verify Encrypt" because magisk is unable to keep dm-verity enabled .
i discovered this when opening magisk manager,the checkbox for preserve dm verity is not checked,and when i do enabled it it does nothing.tried restarting too
i tried various methods including issuing "echo KEEPVERITY=true>>/data/.magisk" command in recovery terminal after flashing magisk with no success ( i even tried flashing different magisk version ,latest version then the one before it and another one..etc) tried supersu too . i tried everything in "Magisk and MagiskHide Installation and Troubleshooting guide " documented in Magisk Troubleshoot Wiki (Didgeridoohan!)
my steps to rooting is the following :
enabling OEM unlock if not enabled
flashing twrp 3.2.3.0 star2lte
formating data then rebooting to recovery
Installing No Verify Encrypt 6.0 star zip file then rebooting to recovery again
installing rmm state bypass v2
flashing magisk ( tried different versions,customs ones too ,supersu)
rebooting to system
(gathered from various tutorials from highonandriod or other places)
What features are gone if i rooted my phone other than secure folder and samsung pay?
When rooted you can't update via OTA. Some games can detect root like pokemon go so you can not play these games without doing some tricks.
frauchgu10 said:
When rooted you can't update via OTA. Some games can detect root like pokemon go so you can not play these games without doing some tricks.
Click to expand...
Click to collapse
Okay, any others than that?
frauchgu10 said:
When rooted you can't update via OTA. Some games can detect root like pokemon go so you can not play these games without doing some tricks.
Click to expand...
Click to collapse
could you help me with my problem?
im having trouble with my device rooting,after the first boot my device freezes up and wont respond.
it seems that samsung patched some of the vulnerabilities used by the bypasses to achieve root,
after the august update. the device is unable to sustain the NO Verity OPT encrypt , the device seems to re-encrypt it self after the first boot
thanks alot man
mrwan74 said:
could you help me with my problem?
im having trouble with my device rooting,after the first boot my device freezes up and wont respond.
it seems that samsung patched some of the vulnerabilities used by the bypasses to achieve root,
after the august update. the device is unable to sustain the NO Verity OPT encrypt , the device seems to re-encrypt it self after the first boot
thanks alot man
Click to expand...
Click to collapse
I see Samsung reinforced the security I'm trying to do something about that. If you want a stable rom I suggest you to install the soldier9312 rom:
https://forum.xda-developers.com/ga...fd-n-stock-rom-soldier9312-1-0-t3771346/page1
frauchgu10 said:
I see Samsung reinforced the security I'm trying to do something about that. If you want a stable rom I suggest you to install the soldier9312 rom:
https://forum.xda-developers.com/ga...fd-n-stock-rom-soldier9312-1-0-t3771346/page1
Click to expand...
Click to collapse
okay thanks alot man i appreciate it
@frauchgu10
i came upon some new information that maybe would be helpful
ashyx ,a recognized contributor to the xda community said ,and i quote the following :
"Since Oreo Dm-verity flags are no longer in the Ramdisk. The flags are dtb based.
If the dtb isnt patched or dm-verity disabled in the kernel source then rooting will likely cause a boot loop.
Same goes for disabling forced encryption, the flags are no longer in the Ramdisk fstab, but usually located in the Vendor partition.
Magisk attempts to hex patch the kernel, but when Samsung update the firmware the hex patch offsets change and patching fails."
i hope this helps man
I truly appreciate everyone’s efforts and commitments Thank you for taking time out of your personal time to this :good::good::good::good:
Related
This morning, waking up I recieved the notification that a new magisk manager is available. I installed it as usual, except this time my device suddenly was not rooted anymore.
Si I press the install magisk button that pops up, it flashes magisk, and BAM. Phone restarts, and boot loop.
The phone's a OP5, android 7.1.1, and I had to do a factory reset twice before it would boot. Even using the magisk uninstaller did yield no results.
How come the phone suddenly got unrooted? Can I safely root it again now? Why wouldn't the first factory reset get it out of boot loop?
How can I prevent data loss in the future? Help?
Update 1 - Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.
So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)
Update 2 - TimMayle managed to run the uninstaller and re-flashing magisk v17 on TWRP, try this if you have the issue. (While the uninstaller wouldn't work for me, that might be a device specific issue.)
TimMayle said:
Hello,
I was on Magisk 16 and probably Manager 5.8.3.
Magisk 17 wouldn't flash from Magisk Manager. So I did flahs it in TWRP.
Then I was in bootloop.
In TWRPm I flashed magisk uninstaller to remove it completely and installed Magisk 17.
Bootloop Gone !
Tim
Click to expand...
Click to collapse
Update 3 - Thanks void74 for another potential procedure that might fix your issues.
void74 said:
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
I hope I have saved some lives.
Click to expand...
Click to collapse
Update 4 - Thank you Shampinger for giving ups a Linux-specific variation on the steps to follow.
Shampinger said:
Same issue here on Redmi Note 5 global (whyred). Thanks to this thread I could fix it.
Steps (on Linux):
1. boot into fastboot (vol down + power)
2. from folder with your twrp zip run:
Code:
sudo fastboot boot twrp-x.x.x-x-whyred.img
there might be an easier way to boot into recovery without having to use the zip on your computer that I don't know about
3. copy Magisk uninstaller and Magisk v17 to phone (if not already there)
4. flash uninstaller zip
5. go back and flash Magisk v17 zip
6. reboot
Click to expand...
Click to collapse
Update 5 - While a fixed version is being perfected, Mangraviti summed up what you should do:
Mangraviti said:
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
Click to expand...
Click to collapse
Update 6 - If you have Wi-Fi issues after update v17, you can attempt what TAJ_Rocks has found out:
TAJ_Rocks said:
Found fix for dead wifi
Delete this p2p supplicant.conf supplicant made wifi a c#nt:laugh:
Reboot after deleting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
+1.
Exactly the same issue. The phone lost root and is now stuck in bootloop. How to recover? Any hopes of saving the data?
Please throw some light....
Same issue here... bootloop after update. I wish I didn't update.
Oreo 8 on Huawei Nexus 6p.
Same here on HTC U11 with Lineage 15.1
Feels bad man.
How do I fix?
I fixed bootloop by uninstalling magisk with magisk uninstaller. After that I installed v16
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Same here (bootloop) after update from 16 to 17. I used unnistaller but ended in fastboot after reboot :laugh:
Had to install rom and v17 to work.
Redmi Note 5 Pro MIUI 9.6.4.0 Global
Same thing on s7 with Android 7.0 , now I'm resetting the device.
Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.
So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
ZioArturone said:
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
Click to expand...
Click to collapse
Okay, so this is guesswork at best, but if you don't wish to flash v17, what I would suggest is uninstalling the latest magisk manager, and going to your magisk folder to install the .apk of the version before.
See if you're still unrooted, then if you are, find magisk v16 either in your magisk folder, or from a download link, and flash that back on for the time being.
Didgeridoohan said:
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Click to expand...
Click to collapse
Hello,
I was on Magisk 16 and probably Manager 5.8.3. (Xperia Z3C on OmniRom).
Magisk 17 wouldn't flash from Magisk Manager. So I did flahs it in TWRP.
Then I was in bootloop.
In TWRPm I flashed magisk uninstaller to remove it completely and installed Magisk 17.
Bootloop Gone !
Tim
Didgeridoohan said:
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Click to expand...
Click to collapse
Yes. That's exactly what I did. OK. So I now ran magisk uninstaller, booted fine. Then installed clean v17.0 and it works now - no bootloop. Many thanks!
I am having the same problem with magisk manager 5.8.3 + v16 zip. After upgrading to v5.9.0(138) all my previous setting all gone. Plus i can install v17 zip at all.
This is on HTC U11+ with android v8.0
Same for me had bootloop on android 7.1.2 i was on magisk 16.0 stable. I got notification before an hour. I upadted the apk and it showed magisk not installed. So i downloaded the zip and flashed 17.0 stable zip and had bootloop. So i just cleaned cache and dalvik now phone is started and root and magsik working. But now wifi is unable to switch on
Also got a bootloop on my Samsung Galaxy S4 jfltexx running Resurrection Remix v5.8.5 (Android 7.1.2). Fortunately I took a TWRP backup before this upgrade and was able to restore it.
But I'm also without root due to Magisk Manager not offering any option other than to install Magisk-v17.0(17000).zip
Some say use the uninstaller or uninstaller.zip but where can I find this? Magisk Manager says "Magisk is not installed" and there's no uninstall-like option to be found.
ZioArturone said:
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
Click to expand...
Click to collapse
I'm in the same situation with a s6. After another device (s7) has a bootloop I don't think that i flash the v17 from the manager
gkmac said:
Also got a bootloop on my Samsung Galaxy S4 jfltexx. Fortunately I took a TWRP backup before this upgrade and was able to restore it.
But I'm also without root due to Magisk Manager not offering any option other than to install Magisk-v17.0(17000).zip
Some say use the uninstaller or uninstaller.zip but where can I find this? Magisk Manager says "Magisk is not installed" and there's no uninstall-like option to be found.
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
In "Downloads" you have "Latest uninstaller" go to recovery and flash the zip, that should uninstall magisk.
Dacraun said:
Okay, so this is guesswork at best, but if you don't wish to flash v17, what I would suggest is uninstalling the latest magisk manager, and going to your magisk folder to install the .apk of the version before.
See if you're still unrooted, then if you are, find magisk v16 either in your magisk folder, or from a download link, and flash that back on for the time being.
Click to expand...
Click to collapse
Uninstalled latest MM, installed previous version, then I installed magisk 16.0 via twrp.
It didn't work, I am unrooted.
This update ****ed up all...
ZioArturone said:
Uninstalled latest MM, installed previous version, then I installed magisk 16.0 via twrp.
It didn't work, I am unrooted.
This update ****ed up all...
Click to expand...
Click to collapse
Check the first post, I quoted someone flashing the uninstaller and flashing v17 again and it worked. Maybe that'll work for you?
I do suggest doing a total backup in twrp first though. Just in case.
Root the OnePlus 6T with no TWRP.
Required:
[*]Latest ADB/Fastboot.
[*]Have OOS 9.0.5 | 9.0.6 | 9.0.7 in place.
[*]Unlocked bootloader.
How to:
[*]Boot into bootloader
[*]Download the patched boot image 9.0.5 here.
[*]Download the patched boot image 9.0.6 here.
[*]Download the patched boot image 9.0.7 here.
[*]Drop the Patched boot image file inside your ADB/Fastboot folder.
[*]Open up a CMD window in the folder location.
[*]Type this command in CMD:
Code:
fastboot boot <filename>.img
[*]When the phone got booted download magisk manager here and install it.
[*]Open Magisk Manager and you'll see that it says that you're rooted.
[*]Make sure you checked "Preserve force encryption" and "preserve AVB 2.0/dm-verity".
[*]Click on Install and select Direct Install (Recommended)
[*]Wait till it's installed and ask you to reboot your device, reboot it.
Your'e now rooted.
If you need any help here is my telegram chat for support, or if you want to chat. here.
delete
Dark Nightmare said:
You should probably remove your telegram chat link, don't think it's allowed.
Click to expand...
Click to collapse
That's only for random links i think. i use a op6 kernel (smurf kernel) and he has his telegram chat open up for a long time.
mingo_mgx said:
That's only for random links i think. i use a op6 kernel (smurf kernel) and he has his telegram chat open up for a long time.
Click to expand...
Click to collapse
Oh okay, then disregard my comment, sorry.
mingo_mgx said:
Root the OnePlus 6T with no TWRP.
Required:
[*]Latest ADB/Fastboot.
[*]Have OOS 9.0.5 in place.
[*]Unlocked bootloader.
How to:
[*]Boot into bootloader
[*]Download the patched boot image here.
[*]Drop the Patched boot image file inside your ADB/Fastboot folder.
[*]Open up a CMD window in the folder location.
[*]Type this command in CMD:
Code:
fastboot boot patched_boot905.img
[*]When the phone got booted download magisk manager here and install it.
[*]Open Magisk Manager and you'll see that it says that you're rooted.
[*]Make sure you checked "Preserve force encryption" and "preserve AVB 2.0/dm-verity".
[*]Click on Install and select Direct Install (Recommended)
[*]Wait till it's installed and ask you to reboot your dervice, reboot it.
Your'e now rooted.
If you need any help here is my telegram chat for support, or if you want to chat. here.
Click to expand...
Click to collapse
Worked perfectly, thank you.
Sorry if this is super noob question, but you still have to unlock the bootloader to do this, correct?
Mdaly001 said:
Sorry if this is super noob question, but you still have to unlock the bootloader to do this, correct?
Click to expand...
Click to collapse
Yes
Hi, I must be missing it but where can I download the patched boot image? Also, is this the same as rooting by flashing Magisk in TWRP? I was rooted that way before but I had that bug where the phone gets stuck on the bootloader is unlocked screen, seems to be a bug in the latest Magisk so I uninstalled it and was holding off for the time being. Thx!
YrrchSebor said:
Hi, I must be missing it but where can I download the patched boot image? Also, is this the same as rooting by flashing Magisk in TWRP? I was rooted that way before but I had that bug where the phone gets stuck on the bootloader is unlocked screen, seems to be a bug in the latest Magisk so I uninstalled it and was holding off for the time being. Thx!
Click to expand...
Click to collapse
Perhaps you're not seeing the link highlighted in the OP on mobile or for whatever reason.
Anyhoo,click on the word "here",Step 2 under the "How To" sub-heading & the "here" Magisk link in the following sub-heading.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or,just click on this link,where it resides:
https://androidfilehost.com/?fid=11410963190603844693
As for the rest,perhaps someone else will chime in soon,I'm still stock/locked,last device I rooted was an Honor View 10 a few months back,have since sold.......
KOLIOSIS said:
Perhaps you're not seeing th link highlighted in the OP on mobile or for whatever reason.
Anyhoo,click on the word "here",Step 2 under the "How To" sub-heading & the "here" Magisk link in the following sub-heading.
Or,just click on this link,where it resides:
https://androidfilehost.com/?fid=11410963190603844693
As for the rest,perhaps someone else will chime in soon,I'm still stock/locked,last device I rooted was an Honor View 10 a few months back,have since sold.......
Click to expand...
Click to collapse
Whoa, there's a couple lines there that aren't showing up in the XDA Android app, one of them being the here button to download the image. of course I have to download them on my laptop but I have a Chromebook right now running Android apps, including XDA. Anyway, thank you for posting it for me ?
Ah ok, do you just not find root necessary? I am basically fine without it, especially when there is no root or it is kind of a hassle. But somehow I can't help but tinker when it's as easy as it is on this phone ?
YrrchSebor said:
Whoa, there's a couple lines there that aren't showing up in the XDA Android app, one of them being the here button to download the image. Thank you for posting it for me
Ah ok, do you just not find root necessary? I am basically fine without it, especially when there is no root or it is kind of a hassle. But somehow I can't help but tinker when it's as easy as it is on this phone
Click to expand...
Click to collapse
I plan on rooting eventually,to disable apps/services that ping back info to who knows where, & using AdAway,that's about it for the main points.
As for ROMs,the choices are awesome once all the different teams get on board,my favorite being either RR Remix or Lineage,otherwise stock/rooted OOS is just as good.
Yeah,root is easy w/this phone,even the T-Mobile version isn't all that bad.
This phone is a good bang for the buck,but,if rooting/ROMs weren't part of the eventual equation,I'd pass on it & opt for a mid-tier phone,as this is my secondary device (Note9 is my DD).
One nice thing about OnePlus phones is the past four models have been one of the better SIM/Carrier free phones to use on T-Mobile US,as they've had the latest LTE Bands & WI-FI Calling & VoLTE work.
VVM probably works as well,but,I have never used it on any phone & probably never will.
KOLIOSIS said:
I plan on rooting eventually,to disable apps/services that ping back info to who knows where, & using AdAway,that's about it for the main points.
Click to expand...
Click to collapse
I logged all the DNS lookups, and I was shocked at how much ET was phoning home.
I black-holed all the bullsh!t telemetry and analytics calls with my DNS server and in the 6T hosts file.
Thank you, works like a charm.
Couldn't we just use the magisk manager app to patch our boot image ourselves and flash it?
YrrchSebor said:
Hi, I must be missing it but where can I download the patched boot image? Also, is this the same as rooting by flashing Magisk in TWRP? I was rooted that way before but I had that bug where the phone gets stuck on the bootloader is unlocked screen, seems to be a bug in the latest Magisk so I uninstalled it and was holding off for the time being. Thx!
Click to expand...
Click to collapse
In this way did you resolve the problem?
Is there an advantage to this method, like being able to get system updates without having to flash them urself?
From a security perspective, how can we trust any images like these?
Unless the file has a digital signature from Google or OnePlus, or a least we can verify the hash, how do we know there is no 'rootkit' or some other backdoor?
No offense intended to OP.
mingo_mgx said:
Root the OnePlus 6T with no TWRP.
Required:
[*]Latest ADB/Fastboot.
[*]Have OOS 9.0.5 in place.
[*]Unlocked bootloader.
How to:
[*]Boot into bootloader
[*]Download the patched boot image here.
[*]Drop the Patched boot image file inside your ADB/Fastboot folder.
[*]Open up a CMD window in the folder location.
[*]Type this command in CMD:
Code:
fastboot boot patched_boot905.img
[*]When the phone got booted download magisk manager here and install it.
[*]Open Magisk Manager and you'll see that it says that you're rooted.
[*]Make sure you checked "Preserve force encryption" and "preserve AVB 2.0/dm-verity".
[*]Click on Install and select Direct Install (Recommended)
[*]Wait till it's installed and ask you to reboot your dervice, reboot it.
Your'e now rooted.
If you need any help here is my telegram chat for support, or if you want to chat. here.
Click to expand...
Click to collapse
Works like a charm thank you! Would you provide us with an updated patched boot file when there is an update to Oxygen OS?
I assume all of you are on tmobile OP 6t since non tmobile would get their updates via OTA, correct? Also, does applying the update in this manner wipe the existing programs on the phone, again, I assume it does since bootloader has to be unlocked and Magisk is reporting root?
And lastly, Magisk Manager newest update is 6.0.1 so is there a reason you state to download 5.8.1 in the OP? Just curious, could be just incidental...?
free4flight said:
I assume all of you are on tmobile OP 6t since non tmobile would get their updates via OTA, correct? Also, does applying the update in this manner wipe the existing programs on the phone, again, I assume it does since bootloader has to be unlocked and Magisk is reporting root?
And lastly, Magisk Manager newest update is 6.0.1 so is there a reason you state to download 5.8.1 in the OP? Just curious, could be just incidental...?
Click to expand...
Click to collapse
For OTA, remove root in current slot within magisk manager, install OTA (full zip) within OOS, don't reboot, then apply root with magisk manager on the other slot (the one where OTA have been flashed) then only you can reboot. Root is preserved.
Unofficial release -TWRP recovery for the Galaxy J6 plus 2018 - SM-J610 MSM8917
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Update 28/7/19
3.3.1-1 build released.
Current status - Beta (tested working)
Treble supported
Bugs: slight delay before touch starts working.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot and hit start.
twrp_3.2.3-1_J610_21230
twrp_3.3.1-1_J610x_28719
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
OREO ONLY: (Below is a DEFEX patched kernel for Oreo. Some root apps may not work correctly without this kernel):
https://androidfilehost.com/?fid=1395089523397922702
PIE ONLY: Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J610FXXU1BSDF_patched_boot_28719
3. Enjoy your rooted device.
DEVICE TREE: https://github.com/ashyx/TWRP_Samsung_j6primelte
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @dope77 for initial testing, @corsicanu for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
the encryption disabler is causing continuous restarts at samsung j6+ logo
dope77 said:
the encryption disabler is causing continuous restarts at samsung j6+ logo
Click to expand...
Click to collapse
It only patches the fstab in the vendor partition.
If it's boot looping it means that dm-verity is not disabled.
Did you flash Magisk first?
my bad,i flashed 17.1 which was useless and not working
reflashed 17.3 and the encryption disabler and phone booted.
twrp is fully functioning and phone is decrypted,
thank you
Will you kindly attach the proper magisk 17.3 zip file?
Rooks said:
Will you kindly attach the proper magisk 17.3 zip file?
Click to expand...
Click to collapse
follow these instructions precisely:
1. do full backup and turn on oem unlock on in developer settings
2. place the twrp in AP in odin and uncheck auto reboot in options
3. connect your phone in download mode and flash the twrp
4. reboot directly to recovery after flashing twrp by pressing power and volume down for 8 seconds while in download mode then press power and volume up when the screen goes black to boot recovery
5. after recovery boots,go to wipe and then format data and type yes,go back to twrp main menu then select reboot and reboot recvoery,after twrp boot again (phone is now decrypted),go to install and install the j6+ encryption disabler,then install magisk zip
6. go back to twrp menu and format data again then reboot
IMPORTANT NOTE:
after your phone boot,go to magisk and try to install any module ,if it fails ,go to twrp again and reflash the magisk.zip
Rooks said:
Will you kindly attach the proper magisk 17.3 zip file?
Click to expand...
Click to collapse
I have linked to it in the OP, isn't that enough?
dope77 said:
follow these instructions precisely:
1. do full backup and turn on oem unlock on in developer settings
2. place the twrp in AP in odin and uncheck auto reboot in options
3. connect your phone in download mode and flash the twrp
4. reboot directly to recovery after flashing twrp by pressing power and volume down for 8 seconds while in download mode then press power and volume up when the screen goes black to boot recovery
5. after recovery boots,go to wipe and then format data and type yes,go back to twrp main menu then select reboot and reboot recvoery,after twrp boot again (phone is now decrypted),go to install and install the j6+ encryption disabler,then install magisk zip
6. go back to twrp menu and format data again then reboot
IMPORTANT NOTE:
after your phone boot,go to magisk and try to install any module ,if it fails ,go to twrp again and reflash the magisk.zip
Click to expand...
Click to collapse
Do i need to perform a format to 'data' partition?
Would i loose all my phone apps and everything?
What about RMM Bypass?
Still touch does not work for me.
And device does not boot to os, instead boots into twrp recovery. Also power key does not work when device turns off the screen in twrp recovery. Volume keys keep the screen alive, but touch does not work.
Let me do a full odin flash.
---------- Post added at 02:40 AM ---------- Previous post was at 01:52 AM ----------
Sorry to announce but touch did not work for me even after a clean install.
---------- Post added at 02:49 AM ---------- Previous post was at 02:40 AM ----------
This file here worked for me.
Rooks said:
Still touch does not work for me.
And device does not boot to os, instead boots into twrp recovery. Also power key does not work when device turns off the screen in twrp recovery. Volume keys keep the screen alive, but touch does not work.
Let me do a full odin flash.
---------- Post added at 02:40 AM ---------- Previous post was at 01:52 AM ----------
Sorry to announce but touch did not work for me even after a clean install.
---------- Post added at 02:49 AM ---------- Previous post was at 02:40 AM ----------
This file here worked for me.
Click to expand...
Click to collapse
You do realise that is exactly the same build as the one in the OP?
Don't you mean this one?
https://androidfilehost.com/?fid=11410963190603864590
ashyx said:
You do realise that is exactly the same build as the one in the OP?
Don't you mean this one?
https://androidfilehost.com/?fid=11410963190603864590
Click to expand...
Click to collapse
The one in OP did not work for me. One i mentioned was uploaded in other thread (post # 25) on 3rd of december and it worked. Enen size is different 16.7mb and 16.9mb reletively.
Rooks said:
The one in OP did not work for me. One i mentioned was uploaded in other thread (post # 25) on 3rd of december and it worked. Enen size is different 16.7mb and 16.9mb reletively.
Click to expand...
Click to collapse
Post #25?
The only one that works is the one I've posted in my previous post which must be the same one you have used.
It seems the build in the OP was the previous not working build which I'd linked by mistake.
Now fixed.
Apologies to anyone that downloaded it, fixed version is now up.
ashyx said:
Post #25?
The only one that works is the one I've posted in my previous post which must be the same one you have used.
It seems the build in the OP was the previous not working build which I'd linked by mistake.
Now fixed.
Apologies to anyone that downloaded it, fixed version is now up.
Click to expand...
Click to collapse
One that worked for me is from other thread, labled "Twrp /Exposed" like this. You know, you and dope77 worked on.
Post # 25: Check that thread and you might find that.
Rooks said:
One that worked for me is from other thread, labled "Twrp /Exposed" like this. You know, you and dope77 worked on.
Post # 25: Check that thread and you might find that.
Click to expand...
Click to collapse
Whatever is in that thread is now in this thread.
So you must have flashed the same twrp that is posted in the OP.
It's strange to notify that my J6+ does not connect to PC after flashing latest Magisk-v18.0(18000).zip file.
ashyx said:
Whatever is in that thread is now in this thread.
So you must have flashed the same twrp that is posted in the OP.
Click to expand...
Click to collapse
iv succesfully booted my device and install some modules from magisk but i cant get through root explorer . its says my device cant run the feature . is this normal sir?
jeyph said:
iv succesfully booted my device and install some modules from magisk but i cant get through root explorer . its says my device cant run the feature . is this normal sir?
Click to expand...
Click to collapse
Go to magisk settings and disable magisk hide, go to root explorer and grant root permission.
dope77 said:
Go to magisk settings and disable magisk hide, go to root explorer and grant root permission.
Click to expand...
Click to collapse
tnx for ur response sir . it really helps . one last thing sir dope. my titanium backup keeps fc and at first it says that my device is not rooted . can u help? sorry for my noob questions . its my first time using magisk. tia
jeyph said:
tnx for ur response sir . it really helps . one last thing sir dope. my titanium backup keeps fc and at first it says that my device is not rooted . can u help? sorry for my noob questions . its my first time using magisk. tia
Click to expand...
Click to collapse
It's either not compatible with magisk or not compatible with your device rom. I also tried titanium backup on my j6+, it didn't work
It's working on my J610G
Thanks
Now im waiting For custom roms ♡
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
Welcome to TWRP for the Samsung Galaxy Tab S7+ 5G (T976B). This same image will also work for the wi-fi-only T970.
Installation
Only proceed if you are comfortable with low-level device management and are capable of recovering an unbootable device, should an unforeseen mishap occur.
Unlock your device's bootloader and then install the recovery image below. If you use Odin to flash it, remember to rename the image recovery.img and tar it before flashing. You will also need to flash a neutralised vbmeta.img image if you have not already disarmed verified boot.
Post-installation
The Tab S7+ 5G utilises proprietary file-based encryption (FBE) in its factory state for the user data partition. TWRP cannot decrypt this, however, so it must be removed. Otherwise, you will not be able to perform back-ups and restores.
To remove encryption from your device, please use TWRP to flash the Samsung multi-disabler and then format /data again. You must use at least v2.5 of the multi-disabler.
These builds are stable and known to perform well on many users' devices.
Latest releases
Android 12 (CULC firmware)
twrp-gts7xl-3.6.0_11-A12-1a7_ianmacd.img
Android 11 (BUA8 firmware)
twrp-gts7xl-3.5.0_10-A11_3_ianmacd.img
Android 10 (ATJ4 firmware)
twrp-gts7xl-3.5.0_10-2_ianmacd.img
Source
TWRP device tree for the Galaxy Tab S7+ 5G (T976B)
Kernel source code for the Galaxy Tab S7+ 5G (T976B)
TWRP source code
Support
For support or just to talk about the device amongst friends, please join our Telegram group dedicated to TWRP/root on Samsung devices.
XDA:DevDB Information
TWRP for the Samsung Galaxy Tab S7+ 5G, Tool/Utility for the Samsung Galaxy Tab S7 / S7 Plus
Contributors
ianmacd
Version Information
Status: Production
Current Production Version: 3.5.0-1_ianmacd
Production Release Date: 2020-12-29
Created 2020-09-16
Last Updated 2022-01-12
Changelog
2021-01-28 3.5.0_A11-3
First release with Android 11 kernel, built for BUA8 firmware.
Any file beginning with Magisk- is now considered flashable.
2021-01-25 3.5.0_A11-2
Fix device rebooting only to recovery.
Fix spurious attempt to perform digest authentication when flashing .apk file.
2021-01-25 3.5.0_A11-1
Report the device as running Android 11.
TWRP will now include files named Magisk.apk, app-release.apk or app-debug.apk in the list of flashable .zip files. This is to accommodate the new packaging of Magisk as a payload within the manager app.
2021-01-19 3.5.0-2
Merge post-3.5.0 release bug fixes.
2020-12-29 3.5.0-1
Update to TWRP 3.5.0.
2020-12-23 3.4.0-3
Fixed bug that causes unmounting of System when Advanced menu is entered.
2020-12-20 3.4.0-1
First production release.
Working MTP implementation.
2020-11-06 3.4.0-1a21
Fixed image back-up of Optics partition.
logcat is now enabled in recovery.
With kernel built for ATJ4 firmware.
2020-10-07 3.4.0-1a16
With kernel built for ATI3 firmware.
Super fast and superb news! Can you make it for t970, wifi only?
Thanks
+1
+++++++++1 please doo pleasssseee
Come on Ian.... :angel: Get that T870 source code and give us 11 inch wi-fi guyz some luv...
ivanox1972 said:
Super fast and superb news! Can you make it for t970, wifi only?
Thanks
Click to expand...
Click to collapse
+1 would really appreciate it if this could be done.
Would love twrp support for SM-T970 wifi. Will definitely buy you some coffee for the hard work.
Thanks. :good:
Please please please +1 +1 for T970 wifi model!!!
donation guarantee from me
Will chip in fora T970 tutorial.
Thank you.
FYI it does work on T970 but ADB is not working.. I was able to put the multi disabler and magisk zip onto my extsd card then flashed twrp, flashed multi disabler, formatted data, reboot recovery flash magisk then boot system. Keep in mind I already had my vbmeta disabled.
I then made a full backup in twrp which went just fine.
So T970 will work but adb isnt working so would need to have your files on a extsd .
EDIT: I spoke too soon.. it actually works including adb after disabling mtp.. i had something screwy with my messin with it lol.. multi disabler worked also
Got it flashed to my Tab S7+ (T970), but I don't see system as a flashable partition when trying to flash an img. Only see Boot, Recovery, Optics image, Prism image and super. I am looking to flash a a GSI
EDIT: It seems the S7+ has dynamic partitions where system.img is within super.img (which also contains other partition images). Flashing a system.img to the super partition won't do. Guess I'll have to research and wait for devs so i can figure out how to flash a GSI on this thing
Gilbot said:
Got it flashed to my Tab S7+ (T970), but I don't see system as a flashable partition when trying to flash an img. Only see Boot, Recovery, Optics image, Prism image and super. I am looking to flash a a GSI
EDIT: It seems the S7+ has dynamic partitions where system.img is within super.img (which also contains other partition images). Flashing a system.img to the super partition won't do. Guess I'll have to research and wait for devs so i can figure out how to flash a GSI on this thing
Click to expand...
Click to collapse
repack gsi into the super.img then flash super
Hello. One thing I wanted to ask. Might I use this TWRP Tree to compile SHRP?
Best Regards,
me
ivanox1972 said:
Super fast and superb news! Can you make it for t970, wifi only?
Thanks
Click to expand...
Click to collapse
mikedavo said:
+1
Click to expand...
Click to collapse
Huntyz said:
+1 would really appreciate it if this could be done.
Click to expand...
Click to collapse
vangry2020 said:
Would love twrp support for SM-T970 wifi. Will definitely buy you some coffee for the hard work.
Thanks. :good:
Click to expand...
Click to collapse
Speedy_Will said:
Please please please +1 +1 for T970 wifi model!!!
donation guarantee from me
Click to expand...
Click to collapse
Jalh said:
Will chip in fora T970 tutorial.
Thank you.
Click to expand...
Click to collapse
ssalkuwari said:
+++++++++1 please doo pleasssseee
Click to expand...
Click to collapse
The T976B image has since been verified to also work without issue on the T970..
3.4.0-1a16 released.
The image has been updated with the latest fixes from the head of the TWRP Android 10 branch, plus a kernel built to match ATI3 firmware.
ianmacd said:
The T976B image has since been verified to also work without issue on the T970..
Click to expand...
Click to collapse
Where can I send a donation to ?
ianmacd said:
The image has been updated with the latest fixes from the head of the TWRP Android 10 branch, plus a kernel built to match ATI3 firmware.
Click to expand...
Click to collapse
Can we update to this build without flashing through odin via a PC?
Also please provide a payment method so we can send money your way:good:
Edit: Just updated to the latest new build using the official twrp app works perfectly on T970.
thanks.
I have a new SM-T970 with now an unlocked bootloader. Is it save to flash this TWRP in "EUX_T970XXU1ATI2" (this is the current firmware on the tablet and no updates to "ATI3" are offered to me currently)?
One additional question: Where I can find a "neutralised vbmeta.img" for the SM-T970?
Edit2: Got it!
For everyone who is struggeling with the "neutralised vbmeta.img" as me here is the manual on how vbmeta can be "neutralised": https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
Click to expand...
Click to collapse
The file which must be flashed as "USERDATA" will be this (on bottom at the first post): vbmeta_disabled.tar
Now lets have a look if the TWRP is working on my ATI2-Firmware.
EDIT3:
Now I got everything to work:
- unlocked bootloader
- root with magisk
- "disabled vbmeta"
- flashed TWRP
- flashed "multidisabler-samsung-2.6.zip" and disabled with this the encryption
- Setup a last time and now I have TWRP and root via Magisk
Thanks everyone who helped to make the tab s7+ much more usable as it is out of the box.
Later I will try backup/restore in TWRP.
EDIT4:
So I just made a backup, wiped data and afterwards restored the backup: Success! The tablet is exact at the state where I backed it up.
So for others: I got a lot of information from this thread which are useful for the Tab S7+ also: https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353
vangry2020 said:
Can we update to this build without flashing through odin via a PC?
Click to expand...
Click to collapse
Yes. If TWRP is already installed, just choose Install from the main menu, tap Image, select the new TWRP image file and flash it to Recovery. Reboot to recovery and you'll be in the new version.
Alternatively, any Android root app capable of flashing the recovery partition can be used. Or even just dd on the command line, using a terminal program or adb to spawn a shell.
Also please provide a payment method so we can send money your way:good:
Click to expand...
Click to collapse
I don't accept donations, but I appreciate the sentiment. Thank you.
Just curious if anyone has any insight as to whether I can use the Magisk app to patch the newest boot.img (12.5.1.0 global / Android 11 / mi9t pro) and whether it will go smoothly if I install it via fastboot flash boot patchedmagiskhere.img?
I just updated the device using the clean_all mode on MiFlash and everything looks to be working fine;
No TWRP or custom recovery installed
Bootloader in unlocked state
As the update is so new I just wanted to check if anyone had any experience before I go ahead. There's also the old method of flashing magisk as a .zip via TWRP which is now 'depreciated'. As the device says 'Ramdisk NO' it implies Magisk may need to be used in 'recovery mode' (i.e. patched recovery.img and vol+power on every boot) but it worked just fine in MIUI11 so I don't think that's right.
Update: If you've come here looking to find out how to do this then I added instructions in this post.
Can't find answers so I might try fastboot boot patched_magisk.img later today. In theory this'll let me test a patched boot.img instead of going in blind with fastboot flash boot patched_magisk.img so that the boot.img isn't flashed, just booted. If it works I assume I can probably just select Direct Install in Magisk.
droident said:
Can't find answers so I might try fastboot boot patched_magisk.img later today. In theory this'll let me test a patched boot.img instead of going in blind with fastboot flash boot patched_magisk.img so that the boot.img isn't flashed, just booted. If it works I assume I can probably just select Direct Install in Magisk.
Click to expand...
Click to collapse
Hey let me know if you find a solution for this.
I upgarded to this version via TWRP last night. Tried flashing Magisk via TWRP and it kept boot looping into TWRP.
Had to re-flash the rom again in order to boot into the system.
I tried patching the stock recovery image but couldn't get the system to boot into Magisk mode. Tried the Volume Up + Power and let go on splash screen combo but it kept going to stock recovery.
Any help would be appreciated. I'll go crazy having to use the phone without root.
Update: I tried what you mentioned. Manually booting patched boot image. No luck. After showing the MIUI logo for a long time it goes back to recovery. I guess it's basically the same as flashing via TWRP.
shajman said:
Hey let me know if you find a solution for this.
I upgarded to this version via TWRP last night. Tried flashing Magisk via TWRP and it kept boot looping into TWRP.
Had to re-flash the rom again in order to boot into the system.
I tried patching the stock recovery image but couldn't get the system to boot into Magisk mode. Tried the Volume Up + Power and let go on splash screen combo but it kept going to stock recovery.
Any help would be appreciated. I'll go crazy having to use the phone without root.
Click to expand...
Click to collapse
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock firmware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
zgfg said:
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock formware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
Click to expand...
Click to collapse
This is what I have always done (patching boot). However it does not seem to be working with v12.5.1.0
I've just tried the Canary build of Magisk as well and no luck. The MIUI splash screen stays on for a while and then it goes to Recovery.
This never happened with any of the previous ROMS (Android 10)
Not sure if I'm doing something wrong.
shajman said:
This is what I have always done (patching boot). However it does not seem to be working with v12.5.1.0
I've just tried the Canary build of Magisk as well and no luck. The MIUI splash screen stays on for a while and then it goes to Recovery.
This never happened with any of the previous ROMS (Android 10)
Not sure if I'm doing something wrong.
Click to expand...
Click to collapse
You may have modules installed and enabled, that do no more work with the new firmware
If you didn't wipe/format Data, modules are still in: /data/adb/modules
(updating firmware does not affect there)
Use TWRP, go to that folder and add an empty file named: disable
(exactly as that), to each subfolder (each subfolder corresponds to one module, you may recignize them by folder names)
Then reboot with the patched boot.img
Later, manage your modules (enable, uninstall, update) from Magisk app (once you successfully boot to Magisk)
zgfg said:
You may have modules installed and enabled, that do no more work with the new firmware
If you didn't wipe/format Data, modules are still in: /data/adb/modules
(updating firmware does not affect there)
Use TWRP, go to that folder and add an empty file named: disable
(exactly as that), to each subfolder (each subfolder corresponds to one module, you may recignize them by folder names)
Then reboot with the patched boot.img
Later, manage your modules (enable, uninstall, update) from Magisk app (once you successfully boot to Magisk)
Click to expand...
Click to collapse
You Sir are an absolute LIFE SAVER!!!!!!!
Thank you!
I also patched magisk just fine . Thanks guys for sharing your experiences; it kinda reassured me it'd probably work - I was thinking booting a patched magisk boot.img might be safer so I did that first and it booted as expected. So I just returned to fastboot and flashed it properly. Installed a few modules (the essentials; ACC, Energized, Busybox), rebooted, we're all good ^_^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think it's already been explained above me but for anyone who hasn't figured it out yet:
Find the recovery zip or fastboot files you updated with (if you don't have them still then go here but use the *exact* region and version - if your device isn't raphael then don't use these), open with 7zip/winrar/whatever and copy the boot.img from them to any folder on your phone. Open Magisk Manager, browse for where you copied it to and patch it; recovery mode box unticked. Then look for Magisk_patched_xxx.img (xxx part being whatever Magisk called it) in your /Downloads folder on your phone. Copy it back to your PC, fire up Tiny ADB & Fastboot.
Do a test-run with fastboot boot Magisk_patched_xxx.img first. If it boots up fine and Magisk shows as working, commit the changes by returning to fastboot with adb reboot fastboot and then the command fastboot flash boot Magisk_patched_xxx.img. Then power it up.
If the temporary boot test-run didn't work, obviously don't execute the flash boot command; power-cycling the phone will get it unstuck.
I should probably note I don't have TWRP (using stock recovery) and I don't know how that factors into this. This was done the day after a clean_all fastboot flash; read previous posts if you've used Magisk previously and updated with your data intact.
I would like to add here to use the boot.img patch method. Flashing magisk as a zip through the recovery will cause a bootloop.
Tested this on my Mi 9T Pro (12.5.1 global) with system encryption enabled.
FPSUsername said:
I would like to add here to use the boot.img patch method. Flashing magisk as a zip through the recovery will cause a bootloop.
Tested this on my Mi 9T Pro (12.5.1 global) with system encryption enabled.
Click to expand...
Click to collapse
I was tempted to do the same because it's the conventional way of installing Magisk and it's how it's always been installed.
That and mucking with something called boot.img sounds like a one-way trip to brick-street. I.e. boot.img makes me think bootloader or in other words, bad news. Although from what I've heard it turns out you can completely screw up the boot.img and you should still have access fastboot and recovery modes. But I didn't run into any problems flashing a new boot.img so I didn't find out .
droident said:
I was tempted to do the same because it's the conventional way of installing Magisk and it's how it's always been installed.
That and mucking with something called boot.img sounds like a one-way trip to brick-street. I.e. boot.img makes me think bootloader or in other words, bad news. Although from what I've heard it turns out you can completely screw up the boot.img and you should still have access fastboot and recovery modes. But I didn't run into any problems flashing a new boot.img so I didn't find out .
Click to expand...
Click to collapse
Men, patching the images is nothing new or exotic.
If you ever read Magisk guide from TJW (the aurhor of Magisk) you would well know that the method has been described there for many years (I personally used the method back since 2018 on other phones)
Besides, it has many practical advantages - if anything goes wrong you just flash the original (unpatched) image
Or, when Magisk updates (unfortunately, it does no more and who knows would it ever again, at least from the established channels like Stable or Canary), if there is a problem with the new Magisk - you just flash your previous version of img that was patched with the working version of Magisk and you are back in business
And there is also nothing impractical here - if you have proper TWRP (you do have for this phone) you don't need to flash the patched img from fastboot but simply from TWRP
You can also use TWRP backup boot.emmc.win instead of extracted boot.img - simply give boot.emmc.win to Magisk for patching (you don't need to rename it) and then flash it
So, guys, did the patched boot image worked for you? for me it did not boot up... :/
HValenti said:
So, guys, did the patched boot image worked for you? for me it did not boot up... :/
Click to expand...
Click to collapse
Of course it does work. But read carefully above. If you just upgraded without Factory reset, and if you had Magisk before, some modules (that remained installed to /data) may cause you the bootloop
And/or, you have to patch exactly the boot.img corresponding to your current firmware, not some from an older A10, etc
In such case, how do you remove the magisk modules after the update? Without root, there is no access to modules.
HValenti said:
In such case, how do you remove the magisk modules after the update? Without root, there is no access to modules.
Click to expand...
Click to collapse
Why don't you read the previous messages in this thread - post #6
Or see:
zgfg said:
Yes, it was asked/answered several times but let it be answered again
Besides adb, there are two other ways of disabling (or even uninstalling) the remained modules
You have to flash your patched boot.img, then
a) Reboott to Android Safe mode, then reboot again to 'normal' mode.
All modules will be disabled but also you will have to re-enable Magisk Hide again
b) Use TWRP (if appropriate for your device), Advanced, File Manager, go to /data/adb/modules and to each folder (foder = module, you can recognize modules by folder names or by reading the textual file module.prop you will find inside) put a file that must be named: disable (exactly as that)
Click to expand...
Click to collapse
Or simoly read the Magisk Wiki, available from Magisk Github (linked from Magisk app):
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
zgfg said:
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock firmware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
Click to expand...
Click to collapse
My Ramdisk says "no" should I still patch boot.img?
not sure how to delete. It does work
Vanmanman said:
My Ramdisk says "no" should I still patch boot.img?
not sure how to delete. It does work
Click to expand...
Click to collapse
It says for everybode on MUII No for Ramdisk but it was discussed snd written everywhere and zillion times that Xiaomi users have to patch boot img
Can I somehow extract boot.img from phone without custom recovery and root?
Rejerf said:
Can I somehow extract boot.img from phone without custom recovery and root?
Click to expand...
Click to collapse
Download the full OTA for your phone, and from it, you can extract the boot.img.
Link for the OTA download and instructions on how to do it is provided here: https://forum.xda-developers.com/t/...-5-1-0-edit-yes-it-does.4299669/post-85271375
Please does someone upgraded succefully from 12.0.5.0 to 12.5.1.0 with root and without wiping data ?
If yes, how did you flashed the 12.5 ROM because TWRP recovery does no support MIUI 12.5 A11 encryption, so I guess flashing it from TWRP is not recomanded.
I am quite afraid to be forced to wipe everything and preserve root is mandatory for me so I did not tried to upgrade for now.
Thank you in advance.