yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A21s Guides, News, & Discussion] LonelyCracker:
Dear Wer99,

I Successfully Made A Non-Rooted GSI By Following Your [Tutorial / Guide],

I'm Wondering How Could I Add SuperSU & Root Permission In It

GSI : [CherishOS, AOSP10, AOSP11]
[Samsung Galaxy A21s Guides, News, & Discussion] David112+:
I tried all of this and I even went as far as trying to literally change the filesystem UUID and the filesystem of system.img as well, I detected some issues when booting a GSI and it's that the filesystem and the filesystem UUID's had to match (filesystem had to be EXT2 for some reason), and after I did all of that, I flashed the super.img to my phone but after a few seconds of it trying to boot (10 seconds after it's past the unlocked bootloader screen) it just reboots and kicks me to fastboot mode, a friend of mine told me that if it booted to fastboot it meant that the bootloader was able to pass instructions to the OS but failed, hence why it kicked me to fastboot, and after that I tried with different GSIs and neither of them worked sadly.

Also in the attributes I'd recommend changing "readonly" to "none" so that the partitions are Read/Write from super.img, after flashing super.img, just edit the fstab file (located in "/etc/fstab" for recovery) and replace "ro" in the mount points with "rw" so that you can read and write data to them, the point of this is to make the partitions read and write so that you can edit them and install anything you'd like, and that's exactly the reason I did it.

After some time we got a modded magisk apk that does work and doesn't have the legacy device detection issue that it had before, due to the phone using dynamic partitions and using a ramdisk, Magisk would detect the device as legacy and it would use "SAR_init", something that the device doesn't needs and because the boot process fails, it reboots.

Also, before I realized that you could make the partitions inside super.img read/write, I would usually use readonly and it wouldn't work either, I'd appreciate if you could help me with this.
[Samsung Galaxy A21s Guides, News, & Discussion] David112+:
Also, Just so you know, the recovery that we have is OrangeFox R11 which is currently an alpha build, thanks to magisk I was able to use the tool "dd" in termux to flash the recovery.img to /dev/block/by-name/recovery (aka the recovery partition) and this helped me bypass DL mode which is even worse now that I upgraded to U5 (I regret it and I tried downgrading from recovery instead of DL mode but the linux kernel itself protects the mmcblk0boot0 partition which is supposed to be the partition where the "BL" is located, and I tried flashing the sboot.bin file to that partition and it didn't work due to it being protected

Anyways back to the original topic, I don't know how but after flashing OrangeFox R11 with dd in android (I used su with magisk of course because), OrangeFox managed to boot with stock vbmeta and this build was supposedly built with A10's firmware in mind, not A11's firmware, so I have some hopes that flashing super.img from recovery might work if given the right vendor and firmware, I even flashed a vbmeta that was made for U3 from OrangeFox and it booted without any issues, oddly enough OneUI booted with that U3 vbmeta.img
[Samsung Galaxy A21s Guides, News, & Discussion] David112+:
You don't need SuperSU anymore, There's already a fixed magisk for it, Here's the links:

https://xdaforums.com/t/sharing-how-to-root-a21s-stock-rom-with-magisk.4272095/

https://xdaforums.com/t/root-modified-magisk-for-galaxy-a21s-r.4271537/
[Samsung Galaxy A21s Guides, News, & Discussion] LonelyCracker:
Yeah I Know But I'm Just Interested In Making A Prerooted GSI
[Samsung Galaxy A21s Guides, News, & Discussion] David112+:
What's the point of making a prerooted GSI with an outdated root method?

You can't even install modules with SuperSU
[Samsung Galaxy A21s Guides, News, & Discussion] LonelyCracker:
To David112+ :

In My Opinion, Prerooted GSI Is Way Better.

You Could See The Comparison I Made Here.

Also Making One GSI Could Gain Me Lots Of Experience.

So I Couldn't Think Of The Reason Why Not

Magisk Patched Stock [Firmware / ROM] Also Have It Own Problem,

Which You Could Find Here.
[Samsung Galaxy A21s Guides, News, & Discussion] David112+:
I don't think you've realized or checked the group of the phone but a load of people have already rooted their ROMs with Magisk and so far they have no problems, and still, everyone agrees that installing modules somewhere from the internet is the responsibility of the end user.

And I'm pretty sure that everyone agrees that magisk is the best root method, and even if you wipe data, you can just reinstall the Magisk apk to get the root prompt and finish setting it up, or better yet. use the systemizer module to systemize the magisk apk so that it's installed in system instead of data.

Making a prerooted GSI is just a waste of time, I'd rather just make normal GSI that's flashable on the phone and just install Magisk or systemize the Magisk APK.

I do agree that making a GSI flashable for the phone makes you gain a lot of experience but you're wasting your time into something that barely anyone is going to use, due to the fact that it has SuperSU which is old and outdated and most people prefer Magisk anyways because it's updated and not only that but you can pretty much install anything you'd like with the modules.
[Samsung Galaxy A21s Guides, News, & Discussion] LonelyCracker:
To David112+ :

Sorry To Disagree With You, I Was Trying To Acheive A Goal There .

My Goal Was To Get ADB (Android Debug Bridge) With "adb root" Working On Magisk Patched Stock [Firmware / ROM]. After Many Research & Attempt To Acheive That, I Gave Up... I Gained Some Knowledge There Too. I Know That Stock Rom Are For Production Purpose & I Can't Gain Root Access Using ADB (Android Debug Bridge).

Hopefully I Could Get Help Somewhere.

But Fun Fact Is...

I Water-Damaged My Phone

Question :

1.) Is It Possible To Make A Non Rooted GSI & Patch It With Magisk ? How ?
[Samsung Galaxy A21s Guides, News, & Discussion] David112+:
Custom ROMs should work with ADB root normally

2. To install Magisk just use the links that I shared in this post (https://xdaforums.com/t/how-to-make-pre-rooted-gsis-for-samsung-a21s.4269227/post-84975373)
[Samsung Galaxy A21s Guides, News, & Discussion] thatha:
After upgrading to U5, I can't install these GSIs anymore. It bootloop all the times
[Samsung Galaxy A21s Guides, News, & Discussion] LonelyCracker:
To David112+ :

But Is Not Possible To Use ADB (Android Debug Bridge) On Magisk Patched Stock [Firmware / ROM]. What I Was Saying Is To Use "adb root" On Magisk Patched Stock [Firmware / ROM]

I'm Only Able To Use The Command "adb root" In Custom GSI Built By Wer99.

Not Every Custom Build GSI Are Prerooted.

Maybe You're Right Magisk Is Better Than Old Little SuperSU. But I Need "adb root" To Work With It
[Samsung Galaxy A21s Guides, News, & Discussion] David112+:
If you have magisk with stock ROM, good news for you, I'll be working a guide in how to get a GSI installed as a magisk module, I tested this with ShapeShiftOS and I got as far as the boot animation of ShapeShiftOS, Once I was booted I checked ADB and sdcard was encrpyted and that's why it wasn't able to start correctly, it was just stuck in the google logo with a loading bar, I'm gonna try decrypting data, formatting and then installing the module

If this does work then I'll be releasing a guide in how to get a GSI of your preference working as a magisk module

Explanation: Thanks to Magisk's Magic Mount feature, I'm able to systemlessly swap the assets of OneUI with a Custom ROM's of my choosing, such as ShapeShiftOS

Edit: This idea is discarded, Because of the userdata partition being encrypted I can't use ShapeShiftOS, and even after decrypting I can't use it because OneUI gets stuck in "Starting android" when using the boot image with patched fstab and magisk
[Samsung Galaxy A21s Guides, News, & Discussion] Oroki:
And if I download gsi android 11 through mediafire, will I have to do all this procedure? or just flash on odin? A21S ANDROID 11.
[Samsung Galaxy A21s Guides, News, & Discussion] LonelyCracker:
To Oroki:

These GSI Is Ready To Be Flashed.
[Samsung Galaxy A21s Guides, News, & Discussion] Oroki:
but will i have to do topic 2 and 3?
[Samsung Galaxy A21s Guides, News, & Discussion] LonelyCracker:
To Oroki :

Please Explain What Do You Mean By Topic 2 & 3
[Samsung Galaxy A21s Guides, News, & Discussion] Oroki:
2. Converta stock_super.img em raw_super.img: e​

3. Extrato raw_super.img:​
[Samsung Galaxy A21s Guides, News, & Discussion] LonelyCracker:
To Oroki :

Those Step You Provide Aren't Necessary Anymore

It's Patched Which Mean You Don't Have To Do Anything To It

Sorry For Late Reply
[OnePlus 9] iSkyJIE:
Read the full page of OnePlus 9 thread! No firmware and boot files were found😔😔😔
[OnePlus 9] TheKnux:
What're you on about?
[OnePlus 9] iSkyJIE:
Did not find the T-Mobile version of OnePlus 9 firmware or boot.img! Need boot files to root this phone！
[OnePlus 9] TheKnux:
You pull the boot.img yourself

There's ways to pull the boot.img using adb/fastboot commands once your bootloader is unlocked. Then all you have to do is patch it using Magisk and flash it in fastboot.
[OnePlus 9] iSkyJIE:
Thank you for your reply！

My bootloader has been unlocked! But I don't know how to extract it to boot.img
[OnePlus 9] Lomeli12:
You don't specifically need the T-Mobile boot.img to root your phone. Get the boot.img from this post: https://xdaforums.com/t/root-oneplus-9.4253651/page-4#post-84874313

Install the Magisk App on your phone

Reboot into fastboot

fastboot boot boot11244AAmagisk.img

Once your phone boots, open the Magisk app

Ignore any message about it needing to setup

Install Magisk with a direct install

Reboot and now your phone should be rooted

I've tested this on my one T-Mobile OnePlus 9 and it works perfectly, even passing SafetyNet
[OnePlus 9] iSkyJIE:
Thank you,

I'll try extracting the 11.2.2.2AA international version of boot, which I'm currently version 11.2.2.2
[OnePlus 9] inspron:
If anyone has the stock oneplus9

T-mobile 11.2.2.2 boot.img please kindly share.​

​

In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img​
[OnePlus 9] TheKnux:
MagiskHide enabled?
[OnePlus 9] inspron:
Yes.
[OnePlus 9] TheKnux:
Not sure then. I'm at work right now so I'm kinda tied up for helping you out until I get home.
[OnePlus 9] inspron:
Thank you. I am hopping that the problem will be fixed when I have access to a stock boot.img from T-Mobile oneplus9.
[OnePlus 9] Jg1234:
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).

Hope it helps you out.

boot.img

drive.google.com
[OnePlus 9] Jg1234:
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
[OnePlus 9] inspron:
Wow! Thank you. Failed Magisk but It does pass this https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest
[OnePlus 9] inspron:
Thank you stranger!!!
[OnePlus 9] inspron:
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
[OnePlus 9] Jg1234:
I'm not to sure on that one.. I came from the 6t t-mobile version and it had the local upgrade option.
[OnePlus 9] nujackk:
No, T-mobile doesn't allow update if bootloader unlocked. has nothing to do with safetynet. If you look in system after unlocking your bootloader and rebooting you will see system update no longer avail. :(
[OnePlus 9] iSkyJIE:
11.2.2.2 AA International’s BOOT is only 96MB, and the T-MOBILE 11.2.2.2 BOOT you provide is 192MB, maybe this is the difference.
[OnePlus 9] Jg1234:
Yes it will!! You have to restore stock boot.img through magisk. OTA update will download, install ,. DO NOT REBOOT!! Go to magisk install to Inactive slot (after ota)

I just did this moments ago with 11.2.3.3
[OnePlus 9] TheKnux:
SafetyNet doesn't pass with stable I don't think. You have to use Canary and enable MagiskHide to get it to pass.
[MTCD  Android Head Units Q&A] Antimyv76:
Does anyone know where I can download the original software for my headunit? MCU version: MTCE_LM2_V3.63a_1 Or can it be replaced with another MCU?
[MTCD  Android Head Units Q&A] lagos911:
here at the link below or contact with your seller for a newer version

MTCD

View and download from Yandex Disk

disk.yandex.com
[MTCD  Android Head Units Q&A] Antimyv76:
the seller refuses to send me even the current one. what changes do they contain that you have shown?
[MTCD  Android Head Units Q&A] marchnz:
What issues do you experience with the current MCU? Is it the MCU or is it Android you are wanting to change?
[MTCD  Android Head Units Q&A] Antimyv76:
The problem is that the headunit only uses gps + glonass satellites. I bought a high precision GNSS antenna instead of the antenna next to the head unit. This antenna can be used with all types of satellite systems. gps + glonass + beidou + galileo. It may be necessary to change the MCU to make all of them usable. My smartphone sees and uses all satellite systems.
[MTCD  Android Head Units Q&A] marchnz:
Not MCU, Android. MCU has zero interaction with GPS

I doubt this will be solved as isn't supported by OS
[MTCD  Android Head Units Q&A] Antimyv76:
is there no modification that would allow the radio to see both beidou and galileo satellites?
[Upgrading, Modifying and Unlocking] sdancer:
I am new to the android programming world. I own an iQR70 device from MLS that is using -if I read well- the kiosk mode for its own application called MAIC (something like Amazon's Alexa virtual assistant).

View attachment 5293473

View attachment 5293475

The real pain with this device is that the application is buggy does not get any updates and overall does not work properly.

So, my questions are, a) is there any way to disable the kiosk mode and work with it as a normal tablet? or desperately b) Can I install a compatible firmware? I don't care for the data inside.
[Upgrading, Modifying and Unlocking] Mobilelearner:
You can check for update. Look for android version of tablet. You can check their site for any upgrade of software.

