Cannot update OOS - OnePlus 7 Pro Questions & Answers

Hi everyone, this is my first post here on XDA but i'm a very looong passionate of this forum.
Recently my loved one plus 7 pro has experience some weird mic issues so I changed the motherboard and this resolved every problem.
But now I'm experience some really strange software issues, I'm able to flash the stock OOS but I can't upgrade OOS, I always get a "signature verification failed" or when I'm able to pass the verification (by downloading many times the update) the update fails, only once I was able to update. The firmware, flashed with msmdownloadtool, works fine. The problem is that often many app crash and the ui reboots randomly. I've also tried to install pixelexperience ROM but it's the same with the apps, the continue to crash, I always clean flash everything.
Do you have any idea why app continues to crash?

Related

Random Reboot on Lollipop 5.1

Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
The_Wolf91 said:
Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
Click to expand...
Click to collapse
Flashed Android 5.0.1 and no random reboots (as I also said when i wrote my first post).
I don't know if the "question" is clear, but can you help me reading the "last_kmsg" which I attached in first post? Thanks
Same exact thing happening to me also.
Sent from my Nexus 5 using XDA Free mobile app
The same is happening to me. And it looks like a hardware problem cuz when the phone reboots it keeping reboot until I keep pressing the power button while boots.
I have a bad experience about it. In my Nexus S when updates to Jelly Bean the same occurs until phone suddenly die. (I live in Brazil so, guess what? I have now a wonderful paper weight)
No luck with 5.1.1
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Try another (custom) kernel.
beekay201 said:
Try another (custom) kernel.
Click to expand...
Click to collapse
I just flashed ElementalX kernel but no luck, random reboot happened on 5.1.1 too. By the way it was quite obvious because it happened already on 5.1 Google's factory image (stock kernel so)..
I have exactly the same issue with nexus 5 since upgrading to 5.1.0.
I went back to 5.0.1, which solved it for a few days, but now this happens with 5.0.1 as well.
also, before random reboots happen, the power button becomes extra sensitive, so one keypress causes the screen to turn on and off again, or to display the shutdown menu.
this does not happen when the phone is stable.
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Sent from my Nexus 5 using XDA Free mobile app
noob424 said:
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Click to expand...
Click to collapse
Same here.
LG Nexus 5 - Lollipop 5.1.1 LMY48B
Unlocked bootloader;
Rooted;
ClockWorkmod 6.0.4.5 (not flashed - just boot on image when used);
Wipe factory reset (in cwm). Flashed 5.1.1 image files (boot, radio, bootloader, system and cache).
Random reboots, and sometimes with apps optimizing.
I have the same problem with N5 since upgrading to 5.1.1 - never had any problems before. Doing it several times an hour now. Trying a cache clean next, after I wait for the optimising apps to finish yet again!
Hi all,
I had the same problem. Everything stock, up to datÄ™, no root. Phone was rebooting itself several times in a row.
Right now it seems that problem dissapeared. Reboots in my case was caused probably by application Autoguard Dash Cam Blackbox. After removal no reboots for 2 months and no memory leak.
cleared cache and it happened again within a minute...
Does seem to be linked to the power button
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
simbapenn said:
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
Click to expand...
Click to collapse
I have N5 kit kat 4.4.2 in Chrome watching videos randoms reboot its happens
This is happening to my fiance's N5. It happens when she's using it and also when it's not being used. When it reboots, it optimizes the apps and says the battery is at 0 when it was a full charge. Only way to turn it back on is to connect it to a charger. Frustrating.
FYI the update to 6.0 did not solve the restart problem. It's either hardware related, app related or a bug that's still in the OS.
I'm selling my Nexus because of this, has been happening for a few months now.
It's not software related, it has to do with the actual power button. Some people had success changing it out, soldering it etc., but I don't have that time or knowledge.
Google wouldn't help, as I'm out of warranty. So I guess it's goodbye Nexus. Really unfortunate given that the phone works fine, it's just a quality issue.. will have to re-evaluate buying another Nexus in the future.
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
---------- Post added at 04:41 PM ---------- Previous post was at 04:20 PM ----------
I have been using this awesome app on my nexus 5, just so I don't have to use the power button here is the play store link.
https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree
maccboy2010 said:
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
Click to expand...
Click to collapse
Confirmed the update will NOT fix this issue.

Error "Fingerprint Hardware Not Available"

Anyone else experience this? It happened after upgrading magisk, then reflashing dtbo and re patching with an earlier version of magisk.
Fingerprint gestures still works inside the OS. And when I try to register a new fingerprint, it reads my finger up until the last "read" then throws an error that the fingerprint registration has failed.
I actually have had this error, wifi also stopped working. It's something to do with Flash Kernel and the current way we have to be unlock. If you flash a stock kernel or the modded one with safteynet pass it should go back to normal.
Thanks for the reply, I wiped and started over before I saw your reply. Next time I'll try the OEM kernel first!
Anyone still having the issues with Fingerprint Hardware and Wifi after updating Magisk and flashing a new kernel? I updated Magisk to 15.3 today and also tried flashing Flash Kernel, and I can't get Wifi or fingerprint to work. Have tried flashing back to the Stock+Safetynet Pass Kernel, but still having the same issues.
I just received this error this week.
So, I should just flash stock firmware and it should be good?
Same description: fingerprint won't unlock/verify, but the gestures still work within the OS. Very annoying.
I had to flash a factory image to fully wipe in order to fix this error.
Swiftkey might be the issue
On mine -- Swiftkey was the culprit. Try removing Swiftkey.

