So, I got an A50, and I'm really happy that I did. However, switching from a phone that had TWRP and Magisk is something I am not finding easy, even if the phone is much faster than my old one. So, of course, after thoroughly reading my warranty, which had no mention of not covering software device damage, I decided to to go ahead and try to flash TWRP and then install Magisk. I went ahead and easily figured out that my model is SM-A505FN (which would have been all that I needed for my old phone). Seeing that there were successful attempts at installing TWRP and Magisk on this model, I decided to try it out, but quickly found myself with a soft bricked phone, so off to finding a Stock ROM I went. After booting it up again I did more digging, but that yielded no result, however, I decided to try using Magisk manager to patch the AP file and then tried patching that. Sadly, no luck. I even went as far as trying a few of those programs that would root your phone from your PC, but that proved to be a waste of time as even that didn't work (which I suspected would happen, but whatever).
While fondling with the phone, I noticed something in the recovery. It wrote a50xx and then I realized that that must have been the reason for nothing working. And now we get to the title of this post. Has anybody been successful at rooting or flashing TWRP on an a50xx device, and, if so, would you be so kind as to elaborate on how you did it?
If not, I guess I should either wait, or look into trying to port TWRP to a50xx myself.
Edit: In case I do decide to port TWRP, any help or pointers are welcome.
Hello @BrainReader,
Same problem here! I tried rooting my device (sm-a505fn as well) by flashing the ap-file using magisk manager. I kept ending in a bootloop. I tried the latest version v20.x and even tried v19.3 which should work stable according to this thread: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271.
I hope this thread gets more attention and someone finds a solution for rooting the a50!
Kind regards,
Shademaster639
I have a rooted a505fn twrp is not working but rooting with magisk works fine. Every magisk version above 19.3 is giving problems. The latest magisk give very much reboots. What I did I first installed the newest software with Odin. Then install magisk 19.3 after that I set in magisk the update channel to get no further then 19.3.
That patch the AP file and reflash everything with the patched version.
It works without problems.
You must flash complete firmware stock
Then reflash complete firmware with mm agisk ap
If I am in a class of 1 in terms of rank stupidity please feel free to delete this post. :silly:I got sick of the updater nags. With a couple of previous Xiaomi phones I got away with finally saying yes to the OTA update which would inevitably fail after which the nags would stop for a good long while.
Not this time. I now have Miui 11 (which I did not want and which has a completely broken feedback function, btw) but lost root, magisk, and exposed.
I should also note that another Max 3 user posted here that permitting the OTA update bricked their device, so I guess things could be worse.
About to see if I can re root using the same method as before the update.
Sorry if I wasted anyone's time on the blindingly obvious.
Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.
brasscupcakes said:
Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.
Click to expand...
Click to collapse
Don't worry about anti-rollback unless you go back to rom that has no anti rollback. I go from miui 10 global to miuieu 11 P beta to miuieu 11 Q beta then back to miuieu 10 P stable. Now I settled on miuieu 11 P stable, yes miui 11 Q is very buggy. A few of my app don't work properly.
[Fix] Root on latest MIUI 11 build !
Just update Magisk Manager to 20.2 !
What's with a screen when charging, it keeps turnin on? Happens after MIUI 10 install...
Since the first version of Android Q, I could never do it Root, I can't make Magisk work, whatever I do.
I install it without problems, but when restarting it is not installed, I never have root.
Try 20.1 and 20.2, it still doesn't work.
I have a Mi Max 3 6/128
I installed the latest Miui 11 OTA update last night - taking a full Orangefox backup beforehand. After reboot, the phone was full of ads suddenly and it took me a while to figure out that root had been removed. I soon discovered that Orangefox had also been removed and replaced with a clunky-looking version of TWRP. I reflashed Orangefox and Magisk - coming back to recovery inbetween-times and it booted fine but the ads were still there so I tried to install Xposed via Magisk and that seems to have pretty much soft-bricked it. I can get into Orangefox where it said 'No Rom' which didn't seem like a good sign. I tried to re-flash the full backup I'd made with Organgefox yesterday (and this not really understanding Orange fox that well) but that hung at 'System image' - so I tried to flash without that and that succeeded but it's still totally bootlooping.
I'd very much appreciate some advice:
1. The Orangefox backup I made was with all the boxes ticked - i.e back up everything. I have the dim idea that trying to simply restore all of this won't work (it certainly doesn't seem to work). What parts of the full backup should I try to restore?
2. If I install the latest Global Miui 10 ROM - which is still Android 9 - using the Miui repair tool, will this brick the phone because of ARB? Or is it safe to do this?
3. Will dirty-flashing the latest Miui 11 rom via OrangeFox likely make something I can at least boot up and get some data (it turns out that 'SMS backup and restore' hasn't been working for weeks so I don't have a pile of work texts that I really wouldn't like to lose)?
4. Any other suggestion most gratefully received. Thanks in advance.
(Thinking about it, this thread is for the OTA breaking the MI Max 3, not my particular woes with restoring an Orange Fox backup - so, with apologies, I'll post in the Mi Max3/Orange Fox thread.)
PS: Flashing the OTA again fixed it, short term: no root is better than no phone.
Hello xda,
I've had the Pad 5 for a year now. Since I needed it to be multi-user capable, I originally installed a phh gsi on it, which has been working alright except for a few unwanted reboots from time to time.
Still, I believe it is more than time to update this thing, if only for security patches. Since I saw there's now a device specific custom rom with arrowos, I thought I was in luck.
However, I need to back all of the data up before doing so, if I don't want to get shout at by my children. I kind of understood that the best way to back this thing up was to first get root.
Since I had not done it originally, I set out to install the magisk app (v. 25.2), found the boot.img of my original firmware, patched it in the app, flashed it with fastboot and happily rebooted.
The happiness was short-lived, though, as the magisk app displayed a pop-up saying that it doesn't support magisk versions older than v22.0
What may I have done wrong to get that message ?
Thanks for your time and help !
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)
I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...
(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)
...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.
Thanks in advance for any help/guidance doing so.
Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol
XDA didn't like file upload so I put it on GDrive for you. Let me know when you've grabbed it so I can delete it
Nimueh said:
Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol
XDA didn't like the .img ending so I had to rename it to .zip - just remove that and you'll be good.
Click to expand...
Click to collapse
I've never done it that way myself. By just restoring images in magisk, I can do a "normal" update, from settings, and it will download just the update, in this case, about 700MB, then Install to inactive slot in Magisk and done.
This avoids me needing to find the full update to download. Probably not a big deal, but this has always worked fine in the past.
I guess i just installed Magisk incorrectly the last time I wiped, which is now causing me this issue.
I appreciate your suggestion, and perhaps that is the better way moving forward.
I didn't see your attachment, but as I'm typing this, i see you edited to say you renamed it, so I'll see if I see it now.
Thank you for your help.
Nimueh said:
Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol
XDA didn't like file upload so I put it on GDrive for you. Let me know when you've grabbed it so I can delete it
Click to expand...
Click to collapse
I just downloaded it, thank you again!
Note: I've never upgraded this device.
Uninstalling Magisk from the app restores the stock boot: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87931933
Primokorn said:
Note: I've never upgraded this device.
Uninstalling Magisk from the app restores the stock boot: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87931933
Click to expand...
Click to collapse
Thank you, but that is the issue. I don't seem to have the stock image on the device, so I can't "uninstall Magisk" to restore the stock image.
Once I make the time to deal with this, I believe the stock image Nimueh shared will let me fix this, but I don't have time to troubleshoot this if it doesn't go smoothly, so it needs to wait a bit longer.
JustinChase said:
Thank you, but that is the issue. I don't seem to have the stock image on the device, so I can't "uninstall Magisk" to restore the stock image.
Once I make the time to deal with this, I believe the stock image Nimueh shared will let me fix this, but I don't have time to troubleshoot this if it doesn't go smoothly, so it needs to wait a bit longer.
Click to expand...
Click to collapse
OK I thought Magisk handled the backup of the stock boot.
I'm not in hurry to upgrade lol
Primokorn said:
OK I thought Magisk handled the backup of the stock boot.
I'm not in hurry to upgrade lol
Click to expand...
Click to collapse
It normally does, but I apparently installed it 'abnormally' last time, so I didn't have/save the stock boot image.
I just need to research the best way to get the downloaded stock image onto my phone so that Magisk knows and can use it, without screwing something up, and having to wipe and reinstall everything (again).
I'm not in a huge hurry to upgrade either, but I do like to be on the latest security patches; especially considering the news with the Exynos chips' vulnerability to WiFi calling issues.
JustinChase said:
I'm not in a huge hurry to upgrade either, but I do like to be on the latest security patches; especially considering the news with the Exynos chips' vulnerability to WiFi calling issues.
Click to expand...
Click to collapse
Luckily that doesn't apply to our devices though - according to the articles I've seen it only affects these devices:
Samsung Galaxy S22, M33, M13, M12, A71, A53, A33, A21s, A13, A12 and A04 series.
Vivo S16, S15, S6, X70, X60 and X30 series.
The Pixel 6 and Pixel 7 series.
Any vehicles that use the Exynos Auto T5123 chipset.
Nimueh said:
Luckily that doesn't apply to our devices though - according to the articles I've seen it only affects these devices:
Samsung Galaxy S22, M33, M13, M12, A71, A53, A33, A21s, A13, A12 and A04 series.
Vivo S16, S15, S6, X70, X60 and X30 series.
The Pixel 6 and Pixel 7 series.
Any vehicles that use the Exynos Auto T5123 chipset.
Click to expand...
Click to collapse
I agree. I'm more concerned about the unpublished vulnerabilities that may exist, that we just don't know about yet.
I figure that if I keep my device updated with security patches, that's better than finding out the hard way I could have prevented an issue.
JustinChase said:
I agree. I'm more concerned about the unpublished vulnerabilities that may exist, that we just don't know about yet.
I figure that if I keep my device updated with security patches, that's better than finding out the hard way I could have prevented an issue.
Click to expand...
Click to collapse
I don't use my device much and mostly at home on my wifi, so I'm not overly worried. I'm still on the last OOS 11 version mysel, mostly because 1 mod I use only exists for OOS 11. I'm sure I'll update eventually but for now I'm ok with old security patches.
#priorities and all that
Upgrading from 11.0.9.1(Android 11) to Android 12 using HD1901_11_F.22 update from system upgrades bricks my phone. I live in India and decided to upgrade my phone to Android 12 just to find my phone bricked after rebooting(a white screen flash/blink followed by black screen) and reverted back to oos 11 and did the install again but same result. Is there any way I can install oos 12. P.S I am currently using a oos 11 based custom rom and I had replaced my phone screen with an unoriginal one(because I broke my original screen) if that makes a difference
Model:HD1901
Variant:India
Can somebody help me please
My best guess is that you need to be completely stock OOS11 to properly update to OOS12.
You say that your on a custom ROM that's Andriod 11 and you want a stock Andriod 12.
Therefore, I suggest that it's possible that you must be on stock Andriod 11 to update to stock Andriod 12.
I think that their is incompatibilities between the custom and the stock ROM causing the bootloop issue.
Which would mean the fill wipe of device and loss of all data I would assume. So save a back up what's needed.
So search for the MSM TOOL which will restore your device to it's wiped/stock state (might be only Andriod 11 at this point - not sure is MSM for Andriod 12 is available). Full update from 11 to 12 at that point should work. (I always utilize the full rom update - not the incremental update but not sure if that even matters).
Bottom line is that stock and custom ROMs irrespective of the Andriod base usually involve a complete device wipe and reset when switching from what little I know.
But, I believe I've been able to point you in the correct direction.
wugga3 said:
My best guess is that you need to be completely stock OOS11 to properly update to OOS12.
You say that your on a custom ROM that's Andriod 11 and you want a stock Andriod 12.
Therefore, I suggest that it's possible that you must be on stock Andriod 11 to update to stock Andriod 12.
I think that their is incompatibilities between the custom and the stock ROM causing the bootloop issue.
Which would mean the fill wipe of device and loss of all data I would assume. So save a back up what's needed.
So search for the MSM TOOL which will restore your device to it's wiped/stock state (might be only Andriod 11 at this point - not sure is MSM for Andriod 12 is available). Full update from 11 to 12 at that point should work. (I always utilize the full rom update - not the incremental update but not sure if that even matters).
Bottom line is that stock and custom ROMs irrespective of the Andriod base usually involve a complete device wipe and reset when switching from what little I know.
But, I believe I've been able to point you in the correct direction.
Click to expand...
Click to collapse
I was on stock oos 11 11.0.9.1 when I updated my phone through the oos system updates
Arnavgr said:
. P.S I am currently using a oos 11 based custom rom and I had replaced my phone screen with an unoriginal one(because I broke my original screen) if that makes a difference
Model:HD1901
Variant:India
Click to expand...
Click to collapse