You can flash other firmware. Find compatible firmware as per your model.

You can disable apps same as you do on android mobile.
[Upgrading, Modifying and Unlocking] sdancer:
My tablet currently Is dead boot and I am trying to find the test points. Anyway, I have no access to the android os to disable apps. The virtual assistant is the only app I can use, all others are forbidden.
[Upgrading, Modifying and Unlocking] zeetotheuno:
Hi sdancer,

I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.

Did you manage to get it back on? And does your PC recognize your device?
[Upgrading, Modifying and Unlocking] sdancer:
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
[Upgrading, Modifying and Unlocking] zeetotheuno:
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?

I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.

If you try it and find out, would you be so kind to share?

By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)

Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)

But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
[Upgrading, Modifying and Unlocking] sdancer:
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.

My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.

So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.

PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
[Upgrading, Modifying and Unlocking] zeetotheuno:
Well, basically just try this, (for the one that still works):

- You just let it boot normally until you see the MAIC woman on the main screen.

- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.

- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times

- Now you'll see a message pop up, which asks you for a password

And this is where I got stuck for a long time. And usually you can't get past this point I guess.

But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.

Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.

What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).

That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.

Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
[Upgrading, Modifying and Unlocking] sdancer:
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.

This is all you need in your case, don't bother with the hardware reset.
[Upgrading, Modifying and Unlocking] zeetotheuno:
That's awesome! Thank you in advance.

