Alright i have been keeping an eye out on a few things and came across BootManager which is a newer app that allows you to easily flash between several roms! Which of course is awesome if you want to try new ones out without reflashing as often. Unfortunately im am not quite as wise in the Android scene yet as i like, new to it with my Acer Iconia as i am, BUT i have been corresponding with the developers for BootManager and they have given me a link so we can submit the Acer Iconia to be added to the devices that can use Bootmanager!
I just don't know how to give them the variables they need!
Could someone that does know how to get the variables needed, (through adb shell or whatever) kindly submit it to them? Here is the link they gave me for submitting new devices, if you do do this, please post it here, so they don't get a bunch of repeat submissions on it, also, so i can keep an eye on the app and get it when they update it accordingly! Thanks very much!
Edit: I can't post links yet, cause i have not posted often enough. Please send me a message and i can give you the link that way! Or just close the space below and use it.
init2winitapps. com/submit_device.html
I'll do it in the morning.
Make damn sure they know they have to run "itsmagic" before/after ANY flash operation (I can never remember which, that's CWM's job!)
I did it too and i sent also a mail to the developers about itsmagic script!
good luck
If you read the information about this program.how it works and the phones that it supports will tell you it will most likely work on our device.THEY SAY WORKS ON PHONES ONLY.and only those WITHOUT LOCKED OR SECURE BOOTLOADERS
But you never know. They might put the efforts to write a new bootloader for this device.the program works by moving the bootloader.well no fifteenth then any other boot manager.
if im wrong and they make it works. I would buy it first.
Goddess erica.
This was posted a while ago and it doesn't appear that the a500 has been added to the supported device list. Has anyone been successful in getting this to work? I want to try it but I'm not sure what issues I might run into if it doesn't work. I need to make sure a Nandroid restore can fix whatever issues might be caused before to try it.
IF i remember right it says on there site this can ONLY WORK WITH UNLOCKED and not encrypted BOOT LOADER DEVICES. I TO Talked to the dev way way long ago..as for this to work they change the boot target in the boot loader to look at there software . then it will boot from there..
kinda like grub to a normal pc.. with the bios being the primary boot . If this makes any sense..
so i think it cant happen.. in the linux thread in our dev area .. someone in the first few pages it talkes about this very app and the flashing the bootloader out.. Dont think they ever figurerd a way around the security..
sorry simple answer is ABSOLUTELY NO WILL NOT WORK
THANKS ACER
I'm confused. My a500 doesn't have a locked boot loader. Thats the reason I got it. I have Thor's recovery loaded on it and I have been able to flash Roms without issue. To boot into recovery I just hold down the volume button and boot the device. I can load custom kernels or pretty much anything else I want. Am I misunderstanding what an unlocked bootloader is?
I had a Razr previously which had a locked bootloader and the only way to flash was to use a bootstrap because it had a locked bootloader. I had loads of problems with it which is why I swapped it out for the Galaxy Nexus when it came out. Both my a500 and Gnex are flashing like champs.
Where there later version of the a500 that had a locked boot loader? I don't think mine does.
trevoryour said:
I'm confused. My a500 doesn't have a locked boot loader. Thats the reason I got it. I have Thor's recovery loaded on it and I have been able to flash Roms without issue. To boot into recovery I just hold down the volume button and boot the device. I can load custom kernels or pretty much anything else I want. Am I misunderstanding what an unlocked bootloader is?
I had a Razr previously which had a locked bootloader and the only way to flash was to use a bootstrap because it had a locked bootloader. I had loads of problems with it which is why I swapped it out for the Galaxy Nexus when it came out. Both my a500 and Gnex are flashing like champs.
Where there later version of the a500 that had a locked boot loader? I don't think mine does.
Click to expand...
Click to collapse
Not locked, but encrypted, we use a magic script called itsmagic to bypass the encryption.
daveid said:
Not locked, but encrypted, we use a magic script called itsmagic to bypass the encryption.
Click to expand...
Click to collapse
Ah. I always wondered what itsmagic did. I get it now. Damn. Is there currently any tablets out there that do not have encrypted or locked boot loaders?
Not any good ones.. welcome to the new communist Tech generation...
they want our devices to be disposable.
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
metpolds said:
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
Click to expand...
Click to collapse
Its not random, and if you look closer its a bootmenu. you can get past it marginally quicker by just tapping power button or use it to boot to recovery, fastboot/bootloader, etc.
And you cannot remove it.
You can go back to b20...
@nujackk and @lafester .. Thanks both of you for your comments. @nujackk I accept that the screen is a way of booting into fastboot mode, I just never used it, before I installed TWRP I always used MiFav Recovery to boot into fastboot. I am presuming that the screen is an integral part of the boot image and I shall continue to try and hunt it down.
@lafester as always lol your comment.
If either of you are interested I am just going to set up a new thread in "Themes Apps and Mods" where I shall post 3 flashable zip boot animations and hopefully in the coming days I will add to them.
metpolds said:
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
Click to expand...
Click to collapse
The screen is part of the bootloader image. I strongly advise you to just live with it since if you screw up the bootloader you're bricked.
Might I suggest you start by looking around in the bootloader unlock zip. Might give you some idea where it is or if it can be removed.
Also look at older list mentioning it, I remember seeing mention of other phones it's been used on, maybe someone has more info in one of those forums.
And I will look for those boot animations. If I can suggest a superman or superAndy would be nice
Good Hunting
metpolds said:
@nujackk and @lafester .. Thanks both of you for your comments. @nujackk I accept that the screen is a way of booting into fastboot mode, I just never used it, before I installed TWRP I always used MiFav Recovery to boot into fastboot. I am presuming that the screen is an integral part of the boot image and I shall continue to try and hunt it down.
@lafester as always lol your comment.
If either of you are interested I am just going to set up a new thread in "Themes Apps and Mods" where I shall post 3 flashable zip boot animations and hopefully in the coming days I will add to them.
Click to expand...
Click to collapse
I know what you are talking about - on older motorola phones we did away with it - it was just a stored image in those phones. Seeing as how here it is a fully functional menu I would bet any attempt to remove or replace it would most definitely brick the phone. I gave up on it a long time ago.
@lafester .. @nujackk .. @bkores .. @tabletalker7 .. Thanks guys for all your comments - I guess my next step eventually, there is no great hurry for this, is to make certain I have a couple of good backups before messing around with disassembling the bootloader and boot image. If I ever get anywhere with this I will let you guys know.
@nujackk I note your comments re the animations. I'm about to add another Andy animation to the thread but have searched in the past for usable Superman material without much success, however I will see what I can find.
Yeah I haven't seen many that were very good either, but keeping hope alive :fingers-crossed:
***UPDATE***
Thanks to reply, I have now successfully done everything I set out to do, and created follow-up guide!
You can find it HERE
Original Post below:
Hello Everyone!
I'd like to start off saying I used to have a Nexus 4, with TWRP and Lollipop-based CyanogenMod. I was able to install this all by myself, and keep both TWRP and the ROM updated. I also flashed custom radio to unlock the LTE capability on that phone. My tool of choice to help customize the phone was Nexus Root toolkit.
I was able to follow guides posted long ago on these forums, to do what I wanted with the Nexus 4 back in 2013/2014, but it seems I'm not so capable these days. I've hit such a roadblock with lack of root and constant stutters/slowdowns with everyday use on my current device, the Axon 7, that I must get away from the stock software. I heard it was not so easy with other devices, and while a few devs have posted wonderful guides for users, it's just not enough for a true beginner like me. From skimming guides posted, it seems like devs already expect you to have installed custom recovery, or unlocked bootloader. Then when I try to do these things, so I can move onto custom ROM, it seems the guides are out of date or just not step-by-step enough for me to use, and I don't want to take a risk and brick my device trying things that I'm not sure about. I'm a power user through and through, but not so up-to-date or knowledgeable enough to be able to follow the guides already on the forums. Consider me 1 out of 5 on tech level for Android software.
Here's the model/software already on my device: Stock everything, from bootloader and recovery, to ROM.
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
will my ROM of choice have Daydream VR support? if not what would be needed?
this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through how to use it once installed to help me unlock bootloader/root on another device, Zenphone Zoom if anyone is interested.
PLEASE, don't link me to other guides for any part of this process, if the steps are thorough and relevant, please copy here, of course with all due credit given to original poster.
Feel free to let me know if more info about my knowledge level or device is needed to help you work on my request.
Thanks for reading, here's to several years more of everyone enjoying this wonderful device!
ok there is three real steps, but it can be aheadache, mainly because you didn't unlock before going to nougat.
Step 1. Downgrade to B29 Marshmallow - go here https://www.zteusa.com/axon-7/ and on the support tab in software updates is a full B29 software package. Download it, unzip it once, then put the update.zip file on your SD card.
- on the phone, in developers options, turn on OEM unlocking (it is needed to flash from sd card)
- boot phone to recovery, choose update from sd card, pick the update.zip from the sdcard, the phone will flash the B29 software. It is a bit slow, let it do what it needs to do.
Step 2. Unlock phone and install TWRP - go here https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 download the miflash program, fastboot unlock program, and twrp for B29.
- instructions are all there, just do what it says.
Step 3, Install LineageOS - https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679 very straight forward. Don't forget to install first the bootloader, then the rom, then gapps.
What makes this so hard is not being easily able to unlock in nougat. Most of us here unlocked way before marshmallow
No need to downgrade to b29.
lafester said:
No need to downgrade to b29.
Click to expand...
Click to collapse
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
gpz1100 said:
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
Click to expand...
Click to collapse
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Help needed
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
kaiso said:
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
Click to expand...
Click to collapse
Did you downgrade to Marshmallow B29 first or skip this step?
[email protected] said:
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
Click to expand...
Click to collapse
I'm praying that someone will compile the information spread about into 3 guides that are model specific so people like us won't rack our heads trying to figure out what on earth to do.
[email protected] said:
Hello Everyone!
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
1with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
2will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
3will my ROM of choice have Daydream VR support? if not what would be needed?
4this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
5NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through
Click to expand...
Click to collapse
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
nolimit78 said:
I'll keep on saying this as much as I need to, I get where you're coming from. There's a lot of data about the correct way of doing things. Best thing to do is read and search. When I got my phone B29 was the new hotness and there was a bunch of older data floating around that I had to sift through. But I did it, I sifted and found my own way and combined two different methods to get my phone rooted and flashed with LOS. Honestly, the trial and error, the searching, the sifting is totally worthwhile because while this device is /DIFFERENT/ compared to methods for HTC and Samsung products, it's not harder. It's better to get yourself properly antiquated to the device you plan on flashing/hacking/rooting because there is /always/ a chance for bricking. Then another thread will be created asking for help to unbrick. Take the time, read now, read everything, understand your device, then push forward.
Click to expand...
Click to collapse
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
nolimit78 said:
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
Click to expand...
Click to collapse
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
KyJelly69 said:
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
Click to expand...
Click to collapse
Yup.
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
[email protected] said:
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Click to expand...
Click to collapse
Thank you for the guide, but I managed to get everything done without having to downagrade from Nougat. I was having issues with my Windows variant recognizing my phone after drivers were installed so I used Linux Mint 18.1 and everything went smooth as a whistle. I think the mods should pin your thread post.
I followed the rootjunkie YouTube videos, worked perfectly and the files were all available.
Sent from my ZTE A2017U using Tapatalk
I have rooted countless phones accross all different manufacturers but never found one as stupid to root as this phone!
There isn't an up to date thread about rooting the phone so I thought I'd share how I did it and got through various things that were not supposed to happen but did!
Firstly, unlocking the Bootloader - as Huwai don't provide a code anymore, I went down the https://www.dc-unlocker.com/ route. It is cheap at £4 and they take PayPal. The unlock code video is out of date which didn't help and I presse3d the wrong button first and got a unlock network code by mistake, so had to pay another £4 to do it again. I used this tool (minimal adb) from this thread (https://forum.xda-developers.com/showthread.php?t=2317790) to put the code in the phone but noticed that my phone wouldn't keep the USB Debugging active and had to slide it on each time I connected to the computer (even had to revoke the computer at one point and reconnect).
From an unlocked bootloader the biggest problem I had was finding a way to put TWRP on the phone. All the threads I could see contained the wrong code to flash and so it always failed. However Dru79 showed the correct form which was to connect in fastboot then use minimal adb (on windows 10, open from the start menu, not left shict right click and 'open window here') and use " fastboot flash recovery_ramdisk TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img " - the correct TWRP is here (https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959)
HOWEVER - my phone would not keep TWRP and more often (over 75% of the time) would boot to stock recovery, SO after I flashed the TWRP I typed in "fastboot reboot" and as I pressed ENTER, I took the power cord out from the phone and used the volume UP and the Power key to get into TWRP. I don't know why my phone wouldn't keep TWRP but it didn't.
Getting root through SuperSU was IMPOSSIBLE no matter how I tried, eventually I downloaded Magisk from (https://www.xda-developers.com/how-to-install-magisk/) and flashed it through TWRP.
Once rooted, I downloaded the PixyOS from https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-pixysos-huawei-hi6250-t3852152 and flashed it...perfect!
Hope this helps someone.
The funny thing is, I actually wanted to post a thread about it in General Section as I had the same frustration as you whole trying to root and install custom ROM on this phone (I've done countless Root's, flashes, unlocking before on couple of phones) and just couldn't find a thread that explains this properly.
Anyway since you already done this, this should be moved to General Section so people can see this properly.
I've flashed Pixy's OS on my phone about 4 weeks ago and just one thing you didn't mention is that if you're on 7.1 nougat then you need to upgrade to Oreo and then install TWRP (I found that out when I tried getting it on nougat and then got errors while flashing and realised the TWRP was developed to work on Oreo). Just get a stock image of Oreo and flash it, the link for it it's somewhere around in the forum, I think it's some kind of Russian website but works well.
Anyway great job, if we can just ask Mod to move this to General section so that this guide can aid new users in rooting their phones properly and efficiently so that they can minimize their changes of encountering errors (as me and OP did).
proadi96 said:
The funny thing is, I actually wanted to post a thread about it in General Section as I had the same frustration as you whole trying to root and install custom ROM on this phone (I've done countless Root's, flashes, unlocking before on couple of phones) and just couldn't find a thread that explains this properly.
Anyway since you already done this, this should be moved to General Section so people can see this properly.
I've flashed Pixy's OS on my phone about 4 weeks ago and just one thing you didn't mention is that if you're on 7.1 nougat then you need to upgrade to Oreo and then install TWRP (I found that out when I tried getting it on nougat and then got errors while flashing and realised the TWRP was developed to work on Oreo). Just get a stock image of Oreo and flash it, the link for it it's somewhere around in the forum, I think it's some kind of Russian website but works well.
Anyway great job, if we can just ask Mod to move this to General section so that this guide can aid new users in rooting their phones properly and efficiently so that they can minimize their changes of encountering errors (as me and OP did).
Click to expand...
Click to collapse
I have asked
Hello there,
Yesterday, I successfully rooted my new Samsung Galaxy S10+ (Android 11) using Magisk and Odin. Before, I used a rooted S8+. During the process, I noted that there were some significant changes which complicated the process of rooting for the S10+, one of them being that you need to press specific buttons and connect the phone via it's port for Magisk to actually boot. Naturally, I found that quiet annoying to always do and looked for a workaround. I did some reading and if I understand correctly, the reason why we must use this workaround is because the S10+ lacks a writable ramdisk part, which is why Magisk is installed in the "recovery" part. Can someone confirm this to me? And with all that being said, I still have some lingering question which I hope some kind soul could provide me the answer to?
Will there every be a way to boot Magisk directly or what would need to happen in order for it to work?
What should I avoid doing to not brick my device? Just the most important things like "Don't try to wipe you data when" etc.
Is there a way to disable the warning notification (the non-original software) during boot?
Should I be concerned because of vaultkeeper?
Should there already be a thread or answer for some of my questions which I overlooked during my search, I would appreciate if you could link them!
With kind regards,
DasMalzbier
Edit: Somehow, I got the achievment "thread poster Lv.3 [You created 100 threads!]" just from this? lol
Yes, the ramdisk is in the recovery.img of your device. There's an easy way to boot with magisk, power+bixby+Vol ↑.
The warning you see is controlled by the bootloader. Once a device is unlocked it will always show that, and there's no way to get rid of it. It used to be controlled by the logo partition, but that changed with Android 9+ for most oems. So unfortunately you're stuck with it. For further issues or questions about your device, please post in the appropriate forms. The S10+ forums can be found here. https://forum.xda-developers.com/c/samsung-galaxy-s10.8693/
I don't blame you for posting here though. The S10+ forums aren't easy to find. But now you know for the future.
Thanks for the quick response and answers
I didn't notice that I posted my inquiry in the wrong thread. Sorry about that, I'll move this thread now.