Database Users

[HOW-TO][ROOT][Unlock BL] Sony Xperia Z3 Tablet Compact

/*
* Your warranty is (probably) now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about rooting
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* PLEASE READ THE ENTIRE THREAD BEFORE YOU DO ANYTHING!
*/
Please leave a reply if this worked or didn't work. I will be most grateful! Thanks
Hi there!
I present the best, the easiest (mm maybe not) and most proper way to root and flash a custom ROM on your Sony Xperia Z3 Tablet Compact!
Requirements:
- A basic understanding of Rooting and Android Development
- ADB and Fastboot (Have a google for Minimal ADB And Fastboot)
- A windows PC (I am not sure how to root with mac, although I am sure it is the same process)
- OEM Unlocking Enabled on your Device.
Don't know how to enable OEM Unlocking? Do this:
Settings -> About Device -> Tap Build Number 7 Times - Back -> Developer Options -> OEM Unlocking -> Enable
Also, if you ever get a message saying: Allow USB Debugging, do this:
{
"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"
}
We'll start with Unlocking your Boot loader. I might as well point out that this will remove ***ALL*** of your apps and files etc. I should also say that you will lose some capability features - such as the Camera may not be as good - although to be perfectly honest I haven't noticed any changes!
Lets start right away: Bootloader
What is your Bootloader?
Your bootloader is a part of your android device that when unlocked, allows you to do lots of things with it! This includes rooting (Like we are now :laugh, flashing recoveries and more.
Is it safe to do this?
As long as you follow my steps, you should be ok. But I have warned you.
Now head to here. This is the official Bootloader unlocking page. Scroll down to the device selection and put in "Z3 Tablet Compact"
Connect your tablet to your compter,
Do the steps it asks and... done!
Congratulations, your Bootloader is Unlocked!
It may seem silly, but for me, this is the only Hard part!
Now let's flash our TWRP!
Before you do this, make sure you have booted after unlocking your Bootloader. I dont know if it will make a huge difference, but I did it, so you should as well. It worked for me like that
What is TWRP
TWRP is a Custom Recovery
Wow, helpful. :laugh: What's a custom recovery?
As android central say:
In Android, recovery refers to the dedicated, bootable partition that has the recovery console installed. A combination of key presses (or instructions from a command line) will boot your phone to recovery, where you can find tools to help repair (recover) your installation as well as install official OS updates.
This means it is a way of changing things that you can't change if you are booted into System (System is Usual Home screen etc...)
Is TWRP Safe?
It's only ever as safe as you are! - Just make sure you flash (install) the right version!
We start by flashing TWRP.
Head to http://twrp.me and click on Devices. Find specifically YOUR version if the Tablet (scorpion_windy is the NON-LTE Version).
Download it.
Drag that file into an empty folder. Then in the address bar, type "cmd"
A black window should pop up.
In this window, type: adb devices
This should display your device.
Now type: adb reboot bootloader
You should now have a blue light on your device.
You cannot perform adb commands anymore! You now are in Fastboot mode. I dont need to explain that, but you need to know that!
Now type: fastboot flash boot twrp-xxxx-scorpion(_windy).img
Congratulations, TWRP Recovery is now Flashed!
(Provided it says everything is ok. )
Our last step is rooting This is an easy task, but requires TWRP - hence why we installed it.
Grab the latest copy of SuperSU from supersu.com - make sure you get the XPERIA SuperSu - and boot into twrp. (Booting into twrp can be done by mashing volume keys after holding down the power key and it vibrates haha). Press install and find your copy of SuperSU (which you should have loaded onto your tablet beforehand). Swipe to flash, and done!
If your tablet bootloops (doesn't turn on), Install a custom rom. I am currently using: this unofficial lineage (14.1).
To do this, boot into TWRP and press install. Find your Rom file (Like you did for Rooting) and swipe to flash. (Make sure you wipe data, system, cache and dalvik beforehand!). You can now reflash your SuperSU Zip and bam, rooted.
You may also want GApps (Google Apps). So head to opengapps.org and select the right package for you. When you flash GApps, make sure you do right after you flashed the rom (dont boot after flashing your rom.)
When I am flashing something I will normally do this:
TWRP -> Wipe -> Advanced Wipe -> System, Cache, Data, Dalvik Cache -> Back -> Install -> ROM -> Add more Zips -> GApps -> SuperSU -> Back -> Reboot -> Reboot system.
Hopefully, you should now be rooted with a custom rom and all. Enjoy!
I should point out that (At the time of writing this) I am only 12 years old. If I have made a few mistakes, please correct me! Thank you

MajorPlayz said:
Now type: fastboot flash boot twrp-xxxx-scorpion(_windy).img
Click to expand...
Click to collapse
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.​...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.

XperienceD said:
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.
...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.
Click to expand...
Click to collapse
Well actually I did fastboot flash boot twrp.img
This works perfectly fine for me

XperienceD said:
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.
...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.
Click to expand...
Click to collapse
What's 291 sorry?

MajorPlayz said:
Well actually I did fastboot flash boot twrp.img
This works perfectly fine for me
Click to expand...
Click to collapse
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
MajorPlayz said:
What's 291 sorry?
Click to expand...
Click to collapse
The FW version.

XperienceD said:
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
The FW version.
Click to expand...
Click to collapse
Ok cool

XperienceD said:
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
The FW version.
Click to expand...
Click to collapse
I may be mistaken though, so if it bricks the device, use Sony's Emma flash tool
It's a pretty useful tool (if you don't have just Google: Sony Emma)

MajorPlayz said:
I may be mistaken though
Click to expand...
Click to collapse
Just tried it on the off chance it might work but doesn't, it just writes the recovery to the boot partition so will only boot to TWRP, just flashed the recovery partition again and now not getting any light. It's a strange one this, going to stick my method.

XperienceD said:
Just tried it on the off chance it might work but doesn't, it just writes the recovery to the boot partition so will only boot to TWRP, just flashed the recovery partition again and now not getting any light. It's a strange one this, going to stick my method.
Click to expand...
Click to collapse
Weird ?
I'm using the SGP612 So there might be a difference? I'm assuming your using 621 (You mentioned PoC)
My friend did the command but he told me that is what it was. I'll grab the full list of commands from him, but flashing twrp was definitely to boot!
Nevermind haha!

MajorPlayz said:
Weird
I'm using the SGP612 So there might be a difference? I'm assuming your using 621 (You mentioned PoC)
Click to expand...
Click to collapse
SGP611, I just don't get it.

XperienceD said:
SGP611, I just don't get it.
Click to expand...
Click to collapse
Weird

For those with any trouble and that can't flash twrp, a full procedure for injecting TWRP into the kernel is here:
https://forum.xda-developers.com/showpost.php?p=74528751&postcount=22

Just out of curiosity, about how much battery power does it take to flash the custom ROM to solve the bootloop problem (which happened to me) and are there any other ways of flashing a custom ROM that do not consume battery power?

Ishtvan said:
Just out of curiosity, about how much battery power does it take to flash the custom ROM to solve the bootloop problem (which happened to me) and are there any other ways of flashing a custom ROM that do not consume battery power?
Click to expand...
Click to collapse
Hi there, sorry for long reply - I've been inactive for quite a while as I didn't have a device to hack with. My tablet unfortunately died!
Anything done on a device, whether it be playing games, streaming media, or using TWRP Recovery will consume Battery.
The un-bootloop problem will take charge from your device, but it is safe to keep the device plugged in, charging, whilst you perform the commands.
If all else fails, use Emma as I mentioned before.

hi,
Following this "how-to" everything fine till end of bootloader unlock.
going under developper option, and can't find OEM unlock
trying to make :
Code:
fastboot flash boot twrp-3.0.2-0-scorpion_windy.img
[sudo] Mot de passe de youb*:*
target didn't report max-download-size
sending 'boot' (12372 KB)...
OKAY [ 0.410s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.413s
Trying under linux and then window 7, same error
I ticked usb debug and paired with my laptop.
don't know what to do now ( I'm under firm 23.5.A.1.291)
edit:
ok working, reflash same firmware (us version) and then flash this kernel
glimmling said:
Hi,
I made a boot.img for the SGP612 [6.0.1] [23.5.A.1.291] unlocked BL.
Sony RIC disabled
TWRP 3.0.2
(DRM fix)
Root and Xposed is NOT included. I recommend flashing Magisk v12 later in TWRP and enable Magisk Core Only Mode and Magisk Hide in the settings. Then it will pass the SafetyNet test and you can use su.
To flash the boot.img, put your SGP612 into fastboot mode (Volume Up + connect USB) and then run:
Code:
fastboot flash boot boot.img
If you have a backup of your TA partition, before you unlocked, see the rootkernel thread by tobias.waldvogel, how the DRM fix works.
Thanks to codfx for give me the idea for a SGP612 counterpart and to tobias.waldvogel for his tool :good:
Click to expand...
Click to collapse
from https://forum.xda-developers.com/z3-tablet-compact/development/kernel-t3472019/page2

hazote said:
hi,
Following this "how-to" everything fine till end of bootloader unlock....
Click to expand...
Click to collapse
Where you able to get this working?
Sorry for the very late reply.

Here you find some more details incl. Magisk root instructions: https://forum.xda-developers.com/showpost.php?p=78588234&postcount=14

Hello, i hope people will be able to help me, i've been stupid and tried rooting my tablet without the necessary knowledge , from what i understood i flashed twrp on boot instead of recovery and now i can't use my tablet at all.
Is there a way to get the old system back ?

lacarte said:
Hello, i hope people will be able to help me, i've been stupid and tried rooting my tablet without the necessary knowledge , from what i understood i flashed twrp on boot instead of recovery and now i can't use my tablet at all.
Is there a way to get the old system back ?
Click to expand...
Click to collapse
Have you tried Flashtool: http://www.flashtool.net/index.php ?

[Tutorials] How To Root Lenovo K8 Note & Install TWRP(UnOfficial) + Stock Rom

Warning
Before Proceeding backup your data
TRY at OWN risk I'm NOT Responsibe if you BRICK YOUR DEVICE
Update- This method is tested & working with latest ota update NMB26.54-74
[/CENTER][/B][/SIZE][/COLOR]
IF ANYTHING GOES WRONG Download & Flash Stock ROM
Stock ROM link
SPFlashTool link
Updated Stock ROM 54-74 GDrive - here
New Oreo 27.43-20 Link
Old version Stock ROM Google Drive Link Stock Rom
nvram backup file by @peacelover94 - here
Solution For
>Tool img DL fail
Just check/tick these option in spflashtool settings & Flash stock rom again
{
"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"
}
Video Guide For Stock Rom Flashing - Youtube
How to Flash Stock Rom via Fastboot Method -
1. Open CMD by Shift + Right Click in Folder where your stock firmware .img files are.
2. Reboot to Fastboot Mode by using cmd command
adb fastboot reboot​Or
Switch off then Press & Hold Vol Up + Power button for while once menu appeared Select fastboot by using Vol Up key & confirm by pressing Vol Down Key
3. In fastboot type following command in CMD Window
For checking devices is connected in fastboot enter
fastboot devices​If Connected then proceed following commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img​ flashing system takes 10+ mins
fastboot flash data userdata.img
fastboot reboot​
Download & Install ADB from here
First Unlock your bootloader
1. First of all, enable the Developer Option
To Enable the Developer Option, Go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2. Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3. Now connect your phone to Computer using USB Cable.
4. When you connect your Phone to Computer, please wait until all the drivers get installed.
5. Open a command prompt window by pressing Shift Key + Right Mouse Click.
6. Now type the command below to reboot your phone to bootloader
adb reboot bootloader​7. If you see a pop up to allow USB Debugging on your phone, Click OK.
8. proceed to unlock the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
fastboot oem unlock​Say Yes to unlock bootloader and then it will some time format your data
9. Reboot Your Device , You will see Orange Status bla bla bla Don't panic Its normal thing now setup your device but do not restore backup yet
Flashing TWRP and ROOT
Updated Black Screen Fix TWRP - Download
Old Download TWRP
Download latest Magisk zip from here
Or
SuperSu zip from here
Flahed & Tested SuperSU v2.82 works fine but SafetyNet Fails
Sock Recovery if needed Link
1. Connect your device to PC
2. Open CMD by Shift+Right click open cmd where your TWRP_3.1.1.0.img is downloaded.
3. Reboot to Bootloader by
adb reboot bootloader​4. Now enter following command in fastboot
fastboot flash recovery TWRP_3.1.1.0.img​5. DO NOT USE fastboot reboot
Use "vol up + down + power button" to manually switch off you k8 note, otherwise twrp will restore to stock if you use fastboot reboot command.
6. After Switch Off Press & hold vol up + power button then select recovery by vol up & press vol down key to enter in recovery.
7. Now Wait for 30 Sec/ till phone vibrates, Then press power button + vol up simultaneously until you see twrp lock screen.
8. Just Cancel if It asks for Enter password to decrypt and Allow modification by swipe.
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
10. GoTo install browse and select Magisk.zip or SuperSU.zip & flash.(optional if needed install Busybox for Android NDK by osm0sis magisk module for busybox)
11. Reboot Enjoy.
Known bug in TWRP-
Battery always shows 50% in TWRP
Video Guide https://youtu.be/HrbppEWlOhs
Join Lenovo K8 Note Development Group on Telegram for direct Conversation Link
WhatsApp Group Link
Enable Wireless Display/MiraCast Magisk Module - Video
Thanks to:
@andy_zhang - for stock rom post link
and me @ysalunke007 for TWRP
NEXT CUSTOM ROM

Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?

Yes
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link

ysalunke007 said:
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link
Click to expand...
Click to collapse
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.

flash via adb fastboot methoad i have succesfully flash adb method
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse

Nice Job
Finally rooting tutorial for Lenovo K8 Note has become available.

Does SuperSu work fine?

Anas Rahman said:
Does SuperSu work fine?
Click to expand...
Click to collapse
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.

peacelover94 said:
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.
Click to expand...
Click to collapse
Yes it's SP flash tool but you can use adb fastboot also

ysalunke007 said:
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.
Click to expand...
Click to collapse
I'll confirm it tomorrow

ysalunke007 said:
Yes it's SP flash tool but you can use adb fastboot also
Click to expand...
Click to collapse
Please tell me how to flash firmware.Im new to this device firmware flashing

lenrussel said:
Please tell me how to flash firmware.Im new to this device firmware flashing
Click to expand...
Click to collapse
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1

Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.

peacelover94 said:
Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.
Click to expand...
Click to collapse
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000

lenrussel said:
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000
Click to expand...
Click to collapse
Thanks for the reply. Anyhow got a work around for downloading from baidu using chrome extension, without account. Just wanted to confirm whether the firmware zip is working fine. If some one used it and been successful, please do tell me.

ysalunke007 said:
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1
Click to expand...
Click to collapse
Do i have to unlock bootloader again after flashing the firmware in order to root the device?

lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.

peacelover94 said:
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.
Click to expand...
Click to collapse
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also

lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
No need to unlock bootloader again if you use fastboot method to flash stock firmware , & for spflashtool I'm not sure but I think it remains unlocked

lenrussel said:
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also
Click to expand...
Click to collapse
No error while extracting firmware downloaded from baidu

[RECOVERY] [OFFICIAL] TWRP 3.6.x for Galaxy A10 Exynos series [SM-A105] [4 January 2022]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Installation
Method 1
1) If you already have twrp on your phone, extract recovery.img from the tar file using Zarchiver (Download here).
2) Reboot your phone and boot into recovery.
3) Flash the recovery.img as "recovery"
4) Finally reboot to recovery to enjoy new twrp 3.6.x
Method 2 (WARNING: YOU WILL LOSE YOUR DATA)
1) If you are installing a custom recovery for the first time, open Odin on your pc. Download both the latest recovery and the vbmeta_disabled file attached below. Boot your phone in download mode.
2) Untick "autoreboot" and flash the vbmeta_disabled.tar file in the AP slot.
3) Follow the instructions on your phone's screen to reboot the phone.
4) Quickly repeat the steps to go back in download mode.
5) Untick "auto reboot" and flash the recovery.tar you downloaded in the AP slot
6) Follow the instructions on your phone's screen to reboot the phone.
7) As soon as the screen turns off, release all keys and press power + volume down keys till you boot into twrp 3.6.x
8) Go to wipe, and format your data.
9) Flash disable_dm_verity.zip (attached in post) in twrp to avoid fbe error.
10) You now have twrp 3.6.x
Download
Twrp 3.6.x for A10
Maintainer
Gabriel260
Support
Contact maintainer on telegram to report any bug → Gabriel
Thanks
TWRP team
Topjohnwu for root
afaneh92
Topser99

