[SUMMARY][PIE GSI] BEST PIE-GSI ROMS to TRY (to this moment)

Which GSI Pie-Rom do YOU prefer ?

  • Havoc

    Votes: 51 28.3%
  • Benzo

    Votes: 12 6.7%
  • PixelExperience

    Votes: 27 15.0%
  • LOS16 PPR2

    Votes: 22 12.2%
  • Arrow

    Votes: 10 5.6%
  • ---

    Votes: 58 32.2%

  • Total voters
    180

joaste

Senior Member
Sep 11, 2011
878
250
83
If you have a vendor partition you dont need to create a new one (reagardless within system or data/ NFounds uses data and LOS uses system).
But flashing the vendor.img/boot like v1.1 Nfound is necessary when you wipe everything even if you have a vendor partition. It's just 'the' place for the vendor, right.
To give you an example, the LOS16 thread mention a creation of a vendor partition. After that you can flash the LOS16 which contains the vendor, system and boot together. So that's an ''all in one'' flash.
Not so when you wipe everything, you have to flash whatever vendor you want, like V1.1, Dotos, Kranoners....so you do need a vendor.img/boot flash for our axon 7 to presume furtheron with a GSI of your choice.
Otherwise it won't work ;)
Btw, you could only wipe system, data, cache and leave the vendor. That's a method too of course. But like said that is totaly up to you which combo you would like to test. Mine is given above.
So to summarize, you need a :
Bootstack
Vendor creation partion (either created by for example LOS or djkuz vendor partition, Oki's tool...)
Vendor/boot img (either within a rom like LOS16, Dotos or seperate like V1.1)
System.img gsi (either with or without gapps)
....rest is up to you

Hope that clears something out.
And btw, as long as your phone isn't falling apart, this precious one is unbrickable ;)
Thanks a ton! I finally got it up and running. I was using another vendor from telegram that was just not working.

I do notice however that it gets hot when charging. Have you found the same thing? In addition, when the theme is set to black, the notifications come out completely black and text is not readable.

Otherwise it is quite nice and fast. I'm curious to see about battery life.

Thanks again for your help!

EDIT: I also have a message at every boot "Vendor image does not match the system...."
 
Last edited:
  • Like
Reactions: raystef66

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
Thanks a ton! I finally got it up and running. I was using another vendor from telegram that was just not working.

I do notice however that it gets hot when charging. Have you found the same thing? In addition, when the theme is set to black, the notifications come out completely black and text is not readable.

Otherwise it is quite nice and fast. I'm curious to see about battery life.

Thanks again for your help!

EDIT: I also have a message at every boot "Vendor image does not match the system...."
This boot message can be ignored. Most of Pie had/have it. Either ''ínternal memory'' or ''vendor issue''.... so just ignore
I have dark theme running with red accents and all is very clear on my part. Black can give some issues on text appearance. Do try a bit.
No heating at all on charge - btw, is your battery in good condition - perhaps check Accubattery and do a couple of cycles.
Which bootstack etc. did you use ? Same as my setup ? Otherwise it won't be comparable.
Btw for some more reliable data...:highfive:
 
Last edited:

joaste

Senior Member
Sep 11, 2011
878
250
83
This boot message can be ignored. Most of Pie had/have it. Either ''ínternal memory'' or ''vendor issue''....
I have dark theme running with red accents and all is very clear on my part.
No heating at all on charge - btw, is your battery in good condition - perhaps check Accubattery and do a couple of cycles.
Which bootstack etc. did you use ? Same as my setup ? Otherwise it won't be comparable.
Btw for some more reliable data...:highfive:
Thanks.

I'm on the B20 bootstack. I just tried again after installing the Darkmode fix, but still no go when the theme is set to black (notifications are black, except for the Google logo in the left of the notification - text does not appear). When the theme is set to Dark or Chocolat, the notifications are white and text appears fine (but I don't like the white notifications).

I tried flashing the System Settings color accents fix, but this caused the ron to no longer boot. I had to reflash the system image.

Do you think this could be related to the bootstack ( I assume not but, ...)?

EDIT: I'm already member of the telegram group ;)
 

runninghamster

