My device bootloops after flashing pixel experience+ gsi, do i install just pixel experience gsi. It is a tecno spark 8 shipped with android 11, has treble support and supports A/B seamless updates
Tried just this method with my Lenovo Tablet TB-606F, but bootlooped even after factory reset. Tablet has 700 chip not 800. That may be why it fails.
Jelly 2 won't boot either with a data wipe after install, mediatek MT6771
Are you absolutely sure the phone is 32 bit? If it is 64, then you should be able to run 64 bit GSIs. Or you can try GSIs that have "arm32 binder64" in the name of the img file that you're downloading.i dont know how to post this question so, im going to post it here.i have a tmobile samsung a13 5g. i just found out it's not 64 bit, i have the 32 bit. how do i get a 64 bit of this firmware
Yes I tried to down the flir one app and would not show up in play store. I got in touch with flir tech support and downloaded an app for them so they could see. Took a screen shot and they got back with me saying I had a arm 64 chip but, the firmware was 32 bit.Are you absolutely sure the phone is 32 bit? If it is 64, then you should be able to run 64 bit GSIs. Or you can try GSIs that have "arm32 binder64" in the name of the img file that you're downloading.
it's just very uncommon these days for an Android device to not be 64 bit.
Here is a screen shot.Are you absolutely sure the phone is 32 bit? If it is 64, then you should be able to run 64 bit GSIs. Or you can try GSIs that have "arm32 binder64" in the name of the img file that you're downloading.
it's just very uncommon these days for an Android device to not be 64 bit.
I see now. The cpu is x64 but the OS/kernel only supports 32 bit. This doesn't mean you can't run a gsi though. I may be wrong, but I think "arm32 binder 64" gsi variants are what you need to use. Phh builds his official AOSP gsi with that variant supported, so in turn this means that most gsis based on his source code will support it too. PE is based on Phh sources.
How do I find this rom?I see now. The cpu is x64 but the OS/kernel only supports 32 bit. This doesn't mean you can't run a gsi though. I may be wrong, but I think "arm32 binder 64" gsi variants are what you need to use. Phh builds his official AOSP gsi with that variant supported, so in turn this means that most gsis based on his source code will support it too. PE is based on Phh sources.
Ok I'm sorta new to this Rom/gsi stuff so...... does it matter what gsi I use and, if I'm correct, I have to use twrp? I use to root and install cyanmod roms awhile back so I know about what I'm doing.I see now. The cpu is x64 but the OS/kernel only supports 32 bit. This doesn't mean you can't run a gsi though. I may be wrong, but I think "arm32 binder 64" gsi variants are what you need to use. Phh builds his official AOSP gsi with that variant supported, so in turn this means that most gsis based on his source code will support it too. PE is based on Phh sources.
Well, normally you would find this variant on the page of wherever the GSI's downloads are. I just checked for you...bad news is PE isn't released in "arm32 binder64" variants. It looks like @ponces has chosen to only build ARM64 A/B variants. You can try one of these, if it doesn't work then you'll have to go with another GSI like the official AOSP by @phhusson.Ok I'm sorta new to this Rom/gsi stuff so...... does it matter what gsi I use and, if I'm correct, I have to use twrp? I use to root and install cyanmod roms awhile back so I know about what I'm doing.
Do you know the rom code name of my phone?Well, normally you would find this variant on the page of wherever the GSI's downloads are. I just checked for you...bad news is PE isn't released in "arm32 binder64" variants. It looks like @ponces has chosen to only build ARM64 A/B variants. You can try one of these, if it doesn't work then you'll have to go with another GSI like the official AOSP by @phhusson.
Or maybe if you ask @ponces nicely, he may consider doing builds of the variant you need.
Not sure what you mean by "ROM code name"...
Install this app on your phone too, it will tell you what aspects of Treble your device supports, and what kind of GSI you should be looking for:Check these pages and expand the Assets header of the newest release. Then you will see what I meant by "arm 32 binder 64" and "arm64 A/B":
![]()
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
![]()
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pegithub.com
Probably. After a repeatedly crashing Pixel Launcher, I moved to Nova Launcher which did not crash for this test. However, the bottom gesture navigation died on Nova Launcher.
- This is a pre-release. This is not considered daily-drivable, though your mileage may vary.
- As you'll notice, there is no A-only variant at the moment. It is still undecided whether A-only variants will later appear.
- If you want unshared_blocks/read-write system, use vndklite variants. Non-vndklite devices are capable of running vndklite variants.