Fix etc/fstab "system_root" to "system" please

Thanks for this amazing build. Never ceases to surprise me.

can we have this twrp without root on phone .... ?
sorry for my silly question

Can you install this on the A10e? (A102)

koyo said:
Can you install this on the A10e? (A102)
Click to expand...
Click to collapse
no

howdeedodat said:
can we have this twrp without root on phone .... ?
sorry for my silly question
Click to expand...
Click to collapse
yeah

UPDATE NOTICE:
Twrp 3.5.1 released

Chatur27 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Installation
Method 1
1) If you already have twrp on your phone, extract recovery.img from the tar file using Zarchiver (Download here).
2) Reboot your phone and boot into recovery.
3) Flash the recovery.img as "recovery"
4) Finally reboot to recovery to enjoy new twrp 3.5.1
Method 2 (WARNING: YOU WILL LOSE YOUR DATA)
1) If you are installing custom recovery for the first time, open Odin on your pc and load the tar file (download below) in the AP slot.
2) On the left of Odin, click on options and untick (remove the tick from) "autoreboot"
3) Boot your phone into download mode and connect it to the pc.
3) Flash the file in Odin. When flashing is complete in Odin, hold power + volume down keys on your phone to reboot
4) As soon as the screen turns off, release all keys and press power + volume down keys till you boot into twrp 3.5.1
5) Go to wipe, and format your data.
6) Flash disable_dm_verity.zip (attached in post) in twrp to avoid fbe error.
7) You now have twrp 3.5.1
Download
Twrp 3.5.1 for A10
Maintainer
Gabriel260
Support
Contact maintainer on telegram to report any bug → Gabriel
Thanks
TWRP team
Topjohnwu for root
afaneh92
Topser99
Click to expand...
Click to collapse
Where is the tar file?

