yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] rINanDO:
Hi everyone,

I got a little progress here. I tried to make MindTheGapps flashable for Android 12.1. But that is WIP. During this investigation I build TWRP 3.6.1 on Android 9.0. But that only works when the recovery-partition is enlarged. That means that we need again a new PIT-file. So I combined everything to an updated clean install instruction in the Opening Post to make it easier to install from scratch coming from every ROM using ODIN. Be aware that your data-partition (that includes media-folder) will be erased using this CLEAN installation method.

Can you flash LOS 18.1/19.0 with afterwards this clean ODIN flash? Yes. That should not be a problem.

How to FULL clean flash LOS 19.1 and TWRP 3.6.1_9.0

Warning: This will erase your data-partition completely!

Download i9100-LOS 19.1 via ODIN.zip and unzip it on your Windows PC.

Start the Odin3 v3.07.exe in the ODIN3 v3.07-folder

Choose for PIT: i9100-LOS-19.1.pit

Choose for PDA: i9100-LOS-19.1_android-12.1.0_r2.tar

Make sure the following checkboxes are checked:

Auto Reboot (optional)

Re-Partition

PDA

Click Start!

Reboot your phone and LOS 19.1 will start. First start could take about a few minutes.

Note about new PIT-file: The recovery image of TWRP 3.6.1 exceeds the 8mb partition size of our PIT. That is why I introduced a new PIT-file. I also enlarged the System-partition (FACTORYFS) to 2GB. These are the partition changes (compared with stock) of PIT-file i9100-LOS-19.1.pit :

Partition name	Stock size	LOS 19.1 size
RECOVERY	8MB	32MB
CACHE	100MB	76MB
FACTORYFS	512MB	2048MB
DATAFS	2048MB	12792MB
UMS	11784MB	8MB
HIDDEN	512MB	8MB
[Galaxy S II Android Development] ale5000:
Great work!!!

Now I have a question, since I develop a flashable zip to install microG and I need to test it over multiple Android versions my question is:

With this new PIT and TWRP 3.6.1_9.0 is it possible to use Android 9/10/11/12.1 (all ROMs made by you) without changing recovery and partitions at every ROM?
[Galaxy S II Android Development] notnoelchannel:
If the PIT repartitions recovery to 32mb i can build OrangeFox for this device!! :D
[Galaxy S II Android Development] ale5000:
It would be nice so I can test my zips over it :)
[Galaxy S II Android Development] rINanDO:
I didn't test older roms, but it should work.
[Galaxy S II Android Development] notnoelchannel:
it didn't compile (TARGET_KERNEL_BINARIES error)

can someone help me?
[Galaxy S II Android Development] Steve2016:
Hi,

I tried it but it boots me directly back to Download mode, after being stuck on the S2 Boot Screen with the Yellow triangle
[Galaxy S II Android Development] ale5000:
The build of TWRP 3.6.1 of rINanDO probably contains many changes that aren't in official sources from https://twrp.me/

But I don't know for certain.
[Galaxy S II Android Development] Aussiewaterdragon:
Same for me, boots back to download mode after restart. If I boot twrp 3.6.1_9-0 cannot mount Data or Preload. It looks as if the repartitioning isn't working for Data.....just my guess.
[Galaxy S II Android Development] DevisG79:
I had to try it multiple times. Always bootloop after installing via Odin. Then I formatted data and did again the Odin Method. Now it works. About info shows LOS 19.1 build from 15.03.2022. Is that right?
[Galaxy S II Android Development] Aussiewaterdragon:
Well, what fun (not). After many attempts, formatting data, and re-download in case corrupted and different zip extractors got it up. BUT couldn't access sdcard0 the phone memory, couldn't download. sdcard1 ok and can install direct. Will try again today. All partitions mount in TWRP but sdcard0 shows empty.

Does anybody have any success? If so, share the magic.

P.S. what version of Magisk are successful installs running?

UPDATE

got access to sdcard0 (phone memory) using TWRP to copy a file from PC to phone sdcard0. It then after reboot started the phone as if 1st install after ROM install. Got Magisk 24.1 up and working. Again, does anybody else have experience in using later versions before I UPDATE?

