no prenormal. now im hoping to find some who can patch a new G970FOXM3ASG8 AP for me.
[Magisk] Root for the Galaxy S10 Series
- Thread starter topjohnwu
- Start date
no prenormal. now im hoping to find some who can patch a new G970FOXM3ASG8 AP for me.
Did you transfer the gep.AP with ADB to the PC?
Without should often occur errors.
No but i did try to unzip it and it works.
Anyway thanks for your time and help. My phone decides to start properly now for some weird reason. After many restarts the phone decides to finish updating.
Last edited:
Did you reboot with the combo keys ( bixby, volume up and power buttons)? Make sure you hold it till u see the bootloader screen for couple more secs then let go. You will boot into the rooted mode
I did that a dozen times, and each time I saw an Android logo with blue background and a quick message saying 'erased', then the phone booted and device was not rooted.
Then decided to try flashing TWRP, but I just flashed (again) magisks_patched and all tar.md5 as per instructions and was still in download mode. So I pressed vol- and power to get out of download mode, and as I wanted to get back to it, kept pressing vol- and power. Instead of going back to download mode it just booted normally and device was rooted ! Magisk didn't even ask to configure anything, it was ready to go.
Is there any way to automotise this reboot. I mean I have to press 3 buttons on every reboot now. Is there any other way like writing a batch file or something for automatically boot into rooted mode with regular reboot option
Sent from my SM-G973F using Tapatalk
There are some tools that can do that. But you have to select > Recovery <. Then the phone boots with root rights.
Attachments
Alternatively to an app you can use this Magisk module:
https://xdaforums.com/app...r-0-7-t3680053
I only use the Magisk Reboot (Galaxy S10) option
I use FireFDS to solve this. I remove Restart button, leave Reboot to Recovery intact but change the text for it (using the option further down) to "Reboot".
--
Aside: thanks to everyone for their help in this thread, got me out of a sticky situation over the weekend.
---------- Post added at 12:19 PM ---------- Previous post was at 12:17 PM ----------
Thank you so much for this. Had no idea this was the case & first two attempts were made using an older firmware (because it made sense to me to use the same one when first rooting). Saw your comment in the thread and that sorted it. Much obliged!
If you have Xposed installed there's the brilliant module called Firefds Kit. With this you can customise the power button. You can even rename and remove some buttons. Screenshots below.
If you haven't yet got Xposed, go HERE for instructions how to install.
Magisk is not installed after an update
So I followed all the steps and was able to install Magisk and had everything working for more then a month... but Samsung had an update these days that enhances the camera using the same functionalities from Note 10 and I wanted to install this update on my working magisk phone.
I followed the instructions here on this link ( https://xdaforums.com/galaxy-s10/de...s10-series-t3918699/post80076303#post80076303 )
Basically I used Frija to successfully download the latest update for my mobile (used the correct model and CSC, etc).
Then I did exactly those steps:
- extracted the downloaded file
- copied the AP to my phone
- opened Magisk Manager
- disabled all modules (lib secure and smally patcher) and reboot the phone
- back at Magisk Manager hit Install, select patch a file and chose the AP I just downloaded
- Copied the "magisk_patched.tar" file to my computer using adb command
- power off and entered download mode
- opened Odin3_v3.13.3, deselect "reboot" under options
- chose the magisk_patched.tar as the AP
- BL, CP from the new firmware and HOME_CSC as the CSC
- hit start and waited until finish with success
- after flashed, I didn't wipe. Pressed and hold Vol-down and Power
- then I booted with the combo to start using magisk.
- after success updating all softwares I had EVERYTHING WORKING pefectly!
The issue was after I tried to re-enable the previously disabled magisk modules (as it was on the instructions).
My phone rebooted a lot of times and then it opened a screen saying that it was unable to open due to an error... that screen had the options to try again (what I did) or clear data.
Now I have my phone working again however magisk is showing as "magisk is not installed".
I already tried several times to boot using the combo with no lucky.
Also I tried to repeat all the steps again flashing the same file but this time with wipe data and formating the phone.. configured everything again but magisk is still not installed.
What did I do wrongly? I think that magisk corrupted after trying to enable the module... however now I cannot even have the magisk working again...
Please any help is appreciated.
So I followed all the steps and was able to install Magisk and had everything working for more then a month... but Samsung had an update these days that enhances the camera using the same functionalities from Note 10 and I wanted to install this update on my working magisk phone.
I followed the instructions here on this link ( https://xdaforums.com/galaxy-s10/de...s10-series-t3918699/post80076303#post80076303 )
Basically I used Frija to successfully download the latest update for my mobile (used the correct model and CSC, etc).
Then I did exactly those steps:
- extracted the downloaded file
- copied the AP to my phone
- opened Magisk Manager
- disabled all modules (lib secure and smally patcher) and reboot the phone
- back at Magisk Manager hit Install, select patch a file and chose the AP I just downloaded
- Copied the "magisk_patched.tar" file to my computer using adb command
- power off and entered download mode
- opened Odin3_v3.13.3, deselect "reboot" under options
- chose the magisk_patched.tar as the AP
- BL, CP from the new firmware and HOME_CSC as the CSC
- hit start and waited until finish with success
- after flashed, I didn't wipe. Pressed and hold Vol-down and Power
- then I booted with the combo to start using magisk.
- after success updating all softwares I had EVERYTHING WORKING pefectly!
The issue was after I tried to re-enable the previously disabled magisk modules (as it was on the instructions).
My phone rebooted a lot of times and then it opened a screen saying that it was unable to open due to an error... that screen had the options to try again (what I did) or clear data.
Now I have my phone working again however magisk is showing as "magisk is not installed".
I already tried several times to boot using the combo with no lucky.
Also I tried to repeat all the steps again flashing the same file but this time with wipe data and formating the phone.. configured everything again but magisk is still not installed.
What did I do wrongly? I think that magisk corrupted after trying to enable the module... however now I cannot even have the magisk working again...
Please any help is appreciated.
I am currently on ASH6. The phone has an unlocked bootloader, rooted and has TWRP ianmacd.
Now I have a question. I want to upgrade to ASIG. I want to try TWRP from Geiti94 but I have not read anywhere how to root ASIG. Is it traditionally with the help of Magisk or something else?
Now I have a question. I want to upgrade to ASIG. I want to try TWRP from Geiti94 but I have not read anywhere how to root ASIG. Is it traditionally with the help of Magisk or something else?
if u patch the AP file with ianmacd magisk manager you will get a failed patched AP(at least that was so with mine). what l did was:
- uninstalled ianmcd magisk manager (not magisk root)
- installed latest canary magisk manager
- rebooted (of course, with the key combos)
- patched ap as usual
- rebooted to download mod
- flashed patched ap and other firmware parts (bl, home csc etc) make sure auto reboot in odin is not ticked
- rebooted again to download mode, flash geiti94 twrp via AP slot in odin
- rebooted to twrp using the combo keys for it and let it do its process
- back in twrp, flashed muilt disabler
rebooted phone via recovery..
And my phone is working properly...
Good luck
Links to windows works perfectly with my s10+. Maybe reinstall "your phone" from windows store.
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
249Here comes official Magisk support for the Galaxy S10!
Let's get Magisk to kick start the development of these Samsung devices!
Link to Instructions
Carefully read through everything in the page linked above! Follow the instructions closely so you don't end up bricking your device
Technical Details
Google enforces all devices that ships with Android 9.0 to use system-as-root in part of "Project Treble", so Samsung finally introduced their own "flavor" of the implementation. More details regarding system-as-root can be found in the official Google dev site. Samsung is using the A-only system-as-root setup, meaning that its boot image will only contain the kernel binary without ramdisk included. Similar setup has already been deployed on many new devices, and the solutions for those devices are rather simple: add a new ramdisk section into the boot image and hexpatch the kernel to always use ramdisk as rootfs. However in Samsung's case, the bootloader simply does not load anything other than the kernel binary to the memory, meaning no matter what we do the kernel will always use the system partition as root directory. This leaves us no option but to install Magisk onto the recovery partition.
Installing to the recovery partition have its own issues: first is that a service called "flash_recovery" will run when the system starts up, which will restore the recovery image back to stock on startup. This is unacceptable because not only does it uninstall Magisk in the process, the data encryption key will also be changed due to fact that Samsung's data encryption keys are tied to the bootloader status and boot/recovery image signatures, and thus causing the device unable to boot in following reboots unless factory reset. The solution to this problem is to simply repack the boot image to remove the binary integrity and also the signature of the partition. The second issue is that since Magisk and recovery shares the same partition, how can we actually boot into recovery? (e.g. to factory reset your device, or have custom recovery co-exist with Magisk) Fortunately a solution that detects button key presses is introduced, which details are already provided in instructions.
To make matters even worse, Samsung introduced a "VaultKeeper" service, which adds another "lock" on top of the OEM lock of the bootloader. By default the service will "relock" the bootloader after data is wiped. Only after the initial setup will it verify the OEM lock option and changes the bootloader state accordingly. If you are running custom firmware with stock system, DO NOT try to wipe data or else you might end up bricking your device due to vaultkeeper locking your bootloader up, which will eventually lead to bootloader refusing to boot because unofficial partitions are detected.
For custom ROM developers, the first few things you would want to remove is VaultKeeper to protect your users from bricking their devices. For stock ROM users, just make sure to always boot to Magisk after a data wipe, or never power off your device before finishing the initial setup and verify OEM lock is enabled.22OK guys, @PillowCake[/MENTI[SIZE="3"][/SIZE]ON] [MENTION=5902940]bininga59 @Norup58
In the interests of accuracy for everyone, afterall this what XDA is all about isn't it, I am scrubbing previous post and re-worded a new one.
---------- Post added at 06:24 PM ---------- Previous post was at 06:14 PM ----------
Firmware updates and keeping your data,
for phones Magisk rooted without TWRP.
Just download new firmware, copy the AP file of the new firmware to your phone.
Open Magisk Manager, ensure Magisk is up to date, if not, update it.
When Magisk is up to date, if you have any Magisk Modules running, go into Modules and disable them (no need to uninstall them). Then reboot and go back into Magisk Manager.
Hit the top INSTALL, select INSTALL again then select 'Select and Patch a File'
Locate the new AP file from your new firmware and patch it. Then copy the magisk_patched.tar back to your computer, preferably with ADB to minimize corruption during transfer.
Power off phone and reboot to Download mode.
Open Odin 3.13.1 on your computer, and
deselect Reboot under Options tab. Now use the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly HOME_CSC into the CSC slot. Press start and let Odin do it's stuff.
When flashed, do not wipe. Press and hold Vol-down and Power, when screen goes off, quickly change to Vol-up, Bixby button and Power. As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Just re-enable your previously disabled Magisk modules.16
Galaxy S10 Firmware update.
The Galaxy S10 May firmware update has started to appear and users will be wanting to update their firmware without losing their data and keep their Magisk root.
For phones with Magisk root only without TWRP.
The process is similar to when you first rooted your phone but you need all the firmware files and DO NOT wipe.
Download your new firmwware using Frija or Samfirm, making absolutely sure it is the correct version for your phone model and region (csc), you can use an app such as 'Phone INFO' to help here.
Unzip the downloaded file to an easy place to find on your computer.
From this unzipped folder locate the file name beginning AP and copy this file to your phone.
On your phone open Magisk Manager and hit INSTALL against Magisk, prompt will come up, hit INSTALL, Select Method - Select and Patch a File, then choose the AP file you have just copied to your phone. Let Magisk process complete.
Copy the new magisk_patched file on your phone back to your computer, preferably the same folder you copied the AP from.
Open Odin (use Odin3_v3.13.1) On Odin Option tab untick Auto Reboot.
Power off your phone and connect it to your computer. Press and hold volume-down until Download screen appears then volume-up to continue. On Odin the box below ID:COM should turn blue.
For the AP option select the magisk_patched file, then select the BL file and the CP file, then the HOME_CSC file.
Click Start and let the process complete - several minutes.
Now the nimble fingers bit, remember NO WIPE. Press and hold Bixby button, (Bixby is superfluous but convenient at this first point) Vol-down and Power, when screen goes off, quickly change to Vol-up button whilst still holding Bixby and Power. As soon as screen appears, let go of all buttons.
Your phone will now reboot into Magisk rooted mode with all your data intact.14Hi John (@topjohnwu),
Great job with this find & guide for it. It works flawlessly if all the steps are followed 100%. Thanks!
I've made a full video tutorial (including ROM downloading and everything), maybe it'll help others who have had problems or just want to see the process while or before they perform it.
Feel free to post it in the OP if you think it helps in any way.
The video link is as follows: https://youtu.be/o3a8YnWT3yk
Thanks!12Last night, I used Magisk Manager to patch the AP file from the ASD5 firmware. This is actually the first time I have upgraded in this way, and I must say that John has made life extremely easy for all of us.
I just wanted to give a tip for anyone who is already running TWRP on their device at the time they need to update their firmware.
Using John's procedure, you'll have to enter download mode a second time to re-install TWRP and re-disable encryption. Since I screw up getting into download mode once in a while, I find it a nerve-racking experience, since failing to boot into download mode at this juncture could initiate a system reboot that would re-encrypt /data.
So, before you flash the patched AP, you can make a copy of your existing Magisk-rooted TWRP recovery. For example, a quick way to do it is by typing this in a root shell:
Code:# dd if=/dev/block/sda15 of=recovery.img
Next, replace the stock recovery image in the AP file that you patched using Magisk Manager. On Linux, that would look something like this. Adapt these commands for whichever platform you use.
Code:$ tar f magisk_patched.tar --delete recovery.img $ tar rf magisk_patched.tar recovery.img
Now, when you flash the resulting file in Odin and reboot, all you have to do is hold the recovery combo down until you reach TWRP. Then, simply disable encryption again (e.g. by flashing my own multidisabler zip) and reboot.
I followed the above procedure myself last night and it worked like a charm.
New posts
-
-
I have a problem with rear camera settings on Junsun V1 Pro (I need help)
- Latest: www_marek@op.pl
-