LemonadeSnake said:
Where is the tar file?
Click to expand...
Click to collapse
Download and install 7zip and right click "recovery.img" file > Select 7-Zip from openned menu>Select "Add to Archive" > Replace "Archive Format" to TAR > Click OK > Wait To Compressing... ANDD Ready your TAR file, WALA!
Nice Day!

What has changed compared to the previous version?
Thanks for ALL!

CrazyGenius said:
Download and install 7zip and right click "recovery.img" file > Select 7-Zip from openned menu>Select "Add to Archive" > Replace "Archive Format" to TAR > Click OK > Wait To Compressing... ANDD Ready your TAR file, WALA!
Nice Day!
Click to expand...
Click to collapse
well too late oof i tried another method by somebody else and my phone is now bootlooping

EDIT:
Okay, now everything works, I did it according to this tutorial:​[Guide/Magisk] Root for the Galaxy A10 Series & Flash TWRP (Unlocked Exynos only, A10s not supported)​
Hello,
I have a problem installing TWRP, turned on OEM unlock, then unlocked the bootloader, then when the phone rebooted and went into OEM setup it was turned off so I turned it on. I put my phone into download mode and tried to load twarp via Odin and got the message "Only official released binaries are allowed to be flashed (RECOVERY).
Now, after starting the phone, when I enter programming options, the OEM unlock option is gone
Can I do something about it now? I have SM-A105FN
{
"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"
}