Still haven't loaded any GAPPS anybody has had any success?
[Galaxy S II Android Development] notnoelchannel:
Use MindTheGapps
[Galaxy S II Android Development] Aussiewaterdragon:
Nobody talked to me so I scoured XDA and found a gapps that works. Playstore up and running. I used open_gapps-arm-12L-pico-20220311-UNOFFICIAL_MOD

I got from member ipdev here https://xdaforums.com/t/gapps-daily...all-android-versions-devices.3098071/page-363
[Galaxy S II Android Development] bersem:
already did but it seems you didnt saw it. look at page 7 ( post 129 ).

Regards !
[Galaxy S II Android Development] JPCastillo2000:
Is there any way to modify the fstab? I am trying to modify zRAMs disksize and mount options, but everytime I edit something, it goes back at how it was after a reboot.
[Galaxy S II Android Development] Aussiewaterdragon:
Is ir me or does anybody else have the following problems with Magisk 24.1

1. The modules are all turned off after reboot

2. Fox's Magisk Module Manager (tried all versions from 3 to the latest)

a. Does not show installed modules

b. Does get Magisk root but says can't access Magisk or root ( can still download and install)

c. because of b. it doesn't show updateable modules.

3. Magic Module Repo not working get an error unzipping downloaded modules so can't install.

4. In Magisk Modules some modules show a greyed-out update icon but are up to date.

Also, does anybody have problems turning on Bluetooth?

P.S. Don' say it's the phone as I have two old S2 and it's the same on both.
[Galaxy S II Android Development] itsAlphaFox:
On 19.0 + BitGApps I had problems with Bluetooth occasionally. I also had some issue with the camera.
[Galaxy S II Android Development] Aussiewaterdragon:
Got Bluetooth going, had to go through every setting related to Bluetooth including all settings in Developer Settings, but got there.
[Galaxy S II Android Development] Chicko24:
so have times the 19.1 Clean installed with

open_gapps-arm-12L-nano-20220311-UNOFFICIAL_MOD

everything works great for me

Bluetooth works

GPS works

finally everything works
[Galaxy S II Android Development] ran000:
Please, more detail: which build, according which installation instruction, which link to open_gapps-arm-12L-nano-20220311-UNOFFICIAL_MOD
[Galaxy S II Android Development] Chicko24:
here the Pico Gapps , install everything clean as described in the first thread

here the LINK for All Gapps.
[Galaxy S II Android Development] lee nomal:
Is there a possibility that the Memory Plus function will be introduced to make up for the lack of RAM?
[Galaxy S II Android Development] Chicko24:
if that were possible that would be really great
[Galaxy S II Android Development] Noboti:
That with:

1. Download i9100-LOS 19.1 via ODIN.zip and unzip it on your Windows PC.

2. Run the Odin3 v3.07.exe in the ODIN3 v3.07 folder

3. For PIT select: i9100-LOS-19.1.pit

4. ……………………………………………………….

didn't work for me (bootloop)

Got about Odin

i9100-LOS-16.0-Emulated-Storage.pit

i9100-LOS-16.0-emulated-memory-TWRP-3.3.1-1.img

Installed.

Then via TWRP 3.3.1-1 I have

Lineage-19.1-20220315-UNOFFICIAL-i9100.zip

lineage-19.1-20220315-UNOFFICIAL-i9100_magisk_24100_boot.img

Installed.

Android 12 has launched on the S2.(y)

BiTGApps-arm-12.0.0-R45_signed.zip cannot be installed.:confused:

Zygisk] doesn't work with magisk:confused:

(English translation via Google)
[Galaxy S II Android Development] Chicko24:
you can try the open Gapps 3 posts above yours
[Galaxy S II Android Development] Noboti:
open_gapps-arm-12L-pico-20220311-UNOFFICIAL_MOD.zip

Thanks for the hint.

