Related
Team Win Recovery Project 3.1.1
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
{
"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"
}
#include <std_disclaimer.h>
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country, European Union for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
Download:
Galaxy S8 (dreamlte - Exynos vaiants - G950F/FD/N/X)
https://twrp.me/devices/samsunggalaxys8.html
Galaxy S8+ (dream2lte - Exynos variants - G955F/FD/X/N)
https://twrp.me/devices/samsunggalaxys8plus.html
Sources:
https://github.com/TeamWin
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - General Discussion
Join to get quick support (when you find my guide confusing or meet any unexpected problem).
You can also discuss about ROMs(this group is "neutral" so you can discuss about or review any ROM. Note: Devs: Do NOT aggressively advertise your work.), get latest updates from developers or report possible bugs.
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
XDA:DevDB Information
TWRP for Galaxy S8 and S8+, Tool/Utility for the Samsung Galaxy S8
Contributors
jesec
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2017-04-24
Last Updated 2018-07-22
Changelog:
Aug. 02:
Merged AQG kernel updates from Samsung.
NOTE: AQG or later bootloader is supported and REQUIRED from this version.
May. 30:
Possible fix for I/O problems.
Backported latest F2FS from Linux 4.12.
Minor kernel updates.
Apr. 27:
Problems Solved:
1. MTP
2. ADB
3. External SD Mount
Features Added:
F2FS - Note: This change ONLY makes it possible to operate F2FS in TWRP. You still need a F2FS-compatible KERNEL to boot into system with F2FS.
Note: As MTP and ADB are available now, flashable zips will no longer be included. Please download them by yourself and transfer them from your computer to phone if you need them.
Useful Links:
Disable dm-verity and make encryption optional: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Magisk: https://forum.xda-developers.com/apps/magisk
Apr. 24:
Initial Release
Guides:
Notice: It may wipe all your data including those in internal storage.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Awesome
Great work thank you very much
Sent from my SM-G955F using Tapatalk
if i wipe data partition in order to disable encryption - is that like erasing my phone and starting from scratch? will i lose all my data?
nk33 said:
if i wipe data partition in order to disable encryption - is that like erasing my phone and starting from scratch? will i lose all my data?
Click to expand...
Click to collapse
Yes you will, make sure you've backed-up as much as you can to your Google Cloud Storage. I promise, it's worth it.
Many Thanks
Kevin_R said:
Yes you will, make sure you've backed-up as much as you can to your Google Cloud Storage. I promise, it's worth it.
Click to expand...
Click to collapse
Thanks.
And if i just install TWRP, and then the root zip file to give me root will it all work ok? will i achieve root ok?
I spent ages getting this phone just like i want it and seriously cant be bothered to do it all again - will i be ok keeping encryption on if all i want to achieve is root?
what will i lose out on if i dont disable encryption?
nk33 said:
Thanks.
And if i just install TWRP, and then the root zip file to give me root will it all work ok? will i achieve root ok?
I spent ages getting this phone just like i want it and seriously cant be bothered to do it all again - will i be ok keeping encryption on if all i want to achieve is root?
what will i lose out on if i dont disable encryption?
Click to expand...
Click to collapse
I found that if I didn't disable the encryption, root wouldn't work as it couldn't mount the file system to make the relevant changes
---------- Post added at 02:19 PM ---------- Previous post was at 02:14 PM ----------
Anyone managed to get Samsung Pass and Secure Folder working? I have Magisk Hide running and Knox Trip is emulated to 0x0. Other apps that would normally detect root don't detect it but Samsung Pass and Secure Folder still can.
Is superSU SR3 working??
its a great work
anyone tried if Samsung Pay still works after this? I have not got my phone yet.
Just for info tried installing the SuperSU binary through TWRP but, as TWRP seems to have no access to the SD card, the flash failed and left me in a boot loop.
Reinstalling TWRP from Odin and reflashing Magisk solved the Boot loop issue.
SuperSU did kill the Knox processes for me though to stop the annoying nagging notifications.
If after flashing from Odin, phone says that needs restore, Just press volume up Bixby Power, wait, then format data, Power off. Now ho back in download mode, reflash with odin, done.
It works all', except personal area and Samsung health
would this work on the SM-G950FD?
if i use this method i lose warranty ? is it possible to do evrything later on normal without having any trouble ?
Phone brick...LOL...
help : just tried to root my g950f Uk 02 - i've flashed it a few times and used the two flash but im getting verification failed and it wont erase anymore when i try use the recovery flash i get invaled mount /data when using that decrypt .zip in flashables do i need to redo the stock firmware and start again?
i am still waiting for my S8(exynos) to arrive and here comes the twrp i did not even wished yet....
I found an app called package signer from https://forum.xda-developers.com/android/software/tool-package-signer-1-0-t3533073 to sign the zip files in android to fix signature verfication error in some recoveries....
Developer stopped development of that app...
and also that thread is closed...
It signs correctly but one issue is, it can't able to sign zips that are greater than 20mb ......
It force closes when working with large zip files...
It is open source is github....
Sir osm0sis i have seen you are helping in zip signers..
Can you please help....
I hope some developer can fix this and post below.....
Please help by fixing that force close error of signing big zip files......
Thanks in advance...!
Edit:- See https://forum.xda-developers.com/t/...-apk-zip-within-android.3835975/post-81324327 for solution.
Nope, you should use zipsigner.jar from my Complete Shell Zip + Signing thread.
osm0sis said:
Nope, you should use zipsigner.jar from my Complete Shell Zip + Signing thread.
Click to expand...
Click to collapse
Since I dont have pc... i am using that sir...
HemanthJabalpuri said:
Since I dont have pc... i am using that sir...
Click to expand...
Click to collapse
It should work on device too if dexed, I'll add it to my thread and post instructions soon.
Reserved this too
DISCLAIMERS (please read !)
The content seen in this thread is targeted at this specific forum's device, the Realme C12, codenamed RMX2189.
Follow the instructions shown in this thread at your own risks, I will not be held responsible for bricking your device, you did this yourself.
That said, the information will be kept up to date relatively frequently, and should you follow the steps and ask questions below when unsure, everything will be fine!
No files will be directly provided. Do not use pre-created/re-uploaded content. Instead I'll teach you to gather the required files from official websites, and create the other ones yourself.
ROM (GSI) Recommendations:
Ordered by personal preference:
1) CAOS
2) LOSQ (LineageOS GSI)
3) crDroid
I'm more than open to feedback, suggested changes & improvements!
Prerequisites for most manipulations:
Your phone, well charged if possible
The USB cable used to link your phone to your computer (the one on your charger works just fine)
A computer, with recent ADB & Fastboot (Platform Tools)
Some time, patience, and the ability to read and follow instructions!
Unlock your bootloader (otherwise this thread is useless to you as it's required for rooting as well as installing custom ROMs)
Tutorial:
Step 0 - Great! You're ready to go. Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 1 - Download and Open In Depth Tool ( Attached With the Guide Down)
{
"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"
}
Step 2 - Click “Start applying”.
Step 3 - Please read the disclaimer in detail, select the checkbox, and submit your application
Step 4 - The Application Will be checked by realme Servers..(Wait 10 mins)
Step 5 - The unlock tool apk will show the status of the unlock request- Successful
Step 6 - You can now click “Start the in-depth test” and the device will reboot automatically. The following string will display on the screen: fast boot_unlock_verify ok
Step 7 - Now Download and install the fastboot tool on your PC and ready to unlock it.
Step 8 - Now in Fastboot Mode type this command
Code:
fastboot flashing unlock
and Press enter.
Step 9 - On your phone press the Volume Up key to select "UNLOCK THE BOOTLOADER” (or press the Volume Down key if you have changed your mind to select "DO NOT UNLOCK THE BOOTLOADER”). When you click the Volume Up, your phone will reboot and enter the in-depth test mode - all user data on the phone will be erased - I recommend you perform a data backup prior to applying.
Step 10 - Now type
Code:
fastboot reboot
And there you go! Your phone will reboot and you can set it all up again, with the ability to follow the rooting tutorial below, and you can also install GSIs/custom ROMs/recovery!
Rooting with Magisk
Tutorial:
The procedure is the same whether you're on the stock RealmeUI Rom or on a custom GSI (treble) one.
Step 1 - Download the latest Magisk Manager on your phone.
Go to the link above, click the latest MagiskManager-vX.X.X.apk you see in the list to start the download, open the file and install.
Step 2 - Download the latest Realme Official Rom from Software Update - realme depending on your region.
Step 3 - Get your ROM you downloaded above, it should be a .ozip archive. Add .zip extension to it. Extract it.
Step 4 - You should now get a folder like shown below, and..
Copy the boot.img to your phone's /sdcard/ folder (where the Android, DCIM, Download, and more are present, just drop it in there).
And here's how it shoud look inside your phone's storage in the end.
Step 5 - On your phone, open up Magisk Manager.
Click the Magisk Install button as shown below.
Then Select and Patch a File.
Go look for your boot.img you previously copied to your phone and pick it.
Click Let's go! and wait for Magisk to complete the process!
Step 6 - Link your phone to your PC, and grab the file the Magisk Manager created. It's located in your downloads folder, called magisk_patched.img.
Step 7 - Paste it where your ADB & Fastboot (Platform Tools) are located, along with the vbmeta.img file located in Stock ROM's images folder from earlier, where you grabbed the original boot.img.
You should now have a folder like this with:
adb(.exe)
fastboot(.exe)
magisk_patched.img
vbmeta.img
Extra files from the platform tools
Step 8 - Alright, we're ready to root! Turn off your phone, and get in fastboot mode like we did during the bootloader unlocking (Power + Volume Down).
Step 9 - Link your phone to your PC with the USB cable if not done already.
Step 10 - Shift + Right click in an empty space inside the folder we prepared in Step 7, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.
Code:
adb reboot bootloader
fastboot devices
And make sure your device shows up, should be a bunch of numbers and letters, a couple spaces, and fastboot.
If nothing does, go back to Step 8 and try again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
You're done! Your phone will reboot, hopefully, without a hitch! Open up Magisk Manager, and check that it's installed.
That said, you will have issues leaving it like this. You need to hide the fact that your phone is rooted, there's no downside to doing it.
Check out the Passing SafetyNet tutorial further down below, it's quick and easy.
Getting EdXposed (Not recommended unless really needed, requires Magisk)
I very much do not recommend to EdXposed your phone unless you have a very good reason for it. It's a pain to pass SafetyNet, doesn't get updated as often as it could/should and has very niche use cases for which it's worth it.
That said, I do include it here for people who know what they're getting into and want the up-to-date instructions on how to do it.
Tutorial:
This procedure requires to be rooted with Magisk. See the tutorial above.
Step 1 - Inside Magisk Manager, go to the Modules tab (4th icon), click the search button (bottom right) and search Riru.
Step 2 - Install the Riru (Riru - Core) module, Activate it and Reboot.
Step 3 - Install the Riru - EdXposed (YAHFA or SandHook, both work fine) module, Activate it and Reboot.
Step 4 - Download and install the latest EdXposed Manager in the exact same way you did with Magisk Manager.
Step 5 - Open it up, it should say EdXposed Framework is active!
You're done! You should now be able to install EdXposed modules.
That said, you will have issues leaving it like this. You need to hide the fact that your phone is EdXposed.
It's a bit more complicated than hiding Magisk, but it's doable! Check out the Passing SafetyNet tutorial further down below, it's quick and easy.
Passing SafetyNet (Only possible with Magisk. Not with SuperSU on GSI's)
Tutorial:
For Magisk Rooted PhonesEnable Magisk Hide inside Magisk Manager's settings.For EdXposed PhonesAgain, I highly recommend not EdXposing your phone and sticking to just Magisk if you can help it.
You should also know that this method will show you're passing SafetyNet inside Magisk but it's a pain to do and isn't as well hidden as Magisk alone.
Step 1 - Do the step for Rooted phones listed above if not done already.
Step 2 - In EdXposed Manager, get the HiddenCore Module and activate it.
Step 3 - Now, in the side-menu: Compat List > tick HiddenCore Module.
Step 4 - Then, go to Settings > Framework > Enable "App List mode".
Step 5 - Finally, Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Google Play Store, Google Services FrameworkReboot and enjoy! You're all set and SafetyNet should pass just fine.
Installing GSI's (Custom ROMs)
Tutorial:
Step 1 - Pick your poison in the Treble Forums!
Check the top of this thread if you want to see my recommendations with links to them.
Step 2 - Download the chosen ROM, A/B Arm64 version (usually nicknamed b), with (g) or without GApps (v), rooted (S) or not (N), that's entirely up to you.
It should be an .img.xz file, extract it and you'll get an .img file.
You're ready to flash. Make sure to backup your phone's data before continuing on with this tutorial, as wiping it is required for installation!
Step 3 - Put your phone into fastboot mode (Power + Volume Up) and link it to your PC.
Step 4 - Move the .img file you downloaded to your ADB & Fastboot (Platform Tools) folder, and rename it to system.img.
Step 5 - Shift + Right click in an empty space inside the folder, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.
Code:
fastboot reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot -w
fastboot reboot
Your phone will now reboot on its own, using the new ROM you picked earlier, set it all up and enjoy!
Relock your bootloader
Tutorial:
Step 0 - Back to stock ROM by flashing it in stock recovery.
Step 1 - Download the unlock tool again to apply to exit the in-depth test.
Step 2 - Click “Apply to exit in-depth test”. You should manual operation enter the Fastboot mode(Press both the Volume up button and the Power button when power is off).
Step 3 - In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
- Enter the command: adb reboot bootloader
- Press “Enter” on your keyboard
- Enter the command: fastboot flashing lock
- Press “Enter” on your keyboardStep 4 - Press the Volume Up button to select the “Lock bootloader” option (or press the Volume Down button to select “Do not lock bootloader" and keep it unlocked).
Step 5 - Then enter command fastboot reboot. The phone will reboot and exit the in-depth test mode. All user data on the phone will be erased - we recommend you perform a data backup prior to applying.
Frequently Asked Questions (FAQ)
Q: Will unlocking my bootloader void my warranty?
A: No, it will not. Unless you brick your device.
Q: Hey, I rooted/edXposed my phone, and now Netflix won't even open, or doesn't work properly, what's up with that?
A: Well, fortunately, there's an easy fix if you have Magisk. Install the liboemcrypto disabler Magisk module, activate it and reboot.
Q: I tried unlocking my bootloader but, PC doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Realme USB Drivers manually from here.
Q: Alright, I did a bunch of manipulations but something went wrong, or I'm tired of it, how do I reset everything, etc..
A:
Step 1 - Backup all the data you might have on your phone to restore it after the manipulation!
Step 2 - Download the stock ROM corresponding to your region from Software Update - realme.
Step 3 - Put the stock rom in your mobile Internal Storage or in Memory Card.
Step 4 - Put your device into recovery mode (Turn it off, then Power + Volume Down) and flash that in recovery.
Step 5 - Reboot to stock rom, all good and fresh!
Hi all,
At my work we are using an android tablet and I need to install root on it. The tablet is a SkyDroid H16. The weird thing is that "adb root" works fine and I can remount /system and add files, but apps cannot see that there is root.
How can I install su and use it.
There is no TWRP for it and the stock image is also not public.
Senna-chan said:
Hi all,
At my work we are using an android tablet and I need to install root on it. The tablet is a SkyDroid H16. The weird thing is that "adb root" works fine and I can remount /system and add files, but apps cannot see that there is root.
How can I install su and use it.
There is no TWRP for it and the stock image is also not public.
Click to expand...
Click to collapse
Root Android Devices without TWRP RecoveryTo root your device without TWRP Recovery, you need to perform two steps. Firstly, the device needs to be booted using the patched boot image file. In the next step, this boot image file will be permanently flashed using the Magisk Manager app. Don’t forget to have a look at the ‘Prerequisites’ section below, before beginning with the process. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.
Prerequisites
Download and install the Magisk Manager APK file on your device: Magisk App [from version 22 onwards, it is known as Magisk App and has both the Magisk ZIP and Manager APK file bundled together].
Next up, check if your device has ramdisk or not. For that, launch the Magisk app and refer to the section under Magisk, if it says YES, then you are good to proceed ahead (see below image). On the other hand, if it says NO, then you will have to head over to our alternative guide: Install Magisk in Recovery and Root Android [No Ramdisk].
{
"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"
}
The bootloader of your device should be unlocked. Have a look at our guide on how to do so.
Enable the ‘USB Debugging’ option. Go to ‘Settings’ -> ‘About Phone -> Tap on Build Number 7 times -> Go back to Settings -> Developer Options -> Toggle on the USB Debugging’ switch.
Although rooting is going to wipe your data, still, it is recommended to make a complete backup of all your data.
Keep your device appropriately charged, at least to a minimum recommended level of 50%
Install ADB and Fastboot Tool for entering Fastboot commands.
Also, download and install the USB Drivers for your device. This helps in successfully connecting your device to the PC.
STEP 1: Get Stock Boot.img File from Stock ROM
To begin with, you will have to extract the stock boot.img file. And as opposed to earlier times, the process is a little bit more complicated nowadays. You cannot simply extract the firmware and get the required partition files (such as vbmeta.img, system.img, boot.img, etc). The reason is that many OEMs packs the ROM’s IMG files inside an encrypted package. For example, OnePlus has these files inside payload.bin, Realme, and Oppo have their files inside the OZIP format, and so on. In that case, you may refer to our below guides to get the stock boot.img file:
Now that you have got hold of the stock boot image file, it’s time to patch it via Magisk and flash it via Fastboot Commands. We have listed the steps for both the older as well as the newer build of Magisk Manager. As far as the difference between them goes, it’s just some UI tweaks here and there, the underlying functionality remains the same. The below update is only for devices running Android 11. If your device isn’t running that version, then you may directly head on to STEP 2A/2B.
UPDATE 1 [FOR ANDROID 11 USERS ONLY]: Quite a few Android 11 users are facing issues while patching the stock boot.img file via Magisk manager. Well, I have found the fix to this issue, please refer to our detailed guide on the same: Fix Magisk patched boot.img issue while Rooting Android 11. If you wish to save a click, then here’s the explanation in short:
You have to install the Magisk Canary build instead of the stable and then change the update channel to Canary from within the app itself. Once you have done the said change, you may then proceed with the below steps to patch the stock boot image file using Magisk and flash it via Fastboot commands. [END OF UPDATE 1]
STEP 2A- Patch the Stock Boot Image File using Older Magisk
Download the stock firmware for your device.
Extract the boot.img file from it.
Transfer it to the device’s internal storage.
Install the Magisk Manager App on your device.
Open it. Tap on the first ‘Install‘ button, next to Magisk status.
In the next menu, again chose ‘Install‘.
Now select ‘Select and Patch a File‘.
Navigate to internal storage and select the stock boot.img file that you extracted earlier.
Let Magisk do the patching process. When it’s done, copy this patched boot.img file, named as magisk_patched.img, from your device (will be present under Internal Storage > Downloads) to PC where you have installed the ADB and Fastboot Tools (inside the platform-tools folder).
How to Update Magisk ZIP and Magisk Manager (without TWRP)
Disable DM-Verity or Android Verified Boot without TWRP
Fix Magisk Module Bootloop without TWRP Recovery
How to Root Android Devices Without TWRP Recovery
STEP 2B: Patch Stock Boot Image File using Newer Magisk
Launch the Magisk Manager app on your Pixel device.
Then tap on the Install button situated next to Magisk.
From the Method section, choose Select and Patch a file.
Browse to the extracted boot.img file and select it.
Then tap on the Let’s Go option situated at the top right.
Magisk will now load the boot.img file and will patch it accordingly. Once that is done, you would get the Download Complete message.
The patched boot image file will be saved in Internal Storage > Downloads. The name of the file will be magisk_patched.img.
Now that you have patched the stock boot.img file, it’s time to flash it onto your device and hence obtain root without TWRP. There are two different methods through which you could do this. This patched boot.img file could either be flashed via Fastboot or through Magisk. It is highly recommended that you proceed with the Fastboot Method. Only in case, if you face any issues, then you should proceed with the Magisk Method. The reason being the fact via the Magisk method, we will be using the DIrect Install feature, which seems to be absent in most devices. Hence to avoid any confusion, you should try the Fastboot Method. If you face any error, then only proceed with the Magisk method to root your Android device without TWRP.
STEP 3A- Install the Patched Boot Image using Fastboot
Connect the device to the PC via USB Cable.
Now transfer the patched boot file from your device to the platform-tools folder on your PC.
Inside the same folder, right-click on an empty area while pressing the ‘Shift’ key.
Select the option ‘Open PowerShell window here’.
Or you could also head over to the platform-tools folder on your PC, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt.
Type in the below code to make sure the device is successfully connected (an alpha-numeric code suggests successful connection):adb devices
Now type in the below code to boot your device to fastboot/bootloader mode:adb reboot bootloader
Next, type the below code to flash the patched boot image file:fastboot flash boot magisk_patched.img
If you get the fastboot: error: Couldn’t parse partition size ‘0x’ issue, as some users have mentioned in the comments, then please refer to our detailed guide: How to Fix fastboot: error: Couldn’t parse partition size ‘0x’.
For devices with an A/B partition, you need to flash the patched boot file to both partitions. Type the below code for the same:fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Now you may Reboot the device by typing the below code:fastboot reboot
If your device is rooted, then you should stop here only. However, if the Fastboot Command method didn’t work out in your case, then only proceed with the next method to install patched boot.img.
If this post is good please thumbs up.
@Senna-chan
Because adb root & adb remount works here is a code example that adds su
Code:
adb root & adb remount & adb disable-verify & adb shell "setenforce 0"
adb push su /system/bin/
adb push superuser.apk /system/app/
adb reboot
jwoegerbauer said:
@Senna-chan
Because adb root & adb remount works here is a code example that adds su
Code:
adb root & adb remount & adb disable-verify & adb shell "setenforce 0"
adb push su /system/bin/
adb push superuser.apk /system/app/
adb reboot
Click to expand...
Click to collapse
So I tried this with a few version of supersu but it didn't work. I tried version 2.76 2.82 and 2.79 and it didn't work. Everytime I get the error no su binary found. The version I uploaded was the arm64 version since I have a ARMv8.
What could be wrong?
Thats great in all but after I flash the boot.img from any version of magisk from v22 onward and the latest canary, it doesn't give me magisk app when i boot back into the os.
Code:
Your warranty is now void.
If you root your device, Your KNOX status will be tripped.
You can still pass the safety net after you root if you follow the instructions.
I am not responsible for bricked devices, dead SD cards although it is not really possible
Please do some research if you have any concerns about doing this to your device
How to flash official firmware? (not the root and unlock bootloader part!)
You will need:
A Galaxy S22 Plus and common sense
Samsung Odin (the flashing tool of the official firmware)
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
You need to extract the zip file and you are going to use the file Odin3_v3.14.1.exe inside the folder.
Samsung Android USB Driver for Windows
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Double-click and install the exe file.
Samsung Official Firmware
Release 1.0.3 · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Download the platform you want to download to. (Windows)
You need to extract the zip and double click open the file Bifrost.exe inside the folder.
You need to fill in the Model, Region, press the Check for Updates button and the Download button.
How to find the Model: on your phone → Settings → About Phone → The third row says the Model number and you need to remove the part with the part of /xx, for example, SM-S906B/DS and you only need to type SM-S906B
How to find the Region: You can check the Region at this link https://samfrew.com/model/SM-S906B/ or https://samfrew.com/model/SM-S906E/
You need to find find a three-letter word depending on your carrier and country and type it in Bifrost, for example, EVR
Press the Check for Update button and download it with the Download button.
Put it to a place you can easily find, ie. Desktop.
After downloading it, find the file SM- S906x_x_xxxxxxxx_xxx.zip.enc4 on the place you put it and change the document format from .enc4 to .zip. Then, double click and extract the file.
Open Odin3_v3.14.1.exe and turn off your phone. Connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrived at Download Mode press volume up. Go back to Odin3_v3.14.1.exe:
-Click on BL and select BL_S906xxxxxxxxxx.tar.md5
-Click on AP and select AP_S906xxxxxxxxxxx.tar.md5
-Click on CP and select CP_S906xxxxxxxxxx.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_xxxxxxxxxx.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_xxxxxxxxxx.tar.md5
Press Start to flash the firmware, after done, your device will automatically reboot to the system.
How to unlock the bootloader?
Go to your phone → Settings → About Phone → Software information → Press Build number 6 times until you see the notice “You’re now a developer”
Go in Settings → Developer options → enable OEM unlocking
Power off your phone first. Then, connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone.
When you arrived at Download Mode, long press volume up until you see the black screen. Confirm to unlock the bootloader and you will erase your device.
How to root your phone?
After you unlock your bootloader, you set up your phone and make sure you do not sign in google account first. Install Magisk https://github.com/topjohnwu/Magisk/releases/download/v24.1/Magisk-v24.1.apk on your phone. Oh yes, in case you do not know, you need to allow the app to install apps so that you can install the apk.
Transfer AP_S906xxxxx.tar.md5 in the firmware you download from your PC/Laptop to your phone.
Open Magisk on your phone and press the install button in the Magisk column. Select 'Select and Patch a File', 'Let's Go' and find the AP_S906xxxxx.tar.md5 and select it. You can have a cup of coffee if you like when you waiting for the patching of the file.
After finishing the patching, you need to transfer the file magisk_patched-24xxx_xxxxx.tar in the Downloads folder back to your PC/Laptop.
Turn off your phone. Connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrived at Download Mode press volume up. Open Odin3_v3.14.1.exe on your PC/Laptop:
Click on BL and select BL_S906xxxxxxxxxx.tar.md5
-Click on AP and select magisk_patched-24xxx_xxxxx.tar
-Click on CP and select CP_S906xxxxxxxxxx.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_xxxxxxxxxx.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_xxxxxxxxxx.tar.md5
When it finishes flashing it, it will automatically reboot and you can gain root access.
Optional: If you want to have the safety net passed (most of the banking apps use it), then you need to install the zip
as a Magisk module in Magisk https://github.com/kdrag0n/safetynet-fix/releases
How? Go to Magisk → Modules → install from storage and select the zip you downloaded.
Here is the other region section for the S22+
https://samfrew.com/model/SM-S906E/
DarkestSpawn said:
Here is the other region section for the S22+
https://samfrew.com/model/SM-S906E/
Click to expand...
Click to collapse
Thank you very much for the reminder
This is only for the Exynos version I'd assumed?
Benetzit said:
This is only for the Exynos version I'd assumed?
Click to expand...
Click to collapse
For all model except USA model
Hi followed your instryuction on SM-S906B
the following is not possible
$su
#mount -orw,remount /
'/dev/block/dm-0' is read-only
rootadvisor said:
Hi followed your instryuction on SM-S906B
the following is not possible
$su
#mount -orw,remount /
'/dev/block/dm-0' is read-only
Click to expand...
Click to collapse
So you have already gain su
Any news? should I or someone open a ticket for this issue on Magisk github?
My magisk logs in attachment
Williamtung said:
For all model except USA model
Click to expand...
Click to collapse
I think it may apply to Canadian models too as I seem to not have an OEM bootloader unlock option in developer options.
exad said:
I think it may apply to Canadian models too as I seem to not have an OEM bootloader unlock option in developer options.
Click to expand...
Click to collapse
OK, thanks for the info. So, I think you also cannot unlock the bootloader then(except the paid services)
Williamtung said:
OK, thanks for the info. So, I think you also cannot unlock the bootloader then(except the paid services)
Click to expand...
Click to collapse
Do you know of any paid services? I wouldn't mind paying for a bootloader unlock
exad said:
Do you know of any paid services? I wouldn't mind paying for a bootloader unlock
Click to expand...
Click to collapse
Yes, but S22 plus is a new device and maybe you need to ask him is it unlockable yet
rootadvisor said:
Any news? should I or someone open a ticket for this issue on Magisk github?
My magisk logs in attachment
Click to expand...
Click to collapse
use magisk alpha
its working
s22+ exynos
{
"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"
}
Is OTA possible after root? How can we update without data loss?
Wired Life said:
Is OTA possible after root? How can we update without data loss?
Click to expand...
Click to collapse
no more OTA updates after root
you need to download firmware, patch ap file with magisk and flash firmware with home csc file
pitelasssss said:
no more OTA updates after root
you need to download firmware, patch ap file with magisk and flash firmware with home csc file
Click to expand...
Click to collapse
So on every update we need to do a full flash? Wow
And the userdata is keep?
Is there a way to backup all before update?
yes full flash with home csc to keep your data
if you want to backup your apps and data with root use migrate app from playstore
pitelasssss said:
yes full flash with home csc to keep your data
if you want to backup your apps and data with root use migrate app from playstore
Click to expand...
Click to collapse
On the root flash there were 2 "erasing everything" screens, one after a message that something is corrupt. Will this happen again?
Can you provide a simple step by step list what to do with new updated firmware?
pitelasssss said:
use magisk alpha
its working
s22+ exynos
View attachment 5571347
Click to expand...
Click to collapse
Hello can you passe me the link For this Alpha Version ?
rootadvisor said:
Hello can you passe me the link For this Alpha Version ?
Click to expand...
Click to collapse
Magisk alpha
带遥测的第三方Magisk版本，比Canary通道更加不稳定，与上游行为有较大不同，无安全性保证，无可用性保证，无隐私协议。 问题反馈请加群发送日志文件，非alpha独有问题建议先在GitHub反馈。
t.me
I am perfom this Sorry for my english, I am from Ukraine
Download archive!
We unpack. Install the adb and mtk preloader drivers, if they are not installed, restart the computer.
In the smart, turn on the developers menu, in it - "Allow OEM unlock" and "USB debugging" and connect the smart to the computer.
We drop valuable photo data from the smart to the computer for any, and, without disconnecting the smart from the PC, run the script (with the phone connected to the PC and loaded into the android phone. Reboot_to_fastboot_getvar current-slot.bat (not from the admin, just click twice).
Smart will look like 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 allow - put a daw, ok. We are waiting for the smart to reboot into fastboot, when the barcode appears on the smart screen, before that we do not press anything in the script
I did the scripts step by step, after each operation in the script window, press enter to continue, and so on until each script is closed
We look at our current slot in the window and remember the letter - a or b:
In the script, press enter so that the smart reboots and the script closes.
Run flash_tool.exe, go to this tab and check the boxes, as in the screenshot:
So we consider the necessary versions of orig. files, so as not to download and sew a specific firmware version for this instruction.
(And best of all, all the checkboxes, except for system, vendor, userdata - they are not critical, if they are not removed, it will take up a lot of space on the computer up to +74 gb, but I did not put these checkboxes, there must be some risk and passion )
We press "Read Back" and only then we connect the switched off smart to the PC, we wait, at the end we disconnect the bodies, do not touch it: sveta:
Go to this tab, remove all checkboxes! And we only put on lk_ with the letter of a non-your slot that we looked at, for example, you had slot "a" - so we put a check on lk_b and vice versa :
Click "Download" and connect the switched off smart to the PC (it was already turned off: sveta
As it flashes, we close the USB flash drive window, disconnect and turn on the smart, after loading, we connect it to the PC again, we already run the script
Unlock_Moto_E6S.bat, wait until the body reboots into a fastboot (to the barcode on the screen) and only then press the input step by step to continue in the script until it is completely closed.
Everything, the bodies are unlocked. Now you can get an excellent and fast root from Magisk, try other firmware, unsubscribe which one is buggy, which one flies. I haven't tried yet. Now I will write how to flash orig. kernel with magisk root (attached magisk boot for xt2053-1 4/64 fw RETEU 288-60-6-29 https://mirrors.lolinet.com/firmware/moto/fiji/official/RETEU/
Additionally, there is a script in the folder to delete the message when loading that the bootloader is unlocked, it does not interfere much, but I deleted it. Since this is not important, I separated it from the main script, since I did not test it on different versions of the firmware, in theory it should work on all versions, you can try after unlock. Or throw off ROM_45 from your firmware, I'll remove it from it. I now have the latest firmware flashed, it is on the server, but for some reason it did not fly through the air. If you flash it, then you can safely delete the message from the bootloader with my script, there is a file from it)
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
severagent007 said:
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
Click to expand...
Click to collapse
dude!! followed all your steps and i now have a bootloader unlocked and rooted device. how did you figure out the lk and signature to unlock that??
proof attached below
Слава Украине!!!
can the mods move this to the moto e6s forum so we can spread the news?
luridphantom said:
can the mods move this to the moto e6s forum so we can spread the news?
Click to expand...
Click to collapse
I took the first firmware I got to try from here: https://4pda.to/forum/index.php?showtopic=892755
but the firmware itself is everywhere, for example here:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
DeveloperLuke Roms - Browse /GSIs at SourceForge.net
sourceforge.net
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You can try to sew any GSI arm64 a/b from anywhere you find and choose the one you like, because smart supports Project Treble.
If you like one and will look cool and work firmware, post links here!
Tested it and it worked! Thanks a lot!
Now looking for delevoping some roms to this device
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
refrigerador67 said:
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
Click to expand...
Click to collapse
did you use the auth file that comes with sp flash tool? without that your device wont boot properly
Yes, i used the correct download agent and auth file
interesting, i followed all his steps and had no problem rooting it. try backtracking with his scripts again?
Solved it, also me and a developer are working on a new, more simple and automated script. Still haven't figured out how to flash the lk via script.
When is done i will post a complete guide in the moto e6s forums on how to do it, i think it might work well, but i would have to test in a non-unlocked device
Can someone please make a video with explanation, I didn't understand very well what is done, so I won't touch anything, but I thank those who record a video explaining it to me (I'm Brazilian)
Here you have a more straight forward guide, note that is still in testing
[GUIDE] How to unlock bootloader on E6s
Hello, in this guide i will show you how to unlock the bootloader on Moto E6s ;) (Sadly for now this guide is Windows only) CAUTION You are doing this AT YOUR OWN RISK! I will NOT take responsibility if you brick your device! Also, remember to...
forum.xda-developers.com
Excuse my ignorance, do you think it is compatible for the XT2053-5 model?
cannot use fastboot flash boot magiskboot.img
sign failed
partition flash is not allowed
hey is the moto e6+ twrp work on e6s