LemonadeSnake said:
well too late oof i tried another method by somebody else and my phone is now bootlooping
Click to expand...
Click to collapse
If you want to get rid of this thing, you can download the Official Firmware, extract it from the compressed file (and extract AP* file), make the necessary changes (replace stock "recovery.img" with TWRP img file, replace stock "vbmeta.img" with custom vbmeta and sarees...) and re-compress all extraxted and changed files to TAR file. Unselect "Auto Reboot" from Odin, select modified AP file from Odin AP menu and flash. If flashing complated, reboot phone directly recovery mode and flash all files.

CrazyGenius said:
If you want to get rid of this thing, you can download the Official Firmware, extract it from the compressed file (and extract AP* file), make the necessary changes (replace stock "recovery.img" with TWRP img file, replace stock "vbmeta.img" with custom vbmeta and sarees...) and re-compress all extraxted and changed files to TAR file. Unselect "Auto Reboot" from Odin, select modified AP file from Odin AP menu and flash. If flashing complated, reboot phone directly recovery mode and flash all files.
Click to expand...
Click to collapse
i can't access download mode without a jig, because it can't even get to the samsung loop animation without restarting.

JUST A NOTICE:
Twrp for A10 is now official !
Cheers

koyo said:
Can you install this on the A10e? (A102)
Click to expand...
Click to collapse
koyo said:
Can you install this on the A10e? (A102)
Click to expand...
Click to collapse
If you need twrp please send me stock recovery.img

