My suggestion is that you purchase an OTG (bout $10++) then place any ROM inside. After that, flash it on your phone through TWRP. If that doesn't work and somehow your partitions are all messed up, there's always the unbrick method here...
The full screen gestures are partially working. Swiping left/ right to go back is not working. Swiping up to home works. I implore you to keep gestures and maybe have them working? My physical buttons are not functioning correctly anymore :crying:
I believe the OP states "Flash cepheus-user-10-QKQ1.190825.002-V188.8.131.52.QFAEUXM-release-keys firmware" and you're flashing the wrong firmware which might be the result of you being required to flash vbmeta. Maybe markakash can chip in? :cowboy:
I've been reading past the last 10 pages or so and saw people mentioning about the latest build of 7.3.1 is fairly usable and unstable at the same time.
There were users reporting of camera & flash not working on builds before 7.3.1. I will like to clarify is the issue resolved?
And I have also...
Ok you sound rude but that aside, I am sure there are links to the files just a few pages back.
Secondly, you cannot flash the OTA update through TWRP but you are free to correct me if I'm wrong.
Only the full zip can be flashed through TWRP
Hi I am sorry that you are experiencing this issue.
OOS4.5.1 is basically the cause of your issue. If you opt to flash any other N-based ROM after flashing OOS4.5.1, you are bound to experience screen not responding.
The only way to resolve this issue is if you use any 8.x based OOS; be it...
Sorry but this isn't a hardware issue if you came from OOS 4.5.1
OOS4.5.1 has issues causing users whom flash any other N ROM after 4.5.1 will result in touch screen issues surfacing; it can be in the middle or bottom of the screen depending on your panel.
The only way right now to have this...
Let's start off with something simple.
I am experiencing touch screen issues whereby a portion of my screen is entirely dead.
This happens on any ROM (custom or OOS) that uses the Nougat firmware.
BUT this does not happen on ROM that uses Oreo firmware.
Let's say I am using an Oreo ROM that is...
System was unmounted but issue persisted.
I flash ROM.zip, reboot into system.
Used fastboot to flash blu spark TWRP followed by flashing Blu Spark kernel and SuperSU.
All is working now. No worries. Only downside is I got encrypted again :rolleyes:
Is anyone facing a similar issue as me?
I am flashing the latest Open Beta 17 on my 3T. After I have flashed the ROM.zip, I tried flashing either Blu Spark r201 or SuperSu and I get a white LED.
I have clean flashed (wiping system, data, cache, dalvik cache) to no avail.
All company does this, even google. Just to what degree are their actions and what do they do with the information that they have obtains is where the question marked should be placed at.
There's always another way out of this, live inside a cave with no tech involved :p
I know this topic is a bit old but I just want to add on to what the both of you gentleman has said. Flashing OOS ROM.zip DOES indeed override TWRP with Oxygen's stock recovery and forces encryption (if your device is decrypted). To prevent any encryption or overriding TWRP by accident, please...
Check your display settings, it has something to do with CM/LOS's livedisplay. Look under settings > display > live display (?) OR night mode and turn that off.
Display will revert back to the original colors that you are using to seeing. :)
Yeah the batter is extremely awesome that I pushed over 10hr+ SOT with 30hr+ standby!
THANK YOU SO MUCH maxwen and the entire Omni Team :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Super hyped about this! I've used AOKP since HTC Desire to HTC One X, M8, OnePlus One and now it's on the OnePlus 3T! :D
---------- Post added at 02:16 PM ---------- Previous post was at 02:11 PM ----------
[/COLOR SeanHacker just wanna check with you. Do you...