Senior Member
Dec 30, 2017
406
334
73
Melbourne
Hey guys! Just to dive further into Pixel Dust GSI, here's my results from testing for 24 hours. Pixel Dust is a great GSI, and it works absolutely flawlessly. Everything that @raystef66 mentioned is the same, and everything works. I used a different setup from him, to test whether or not it was the rom or the setup Raystef was using that was getting him 7 hours SoT.

*B20 bootstack from Verequies* - Just providing a link, not created by me whatsoever. This is a modified version of @DrakenFX 's B20 bootstack.
*Vendor from latest DotOS* - from Mike, SaintZ93 . Thanks for providing vendor from your DotOS build.
*Schwifty 5.8* - This is from the Schwifty Telegram group, it is an unofficial version. Join the group to get it, I won't be providing link as I don't have permission.
*NFC / Hotspot Fix* - from Raystef and kountry83.
And the rest is just Pixel Dust GSI, and Magisk 17.3 .
From my results, you can see that I got 6h of SoT, and this is actual SoT, not estimated. I also had Bluetooth on and playing music with Spotify for 1.5 hours during this time. Without bluetooth, this would have been closer to the 7h Raystef was talking about.
Thanks for your time reading this. :)
 

Attachments

Last edited:

joaste

Senior Member
Sep 11, 2011
878
250
83
Hey guys! Just to dive further into Pixel Dust GSI, here's my results from testing for 24 hours. Pixel Dust is a great GSI, and it works absolutely flawlessly. Everything that @raystef66 mentioned is the same, and everything works. I used a different setup from him, to test whether or not it was the rom or the setup Raystef was using that was getting him 7 hours SoT.

*B20 bootstack from Verequies* - Just providing a link, not created by me whatsoever.
*Vendor from latest DotOS* - from Mike, SaintZ93 .
*Schwifty 5.8* - This is from the Schwifty Telegram group, it is an unofficial version. Join the group to get it, I won't be providing link as I don't have permission.
*NFC / Hotspot Fix* - from Raystef and kountry83.
And the rest is just Pixel Dust GSI, and Magisk 17.3 .
From my results, you can see that I got 6h of SoT, and this is actual SoT, not estimated. I also had Bluetooth on and playing music with Spotify for 1.5 hours during this time. Without bluetooth, this would have been closer to the 7h Raystef was talking about.
Thanks for your time reading this. :)
Thanks for the info.
Am I correct that to get the dotos vendor partition, I have flash the whole rom, then flash the pixeldust gsi?
 

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
Thanks for the info.
Am I correct that to get the dotos vendor partition, I have flash the whole rom, then flash the pixeldust gsi?
You can ( but wipe system/data/cache again when you flash the GSI) but you don't have to if you have the extracted vendor/boot from @SaintZ93 - I could upload it but leave that to him beacuse he made one for us. Look into our TG for the time being since he didnt uploaded it yet. Just flash that and you'll have the vendor/boot setup to work on.
 
Last edited:

joaste

Senior Member
Sep 11, 2011
878
250
83
You can but you don't have to if you have the extracted vendor/boot from @SaintZ93 - I could upload it but leave that to him beacuse he made one for us. Look into our TG for the time being since he didnt uploaded it yet. Just flash that and you'll have the vendor/boot setup to work on.
Thanks for the quick reply raystef66.

I bit the bullet and decided to clean flash everything, starting with the B20 from Verequies, the DotOS ROM, Schwifty 5.8 and then the Pixeldust gsi.

I'm setting everything up as I type this. Phone is charging at the same time and is already quite hot...
 

SaintZ93

Senior Member
Feb 4, 2011
1,518
4,682
153
27
Massachusetts
github.com
You can ( but wipe system/data/cache again when you flash the GSI) but you don't have to if you have the extracted vendor/boot from @SaintZ93 - I could upload it but leave that to him beacuse he made one for us. Look into our TG for the time being since he didnt uploaded it yet. Just flash that and you'll have the vendor/boot setup to work on.
Here is a latest Vendor I made, all you have to do is make sure System & Vendor is selected before flashing.

Link: https://www.androidfilehost.com/?w=files&flid=285717
 

ramnkc

Senior Member
Jun 6, 2005
354
38
0
Hey guys! Just to dive further into Pixel Dust GSI, here's my results from testing for 24 hours. Pixel Dust is a great GSI, and it works absolutely flawlessly. Everything that @raystef66 mentioned is the same, and everything works. I used a different setup from him, to test whether or not it was the rom or the setup Raystef was using that was getting him 7 hours SoT.

*B20 bootstack from Verequies* - Just providing a link, not created by me whatsoever. This is a modified version of @DrakenFX 's B20 bootstack.
*Vendor from latest DotOS* - from Mike, SaintZ93 . Thanks for providing vendor from your DotOS build.
*Schwifty 5.8* - This is from the Schwifty Telegram group, it is an unofficial version. Join the group to get it, I won't be providing link as I don't have permission.
*NFC / Hotspot Fix* - from Raystef and kountry83.
And the rest is just Pixel Dust GSI, and Magisk 17.3 .
From my results, you can see that I got 6h of SoT, and this is actual SoT, not estimated. I also had Bluetooth on and playing music with Spotify for 1.5 hours during this time. Without bluetooth, this would have been closer to the 7h Raystef was talking about.
Thanks for your time reading this. :)
not sure what went wrong, after i flashed pixeldust and gapps it booted fine until i need to setup wifi and etc... keyboard is not there for me to key in anything except voice input... probably need to reflash eveything again. :(

WTF, i know what causes it... i flashed gapps again and causing google keyboard missing... which i found out pixeldust already included gapps which i doesn't need to flash again... stupid me :(

And again, i'm not sure why i couldn't connect to my home hidden SSID.... how do i capture logcat on that?
 
Last edited:

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
I can't get Magiskhide Props Config working. Getting the error message "props not found" in Termux. Other modules work fine.
B12
Nfound treble 1.1
Pixeldust
Magisk 17.1
Is your MagiskHidePropsConfig module up and running ? The latest ? https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Also use Terminal app : https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=nl
And try again. Should work though...

Btw, same setup as yours ;)
 

Attachments

Last edited:
  • Like
Reactions: JKSurf

ttkian

Senior Member
Feb 4, 2017
89
41
18
I can't get Magiskhide Props Config working. Getting the error message "props not found" in Termux. Other modules work fine.
B12
Nfound treble 1.1
Pixeldust
Magisk 17.1
I am guessing that your basicintegrity is false? I had this experience twice, the only way I got it fixed is by flashing Los 15.1 bootstack. Or, any newer bootstack might do too.
 
  • Like
Reactions: JKSurf

bedroidapp

Senior Member
Jan 14, 2014
62
14
8
HOW TO...
Round Trip from NOUGAT or OREO to PIE GSI
OK, the full instructions to go from Nougat or Oreo to Pie, and back, would be:

Prerequisite

Bootloader Unlocked Axon 7

Install tools and configuration
1. Install TWRP Labs Mod Custom Recovery. Use the B12 version in case you are currently using Oreo encryption. Reboot to recovery.
2. Open the PARTY tool under Advanced > Oki Labs. If you do not have vendor partition you need to create one. Use the default configuration (System, 512MiB, at the end). Accept to reboot recovery. If the vendor partition is there, then just leave PARTY tool and continue with the next step.

Backup your daily driver config:
3. Go to the EDL Backup tool under Advanced > Oki Labs and create the Backup zip choosing FULL. If something goes wrong you will be able to restore your device using TWRP or MiFlash
4. From the Main Menu, backup your Data partition to the External SD.
5. Backup your Internal Storage using the option under Advanced > Oki Labs (Check the available space, the tool is not yet checking for available space, I will add it this weekend)

Prepare Treble configuration:
6. From TWRP Install the special B12 Bootloader with enabled EDL key combo support (The Universal Bootstack leads to DFU mode) and the modem for your region.
7. From the Main Menu, Wipe Vendor
8. Flash Axon 7 Treble ROM v1.1

Flash GSI package:
9. From the Main Menu, Wipe Dalvik / Cache / System / Data
10. From here you have to follow the installation instruction for the Generic System Image (GSI). Usually it is a single img file. So go to Install, press Install_Image button and navigate to the GSI file to flash it. Then just reboot. Some images would require additional ZIPs such as GApps or recommended patches.

Here you test the Pie ROM. If you want to test another Pie ROM you can try just going back to step 9. However, to ensure everything is clean you should start in step 7.