Topser99 said:
If you need twrp please send me stock recovery.img
Click to expand...
Click to collapse
I don't have the phone. I was gonna buy it on the basis that it had TWRP but it doesn't so I bought the Moto G7 Play

Staniczek said:
EDIT:
Okay, now everything works, I did it according to this tutorial:​[Guide/Magisk] Root for the Galaxy A10 Series & Flash TWRP (Unlocked Exynos only, A10s not supported)​
Hello,
I have a problem installing TWRP, turned on OEM unlock, then unlocked the bootloader, then when the phone rebooted and went into OEM setup it was turned off so I turned it on. I put my phone into download mode and tried to load twarp via Odin and got the message "Only official released binaries are allowed to be flashed (RECOVERY).
Now, after starting the phone, when I enter programming options, the OEM unlock option is gone
Can I do something about it now? I have SM-A105FN
View attachment 5251963
Click to expand...
Click to collapse
If you are 100% sure of having your bootlaoder unlocked, reflash the stock rom you are on. It worked for me yesterday night.

Chatur27 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Installation
Method 1
1) If you already have twrp on your phone, extract recovery.img from the tar file using Zarchiver (Download here).
2) Reboot your phone and boot into recovery.
3) Flash the recovery.img as "recovery"
4) Finally reboot to recovery to enjoy new twrp 3.5.1
Method 2 (WARNING: YOU WILL LOSE YOUR DATA)
1) If you are installing custom recovery for the first time, open Odin on your pc and load the tar file (download below) in the AP slot.
2) On the left of Odin, click on options and untick (remove the tick from) "autoreboot"
3) Boot your phone into download mode and connect it to the pc.
3) Flash the file in Odin. When flashing is complete in Odin, hold power + volume down keys on your phone to reboot
4) As soon as the screen turns off, release all keys and press power + volume down keys till you boot into twrp 3.5.1
5) Go to wipe, and format your data.
6) Flash disable_dm_verity.zip (attached in post) in twrp to avoid fbe error.
7) You now have twrp 3.5.1
Download
Twrp 3.5.1 for A10
Maintainer
Gabriel260
Support
Contact maintainer on telegram to report any bug → Gabriel
Thanks
TWRP team
Topjohnwu for root
afaneh92
Topser99
Click to expand...
Click to collapse
Can you install this on the a10 sm-a105m Android 10?

