Microphone on my Google Pixel stopped working after some random period of time. It works after inital boot after factory reset but when i install all the apps that i use, mic stops working. I installed different ROM, different kernel, everything different but nothing helps. Someone told me it's a software problem, which it is because it works for a short period of time then it stops. Now i want to install LineageOS but when i try to find it in TWRP install section it shows some random folders and i can't find it there. When i want to ADB Sideload via TWRP it won't register it on computer when i type sideload devices... Idk what to do, i think that problem will be fixed when i install LineageOS without GAPPS but it's not possible. Any help???
https://www.theverge.com/2019/5/14/...y-mic-issues-lawsuit-payout-hairline-fracture
Here's your answer. It's a common problem unfortunately.
Related
Hey all,
I've been running Pac-ROM 4.4.4 for quite a while with hardly any issues, but I recently noticed some touch errors such as the home button and task button activate simultaneously when I only press one button. It sometimes takes a few taps before only the home button is registered. Also on the right side of the screen I can't pull down the notifications bar; that only works in the middle-left of the screen. Because of this, I decided to upgrade my ROM to the newest beta version of Pac-ROM lollipop.
Now my issue: the new ROM had issues with google store and services. Instantly upon booting up, youtube kept spamming my screen saying it couldn't run. I also had notifications for google play store, so I uninstalled both youtube and the play store (after clearing cache for a simpler fix). That got rid of the pop-ups, but I still couldn't access my google account. I browsed some threads and they suggested to remove my google account and clear cache for google services. This didn't fix the problem so I decided to flash back to the stable 4.4.4 and reinstall the apps I removed.
Here is where I foolishly realized I never updated my gapps to 5.x.x. Being too late, I thought I'd just flash the gapps and lollipop rom after getting things back to normal in 4.4.4. Unfortunately, I was never able to boot after flashing 4.4.4.
Now I am stuck in a boot loop, do not have debugging enabled thanks to the update (so I can't use adb), my recovery won't boot using power + vol down, and my computer doesn't even recognize my phone when using LG mobile support tool.
Other things that may help:
LG G2 ls980zve
TWRP 2.8.x.x
cannot access adb or fastboot
cannot access recovery
cannot turn on phone
updated lg drivers as of today, but computer doesn't recognize my device in device manager
followed these threads but couldn't resolve the issue:
http://www.rwilco12.com/forum/showthread.php?tid=96
http://forum.xda-developers.com/showthread.php?t=2432476
http://forum.xda-developers.com/showthread.php?t=2471370
Ask if I forgot to mention anything crucial.
Good luck figuring this out
ForceClosed said:
Hey all,
I've been running Pac-ROM 4.4.4 for quite a while with hardly any issues, but I recently noticed some touch errors such as the home button and task button activate simultaneously when I only press one button. It sometimes takes a few taps before only the home button is registered. Also on the right side of the screen I can't pull down the notifications bar; that only works in the middle-left of the screen. Because of this, I decided to upgrade my ROM to the newest beta version of Pac-ROM lollipop.
Now my issue: the new ROM had issues with google store and services. Instantly upon booting up, youtube kept spamming my screen saying it couldn't run. I also had notifications for google play store, so I uninstalled both youtube and the play store (after clearing cache for a simpler fix). That got rid of the pop-ups, but I still couldn't access my google account. I browsed some threads and they suggested to remove my google account and clear cache for google services. This didn't fix the problem so I decided to flash back to the stable 4.4.4 and reinstall the apps I removed.
Here is where I foolishly realized I never updated my gapps to 5.x.x. Being too late, I thought I'd just flash the gapps and lollipop rom after getting things back to normal in 4.4.4. Unfortunately, I was never able to boot after flashing 4.4.4.
Now I am stuck in a boot loop, do not have debugging enabled thanks to the update (so I can't use adb), my recovery won't boot using power + vol down, and my computer doesn't even recognize my phone when using LG mobile support tool.
Other things that may help:
LG G2 ls980zve
TWRP 2.8.x.x
cannot access adb or fastboot
cannot access recovery
cannot turn on phone
updated lg drivers as of today, but computer doesn't recognize my device in device manager
followed these threads but couldn't resolve the issue:
http://www.rwilco12.com/forum/showthread.php?tid=96
http://forum.xda-developers.com/showthread.php?t=2432476
http://forum.xda-developers.com/showthread.php?t=2471370
Ask if I forgot to mention anything crucial.
Good luck figuring this out
Click to expand...
Click to collapse
Here's a guide that can help you.
i am sure that there's guides here on xda too.
That guide was essentially the same as the two links I referred to except one thing... It reminded me to reboot the computer after installing drivers! HAHA. Now it worked smoothly.
Such a simple fix, thanks!
ForceClosed said:
That guide was essentially the same as the two links I referred to except one thing... It reminded me to reboot the computer after installing drivers! HAHA. Now it worked smoothly.
Such a simple fix, thanks!
Click to expand...
Click to collapse
Hahaha!! Happy that I helped someone!
Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.
Hi all,
here is my problem.
I have an OPO since 2014, since then I flashed quite everything to it.
A couple of months ago my sim module stopped working, it was an hardware problem, so I had it repaired a week ago (I wasn’t in a rush, I have another phone I use as my main one) and came back fully working. I don’t know if this is implied in the problem I’ll describe, but it’s a fact that worths the mention.
Since I was on the new CM 14.1 nightly, I decided to update the ROM from the updater in the settings menu, so I downloaded the latest one and reboot in recovery and install it.
There started all my problems: it happened an error while TWRP was working, “E: unknown command [log]”, I didn’t understood what it was about so I restarted anyway.
The phone was in bootloop in that moment, thus I decided to clean install the nightly I downloaded earlier, this time also with the gapps: this time, after the same error already mentioned, TWRP crashed while installing the gapps.
From that moment I couldn’t do anything: the phone acted weird, it restarted three or four times and then it went black. I was able to enter fastboot, I hardly managed to enter the recovery since not every time the combination “vol-+power” worked.
So I decided to flash the stock ROM with fastboot. Nothing, it wasn’t a solution, the problems are still there and I don’t know what to do.
I’m now able to enter TWRP with fastboot, and I can install a ROM without problems, but eventually TWRP crashes, the phone restarts three or four times and then it dies.
What the hell is going on with my phone?
I also notice something: when I install a new ROM (with TWRP), the recovery crashes etc etc but when I manage to renter, folders in the “sdcard” are:
- a “0” one
- an “obb” one
- the "TWRP" one.
If I put a zip in the “sdcard” folder, and again install it, after the reboots the “sdcard” folder is still intact, with the three folder “0” “obb” and “TWRP”, the zip I flashed seems to disapper
BUT
If I open the “0” folder, I found the zip I copied earlier! It happens every time I install a ROM: I found multiple combination of the three folder on the path "sdcard/0/0/0" ect etc. I have a video that can show this issue more clearly, but I can't post it at the moment (I'm a "new" user).
It’s a long post, I know, but I wrote the less I could, if someone needs some other infos pleas ask, I really want to bring back this phone.
Thanks
Pardon for a long story but someone gave this Samsung J7 Prime(SM-G610F) to me with an issue "An Error Has Occurred While Updating The Device Software". So I gave Samsung Smart Switch a try sadly they removed the Initialize option and old version don't seam to do what it suppose to do so I wen to a traditional Odin flashing. I then look for a stock rom for the phone that I think is the right one. Started with android 6 MM region pakistan and flashing went well. I was able to use it for a good hour or two until I notice it restarted by it self, then it keeps doing it 10-20 seconds after booting up. I though its the firmware I'm using so I went and look for Oreo version this time I region india (I don't know if region matters). So I flashed it again and tested the device again. I'm still able to use it for a good while till it restarted again. I then keep testing it to see what may be causing the problem. I notice that when the WIFI is on it just crash the phone to reboot so as soon as the phone reboots I turned the wifi off and it didn't crash anymore. I then factory reset the phone cleared everything, wipe cache then installed benchmark tools first. Thing I notice is it crashes when Google Play store is trying to install or download something. I tested it a couple of times to see when it crash and it does crash when downloading or installing something. I was still able to install 3Dmark and run it with wifi off. It completed the test without crashing so it couldn't the processor issue. I then look for another rom and tried flashing it. This time I had issue with it failing at system.img even if I use recent rom that worked. I then keep trying till flashing TWRP worked and flashing the rest of the rom is fine again.
What bothers me is why doesn't it crash during the first couple of hours. I've search similar issues and they say it may have been and app issue. I've already disabled bunch of app but nothing changed. Run the phone in safe mode but this time instead of crashing and rebooting right away it freezes for a few seconds. I suspect if google play or something being an issue since I've tried disabling it and it didn't crash for a couple of hours. Looked for allot of related thread but none of them seam to solve my problem.
I suspect either its the rom that I'm using and it can only be fixed by using the original rom, or its having a memory issue but don't know how to pin point it. Anyone can suggest on how I can debug this? I'm used to debugging things in real time and my knowledge with android is a quite slim but as a programming understanding the errors won't be a problem. I hope.
Edit: Hmm. Does copying kernel log with TWRP work or the kernel logs get overwritten every time the phone reboots? Because I see the kernet logs but don't see anything failing except for something saying SHUTDOWN but I don't think thats it. :S
Still no reply. :S I think its /system dismounting it self while doing a write operation. but it doesn't trigger until a certain amount of time after the phone is flashed or factory reset. I have to go to recovery and mount system back but that only happens on marshmallow. over version it remounts it self after the random reboot. After factory reset I'm able to install COD mobile and play a couple of match. after a long while it just decides to reboot.
I also tried z3x and after reading PIT from phone OK. the phone just reboots and flashing completes without it doing any flashing.
Good evening guys.
For a couple of days the phone has been in bootloop and I have problems with the persist partition. It all started at the beginning of the year. For no apparent reason, the main camera stopped working (error: unable to connect to camera). The curious thing is that in the smartphone test menu, all the cameras are functional, except for the main one. The tests I did were:
Format the phone from the settings.
Reinstall the rom via fastboot.
Install other roms.
In the case of formatting and reinstalling, the camera app only worked if I held down the icon and chose to take a selfie. Using other roms, however, the pre-installed camera (camera go, for example), did not start. If instead I installed one of the various gcams for surya, these worked. But if I tried to load the config files briefly into the gcam, it also crashed and wouldn't open anymore.
In the end, I opted to keep the stock rom (rooted) and use a gcam with no setup. These days, the phone hasn't been used except to play online (only on wifi) and hasn't given any problems. Yesterday however, while I was playing, the gyroscope started moving by itself and/or getting stuck and not working.
At that point, I decided to do yet another fastboot flash. This time though, the phone didn't boot anymore, remaining in bootloop. I also tried to change version (from global to european), to flash again other roms (pixel os, miui.eu, pixel expiriece), but nothing to do. The only thing I noticed is that the recovery warns me that I can't mount /persist. I also tried recovering the persist.img from the original rom (I don't have a backup) and flashing from twrp. It seems to work fine, but then actually the same error comes back. I also tried from the terminal, always via twrp, but even there it says it has copied the data, but the error returns.
Could you help me?
Thank you.