Return to your Daily Driver Config
11. Boot Recovery and flash the backup EDL ZIP you created in step 4. If you bricked your device just extract the contents of the file in your HD, Boot your phone into EDL mode, and use MiFlash. This step restore your original bootstack, modem and OS.
12. From main menu restore your Data partition
13. Go to Advanced > Oki Labs and restore Storage.
14. If you had to create the vendor partition in step 2, just run the PARTY tool again to remove the vendor partition.
15. From the Main Menu, Wipe Dalvik / Cache and reboot to system.
the link "special B12 Bootloader with enabled EDL" is dead.
And i understand that flashing treble 1.1 is not required anymore, at least if we are on lineageos15.1?
i used the oki labs edl 1.3 to easily install lineageos 15.1 from scratch, but i cannot find what bootstack it comes with :(
 
Last edited:
  • Like
Reactions: Raffelberger

DJ_Geert

New member
Nov 19, 2018
1
1
0
PixelDust Rom

After some tries i have found this set-up. Los 15.1 Bootstack v2 / TWRP 3.2.1-8 Treble NFound / AOKP vendor / NFC fix / Jojoc tweak 2.1 / Universal Safetynetfix v3. Works flawless for me. I have a G version. No problems with black menu setting (all text is visible) and Magisc installs fine. Great battery life. PixelDust Rom is the best.
 
  • Like
Reactions: amphi66

runninghamster

Senior Member
Dec 30, 2017
406
334
73
Melbourne
the link "special B12 Bootloader with enabled EDL" is dead.
And i understand that flashing treble 1.1 is not required anymore, at least if we are on lineageos15.1?
i used the oki labs edl 1.3 to easily install lineageos 15.1 from scratch, but i cannot find what bootstack it comes with :(
If you have LineageOS 15.1 running currently, then you are using the LOS B12 bootstack. This can be found in original post of LOS 15.1 .
Also, if you are running LOS 15, then you don't need to flash Project Treble v1.1 .
 

bedroidapp

Senior Member
Jan 14, 2014
62
14
8
If you have LineageOS 15.1 running currently, then you are using the LOS B12 bootstack. This can be found in original post of LOS 15.1 .
Also, if you are running LOS 15, then you don't need to flash Project Treble v1.1 .
Thanks. I flashed dotos vendor instead anyway and pixeldust. Works great so far
 

pingouin47

Member
Sep 28, 2012
46
21
0
Hey guys! Just to dive further into Pixel Dust GSI, here's my results from testing for 24 hours. Pixel Dust is a great GSI, and it works absolutely flawlessly. Everything that @raystef66 mentioned is the same, and everything works. I used a different setup from him, to test whether or not it was the rom or the setup Raystef was using that was getting him 7 hours SoT.

*B20 bootstack from Verequies* - Just providing a link, not created by me whatsoever. This is a modified version of @DrakenFX 's B20 bootstack.
*Vendor from latest DotOS* - from Mike, SaintZ93 . Thanks for providing vendor from your DotOS build.
*Schwifty 5.8* - This is from the Schwifty Telegram group, it is an unofficial version. Join the group to get it, I won't be providing link as I don't have permission.
*NFC / Hotspot Fix* - from Raystef and kountry83.
And the rest is just Pixel Dust GSI, and Magisk 17.3 .
From my results, you can see that I got 6h of SoT, and this is actual SoT, not estimated. I also had Bluetooth on and playing music with Spotify for 1.5 hours during this time. Without bluetooth, this would have been closer to the 7h Raystef was talking about.
Thanks for your time reading this. :)
Testing with same setup as you, but without Schwifty. All is working very well :)
Battery drain seems very good too. I'll check tomorrow after full charge.

Is someone found a good app camera without flash delay problem ? Open camera from Play Store give withe picture in low light situation with flash
 

Mousman

Senior Member
Feb 21, 2011
62
5
0
So I just moved to PIE and I have two issues as of now one is that after every reboot it says that there is an internal problem and the other one is that the swapping of back and recent is not working, the flashable zip nor the Havoc 2 option, did someone managed to swap the HW keys?
 

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
So I just moved to PIE and I have two issues as of now one is that after every reboot it says that there is an internal problem and the other one is that the swapping of back and recent is not working, the flashable zip nor the Havoc 2 option, did someone managed to swap the HW keys?
The ''internal problem'' is not a problem, ignore that. It's on many Pie.
Flash the A2017X_softkey_reverse_DF!NR but mount system&vendor before you flash. Tested that on Havoc too ;)
 
  • Like
Reactions: Zobat