Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hangs A14 Build AP1A.240305.019.A1 #30

Open
Bennett-69 opened this issue Mar 6, 2024 · 11 comments
Open

Hangs A14 Build AP1A.240305.019.A1 #30

Bennett-69 opened this issue Mar 6, 2024 · 11 comments

Comments

@Bennett-69
Copy link

After flashing Android 14 OTA from March 2024 (build AP1A.240305.019.A1) on Pixel 8 Pro, phone will no longer boot with this module enabled.

@kidney715
Copy link

Same issue here on a Poco F3 with a Pixel port running build AP1A.240305.019.A1.

@distbit0
Copy link

distbit0 commented Apr 7, 2024

Same issue with pixel 5a on 14.0.0 (AP1A.240305.019.A1, Mar 2024)

@distbit0
Copy link

distbit0 commented Apr 7, 2024

What should I do to recover from this? thx in advance

@Bennett-69
Copy link
Author

What should I do to recover from this? thx in advance

You need to disable or remove the Magisk module. Easiest way is probably:

  1. Boot Android into Safe Mode (search online if you're unfamiliar)
  2. Reboot normally, all Magisk modules should be disabled after detecting previous Safe Mode boot
  3. In Magisk Manager, re-enable all modules except this one
  4. Reboot for changes to take effect.

@kidney715
Copy link

What should I do to recover from this? thx in advance

You need to disable or remove the Magisk module. Easiest way is probably:

1. Boot Android into Safe Mode (search online if you're unfamiliar)

2. Reboot normally, all Magisk modules should be disabled after detecting previous Safe Mode boot

3. In Magisk Manager, re-enable all modules except this one

4. Reboot for changes to take effect.

Adding to this, my system wouldn't boot after safe mode too. Just sharing it as an alternative / just in case thing: I connected my phone to my PC in safe mode with USB debugging on, and ran the following command in cmd to remove all modules, after which my system booted normally:

adb wait-for-device shell magisk --remove-modules

Then I reinstalled all my modules except AudioHQ.

@distbit0
Copy link

distbit0 commented Apr 7, 2024

thanks for this advice. My understanding is that booting into safe mode requires me to boot up my device first and then use the android UI to reboot into safe mode, however this is not possible as I can not boot with the module still installed.

What I ended up doing was flashing the stock boot.img from the android website for my pixel, which has allowed me to boot up but has un-rooted my phone. This is because by flashing the boot.img, I have disabled magisk and hence disabled this module as well.

I do not know how to re-root it though, as if I simple flash a boot.img file that has been patched by magisk, I suspect I will re-enter the boot loop when I boot up after flashing, because it will re-enable magisk and hence also re-enable this module.

I also do not know how I can delete the module before rooting, as the module is installed under the /data directory which is only accessible as root. I also can not run magisk --remove-modules as I get a magisk not installed error (because my device is not yet rooted). I.e. I can not simply disable the module in the magisk app because the modules tab is greyed out as a result of my device not being rooted.

I've tried booting into safe mode but I do not see how it helps as it just disables all downloaded apps, including magisk.

Many thx

@distbit0
Copy link

distbit0 commented Apr 7, 2024

ok I figured it out. The steps were:

  • re-flash the patched boot.img
  • boot into unpatched boot.img
  • reboot into safe mode
  • run adb wait-for-device shell magisk --remove-modules

thanks for the help. much appreciated

@Bennett-69
Copy link
Author

For future reference, regarding Android and Magisk safe modes:

https://topjohnwu.github.io/Magisk/faq.html

@znbaboy
Copy link

znbaboy commented May 16, 2024

same. Pixel 7 Pro LineageOS 21 May 14th build

@MadTooth
Copy link

@Alcatraz323
Same. lineage_alioth-userdebug 14 AP1A.240505.005 7f88b7efe6 (21-20240515-NIGHTLY-alioth)

@RGBok
Copy link

RGBok commented Jun 8, 2024

Same Issue Pixel 8 Pro on 14.0.0 (AP1A.240505.005, May 2024)
Anyone found a fix?

Downgraded to 14.0.0 (UQ1A.240205.004, Feb 2024), Result: Audiohq works

@Karabiner07 Karabiner07 mentioned this issue Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants