-
Following on from this thread, I have acquired two of the above devices. One was going to be my "new" phone for Android as my other device was failing, so it was on Android 13. The other has a smashed but functioning screen...
So let us try installing Ubuntu Touch... I downloaded the Android 11 (required) ROM to downgrade from Android 12 and 13 from here and followed the downgrade instructions to the letter, so both devices went back to Android 11.
After Android was setup again, unlocking the bootloader involved booting to the bootloader (fastboot mode) which unlike Qualcomm, you have tiny writing indicating you are in fastboot mode. I used windows so the command was ./fastboot flashing unlock. The difference is the device seems unresponsive afterwards. Just switch it off by pressing power+volume up+volume down together till it turns off. Wait a few seconds and then power on and set up Android and again enable Developer options.
I will then use bold capitals to make a point:
FOLLOW THE INSTRUCTIONS ON THE INSTALLER - THERE IS A DROP DOWN BOX WHERE YOU CAN SELECT 16.04 DEVELOPER, 20.04 DEVELOPER AND 20.04 RELEASE CANDIDATE.
Install went through, however i ended up in a reboot loop or boot to recovery.
If it reboot loops, power off the device and power into fastboot mode, but this time you have to manually select the device from the installer drop down box, then run the installer again and Leave the WIPE DATA box unticked. It should boot into UT.
If it boots into recovery go into factory reset and wipe cache, got to advanced and mount system then reboot the system and it should boot into UT.
On one device it took three uses of the installer to work this out and get a successful install.
So 16.04 works, yet to fully try it out.
20.04 Developer and Release candidate - no ADB and you will lose your IMEI so no phone - it is still there as I dropped to 16.04 and both where present.
Disclaimer.
As @Moem pointed out this is a far from complete port so I wouldn't do this on a daily driver and be prepared for an Android recover scenario.
-
I have this device as well and tried improving the 20.04 port but no avail.
The IMEI is not lost, it is just that ofono crashes and SIM relates functionality does not work.
When you install 16.04 it works again, in fact I used it as a daily driver for more than a year.For me the first install went butter smooth.
OnePlus devices are easy to work with in general, easy unlock, BROM mode for hard brick recovery (mediatek only), etc.
For some reason hard brick was in warranty and had free service after messing with the preloader. -
@ikoz Many thanks for the work. I have them both on Xenial at the moment. I don't have the skillset to further these devices unfortunately.
As for the IMEI disappearing, I assumed (never assume) that something like that was the case, so no panic.
I don't know why my installs didn't quite go to plan, but figuring it out and then seeing UT running made it worthwhile.I am a big fan of the OP devices, quality hardware and a pretty straightforward install the vast majority of the time and I would personally award them a medal for making the bootloader not a chore to unlock!
-
K Keneda moved this topic from Devices on
