How To Guide How to Root S23 (S91*B/N/0) - Samsung Galaxy S23 Ultra

How to Root Samsung S23 (SM-S91*B/N/0)
WARNING!
Before you root your device you must be aware that
This will void warranty.
As of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
There are many features stop working when you unlock bootloader other than S pay/Pass like Samsung Health, Secure Folder, Galaxy Watch pairing issue, Issue connecting old gear watch (S3 or earlier), Google Pay etc but some ROMs are patched for all these mentioned features, you can use custom ROM or patch it yourself for stock ROM. Still you may trouble using some bank apps and these may fixed by adding these apps to Magisk Hide
There may be some knox features there which you may not able to use but I can't list those as I never used. Just Google It
Patched featurs are working today when writing this, No idea if it may stop working next moment/tomorrow or later
Also to note, once you root, you can't go back to "pre-rooted" state completely. It is one way!
OTA won't work once you root device.
ROOT with caution.
You can unroot & Relock bootloader after flashing stock firmware, but still your warranty flag remain 0x1 and most of countries it still voids warranty. Also after unrooting & relocking bootloader, some knox features never work again.
How to Unlock Bootloader
Follow below four steps to ulock the bootloader
1.Enable Developer Option
Open the Settings app on your Galaxy device.
Choose About > Software Information.
Now tap on Build Number 7 times to enable the developer option.
You’ll get a message “You’re now a developer.”
Now Developer option has been enabled.
2: Enable OEM Unlock
Go to the Settings app again on your device.
Navigate to the Developer option.
Enable the toggle next to OEM Unlocking.
Tap YES to turn on the confirmation dialog box.
3: Boot Your device to Download Mode
While device is booted → Connect device to PC → Select to Restart → As soon as device screen turns off, Press and hold Volume Up + Volume Down simultaneously OR In case device is powered off Press and hold Volume Up + Volume Down simultaneously and connect your device to the PC via a USB Cable.
You can see the warning message on your device and release the pressed keys.
Finally, press the Volume Up key once, and you will be booted into Download Mode.
4: Unlock Bootloader
Once device booted into Download Mode, you will see option to long press Volume up to unlock bootloader,Now, press and hold the Volume Up key for a few seconds., Here, you’ll get a confirmation whether you are sure to proceed.
Use the Volume Up button to reply to the confirmation.
This will erase all the data on your device and unlock the bootloader.
Once completed, your device will automatically boot up to the OS.
Now you have successfully unlocked the bootloader
How to root S23
Instructions for stock non rooted ROM​
Use either samfirm.js, Frija, or Samloader to download the latest firmware zip of your device directly from Samsung servers.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Download and Install latest Magisk apk (Get Latest Magisk apk from here)
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the AP tar file
When done, copy patched file to PC
Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
Install the Magisk app you’ve already downloaded above and launch the app. It should show a dialog asking for additional setup.
Let the app do its job and automatically reboot the device. Voila!
Upgrading the OS​Once you have rooted your Samsung device, you can no longer upgrade your Android OS through OTA. To upgrade your device’s OS, you have to manually download the new firmware zip file and go through the same AP patching process written in the previous section. The only difference here is in the Odin flashing step: do NOT use the CSC tar, but instead use the HOME_CSC tar as we are performing an upgrade, not the initial install.
Important Notes​
Never, ever try to restore either boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.
To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.
Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading.
PS : It is strongly recommended to make EFS backup once you root device and save to safer place like on cloud or PC
For TWRP : Read here
Credit : topjohnwu Guide part taken from Origin guide here
{
"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"
}

Will try this now. Should the other slots BL/CP/CSC be filled with the firmware files when flashing this AP?

zzattack said:
Will try this now. Should the other slots BL/CP/CSC be filled with the firmware files when flashing this AP?
Click to expand...
Click to collapse
No needs, Flash requied file with AP slot onl

I flashed the AP file. I could not enter recovery mode to do factory reset. Device went into boot-loop mode, but after some failed attempts launched recovery by itself. Then I was able to do factory reset, and device boots properly.
Magisk (25.2 from apk in your zip file) still indicates: not installed. Ramdisk yes. Zygisk no (obviously).

zzattack said:
I flashed the AP file. I could not enter recovery mode to do factory reset. Device went into boot-loop mode, but after some failed attempts launched recovery by itself. Then I was able to do factory reset, and device boots properly.
Magisk (25.2 from apk in your zip file) still indicates: not installed. Ramdisk yes. Zygisk no (obviously).
Click to expand...
Click to collapse
You flashed AP file I have provide or one with patched with magisk yourself?

Earlier today I used Magisk alpha to patch the AP from WA6 firmware.
Some minutes ago I flashed AP file from you on top. It only wrote boot and vbmeta.
Any debug info/logging I can provide?

zzattack said:
Earlier today I used Magisk alpha to patch the AP from WA6 firmware.
Some minutes ago I flashed AP file from you on top. It only wrote boot and vbmeta.
Any debug info/logging I can provide?
Click to expand...
Click to collapse
Odin was passed successful?
Kernel I have provided is surely Patched., May be needs to contact Jhon with log. Kindly post in Magisk thread

Yes, no problems from ODIN. I will try to find the magisk thread and useful logging infos.

Magisk log added

zzattack said:
Magisk log added
Click to expand...
Click to collapse
If you can save log from Magisk App - Logs - Save and attach here
Also show me screenshtot of magisk app

Nice!!!

zzattack said:
Magisk log added
Click to expand...
Click to collapse
I have updated link (with debug version), Can you flash again and Install included Magisk? After this take log so I can send to Jhon with debug version. Also take screenshot of magisk app

Logs + magisk screenshot attached with debug image and apk.

zzattack said:
Logs + magisk screenshot attached with debug image and apk.
Click to expand...
Click to collapse
Do you have telegram? If yes inbox me. We can do some test with easy communication

@zzattack or any other user
I have updated link(v3), If anyone available to test new version.
.

This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!

zzattack said:
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
Click to expand...
Click to collapse
Great,
That's awesome news!
Thank you very much for testing.

Any other user available to test then let me know, Next test will be for Root with Magisk Stable (25.2)
Debug version already reported working (reported by @zzattack )
.

I'm waiting for my s23 ultra next week and then I'll be able to test.
I'm aware I'll lost Samsung Pay and pass. I really don't care... Don't use it... But, will I have troubles with Google pay and secure folder if rooted?

zzattack said:
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
Click to expand...
Click to collapse
does zygisk work?

Related

[RECOVERY][ROOT][TWRP 3.2.1-1][Magisk v14] Samsung Galaxy Tab A6 SM-T280/SM-T285

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP custom recovery for the Tab A SM-T280/T285. Latest build is 3.2.1-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
UPDATE 08/01/2018 - TWRP updated to version 3.2.1-1
UPDATE 21/11/2017 - Magisk updated to v14
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
DOWNLOAD:
TWRP_3.0.2-1_SM-T280_261016
twrp_3.2.1-1_sm-t280_080118
twrp_3.2.1-1_sm-t285_080118
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this. (FIXED)
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
This step only required for the SM-T280
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v14:
1. Download Magisk v14 to your device
Magisk v14
2. Install the Magisk v14 zip with TWRP
This step only required for the T280
3. Flash the patched boot image below with TWRP.
magiskv14_boot_aqd1
4. Reboot
5. Install Magisk manager
Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Help me root my phone
Sent from my SM-G903W using XDA Free mobile app
ashyx said:
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Click to expand...
Click to collapse
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
jedld said:
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
Click to expand...
Click to collapse
Hi Jed, after trying various different configs in twrp and even modifying the graphics source code it made no difference.
Using the the touch debugger in twrp it was apparent that the touch was responding fine.
So I turned my attention to the kernel.
After several builds of modifying the cpu config making no difference, it turns out TWRP only supports double buffering, but the kernel was forcing triple buffering.
It seems this was causing an extra frame to be displayed causing what seemed like lag and explains why when pressing the screen a second time would cause the frame to update.
The page that was in ram had changed when tapping a button, but the wrong frame in the buffer was displayed until the next touch which then updated the display.
Disabling triple buffering in the kernel fixed the issue.
jaritico said:
PRE-ROOTED boot image can be used on 285? (needed for Systemless Root ) same at magisk patched boot
Click to expand...
Click to collapse
You don't need it for the T285.
Worked perfectly, first time.
Installed supersu via trwp and then img via boot in twrp also.
Thank you for the clear tutorial.
Excellent
just about to root mine now are there any custom roms that can go on it?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
I don't know how this is working for others, but installing SuperSu uninstalled android.
Ethan-56 said:
I don't know how this is working for others, but installing SuperSu uninstalled android.
Click to expand...
Click to collapse
It does what? [emoji55]
Also please don't quote the entire OP.
ashyx said:
It does what? [emoji55]
Also please don't quote the entire OP.
Click to expand...
Click to collapse
OK, I'm new to XDA. I installed TWRP and supersu, but when switching to Odin to install that other supersu thing, It wouldn't boot properly I tried deleting supersu, but I uninstalled android entirely. I got the splash screen, but TWRP warned that there was no OS installed. Does XDA Developers have a tutorial on reinstalling Android? I also can't locate the stock firmware and I forgot to back up my system.
Download the stock firmware from sammobile or UPDATO and flash with odin.
T280 comes in on Tuesday, will try this method and report back. Seems fairly easy, thanks for allowing us to have TWRP and root, it will help in debloating this 8gb version i picked up.
Any suggestion how to install Magisk v9?
Root done in five minutes, I can't believe!
Thanks ashyx!
What Gives???
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
gello924 said:
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
Click to expand...
Click to collapse
Ffs have you never heard of false positives? [emoji55] What do you expect you're installing files that compromise an operating system.
Also what relevance is it that my AFH user name is different?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
followed your instruction & it works, many thanks..much appreciated:good::good::good:
Hi ashyx
To start sorry for my English, I am French and a bad student.
I want to thank you for this guide and all of your contribution on the Android scene :good:
I followed your instructions successfully but I have some questions
Can I install Busybox? If so, is it useful? If yes, how?
I have to do update Magisk v7 to v9?
To finish what is the best solution to extend the internal memory? Actually I used Link2Sd but I'm not satisfied
Thanks again for your work, a little boy will be in the angels when he will receive his gift of Christmas
Error - Security check (boot)
While odin is telling me everything it's correct and shows PASS message on my tablet Sm-t280 shows Security check fail - (boot) and when i restart i can't see any changes,
Oem unlocked and usb debug activated i tried flash with twrp image file and with supersu img file.
I hope your help thanks

[RECOVERY][ROOT][TWRP 3.0.2-1] Samsung Galaxy Tab A6 LTE SM-T285

Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
TWRP-3.1.1-0 for the SM-T285 is now available, you should hop on to this thread for more information.
Update 01/17/2017
==============
TWRP with F2FS support here. Use only if you plan to use the F2FS enabled CM13 builds for the SM-T285.
Update 11/24/2016
==============
* MTP should now be fixed
Installation Instructions
This installation instruction is only for the LTE enabled version of the Samsug galaxy tab A 7" 2016 (SM-T285). If you have a wifi-only version (SM-T280) go to this thread instead.
Disclaimer: I am not responsible for bricked devices and provide no warranty, make sure you made the proper backups and contingencies before you do this procedure. Make sure you have a stock firmware available as a contingency plan
Before going through this make sure your tablet is OEM Unlocked. Make sure you have developer settings enable and there should be a setting there that says OEM unlock. That should be enabled, otherwise your SM-T285 will not accept firmware changes. Also make sure your tablet has sufficient charge and is not about to die.
1. Put your tablet in download mode (Turn off. holding POWER + HOME + VOL DOWN until download mode appears. There will be a warning that about custom firmware blah- blah-blah just hit volume up to proceed). Connect your tablet to your computer using the provided micro usb cable.
2. Flash with ODIN 3.10.7 in the AP slot. Uncheck Auto reboot. (If you are on Linux you can use Heimdall
3. Load the respective attached file (TWRP_3.0.2-1_SM-T285_20161124.zip) in this thread below into the AP slot and hit start.
4. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Root and SuperSU
==============
1. Download the latest available SuperSu Zip from chainfire. Install Zip using TWRP. Reboot phone.
2.Your phone might reboot a couple of times, however at the end of the process you should be rooted.
enjoy!
jedld said:
Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
For the installation instructions, should be the same with the SM-T280 in this thread http://forum.xda-developers.com/galaxy-tab-a/development/recovery-samsung-galaxy-tab-a6-sm-t280-t3475381
enjoy!
Click to expand...
Click to collapse
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Thanks
I rooted my device (Glaxy Tab a 7" T285)by your method and files.
Next day i saw my device was off ,i pressed power but it could not boot and show this:
Code:
custom binary blocked by frp lock
Afterward i tried to go recovery by pressing Home+Power+volum up but it could not go recovery and show me:
Code:
custom binary blocked by frp lock
Recovery is not Seandroid Enforcing
Therefor my device had been useless.
so I go to download by odin and install a stock ROM.
I search and saw 2 advises:
1)this problem occur if androd version is 5.1.1
2) this problem occur if in developer menu OEM Unlock Option is disabled.
IS THIS ADVISES TRUE? OR THAT PROBLEM HAS OTHER REASON?
I went dev menu and enabled OEM and afterward i did ROOT again.
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
2) How do i unroot my device?
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
Click to expand...
Click to collapse
If you install a new rom, then yes you have to factory reset. If it is just to install TWRP I don't think you need to do that.
2) How do i unroot my device?
Click to expand...
Click to collapse
Easiest way is to just flash stock again
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
acornkenya said:
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Click to expand...
Click to collapse
MTP should now be fixed with the latest release.
jedld said:
MTP should now be fixed with the latest release.
Click to expand...
Click to collapse
MTP is now working like a charm; thank you
Adam Hui said:
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
Click to expand...
Click to collapse
Pls help subinary files not installed superSU v2.78.SR1
siukbah112 said:
Pls help subinary files not installed superSU v2.78.SR1
Click to expand...
Click to collapse
Just download & flash latest SR5 superSU.zip
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Shook1 said:
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Click to expand...
Click to collapse
ok, I've updated the instructions.
finally, I've managed to flash the recovery img to my Stock 285. I have compiled the heimdall from source (github), using Debian 8 Jessie. I also managed to download the stock firmware from sammobile using wget + cookies trick so it can be resumed without requiring a premium account. Thanks for the TWRP
BTW, after installing the SuperSU the SELinux is gone? do I need to flash your custom kernel too?
What do you mean? Was SELinux set to permissive? From what I know the stock kernel has SELinux configured to always enforce and can't be disabled that easily.
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
{
"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"
}
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
gian20 said:
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
Click to expand...
Click to collapse
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
jedld said:
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
Click to expand...
Click to collapse
I don't know if that issue (missing keyboard) was patched with the new stock firmware update on Dec 13, 2016 or if it may block installation of custom firmwares... I ended up not using a password on the lock screen, I deleted the passowrd.key and modified the android settings database to disable password lock, but seperating the necrpytion password using an app.
Unroot without rebloating?
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
DJThunderGod said:
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
Click to expand...
Click to collapse
If you have removed the bloatware it should stay like that unless you reflash the stock rom.
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
kannaiah said:
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
Click to expand...
Click to collapse
It's possible the stock rom overwrites the recovery since you rebooted straight to stock after flashing. Try to flash again but this time when the device reboots, try to press and hold power + home + vol up immediately to attempt to load TWRP recovery.

[Q] Root & TWRP 3.4.0 for Android 10.

{
"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"
}
Root & TWRP 3.4.0 for Android 10.
Root and absolutely working TWRP 3.4.0 on Android 10!​
In the new TWRP and Root installation method described below, there is no need to format the Data partition to remove the encryption.
Thanks to TWRP's built-in FB Encryption (File Based Encryption), the contents of the Data partition are available with encryption preserved. The folders on the external memory have the correct names and structure.
Temporary flaw: each new firmware requires a new TWRP.
1. Download archive for up-to-date firmware (as of 09.12.20 - QPHS30.29-Q3-28-13-6) with files for installation TWRP and Magisk Root_TWRP_QPHS30.29-Q3-28-13-6.zip
2. Extract files:
- TWRP-Q-3.4.0-parker-nemo-nemo.img to the drivers adb & fastboot folder;
- Magisk-disable-dm-verity-v20.4.zip to the SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash boot C:\adb\TWRP-Q-3.4.0-parker-nemo-nemo.img
4. After installation is complete, restart the phone in Recovery.
5. Go to the "Install" section. Click on "Select Storage" button, select Micro SD card, OK. Install Magisk-disable-dm-verity-v20.4.zip.
6. Reboot into the system.
Attention, it's important!
In case of release of new stock firmware RETEU, or you have a device for other regions, you can update TWRP yourself in the following way:
So, in order for you to have TWRP, mobile communications and Wi-Fi, you need to do the following:
- Copy to SD Card boot.img from Stok firmware archive, which is currently installed on your phone;
- Copy to the SD card twrp-installer-3.4.0-0-parker-nemo-nemo.zip;
- Follow step 3 of the basic instructions;
- Install directly in the TWRP boot.img itself under Boot;
- Install the twrp-installer;
- Install Magisk-disable-dm-verity-v20.4.zip.
Earlier versions of TWRP
QPHS30.29-Q3-28-13-2
QPHS30.29-Q3-28-13
Old Instruction:
1. Download archive with files for installation Magisk and TWRP Google Drive.
2. Extract files:
- boot_magisk_q.img to the drivers adb & fastboot folder;
- Magisk-ddmv-v20.4.apk, Magisk-disable-dm-verity-v20.4.zip, twrp-installer-3.4.0-0-parker-nemo-nemo.zip to the SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash boot C:\adb\boot_magisk_q.img
4. Reboot into the system and install Magisk-ddmv-v20.4.apk.
5. Run the application Magisk Manager, go to the "Modules" tab and select twrp-installer-3.4.0-0-parker-nemo-nemo.zip.
6. After installation is complete, restart the phone in fastboot mode and then in Recovery.
7. Go to "Wipe" section and press "Format data" for decryption. Type "Yes" on request. Go to the TWRP Main Menu and reboot again in the Recovery.
8. Go to the "Install" section. Click on "Select Storage" button, select Micro SD card, OK. Install Magisk-disable-dm-verity-v20.4.zip.
9. Reboot into the system.
Updated TWRP to firmware version QPHS30.29-Q3-28-13-2.
Hey, thanks for doing this. I'm a newbie, but I got through your instructions and it worked! At least at first. After I OEM-unlocked and installed TWRP, Android seemed to be working fine. I went into TWRP installed Magisk and when I restarted it seems my wifi (wifi mac address is "unavailable") and the service state of my radio is off. I can't figure out how to get it back on.
I tried messing around with settings in *#*#4636#*#* , no luck.
I put my sim card in an old phone and it still works (I wondered if I got locked out by my carrier?)
Think it might be connected at all or do I have a separate issue going on here?
EDIT: Nevermind - I used Lenovo's Rescue Smart Assistant and got it fixed...
Thanks!
Wijitmaker said:
Hey, thanks for doing this. I'm a newbie, but I got through your instructions and it worked! At least at first. After I OEM-unlocked and installed TWRP, Android seemed to be working fine. I went into TWRP installed Magisk and when I restarted it seems my wifi (wifi mac address is "unavailable") and the service state of my radio is off. I can't figure out how to get it back on.
I tried messing around with settings in *#*#4636#*#* , no luck.
I put my sim card in an old phone and it still works (I wondered if I got locked out by my carrier?)
Think it might be connected at all or do I have a separate issue going on here?
EDIT: Nevermind - I used Lenovo's Rescue Smart Assistant and got it fixed...
Thanks!
Click to expand...
Click to collapse
What Software Channel intended your phone? I have a RETEU. If you have a different region, this is most likely the reason.
So, in order for you to have TWRP and work mobile communication and Wi-Fi, you need to do the following:
- from the Stock Firmware archive, which is currently installed on your phone, copy boot.img to SD Card;
- twrp-installer-3.4.0-0-parker-nemo-nemo.zip copy to SD Card (see at the attached files).
Install directly in TWRP boot.img and then install TWRP-installer.
Then reinstall Magisk-disable-dm-verity-v20.4.zip (see at the attached files) and whatever you want.
Hi do you have a way to apply OTA update without remove twrp?
Hey,
I have a brand new One Zoom here and like to root it.
Don't wanna brick it, so I have two silly noob questions:
Before performing step 3 in first post above
(fastboot flash boot C:\adb\TWRP-Q-3.4.0-parker-nemo-nemo.img)
I still have to unlock the bootloader, right???
On github, currently there is Magisk v21.1 out. Can I use this newer version or do I MUST use the version provided by ilia3367 in first post?
Thanks to all of you
Solo8000 said:
Hey,
I have a brand new One Zoom here and like to root it.
Don't wanna brick it, so I have two silly noob questions:
Before performing step 3 in first post above
(fastboot flash boot C:\adb\TWRP-Q-3.4.0-parker-nemo-nemo.img)
I still have to unlock the bootloader, right???
On github, currently there is Magisk v21.1 out. Can I use this newer version or do I MUST use the version provided by ilia3367 in first post?
Thanks to all of you
Click to expand...
Click to collapse
Yes your bootloader need to be unlock.
For me with use or twrp I can t install OTA update for résolve that I Have flash again m'y phone with stock Rom and use magisk patch way to Root m'y phone
I have write some instruction on that here
Updated TWRP to version QPHS30.29-Q3-28-13-6, updated the manual.
Solo8000 said:
On github, currently there is Magisk v21.1 out. Can I use this newer version or do I MUST use the version provided by ilia3367 in first post?
Click to expand...
Click to collapse
Use Magisk which is in the Instruction Manual.
This is a special version of Magisk for Motorola devices.
Magisk v21.4 刷机包 Motorola 修改版 | 云梦
介绍 Motorola 有个奇怪的 hab 保护技术,这个组件会保护系统不受侵害。如果不去除这个组件,在开机状态修改系统后,重启将会还原更改,在 TWRP 下修改系统,将无法开机。所以我做了一个修改版 Magisk,以彻底去除这个东西。 注意:仅适用于 Motorola 机型。 特性 - 强制去除 dm-verit
www.htcp.net
When I flash your version of TWRP my network connections go away. I had to reflash the original boot image to get it back.
finally got it. didn't realize you had included the modified zip file in another post.
Just a report:
did the process today, worked like a charme.
One caveat: unlocking bootloader via this stupid motorola web service did not work at first; yesterday evening submitting the correct unlock string always returned "Your Device Does Not Qualify For Bootloader Unlocking"; tried exact same procedure this morning - worked immediately; so I guess this is a problem with Motorola servers.
Right now I have TWRP, Magisk and as it looks ALL smartphone functions including wifi, radio, fingerprint.
My device: Moto Zoom, reteu, build number QPHS30.29-Q3-28-13-6; it's brand new and I did not set up any lock mechanism (like fingerprint) before this process (because some people complain that their fingerprint reader does not work anymore after flashing/rooting; maybe this is a solution to that problem)
Hello, I have a problem/question.
Recently I have a notification of system update available: QPH30.29-Q3-28-13-10, Im' currently on (QPH30.29-Q3-28-13-6) with TWRP an Magisk Installed.
When I try to make the update with the normal System Update it can't apply the update (no specific error).
So I would like to make the update manually; I downloaded the full image zip from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Then I think I could flash it with MotoFlashPro (using servicefile.xml), but what are the steps to keep everything working (TWRP, Magisk, and all network and fingerprint)?
Are these correct?
So, in order for you to have TWRP, mobile communications and Wi-Fi, you need to do the following:
- Copy to SD Card boot.img from Stok firmware archive, which is currently installed on your phone; (so I have to download the current full image and use the boot.img from this one and not the new firmware?)
- Copy to the SD card twrp-installer-3.4.0-0-parker-nemo-nemo.zip;
- Follow step 3 of the basic instructions;
- Install directly in the TWRP boot.img itself under Boot;
- Install the twrp-installer;
- Install Magisk-disable-dm-verity-v20.4.zip.
Sorry for the stupid questions but I don't want to start the process and brick the phone or lose something.
Thank you
TWRP already got official, is there a small chance to see custom roms like lineage os 18 in future?

How To Guide Unlock, Change from Chinese to Eu rom, and root guide with magisk

Unlocking your mi mix 4 :​
lets start by enabling developer options on our mix 4, to do that go to device settings,then tap on My device > All specs > keep tapping on miui version till u enable developer options.
{
"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"
}
this will enable developer options under additional settings,
go to developer settings and enable OEM unlocking, and
select mi unlock status, put in a sim card, disconnect from wifi, enable cellular data, and tap on add account and device
wait for a week, only then u are allowed to unlock.
on your windows pc download and install adb, fastboot and drivers using the 15 seconds adb install tool link
this should install device drivers,
boot your phone into fastboot mode,
to boot your phone into fastboot, power off your device, and while poweing on hold volume down button.
this will put your phone into fastboot mode, connect it to your windows pc, check if the drivers are installed properly by going into
device manager and see if android device is shown without any errors,
open power shell and see if the device is recognised by the system by typing in
Code:
fastboot devices
this should display your device id.
Warning : unlocking your phone will format the whole phone please take a bakcup of your daata.
now download mi unlock tool from this link
open the mi unlock tool select your device and tap on unlock, it will prompt for your credentials,
type in your mi account details that are binded to your device, and once your are logged in,
click on unlock again, this will start the unlock process
on your mix 4, you will be prompted with this,
tap on the first option and log in using your mi account credentials,
your phone is now unlocked.
Replacing the chinese rom with an EU rom:​now that the phone is unlocked, lets download the latest available EU fastboot flashable build from the following link
extract the downloaded rom, before we flash the rom, we need to reboot our phone to fastboot mode, to do that
as i told earlier, power off your device, and while powering the phone on, hold volume down, this will boot your mix 4 into fastboot mode.
lets reverify if your phone is unlocked by opening powershell and type in this command
Code:
fastboot oem device-info
Warning : the next step will format your device to factory settings, please backup the needed files.
now that we verified that the device is unlocked, lets flash the rom by clicking on
windows_fastboot_first_install_with_data_format.bat
this will start the flashing process. once the flash process is done, you can setup the mix 4 device.
Rooting mix 4 with magisk manager:​warning : to root the phone your phone should be having an unlocked bootloader, please dont try to root your phone without unlocking the bootloader.and also banking apps, and payment apps might not work, so do accordingly.
copy imgages/boot.img file from extracted eu rom folder to mix 4 device,
install magisk manager from magisk github link.
once the magisk manager is installed,
open magisk manager, tap on install button next to Magisk,
then tap on select and patch file,
from the file manager, select the copied boot.img, and tap on next.
this will patch the boot.img image file and generate a magisk_patched.img in the downloads folder.
copy the magisk_patched.img file from downloads folder on android to the desktop on windows,
reboot your mix 4 to fastboot mode, and connect it to pc.
now open power shell window in the desktop folder by howering your mouse in the empty space,
and while holding the shift key on your keyboard, right click on the mouse, this will show an option
of open power shell window. click on it, and see if the device is recognised in fastboot mode by typing in
Code:
fastboot devices
this should show your device code.
now that the device is in fastboot mode, type in the following command
Code:
fastboot flash boot magisk_patched*.img
this will flash the magisk patched boot image, you can reboot your phone by typing in
Code:
fastboot reboot
once the phones booted up, open magisk manager, it should say installed : yes under magisk
and also a hovering menu at the bottom which will give access to super su functionality, and magisk modules too.
so if you guys want a detailed video for the same, check out ,
Great tutorial, i did all this but did not use magisk or root the phone, is there any reason to ?
jrvenge said:
Great tutorial, i did all this but did not use magisk or root the phone, is there any reason to ?
Click to expand...
Click to collapse
If you want to use Google Pay or any other app that uses SafeNet API to detect root, you might want to use Magisk to add hide module to trick SafetyNet and hide. SafetyNet unfortunately detects even unlocked bootloader and/or flashed custom ROM.
inao said:
If you want to use Google Pay or any other app that uses SafeNet API to detect root, you might want to use Magisk to add hide module to trick SafetyNet and hide. SafetyNet unfortunately detects even unlocked bootloader and/or flashed custom ROM.
Click to expand...
Click to collapse
so most of the banking apps or payment apps only stop working if u have rooted your rom. so i am on eu rom and most of the banking apps work if i dont root it
I guess it depends. On my MIX 3 Google Pay wasn't working because I had bootloader unlocked even when nothing was flashed. I'm planning to experiment a bit when official TWRP comes out because I really hate CN XiaoAI and a lot of features missing.
vamsi209 said:
so most of the banking apps or payment apps only stop working if u have rooted your rom. so i am on eu rom and most of the banking apps work if i dont root it
Click to expand...
Click to collapse
It does? Maybe try this one...
wipe cache of google play services
then perform safetynet-check...
I use google Pay on a daily basis and my phone is rooted.
SanHelios said:
It does? Maybe try this one...
wipe cache of google play services
then perform safetynet-check...
I use google Pay on a daily basis and my phone is rooted.
Click to expand...
Click to collapse
ok but rooted phones how is ur safetynet check passing mate ?
vamsi209 said:
ok but rooted phones how is ur safetynet check passing mate ?
Click to expand...
Click to collapse
Yes, everytime...
I should mention, that i use magisk hide for all my playstore and banking apps too.
Will the wait time to unlock bootloader reset if the phone is turned off for 7 days?
Aleksanderbjorn said:
Will the wait time to unlock bootloader reset if the phone is turned off for 7 days?
Click to expand...
Click to collapse
No. I turned off my device too. Unlocking proceeded without any problems.
Can anybody give instruction on root and magisk without installing eu? If i wanna use ch?
flozzz said:
Can anybody give instruction on root and magisk without installing eu? If i wanna use ch?
Click to expand...
Click to collapse
so inorder to root, you have to have your bootloader unlocked for sure,
so unlock your device as shown in my post above,
then extract your boot.img from the rom( find the version of your rom, download that specific rom from https://mifirm.net/model/odin.ttt )
and follow the above instructions for root as shown in my post(basically install magisk manager on your phone, use magisk to patch the boot.img, and the finally flash the boot.img using the command in fastboot mode.
Code:
fastboot flash boot magisk_patched*.img
and your phone should be rooted.
What if I want to return a phone to stock?
Bootloader is unlocked and it is running MIUI 12.6 by xiaomi.eu.
So I want to lock the bootloader and install the official rom so I can get OTA updates.
I downloaded MiFlash2020-3-14-0 and China Fastboot ROM: odin_images_V12.5.12.0.RKMCNXM_20211021.0000.00_11.0_cn_0d71adc934.
In MiFlash I selected clean all and lock. When trying to flash I am getting an Antirollback check error.
Short update: it seems you can't have spaces in the file path. After fixing this it flashed with no errors
ferid said:
Short update: it seems you can't have spaces in the file path. After fixing this it flashed with no errors
Click to expand...
Click to collapse
thaanks for the update
By switching to the EU rom, does that mean I will not have to change any permission settings to get the gaps to work or will I still have to change permissions settings even after the ROM comes preinstalled with Google apps?

How To Guide Updating firmware after unlocking bootloader and rooting

It might be common sense for some, but I didn't see this as a separate post and it might help people get around this.
Once you unlock the bootloader and root with Magisk, you can't have OTA updates from the phone itself.
But what you can do to get these updates is to use the Xperia Companion tool.
You have to go to Magisk first and click on Uninstall and choose Restore images. This will bring back your original boot image from a backup Magisk does when patching the image.
Once this is done, reboot and connect the phone with Xperia Companion. Allow file transfers through USB. No need for USB debugging.
If there's an update available, it will download and transfer it to your phone. You'll see the install process in the status bar.
Once this is done, you can reboot and verify the update was installed. Now it's time to use Magisk to patch the new boot image.
There's a good guide already made - here.
In short use XperiFirm to download the latest FW, get the boot-x... sin file, put it in the folder where you have unsin executable file and just drag it over unsin. This will produce an image file, which you copy to your phone. Start Magisk, Magisk -> Install, it will ask you where the image file is, so point to the location where you saved it.
The result file will be put in Downloads on your phone. Copy it over to your PC.
Reboot the phone to Fastboot (Volume Up and Power buttons, or turn off the phone and press Volume Up, then connect the USB cable), you'll see you're in Fastboot if the LED is blue.
Open CMD, point to the location where you have ADB files copied and type in:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Where magisk_patched.img is your image file, so just put in the name and location to that file.
For example: fastboot flash boot_a c:\temp\boot_X-FLASH-ALL-4BA8.img
If the command fails, type in fastboot devices and that should list one device - the phone you connected.
If no devices are listed, check if you have the drivers for your phone. The article link above lists all driver and utilities downloads.
I've used newflasher and it soft bricked my phone. Maybe it's something I did wrong, but using the above is way easier and safer, in my opinion.
Hope it helps you too!
i tried your guide, and magisk don`t have backup of boot,
Was there any sort of an error message from Magisk?
It worked straight out for me.
Can't find Magisk's backup folder though, so I can see what I have inside.
unicastbg said:
Was there any sort of an error message from Magisk?
It worked straight out for me.
Can't find Magisk's backup folder though, so I can see what I have inside.
Click to expand...
Click to collapse
yes
Sakuma_Eitarou said:
yes
Click to expand...
Click to collapse
Emm, ok, what was the error message? I can guess one or two, but better ask than assume the wrong thing.
unicastbg said:
Emm, ok, what was the error message? I can guess one or two, but better ask than assume the wrong thing.
Click to expand...
Click to collapse
I did't deal with blocking the bootloader, but I expressed my thoughts
Let's see if someone else has the same issue.
I found Magisk uses root/data/magisk_backup_xxxxxxxxx folders, where xxxx is a combination of numbers and letters. There's a boot image copy in there.
When I flashed my magsik patched boot file, I had to factory reset my phone, otherwise on boot android would tell me my file system is currupt.
Any ideas why that might be?
cheesepuff said:
When I flashed my magsik patched boot file, I had to factory reset my phone, otherwise on boot android would tell me my file system is currupt.
Any ideas why that might be?
Click to expand...
Click to collapse
reflash with newflasher and use 2.4,3 of magisk ad\nd upgrade from that point
bountyman334 said:
reflash with newflasher and use 2.4,3 of magisk ad\nd upgrade from that point
Click to expand...
Click to collapse
I'm not 100% sure what all that means.
What's ad/nd?
And I'm not sure what 2.4,3 means in regards to magisk
Pretty sure that was a typo and they meant "and". Plus the magisk Number is the variant for example I'm on 25.2 which should be the latest one...
unicastbg said:
It might be common sense for some, but I didn't see this as a separate post and it might help people get around this.
Once you unlock the bootloader and root with Magisk, you can't have OTA updates from the phone itself.
But what you can do to get these updates is to use the Xperia Companion tool.
You have to go to Magisk first and click on Uninstall and choose Restore images. This will bring back your original boot image from a backup Magisk does when patching the image.
Once this is done, reboot and connect the phone with Xperia Companion. Allow file transfers through USB. No need for USB debugging.
If there's an update available, it will download and transfer it to your phone. You'll see the install process in the status bar.
Once this is done, you can reboot and verify the update was installed. Now it's time to use Magisk to patch the new boot image.
There's a good guide already made - here.
In short use XperiFirm to download the latest FW, get the boot-x... sin file, put it in the folder where you have unsin executable file and just drag it over unsin. This will produce an image file, which you copy to your phone. Start Magisk, Magisk -> Install, it will ask you where the image file is, so point to the location where you saved it.
The result file will be put in Downloads on your phone. Copy it over to your PC.
Reboot the phone to Fastboot (Volume Up and Power buttons, or turn off the phone and press Volume Up, then connect the USB cable), you'll see you're in Fastboot if the LED is blue.
Open CMD, point to the location where you have ADB files copied and type in:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Where magisk_patched.img is your image file, so just put in the name and location to that file.
For example: fastboot flash boot_a c:\temp\boot_X-FLASH-ALL-4BA8.img
If the command fails, type in fastboot devices and that should list one device - the phone you connected.
If no devices are listed, check if you have the drivers for your phone. The article link above lists all driver and utilities downloads.
I've used newflasher and it soft bricked my phone. Maybe it's something I did wrong, but using the above is way easier and safer, in my opinion.
Hope it helps you too!
Click to expand...
Click to collapse
Going through relock and using xperia companion to update is way too slow, inefficient and you loose your data in the mean time.
Just download latest fw from xperifirm, get the new bootimage (unsin ), magisk it, flash the whole fw with new flasher in flash mode (usb + vol down), goto fastboot, flash magisk boot image, reboot, done !
You've lost 0 data, didn't lost root, and you have the new fw
That's nice, but bootlocker remains unlocked during the procedure I wrote about. Therefore no data is lost in the process.
I used newflasher before and softbricked my phone.
And it's always good to have an alternative.
All of the options are way too complicated, compared to using TWRP. But we sadly don't have custom recovery.
unicastbg said:
That's nice, but bootlocker remains unlocked during the procedure I wrote about. Therefore no data is lost in the process.
I used newflasher before and softbricked my phone.
And it's always good to have an alternative.
All of the options are way too complicated, compared to using TWRP. But we sadly don't have custom recovery.
Click to expand...
Click to collapse
I don't get how you soft bricked with newflasher, bad firmware maybe ? model crossflashing ?
I've always used newflasher since it's out, before I was using flashtool by androixyde and didn't had issues too
It stopped on the very last step. To be honest the first time I used FW for another region. When I realized that, I tried flashing the proper one, but newflasher always stopped on the very last step. Can't recall what it was checking or verifying for.
Today LSposed was updated and I ended up in bootloop. As @fastbooking was saying why not use newflasher. So I did. And I ended up exactly where I was before.
{
"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"
}
unicastbg said:
Today LSposed was updated and I ended up in bootloop. As @fastbooking was saying why not use newflasher. So I did. And I ended up exactly where I was before.
View attachment 5758521
Click to expand...
Click to collapse
Try an usb 2.0 port maybe
I tried everything the guys proposed on the newflasher xda thread. Sadly it made no difference. I tried different USB ports, cables, Windows, Linux... I'm giving up on an otherwise app with a great potential.
unicastbg said:
It might be common sense for some, but I didn't see this as a separate post and it might help people get around this.
Once you unlock the bootloader and root with Magisk, you can't have OTA updates from the phone itself.
But what you can do to get these updates is to use the Xperia Companion tool.
You have to go to Magisk first and click on Uninstall and choose Restore images. This will bring back your original boot image from a backup Magisk does when patching the image.
Once this is done, reboot and connect the phone with Xperia Companion. Allow file transfers through USB. No need for USB debugging.
If there's an update available, it will download and transfer it to your phone. You'll see the install process in the status bar.
Once this is done, you can reboot and verify the update was installed. Now it's time to use Magisk to patch the new boot image.
There's a good guide already made - here.
In short use XperiFirm to download the latest FW, get the boot-x... sin file, put it in the folder where you have unsin executable file and just drag it over unsin. This will produce an image file, which you copy to your phone. Start Magisk, Magisk -> Install, it will ask you where the image file is, so point to the location where you saved it.
The result file will be put in Downloads on your phone. Copy it over to your PC.
Reboot the phone to Fastboot (Volume Up and Power buttons, or turn off the phone and press Volume Up, then connect the USB cable), you'll see you're in Fastboot if the LED is blue.
Open CMD, point to the location where you have ADB files copied and type in:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Where magisk_patched.img is your image file, so just put in the name and location to that file.
For example: fastboot flash boot_a c:\temp\boot_X-FLASH-ALL-4BA8.img
If the command fails, type in fastboot devices and that should list one device - the phone you connected.
If no devices are listed, check if you have the drivers for your phone. The article link above lists all driver and utilities downloads.
I've used newflasher and it soft bricked my phone. Maybe it's something I did wrong, but using the above is way easier and safer, in my opinion.
Hope it helps you too!
Click to expand...
Click to collapse
hi, I have some questions, could you please help me explain:
1. Uninstalling magisk and rebooting backup boot image will wipe device data?
2. If I can't find back up of boot image, can I use the one downloaded from Xperifirm with the same build number of my device?
3. Is there any other way to update ota without haveing to reset device. Thanks
dieuluucanh said:
hi, I have some questions, could you please help me explain:
1. Uninstalling magisk and rebooting backup boot image will wipe device data?
2. If I can't find back up of boot image, can I use the one downloaded from Xperifirm with the same build number of my device?
3. Is there any other way to update ota without haveing to reset device. Thanks
Click to expand...
Click to collapse
Hi,
1. This won't wipe the device data nor change any system or user apps.
2. Yes, you can use a boot image of the same FW version as the one installed on the phone.
I even did it with a different version, by a mistake, and the phone booted OK. But I don't know what might go wrong so I can't recommend this.
3. OTA doesn't work with the patched by Magisk boot image. So you need to replace the image with the original one, restart, apply the OTA (via Xperia Companion), restart, replace with the patched file of the new FW boot image.
This process doesn't reset your data as it's on another partition. If you have a custom boot animation (the first one), it might be lost.
If we had a full TWRP support, the whole process would have been way easier. Developers are trying to get it to work, for which I'm grateful even if it doesn't work at the end.

Categories

Resources