Hello,
so a few days ago, my One Plus one startet showing the message that AudioFX has crasched, every time I used anything that used the speaker or the microphone. I searched for that issue and found some methodes to fix that. I tired all of them serveral times:
- wipe cache
- factory reset
- flashing back to CM11
- flashing OxygenOS
- erasing and flashing persist.img and reserve4.img
- flashing MaxxAudio to replace AudioFX
- flashed Volume Increase Mod
- installing TWRP and run the following terminal command " make_ext4fs /dev/block/mmcblk0p15 " (as seen in this instruction)
Anything I've done changed nothing. The AudioFX is still not working.
I hope you got some ideas how to fix this
Related
Hi all,
I have a Xoom, running one of the nightlies from Team EOS (#34) and it was running fine until it started to get a lot of force closes. I figured thats fine ... I'm running a nightly, but then I started noticing that when I delete or install apps, then do a reboot, the apps are either not there (if I'd done an install) or still there (if I'd removed).
So then I figured, oh well, high time I got up to the latest nightly or even the stable build, and tried that, but low and behold after flashing the stable version of the Team EOS rom, when I booted back into the OS it was still the nightly #34.
So I tried restoring to the stock Motorola rom via fastboot, same result: booted into the OS on nightly #34. I tried a simple factory reset but when I boot back in all my data is still there.
So this is what I've tried:
- install Team EOS 1.0.0 stable build via CWM
- install Motorola stock rom via fastboot
- wipe data and cache via fastboot
- wipe data and cache via CWM
- factory reset via OS
... all with the same result - it just boots back into the OS with apps still there that I've deleted many times, and apps not there that I've installed many times. One slight point of note is that when I do the factory reset via OS, for some reason it boots into recovery, rather than back into the OS ... not sure if this is significant
Please help? I've searched around and people have mentioned this problem, but the threads always end without an answer
you could try to unlock your xoom again (even if it is not locked!), that should wipe your /data partition. As to why it doesn't through fastboot (assuming you used fastboot erase userdata), no clue... Also, if you're flashing something through fastboot and you don't get an error message and it still didn't work, that sounds like serious trouble...:-\
Thanks for your reply.
I'll try that out (the unlock) and I'll give fastboot another go with that command. I may have used fastboot -w on one occasion, and:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
on another.
I was wondering if I can do anything tricky with mounting/unmounting in CWM, but thats an area I have little of my own knowledge. Any thoughts?
I tried both of those suggestions, with no luck. And no error messages either.
Please continue to help .. I appreciate it!
Must say ive got the same problem - getting spurious erros after updating to the final build (3.0) - even after a hard reset and then going through the startup stuff i still end up with my desktop wallpaper from before....although i must confess i havent done the command line stuff yet...
Sorry buddy, but the bad news is that i put mine in for repair, and they were unable to fix it. They said that some aspect of the hardware had been fried and would need an expensive replacement, which would not be worth the cost. One of the risks of custom ROMs .....
Hi all - this is bugging me as I can't seem to find the root cause or a fix.
TF300T was running CM11 nightlies - last update applied was 04/05/14 and worked OK for a couple of days but when I tried to cold boot yesterday, boot loop half way through start screen. I wasn't bothered too much as I had a full backup before I updated ROM - however, restored backup and it failed to restore.
So have been trying to get a ROM installed but just can't and it's really annoying me. I have tried wiping & fresh install with several ROMs (CM11 2xnightlies, Omni, SlimROM) but all give the same result - boot loop. I have tried using both TWRP and ADB sideload
I have tried with SDCARD removed and get error * failed to write data 'protocol fault (no status)' *. SDCARD seems fine (can read / write from PC) but will format it anyway in TWRP and try again.
Any suggestions welcome.
Device details;
unlocked bootloader
recovery - TWRP 2.6.3
ROMs tested - CM11, Omni, SlimROM
SDCARD - SanDisk Ultra 64Gb
EDIT - knowing there was something corrupt with storage / system, I flashed stock then TWRP recovery. Booted into Stock OK but once I tried to install a different ROM, failed again.
So I’ve had my phone for about 3 weeks and from the get go I decided not to unlock the bootloader or root and just wanted to enjoy CM11S in its stock form. I downloaded and installed a bunch of CM11 themes and would constantly change them well once I changed the frost theme and ended up rebooting my phone the moment it booted into android I started getting spammed with unfortunately AudioFx has stopped errors and system UI crash.apk errors. I power my phone off as I am at work I reboot into the stock recovery and reluctantly did a factory reset and reboot thinking that it would relieve the problem. Upon that first initial reboot when you reach the cyanogens mod setup screen the audioFx errors return basically rendering the phone unusable. I found a method on android headlines to flash back to stock which I did through fastboot when I got home from work that do. I flashed the img files numerous times and I’m still greeted by the error upon reboot. My phone can’t be bricked because it actively lets me access fastboot and recovery…I even flashed twrp recovery and Cwm.img files through fastboot and successfully booted into recovery with no luck. My bootloader is locked so that basically stops me from flashing anything or mounting my internal storage in recovery. Every time I try to unlock the bootloader by fastboot oem unlock I get a counting second sequence on adb then nothing. Is there something I’m doing wrong I have rooted and unbricked tons of Android handsets. I love this handset Please help!!
I don't mean to be rude but please separate your text into different blocks (paragraphs). I'm getting very nauseous trying to understand what your problem is when I have to read 7-12 lines of text without any separation.
justinaquinnrambo said:
So I’ve had my phone for about 3 weeks and from the get go I decided not to unlock the bootloader or root and just wanted to enjoy CM11S in its stock form. I downloaded and installed a bunch of CM11 themes and would constantly change them well once I changed the frost theme and ended up rebooting my phone the moment it booted into android I started getting spammed with unfortunately AudioFx has stopped errors and system UI crash.apk errors. I power my phone off as I am at work I reboot into the stock recovery and reluctantly did a factory reset and reboot thinking that it would relieve the problem. Upon that first initial reboot when you reach the cyanogens mod setup screen the audioFx errors return basically rendering the phone unusable. I found a method on android headlines to flash back to stock which I did through fastboot when I got home from work that do. I flashed the img files numerous times and I’m still greeted by the error upon reboot. My phone can’t be bricked because it actively lets me access fastboot and recovery…I even flashed twrp recovery and Cwm.img files through fastboot and successfully booted into recovery with no luck. My bootloader is locked so that basically stops me from flashing anything or mounting my internal storage in recovery. Every time I try to unlock the bootloader by fastboot oem unlock I get a counting second sequence on adb then nothing. Is there something I’m doing wrong I have rooted and unbricked tons of Android handsets. I love this handset Please help!!
Click to expand...
Click to collapse
I'm also in the same boat.
In essence on bootup the phone gives a message that "AudioFX has stopped" on clicking the OK button the message appears within a second rendering the device unusable.
My first guess for me will be to remove the last installed app (which in this case was the Cerberus (cerberus_disguised-4.4.zip)
I flashed the version that integrates with the OS to prevent thieves being able to factory reset and remove protections.
**EDIT**
Okay it was an easy solve,
I removed via ADB , Volume+ which was causing the issue and will be moving instead to Viper4android
I had the same problem after changing some values in mixer_paths.xml and i follow this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and flash the phone.This guide will wipe your data,fotos,e.t.c.
You don't need to flash everything to fix the issue.
From the guide posted above, just download the factory image and ADB/fastboot tools, extract everything and flash system using "fastboot flash system system.img".
That restores the broken mixer_paths.xml in the /system/etc folder to the standard version. You don't even loose anything you installed or setup, as it's all on the data partition.
Btw, it's a very strange thing, that changing themes actually messes up a file which has nothing to do with themes, but is related to sound settings.
Dzhedaj said:
You don't need to flash everything to fix the issue.
From the guide posted above, just download the factory image and ADB/fastboot tools, extract everything and flash system using "fastboot flash system system.img".
That restores the broken mixer_paths.xml in the /system/etc folder to the standard version. You don't even loose anything you installed or setup, as it's all on the data partition.
Btw, it's a very strange thing, that changing themes actually messes up a file which has nothing to do with themes, but is related to sound settings.
Click to expand...
Click to collapse
How do you "fastboot flash system system.img" when you are in fast boot mode?
---------- Post added at 06:33 PM ---------- Previous post was at 06:13 PM ----------
Dzhedaj said:
You don't need to flash everything to fix the issue.
From the guide posted above, just download the factory image and ADB/fastboot tools, extract everything and flash system using "fastboot flash system system.img".
That restores the broken mixer_paths.xml in the /system/etc folder to the standard version. You don't even loose anything you installed or setup, as it's all on the data partition.
Btw, it's a very strange thing, that changing themes actually messes up a file which has nothing to do with themes, but is related to sound settings.
Click to expand...
Click to collapse
I'm a noob. Can you be more specific?
zoro25 said:
I'm also in the same boat.
In essence on bootup the phone gives a message that "AudioFX has stopped" on clicking the OK button the message appears within a second rendering the device unusable.
My first guess for me will be to remove the last installed app (which in this case was the Cerberus (cerberus_disguised-4.4.zip)
I flashed the version that integrates with the OS to prevent thieves being able to factory reset and remove protections.
**EDIT**
Okay it was an easy solve,
I removed via ADB , Volume+ which was causing the issue and will be moving instead to Viper4android
Click to expand...
Click to collapse
Would you be kind enough to tell me exactly what you put into the cmd screen to get volume+ removed? I'm having the exact same issue, and im pretty bad with adb. i've been looking for hours for a solution that works.
none of the previous methods work
has anyone gotten a method to work? i've tried every method above in this thread
edit:
except the adb command to remove the volume+ app because I don't have adb access while the phone is at the Cyanogen Welcome screen
You guys didn't search hard enough if you're still having this audiofx issue.
Here you go. Read my op carefully
http://forum.xda-developers.com/showthread.php?p=55488755
Dzhedaj said:
You don't need to flash everything to fix the issue.
From the guide posted above, just download the factory image and ADB/fastboot tools, extract everything and flash system using "fastboot flash system system.img".
That restores the broken mixer_paths.xml in the /system/etc folder to the standard version. You don't even loose anything you installed or setup, as it's all on the data partition.
Btw, it's a very strange thing, that changing themes actually messes up a file which has nothing to do with themes, but is related to sound settings.
Click to expand...
Click to collapse
Thank you so much! Your method is work!!!!!
I guess the audiofx FC loop may due to I have edited the file under system/etc for louder headset volume.....
Anyway, thanks again!
Hey people.
I have i simingly small problem but a very real one with my Z3 D6603
What i have done:
1. Unlocked bootloader with unlock code from sony dev site and adb in fastboot mode. Succsessfuly, checked service meny. All Ok so far.
2. I realized that i should haved backed up my drm keys when i upon next boot noticed i lost a couple sony stock features i like.
3. I followed this thred to the letter with a little reasonable thinking.
I used "D6603_23.0.1.A.5.77_IT.ftf" for TA partition restore. and "D6603_23.1.A.0.690_CentralEurope.ftf" for LP Stock.
4. I Used "Z3_ADV_stock_LP_v2" as kernel flashed in adb as fastboot. Everything else is flashed in Sony flash tool in flash mode on Z3.
5. Finally flashed "DRM Function Restoration for Xperia Lolipop V2.zip" in twrp.
6. Rebooted - Back to twrp flashed Chainfire Root zip 2.46 - rebooted.
All fine till this Point.
All working twrp 2.8.5.0 plus root.
Time for Xposed. Recovery - flashed "arm 15-03-08" rebooted. Install apk xposed alpha 2.
Download module "Xperia/AOSP NavBar Buttons" - check it for activation - reboots and NOW the problem beggins!!!
It get completely stuck at "SONY text in the beginning. I force shut it down by Power + Volume Up.
I dont remember exactly but the last can have been done Before i did a complete reflash for restoring sony orig features. (step 3)
7. Fresh install with root, sony orig features and twrp.
8. Install Xposed no problem. Installing "gravetyBox LP 5.0.6 Alpha.
9. Rebooting and starting to load bootanimation 5-6 seconds later it gives an ugly best described as hardware fail sound Sharp but dim tone and starts to bootlooping.
10. At this poing i can only get up and running by booting in to twrp - whipe - advanced wipe - chache and dalwik chache - reboot system it "optimizing 306 apps of about 15 minutes each time. Then its alive with everything working again. Root, Xposed, modules system and so on.
I have tried Another kernel "Z3_AndroPlusKernel_v51.zip" flashed via adb and fastboot. This resulted in a brick phone, not a Life sign at all.
adb and fastbooted z3. Flashed this kernel resulting in working phone with twrp 2.8.6.0 after Another step 10 procedure again.
Please, Please help! It would be fun to be able to shut down or rebooting my Z3 without this huge hang-bootloop problem. I finally got Everything working exept for above issue.
Im basicly stuck right now and just avoiding turning it off.
Come on all great xda people, help a fella in need!
Hi,
I have installed LineageOS on my Pixel 2 XL and I was having a media volume issue so I rebooted into Recovery and re-flashed Lineage... tried to boot and it was hung on the loading spinner.
I rebooted to Recovery again and flashed Magisk Uninstaller, LineageOS & GApps... tried to boot and it was hung on the loading spinner.
I rebooted into TWRP Recovery, wiped the System partition. Rebooted into Lineage Recovery and re-flashed LineageOS... I tried to flash Gapps but it is now saying that my device doesn't have enough resources!?
EDIT: I tried a few more times switching between slot a and B a bunch of times... and I've finally got it booting again but now the issues are:
- Google Messages is crashing all the time...
- Google Play Games is crashing all the time...
- Google Keep is crashing all the time...
- Google Photos is crashing all the time (This issue existed before!)