Database Info

[TREBLE][DEV] Mistery solved, developer documentation for GSI on One Plus 6

So after 2 weeks of debugging and trying to figure out why Treble GSI were not booting, then booting only for some users the final answer has been found.
This bootloader is way too stateful.
So if you try directly with proper vbmeta & system.img, you won't notice anything, it will just work, that's why some people say it works.
If you try system first without doing vbmeta, then it will mark the slot as not bootable. Flashing vbmeta afterwards will NOT mark it as bootable.
it also requires the latest fastboot with --disable-verity and --disable-verification, don't know why yet exactly.
Now if you bootloop to mark it as bootable again, you need to flash the boot partition of the slot.
Even worse than that "fastboot boot" works only if current slot is not marked as not bootable, so any try to launch TWRP fails once your in this mode.
This same issue also applies to users trying to restore to stock sometimes.
This means that the One Plus 6 will require proper documentation on how to do things, and people will have to stick to it, see official instructions in post 2.
Now that we know what the exact cause is, and how to deal with it, let the development begin.
PS
Doesn't seem to be OP fault, just stock Qualcomm bootloader.
Credits to Phhusson and me for making this possible, providing phh a device, documenting the findings and all.

WARNING This is still ALPHA
OFFICIAL INSTRUCTIONS
Correct installation procedure of a GSI on the One Plus 6, determined together with @phhusson
Make sure you unlocked the bootloader and that you have the absolute latest ADB and Fastboot from Google, none of the minimal packages we know of will work!
Then in fastboot flash the following, WITHOUT rebooting in between! this needs to be done all in one go!
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Use the STOCK boot image!
Then flash the GSI system image of your choice
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
Then flash STOCK vbmeta image with the specific commands!
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then just fastboot reboot or select start on the phone.
---------------------------------------------------------------------------------------------------------------------------------------------------
If the above fails and you get a bootloop you will have to repeat all the steps above.
---------------------------------------------------------------------------------------------------------------------------------------------------

So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?

@Exelios
Thank you for sharing.

Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ

Great work man,
I had held off trying as I didn't know if it would work for me or not. Looking forward to trying this out!!!
Sent from my OnePlus6 using XDA Labs

joemossjr said:
So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?
Click to expand...
Click to collapse
Yeah you can do that once, but to get your first slot back you will need to re flash boot also at some point.
And remember once you flash boot you need to root and TWRP again.
Sent from my OnePlus 6 using XDA Labs

CertifiedBlyndGuy said:
Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ
Click to expand...
Click to collapse
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs

Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.

DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
Give it a day, phh is trying to implement fixes to the findings in a more elegant and easier way for the end user, this thread was more intended to share our findings with other devs.

DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
I've booted multiple roms comsic aosp aosip they boot just gotta get it right the first time

Exelios said:
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Ok. Just PM me and I'll move the thread when it happens

Still investigating, there is probably still something to this I'm missing

Exelios said:
Still investigating, there is probably still something to this I'm missing
Click to expand...
Click to collapse
What is the findings so far?

DocRambone said:
What is the findings so far?
Click to expand...
Click to collapse
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.

Exelios said:
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.
Click to expand...
Click to collapse
I couldn't get v19 of phh's AOSP to boot for the longest time until I tried this! Thanks man!! :good:

I have cleaned up the OP and added clear instructions in post 2.
Tho LOS still doesn't boot for now, but that's because of a bug specific to the GSI, not a bootloader issue.

Delete

CertifiedBlyndGuy said:
Ok. Just PM me and I'll move the thread when it happens
Click to expand...
Click to collapse
Might I ask to make this a sticky?
Because every developer needs to be aware of it, this doesn't affect just GSI, one can run in the same issue even if flashing TWRP or restoring to stock or anything.
And every user should know about the official way to do things on the One Plus 6, which is slightly different then all other phones.
Thanks

