…Enter suggestions to improve documentation in this category. Do not raise bugs or issues here…
At step 10. :
Press
enterkey on the keyboard to start the sideloading The screen will show the progress percentage…This might pause at 47%
For me it was the end, not a “pause”. I never add step 12. and 13.
Just a message on phone :
To install additional packages, you need to reboot recovery first Do you want to reboot recovery now ? No / Yes
I choose “Yes”
and then “reboot system”
and that was OK for me at reboot. It’s works on /e/
So I suggest :
- Press
enterkey on the keyboard to start the sideloading The screen will show the progress percentage…This might pause at 47% - Give it some time
- on the phone you’ll get a message : “To install additional packages, you need to reboot recovery first Do you want to reboot recovery now ? No / Yes” : choose “yes”
- This means that the install was successful
- select
Reboot system now
Maybe a little more emphasis on the required Android version would be interesting.
Pixel 6 ships with Android 14 by default, so downgrading to 13 is needed.
Hello, some weeks ago I bought a Pixel 6 with Android 16 and I had installed oriole - here my experiences:
The downgrade to android 15 is failed, the zip from google android was out of function. But I thought, the risk of bricking the device is lowly, because the difference between android 15 and 16 is also not high.
I tried it with android 16 and it was successful, the device runs good with oriole.
But I can’t give guarantee.
The installation-guide for oriole is good and helpful. Thanks on the Community!
1 Like
I got a Pixel 6 oriole and started the installation process.
I first upgraded to Android 15. I’m not sure that was the best idea, because after then unlocking the bootloader, the phone won’t boot anymore. It first claims that the system is corrupt, tries to proceed anyway, and then it remains stuck on the Google logo forever.
Any hints to both solve my issue and update the documentation so that no other users get bitten by this?
With caution, I asked an AI agent which told me not to re-lock the bootloader, as one of the partitions was likely wiped. I don’t know if that’s true, but it’s good that it told me that: I was going to try to relock in the hope to get a bootable system again.
In the docs, I’m currently in “Unlocking the bootloader”, step 7. “Since the device resets completely, you will need to re-enable USB debugging to continue.”
I think I need to flash the additinal partitions first. The doc should not invite me to re-enable USB debugging before this step is done.
Another suggestion (adding as edit because the forum tells me I must wait another 30 minutes to post another message…): when following the process, as someone not used to flashing phones, it’s hard to know exactly what we’re doing. Sure, the doc gives us commands, a few keywords, but it would be really nice to include, as an introduction, a summary of the overall process: we’ll first unlock the bootloader, then flash a recovery system, then use that to install, etc…
Hello @stormi, Welcome to the /e/ users forum.
Relocking is not a good idea as it is dangerous and not documented for this device.
but reinstalling a working android 15 based GogolOS with unlocked bootloader is needed at this point.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
1 Like
Are you sure I need to reinstall a stock android at this point? That was already my starting point (well, Android 14, then upgraded to 15 via the official OS updater). I think I should try to flash the additional partitions with the recovery system instead, as the doc says. And simply ignore point 7 from the unlock bootloader stage.
no, all steps are necessaries,
it is hardly stipulate to not continue if a step fail.
and enable “adb” USB debugging is needed for the following…
I can confirm that reinstalling stock Android 15 for oriole (the latest update available for this version, from may 2025) allowed me to then proceed with the rest of the procedure.
Another degoogled phone 
1 Like