i had the same problem. red logo and text "Your device is corrupt. It can't be trusted and will not boot". i got this after flashing first HOS beta.
i tried many factory resets and relocking and unlocking bootlader with no success.
at last i reseted the phone with MsmDownloadTool and started...
please share your experience with installation and how well it fits.
does the reviewer use the original silicone case for installation?
i ordered one on amazon but have to wait more then a week until it will arrive.
yesterday i applied the oneplus original tgsp but it cuts the screen of a little...
try this one: https://drive.google.com/open?id=1WyjMQMi3RriWMK19lHA9oUZni7k-vIFs
it`s the latest release from august. source: 4pda
if this also not works, maybe relock and unlock bootloader and then try again. but don`t forget to backup before because it will factory reset the device.
i have the same problem with every custom OOS kernel. stock kernel (clean flash, no custom kernel before) does not have this problem.
i think this has something to do with the wifi driver or power saving features of this. maybe one source commit all devs are using for better battery but which...
eng.stk i very often use whatsapp web but with every oreo oos custom kernel (including yours) it is unusable. i always have to wake the phone to have real time conversations or it will take for ever until the messages are sent / received. i have no wakelocks blocked so this should not be the...
nice too have a way to query security patches. we should do this every 1-2 months to get newer security patch level updates.
with actual security patches i would have no problem without oreo. but hopefully the next update will not take this long. last security patch level was may.
anyone tried magsik beta 14.5? plan to buy this but would prefer magisk over superSU.
what i have read for other huawei devices is that huawei kernels since april 2017 updates should support loop mounting and therefore it should support magisk.
if anyone is brave enough and could try and report...
you are right. whatsapp web client just does not sync correctly with all custom kernel (bluspark, lightning, flash) but works as it should with stock kernel.
maybe they use all too aggresive wackelock blocking configs or there is something wrong with kernel source.
anyone else have connection stability problem with whatsapp on ob1? tried bluspark and lightning kernel and whatsapp web always loses the connection.
battery optimization for whatsapp already turned off but this does also not help.
i did adb sideload with bluespark twrp to OOS 4.5.14. then adb sideload with stock recovery to oreo beta did work with the usual adb drivers.
maybe boot 4.5.14 one time and make a adb connection with authorization before sideload oreo beta. this is what i did with the same problem.
there is i new oreo build from today: https://androidfilehost.com/?fid=673791459329055773
but i`m afraid to flash this on encrypted storage. would this wipe my internal storage or is this compatible with encrypted like Unofficial OmniRom 8?
which one of both?
maybe you could give a helpful hint how to solve lowest brightness. at now it is much too bright for using it in the evening. i have also no apps installed which interact with brightness.
the high cpu usage of big cluster is maybe some incompatibility with ex kernel manager. i...
on latest oreo test build the lowest brightness setting is much too bright.
also cpu big cluster stays forever on 2457MHz which sucks battery like hell.
the rest seems to be really stable. thanks for this first really usable oreo rom for OP5! :good:
could anyone build a new oos cam flashable zip with the new files from oos 4.5.10?
edit: we would need this files:
i`m on AOSiP and just don`t want to flash oos for this files. so if anyone could extract them we could try if it works on AOSiP or RR unofficial by eliminator.
veeery smooth and stable until now! did not find a single bug. :good:
please keep us updated with simple changelogs.
just downloaded 21.08. build and testing it.
if oos cam would work on this rom this would be my perfect daily driver! :)
you are right. it was not very tactful. sorry to the devs who did all the work where TWRP is now. i don`t wanted to be disrespectful.
but i hope with new experienced devs on the OP5 and their input we should sooner see a full working TWRP.
@ topic: there are many questions about data restore...
sorry i thought it is a anykernel issue. with my knowledge i shouldn`t take assumptions. many of us using decrypted because with encrypted storage and the actual TWRPs that are floating around you can get easily in troubles when you do some flashing, testing, backuping and restoring .
my assumption was because he did it for the op3 / op3t also. sooner or later i think we will see a twrp build from him because he don`t like broken things and is the right dev to fix it. but hey ... it was just an assumption. hopefully it will get true! :D
how did you solve the recovery boot loop? i got it also with xXx and stock kernel on a decrypted device.
flashing the no-verity and supersu before blu_spark kernel did not help. i had to restore a nandroid backup to get it working again.