The instructions in post 2 is the same as in the treble thread, still no boot other than aosp v18

Noob guide to install GSI on whyred

Today I flashed Pixel Experience GSI on my whyred after much trouble so here is a guide to make things clear.
if you are coming from MIUI you have to format data from twrp. this is a must to disable encryption.
after you are done formatting data. just do factory reset from twrp and then go to advanced wipe and then do the regular dalvik, cache, system, data and then swipe to wipe.
now the thing is whyred officially supports treble but the implementation is shoddy according to XDA folks. so if you flash GSI over miui's vendor there will be many bugs. like brightness slider not working and many things. so they(all credit goes to them) created a vendor zip which makes things really good. there are no bugs and it also supports volte. here is the download link .
https://www.androidfilehost.com/?w=files&flid=273660
now flash this zip file in twrp.
after that download the GSI of your choice from here.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
remember to download arm64 A only system image.
here is pixel experience GSI which I prefer:
https://download.pixelexperience.org/treble_gsi/
now extract the zip and you will get a single .IMG file which is your system image. now go to twrp and then go to install then go to select install image downward. (don't flash directly, it's an .IMG file) then select the extracted .IMG file and then choose system and then flash.
then reboot system. that's it. you should boot fine.
download latest official twrp from here: https://dl.twrp.me/whyred
if you want root you will have to flash magisk beta 16.6 which works better on GSI. download here.
https://github.com/topjohnwu/Magisk/releases/download/v16.6/Magisk-v16.6.zip
to use Google camera you will have to enable camera2api. arnova's gcam doesn't work on this build. you will have to use BSG's gcam. here is the link. enable nexus style and active portrait mode from settings.
https://www.celsoazevedo.com/files/android/google-camera/f/MGC_5.2.022.apk
few tips: if your device is not booting and going to fastboot, flash magisk. it will definitely boot up.
if your device shows decryption failed, just format data from twrp. it will delete all user data btw.
no need to flash lazyflasher.
there are no uncertified device pop up from Google. so no need to worry.
playstore shows uncertified btw and magisk shows CTS false.
all the links that I have linked here, the credit goes to the creators. I am a normal user of XDA. thanks to them.
happy flashing and all hail the XDA lords.

How is Pixel experience gsi though?....faced any bugs till now?

it's good but there where few bugs. anyway pixel experience rom specifically for whyred has been released. you can flash that. it's great and bug free. download it here. it's not GSI though. normal ROM.
https://download.pixelexperience.org/whyred/
mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse

mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.

I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
goofball2k said:
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.
Click to expand...
Click to collapse

mearjunsha said:
I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
Click to expand...
Click to collapse
So should I flash the ROM or the gsi?....are there any differences?

you should flash the ROM as it's specifically for whyred. its flashing instruction is different than GSI. but easy. just wipe and then flash the ROM. and reboot. that's it.
you may have to format data to disable encryption.
here is the forum discussion: https://forum.xda-developers.com/redmi-note-5-pro/development/rom-pixel-experience-t3816099
mr._.nobody said:
So should I flash the ROM or the gsi?....are there any differences?
Click to expand...
Click to collapse

Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?

remove all security like fingerprint, pattern etc.
go to twrp
go to wipe
do factory reset
go to advanced wipe
select dalvik, cache, system and data and then wipe
go to install
flash the pixel experience rom
reboot to system
that's it
if you get a prompt to enter password to start android then you will have to go back to twrp and go to wipe and format data and type yes. it will delete all your files btw. so backup everything. then reboot it will boot up fine.
after you have done booting and set up, go back to twrp and flash magisk v16. reboot to system. all done.
I have already given details of gcam in my OP. Kindly check that. The same works great on this ROM.
ask me if you face any problem. happy to help ?
trazalca said:
Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?
Click to expand...
Click to collapse

You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!

I understand your excitement but do check your build whether you are on Anti rollback. if you are on 9.5.19 you should absolutely not proceed right now.
read about it on XDA.
trazalca said:
You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!
Click to expand...
Click to collapse

