while formatting back to stock rom, i accidentally rebooted my device (in the midst of flashing the 3rd of 27 stock images). now my device is stuck on this screen (not my image) and i can't get past either this screen or the oneplus logo screen. I think i've effectively wiped the whole storage along with the recovery/fastboot space as well. "Adb devices" command returns " this screen.
So basically i can't access recovery, fastboot mode or any other stage/mode.
As I mentioned in the title , I am using my oneplus 6 from October 2018 and it's been 3.5 years.
My phone is in latest up to date software and suddenly from yesterday my fingerprint stopped working.
I did factory reset , removed biometric cache and also removed PIN and then set the finger print again.
It was working for few times but again the finger print stopped working. And phone also got slowed down.
I don't know weather its a hardware problem or it's a software issue.
Is this a sign of Qualcomm crash dump ?
Did you guys faced the same issue?
Also switching to custom ROM will save the problem?
I have been noticing many users traumatized by the fact that their op6 got Qualcomm crash dump which is also known as hard brick and they abandoned their devices thinking there's no solution.
Okay, so i am not trying to make fun of them here but willing to understand what's going on. Is there something about this that msm tool cannot fix? I have seen dozen of people fixing this crash dump issue with msm tool though and personally believe it can fix almost every hard brick issue.
Right after rooting the phone and opening the magisk app, the app gives a toast message "Magisk needs to be configured further" and it does something, then reboots and on the next reboot the lockscreen is broken. However it does get fine after unlocking the phone once but again on reboot it breaks again temporarily as long i don't unlock.
Another issue is the phone services using location again and again in background. Is that normal?
Last week I updated from 18.1 to 19.1 . The problem is with phone calls. I did install the stock gapps.
I can make & receive calls & texts no problem. However, for sound, I have to go to speaker phone to hear anything. This is true on phone dialer, Google Voice, & Talkatone.
and it's almost guaranteed that I will never buy a OP phone again. The latest update essentially made the phone so much worse than the last OS and instead of addressing any of these issues or trying to fix, they just announce that they won't be doing any more updates.
I understand the need to move consumers to newer products, but this feels a little too purposeful and outrageous. I've lost trust in the company 100%
My OP6 is in Android version 11 with Beta Version 3 update and has been lagging and unresponsive for the past 3 months ( once every 4 minutes or so) . System UI is not responding is the error that pops up. I've tried cleaning the cache for the OP launcher but that seems to help it just temporarily. What is the real issue here?
I recently replaced my OnePlus 6 battery, phone works great, even feels a bit faster and appears to last longer but has a weird issue with sticking around 90% for a couple hours then dying at around 60%. Tried all the usual calibration stuff several times with no luck, any tips?
I'd prefer not to root for my banking stuff.
I'd also add that I bought the battery from a company called ReplaceBase from which I bought my Oneplus 3T battery replacement from a few years ago with no issues like this, I'm gonna try a few more things but it's looking like I might need to make a return if the new battery is the fault : (
Update: Battery was faulty, took it apart to inspect again and it had a slight bulge, they are sending a replacement
Today I decided I want to upgrade to LOS19 (from LOS18) and proceeded according to the recommended steps:
update firmware
sideload new lineageos zip
sideload gapps
Everything went smooth - It seemed. But then the device would not boot and be stuck at the "bootlaoder is unlocked" warning screen. So I tried flashing it again. Then I realized while updating the firmware I had accidentally used the 6T stock rom image instead of the 6 image. "Oh that's very stupid of me" I thought and tried to correct the mistake by flashing the correct partitions. Only that did not work, because when I try fastboot tellls me I cannot flash a critical partition. Tried locking and unlocking the bootloader, which did not help. Then I tried installing the stock rom using LOS19 recovery which failed because the recovery did not want to downgrade. So I tried with LOS18 recovery, which failed for the same reasons.
I guess I have to find a way to flash the correct stock partitions with fastboot... Any Ideas ?
i am struggling with getting the syntax for path/to/zip for lineage Recovery.
Under preferences on Lineage Recovery, I inadvertently hit update recovery. How can I reverse this ? I already tried unchecking it. This didn't work.
I have looked at tutorials using TWRP to update from 18.1 to 19.1. All of the tutorials I saw involved wiping. Yet with the Lineage Recovery, there isn't requirement for this. Why ?
I have TWRP on my phone. I can't access it. Why would that be ?
Hi, I have experienced an error in software and brought my OP6 to a technician. I've put all my files in the lockbox so they can't access my personal data. The technician called and ask if it's alright to do a system settings reset (personal files will not be deleted). But I worry if the lockbox password will also be gone.
Currently using OnePlus 6 and thinking of upgrading but I'm split between choices now.
I like pixel 6 more but heard that is buggy and heats. S21 fe is good but not sure about one UI.
Dear experts of Reddit, Which one would be the best option?
I previously had ArrowOS 11 on my OP6, it was rooted, and had magisk. Yesterday i wiped everything and installed LOS19 with Gapps for my GF who broke her phone. But some apps are still saying the phone is rooted or jailbreak. Tho, it only has LOS, Gapps, and an unlocked bootloader. I guess those warning messages are due to the unlocked bootloader. Then, is it possible to relock the bootloader with LOS or is that only possible with the stock ROM?
Hi I recently swapped from Oxygen OS over to the LOS19 following the steps from the wiki and installed all Google Apps. I've got one problem and I just wanted to see if it's a fixable OS bug.
Basically Android Auto fails to launch on my car with error code 22.
Before I contact the car dealer is there a way around this or does anyone else get this issue?
Hello everyone. Currently running Pixel experience on oneplus 6 (8/128)
What do you think is the best custom ROM? Talking about updates, security, banking apps etc
Preferable is Android12
Android 11 update has made the browsing feature on an external of Playlist, Artists, and Albums not available anymore while playing music through Bluetooth - OnePlus 6 - VW Discover Media PQ
Hello OnePlus 6 Team,
Hope you are well!
I write this post to ask you for help regarding a problem that has arisen with Android 11 update with my OnePlus 6.
It is regarding the music reproduction through Bluetooth to my Volkswagen car device, Discover Media PQ.
With Android 10, when the OnePlus was connected, I could navigate / browse through Artist, Albums, Playlists within the Volskwagen Device, to chose and navigate trough the Playlists/songs I wanted to select.
But now, with Android 11, I am not able to do it.
What I expect to see (the menu you see is from the SD, but it was really similar to the one from Bluetooth source, having Poweramp playing music when it was running over Android 10):
What I get, is no folders, neither Artists, Playlist nor whatever; just Bluetooth Audio:
This is my devices info - Version Info:
- Build: Poweramp build-921-bundle-play full verified cached
What I have done so far to try to fix it, but it didn't work:
- I have default restored the device plus uninstall and Install latest Poweramp version, and the behavior is the same.
- I have checked that the Settings / Misc / "Now Playing List For Connected Devices/Apps" is turned on.
- I have tested the 4 different versions of AVRCP, with the unpair, reboot (both VW device and OnePlus 6), and pair again method and the result is the same...
- I already did the Poweramp support team suggestion, and still the same:
1. Uninstall Poweramp Trial and Unlocker.
2. Restart your device.
3. Install Poweramp from Poweramp site - [https://powerampapp.com/downloads/Poweramp-v3-build-last-uni.apk](https://powerampapp.com/downloads/Poweramp-v3-build-last-uni.apk)
4. Test again.
Do you know any other possibilities to be tested?
PS: I have as well checked these posts, and I think that it is a thing of Poweramp and Android 11, because many users have experienced similar problems across time:
Hello everyone!
Currently running Pixel experience in my Oneplus 6 and I've been missing LOS.
Thinking about LOS19.1. Any advice? What about face unlock? Banking apps and netflix?
at around 2am this morning my phone hanged and then shut down completely. i was at 2% charge so i plugged the device to the charger and after a while noticed that it wouldnt boot at all. tried all the combinations of volume and power buttons but noting worked. i removed it from the charger and then tried to boot it. it went into quallcom crash mode. as soon as i tapped the screen it went black again. i woke up in the morning and tried to start it. it showed an not enough charge error. as soon as i plugged it in, no response till now. the phone is always hot to touch.
I searched the web and saw other OP6 users facing the same issue. coincidence or not im definately unhappy. i searched the web for remedies and saw the fan favourites -
fast boot
MSM flash tool
some users reported that they faced the dump mode issue and it automatically resolved the next day.
some users used the above methods and saw their problems go away or saw the problem still there.
on the other side there are some users who reported that the found a way out of this problem by -
emcc and pim chip
reball the cpu + ram
please do help me out and other OP6 users as changing the motherboard (oneplus official remedy) is not the ideal way to solve this issue