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

Google Pixel 2 bootloop on Android 11 #3157

Closed
kyoto44 opened this issue Sep 9, 2020 · 20 comments
Closed

Google Pixel 2 bootloop on Android 11 #3157

kyoto44 opened this issue Sep 9, 2020 · 20 comments

Comments

@kyoto44
Copy link

kyoto44 commented Sep 9, 2020

Installed latest version from canary branch via TWRP and boot doesn't even starts

@stanleylhs
Copy link

stanleylhs commented Sep 9, 2020

Try using the patch boot.img method and flash via fastboot, it works as in #3153

@IahmadDev
Copy link

boot.img method also creates a bootloop on my pixel 2, I had to reset it.

@MaxwellDPS
Copy link

Can confirm, boot Loop occurring on Pixel 4 flame using the manager app as well

@SkeleBones
Copy link

SkeleBones commented Sep 9, 2020

I am having the same kind of issue on Pixel 2 XL. It just gets stuck booting up though not a bootloop. Unless that is considered a bootloop.

@topjohnwu
Copy link
Owner

According to @stanleylhs, this is apparently user error

@kyoto44
Copy link
Author

kyoto44 commented Sep 10, 2020

@topjohnwu user error? so if you install magisk on clean system and then it isn't boots it's user error?

@topjohnwu
Copy link
Owner

@kyoto44 don't install via TWRP, it's that simple.
TWRP is not designed to run on Android 11 yet

@kyoto44
Copy link
Author

kyoto44 commented Sep 10, 2020

@topjohnwu could you tell the way how me and others should install it?

@109021017
Copy link

109021017 commented Sep 10, 2020

@topjohnwu could you tell the way how me and others should install it?

You can install magisk without TWRP

  1. patch your boot.img by magisk.
  2. reboot to bootloader
    adb reboot bootloader
  3. flash the new magisk patched boot img.
    fastboot flash boot magisk_patched.img
  4. reboot to system
    fastboot reboot

But I am actually install it this way on my Pixel 2 XL. Stuck at Google Logo, after I doing this. Not sure if it's my problem or not.

@Didgeridoohan
Copy link
Contributor

But I am actually install it this way on my Pixel 2 XL. Stuck at Google Logo, after I doing this. Not sure if it's my problem or not.

Have you made sure that you don't have any modules installed that could be incompatible with A11?

@109021017
Copy link

@Didgeridoohan No module has been installed yet.

@Didgeridoohan
Copy link
Contributor

@Didgeridoohan No module has been installed yet.

And no leftovers from a previous Magisk install? Did you perform a full uninstall of Magisk prior to updating, or wipe /data?

@109021017
Copy link

109021017 commented Sep 10, 2020

@Didgeridoohan No module has been installed yet.

And no leftovers from a previous Magisk install? Did you perform a full uninstall of Magisk prior to updating, or wipe /data?

Yes, I cleared the storage of Magisk Installer from Settings after update to canary version.

@mu198
Copy link

mu198 commented Sep 10, 2020

Have you also tried after the flashes to come to the stocj recovery and made a factory reset there, had worked for me

@109021017
Copy link

Have you also tried after the flashes to come to the stocj recovery and made a factory reset there, had worked for me

I don't want to wipe the data. But if that's the only way, I will give it a try.

@Didgeridoohan
Copy link
Contributor

Yes, I cleared the storage of Magisk Installer from Settings after update to canary version.

What? That wouldn't remove any modules... Modules are stored in /data/adb/modules, completely separate from the Manager. You would have to either do a complete uninstall of Magisk (not the Manager), manually delete them from /data/adb/modules or wipe /data to remove them.

@mu198
Copy link

mu198 commented Sep 10, 2020

Haben Sie auch versucht, nach den Blitzen zur stocj-Wiederherstellung zu kommen und dort einen Werksreset durchzuführen, hatte für mich gearbeitet

You don't have to make a complete reset, your data can be preserved

Do they just have to look at what their recovery writes/says 😉

@109021017
Copy link

109021017 commented Sep 10, 2020

Yes, I cleared the storage of Magisk Installer from Settings after update to canary version.

What? That wouldn't remove any modules... Modules are stored in /data/adb/modules, completely separate from the Manager. You would have to either do a complete uninstall of Magisk (not the Manager), manually delete them from /data/adb/modules or wipe /data to remove them.

Migisk successfully installed after I:

  1. I boot into TWRP temporarily, and delete the /data/adb/modules folder
  2. reboot to bootloader
  3. flash the patched boot.img
  4. reboot to system

Thank you.

@OneTw0
Copy link

OneTw0 commented Oct 9, 2020

Try using the patch boot.img method and flash via fastboot, it works as in #3153

Also, at least for me. After trial & many errors. I realized my adb files where the culprit. I hadn't updated them. After that. Everything went smoothly. Running Android 11 Magisk on Pixel 2 XL.

@mstan
Copy link

mstan commented Nov 20, 2020

HI all, re-opening this issue since I'm running into the same problem without any clear solution.

Pixel 2 XL unlocked. Android 11. Factory reset. Tried installing Magisk right out of the gate. Attempting either the TWRP method or fastboot magisk install method cause a bootlop.

No modules are installed. Just trying a clean Magisk install on Android 11. Patched using Canary nightly. Doesn't seem to matter.

Double checked to see if /data/adb/modules was present. Folder doesn't even exist.

No idea where to go from here.

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