Hello,
Here is the status as of few days ago. So most of Phh-based GSI should have the same status, just pick whichever you want.
What works:
- Backlight control works (requires "Force alternative backlight scale" in Treble Settings => Misc)
- 5G
- Bluetooth
- A2DP/Bluetooth media (requires "Force disable A2DP offload" in Treble Settings => Misc)
- USB-C headset
- Speaker
- 90Hz screen (Recommend "Force FPS" to 90Hz in Treble Settings => Misc)
- BSG GCam
- SELinux enforcing
- Encrypted userdata
- 65W Dash charge
What doesn't work:
- Under-display fingerprint
- Others?
Fixed in my AOSP GSI v311 (2021-08-07):
- Access to auxiliary cameras (Expose Aux cameras in Treble Settings => Misc)
Fixed in future AOSP GSI release:
- VoLTE (needs to click all 4 options in Treble Settings => IMS Settings)
- Alert slider
Links:
My AOSP GSI
List to other GSIs -- I recommend to try out LeOS, CAOS, or AndyYan's LineageOS
Flash procedure:
- Unlock bootloader
- Reboot into bootloader
- Download https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
- `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`
- `fastboot reboot fastboot`
- `fastboot flash system system-roar-arm64-ab-gapps.img`
- On the phone itself, do a full factory reset
As a small bonus, I attach the boot.img that I got on my device. It could be useful for people wanting to root with magisk, since currently the stock ROM isn't available. In exchange, I'd really like a dump of system partiton
Hmm... if i patch the boot dump with magisk it doesnt boot... if i flash the dump as it is, it boots fine
Thanks BTW!
do i have to flash vbmeta as well?
HofaTheRipper said:
do i have to flash vbmeta as well?
Click to expand...
Click to collapse
Hum yeah, it's likely that if you modify boot.img you need to disable boot.img verification through vbmeta
phhusson said:
Hum yeah, it's likely that if you modify boot.img you need to disable boot.img verification through vbmeta
Click to expand...
Click to collapse
OK i shouldnt have done this... now i have root bot no wifi/bluetooth anymore :-(
HofaTheRipper said:
OK i shouldnt have done this... now i have root bot no wifi/bluetooth anymore :-(
Click to expand...
Click to collapse
Does fingerprint unlocking work properly after rooted?
mlgmxyysd said:
Does fingerprint unlocking work properly after rooted?
Click to expand...
Click to collapse
Yes but i am rooted on oxygen... i think this boot.img missmatches with my modem firmware and so wifi and bluetooth is broken.
@phhusson do you have your modem.img for me to fix my problem or do you have another idea?
Hum there is no modem partition
hmmm do you have any idea, why my wlan and bluetooth isnt working anymore? wrong version of boot.img?
Have no bt address and a weird wifi mac
HofaTheRipper said:
hmmm do you have any idea, why my wlan and bluetooth isnt working anymore? wrong version of boot.img?
Click to expand...
Click to collapse
Do you have Indian varient?
No... should be EU Variant
ravinder0003 said:
Do you have Indian varient?
Click to expand...
Click to collapse
No should be EU Variant
Yeah it should be vendor/boot mismatch, so AFAIK, I'm on latest OTA, I'm assuming you too?
[ro.bootimage.build.fingerprint]: [alps/vnd_oplus6893/oplus6893:11/RP1A.200720.011/1626976753491:user/release-keys]
[ro.odm.build.fingerprint]: [OnePlus/DN2103EEA/OP515BL1:11/RP1A.200720.011/1626976753491:user/release-keys]
This is the build I currently have.
I've attached my vendor as well (which contains the kernel module that I'm guessing you are missing)
Can you dump your system partition, and send it to me? I need it for various developments
phhusson said:
Yeah it should be vendor/boot mismatch, so AFAIK, I'm on latest OTA, I'm assuming you too?
[ro.bootimage.build.fingerprint]: [alps/vnd_oplus6893/oplus6893:11/RP1A.200720.011/1626976753491:user/release-keys]
[ro.odm.build.fingerprint]: [OnePlus/DN2103EEA/OP515BL1:11/RP1A.200720.011/1626976753491:user/release-keys]
This is the build I currently have.
I've attached my vendor as well (which contains the kernel module that I'm guessing you are missing)
Can you dump your system partition, and send it to me? I need it for various developments
Click to expand...
Click to collapse
How do i flash this vendor.xz ?
my build is now (broken wifi / bt):
[ro.bootimage.build.fingerprint]:[OnePlus/DN2103EEA/OP515BL1:11/RP1A.200720.011/1627567766349:user/release-keys]
[ro.odm.build.fingerprint]: [OnePlus/DN2103EEA/OP515BL1:11/RP1A.200720.011/1627567766349:user/release-keys]
i would be happy to help you with a system dump. please tell me what to do.
K, looking at your properties, looks like I don't have the latest OTA, hum weird.
Decompress vendor.xz into vendor, then `fastboot flash vendor vendor` (you can rename vendor.xz to vendor.img.xz if it eases your spirit)
To make a system dump, from termux, with magisk installed, do:
`su` then `dd if=/dev/block/mapper/system of=/sdcard/system.img`, then retrieve system.img to your computer, compress it, and send it
phhusson said:
K, looking at your properties, looks like I don't have the latest OTA, hum weird.
Decompress vendor.xz into vendor, then `fastboot flash vendor vendor` (you can rename vendor.xz to vendor.img.xz if it eases your spirit)
To make a system dump, from termux, with magisk installed, do:
`su` then `dd if=/dev/block/mapper/system of=/sdcard/system.img`, then retrieve system.img to your computer, compress it, and send it
Click to expand...
Click to collapse
ok i will make the dump
btw:
C:\Fastboot\Fastboot ROMinstaller\fastboot_installer>fastboot flash vendor vendor
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/6 (131056 KB) OKAY [ 3.116s]
Writing 'vendor' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
This is what im getting
You need to do `fastboot reboot fastboot` before being able to flash vendor
phhusson said:
You need to do `fastboot reboot fastboot` before being able to flash vendor
Click to expand...
Click to collapse
Thank you very much! its working!!!
system.img is on the way!
Related
Hello guys, I have few questions and hopefully someone can answer them.
I am trying to root my mate 10 pro with version:
BLA-L29 8.0.0.127(C432)
I want to root it with magisk and since twrp is not available yet,
is it possible to root by patching the boot image?
If it is possible, how do I extract the boot image without root?
This is what i found online.
Method 2: Patching Stock Boot Image
This method doesn’t require you to have TWRP in order to install Magisk 15.0 update.
1. Download the latest Magisk Manager APK: MagiskManager-v5.5.1.apk
2. Use a file manager to install the downloaded app on your device.
3. Grab the stock boot image (kernel) and it should be corresponding to the firmware installed on your device.
For Nexus and Pixel devices, you can extract it from the factory image. For other OEM devices, you might need to check it with your manufacturer’s support.
4. Copy the downloaded “boot.img” to the internal storage of your Android device.
5.Open the Magisk Manager app and tap on the ‘Install’ button.
6. Again, choose ‘Install’ and then ‘Patch Boot Image File’.
7. Navigate to the storage and select the ‘boot.img’ file you just transferred.
8. The Magisk Manager app will patch the stock boot image and place the resultant ‘patched_boot.img’ in the ‘MagiskManager’ folder.
9. Transfer the file from your phone to C:\adb folder on your PC.
10. Hold the SHIFT key on your PC and right-click on an empty space inside the folder. Then select ‘Open PowerShell window here’ from the menu.
11. Boot your Android into Fastboot mode and connect it to the PC.
Enter the following command to root your Android phone using Magisk 15.0 update:
fastboot flash boot patched_boot.img
Finally, reboot your device.
fastboot reboot
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Dagda-Esus said:
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
Did you get the boot.img file ? or did you do it in another way ?
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
trackloading said:
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
Click to expand...
Click to collapse
ramdisk.img is correct. boot.img is ramdisk and kernel combined, but as of Oreo it's now ramdisk.img and kernel.img.
So patching ramdisk.img is the way to go?
yfaykya said:
So patching ramdisk.img is the way to go?
Click to expand...
Click to collapse
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
dawnc said:
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
Click to expand...
Click to collapse
Do you know your model number?
Like
xxx-CxxxBxxx
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
Did you get magisk working ?
lisa99 said:
Did you get magisk working ?
Click to expand...
Click to collapse
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the "Your device is unlocked" screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
ante0 said:
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the Your devices is unlocked screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
Click to expand...
Click to collapse
let me know if you figure something out.
ante0 said:
do you know your model number?
Like
xxx-cxxxbxxx
Click to expand...
Click to collapse
bkl-al20c00
dawnc said:
bkl-al20c00
Click to expand...
Click to collapse
You seem to have fixed it already?
ante0 said:
You seem to have fixed it already?
Click to expand...
Click to collapse
I've made a boot.img with supersu inside.
But can't fix magisk root
dawnc said:
I've made a boot.img with supersu inside.
But can't fix magisk root
Click to expand...
Click to collapse
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
ante0 said:
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
Click to expand...
Click to collapse
Have u found a way to make magisk work?
dawnc said:
Have u found a way to make magisk work?
Click to expand...
Click to collapse
It might be because loop is not fully working.
But no, haven't found any way.
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
dawnc said:
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
Click to expand...
Click to collapse
Not both at once no.
This is AOSP 10 for devices lunched with Android 9.0 , for older devices and devices with overlays and better support generally use this :
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
but if you want lean & mean AOSP with no modification and minimal gapps , here you go :
https://mega.nz/#!y7J1DCRL!YcPmXLGf71ptVF4IP3N_46Y5o4yOOac32Pj1lSmQ0G0
also it is a user build so it passes basicintegrity , to pass CTS install safeteypatcher from magisk repo .
arm build :
https://mega.nz/#!7yggQC5A!EyXx_ZJ1hGInlf_XXYwYAZU8qtErajsNJzGdmDsEWqs
any source?github?
reynard1 said:
any source?github?
Click to expand...
Click to collapse
it's built on top QP1A.191105.004 with mindthegapps :
https://gitlab.com/MindTheGapps/vendor_gapps
@AJ
Be more specific in describing your builds. Arm64 - A-only or A/B ?
Nordicus said:
@AJ
Be more specific in describing your builds. Arm64 - A-only or A/B ?
Click to expand...
Click to collapse
Need this info OP
Nice work. Could you upload an arm32 version?
Nordicus said:
@AJ
Be more specific in describing your builds. Arm64 - A-only or A/B ?
Click to expand...
Click to collapse
Go to proper thread from OP. That one is only some like an info, I think.
Nordicus said:
@AJ
Be more specific in describing your builds. Arm64 - A-only or A/B ?
Click to expand...
Click to collapse
read this :
https://source.android.com/setup/build/gsi#p-gsi-build-targets
the new naming arm64 apply to both AB and non AB .
Hanthonious said:
Nice work. Could you upload an arm32 version?
Click to expand...
Click to collapse
arm build added .
AJ said:
arm build added .
Click to expand...
Click to collapse
Awesome man thanks but is A64 a-only supported?
Not booting, is the arm32 system A or AB?
Hanthonious said:
Not booting, is the arm32 system A or AB?
Click to expand...
Click to collapse
you have to be on stock rom then flash system & vbmeta with :
fastboot --disable-verification flash vbmeta vbmeta.img
and it works on both a and a/b if your device shipped with android 9
mahmmoud1231 said:
Awesome man thanks but is A64 a-only supported?
Click to expand...
Click to collapse
Check post #8
AJ said:
This is AOSP 10 for devices lunched with Android 9.0 , for older devices and devices with overlays and better support generally use this :
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
but if you want lean & mean AOSP with no modification and minimal gapps , here you go :
https://mega.nz/#!y7J1DCRL!YcPmXLGf71ptVF4IP3N_46Y5o4yOOac32Pj1lSmQ0G0
also it is a user build so it passes basicintegrity , to pass CTS install safeteypatcher from magisk repo .
arm build :
https://mega.nz/#!7yggQC5A!EyXx_ZJ1hGInlf_XXYwYAZU8qtErajsNJzGdmDsEWqs
Click to expand...
Click to collapse
bugs reported?
I tried flashing this rom via fastboot but faced sparse error, tried with twrp but system failed to boot. My device is Infinix s5, I am able to boot phh gsi 9.0 without issues and yes my device was released with android 9.0.
contactwajeeh said:
I tried flashing this rom via fastboot but faced sparse error, tried with twrp but system failed to boot. My device is Infinix s5, I am able to boot phh gsi 9.0 without issues and yes my device was released with android 9.0.
Click to expand...
Click to collapse
The official flashing instructions :
Code:
fastboot erase system
fastboot flash system system.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
If the sparce error means nit enough space in system do :
fastboot delete-logical-partition product_a if A is your main slot
AJ said:
The official flashing instructions :
Code:
fastboot erase system
fastboot flash system system.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
If the sparce error means nit enough space in system do :
fastboot delete-logical-partition product_a if A is your main slot
Click to expand...
Click to collapse
I followed the exact same instructions, I get the following error after I enter fastboot flash system system.img
"Invalid sparse file format at header magic"
Edit: that is when I tried to flash with twrp, but it resulted in bootloop just soon after the initial device logo. Please advise.
contactwajeeh said:
I followed the exact same instructions, I get the following error after I enter fastboot flash system system.img
"Invalid sparse file format at header magic"
Click to expand...
Click to collapse
Which fastboot and system are you using ??
AJ said:
Which fastboot and system are you using ??
Click to expand...
Click to collapse
fastboot version 29.0.5-5949299
Installed as C:\Windows\fastboot.exe on windows 10
contactwajeeh said:
fastboot version 29.0.5-5949299
Installed as C:\Windows\fastboot.exe on windows 10
Click to expand...
Click to collapse
I would try older fastboot that mtch your rom security patch , and also maybe try linux if you have access to it .
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
^
Sekiyama-Kernel for Oneplus N200 5G
Features:
Main Features:
- Based on latest kernel sources from OnePlus for Android 11
- Upstreamed against latest kernel-common (android12-5.4-lts)
- Linux-Stable-Upstream included to latest 5.4.179
- compiled with Clang 13.0.1 prebuilt from Google
- built with -O3 speed optimizations
- Link-Time-Optimization (ThinLTO)
- Link the kernel with LLD and use RELR-Relocation
- fix several coding issues detected by newer Clang-Toolchains
- include important fixes/improvements from kernel/common
- Supports ALL variants, NA/TMO/OEM
- Wireguard Support
- If you want magisk, you must patch first!!!
Downloads:
https://github.com/ArtiicPanda/oneplus-sm4350/releases
Requirements
- Unlocked Bootloader
- USB Debugging in developer options enabled
- Latest adb and fastboot
How to flash the Kernel:
Boot to fastboot/bootloader to flash boot.img:
Either select Reboot to bootloader option via buttons
or type:
Code:
adb reboot-bootloader
Now in fastboot flash boot.img
Commands:
Code:
fastboot flash boot boot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Reboot either via buttons
or by typing
Code:
fastboot reboot
@Freak07 for his kernel thread from which I drew inspiration.
Source Code: https://github.com/ArtiicPanda/oneplus-sm4350
reserved
reserved
Any updates?
blowtorchhonor said:
Any updates?
Click to expand...
Click to collapse
Need some time to create a great OP
Tests builds are available here:
Join «Nord N200 Testers» on Telegram: https://t.me/OnePlusNordN2005G
Released. Thank you to all that helped test prior to release. Enjoy!
I can vouch that this kernel really helps this device run faster. I already tested many things from bluetooth to phone calls and everything works. Enjoy everyone!
11.0.2 Update posted, changelog on github
Wonderful work to you and @Travisholt92. Really surprised how far everyone has gotten in such a small amount of time.
Wivioo said:
Wonderful work to you and @Travisholt92. Really surprised how far everyone has gotten in such a small amount of time.
Click to expand...
Click to collapse
Apparently all it took to kick things off was me extracting the defconfig from the stock kernel and showing it could be built (partially) and then @ArtiicPanda being awesome decided to get in on the action
Travisholt92 said:
Apparently all it took to kick things off was me extracting the defconfig from the stock kernel and showing it could be built (partially) and then @ArtiicPanda being awesome decided to get in on the action
Click to expand...
Click to collapse
definitely was a team effort. again thanks to the testers as well. @blowtorchhonor @TheLoonyRebel
Just flashed 11.0.1 (couldn't find a binary for 11.0.2) and it successfully booted on my TMO/metropcs flashed to unlocked firmare running latest Pixel Experience A12 GSI
cognitoinc566 said:
Just flashed 11.0.1 (couldn't find a binary for 11.0.2) and it successfully booted on my TMO/metropcs flashed to unlocked firmare running latest Pixel Experience A12 GSI
Click to expand...
Click to collapse
I think they forgot to post 11.0.2
edit: they forgot to compile the source to a .img
No, there were some minor issues with 11.0.2 so it's being reworked, just use 11.0.1 until then.
Update posted, change log on GitHub
I have this notification that says serial console enabled performance is impacted to disable check bootloader and I have no idea how to disable it. I'm also unable to use usb debugging for more than 2 seconds as it goes away and stops
Tyreethetruth said:
I have this notification that says serial console enabled performance is impacted to disable check bootloader and I have no idea how to disable it. I'm also unable to use usb debugging for more than 2 seconds as it goes away and stops
Click to expand...
Click to collapse
Same here. I installed 11.0.2.1, the most recent one on T-Mobile stock 11.0.1.9 and the same notification shows up.
After reboot, the screen got darker, and can't control brightness anymore.
Going back to stock boot...
lentm said:
Same here. I installed 11.0.2.1, the most recent one on T-Mobile stock 11.0.1.9 and the same notification shows up.
After reboot, the screen got darker, and can't control brightness anymore.
Going back to stock boot...
Click to expand...
Click to collapse
I fixed it, you just have to reflash magisk via fastboot
Tyreethetruth said:
I fixed it, you just have to reflash magisk via fastboot
Click to expand...
Click to collapse
I patched kernel image via magisk then flashed magisk patched kernel image via fastboot and it happened.
lentm said:
I patched kernel image via magisk then flashed magisk patched kernel image via fastboot and it happened.
Click to expand...
Click to collapse
Try flashing the kernal via fastboot then fully boot the phone then flash the magisk patched image again via fastboot and it will get rid of the notification
Hello all, I've been trying to install /e/ OS GSI on my Redmi Note 11S, but that didn't go exactly well. Luckily, I managed to fix it. So before I brick this thing again, How should I install a GSI properly without bricking, and which GSI would you recommend? I am looking for something more privacy oriented. Thank you in advance
[TOOL][AUTOINSTALLER][GSI]SMINORI GSI AUTO INSTALLER FOCO M4 PRO
After i'm search many tutorial and thread about installing clean and optimal GSI and take a lot of time. So, i decided to make batch auto installer for GSI ROM for help u guys, this is easy way for installing gsi rom WITH JUST PRESS ENTER:sneaky...
forum.xda-developers.com
nothing other than that. thats it.
when it goes wrong u can easly flash full stock with miflshtool
lurchiii said:
[TOOL][AUTOINSTALLER][GSI]SMINORI GSI AUTO INSTALLER FOCO M4 PRO
After i'm search many tutorial and thread about installing clean and optimal GSI and take a lot of time. So, i decided to make batch auto installer for GSI ROM for help u guys, this is easy way for installing gsi rom WITH JUST PRESS ENTER:sneaky...
forum.xda-developers.com
nothing other than that. thats it.
when it goes wrong u can easly flash full stock with miflshtool
Click to expand...
Click to collapse
Thank you
Is there some sort of Linux alternative?
And which GSI would you recommend?
kritomas said:
Thank you
Is there some sort of Linux alternative?
And which GSI would you recommend?
Click to expand...
Click to collapse
I have tried Evolution X A13 & Pixel Experience Plus A13 & CRDROID A12 and on all of them I had issues with Wifi, bluetooth, thethering - non of them worked so I gave up and went back to miui
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (take the vbmeta.img file from your current firmware)
3. fastboot reboot fastboot (because gsi must be flashed in fastbootd )
4. fastboot getvar is-userspace
5. fastboot erase system
6. fastboot delete-logical-partition product_a
7. fastboot flash system YOUR_GSI_ROM.img (system.img)
8. fastboot reboot recovery
9. (in recovery) wipe data
10. (in recovery) reboot to system
i flashed yesterday Arrow OS lite A12 it has several fixes for most common problems on board and it worked very well and smooth.
on telegram you can found a magiskmodul fix for auto-variable Hz and a magisk modul for disable hw-overlays consistent. (cauz after reboot it turn back on automaticly)
BUT gaming performance is horrible and good kernel tweaks are over my level
Had someone tried any of these GSI images without having wifi / bluetooth issues?
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
..... flash vbmeta vbmeta.img (take the vbmeta.img file from your current firmware)
Click to expand...
Click to collapse
Where should I take the vbmeta.img for my phone?
shady9090 said:
Where should I take the vbmeta.img for my phone?
Click to expand...
Click to collapse
Download the Fastboot Firmware that match the Firmware on your phone from here: https://forum.xda-developers.com/t/...dmi-note-11s-4g-poco-m4-pro-4g-fleur.4428655/
Extract it with the file and in the images folder is the vbmeta.
I have this weird issue on every GSIs where the status bar isn't aligned with the camera. Does anyone know how I can fix that?
Dio Off-Brando said:
I have this weird issue on every GSIs where the status bar isn't aligned with the camera. Does anyone know how I can fix that?
Click to expand...
Click to collapse
In the Developer Options is a fix for that. But idk how the exactly Name was for it.
lurchiii said:
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (take the vbmeta.img file from your current firmware)
3. fastboot reboot fastboot (because gsi must be flashed in fastbootd )
4. fastboot getvar is-userspace
5. fastboot erase system
6. fastboot delete-logical-partition product_a
7. fastboot flash system YOUR_GSI_ROM.img (system.img)
8. fastboot reboot recovery
9. (in recovery) wipe data
10. (in recovery) reboot to system
i flashed yesterday Arrow OS lite A12 it has several fixes for most common problems on board and it worked very well and smooth.
on telegram you can found a magiskmodul fix for auto-variable Hz and a magisk modul for disable hw-overlays consistent. (cauz after reboot it turn back on automaticly)
BUT gaming performance is horrible and good kernel tweaks are over my level
Click to expand...
Click to collapse
So from Linux with platform-tool installed and by giving the mentioned commands I can flash Gsi rom Pixel Experience right???
fastboot delete-logical-partition product_a??? no b???
yes you can flash it from windows or from linux. they are the same commands..
and yes only a
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com