I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?

you can go ahead. happy flashing! ?
trazalca said:
I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?
Click to expand...
Click to collapse

[dupe sorry]

You should by all means read about antirollback to be sure, but my understanding is that the antirollback refers to the firmware, not the rom. MIUI roms all include different firmware, so you can't rollback a MIUI rom (unless it's been modded to be firmwareless). But as far as I know, no custom roms include firmware, so you should be fine even if your firmware is ARB triggered if all you're doing is installing custom roms.

Hi, someone flashed latest Pie Phh GSI? I tried with PE CAF, AOSIP, and Mokee vendors but doesn't boot, always stuck at the Mi logo, even I flashed the permissiver patch without luck.

Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?

ShadowFax said:
Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?
Click to expand...
Click to collapse
Nope.

[GSI AB][10.0?] Android Q developer preview - working!

Hi, I was trying to flash some new gsi and I found this https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
Working Android Q! Bugs are normal with base 10.0.3.0 - Fingerprint not working... etc.
I used traditional method:
-Flash base
-fastboot erase system
-fastboot -w
- TWRP- flash Permissiver_V2.zip and Disable force encryption
Voila! Enjoy
Bug: Notch support

Hello,
First of all Congratulations for your success,
Could you please describe the flashing process because i have been trying it for 2 days still no success.
Did you flashed vbmeta? & which one did you used ARM64 OR ARM64+GMS?

you cant and you dont need to flash vbmeta. before doing anything read the instructions carefully. first, mia2lite doesnt have any vbmeta partition so you cant flash it, secondly its written there that this partition is needed to remove avb from boot partition of some specific phone so you dont need it.
what you need is flash remove_verity zip or patch your boot.img with magisk disabling preserve avb.

masumrussell said:
you cant and you dont need to flash vbmeta. before doing anything read the instructions carefully. first, mia2lite doesnt have any vbmeta partition so you cant flash it, secondly its written there that this partition is needed to remove avb from boot partition of some specific phone so you dont need it.
what you need is flash remove_verity zip or patch your boot.img with magisk disabling preserve avb.
Click to expand...
Click to collapse
I still didn't get it, he says flash base means he is talking about stock or GSI & if GSI then how?

CherryFarmer8 said:
I still didn't get it, he says flash base means he is talking about stock or GSI & if GSI then how?
Click to expand...
Click to collapse
Flashing base means to flash stock firmware
In this case it's 10.0.3.0. as mentioned in the first post

capajga said:
Flashing base means to flash stock firmware
In this case it's 10.0.3.0. as mentioned in the first post
Click to expand...
Click to collapse
okay so in which step do i have to flash GSI?

CherryFarmer8 said:
okay so in which step do i have to flash GSI?
Click to expand...
Click to collapse
You can try it like this:
Gumka1977 said:
https://github.com/tkchn/daisyinstall Do it like here, but instead of system.zip in TWRP - install system. img !
Click to expand...
Click to collapse
Thanks to Gumka1977

capajga said:
You can try it like this:
Thanks to Gumka1977
Click to expand...
Click to collapse
And what gsi did you flash?

[ROM] [AOSP Pie] [2019-08-25] Phh-Treble

Hi all,
I'm presenting here my ROM for S10e (whose main thread is https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915 ).
It is generic, but it doesn't mean anything bad!
Pretty much every works, and this is my daily driver (Exynos variant).
What works:
- Camera
- Wifi
- 2G/3G/4G, including signal level
- Phone calls
- Fingerprint sensor
- Encryption
- Proximity sensor
What doesn't work
- VoLTE
- stock OneUI camera app
- MTP
You can install some modded Google Camera on it for acceptable Camera quality.
Download links:
- With included gapps
- Without included gapps
How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset.
- Enjoy!
Recommended after installing:
- Default Launcher is AOSP's. It sucks. You should really install another Launcher. I recommend and use Lawnchair
- Pretty much no Google app is preinstalled, only Play Store and Chrome. You'll probably want to install Google, Google Assistant apps, Gmail, ...