Yeah, I guess the hardware reset really takes some time and a lot of trial and error.

But if you manage to do it, let me know, I'm just curious in general, if that's possible with this device.
[Upgrading, Modifying and Unlocking] sdancer:
View attachment 5311585

View attachment 5311587

View attachment 5311589

View attachment 5311591

To Flash your device,

1) Install the drivers

2) Press Download from SP Flash Tool

2) Connect USB

3) Connect the power outlet from your device (in this case) or connect the battery

****WARNING: DONT FORMAT THE PRELOAD or you will get a DEAD BOOT device, use ONLY DOWNLOAD and not download+format

AutoInstall

=================

MediaTek_Preloader_USB_VCOM_drivers.exe

File on MEGA

mega.nz

Manual Install

=================

MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip

File on MEGA

mega.nz

MediaTek_Preloader_USB_VCOM_Drivers.zip

File on MEGA

mega.nz
[Upgrading, Modifying and Unlocking] zeetotheuno:
Hey @sdancer, thank you for the drivers. But I must do something wrong, because it's still not detected. It's not showing in my device manager and nothing happens in SP Flashtool.

I tried the automatic install and the manual install, but still nothing :/

Could you maybe explain how exactly you installed them? Maybe I'm making a mistake there.
[Upgrading, Modifying and Unlocking] sdancer:
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)