LineageOS starts booting, but then phone goes to Qualcomm Crash Dump Mode

Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.

Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.

Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.

MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock

Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?

Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.

@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.

Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!

Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.

Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"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 forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?

freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.

MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.

MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.

Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?

freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.

MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?

No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.

But adb seems to work, adb devices returns my phone ID.

It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.

Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)

Samsung S8/S8+ TWRP & Root / Magisk Guide - SM-G955F Tested [2022]

XDA has helped me with many previous projects, its about time I gave back to this community. I have been trying to fix my Samsung S8+ which took 3 to 4 guides from this forum and combining into one.
From what I can tell, pre-2019 was a lot easier to do and a lot of old posts remain up which no longer work and can lead people to semi-brick the devices and send them boot looping. This guide is working as of 30th September 2022.
Pre-requirements:
- Samsung Drivers.
- Odin 3.13.1 (exactly this version for s8/s8+).
- PC with USB-C cable.
Flash latest Firmware, stock. - Sammobile Downloaded.
Using Odin 3.13.1 (required for s8/s8+) flash first 4 options.
During first boot:
- Skip all options to connect to stuff.
- Set time months in the past.
Once first booted/setup completed:
- USB Debugging ON (always trust).
Reboot.
Connect to WiFi / Internet.
Reboot.
OEM Unlock ON (won't have to wait as auto-unlocks).
CMD Terminal - adb reboot bootloader
Odin AP - TWRP - Turn auto-reboot off under options.
Hold Volume Down and Power to reboot.
Once off, Hold Power, Volume Up and Bixby till vibration, let go and wait to TWRP Recovery.
In TWRP, Read Only mode.
Go to Wipe > Format Data.
Hit back in menu, Reboot to Recovery.
In TWRP, Read Only mode.
TWRP Folder will now be accessable by connecting to PC.
Place RMM Bypass v3 and Disable_Dm-Verity_ForceEncrypt_11.02.2020 (at time of guide) onto the phone.
Install RMM Bypass v3.
Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.
Reboot to System.
At this stage, 2 things can go wrong:
- No boot at all. In which case begin from beginning. Phone isn't bricked if boot looping. Hold Power and Volume Down during one of the loops and enter into Recovery mode. You can then start the process again to stock always.
- First boot will work. Setup the phone, on restart however it will say only official binaries are supported. Do above again. This is referenced below.
During setup, set the date backwards once again. Skip all other options.
Reboot the phone to check all is functional, follow above if fails to boot, else continue.
TWRP is now fully installed. With RMM disabled.
Installing Magisk is done via transfering the Magisk file, use preferred method. If you need a way transfer it over via TWRP as we did above for KMM zip. This guide will show this method.
From the booted phone, unlocked, CMD Terminal - adb reboot recovery
Once TWRP has booted and the phone appears in PC, transfer Magisk APK over to phone.
In TWRP, navigate to Install and install Magisk.
Reboot System.
You should now have a rooted (with Magisk if needed) Samsung S8/S8+ !

Thanks buddy! Worked for me, very useful information! Appreciated!

This guide is just confusing and lacking any hint at where to acquire RMM Bypass v3 and Disable_Dm-Verity_ForceEncrypt_11.02.2020.
Also does the guide suggest flashing the magisk apk as an apk in twrp without renaming it to .zip?
A guide should provide at least indication of where to get required files as well as include all prerequisites at beginning.

I'm noob, i would need files and more specific informations on how to do it. I have rooted in the past, but didn't manage it for years

I've been following this guide and it did help me, although the OP has missed some links and description making it difficult for non-experts to follow through. Let me try to fill the gaps and make it more informational.
RMM Bypass V3​
Download -
RMM-State-Bypass-v3-corsicanu.zip | by RC Chuah for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
XDA Thread - https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
XDA Post with latest binary - https://forum.xda-developers.com/t/...ynos-samsung-after-2018.3747535/post-79745844
Blog for context - https://www.thecustomdroid.com/prenormal-rmm-state-on-samsung-galaxy-guide/
Disable_Dm-Verity_ForceEncrypt_11.02.2020​Download : https://androidfilehost.com/?fid=17248734326145725184
XDA Post : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
GitHub: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt
Latest S8+ Firmware​You are on your own.. find which version you had first, but mostly this should work for India
Download Samsung Galaxy S8+ SM-G955F DBT Germany G955FXXUCDVI1 firmware
Fast download latest Samsung Galaxy S8+ firmware SM-G955F from Germany with G955FXXUCDVI1 and Android version 9
www.sammobile.com
If you need to understand the rooting process in depth, this video will help as reference, BUT BUT BUT
REMEMBER that the video is backdated and what OP mentioned is more recent. So do your due diligence in understanding the difference and applying accordingly.

Regarding flashing Magisk, for me flashing via recovery did not work.
Downloaded latest APK 25.2 APK and renamed it to .zip and flashed via TWRP - no luck. Flashing completed but Magisk Manager keeps saying not rooted.
Tried following the official Samsung Android 9.0 guide here https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
That also kept failing while trying to patch the AP file. What finally worked is that I patched it on another android device. Apparently S8+ file access permissions does not play well with Magisk apps for some reason.
Once AP is patched you can open up the AP file in 7zip and take the boot.img to flash from recovery
Make sure to
Install RMM-State-Bypass-v3-corsicanu
and
Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.
after installing new patched boot.img
OR
you can follow the official guide.
If following official guide - remember to flash DM verity and RM Bypass zips at proper timing (I did not do this way and I am not sure here).

Debaucus said:
XDA has helped me with many previous projects, its about time I gave back to this community. I have been trying to fix my Samsung S8+ which took 3 to 4 guides from this forum and combining into one.
From what I can tell, pre-2019 was a lot easier to do and a lot of old posts remain up which no longer work and can lead people to semi-brick the devices and send them boot looping. This guide is working as of 30th September 2022.
Pre-requirements:
- Samsung Drivers.
- Odin 3.13.1 (exactly this version for s8/s8+).
- PC with USB-C cable.
Flash latest Firmware, stock. - Sammobile Downloaded.
Using Odin 3.13.1 (required for s8/s8+) flash first 4 options.
During first boot:
- Skip all options to connect to stuff.
- Set time months in the past.
Once first booted/setup completed:
- USB Debugging ON (always trust).
Reboot.
Connect to WiFi / Internet.
Reboot.
OEM Unlock ON (won't have to wait as auto-unlocks).
CMD Terminal - adb reboot bootloader
Odin AP - TWRP - Turn auto-reboot off under options.
Hold Volume Down and Power to reboot.
Once off, Hold Power, Volume Up and Bixby till vibration, let go and wait to TWRP Recovery.
In TWRP, Read Only mode.
Go to Wipe > Format Data.
Hit back in menu, Reboot to Recovery.
In TWRP, Read Only mode.
TWRP Folder will now be accessable by connecting to PC.
Place RMM Bypass v3 and Disable_Dm-Verity_ForceEncrypt_11.02.2020 (at time of guide) onto the phone.
Install RMM Bypass v3.
Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.
Reboot to System.
At this stage, 2 things can go wrong:
- No boot at all. In which case begin from beginning. Phone isn't bricked if boot looping. Hold Power and Volume Down during one of the loops and enter into Recovery mode. You can then start the process again to stock always.
- First boot will work. Setup the phone, on restart however it will say only official binaries are supported. Do above again. This is referenced below.
During setup, set the date backwards once again. Skip all other options.
Reboot the phone to check all is functional, follow above if fails to boot, else continue.
TWRP is now fully installed. With RMM disabled.
Installing Magisk is done via transfering the Magisk file, use preferred method. If you need a way transfer it over via TWRP as we did above for KMM zip. This guide will show this method.
From the booted phone, unlocked, CMD Terminal - adb reboot recovery
Once TWRP has booted and the phone appears in PC, transfer Magisk APK over to phone.
In TWRP, navigate to Install and install Magisk.
Reboot System.
You should now have a rooted (with Magisk if needed) Samsung S8/S8+ !
Click to expand...
Click to collapse
What means
"Using Odin 3.13.1 (required for s8/s8+) flash first 4 options."?
I don't see the connection to the text before or after.
As far as I understand it I do the following:
1) I update the firmware (I'd prefer to just use smartswitch for this)
2) boot the phone (set time in the past, don't connect to stuff)
3) Activate Debugging
4) reboot, connect to WLAN
5) reboot, OEM unlock
6) CMD Terminal - adb reboot bootloader
---> for what do I do this?
Couldn't I just use the correct buttons and boot into download mode?
...Because the next step is
7) Install TWRP via Odin
8) Install RMM Bypass v3 and Disable_Dm-Verity_ForceEncrypt_11.02.2020 ( I would do this via SD card)
9) Install Magisk
Thank you for your manual. It's just that people like me don't "get it" completely
I have rooted a couple of phones and installed different lineage or CM versions, but I lack the deeper understanding that you have.
___________________________________________________
Aside from that, is there a reason not to just follow the Instructions from Rootmygalaxy instead? It seems way easier to someone like me.