free post for me and myself

Support for G9700?

Could system.img possibly be flashed through recovery? And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler

DeHuMaNiZeD said:
Could system.img possibly be flashed through recovery?
Click to expand...
Click to collapse
Yes
And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler
Click to expand...
Click to collapse
TBH I recommend not to flash any disabler, they bring more issues than they fix.
Android security is already not ideal, disabling encryption sounds like a very bad idea
(And disabling dm-verity is totally useless, because when flashing a GSI it already is)
NisseGurra said:
Support for G9700?
Click to expand...
Click to collapse
Yes G9700 is supported, though bear in mind that since it's not the same device, you don't really have the same guarantees. I'll help you through your issues either way.

Ok, tested on G9700, latest stock rom installed (android 9).
TWRP with multidisabler installed, format data, reboot recovery. Install V120 gsi, reboot.
Boots nicely.
Findings: no autobrightness, slider ok tho. Wifi/BT/NFC ok. No MTP (as stated)
Dual sim ok, voice calls ok, data ok. 3.5 output ok
Edit: Best way to root?, addonsu-16.0-arm64-signed.zip?

im gonna try this right away

i have one simple question before trying does magisk work with this and can i just use a magisk pachted system
---------- Post added at 07:32 AM ---------- Previous post was at 07:16 AM ----------

To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B

mikk150 said:
To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B
Click to expand...
Click to collapse
In the true sense, it is A-only, it doesn't have seamless update.
The difference between A-only and A/B was that A/B included the init, while A-only didn't.
But since Pie, A-only also includes init, like A/B. I didn't update the naming convention (because it just gets even messier).
Hackintosh5 developed Treble Info ( https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en_US ) to make things clearer.

Do you have PHH for Android 10 for this device?

vlubosh said:
Do you have PHH for Android 10 for this device?
Click to expand...
Click to collapse
It is still unstable, that's why I haven't shown it in this forum yet.

Do these steps apply to any devices? Or only specific models? I have an Elephone Soldier, and I notice different website have different procedures. Not sure which one is right. Thanks.
"How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/and...gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset."

I just installed AOSP 9.0 v119 for my Elephone Soldier. I can confirm the system boots up, but there is no sound. (ie. ring tone, media, notification) None of these sound work.

One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks

BratoMo225 said:
One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks
Click to expand...
Click to collapse
No as I have heard. The knox fuse is a physical fuse which can never be reset so these apps will not work.

[Tutorial] Magisk on GSI on devices with dynamic partition

I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/...ynamic-super-partition.4256667/#post-85271987
If youre on stock before flashing GSI then dont "fastboot delete-logical-partition product" like other tutorials may suggest. Just flash the product image (fastboot flash product [insert img here]) attached below and it will get resized automatically as well, giving you plenty of space to flash your GSI.
If youve already flashed GSI before following this guide and have done "fastboot delete-logical-partition product" then just create product partition (fastboot create-logical-partition product [size]) and flash the img on product.
whichever course youve taken you can now flash magisk through twrp or patch the boot img and flash that.
Please note that this product image wasnt made by me and the credit for it goes to: @Allexwin50
tested on infinix zero 8 X687

Thanks for the tutorial, I will give it a try but have one question: you said to" create product partition and give size " I don't understand about size!

shjeanpy said:
Thanks for the tutorial, I will give it a try but have one question: you said to" create product partition and give size " I don't understand about size!
Click to expand...
Click to collapse
when you create partition you also need to specify its size, just add some number

kusti420 said:
when you create partition you also need to specify its size, just add some number
Click to expand...
Click to collapse
What size would you advise me please