Playstore can actually be installed with Open Gaspps and you can also register. After that, it no longer connects to the Internet, although there is an Internet connection.:(
[Galaxy S II Android Development] Noboti:
I finally managed (at least I think so) to flash the S2 properly

In any case, everything seems to be working more or less.

I was able to install Google Pay with "open_gapps-arm-12L-nano-20220311-UNOFFICIAL_MOD.zip" but still got the message no connection (see entry 168.)

Magisk including Zygisk works. An app for digital identity can now be started (this was not possible without Zygisk) unfortunately the app hangs when reading a QR code. Here the cooperation with the camera does not work properly or the hardware is too weak.

How did I install all of this?

1. First with twrp-3.3.1-1 installed on my S2 everything erased and formatted

2. Installed via Odin twrp-3.6.1_9.0-i9100.tar and i9100-LOS-19.1.pit

Attention for «twrp-3.6.1_9.0-i9100.tar» I renamed the image «twrp-3.6.1_9.0-i9100.img» to «recovery.img» and then «recovery.img» to «twrp- 3.6.1_9.0-i9100.tar» compressed.

3. After restarting TWRP 3.6.1_9.0 I have

“lineage-19.1-20220315-UNOFFICIAL-i9100.zip” and “lineage-19.1-20220315-UNOFFICIAL-i9100_magisk_24100_boot.img” installed

4. After restarting Android 12, I renamed the file "lineage-19.1-20220315-UNOFFICIAL-i9100_magisk_24100_boot.img" to "boot.img" for "Magisk" and copied it to the download folder. For "Magisk/Zygisk" I also downloaded the "safetynet-fix-v2.2.1_113247.zip" module and installed it via "Magisk".

;)
[Galaxy S II Android Development] hagadus:
Wow! Big thx for the hard work!
[Galaxy S II Android Development] hagadus:
:cool:(y)
[Galaxy S II Android Development] russanandres:
Hi again. Has a solution been found?
[Galaxy S II Android Development] Aussiewaterdragon:
Got some progress

Used Magisk Canery and now Zygist is enabled.

Modules still not enabled after reboot.

Wifi sometimes ok after reboot and sometimes enabled after network reset

Bluetooth good

Now using Microg all good except can only access Google email accounts via Gmail and not Fairmail, K9, Bluemail. Other email accounts fine.

Still can't get Titanium pro to work.

Still remarkably good for port of Android 12L
[Galaxy S II Android Development] xywojtek:
Is there any way of encrypting this ROM? when I try to do it, phone soft reboots.
[Galaxy S II Android Development] Concept48:
Rinando , last week I got a new S2 special for your Roms , now i have 3 lol
[Galaxy S II Android Development] zpunout:
Hi, I've had the latest build of LineageOS 19 on my S2 for a couple of months now. Today, when I tried to connect the phone to my laptop in USB Debugging mode, adb devices only returned the phone as "offline"

I tried revoking USB debugging authorisations, adb kill-server, restarting the phone and using an older version of adb. None of these attempts resulted in the "Allow USB debugging?" RSA key window to pop up on the phone. Is there something I'm doing wrong?
[Galaxy S II Android Development] notnoelchannel:
Hello, do you use "Minimal Fastboot and ADB"? Older ADB's show that the device is "offline"
[Galaxy S II Android Development] zpunout:
I'm using a recent (possibly still the latest) version of platform-tools on Linux Mint which was installed a couple of months ago. I also have a legacy version of platform-tools which I use for communicating with some old devices such as the 2011 model Xperia Arc. I tried adb from both versions of platform-tools on the Galaxy S2 LineageOS 19.

I'm considering a factory reset to see if that will get adb working. When connecting the S2 to the PC, a message pops up on the phone stating that it is connected in debugging mode, despite having revoked the USB debugging authorisations. Maybe that has something to do with why there is no pop-up message about accepting the RSA key to authorise debugging.
[Galaxy S II Android Development] OllieW:
Here my impressions of the LOS 19.1 alpha for the Galaxy S II (GT-i9100) after I've testet the no-Magisk versions 20220315 from the first post and a newer version 20220512 from AndroidFileHost with the unofficial OpenGApps 12L Pico versions 20220311 and 20220512 from here after a full wipe with the new PIT-File and the new TWRP version completely fresh installed:

With the May 2022 versions I can conform that GPS is working. Unfortunately the front camera bug is still present - back camera is working, but after switching to front camera the app will close immediately and can't be started again (ever after deleting config and cache in app info) - only reinstalling the LOS 19.1 image helps the camera app starting again with back camera.

The install assistent at the first startup won't connect to SIM immediately and Wi-Fi connection cannot be used (Google Speed Services will also hang up because of no internet - same problems as with LOS 18.1). After assistent is finished, the SIM and Wi-Fi can be used and the Google services will fetch all updates (also for Speech Services) and everything is OK. The phone is really slow and there is no "performance" settings in battery like in former versions to speed up clock (and disable energy saving).

@rINanDO Great work again! The Galaxy S2 will never die.. ;-)
[General Questions and Answers] double b26:
UPDATE: You can now get root on the Android 10 Umidigi A7 Pro using magisk.zip v25.2 (25200).

See post 10 for more info

----------

to cut to the chase, i have this Umidigi A7 Pro [128gb, global, non-eea rom] that im trying to root. ive hit a snag with Magisk patching.

at this point, and after much tribulation finding correct drivers, i have managed to get the bootloader unlocked [orange state notice at boot] via fastboot commands on the windows 10 box. device successfully boots to stock, un-rooted rom

then...

ive installed the latest Magisk Manager,

copied the original boot image from the stock rom over to the device,

ran the patch operation on magisk

copied patched boot file back over to pc.

load up smart phone flash tool and the stock rom,

selected the patched boot file in the flash tool > boot

pushed to device

ENDS with error notice on flash tool. device goes into bootloop.

resolve by flashing back all of the unmodified stock rom.

multiple attempts, same results

from what ive gathered, there may be an issue with the later versions of Magisk that have a problem patching the file correctly. word is that v20.2 and lower have worked with this device.

so at this point, im trying to install a downgraded version of Magisk. when i install an older version of magisk manager, it want to update the manager, and install magisk newest version. in settings, ive seen a custom update channel option, but i cant find the right input to make that point to an older version. IF thats even the right path to take?

ive been rooting devices for over ten years, but in the past few, i kinda fell out of the game since the newer devices have most of the features i used to have to root/rom to have. but now, im wanting to focus more on secuity and privacy, so im back at it. only to find things have changed substantially. so im well versed in the field, just rusty, and needing a crash course on magisk in general, and specific advice on this umidigi.

for picking it up on sale for $70 brand new from the manufacturer (summer 2021), its a solid device. on par with with same-year samsung A series, but half the cost and twice the storage. the Umi doesnt have an oled screen like the samsungs, but it does have a metal frame and glass back. also came with a decent phone case and preinstalled screen cover. 4g unlocked dual sim slots work with t-mobile over old sprint tower nearby, and their gsm towers in other areas. handles a 128gb sd card without problems. cameras are very similar to a samsung a20, but the umidigi includes an added marco lens, which is nice.

once i get this thing hammered out, ill try to compose a concise how-to and upload the files. looking around online, theres a lot of bad or outdated info for this device. ive had to hodge-podge the bootloader unlock from various guides for this and other umidigi models.

thanks in advance everyone!
[General Questions and Answers] double b26:
[reserved]
[General Questions and Answers] double b26:
earlier today i managed to find a link for magisk canary. i dont have the device near me atm, but i believe the manager is v7.5 and magisk itself is v19.X. the output patch file comes out named differently with the older version (newer version appends a unique string behind the name). however, same results as before. boot loop.

one positive note tho: the patched boot file completes with a big green check rather than the runtime error, or whatever it was previously.

i tried pushing the patched boot file over fastboot and via the flash tool. same results regardless.

re-flashed the stock boot image and phone is back up and running. still no root though.

still leaning strongly toward it being a magisk problem, but ive seen mention of disabling some security features dealing with individual partitions, but that was on other umidigi models, so ill have to research further if nothing else pans out
[General Questions and Answers] double b26:
found this tut mentioning vbmeta. otherwise, same process that ive been using with no success. figure its worth a shot. ill post back with results

rooting the umidigi a7 pro (magisk)

rooting the umidigi a7 pro (magisk). GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

This guide is for advince users only! better guide comming soon on XDA (I have test this on my own umidigi a7 pro )

In order to root your umidigi a7 pro you need to:
1) download device FW --> https://community.umidigi.com/forum.php?mod=forumdisplay&fid=235 (DO NOT download the EEA verison if you are not in Europe!)

2) download sp flash tool in case you brick you phone. --> https://spflashtool.com/

3) unlock your bootloader --> https://www.getdroidtips.com/unlock-bootloader-umidigi-a5-pro-2/

2) flash this vbmeta.img file with fastboot in bootloader mode. --> https://mega.nz/file/dnAS3AhD#g5PnSg-0UKFvyhZSZ8Em6gKO2Do7avaUepPmsH75-Bg
cmd: fastboot flash vbmeta vbmeta.img