Okay, I got it as far as I see it.
My questions with the "Odin 4 options" cleared itself up after I downloaded the firmware.
I followed the guide to the letter and everything worked well.
Installing magisk got me in a bootloop though. I reinstalled everything and went without magisk.

According to root checker and another app, I do not have root access. This surprises me a little.
But at least installing TWRP and a custom ROM worked well.

How do I CMD? In windows or on the s8 itself? Confused about that part?

Shonenjack said:
How do I CMD? In windows or on the s8 itself? Confused about that part?
Click to expand...
Click to collapse
CMD means command prompt from windows. you can either type adb reboot bootloader if you have adb installed to turn phone to download mode, or use vol- + Bixly + power together to download mode

For S8 China and Hong Kong variant 9500. You never seen OEM Unlock in the developer option. But you have to do the same steps for installation of TWRP and custom rom.

anyone can install Magisk successfully into 9500 with newest rom TGY-G9500ZHS6DUD1? I've installed TWRP but failed to install Magisk. always bootloop once installed magisk...

When I try to flash TWRP I get an error in odin saying it failed to flash and an error on the device saying "Only official released binaries are allowed to be flashed" at the top of the odin/download mode screen and the progress bar just sits at almost full. I'm guessing I'm getting these errors because I'm trying to flash TWRP which isn't official samsung firmware.
I have zero idea on how to fix the error, I even tried this but I was unsuccessful.
This *could* have something to do with the fact that this was originally a Telstra phone, but I did flash stock (non telstra) firmware and the issue persists.
All I need is TWRP to do anything that I need to, but it just isn't working.
Any help is appreciated, and thank you to everyone who tries to help.
{
"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"
}