In the meantime I flashed stock rom oxygen 11, let all updates run to oxygen 12 LE2113_11_C.66 which is the latest I think. Again flashing /e/ went throug with no errors but again the touchscreen does not work.
When I use recovery to sideload the os the touchscreen still works. From /e/ os first boot the touchscreen doesn’t work any more, even in recovery.
I flashed a oneplus 9 last year which went well then. I think I used those images:
[e-1.6-s-20221201239247-dev-lemonade.zip] [recovery-e-1.6-s-20221201239247-dev-lemonade.img]
This time I used the latest files. Do you think that might be the cause for the problem? Or is it again something with those other images dtbo and vendor_boot? Any Ideas?
Otherwise I love /e/ on op9, it runs really smoth on the other device I got.
I flashed mine about 2 months ago. Got help from another user and I definitely needed an older boot / vendor image. Since LOS does only keep the last 5 files I wasn’t able to even flash my OP9 with /e/.
If you DM me I could email you download-links. Might be Monday night, though. Am out for the weekend.
Those are Lineage 20.0, Android 13; not good for flashing /e/-s.
If you managed to boot recovery and flash the rom using the older vendor boot etc that should be ok because the new installation comes complete with those files anyway and will overwrite them.
The problem must lie elsewhere.Could be the latest /e/ version you are trying to install, but unlikely. More likely it’s something in the preparation of the device in the first place.
What method did you use to downgrade from android 13? I think MSM would be the preferred method.
I’ve just been looking at my flashing notes which were back in November and see that I had used msm to restore device to OOS 11.2.7.7 then update via ota’s to 11.2.10.10 (at this point I unlocked bootloader again due to previous problems with this device where it would not update to OOS 12 with it locked). Carrying on with ota’s the next was c47 followed by c.61 (big one 1.6GB) followed by a small incremental ota to c.66.
I don’t think you should get sidetracked with that. As I said earlier, each eOS rom has all of those files and they will overwrite whatever is on the other slot when it installs.
Is your phone still at the stage you described above in post #20?
There are things to try, just so long as you know where you are with the phone and don’t get lost with trying other things randomly.
When you first flashed the older lineage dtbo, vendor_boot and recovery they will still be there on the slot that you started the install from.
So if the phone is still in the same state and you can get into fastboot mode you can try changing slot, reboot bootloader, and select recovery: which should be the lineage recovery you started with.
At this point have a rethink. For example, did you sideload copy-partitions file in recovery before doing the factory reset/format data?
I got it working. The problem was that I used an old version of fastboot. I hat to clean up my PC, removed an old copy of the platform-tools wich I probably used without knowing. Then all worked like a charm. Thanks for all the help anyway!
OnePlus 9 with /e/ is such a nice device!
Nope. It’s my daughters device. I myself still use a device with sailfishOS as my dayly driver. Love the concept a lot but I think about switching to /e/.
Ive been having trouble installing this version of /e/ OS, every time i get it installed properly its touch screen doesnt work. The first recovery also shows up as a lineage recovery instead of /e/OS which wasnt expected. I was able to have the previous /e/OS version work fine.
Im currently using the global android 12 stock ROM, i see others seem to be using the EU version, should i be using the EU version as it seems to go up to c.66 while GO stops at c.48?
i find it funny yours works without following the instructions but mine seems to not following it.
Just tried flashing all of those A12 versions in order and got the same thing, interestingly when i rebooted the device it displays a battery with a question mark and then reboots again.
When it was booted it also showed a completely blak battery.
It may not make a difference for your problem but latest platform tools is now r34.0.1.
If you sideloaded or used the oxygen os local update method to install c.36 followed by c.48 you effectively have a basic starting point for flashing custom rom (such as /e/ ) where your device has c.36 on the other slot and c 48 on the current slot.
This could possibly be a problem because when you sideload /e/ it will install to the other slot; i.e. on top of the older c.36.
It may be better to go back to stock like you did before and add an extra step of installing c.48 one extra time so that it is on both slots.
Last question: Is the phone global device LE2155 as bought? If yes, then that’s ok!
i did notice that if i flashed /e/ from each slot one side would fail far worse so maybe. I did use that copy-partition thing first after initial recovery though so i guess that didnt work.
Both sides (including recoveries) dont seem to have touchscreen support.
Im pretty sure i tried that once before though and got the same issue. I will try again and as maybe i messed up another step that time.
It does feel like both sides end up having the touchscreen issue though (after i flash from the failed install, the recovery still ran fine), so i expect ill just end up with both sides with the “working” OS just no touch screen.
Ah. That’s the Chinese variant and will probably need a different approach to restoring it. Good news is that LE2110 is supported device for flashing /e/ though.
My instinct tells me that you should aim to restore Color OS on the device and then update it to the latest Android 12 version of Color OS. I don’t know what numbers these updates would be at the moment.
Best forget about /e/ for the moment and focus on getting the phone back to it’s original state. The xda thread with repo of OOS builds has links to a guide for crossflashing LE2110 to OOS builds. Guess you’ve read it?
I need to do a bit more research and head scratching before offering more solid advice but it would help to know what the msm initial build number is that you are restoring the device to?
A rough plan would be:
Get the ColorOS downgrade build from the xda links
MSM restore as you did before and update to a higher version number than the ColorOS downgrade build.
Install the ColorOS downgrade build and if it’s ok update it on device to latest 12 version OTA (would need to get info about version numbering for this)