Related
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!
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
what method did you use (there are a million rooted guides)? did u get the correct OS OTA for you model phone? provide us more info please.
Looks like i forgot to turn off the magisk modules. I had to go into twrp and delete them all and re download the modules. silly me
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
jakemaxfield said:
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
Click to expand...
Click to collapse
I stuck at the same situation. Can you flashboot flash boot.img and then it can boot normally?
Same problem here.
Situation before flash: stock 9.5.8, Magisk, a number of Magisk modules
What I did:
* downloaded 9.5.9 with Oxygen Updater
* disabled Magisk modules
* rebooted
* installed 9.5.9 from the builtin System Update
* went to Magisk, installed it with After OTA
* rebooted to recovery
* installed TWRP and Magisk
* cleared Dalvik
* rebooted to system
The phone seems to start normally, but when it reaches the unlock screen it immediately goes to Power Off, then it reboots to TWRP (not power off). From TWRP I can decrypt data ok etc.
I tried reinstalling the boot loader, OTA image, TWRP, Magisk - same result. Rebooting to system from TWRP just goes back to Power Off then TWRP.
equlizer said:
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
Click to expand...
Click to collapse
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
manor7777 said:
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
Click to expand...
Click to collapse
That's exactly what I did. It landed me to the bootloop.
All you guys had to do is,
Install the full uddate zip in twrp,
Install the latest twrp zip,
Reboot recovery,
Install latest magisk,
Reboot system,
Hope this helps, cheers
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
lcd047 said:
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
Click to expand...
Click to collapse
I'm in the same boat.
My twrp doesn't offer to decrypt partition_b so I cannot manually install Magisk on the new partition.
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
sapalot said:
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
It worked for me for 9.5.8, got the bootloop this time around. I guess this means I'm not the Chosen One.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
djsubterrain said:
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
Click to expand...
Click to collapse
I tried that too. When I switch to the other slot I get to a menu where I can only wipe data, reboot to boot loader, or reboot to recovery. Not particularly useful.
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
mkos86 said:
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
Click to expand...
Click to collapse
What I had to do here was go to fastboot mode and flash twrp img. Then in TWRP I flash the TWRP zip file and magisk and rebooted. All good
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
jakemaxfield said:
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
Click to expand...
Click to collapse
Thank you sir, this fixed it for me, too. So the missing link was that Magisk modules have to be removed completely, not just disabled, before upgrading. Removing all directories except .core from /data/adb/modules allows the phone to boot normally, with Magisk enabled.
schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
Thats the way i tried that time and got stuck in bootloop.
I flashed OxygenOS 10.0.1 by the fastboot method. Then flashed modded TWRP and then Magisk. This all happened successfully. I wanted to install Youtube Vanced but stock Youtube was causing it to not show up. So I tried uninstalling Youtube through Titanium Backup but it said 'apk not found'. So I downloaded some other app (I think it was named 'System App Remover'). Since then I have been getting bootloops. Phone gets stuck on 'Bootloader unlocked warning' screen then goes into Fastboot mode. I had to uninstall Magisk through TWRP to boot the phone. I don't understand what's wrong in this entire process. Please help.
I think the issue is with the System App Remover. I tried using possibly the same exact app previously but I also got boot loops. I would try a factory reset, reflash twrp and magisk and try the Magisk module "Debloater".
You have to clean temporary magisk files.
Probaby you had enabled some magisk modules on previous system and you forget disable them.
Thanks for the replies. I fixed the problem by restoring System from an earlier TWRP backup.
Usually bootloops from Magisk modules can be fixed by deleting problematic module from twrp file explore /data/adb/modules
Don't have to fart around with uninstalling entire Magisk or installing Magisk debloater anymore
I installed Magisk via twrp(Temp version). and installed a bunch of modules.
Then I decided to complexly uninstall Magisk. I've done that from the Magisk Manager apk(The Complete Uninstall button)..
The phone rebooted and stuck into the phone logo with red danger logo. which means perhaps the boot img is missing ?
I should have uninstalled the modules first, which might have caused this issue..
Now, I Flashed Magisk again via Temp twrp, but now few apps keeps crashing, even after uninstalling and installing them.
i don't have the stock bot image, otherwise i guess i can do fastboot boot boot.img to escape the boot issue after uninstalling Magisk from the app
Note : i tried flashing the uninstall zip file from twrp but that didn't work, Magisk framework still exists !
What should i do now ?
My HTC is the duel sim version (Asia) and i'm using Magisk 22 latest version
Have you tried cleaning dalvik cache?
XDHx86 said:
Have you tried cleaning dalvik cache?
Click to expand...
Click to collapse
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu
Coldz0 said:
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu
Click to expand...
Click to collapse
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root
XDHx86 said:
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root
Click to expand...
Click to collapse
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !
Coldz0 said:
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !
Click to expand...
Click to collapse
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.
XDHx86 said:
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.
Click to expand...
Click to collapse
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)
Coldz0 said:
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)
Click to expand...
Click to collapse
You can find your device's ROM here (Literally first google results..):
HTC website
HTC dev center
GetDriodTips (Only for U12+)
**Disclaimer:** I don't own any of those ROMs and I don't hold responsibility whatsoever should you brick your phone or anything goes awry.
had exactly the same issue and exactly due to the same reason (I hate those pseudo-secure banking apps).
I couldn't wipe dalvik as TWRP is still not available for my P5.
But it was fixable really easy by reflashing the patched boot.img:
run command "fastboot flash boot magisk_patched.img"
btw I'm still looking for a solution for that stupid banking app.
I tried the above mentioned "magisk hide" and "safety net fix" and tried hiding the app itself but all that does not help.
Can we delete magisk and still use the phone rooted ? Or will it unroot my phone if magisk is removed. I’m planning to sell my s10 and the buyer does not want the application.
Good information from GetDriodTips (Only for U12+). Thank you.
Hello!
I wanted to update my oneplus 8 from 11.0.4.4 to newest version. OTA was not working idk why. I had magisk in place and I patched magisk to second partition or something like that [I dont remember how it was called] - I'm sure this is the reason of the problems. I turned off devices and wanted to boot into recovery, but suddenly it boot into Qualcomm crash dump mode with message: Attempted to kill init! exitcode: 0x00007f00 do_exit - that's all. I can't boot the system, I can;t boot into recover, I flashed patched boot, I flashed recovery - none of these works. Fastboot is present and recognized by PC.
First question can I do some backup through fastboot? To be honest I was not prepared for such problems. APKs are not even such a problem I care more about photos, documents and other data.
Can I flash some rom and restore phone back to life without wiping my personal data?
Maybe an idea would be to load TWRP recovery and then do backup, but how to boot into recovery when even after flashing recovery or booting via fastboot it enters in qualcoom crash dump mode. Something must be corrupted, but is it possible to fix some partition just in order to flash recovery to do backup of the files?
Please can you help me? I tried with some tutorials, but no success...
What did you try doing if OTA wasn't working?
You won't be able to use TWRP since you're on Android 11.
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?
I would disable the magisk modules first in case that is what caused problems. Then do a local upgrade using the full OTA zip. Then install magisk to the inactive partition. I think that would work, but I'm not sure if a messed up A partition might affect the installation. I don't think so, but I haven't read anything about it. After, you can try re-enabling the magisk modules.
I turned off all the modules obviously and still OTA is not working via the oneplus updater. It does not see the zip rom even though it's in the main directory. I don't know what is wrong...
Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.
L
trinidude4 said:
Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.
Click to expand...
Click to collapse
Lol yes you're right it was jar. Now the updater sees the zip file, but I'm afraid to update because I'm not sure if the phone won't brick or bootloop. What do you think?
I think it should be fine. I think the only thing that got messed up was the boot partition on the A slot and that will get overwritten with the OTA.
How about the root and magisk?
Okay I updated and it's working fine. I'm on 11.0.7.7 but now magisk is not working, how to get it back?
remialfa said:
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?
Click to expand...
Click to collapse
Any idea if it's possible to do something similar to rooted OP6?
I have a similar situation where I tried to update magisk and ended up with a bricked device.
I can reboot to fasboot, but I can't boot to recovery or flash anything through some pc flashing apps.