2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4

3) Follow the instructions I recorded for you at
[Upgrading, Modifying and Unlocking] zeetotheuno:
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.

Really tough thing, this MAIC, haha.
[Upgrading, Modifying and Unlocking] sdancer:
Hi

I suppose that this is a driver's problem, you should try to fix it someway.
[Upgrading, Modifying and Unlocking] Marko121212:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.

I'm seeking for help for months now, so, if anyone can help me, I will be really grateful :)

Thank you, Marko
[Upgrading, Modifying and Unlocking] paulos2951:
Any idea, Any fix?
[Upgrading, Modifying and Unlocking] Marko121212:
I have no idea bro :/ Hoping that someone will help me
[Upgrading, Modifying and Unlocking] Jim-Kyritsis:
I have the same problem with you

If you find a solution please send me a message !
[Upgrading, Modifying and Unlocking] Marko121212:
Hi friend! Are you Greek? Is there a way to contact MLS in Greece?
[Upgrading, Modifying and Unlocking] Jim-Kyritsis:
Yes i am from Greece

No they have a website but you speak to a robot not at a person

That's why i am searching the problem by my self

If you call this number 210 9902570 they will say that the product is so old that you can't fix it!
[Upgrading, Modifying and Unlocking] Jim-Kyritsis:
Now i have a biger problem .

I tried to format it again and now its stuck on the downloading screen!

I don't know what to do with this assistand 😡
[Upgrading, Modifying and Unlocking] Marko121212:
So, basically, we can just throw it in the trash :poop: