Related
Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You
Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.
Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.
1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.
Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.
Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again
I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.
Ok.Thank you very much.I will learn more ...
Firstly, I apologize if this is posted in the wrong place and topic has been covered before, but I really need your help!
I got the A6 brand spanking new 4 days ago, and have managed to flash TWRP (TWRP-3.2.3-TwrpBuilder-a6ltexx-2018-11-26_20-43.tar) successfully and get RMM-State_Bypass_Mesa_v2.zip, Magisk-v18.0.zip & no-verity-opt-encrypt-6.0.zip (in that exact order) and I thought was all good.... BUT here lies the problem, after I have flashed the above files, I need to update Magisk to the latest version to be able to use the Magisk Hide & Superuser functions.. Whenever I have updated Magisk, either by direct install or download only then install in TWRP, it makes the phone reboot at random intervals..
it can be hours between reboots or it can be minutes, it goes blank and restarts from the android boot animation, where I have to enter my pins to be able to use it again.. WHY is Magisk causing this random reboot and how can I fix it??
Ive re-flashed the A600FNXXU3ARL1_A600FNOBE3ARL1_EVR (Android 8.0.0) a good few times now, but this random reboot bug Isn't present since I flashed it back to stock..
Also, a separate question; WHY are certain android apps refusing to run due to phone being rooted?? I thought once you re flash official stock firmware the phone appears "warranty intact"?
I used to be up-to-date with android rooting & modifying back in the day, but I have been out of the loop for a long time.
Thanks for your patience reading this and thanks in advance for any help/answers/time taken by me.
Arty.
Magisk on Oreo doesn't work well if you don't have the one with anti defex version as the kernel keeps avoiding you to use superuser commands as part of security feature even after rooting.
About the stock apps refusing to work after flashing the stock rom, you already tripped knox while flashing twrp which once gone you won't be able to turn back. But flashing a custom kernel would fix such problems most of the time.
henok.gk said:
Magisk on Oreo doesn't work well if you don't have the one with anti defex version as the kernel keeps avoiding you to use superuser commands as part of security feature even after rooting.
About the stock apps refusing to work after flashing the stock rom, you already tripped knox while flashing twrp which once gone you won't be able to turn back. But flashing a custom kernel would fix such problems most of the time.
Click to expand...
Click to collapse
Thank you for your reply!
How do I get said anti defex version? Ive tried googling it but only found unrelated results, could you please point me in the right direction in how to proceed please? thanks
Arty.
I can't point you a direct link with a magisk version you need to flash to get rid of defex. If you're lucky you may get a custom kernel built including it. Try one of the oxygen/phoenix kernels through this A6 thread.
The kernels will also help you byass all knox security related stuff which in turn will help most stock apps get back to working state expect for samsung pay and secure folder.
Hi,
I hope somebody can give me a hint.
I just got a used p20 pro with open bootloader but stock rom.
Unfortunately the Google security check has some "problems" with this situation and doesn't allow me to use several apps like Netflix, Google pay, etc.
So I'm looking for a way to easily fix this problem, the phone will be used by my parents.
Either lock the bootloader or "hide" it probably.
But how - I don't have the bootloader code - and I'm not too much into android rooting...
Usefull hints are appreciated.
Merry xmas
Mounty
You're on thin ice my pedigree chum..
Avoid flashing anything that would allow a block of any kind which is an absolute reality.
Having used absolutely every ROM and OS from 8.1 to 10
My advice. Flash AOSIP and then ask in thread to get safety net working.
Literally nothing else it worth your time.
Unless you're strange and like EMUI.
In such case, stuck with stock.
Just be aware you're in a position that a lot of people would kill for.
Google have done some **** stuff to make people who have unlocked bootloader a nightmare. I don't think there is a way to hide it unless you use Magisk
mounty77 said:
the phone will be used by my parents.
Click to expand...
Click to collapse
If they are not some kind of advanced users, unlocked bootloader has exactly 0 added value for them. Search the forum for flushing methods, the ones that will warn you that this method re-locks the bootloader, flush the latest stock ROM for your region and live a happy and calm life.
As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.
Horayken said:
As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.
Click to expand...
Click to collapse
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty
mounty77 said:
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty
Click to expand...
Click to collapse
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
thx for your offer/advise. I’ll try this way - it sounds most promising to me.
Can I do this on the mobile only, or do I need a pc?
Where / How do I find the ramdisk recovery?
BL Lock
I can lock (yes, lock) your bootloader for free.
Contact me at Telegram (@AntiEngineer), you don't need to open up your device.
abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
unfortionatly I wasn´t sucessfull till now.
At https://openkirin.net/ is a very usefull description availaible but I´m still searching for the RAMDISK Extract. I found that database where you can donwload several versions, but mine wasn´t provided there
https://pro-teammt.ru/en/online-firmware-database/
My Version is:
CLT-L29
10.0.0.138 (C432E3R1P3log)
Anybody knows where I can download that`?
Best regards
mounty
@mounty77
You are on Android 10 Beta?
Root on Android 10 Beta not working for me.
You are on Android 10 Beta?
Root on Android 10 Beta not working for me.
Click to expand...
Click to collapse
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader
mounty77 said:
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader
Click to expand...
Click to collapse
Installing a "RECOVERY_RAMDIS.img" patched with Magisk is rooting the phone.
I´m fine if i have to root it to hide the open bootloader
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
ZeroXO said:
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
Click to expand...
Click to collapse
Okay I was thinking I might of missed something. The patch for oem issue I thought covered that.
Is the unknown (bat) firmware the one I need to flash to stock?
Sent from my OnePlus6T using XDA Labs
TheLogicalGamer said:
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
Click to expand...
Click to collapse
Using odin 13.1.3 is recommended.
As you have the N950F, it is part of the multi OXM CSC, so you can flash the filmware for you country and carrier if desired (N950F)
If you want to root, I suggest just flashing a custom rom or kernel, as they have been patched for the RMM KG state issue.
How to Root Samsung S23/S23+ *Newbie Guide*
Attention, FYI:
The Root method was performed and successfully tested with a Samsung Galaxy S23 SM-911B/DS.
I do not guarantee that it will work on the other models, I can not test it because I do not have the devices.
However, it would be nice to hear if you have done it on another device model and it all works out, post here in the forum which model you have rooted.
Spoiler: Galaxy S23 - Model Information
SM-S911B -- Europe / Africa / Middle East / Oceania
SM-S911B/DS -- (assumed same as above, Dual SIM)
SM-S911U -- USA
SM-S911U1 -- USA ( factory unlocked )
SM-S911W -- Canada
SM-S911N -- Korea
SM-S9110 -- China / Taiwan / Hong Kong
SM-S911E -- Latin America
SM-S911E/DS -- (assumed same as above, Dual SIM)
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 ROM is patched for all these mentioned features. 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.
Once you root the device, you will forever receive the following message: "Access denied - Unauthorized changes have been made to your phone. To get help, contact Customer Service.". Even if you reset the device back to factory settings and lock the bootloader, the message remains !!!! (with root there is a solution).
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.
First of all you need the following tools.
*A previously unlocked bootloader is the prerequisite!!*
Download last Samsung Drivers.
Download Odin v.3.14.1. (Thanks to realbbb)
Download Frija or Bifrost (Github Info)
Download Magisk v26.1 (Github Info) (Please use only this Magisk APK.)
1. Go into your Phone to developer mode and activate USB-Debugging
2. Install Magisk v 26.1 APK.
3. Download your (new) Firmware in Frija or Bifrost and Unzip File to PC.
4. Unzip Downloaded Firmware.zip.
5. Take from Unpacked Firmware.zip the "AP" to your Phone and open Magisk.
Go in Magisk to Install (from Device Slot) and take file the "AP- Data" from Storage and patch.
6. After Patch go your Download Folder from Device there is a MagiskPatched .tar Data. (your new AP-Data !)
Take the MagiskPatched.tar Data from your Phone to you Computer. (in same Folder like the Firmware files)
7. Open Odin on PC and turn off your Phone. Once your device is turned off > Hold Vol. UP + DOWN and Connect your USB-C cable from PC to your Phone. (Now start your Phone in Download Mode.) > Klick 1 time Vol. UP to start Download Mode.
Now in Odin your Device must be connected like "0:COM (Number)" in blue.
8. Now take from Unpacked Firmware.zip >
BL to BL
AP to MagiskPatched.tar
CP to CP
CSC to ***Read Attention***
*** Attention important!!! ***
#CLEAN - If you flash the first time Magisk clean on your device you must use the "CSC_OXM". (Accordingly, you lose all data and must set up your device again!!!)
#Update_Firmware - If you already have Magisk on your device and only make a firmware update take only the "HOME_CSC_OXM" !!! With the "HOME_CSC_OXM" you will not lose any data!
Start the Flash in Odin. (it takes 5 - 10 minutes!!!) Make sure that the cable is not accidentally touched / disconnected. It is best to use the supplied cable! Make sure that the cable has no loose contact and is seated correctly!
9. When the flash is finished, Odin says 1/Successful.
Your device will now restart automatically.
10. Once your device is successfully booted, open Magisk-App and you are successfully rooted. (A further reboot is automatically performed by Magisk!)
Finish !!! Gratulation !!!
If you have rooted your device I recommend the following Magisk extensions:
- Magisk Bootloop Protector v1.8.1-10015 - Safe you from Bootloop if u add wrong Magisk Module.
- BusyBox v1.0.4 - must have...
- SafetyNetFix v.2.4.0 > to pass SafetyNet and use Apps like Banking, etc.
- digitalkey_disabler_afaneh92 v1.0 > to FIX pop-up message "Access denied - Unauthorized changes have been made to your phone. To get help, contact Customer Service.". Even if you reset the device back to factory settings and lock the bootloader, the message remains !!!! (with root there is a solution)."
- ***Knox Patch v.0.5.0 (Thanks to BlackMesa123) > to FIX any Samsung Apps.
***For the KnoxPatch you need LSPosed v.1.8.6-6712-zygisk-release + KnoxPatch-APK + the KnoxPatch-Magisk modul.
Attached I have created a folder where I upload more Magisk extensions and APK tools for the S23. I will try to maintain it. If something useful is added I will pin it directly.
Root-Tools-Collection
If I have forgotten something, complement me.
Greetings Ramme
Do you have experience with ROM tool from Dr.Ketan? In this Magisk module there is an AdFree option and a lot customization. I thought that then KnoxPatch isn't needed because the fixes are also included.
waterpolo said:
Do you have experience with ROM tool from Dr.Ketan? In this Magisk module there is an AdFree option and a lot customization. I thought that then KnoxPatch isn't needed because the fixes are also included.
Click to expand...
Click to collapse
Yes, I personally use the Dr.Ketan Pro version. However, I try to work without the ROM-tool this time.
There is the ROM-tool-apk and if you pay the ProTwearks-extension-apk.
The problem is that you have to reset all settings in both tools after each system update, so I personally see no advantage in the ROM tool. With the last firmware update I was a little too hasty and have even shot me the ROM tool.
Unfortunately, Dr. Ketan makes no FULL ROM for the S23/S23+ so you have to live with it.
The Pro version is personally only for debloat.
On the subject of AD-Free, this is a nice extension, but this is a non-configurable AD-blocker, so you can not set personal configurations such as adding exceptions. So the classic and well working way use AdAway.
For AdAway there are some sources, I recommend if you are lazy the GoodbyeAds source + Own Exceptions.
Regarding the Knock Patch, I can't say anything about it, I use the file I pinned + LS-Posed (as a shortcut) and it works fine.
My SafetyNet is PASS.
Hello will this work on galaxy s23 sm-s911n ?
If not, do you have root instructions for sm-s911n
cashmonkey said:
Hello will this work on galaxy s23 sm-s911n ?
If not, do you have root instructions for sm-s911n
Click to expand...
Click to collapse
If you have the possibility to unlock the bootloader, it should work. The steps do not change.
However, I can't guarantee that it will work, so you have to try it at your own risk.
As far as I know, the bootloader cannot be unlocked on the US models, so you have no possibility to root there.
Ramme said:
If you have the possibility to unlock the bootloader, it should work. The steps do not change.
However, I can't guarantee that it will work, so you have to try it at your own risk.
As far as I know, the bootloader cannot be unlocked on the US models, so you have no possibility to root there.
Click to expand...
Click to collapse
Thank you for the prompt reply!
I'm in USA T-Mobile and purchased the galaxy s23 sm-s911n so I can get the 512gb version
I'll let you know when I get the phone and try the rooting to see if it works.
Fingers crossed
Thanks
hello there
after a further reboot automatically performed by Magisk,i lose root again,how to fix it
thanks
zeroabcdezero said:
hello there
after a further reboot automatically performed by Magisk,i lose root again,how to fix it
thanks
Click to expand...
Click to collapse
Did you use Magisk S23 version.
Last week my S23 rooted with the procedure in OP and have still root.
zeroabcdezero said:
hello there
after a further reboot automatically performed by Magisk,i lose root again,how to fix it
thanks
Click to expand...
Click to collapse
I had exactly the same problem, so it is very important to use exactly this Magisk version, which I have linked. Also, after installing Magisk, do not update Magisk for the time being.
Ramme said:
I had exactly the same problem, so it is very important to use exactly this Magisk version, which I have linked. Also, after installing Magisk, do not update Magisk for the time being.
Click to expand...
Click to collapse
Succeded!
Thank you again.
Ramme said:
I had exactly the same problem, so it is very important to use exactly this Magisk version, which I have linked. Also, after installing Magisk, do not update Magisk for the time being.
Click to expand...
Click to collapse
is the APK you linked the same as the canary version from the official Magisk GitHub?
Enddo said:
is the APK you linked the same as the canary version from the official Magisk GitHub?
Click to expand...
Click to collapse
No this is the APK which was posted in the "How to Root" topic by Dr. Ketan. This is currently the only Magisk APK that works with the S23 models.
For more info about the Magisk(KlickME). (Thanks to @BlackMesa123)
I have only uploaded everything separately in my cloud, on the one hand so that I can find the data quickly, on the other hand so that I can always keep the data up to date.
The only thing stopping me from rooting is losing Samsung Pay, which allows me to pay for public transportation without needing to unlock/authenticate.
Is there a way to retain Samsung Pay after rooting?
Gymcode said:
The only thing stopping me from rooting is losing Samsung Pay, which allows me to pay for public transportation without needing to unlock/authenticate.
Is there a way to retain Samsung Pay after rooting?
Click to expand...
Click to collapse
No there is (currently) no possibility to use SPay, there probably won't be.
You can use GPay as an alternative.
But it is also all described above in the topic. Please read it carefully before questions are asked. Alternatively, use a translator...
If new special possibilities come, I will of course share them with you, if you discover important features, please share them with me as well.
Adway is updated:
Releases · AdAway/AdAway
AdAway is a free and open source ad blocker for Android. - AdAway/AdAway
github.com
Hello all,
I'm running into an issue rooting S23 Plus that im not finding any information about online.
My boot loader is unlocked, I've followed the process to root. After installing the patched file from Magisk, the phone boots fine and gives me the setup, but I get an error at the portion where I accept Samsung terms. I just get -45
If I erase the phone back to the default FW, the setup completes without issue.
Has anyone ever seen this error before?
balbosta said:
Hello all,
I'm running into an issue rooting S23 Plus that im not finding any information about online.
My boot loader is unlocked, I've followed the process to root. After installing the patched file from Magisk, the phone boots fine and gives me the setup, but I get an error at the portion where I accept Samsung terms. I just get -45
If I erase the phone back to the default FW, the setup completes without issue.
Has anyone ever seen this error before?
Click to expand...
Click to collapse
Unfortunately not yet seen/had.
Try to reset your device according to my instructions, but for the first time without Magisk. Do not use the Home_CSC, but the normal CSC for the first time.
If your device can be set up and you get into the system, repeat the flash process with Odin, but now use the patched AP file and the Home_CSC file.
Now your device should boot, is set up and it should also have Magisk on it.
Ramme said:
Unfortunately not yet seen/had.
Try to reset your device according to my instructions, but for the first time without Magisk. Do not use the Home_CSC, but the normal CSC for the first time.
If your device can be set up and you get into the system, repeat the flash process with Odin, but now use the patched AP file and the Home_CSC file.
Now your device should boot, is set up and it should also have Magisk on it.
Click to expand...
Click to collapse
Okay, so just to confirm I'm doing this all correctly, since I'm fairly new to rooting.
I've downloaded the stock FW from Samfrew.
It contains 5 files.
AP, BL, CP, CSC, and HOME_CSC
On a clean install, I need to transfer AP to the phone and use Magisk to patch. After patch, I move back to my PC.
In Odin, I should be using AP from Magisk, then BL, CP, and HOME_CSC files from stock FW.
Is this correct?
balbosta said:
Okay, so just to confirm I'm doing this all correctly, since I'm fairly new to rooting.
I've downloaded the stock FW from Samfrew.
It contains 5 files.
AP, BL, CP, CSC, and HOME_CSC
On a clean install, I need to transfer AP to the phone and use Magisk to patch. After patch, I move back to my PC.
In Odin, I should be using AP from Magisk, then BL, CP, and HOME_CSC files from stock FW.
Is this correct?
Click to expand...
Click to collapse
Download your ROM in Frija.
Take out all the data.
Flash as follows:
BL, AP, CP, CSC. ( do not use the magisk-Patched-AP data)
Boot your device, set it up.
Once it's set up, install the Magisk APK version I post above and launch Magisk.(Dont Update Magisk!)
Drag the AP file to your device, patch the AP into Magisk and make it back to your PC.
Now flash BL, (Magisk-AP), CP, Home_CSC.
Then your device should boot normally and magisk is installed.
Ramme said:
Download your ROM in Frija.
Take out all the data.
Flash as follows:
BL, AP, CP, CSC. ( do not use the magisk-Patched-AP data)
Boot your device, set it up.
Once it's set up, install the Magisk APK version I post above and launch Magisk.(Dont Update Magisk!)
Drag the AP file to your device, patch the AP into Magisk and make it back to your PC.
Now flash BL, (Magisk-AP), CP, Home_CSC.
Then your device should boot normally and magisk is installed.
Click to expand...
Click to collapse
I tried this step by step.
After flashing with BL, Magisk-AP, CP, and Home_CSC, the phone will not boot. Eventually it tells me I need to factory reset. If I factory reset, the phone will boot to the setup, but im still met with "-45" when the phone should activate.