OOS camera keep crashing/freezing

I am currently on rooted OOS stable v 9.0.0 with blu_spark v51 and xXx mod. My OOS camera kept freezing/crashing and I have to force rebooted it everytime. Anyone have encountered this problem? Please advise
Try stock kernel, some reported having issues with cam + custom kernel. No idea why not all is affected.
Yes, I'm having very FREQUENT issues where the entire system freezes and locks up and I have to hard reboot. Happens very often when opening the WhatsApp camera (from the photo button in the text field on any conversation) as well as once in the actual camera app, which I've only opened a couple of times since switching over to the phone. It's infuriating really. This is the kind of bug you expect from poorly-made custom roms, not software that is supposed to be a stable, professional release.
This is on a 6T, though, but the software is very close and I've seen numerous people complaining about the same issues on both devices over on the OnePlus subreddit.
And to clarify, I'm running stock except for having Magisk root. This is a problem in stock OOS that OP needs to address.
Same issue here
9.0.2 Pie on OnePlus 6
Rooted with Magisk 17.2
Camera/phone will freeze close to every time I open it
Restart the device and it will open
Can't seem to find much about it on OnePlus forums except for people saying to reset the cache and then closing the thread off
I'm having the same issues...
Any new solutions?
ult1m4tum said:
Same issue here
9.0.2 Pie on OnePlus 6
Rooted with Magisk 17.2
Camera/phone will freeze close to every time I open it
Restart the device and it will open
Can't seem to find much about it on OnePlus forums except for people saying to reset the cache and then closing the thread off
Click to expand...
Click to collapse
rasluht said:
I'm having the same issues...
Any new solutions?
Click to expand...
Click to collapse
This solution in the 6T forum seems to have worked for me: https://forum.xda-developers.com/showpost.php?p=78138000&postcount=3
Specifically, I uninstalled the camera using magisk debloater then reinstalled the version from apkmirror... so far it all seems fine now.
Is the rom flashed in both a/b partition? Some people have solved these freezing issues by flashing on both a and b because they only flash in one partition not both which caused their cams to freeze. Uninstalling the cam and reinstalling could also help
possible fix
my gcam mod and the stock camera crashed always when i opened them, i'm also on xXx rom with custom kernel.
i have nova launcher and when i flashed xXx again, like to update and have nova launcher in xXx profile activated it causes my camera apps to crash. Disable your launcher and try your cameras. Maybe this helps someone.

Camera and Flashlight error in LineageOS 17.1 osprey

So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
atharvvvg said:
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
Click to expand...
Click to collapse
Hello members,
Last week i'v also installed the latest lineageOS version ( 17.1, android 10) Gapps nano, on my Samsung A3 2017. With the TWRP tool., Nice ROM!
Unfortionally with the same issue as above, Samsung and other camera app's very often not working, need to reboot to fix that.
The flashlight does not work either then, and much more irritating BlueTooth not working anymore, my A3 always had perfect connection with my Parrot carkit CK3100.
I'v found in several forum some workarounds for this but these do not solve the issues long enough.
But the issues are also found in older releases from LineageOS.
Will there be a update for these mentioned 3 issues?
If not, i need to install another ROM which is not based on LineageOS.
The Cam and BT must work without any problems.
Thank you very much.
Frank.

Cant rollback from OxygenOS 12 to 11

Hi, I have this super-weird issue - my OOS got update to v12 and since then weird things happened:
It started to suddenly and immediately turn off and I couldnt do a thing. I did hard reset and noticed that turning on Gooogle Assistant (or using the mic at all) caused these resets. So I didnt activte Assistant. Unfortunnately, this caused my mic not to work at all.
So i have given up and decided to revert to previous rom - v11. Unfortunately, that is everything but simple:
I have downloaded ROM for EU from here oneplus site and tried both OP local update tool and this weird app named my application2. Both dont seem to work and im not sure why, I checked like 5 different ROM versions and I am kind of stuck. OP Local prompts me that I cannot install lower version of package than currently installed and this other app throws me pop up with this message: "Verification failed". I tried to google it and checked here on forum and I cant find similar thread.
Could anyone help me out with this?
I just went through this. I downgraded from 12L to 11. For some reason some of the roms do not want to be used by the local upgrade app. I used a different one from the one I will direct you to and it said that I couldn't downgrade. I just had to find the right one. Go here: https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3930585/
Under "signed flashable zips" in the op, click "click to show content". I don't know which one you need global/India or Europe. I specifically used the global/India OnePlus7ProOxygen_21.P.41_GLO_0410_2112101753.
Use the local upgrade tool app. Downgrading will completely wipe your phone. So, make backups of your backups. If you root your phone, make sure to freeze the System Update app to get rid of the annoying update notification. So happy to have root/twrp back.
Thanks, unfortunately I have rolled back to OOS 11 and it didnt solve a thing - i keep seeing this lightning symbol and phone turns off even on full battery, I cant make phone calls because any use of mic turns off the phone immediately and I have no clue what to do next with it.

Categories

Resources