New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OnePlus 7 Series Firmware Issue Fun #167
Comments
The newer firmware for OP7 may no longer support locking like is known on OP8 and OP9: https://calyxos.org/news/2022/07/06/oneplus-android-12-relock-issue/ |
I also have the same update issue on guacamole. |
There are two issues here: The first is being unable to install the update, I received a log for this:
Which shouldn't happen: https://review.lineageos.org/c/LineageOS/android_hardware_oplus/+/340515 The second issue is that the new 12 firmware likely did remove relock support.
|
you can |
Personally I think the second option is preferable |
Well, the Oneplus 7T is EOL anyways. The firmware will quickly become outdated/insecure as well. So I guess the question is whether there are any serious vuln that has been fixed between March (which was previously included in the October build) and August. |
New 19.1 builds are up for OnePlus 7 series with firmware removed so users can choose. Firmware is still included on OP8/9. |
What about the 20 builds? |
I'll compile 20.0 with firmware removed another day. |
Oh, and I wonder if you have the firmware for the OP7T posted somewhere or should I go ahead and extract it from the stock OS myself? |
I'm re-opening this. I just received a report of non-functional touch/screen on guacamole 19.1 with A11 firmware. A12 firmware may actually be required. I've added some warnings here: https://divestos.org/index.php?page=news#2022-11
|
Ah fun. Divest 20 runs just fine on my 7T with the Android 12 firmware. |
so with the bootloader unlocked? |
I've pulled all the OP7 series builds. Any users who upgraded to yesterday's 19.1 builds with A11 firmware installed and have no touch screen should flash A12 firmware if they are unlocked. Otherwise they can unlock, flash the previous build, and restore from backup. Old builds are available here: https://divestos.org/builds/old/old.txt I will fix the flashing issue and include A12 firmware back for the next builds. |
so if i understand correctly, all op7 users have to unlock their bootloader ? |
Yes |
New builds are uploading: https://divestos.org/index.php?page=news#XXXX-XX |
I didn't read the update instructions. My 7 pro is not locked. Touch is not working since the update last week Wednesday. I did wait until battery was empty and device shut down itself. Holding Power loooong time did not work. Shut down happened today :) Maybe there is another solution to power it off? PS: adb devices -> unauthorized |
@hbarthel fix your adb, to access fastboot use volume up + power, to access recovery use volume down + power also to force most modern devices off can usually use volup+voldown+power, and next time don't wait a week before asking for help 😉 |
Thanks a lot. PS: they have the wrong keys: https://wiki.lineageos.org/devices/guacamole/#special-boot-modes |
@hbarthel |
Can we sum up this thread? (I ran into the no-touchscreen issue with my OP7 Pro upgraded from Resurrection Remix (Android 10) to Divested 20, then Bricked it, got OOS11 running, with the locked-only bootloader, den MSM-Tool downgraded to OOS10 (Android 11) and unlocked the bootloader) What is the current recommended way to install Divested 20 on Oneplus 7 pro?
|
@bbczeuz |
@SkewedZeppelin Thanks. Works smoothly. (Had some issue with fastboot install getting stuck; switched USB ports and problem solved) Procedure: Use MSM Tool to install OOS10 (A11), Unlock bootloader, flashboot Divestos, sideload Divestos, works |
My touchscreen did not work on slot a (but on slot b) after the first installation. I re-did the installation and re-formatted /data multiple times, after then it works now on both slots. Is there an easy way to restore locking-support? |
@Tecol87
You cannot simply just downgrade the firmware, you have to downgrade the kernel and the vendor blobs to match it which is non-trivial. |
@SkewedZeppelin |
I tried updating from the October build to the November build, and it failed to apply the update. I then proceeded to unlock the bootloader, adb sideloaded the November build, and relocked it. It's soft bricked and gave "The current image (boot/recovery) have been destroyed and cannot boot". Maybe it wasn't signed properly or the firmware changed?
It does boot just fine with an unlocked bootloader.
The text was updated successfully, but these errors were encountered: