Related
OK so I smashed my s5, am a UDP verizon guy and hooked on the open bootloader, so i searched far and wide for another one with the 15 chipset...which I didn't find but I found a note 4 with it.
I bought it and unlocked it and loaded on a rom I loved. (5.0.1 og5). Well...no sense lying here...I was trying to do some less than kosher things regarding my ex's Facebook account with it. In the process I wasn't smart enough to cross check MD5s (a precaution I learned all too well) and opened an app that has me baffled.
It basically hijacked admin on my device completely. No Antivirus program can touch it, though many detect it. "Unknown sources" in my security folder is stuck permanently enabled, and I can't take over as admin on my own brand new note4.
I have tried flashing twrp and titanium backups to no avail, and also tried the safe stock og5 firmware through Odin but it never completes. I am stuck. I have logcat records and all the tools I would think might help, but I can't get rid of it...it seems to have used root and embedded itself into every facet of the device.
I am willing and ready to do anything including a full unroot and stock rom, I just don't want a locked update. Can anyone help me please?
As of now, no roms break it, only the stubborn malware CM app tries to get rid of it, but only identifies it as "suspicious file". My user admin and unknown sources are both locked, and a gaggle of bizarre log events happen constantly, forcing my device into crazy lag. As soon as it happened I received a couple random number-link blank text messages, but I never opened them. I don't have the numbers saved as I've flashed the phone like 30 times since trying to rid myself of this. Aside from the lag and locked unknown sources and admin, and an inability to clear trusted credentials, the phone seems to run normally, though I am scared to use it to log on to pretty much anything. The malware didn't come from a text, but from an app that I knowingly permitted thinking it was something else and I feel like a moron for it. It doesn't seem to have a name. It installed as an untitled app and I couldn't delete it with the root system app deleter, because it put a green bar over the check box in the app. I got rid of it with titanium, but to no avail. It still lurks.
Thanks in advance, and let me know of any screens hits or logs or tests I can provide to help.
At that point, I would recommend using Samsung's Smart Switch for PC program to do an emergency firmware upgrade & initialization. This will download a full copy of the stock firmware for the device (including a few bits that you won't find in stock firmwares available for download through sites like SamMobile) and will erase everything on the device and restore your phone to stock firmware.
If you are in the US and have a Best Buy nearby, you can see if one of their Samsung reps can perform a factory recovery using their SMART tool (which will do the same thing that Smart Switch's emergency firmware initialization will). Officially, rooted devices are not supported and they may rightfully refuse to do this, but it's worth asking if you don't have a computer to use for Smart Switch or don't want to wait.
You will need to redo the developer conversion, but that's the only thing I can think of that will definitely completely restore your phone to stock and eliminate all traces of whatever you installed.
thanks. that solved my problem and got it back to stock, rid of the malware completely. unfortunately, when i tried to return to the rom i had used, everything fell apart for me :/.
So, here's the basics:
AT&T Note 4, Official. Never had issues, never needed to root...
Build MMB29M.N910AUCS2EQF1
June 1, 2017 Security Patch Update
6.0.1
All updates have always come OTA.
Here's the issue:
When the MAY security update come out, I updated like I always do. Since then, my phone started locking up, randomly rebooting, all around pissing me off
I read about having Samsung Experience in Best Buy reapply the update, but our Best Buy no longer has Samsung.
So I went to AT&T to see if they had capacity to do it, nope; just a moron sales-boy who was clueless, just wanted me to pay $225 for my deductible and get an S8 (maybe if they offered the + I might have).
Went to a third party mobile repair and they quoted $35 up front but didn't guarantee they'd be able to 'find the update cause they're in China' (true story).
I've uninstalled apps and reinstalled systematically trying to find a culprit (to no avail).
Tried using Kies and Smart Switch and they both error when I enter the model and serial.
I did a factory reset from recovery and wiped caches, but the problem persisted.
So I installed Wake Lock (darken) and that seemed to tide it and 'cure' the problem.
June security update come out and I installed it. I had to remove and re-seat batteries, restart, pray to my fictitious gods and finally it got to the green App Optimizing and finished.
I removed the wake lock but the problems persisted; so I reinstalled it and that's currently where I am...
I have close to 20 years with computers, but am total n00b with Android.
I see there are the security updates here and downloaded the May and June.
At this point, would applying back to the May update have the possibility of helping even though I've now installed the June?
If so, how? I read you copy it to the root of an SD Card and apply update through the recovery screen, is this correct?
Should I factory reset/wipe caches before re-applying the update?
If I need to re-image the phone (another possible fix I read), what file do I need to use to go about doing that?
At this point, I'd like to A) limp by til the Note 8 comes out and B) get this back up and running so my kids can inherit it for their games when I get the 8...
Any help or direction would be greatly appreciated.
(Just noticed this might be more appropriate in the Help section. Mods, please feel free to move this to the correct sub-section. I can't find a way to delete the post and repost it there...)
I've also posted this on Reddit and the OnePlus forums, but I'm hoping I can find an answer here, too.
Long story short: I really messed up my phone and I'm looking for help getting it to at least boot into the system. Lots of weird, confusing things have happened within the past few days, so bear with me; might be a long story, but I'll try to give you the abridged version.
I run locked and unrooted. I flashed OOS Beta 3 over 4.7.6 on my 5T, wiped my cache, and everything was wonderful for a week. Then one day, I got a system message saying "Bluetooth has stopped". I cleared that and thought nothing of it, but I got another message saying "Bluetooth keeps stopping". This message would actually pop up (with no exaggeration) every second. I could only stop the messages completely after going to the Bluetooth app and clearing the data, then disabling Bluetooth Scanning.
I figured the problem would fix itself, but the next day when I tried to connect to my car via Bluetooth, my phone would freak out again like the previous day. I had to listen to a CD like it was 1996. I thought I could fix the problem with a Factory Reset. As soon as I hit the Welcome screen, "Bluetooth has stopped". When I went to check the Storage section of the Bluetooth app in the Applications list, the app portion read 0 bytes. What? Even when I went into Settings --> Bluetooth and tried to turn it on, nothing would happen. I thought maybe I should revert back to 4.7.4 and start from the very beginning.
That served no purpose. The Bluetooth symbol did show temporarily in the Status bar as I was setting up my phone, but eventually disappeared, with the Bluetooth app once again taking up a whopping 0 bytes. I've done various combinations of installs, but I cannot get Bluetooth to function normally. And at some point, my phone developed a new problem: any time I hit the Bluetooth button in Quick Settings, the phone would eventually reboot on its own. Later, it wouldn't need any input from me at all. It would just be sitting in the Lock screen and reboot.
Icing on the cake: I got desperate, unlocked the bootloader, deleted the system and cache partition in fastboot, then wiped the data in Recovery with the hope that doing a completely fresh install would fix the problem, but at some point my internal storage got wiped and now I have no ROM on my phone to install. Even better: I'm having some real problems trying to install OOS (any version) on my phone via ADB sideload. I keep getting the message "cannot read <filename.zip>", even though it's in the correct folder.
I am currently back on my OnePlus 3 and the proud owner of a very sleek brick. I used to root and unlock Nexus devices and Moto X's, so I'm pretty embarrassed that I managed to ruin my phone while it was running (basically) all stock. It can still boot into Bootloader and stock Recovery. Is there anything at all that I can do to at least load OOS (or any ROM)? Do I have to send it back to OnePlus and beg for a replacement? Will they even take this phone in it's current state? Am I just SOL?
I've run out of ideas and patience. I'm really hoping someone out there can help me. At the very least, thanks for reading my long sob story. Hopefully this never happens to you.
try flash orero based twrp and flahs stock 5.0.3 zip in twrp, see if it works. then figure out the reset.
Why would you delete system from fastboot? Does people not formating partition from recovery more often？
The twrp I use
https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673
Update: I managed to unbrick my phone using an unbrick tool. The process was pretty painless and it will revert your 5T back to OOS 4.7.4 no matter what you did to it. Props to Drasm19 from the OnePlus forums and the geniuses behind this tool! Funnily enough, I was ultimately led back here:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
You guys more than likely already knew about this tool, but definitely keep this in mind if you manage to brick your phone like I did.
Now I'm back to my original problem: Bluetooth is really messed up. This is what I'm talking about:
https://imgur.com/gallery/eEkbX
No matter what I do, no matter how many times I flash any version of OOS, this is always the result. As you can see, even with the toggle in the "on" position, Bluetooth refuses to do what it's supposed to do and the app takes up 0 bytes. Something is up...
I've searched a lot of threads that reference Bluetooth issues, but it looks like I'm the only one with this problem. I'm open to any and all suggestions that'll help me solve this and get back to using my 5T. I already miss those awesome navigation gestures.
Thanks again for your time and help.
im not really a developer type, but a while back it was easy to root and un root with kingo. and i could put things in the system with FX. please bare with me a sec.. p9's i like, but getting some glitches. when the gboard went byby, on reset, i had to set up my welcome screen by shouting at the phone.. 'at sign' does give you @ but to get capitals you have to trick it, eg. 'USA' to get an upper case 'u'
anyway, i got in, and got gboard from 'my apps' ..fine but of course, wont survive another reset.
so about the missing bluetooth.. iv got the directory info. and the missing files. thanks ..but i didnt want to wipe the phone, it seems rooting has become a can of worms.
wouldnt it be nice if there was a nice (no root) app , to run bluetooth from the apps ? so that 'joe blow' doesnt have to throw his phone away, cos it doesnt work in the car ect.. thanks
I have a mate SE (BND-L34) that was on 8.0. Back in September of 2018, I unlocked it and rooted using another thread in this forum. All was working fine until a few days ago when I tried to install xposed using magisk. That bricked the phone. TWRP came up but boot looped. Finally got to the point where my only option was to let it download a stock image through wifi. I did, and then it had a couple updates available, and I let it update to build number BND-L34 8.0.0.352(C567). It also shows android security patch of February 1, 2019. That took the phone back to completely stock. All data wiped, no unlocked warning at bootup.
correction: At bootup, it does still give me the unlocked warning.
So anyway, All seemed to be working and I could add fingers to the list and they will unlock the phone fine. Then I installed an app that could use the fingerprint to unlock it, and I found that it did not work at all. The app waits for the fingerprint to be detected and it never happens. So I tried a different app, and same thing, just waits for the detect to happen. Again, the finger print unlocks the phone without hesitation, every time.
This makes me think that one of the updates is causing a problem. I've done some searching both on xda and google, and come up with nothing. Like no one else has seen this problem.
So I have a few questions:
1) Has anyone else seen this problem?
2) Can I use firmware finder to install a previous build, like the one from January or even the one from September? I don't have TWRP or root, just the stock image.
3) If I can't use firmware finder to downgrade, is there another way? Like through adb or something.
update:
Here's the answer to questions 2 & 3 above:
I was able to use firmware finder to download the January build .351. I couldn't get firmware finder to flash it. I then installed twrp into recovery using the image I found here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500. I followed the steps in this post https://forum.xda-developers.com/honor-7x/how-to/tested-unbrick-bnd-l24-t3811645 to flash the .351 image. I just used the files I downloaded from firmware finder instead of the ones list there.
And since no one has replied, I'm guessing that this problem is mine alone. Also, going back to 8.0.0.351 did not solve the problem.
I finally rolled all the way back to 8.0.0.344(C567) (first Oreo, I think, from September) and now the fingerprint sensor works for applications. I have no idea why. Maybe there was a security update in the Jan build that disabled the fingerprint if the phone was unlocked. But it seems unlikely since no one else saw the same problem. I can't be the only person with an unlocked BND-L34 that let the phone update to the latest ota.
So I have another question: is there any way to stop the phone from looking for ota updates? It's damn annoying to have that "update available" thing pop up every day.
Delete
electric bill said:
So I have another question: is there any way to stop the phone from looking for ota updates? It's damn annoying to have that "update available" thing pop up every day.
Click to expand...
Click to collapse
Yeah, I posted the same thing a month or so ago and ended up figuring it out. Since you are rooted, the same solution I used will work for you. Froze the EMUI System Update process with Titanium Backup.
https://forum.xda-developers.com/hon...ation-t3897144
Welp
It was working, then I tried to install magisk, but it wouldn't install with twrpimgmount_ramdisk.img so I flashed twrp_p10_lite_0.4.img and then magisk 18.1. After that, fingerprint stopped working for apps . I tried re-flashing 344 build, factory resets, different twrp versions, running the magisk uninstall zip, I even re-locked the bootloader. No dice. This phone is back to stock now just the way I got it, no mods, no twrp, no root, and it still has a problem. I just can't figure it out. I think I'm done.
I really liked the phone. It has great features for a $200 phone. I could still use it without the fingerprint password feature, but I really liked that... alot. I certainly have the root procedure down.... I might buy another one and try again, or I might look for something else in that price range and say fu huawei.
electric bill said:
It was working, then I tried to install magisk, but it wouldn't install with twrpimgmount_ramdisk.img so I flashed twrp_p10_lite_0.4.img and then magisk 18.1. After that, fingerprint stopped working for apps . I tried re-flashing 344 build, factory resets, different twrp versions, running the magisk uninstall zip, I even re-locked the bootloader. No dice. This phone is back to stock now just the way I got it, no mods, no twrp, no root, and it still has a problem. I just can't figure it out. I think I'm done.
I really liked the phone. It has great features for a $200 phone. I could still use it without the fingerprint password feature, but I really liked that... alot. I certainly have the root procedure down.... I might buy another one and try again, or I might look for something else in that price range and say fu huawei.
Click to expand...
Click to collapse
it's a problem with the app. If I restore an older version with titanium, it works fine.
Hi, I unlocked my mate SE boot-loader and rooted it. After upgrading to BND-L34 8.0.0.352, My TWRP disappeared and lost root. I tried used fastboot to reflash TWRP and failed. Could you confirm if your TWRP worked on version 352? Even I reverted my rom back to 344 using "Firmware finder", I still could not install custom any recovery. Could you help?
I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.
iwestfall7062 said:
I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.
Click to expand...
Click to collapse
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.
billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
The error happened once immediately after a full factory image flash before I had downloaded a single program or changed a single setting, so I don't see how it could be bluetooth settings, battery optimization, wifi/bluetooth scanning, or a rogue app. Oddly enough, since posting this last night I've managed to go 12 hours without an errors after flashing the Sept 2018 factory image. buuuuuuuut now I'm afraid to upgrade to Android 10 again.
jd1639 said:
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.
Click to expand...
Click to collapse
Thank you for making sure I understood this. Yeah, I generally factory reset my phone and laptop once a year so I always back everything up before a reset. And yeah, I haven't changed anything from stock on this phone since I've had it, so unlocking and locking the bootloader should never cause any issues. As I told Billy, the Sept 2018 image seems to have fixed the problem, fingers crossed.
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.
iwestfall7062 said:
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.
Click to expand...
Click to collapse
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.
jd1639 said:
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.
Click to expand...
Click to collapse
Yeah, I mean I would much prefer being on Android 10 and having the latest updates, I normally update as soon as they come out. But, given that I flashed the Jan 2020 image and bluetooth was still broken, and then flashed the Sep 2018 which seems to have fixed it, I'm hesitant to go back to the Jan 2020 updates. Kind of tending towards the if it isn't broken, don't fix it philosophy right now. If I had time to monkey around with my phone all the time I wouldn't mind, but the semester just started and I use my phone for everything at school so I don't really have time for it to be not working. >.< Such an odd issue and odd fix.
Looks hardware related, like the cable is loose.
wangdaning said:
Looks hardware related, like the cable is loose.
Click to expand...
Click to collapse
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.
iwestfall7062 said:
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.
Click to expand...
Click to collapse
What do you have Bluetooth connected to when it happens?
jd1639 said:
What do you have Bluetooth connected to when it happens?
Click to expand...
Click to collapse
Nothing. It doesn't matter whether anything is connected or not. It literally happened on first boot up of a fresh flashed Jan 2020 factory image, before I had put a single thing on the phone.
Generally I have my Fitbit Versa connected, I got 2 tiles awhile ago, but first troubleshooting thing I did was remove the app and delete those from bluetooth since those were my latest additions to bluetooth. I have backbeat fit headphones I use sometimes, the same with bose soundlink ii headphones, ps4 controllers, a jbl pulse 3, my car radio. But I factory restored all of those items so they weren't trying to connect to my phone, and then flashed the factory image. So I don't see how it has anything to do with an actual bluetooth connection.
Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10
JJT211 said:
Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10
Click to expand...
Click to collapse
Yeah, I wish this thread held a solution for you. I've searched and searched and tried every solution I've found on google and nothing has worked, and really none of the threads I have found have ever had a concrete solution either, just one or two people going "well I did THIS and it worked", and a bunch of people saying it didn't work for them. I just cannot fathom how a full factory flash back to the very first image would not revert the changes that came with Android 10. That's why I was questioning whether or not a factory flash replaces driver binaries. It's the only way I could see the factory flash to Sept 2018 not fixing our issue. (Other than it really being a hardware issue, but that doesn't seem possible to me.)
Oh wow, you're still having same issues on Android 9??
Im still on Android 10, most recent update. I did do a full factory flash a few weeks ago and it was quite the improvement. But I still do have the Bluetooth/radio issue every once in a while, like yesterday.
I wonder if it's a hardware issue and/or substandard hardware performance that Android 10 made more prevalent? That's something we'll probably never know
I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.
wangdaning said:
I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.
Click to expand...
Click to collapse
Oh no, I didn't think for a second you were being rude. And I appreciate your idea, just with what I'm experiencing with my specific phone it doesn't seem to be a hardware issue.
Strangely enough, the issue has been tapering off as of late, after the factory resets I just continued to use my phone while I wait to figure out if I can get a refund or a warranty replacement, etc. The issue has been occurring with much less frequency since then. Still happens, but not like it was.
Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.
JJT211 said:
Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.
Click to expand...
Click to collapse
Yeah, mines been better for like 4 days, and then it just crashed and rebooted by itself earlier today.
has anyone gotten to the bottom of this yet? it seems to be a result of the play store system update being "stuck" on Sept 1st...even if you get it to download to the current version, currently March 1st, after a reboot it will not show the March update has been applied. And should it actually show that the March update has been applies, within a day the phone will reboot and the bluetooth bug will return, strangely the update to the play store system reverts to Sept 1st.
I'm having this issue with my son's phone. I tried unlocking the bootloader and flashing the factory img from April but of course the bug is still there, and after signing in the Play Store system is of course dated Sept 1st
There is no fix. I made an official Android Issue Tracker thread.
https://issuetracker.google.com/issues/151033055
and a Google Pixel Phone Help thread.
https://support.google.com/pixelphone/thread/32828289?hl=en
Google's being ****ty about it. I eventually just bought a new Pixel 4 XL. I needed a functional phone for school and work, and as much as I hate to spend money on another Google product after this mess, they do make the most powerful pure android phones with the best camera. Ebay FTW, $600, never giving them another penny directly.
If you still have warranty, get it warrantied immediately, and don't take no for an answer. I dawdled around thinking it would get fixed and even though I reported that I was having issues with it directly to Google's phone support BEFORE the warranty expired, by the time I called a second time and pushed a manager to see if they could warranty it, my warranty had expired so they told me to go jump in a lake.
to make it worse, Google told me the phone still has an extended warranty but I'm not the original owner and have no way to contact that individual. But you need that person's email address for it to work. So it was purchased but because of this technicality it's null and void. I get the security of it but it's still garbage