Related
WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!
The goal of this ROM is to experience ColorOS 6.0 on any non-oppo and non-realme phone.
For a list of treble supported devices, consult and fill https://github.com/phhusson/treble_experimentations/wiki
How to flash:
1- Flash a treble pie rom (CAF vendor recommended.)
2- Extract 7z file and flash system.img
3- If base rom isn't permissive flash permissiver.
4- Reboot
Bugs:
- Fingerprint
- Since it's oem port maybe more on your device. But common bug is Fingerprint.
Download:
system.img for A-A/B ARM64 devices
Telegram Account: MacTavishAO In case of any problem please send me logs.
Thanks to: @erfanoabdi for everything..
Reserved. You can follow me on github.
Changelog:
1.0: Initial release.
Does it include stock sounds and ringtones? Thanks
ZoiraP said:
Does it include stock sounds and ringtones? Thanks
Click to expand...
Click to collapse
yes
Nice work.
Keep it up.
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
surfer30 said:
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
Click to expand...
Click to collapse
You need pie treble vendor, permissiver.
I flashed over Lineage 16GSI (android 9). But not flashed permissiver - you sugested tryed once more?
Kanka Lenovo Z5 direk crash diag bölümüne atıyor dediklerini harfiyen yaptığım halde.
Lenovo Z5(L78011) didnt work.
Stuck on boot logo. My Vendor is CAF and flashed permissiver V2
Couldn't flash in nokia 6.1 plus
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Either bootloops or doesn't get past the boot image on Note9 N960F no matter what. (Different kernels, flash on different systems etc.)
rahul387 said:
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Click to expand...
Click to collapse
That isnt how it works
Some random said:
That isnt how it works
Click to expand...
Click to collapse
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
I have 2 questions :
1) Can I flash this ROM on Mi Max 2 with Orange Fox 10 recovery?
2) Can this be used for daily life usage?
Thank you
No boot
System partition smaller than image
rahul387 said:
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
Click to expand...
Click to collapse
I read that we have to resize the system partition when that error occurs. It's too advanced for me so I left it.
Kicked into fastboot
I've tried installing it exactly as described here and also how it's described for other pie GSIs for oneplus5t but I only get kicked into the fastboot mode. I really like to try out this rom on an amoled display. Any specific methods I should follow? (I used mokee phh treble vendor as that was recommended in most forums, am also decrypted..maybe i have to try by flashing noverity too) all gsi tutorials and pages for oneplus 5t are about a year old so i'm not sure I can follow that and succeed. Any help would be appreciated. Thanks.
I cant install in redmi 6a
Galaxy A3 2017? (a3y17lte)
I have discovered a thread of the project treble port, how to fix stuck on boot screen?
I have been developing Ubuntu Touch for the Tab A 10.1 2019
This ROM has been tested on both SM-T510 (WiFi version) and SM-T515 (WiFi + LTE)
Any developers reading this and has the device with them and are interested in the project may contact me :
@midhunvnadh on Telegram
Not Working :-
Bluetooth
Audio
Anbox (Android Emulator)
MTP
I am trying to fix these.
Download Files
Download the Halium arm32 GSI file : from Here
(Optional) Download SamsungUSBTethering zip : from here
Ubports Patched Kernel : from here
Get all the above files copied to your External SD Card
Installation
WARNING : I am NOT responsible for any damage caused to your device
If you are following this post, please takeup full responsibility of your device.
Noobs at flashing ROM's can click here: https://telegra.ph/Installing-Ubuntu-Touch-T510T515-08-22
Thanks to @ahamshubham for making this
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
(Because not tested on STOCK Android 10.0)
1.5 Boot into TWRP and Wipe all except external SD. REBOOT to recovery.
2.0 On TWRP : Flash the Lineage 16.0 build. DON'T REBOOT.
3.0 On TWRP : Goto Install -> Install Image -> (Flash halium-boot.img) DON'T REBOOT.
4.0 On TWRP : Goto Install -> (Flash ubports_GSI_installer_V1-arm32.zip).
5.0 (Optional) : Goto Install -> (Flash samsung-usb-tethering.zip)
5.1 Reboot.
(Incase : unable to boot ? , boot into TWRP -> reboot -> system)
samsung-usb-tethering.zip is used to get an SSH console from device to PC. Credits to @erfanoabdi
Please report all the errors you encounter here.
Sources
Kernel : https://github.com/midhunvnadh/android_kernel_samsung_gta3xlwifi
Device Tree : https://github.com/midhunvnadh/device_samsung_gta3xlwifi
GSI arm32 : https://github.com/midhunvnadh/android_device_halium_ubport
The Device tree is a dummy tree with kernel sources linked. Which serves a purpose of compiling halium-boot.img. For more info contact me.
Donations are always appreciated : Just click here
Reserved
Reserved
Pick me! Pick me!
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
mikehunt723 said:
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
Click to expand...
Click to collapse
Hello, you gave me a first reply... !!!
This is my real thread post on ROM's.
I didn't understand what you meant by "Pick me" and "I will gladly take that on. "
Are you looking forward to make contribution to this project ?
Bruh this is amazing work, keep it going!
This looks like an interesting project, none of the download links work for me
nubianprince said:
This looks like an interesting project, none of the download links work for me
Click to expand...
Click to collapse
It is a direct link. It works for me ?
Can you support Galaxy Tab A6?
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
I can try if you can give me a device.
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los14 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
MIDHUN.V.NADH said:
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
Click to expand...
Click to collapse
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
aveemashfaq said:
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
Click to expand...
Click to collapse
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi ! Thank you for your reply.
Were you able to boot into the OS ?
I haven't faced that issue. Can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32 eventhough some devices with the same SoC has full arm64.
I am trying to port arm64 vendor into the device but I think arm32 will be better because the device only has 2GB RAM (Atleast on my device)
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Worked!!
I was looking forward to run Ubuntu Touch on my Samsung Galaxy Tab A (SM-T515NZKDINU). I contacted MIDHUN.V.NADH, he helped me through the process and we got Ubuntu Touch running on my device. I would like to thank him for his help and his post. I, however, felt that I could not follow the instructions in the post very easily. Maybe, this is because I am doing something like this for the first time. So, I compiled a list of instructions to follow. I will send him this list of instructions and post them here too. I feel they will be helpful for people looking to run Ubuntu Touch on the same device.
MIDHUN.V.NADH said:
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Click to expand...
Click to collapse
Yes. I managed to initialize, however, this problem happens to me. I uninstalled Ubuntu and returned to android. Someday, when I have something stable, I test it again.
And about the processor architecture, I understand your explanation. Thank you!
Just adding instructions on how I did it on my device
My device details:
Device Model Number: SM-T515 (NZKDINU)
Linux Kernel Version: 4.4.111-17420370
Instructions for SM-T515:
1) Download these files using the links given in the post I am commenting on:
a) Halium arm32 GSI file
b) Ubports Patched Kernel
c) (Optional) SamsungUSBTethering zip
2) Copy all the above files to your External SD Card and insert this SD card in the device (tablet)
3) Flash STOCK Android 9.0 Pie on your device (tablet) and install TWRP:
a) For installing TWRP, use the following post: https://forum.xda-developers.com/ga...very-twrp-3-3-1-2019-galaxy-tab-10-1-t3934805. The instructions for installing TWRP as given in this post are:
i) Unlock bootloader (See the end of my comment)
ii) Hold Vol Up & Vol Down buttons during restart to enter Download mode
iii) Install TWRP to AP with Odin
iv) Hold Power & Vol Up buttons during restart to enter TWRP recovery
v) On TWRP: Swipe to allow modifications
vi) On TWRP: Wipe -> Advanced Wipe -> Select all except SD card
vii) On TWRP: Reboot -> Recovery
4) On TWRP: Go to Install -> Install Image -> (Flash halium-boot.img. Partition to flash image is BOOT). DON'T REBOOT. PRESS BACK.
5) On TWRP: Go to Install -> (Flash ubports_GSI_installer_V1-arm32.zip. Don't check any check boxes)
6) (Optional) On TWRP: Goto Install -> (Flash samsung-usb-tethering.zip)
7) Reboot
8) Ubuntu Touch will open. The password is: phablet
Unlocking Bootloader (Check this post: https://www.getdroidtips.com/oem-unlocking/):
1) Enable Developer Mode in Device Settings
2) Enable OEM Unlocking Option in Developer options after connecting to WiFi and setting the year in the phone to the year 2019
3) Get into Device Unlock Mode: Press (Volume Up Key + Volume Down Key + Insert USB Cable in the phone) while restarting the phone
4) Unlock bootloader. (Very Important!!) DON'T LET THE DEVICE BOOT INTO THE ANDROID OS AFTER UNLOCKING DEVICE BOOTLOADER
MIDHUN.V.NADH said:
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Click to expand...
Click to collapse
Hi, I just tried it out on my device. I had stock 9.0 over which I had flashed Lineage OS 17.1(based on Android 10). Over that, I flashed LOS 16, halium-boot, ubports-gsi and usb tethering. Worked for me.
I have to say, I have a pinephone and it seems that ubports on Samsung tab is faster than on pinephone.
antoine62 said:
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los15 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
Click to expand...
Click to collapse
Did you ever get this to work/ any tips for trying because I really want this to work (I am trying at the moment).
Hi everyone.
I just need help getting ported or compiling a TWRP for a Motorola One Macro it uses Android 9 with an Mediatek helio P70 processor, I have tried but I couldn't due the device has A/B partition system. can someone help me?
My boot.img if needed https://mega.nz/file/2aRUlYqY#GFeIbb1TYPg8x8Lq_fBiNu9UFenUgvFH1-eVjIm4uqE
TWRP patches device's boot.img, has nothing to do with whether device is an A/B system or an A-only system. On both systems only 1 boot.img exists.
jwoegerbauer said:
TWRP patches device's boot.img, has nothing to do with whether device is an A/B system or an A-only system. On both systems only 1 boot.img exists.
Click to expand...
Click to collapse
Got it, just the only thing is that i am a little confused due actually the boot and recovery are together on the same image that I uploaded, I previusly worked on A systems they have an specific recovery partition which this device doesnt do, so i just dont know how to work on it due always I try it ends on bootloop
@Kratos574
A-only systems have a dedicated /recovery partition, whereas A/B-systems don't have it: there boot.img contains recovery mode ramdisk
With regards to your bootloop problem: might be AVB ( read: Android Verified Boot ) didn't get disabled.
Also take note that TWRP won't install if AVB is enabled.
jwoegerbauer said:
@Kratos574
A-only systems have a dedicated /recovery partition, whereas A/B-systems don't have it: there boot.img contains recovery mode ramdisk
With regards to your bootloop problem: might be AVB ( read: Android Verified Boot ) didn't get disabled.
Also take note that TWRP won't install if AVB is enabled.
Click to expand...
Click to collapse
Well my AVB is already disabled, but its happenning the same thing the device just bootloops forever I have no experience on this kinda devices I stopped developing when android 6.0 came out haha
@Kratos574
Re-flash Stock ROM.
The process of flashing alone is conventional, shouldn't even need a thread to detail, but still leaving a thread here for search indexing.
With an unlocked BL, flash an ARM64 AB GSI within fastbootd, reboot to recovery, format userdata, reboot, profit. vbmeta isn't even needed in my case.
EDIT: One thing that's unconventional and I forgot to mention is, for many GSIs, you gotta delete product_a to make room prior to flashing:
Code:
fastboot delete-logical-partition product_a
EDIT2: Magisk doesn't like to see product_a go. Instead, just flash a blank one (from #15) to it:
Code:
fastboot flash product product_gsi.img
Thanks to @Whoareyou for the original finding and @darkghost568 for additional ideas.
Are we getting closer?
Winnower Amber said:
Are we getting closer?
Click to expand...
Click to collapse
To proper custom ROMs? Dunno, I don't do bringups. I'll at least make/refine/submit the device overlay so GSIs would look proper.
Note that Magisk seems incompatible and prevents booting, at least when paired with my GSI - need to restore to stock boot image. Mine comes with PHH-SU so I'm not keen on getting Magisk working anyway.
OK I'll ask since I have no clue. What's a GSI?
alarmdude9 said:
OK I'll ask since I have no clue. What's a GSI?
Click to expand...
Click to collapse
Home
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
AndyYan said:
Not sure why the GSI front is so quiet even after TMO variant got its unbrick tools...
Click to expand...
Click to collapse
I'm personally waiting until TWRP is more stable for this device before jumping into GSI.
Android 12 boots unsurprisingly as well, not as usable as 11 ofc.
A Generic System Image, is a universal version of android, which is available since project Treble separated the O/S into a "HAL" (Hardware Abstraction Layer) driver layer interface and the core operating system.
boot contains the kernel.
vendor, vendor_dlkm, odm, odm_dlkm are the drivers.
system, system_ext are the O/S core.
product is device specific O/S customizations.
Overview | Android Open Source Project
source.android.com
Project Treble is a good thing, making strides for Android to become a standardized operating system.
GSI install Guide:
Using information from:
Generic system images | Android Open Source Project
source.android.com
We find that we are supposed to flash vbmeta.img with "--disable-verification" because GSIs don't "include a verify boot solution". However, this step is not required on our particular device, due to OnePlus specific changes of verification being automatically disabled upon bootloader unlock.
Prerequisites: unlocked bootloader, up to date fastboot installed on a computer
1. Boot the phone into fastbootd mode by:
booting into recovery mode, by holding power and volume down during boot, then
rebooting into fastboot (only) mode, using touch menus: advanced, reboot into fastboot, then
connecting usb-c to a computer and using the poorly named command:
fastboot reboot fastboot.
Now we can use fastbootd commands.
2. We must erase the system partition:
fastboot erase system
3. next we need to obtain a GSI. I used phhusson's GSI build.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Choose arm64-ab for our phone's architechture
floss for open source apps but no GAPPS or vanilla for no GAPPS,
don't choose vndklite (Vendor Native Development Kit Lite) as it is a compatibility version for older versions of android's "HAL" layers.
"system-roar-arm64-ab-floss.img.xz"
decompress it to .img (and rename to GSI.img for brevity)
4. If we attempt to flash our GSI into the system partition:
fastboot flash system GSI.img
It will inevitably fail due to "not enough space to resize partiion"
The tool isn't smart enough to handle this task of resizing a "full" dynamic partition.
So we have to delete virtual partitions out of super to make room.
5. We must remove any present -COW partitions, which are Copy On Write partitions, which seem to be made by an A-Only virtual dyamic upgrade system. Their purpose is to host temporary changes to a partition, so the original partition is preserved for an emergency rollback, using associated interfaces to the original partition and the COW partition for access.
check your "fastboot getvar all" for any COW partitions, and delete them.
fastboot delete-logical-partition system_b-cow
6. In the official documentation, they admit that we have to delete the product partition(s) manually to make room.
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
7. With that done, we can reattempt to flash the GSI.
fastboot flash system GSI.img
8. The official instructions then require a fastboot -w in order to clear user data and "system partitions" data, but this is optional.
Are (A11 based) GSI's daily-drivable on the N200?
Also, do they allow for safetynet for banking apps, etc?
oCAPTCHA said:
Unofficial lineageOS 18.x by AndyYan is a Phhusson GSI derivative that claimed partial Magisk compatibility, but it also would not boot when Magisk patched. microG signature spoofing was not supported.
Click to expand...
Click to collapse
That Magisk compatibility does work on most other devices, even including an OPPO device which N200 is a rebadge of. Not sure why it is. Install PHH's Superuser and you get root for apps at least.
MicroG support is limited to priv-app for safety, as shown here.
BTW, long writeup, might wanna cut it down and/or add some emphasis?
lzgmc said:
Are (A11 based) GSI's daily-drivable on the N200?
Click to expand...
Click to collapse
VoLTE is one major hardware feature I can't verify; basic functionalities should be good. Heck, I daily-drive GSI on a device that has way more bugs than this.
mthous01 said:
Also, do they allow for safetynet for banking apps, etc?
Click to expand...
Click to collapse
PHH's "securize" option might allow you to do so for now (and unroot). I don't use GAPPS at all.
Rooting GSI Android 11
@AndyYan
AndyYan said:
That Magisk compatibility does work on most other devices, even including an OPPO device which N200 is a rebadge of. Not sure why it is. Install PHH's Superuser and you get root for apps at least.
MicroG support is limited to priv-app for safety, as shown here.
BTW, long writeup, might wanna cut it down and/or add some emphasis?
VoLTE is one major hardware feature I can't verify; basic functionalities should be good. Heck, I daily-drive GSI on a device that has way more bugs than this.
PHH's "securize" option might allow you to do so for now (and unroot). I don't use GAPPS at all.
Click to expand...
Click to collapse
Rooting GSI Android 11
Have you tried this yet, to get Magisk to work? I'm still on the bubble on wiping my phone and trying this, as it's my only daily driver right now.
mthous01 said:
Have you tried this yet, to get Magisk to work?
Click to expand...
Click to collapse
The /sbin hack is already integrated, but that doesn't seem enough here.
To root y'all need to do:
fastboot create-partition-primary 512 product
Then flash the attached product.
Then flash your rooted img, it'll boot successfully.
This GSI also works beautifuly, even has 90hz, if only there was an overlay for fingerprint scanning.
http://[STRIKE]https://jmirror.ml/0:/Jarvis-Mirror/Pixel5-Beta5-CB-GSI-Tutorials.7z[/STRIKE]
https://sourceforge.net/projects/gsitutorials-sgsi/files/SGSI/A12Beta/Pixel5-SP1A-A12-SGSI-GSI-Tutorials.7z/download
Whoareyou said:
To root y'all need to do:
fastboot create-partition-primary 512 product
Then flash the attached product.
Click to expand...
Click to collapse
OPlus devices really like to throw files (overlays, fstab, etc.) everywhere... TIL, thanks.
I tried out WhoAreYou's product image using
fastboot create-logical-partition product 512
(His syntax gave an error.)
While It did allow me to boot with a Magisk 23 patched boot.img along with Phhusson's vanilla GSI, Magisk did not work. The Magisk 23 app gave a strange error "Unsupported Magisk Version, This version of the app does not support Magisk version lower than v20.4". I downgraded to Magisk Manager 7.3.2 and the system hung whenever Magisk ran instead. Perhaps it is a conflict with the SU system in the GSI. I tried the "securize" option in the Phh treble menu, which caused a reboot, but did not remove root / su . I do not know how to remove the SU modifications present in the GSI, if that is required.
I attempted to use his product image along with his linked pixel 5 beta Android 12 GSI, but the system would not boot with a Magisk 23 patched boot.img.
I attempted to use his product image along with AndyYan's Unofficial Lineage 18.1, but the system would not boot with a Magisk 23 patched boot.img.
oCAPTCHA said:
I tried out WhoAreYou's product image using
fastboot create-logical-partition product 512
(His syntax gave an error.)
While It did allow me to boot with a Magisk 23 patched boot.img along with Phhusson's vanilla GSI, Magisk did not work. The Magisk 23 app gave a strange error "Unsupported Magisk Version, This version of the app does not support Magisk version lower than v20.4". I downgraded to Magisk Manager 7.3.2 and the system hung whenever Magisk ran instead. Perhaps it is a conflict with the SU system in the GSI. I tried the "securize" option in the Phh treble menu, which caused a reboot, but did not remove root / su . I do not know how to remove the SU modifications present in the GSI, if that is required.
I attempted to use his product image along with his linked pixel 5 beta Android 12 GSI, but the system would not boot with a Magisk 23 patched boot.img.
I attempted to use his product image along with AndyYan's Unofficial Lineage 18.1, but the system would not boot with a Magisk 23 patched boot.img.
Click to expand...
Click to collapse
oCAPTCHA said:
Could you flash a stock kernel on top of a GSI, then reroot with Magisk?
Click to expand...
Click to collapse
Try this updated GSI from the stable release, I just flashed it and it's definitely working:
https://sourceforge.net/projects/gsitutorials-sgsi/files/SGSI/A12Beta/Pixel5-SP1A-A12-SGSI-GSI-Tutorials.7z/download
Am using the same product I linked and magisk canary patched stock boot.img, Literally works perfectly aside from the fingerprint scanner.
oCAPTCHA said:
I tried out WhoAreYou's product image using
fastboot create-logical-partition product 512
(His syntax gave an error.)
While It did allow me to boot with a Magisk 23 patched boot.img along with Phhusson's vanilla GSI, Magisk did not work. The Magisk 23 app gave a strange error "Unsupported Magisk Version, This version of the app does not support Magisk version lower than v20.4". I downgraded to Magisk Manager 7.3.2 and the system hung whenever Magisk ran instead. Perhaps it is a conflict with the SU system in the GSI. I tried the "securize" option in the Phh treble menu, which caused a reboot, but did not remove root / su . I do not know how to remove the SU modifications present in the GSI, if that is required.
I attempted to use his product image along with his linked pixel 5 beta Android 12 GSI, but the system would not boot with a Magisk 23 patched boot.img.
I attempted to use his product image along with AndyYan's Unofficial Lineage 18.1, but the system would not boot with a Magisk 23 patched boot.img.
Click to expand...
Click to collapse
^
I am looking for a Nethunter Kernel for Readmagic 7 devices. I already have a rooted device and nethunter running but I could not put my wifi adapters to run even installing the drives using magisk. I am going to try flashing the kernel. Anyone here already made it for redmagic 7?
Thank you
sevenb_cezar said:
I am looking for a Nethunter Kernel for Readmagic 7 devices. I already have a rooted device and nethunter running but I could not put my wifi adapters to run even installing the drives using magisk. I am going to try flashing the kernel. Anyone here already made it for redmagic 7?
Thank you
Click to expand...
Click to collapse
Not sure if you made any headway on this? i'm working on the same thing and trying to compile a TWRP for NX679J.
Working on compiling a SkyHawk (SHRP) custom recovery for NX679J , also getting device tree slowly but surely...
polarbear666 said:
Working on compiling a SkyHawk (SHRP) custom recovery for NX679J , also getting device tree slowly but surely...
Click to expand...
Click to collapse
I'm close with the NX679J, is tricky but I have to start by changing the partition table... however, by pure accident I may have found a way to unlock bootloader on the meta quest 2 and it doesn't have the circus of A/B partitions that the NX679J has. building SHRP in terminal has been riddled with errors.BUT because of it's light weight design I'm compiling a pitch black recovery zip (PBRP). The only difficult thing is is that if the flashing app doesn't work inside Android I will have to go into fastboot and flash each partition over manually...Unlike TWRP- PBRP can seems more compatible with Android 12-12.1.... unlike TWRP that is very limited on 12 -12.1. PBRP (along with a specialized partition tool) can establish systemROOT on botH devices in theory..