3) extract the boot.img from fw.7z file and patch it with magisk

4) flash your patched_boot.img in bootloader mode
cmd: fastboot flash boot boot.img

enjoy your rooted phone!!!
[General Questions and Answers] double b26:
nope, the vbmeta thing didnt help. bootloop. i tried using the patch from the latest magisk, and the patch from the older version of magisk. same across the board.
[General Questions and Answers] 19deke55:
Glad to see I'm not the only one seriously interested in modding this phone. Although, now it belongs to my partner because her Huawei was not playing well with what she was using it for - playing a couple of games and messaging. It had started to slow down. Anyways, to get back to the Umidigi. I had looked at modding it and to be honest it seemed to be more hassle than it was worth and I think I couldn't get the thing rooted. I could connect to my laptop (it's honeslty much easier using Linux and installing ADB and Fastboot there) as Linux does not have the same issues with drivers that Windows has. Everything I do is through Linux...

So, in the end and because I now don't have the phone, whenever I need added peace of mind with a phone I try very hard to not install my Google account on the phone. I can install apks using APKPure for the few additional apps that may not be on the Stock ROM or not initialized through Play Store.

I'm afraid I can't help with Magisk though. The couple of times I've tried to work with it has not worked and I simply do all work through Linux and either push or sideload stuff or use a microSD. Often using TWRP but not always.

Cheers... hope you have some luck with what you are trying to achieve.
[General Questions and Answers] double b26:
[RESOURCES]

magisk download archive

Download Latest Magisk zip v23.0 and Magisk Manager 8.0.7 and Root your phone

On this page, we will share the full instructions to download and install Magisk zip on your Android Phone. This tutorial is also for the newbies/noobs

www.getdroidtips.com
[General Questions and Answers] double b26:
the driver issue was a bit of a hassle to sort out, but partially due to my sub-standard hughesnet satellite connection being sooo sloooooow. everything takes ridiculously long time.

> thus far, ive managed to get drivers and all that to mesh.

> bootloader unlock was straightforward... a few command lines

> from there, it should be a simple process of sideloading the magisk manager apk. within the manager, select [install] magisk zip, select [patch file] option from popup, point it to the [boot file] u pull from the stock rom image (now on your device storage)

> move the magisk patched boot file to the computer, run the flash tool, flash the patched boot, reboot and verify root <<OR>> push via fastboot

rather than reboot, i get boot loop. LOL

everything goes thru successfully, but just not working out. ive read around and seen talk of there being issues with magisk itself, and the patch file it outputs. something about using an older version, perhaps it has to be a specific one, will allow successful root. i gotta see if i can find that, and go from there.

magisk, from my understanding, serves the same purpose as super user or superSU. but also has some added benefits that are needed with modern system security, and the ability to install 'modules' from the magisk zip. sounds like it may be similar to xposed framework, if you know that. anyway, check the link i posted in previous post if you want to know more. apparently its the new big thing in root.

also, i guess TWRP is only partially functional on the Umidigi A7 Pro. im not sure exactly how or what. i just decided i would try the newer method since it seems like the way things are headed

if i can get this thing sorted out, ill bundle up the files and post up a package for people to grab. the way people talk, the same process can be used for several umidigi devices, and basically the same process for all (most?) mediatek chipped devices. MTK chipsets

also worth mentioning there is a pre rooted rom floating around, here on xda, i believe. cant recall the name of it off hand tho. however its a GSI rom (i think theyre called). my understanding is that GSI is like a one-sized-fits-all build method, where as long as the device meet preset criteria, the rom will run. that doesnt mean it will run well on every device tho, from what ive read. but, worst case scenario, its another avenue to consider.
[General Questions and Answers] 19deke55:
Thanks. The Mediatek side of things is interesting as I have at least one Lenovo tablet that uses them and the Kindle Fire tablet I have also. Such a pain that manufacturers have went down the road of locking bootloaders the way they have. It used to be so easy to install ROMs. Oh well. C'est la vie.

Thanks for the info. I can't see me touching the Umidigi now for a couple of years. It would be more than my life's worth, lol. I'll copy the contents of your post for future reference.

Have a nice day. Hope you have success with your efforts and that your satellite connection improves.