-
We are moving to xdaforums.com!
Posts made between now and when the migration is complete will not be carried over.
You will be automatically redirected once the migration is complete.
How To Guide Samsung Galaxy A54 5G [Root Stock ROM with Magisk]
- Thread starter knighToFdemonS
- Start date
Same issue for a French A54
Don't know how to fix that annoying nag screen....
i haven't this with the stock rom...
Yes same here Fred (FR + Bouygues), and no issue with stock
I tried a few queries like "force reset network capabilities" things like that, to no avail
It's still manageable (switch app twice after clicking "redémarrer", because after clicking this button the screen is like frozen), but painful yet
I know very well OP is not responsible for the firmwares we can download from samfrew or sammobile, so I'm not throwing any stones here
However, would loooove to get rid of that glitch! ^^
Maybe it's specific to French firmwares that are broken somehow, and we must wait for an update from Samsung.
Or maybe we should have downloaded an older firmware, and proceeded afterwards with an update directly on the phone...
too lazy to try, I must confessYes same here Fred (FR + Bouygues), and no issue with stock
I tried a few queries like "force reset network capabilities" things like that, to no avail
It's still manageable (switch app twice after clicking "redémarrer", because after clicking this button the screen is like frozen), but painful yet
I know very well OP is not responsible for the firmwares we can download from samfrew or sammobile, so I'm not throwing any stones here
However, would loooove to get rid of that glitch! ^^
Maybe it's specific to French firmwares that are broken somehow, and we must wait for an update from Samsung.
Or maybe we should have downloaded an older firmware, and proceeded afterwards with an update directly on the phone...
I tried many things like you with no luck ( SFR too) install/unistall Carrier from google, remove APN parameters.
i will run under stock rom until someone find the trick.
hope he/she will read this thread
Hey, I had the same issue, you can disable the system packages responsible for that nasty popup. Via adb shell or any terminal emulator :
Bash:
su
pm disable com.samsung.android.sdm.config
pm disable com.samsung.android.cidmanagerYou can also use any debloater to blacklist packages named (in French): "Mise à jour configuration"
The only weird thing I see is sometimes a random reboots that happens after a manual reboot, but it's okay.
EDIT: I know it's not the root of the issue but only a small patch on it, but it makes magisk usable until a definitive patch will be out
Are you talking a/b downgrading from the current firmware on my A54 device by using Odin to flash it? That's the only logical method that I could think of w/o unlocking the bootloader...
It's maybe not Magisk's fault, it could be a knox related issue for example, one should investigate that and if it's really coming from Magisk, then I think we could report the bug.
@Nitorac :
could it be only a french issue ?
this rom is not a XEF only like before but an EUX so, a lot of foreign users should report this bug...
a noticed that the root procedure is a bit different than other android versions :
before this A54 i was owning an A40
with this phone i just a had to patch the boot.img located in Ap file with magisk and then flash this boot.img zipped in a tar file with odin and the root was done.
with this A54 and android 13, i had to flash all this big AP file.
i tried the old good procedure with this new A54 with no luck (just flashing the boot.img)
and i neved had an issue like this about carrier update before.
like you said, perhaps it's not a magisk issue, knox, or just the carrier that detects root ?
Could we backup the carrier settings from a stock Rom and then over write it to the rooted rom ?
could it be only a french issue ?
this rom is not a XEF only like before but an EUX so, a lot of foreign users should report this bug...
a noticed that the root procedure is a bit different than other android versions :
before this A54 i was owning an A40
with this phone i just a had to patch the boot.img located in Ap file with magisk and then flash this boot.img zipped in a tar file with odin and the root was done.
with this A54 and android 13, i had to flash all this big AP file.
i tried the old good procedure with this new A54 with no luck (just flashing the boot.img)
and i neved had an issue like this about carrier update before.
like you said, perhaps it's not a magisk issue, knox, or just the carrier that detects root ?
Could we backup the carrier settings from a stock Rom and then over write it to the rooted rom ?
All US version samsung phones, be it unlocked version or carrier versions, are not eligible for bootloader unlock. There are some paid 3rd party service to unlock bootloader like the A53.
100% sure unless you are talking about old samsung phones before 2017. I am talking about a fact, not assertion.
No us version samsung phones after galaxy S7 are eligible for official bootloader unlock.
I agree !
I also have observed this and I was wondering if it's related. I googled some forums to create a single-CSC rom with XEF instead of EUX but for now I have no clues.
I think it worked that way on A40 because you had already applied a custom vbmeta and samsung multidisabler.
On this rom, when giving to Magisk the full rom, it patches the boot.img and vbmeta.img
> like you said, perhaps it's not a magisk issue, knox, or just the carrier that detects root ?
I don't know, maybe when I'll have time I could investigate that.
> Could we backup the carrier settings from a stock Rom and then over write it to the rooted rom ?
It could work yes !
I'm new to Android firmware patching, ecosystem, compilechain and stuff.
I achieve to port TWRP for the A54 5G by learning from afaneh92 TWRP ports for other devices : https://github.com/Nitorac/android_device_samsung_a54x
The recovery boots but there is many errors probably due to lack of multidisabler and I think I did something wrong with the partition mounts (/etc/fstab) but I don't know why (maybe I have to convert vendor's EROFS to F2FS RW but I have no clues).
If you have no data to loose and you want to test it : https://github.com/Nitorac/android_device_samsung_a54x/tree/main/manual_builds/b1f7b7b
I will try to fix the errors but since my A54 5G is my main phone, I have to make backups everytime I dev on it x')
I achieve to port TWRP for the A54 5G by learning from afaneh92 TWRP ports for other devices : https://github.com/Nitorac/android_device_samsung_a54x
The recovery boots but there is many errors probably due to lack of multidisabler and I think I did something wrong with the partition mounts (/etc/fstab) but I don't know why (maybe I have to convert vendor's EROFS to F2FS RW but I have no clues).
If you have no data to loose and you want to test it : https://github.com/Nitorac/android_device_samsung_a54x/tree/main/manual_builds/b1f7b7b
I will try to fix the errors but since my A54 5G is my main phone, I have to make backups everytime I dev on it x')
What do you guys (with no OEM unlock option) get, when you enable USB debugging and try to unlock it via fastboot?
Seems like the command for that has changed over time, try "fastboot flashing unlock", "fastboot oem unlock" ... there seems to be a few iterations. does that work or what error do you get?
Seems like the command for that has changed over time, try "fastboot flashing unlock", "fastboot oem unlock" ... there seems to be a few iterations. does that work or what error do you get?
Right tf on! Or why would you not want to?Funny how this pops up in every thread here
and to settle the argument: install a custom rom to get rom updates beyond the manufacturers lifetime support, simple as that. faster security updates, debloating, etc, dont get me started.
If you don't know the benefits and risks and effort/time/patience to root, go up several levels to a different thread or board. Wondering with open mouth and neutral brain in a model specific board with rooting issues doesn't add anything of value here. You will hopefully get a polite response but don't expect one.
Maybe I missed it earlier in the thread, but it's always good to mention bootloader locking initially to be sure you know the Samsung Corporate policy, which seems to be US + Broadcom specific. The second important thing for everyone to know is whether you're working to root stock firmware or not.
The answers to that used to be that non-stock required root but there are claims that non-stock firmware can be implemented without root: I haven't attempted that on a Samsung device. Anyone that suggests it's better or even possible should have done it themselves and be ready to answer specific questions.
Anyone new here should note that a number of people will claim to have done something a very seasoned developer has found from experience will not work. As with DNA mutations rarely are these repeatable or beneficial without serious introduced device problems. My advice on this, consult with a senior technical person here before making claims and never offer, 'yes that worked' unless you did exactly what was specified and you can prove it.
I'm still in the doubt phase of A54, my first non-S flexibility. Not only for root, but now also removable storage, an insidious inflation to retail pricing with no benefit, like other iPhone innovations like the audio jack. Note that both were sold as space saving and water resistance required and were both were manufacturer cost plus revenue upside building changes, for the manufacturer for memory and more broadly through Bluetooth headphones/sets that always have vendor specific settings.
Maybe I missed it earlier in the thread, but it's always good to mention bootloader locking initially to be sure you know the Samsung Corporate policy, which seems to be US + Broadcom specific. The second important thing for everyone to know is whether you're working to root stock firmware or not.
The answers to that used to be that non-stock required root but there are claims that non-stock firmware can be implemented without root: I haven't attempted that on a Samsung device. Anyone that suggests it's better or even possible should have done it themselves and be ready to answer specific questions.
Anyone new here should note that a number of people will claim to have done something a very seasoned developer has found from experience will not work. As with DNA mutations rarely are these repeatable or beneficial without serious introduced device problems. My advice on this, consult with a senior technical person here before making claims and never offer, 'yes that worked' unless you did exactly what was specified and you can prove it.
I'm still in the doubt phase of A54, my first non-S flexibility. Not only for root, but now also removable storage, an insidious inflation to retail pricing with no benefit, like other iPhone innovations like the audio jack. Note that both were sold as space saving and water resistance required and were both were manufacturer cost plus revenue upside building changes, for the manufacturer for memory and more broadly through Bluetooth headphones/sets that always have vendor specific settings.
Last edited:
I'm not sure how you're defining official, but several phones including US versions have bootloader unlockable by paid service. That's certainly not official Samsung and "official rooting" may be done by other manufacturers but I've never seen that claim on a Samsung mobile or tablet.
Official means manufacturer (samsung) allows bootloader unlock and samsung will provide the OEM unlock toggle in the settings and the bootloader unlock procedure in the firmware.
Samsung phones/tablets in non-us markets allow for official bootloader unlock. Samsung non-cellular tablets in the US are also eligible for official bootloader unlock.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7
Funny how this pops up in every thread here like people get paid to go to a forum for custom roms and then leave their opinion, why a custom rom is useless...just why? how do you people even get here, arent you in the totally wrong place?
and to settle the argument: install a custom rom to get rom updates beyond the manufacturers lifetime support, simple as that. faster security updates, debloating, etc, dont get me started.4WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel4Recommended changes:
- Build Number need only be tapped 8 times to activate developer mode, not ten.
- After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
- Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
- The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
- The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.
"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.
"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)
"App > Installed" shows the currently installed version of the Magisk app2
Thank you kindly for this! I am quite a noob so I don't want to reflash the ROM all the time either ^^
Not sure about these adb commands, but I might have a look if I have time (this is my gf's phone, I don't want to bother her all the time)
Btw, for the installation, I had to do these steps (most are identical, but some are slightly different or more specific):
- ### Preparation steps:
- "Called"
*#1234#to get CSC and other information - I used SamMobile (premium sub to get the file quickly because I was in a hurry -- this is not a promo, I have zero link with them whatsoever)
- Went to this thread to get Odin 3.14.1 3B PatcheD (not sure it changed anything)
- Did the steps to activate developer mode, USB debugging, OEM unlocking (it did not wipe anything for me)
- Turned the phone off
- Turned it on again using VOL+ and VOL- at the same time (had to try again because it didn't work the first time)
- Another option is to use ADB:
adb reboot recovery(first you have to list devices, and if need be authorize (from the phone) ADB to access it) - In the blue screen, written at the center, are the options you can "press" for (not easy to see at first)
- So, LONG (!!) press VOL+ to ask to unlock bootloader
- SHORT press VOL+ to confirm unlocking the booloader (which will wipe data)
- Reboot phone
- ### Firmware/flashing steps:
- On the PC, unzip the Samsung firmware
- Put (only) the "AP" file into the phone (e.g. "Downloads" directory) (I had first to remove the trailing ".md5" from the filename to only keep ".tar", not sure it is mandatory but I didn't want to lose 12 minutes of copy for nothing)
- Install Magisk on the phone (ONLY from their GitHub : topjohnwu) (you have to do it AFTER the bootloader is unlocked, if I understood things properly)
- Using Magisk, click the first "install" button at the top (which will actually patch an AP file), choose the AP.tar file from your "downloads" folder (for example)
- When done, copy the newly generated file (
magisk_patched-26100_{UID}.tar) to the computer (I first had to unplug USB and replug, because it would not refresh the folder properly, at least on Windows 10) - The file was already in .tar extension (at least for me) so I didn't have to compress it again
- Reboot the phone in recovery or "download mode" (using the same steps as earlier)
- Launch Odin, plug the phone, and flash the Magisk-patched AP file (only this file) (leave the options to their default)
- It should reboot the phone when it's done
- ### Magisk-related steps:
- Install Magisk again (it should (??) be wiped iirc), it will ask you to reboot after some changes it automatically made
- Reboot
- Relaunch Magisk, go to options, activate Zygisk: it will install a new module
- Reboot
- Go to Magisk, enable systemless host file (or something like that) so that ad blockers (e.g. AdAway) can work properly
- Reboot
- Go to Magisk again and enable "hide magisk" from the options, choose a custom name
- Reboot one last time (not sure you have to reboot for each Magisk step, it's just to be sure)
Thank you again for the tutorial!
For the carrier services, I tried to "reset network" but it didn't do anything.2I'm new to Android firmware patching, ecosystem, compilechain and stuff.
I achieve to port TWRP for the A54 5G by learning from afaneh92 TWRP ports for other devices : https://github.com/Nitorac/android_device_samsung_a54x
The recovery boots but there is many errors probably due to lack of multidisabler and I think I did something wrong with the partition mounts (/etc/fstab) but I don't know why (maybe I have to convert vendor's EROFS to F2FS RW but I have no clues).
If you have no data to loose and you want to test it : https://github.com/Nitorac/android_device_samsung_a54x/tree/main/manual_builds/b1f7b7b
I will try to fix the errors but since my A54 5G is my main phone, I have to make backups everytime I dev on it x')