shjeanpy said:
What size would you advise me please
Click to expand...
Click to collapse
idk, i used 400000000

Thank you very much for your great tutorial. it worked for me on my device.

Thanks a lot for putting this together. I was stuck for a day and a half trying to figure out how to flash Magisk with no product partition. Great work.

nickelnine said:
Thanks a lot for putting this together. I was stuck for a day and a half trying to figure out how to flash Magisk with no product partition. Great work.
Click to expand...
Click to collapse
and i was stuck for multiple months...

@kusti420 if I've flashed a GSI on to stock (apart from flashing vbmeta and TWRP) can I fastboot flash that product.img and then successfully TWRP flash magisk or patch with app (using Phh SU temporarily for root) ? is that enough ?
EDIT 1: thought I'd just see for myself, flashed the product_gsi.img and my phone (S20FE 5G) still booted. tried flashing magisk 21.4 zip from TWRP and got a bootloop. will check later if I can patch my boot.img and post.

Hey, where did you take this product_gsi.img? I think it does not work with Android 12, I wonder if it can be updated or something like that.

felipecassiors said:
Hey, where did you take this product_gsi.img? I think it does not work with Android 12, I wonder if it can be updated or something like that.
Click to expand...
Click to collapse
it was sent to me in telegram, where i also traced it back to @Allexwin50, afaik he made it. worked fine on android 10 and 11. asking him for img for a12 could be an option

Sir, When I Flashed any GSI rom A11 , any way to remove the standard superuser root from rom ? if some solution , please advise me , (my device use fastboot commands not use twrp)

gamal001 said:
Sir, When I Flashed any GSI rom A11 , any way to remove the standard superuser root from rom ? if some solution , please advise me , (my device use fastboot commands not use twrp)
Click to expand...
Click to collapse
idk wtf u mean by "standard superuser root" prolly phh su, if yes then there is definetly a way to get rid of that

Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.

K1569GHENT said:
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
Click to expand...
Click to collapse
maybe, cant remember by heart, dont have enough time to test it out myself

Working on Nippon Android Tiramisu SGSI on Pixel 3a, very nice

K1569GHENT said:
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
Click to expand...
Click to collapse
Obtain a stock copy of your boot.img.
Patch it through the magisk app before you do your whole thing installing your chosen gsi.
Once you have the patched image, you can fastboot it using fastboot flash boot boot.img in cmd onto your gsi ROM.
Make sure to install the boot.img to both slots A and B. Then go back to your active slot.

ninjasinabag said:
Obtain a stock copy of your boot.img.
Patch it through the magisk app before you do your whole thing installing your chosen gsi.
Once you have the patched image, you can fastboot it using fastboot flash boot boot.img in cmd onto your gsi ROM.
Make sure to install the boot.img to both slots A and B. Then go back to your active slot.
Click to expand...
Click to collapse
he talked about removing phh-superuser

kusti420 said:
he talked about removing phh-superuser
Click to expand...
Click to collapse
It's locked to your boot image, so using 100% stock image removes superuser since it's no longer system as root.

kusti420 said:
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/...ynamic-super-partition.4256667/#post-85271987
If youre on stock before flashing GSI then dont "fastboot delete-logical-partition product" like other tutorials may suggest. Just flash the product image (fastboot flash product [insert img here]) attached below and it will get resized automatically as well, giving you plenty of space to flash your GSI.
If youve already flashed GSI before following this guide and have done "fastboot delete-logical-partition product" then just create product partition (fastboot create-logical-partition product [size]) and flash the img on product.
whichever course youve taken you can now flash magisk through twrp or patch the boot img and flash that.
Please note that this product image wasnt made by me and the credit for it goes to: @Allexwin50
Click to expand...
Click to collapse
Hello kusti420
I had already deleted the product partition when I found your post.
The GSI was not cool.
I reflash the product partition and reflash the GSI, now it's good.
Thanks for the file and the tip.