Related
So i saw a post on XDA regarding the android 11 preview GSI, and decided to try it out.
I used this thread https://forum.xda-developers.com/rog-phone-2/how-to/guide-install-gsi-image-google-apps-t3998133 as the basis for how to do it
Download the preview and vbmeta image (included with the GSI image download) here: http://developer.android.com/preview/gsi-release-notes
It didn't work at first (bootlooped) so i re-entered fastboot and tried again using fastboot --set-active=a>flashing the vbmeta img >erase system>flash GSI image>reboot bootloader then fastboot --set-active=b and repeat.
Then rebooted to recovery. I had TWRP installed before hand, and my phone still rebooted to TWRPl, so i did factory reset, and then format data. After this, it booted! (I have no idea if setting active to slot b helped or is necessary, or if it was the formatting data in TWRP that made it boot)
A few words of caution:
- the default phone app has no sound. it rings (the person receives the call) but no sound on either end.
- setup is a bit glitchy, however going back, and then through the options again worked for me
- there is no default ringtone or notification sounds, so you will have to use Zedge or something similar to get these
- there is no option for a screen lock (that i could find), only 'swipe' - this interferes with the use of one of my banking apps, and other apps may have issues with it
-everything is very... square
yeah i tied it but that vbmeta img always gives me an unbootable slot
Kitharn said:
So i saw a post on XDA regarding the android 11 preview GSI, and decided to try it out.
I used this thread https://forum.xda-developers.com/rog-phone-2/how-to/guide-install-gsi-image-google-apps-t3998133 as the basis for how to do it
Download the preview and vbmeta image (included with the GSI image download) here: http://developer.android.com/preview/gsi-release-notes
It didn't work at first (bootlooped) so i re-entered fastboot and tried again using fastboot --set-active=a>flashing the vbmeta img >erase system>flash GSI image>reboot bootloader then fastboot --set-active=b and repeat.
Then rebooted to recovery. I had TWRP installed before hand, and my phone still rebooted to TWRPl, so i did factory reset, and then format data. After this, it booted! (I have no idea if setting active to slot b helped or is necessary, or if it was the formatting data in TWRP that made it boot)
A few words of caution:
- the default phone app has no sound. it rings (the person receives the call) but no sound on either end.
- setup is a bit glitchy, however going back, and then through the options again worked for me
- there is no default ringtone or notification sounds, so you will have to use Zedge or something similar to get these
- there is no option for a screen lock (that i could find), only 'swipe' - this interferes with the use of one of my banking apps, and other apps may have issues with it
-everything is very... square
Click to expand...
Click to collapse
Thanks for the heads up, can you please post some pictures :good:
Kitharn said:
So i saw a post on XDA regarding the android 11 preview GSI, and decided to try it out.
I used this thread https://forum.xda-developers.com/rog-phone-2/how-to/guide-install-gsi-image-google-apps-t3998133 as the basis for how to do it
Download the preview and vbmeta image (included with the GSI image download) here: http://developer.android.com/preview/gsi-release-notes
It didn't work at first (bootlooped) so i re-entered fastboot and tried again using fastboot --set-active=a>flashing the vbmeta img >erase system>flash GSI image>reboot bootloader then fastboot --set-active=b and repeat.
Then rebooted to recovery. I had TWRP installed before hand, and my phone still rebooted to TWRPl, so i did factory reset, and then format data. After this, it booted! (I have no idea if setting active to slot b helped or is necessary, or if it was the formatting data in TWRP that made it boot)
A few words of caution:
- the default phone app has no sound. it rings (the person receives the call) but no sound on either end.
- setup is a bit glitchy, however going back, and then through the options again worked for me
- there is no default ringtone or notification sounds, so you will have to use Zedge or something similar to get these
- there is no option for a screen lock (that i could find), only 'swipe' - this interferes with the use of one of my banking apps, and other apps may have issues with it
-everything is very... square
Click to expand...
Click to collapse
Were you on ASUS' Android 9 Pie or Android 10 beta before you flashed Google's Android 11 GSI?
MishaalRahman said:
Were you on ASUS' Android 9 Pie or Android 10 beta before you flashed Google's Android 11 GSI?
Click to expand...
Click to collapse
I was on android 9
Kitharn said:
I was on android 9
Click to expand...
Click to collapse
Impressive that it worked. You might have a better experience if you upgrade to the Android 10 beta and then flash the GSI.
MishaalRahman said:
Impressive that it worked. You might have a better experience if you upgrade to the Android 10 beta and then flash the GSI.
Click to expand...
Click to collapse
i was on beta 10 couldnt use it long had to flash back because of work but main bug is the one from them all which is no sms incoming going to try it a little more today
10 beta for me usable as daily driver but still got bugs left to be squashed...Android 11 tempting but seeing 10 beta the way it is guess I'm staying on 10 til stable ba
How is this going on? Someone on A11 Beta 1 already? Exciting for the review!
Kitharn said:
So i saw a post on XDA regarding the android 11 preview GSI, and decided to try it out.
I used this thread https://forum.xda-developers.com/rog-phone-2/how-to/guide-install-gsi-image-google-apps-t3998133 as the basis for how to do it
Download the preview and vbmeta image (included with the GSI image download) here: http://developer.android.com/preview/gsi-release-notes
It didn't work at first (bootlooped) so i re-entered fastboot and tried again using fastboot --set-active=a>flashing the vbmeta img >erase system>flash GSI image>reboot bootloader then fastboot --set-active=b and repeat.
Then rebooted to recovery. I had TWRP installed before hand, and my phone still rebooted to TWRPl, so i did factory reset, and then format data. After this, it booted! (I have no idea if setting active to slot b helped or is necessary, or if it was the formatting data in TWRP that made it boot)
A few words of caution:
- the default phone app has no sound. it rings (the person receives the call) but no sound on either end.
- setup is a bit glitchy, however going back, and then through the options again worked for me
- there is no default ringtone or notification sounds, so you will have to use Zedge or something similar to get these
- there is no option for a screen lock (that i could find), only 'swipe' - this interferes with the use of one of my banking apps, and other apps may have issues with it
-everything is very... square
Click to expand...
Click to collapse
Is this same method for flashing android 12 gsi
On asus rog phone 2 ?
patilrohit9001 said:
Is this same method for flashing android 12 gsi
On asus rog phone 2 ?
Click to expand...
Click to collapse
And dynamic partition not support but it's treble support with A/B , On Omni A11 custom rom can I flash android 12 gsi on it ?
This is a guide how I flashed Android 10 to my Cubot Power.
Preparation:
HINT:
Make a Backup! You will definitely loose all your data on the phone due to several factory resets!
First make sure your Device can use treble and also which one you need with this app:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
(according to this post https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559)
note down:
Architecture: (Cubot Power: arm64)
System as Root: (Cubot Power: A-only)
then you will need fastboot and adb:
Windows:
https://forum.xda-developers.com/showthread.php?t=2588979
Linux:
Code:
sudo apt-get install android-tools-adb
Code:
sudo apt-get install android-tools-fastboot
Then you need twrp Recovery or something similar. Cubot Power is not supported by the official twrp project, but there is this unofficial version:
https://unofficialtwrp.com/twrp-3-2-3-recovery-cubot-power/
And you will probably need gapps:
https://opengapps.org/
For cubot power you will need "arm64" and "anrdoid 10" of course.
For the variant version I went with "nano" but you can probably choose what you like.
If you have a external sd card you want to copy the gapps, supersu and no-verty-opt-encrypt ZIP onto it.
Now download the android 10 treble image from:
https://github.com/phhusson/treble_experimentations/releases?after=v211
For the Cubot Power i went for the system-quack-arm64-aonly-vanilla.img.xz. But you should select the right one according to the treble app.
I went for vanilla because with gapps it did not seem to work.
Optional:
From this site:
https://romprovider.com/cubot-power-root-twrp/
Download SuperSu (https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip)
and no-verty-op-encrypt (https://romprovider.com/download-no-verity-opt-encrypt-version/)
this prevents bootloops.
In case something goes wrong have your stock rom and sp flash tool ready:
Cubot Power: http://forum.cubot.net/viewtopic.php?f=21&t=2419
Flashing
Make sure your phone is charged probably. Booting might take up to an hour. At least 70% is recommended.
Go to developer settings and enable usb -debugging and disable oem.
now type:
Code:
adb reboot bootloader
the device should now restart and boot into fastboot
now disable oem in fastboot and unlock flashing: (WARNING: this will factory reset your phone)
Code:
fastboot oem unlock
Code:
fastboot flashing unlock
now we want to "install" twrp:
Code:
fastboot flash recovery TWRP_cubot_power-030918.img
--(Optional) check if twrp is working:
Code:
fastboot reboot
and restart with the volume up button
in twrp go to mount and check if you can mount data. If not: https://appuals . com/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/.
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Then go to install and install no-verty-op-encrypt.
then got to reboot and select bootloader.
--
continue with flashing android 10:
unzip the xz file
Code:
fastboot flash system system-quack-arm64-aonly-vanilla.img
this might take a while.
Then reboot
Code:
fastboot reboot
now your phone should boot into android 10. This can take very long for me it took about 30 minutes. If it takes longer then one hour you can probably start troubleshooting.
Install google apps(playstore)
once it has booted you either can start the login process and enable usb debugging again and reboot into recovery:
Code:
adb reboot recovery
or turn it off and restart into twrp (power button and volume up).
In twrp again check if you can mount data (see the optional step).
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Install super su and gapps.
Now reboot to system.
Now again the phone will boot a very long time (up to a hour).
Conclusion:
For me it is pretty stable but sometimes the fingerprint sensor does not work or the sim card is not recognized. But a reboot fixes it (sometimes).
But rebooting always takes time. At least 5 minutes sometimes up to 30 minutes. Once the system is booted there are no feel-able performance issues.
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Click to expand...
Click to collapse
Probably it will work, but I can give you no guarantee for that.
Thank you!
Hi Johanno,
Thank you for this great tutorial! I think I already downloaded the treble check tool in March and I also found the github page, but I didn't find any experience on the net related to Cubot Power, so I didn't dare to upgrade.
Did you try later releases?
Should I go with latest release v222 or do you know about any change in v211 that prevents us from upgrading to a later version? ( your link in the tutorial shows only older versions: https://github.com/phhusson/treble_experimentations/releases?after=v211 )
Did you use windows or linux?
Did you experiment with V25 ROM?
https://www.cubot.net/platform/Support/detail/id/192/cid/23.html
Br,
taarzaan
I'm trying the latest release v222. I'm after the last reboot. It's not fast, but I would say it's less than 30 minutes. It should boot in 5 or 10 minutes.
Br,
taarzaan
Results of my experiments
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports legacy Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
regards
Al
Click to expand...
Click to collapse
hi
i just want to understand what is legacy version? and vndk27 ? i googled but few info
my phone say same info here
i ll post the results but if one could explain those 2 things
thank u in advance
taarzaan said:
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Click to expand...
Click to collapse
notes for the next experiment (we should open a proper ticket for phhusson):
"What does "can't be used" mean? Does the pone vibrate? Does screen lights on? If you go in Fingerprint settings, do you see the enrolled fingerprint? Can you enroll a second one? If you press your fingerprint sensor when you're on that screen, what happens?"
I've tried with both v211 and v222 - but I don't seem to get past boot screen.
After using fastboot flash (and I've also tried SP flash tool flash) the phone shows cubot boot screen (with a warning about "orange mode" not being trusted) and can boot into TWRP but when booting system it shows a black screen with white slowly flashing "android" for a long time. More than one hour. I lose faith and re-install stock each time.
Any ideas how to debug and see what's happening?
Any improvements to this? I am having a P20/cubot and had same problems. AOSP v222 does not boot but I tried lineage-17.1-20201215-UNOFFICIAL-treble_arm64_avS.img.xz from https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
Surprise. it works but a bit slowly. Due to large battery I am thinking of cubot power?
I have 2 questions:
1. Can you please try the lineage-17.1 rom?
2. BTW, did AOSP8 work OK in cubot power? (i like oreo more than android 10)
Thanks for your replies.
htorsten2020 said:
1. Can you please try the lineage-17.1 rom?
Click to expand...
Click to collapse
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
htorsten2020 said:
2. BTW, did AOSP8 work OK in cubot power?
Click to expand...
Click to collapse
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
taarzaan said:
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
Click to expand...
Click to collapse
Call/SMS/data stability. A lot of devices that came with oreo (vendor) have lots of issues with signal (mobile SIM) dropping after some hours. Thanks
taarzaan said:
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
Click to expand...
Click to collapse
Cubot Power ships with Android 8.1 (oreo). So I asked if you tried the old AOSP from phhusson (v32 - this is AOSP8 equivalent treble ROM). I found the AOSP from the same version (oreo as the device) is faster than installing newer ROM.
Hi guys, as you may have noticed I am not very active here ;-)
I actually went back to stock firmware after a few weeks because I couldn't get the phone working again. And since I want to use my smart phone and not tinker on it every few days I gave up. But now I am thinking about using Lineage os.
But first I need to back up everything and that's probably the thing that will hinder me the most.
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
kezyr said:
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
Click to expand...
Click to collapse
hi, how exactly did you install the lineageos 18.1 with the twrp 3.2.3? thank you in advance for your help
i just get boot loop on every rom i try on cubot power
I had the same problem and gave up
Hi guys.
I'm trying to patch a boot.img from latest version V11.0.19.0 with Magisk 23 but the resulting file does not complete the boot procedure when used with platform.tools.
It starts the booting process but after security pattern it remains with the booting animation forever. I need to restart the phone to access it.
i got the boot.img file from the Fastboot image available here - https://xiaomifirmwareupdater.com/miui/daisy/stable/V11.0.19.0.QDLMIXM/
Could any of you try to sort this out for me.
Thanks in adavance
Jiute
Problem resolved. It was the Magisk Modules still active. Had to Disable them and then all went smooth.
I just upgraded my phone from BTJ4 to DUF9 and everything seems to be correct except when I try to re-install Magisk to get root again .. after patching the boot.img.lz4 file(via boot.tar) and installing it via Odin AP the phone just enter a bootloop with the black screen and Samsung logo on it.
I've tried everything I can come up with but I get nowhere.. I've tried Magisk v22 and v23 - same result, tried installing with BL+CP+CSC/BL+CP+CSC with vbmeta_disable in USER and the patched magisk boot image in AP .. still no luck.
Magisk seem happy patching both with v22 and v23 so that seems correkt. The file grows from ~20k as boot.tar to ~60k as magisk_patched tar - which I guess is ok..
Would appreciate any help in getting this to work.
hochocnua said:
New version for SM-G985F with region/firmware DBT/G985FXXU6DUB5
Guide firmwares update and file here
Downloads for : Samsung Galaxy S20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Thanks @ianmacd and @afaneh92 for help and guide
1. Select the BL, AP, CP and HOME_CSC files (save data)
** don't run the firmware yet
2. Download Ian's latest TWRP (twrp-z3s-3.5.0_10-A11_x_ianmacd.img) containing TWRP + patched vbmeta.img into USERDATA slot in Odin.
twrp-z3s-3.5.0_10-A11_6+vbmeta_DUB5.tar | by LEAKs Việt Nam for Galaxy S20
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
3. Uncheck the automatic reboot option in Odin
4. run the flashing
5. When the firmware is finished (leave USB connected !!!), hold the Vol Down + Power buttons, and then, as soon as the screen turns black, hold the Vol Up + Power buttons to boot into recovery
*, keep in mind that the first time you boot into recovery, it initializes and then reboots, so just keep the Vol Up + Power buttons pressed for longer than
6. TWRP - Multi-Disabler Firmware
7. Reboot TWRP - Flash Magisk (stable)
8. Flash Fix_warning_up_param_S20 +
9. RESTART.
Click to expand...
Click to collapse
You have to use this method.
Try using canary version of magisk.
Hmm chieco’s post explains pretty much everything
Tried Canary build of Magisk - didn't help.
Installed TWRP according to above .. didn't work at all. Now the phone is completely dead, only thing that boots i TWRP Recovery.
Correction - without flashing anything at all with TWRP I can actually boot into the phone ..
Correction 2 - when I flash the multidisabler-samsung-3.1.zip it stops the phone from booting.
Correction 3 - so after finally trying just about everything I can come up with it seems as when anything at all touches the boot or system partitions it stops the phone from booting normally.
If I just install the rom with twrp+vbmeta everything works as it should. If I then flash anything at all, doesn't matter what, it stops working. If I flash a magisk patched image - it stops booting.
So.. now I'm stuck.. I have no more ideas.
I even installed the previous release DUE4 with the same result.
I tried patching the complete AP file with magisk - same result.. phone refuses to boot normally.
If I do the Magisk patch file patching before doing the first system boot after upgrading it does the optimize apps thingie but then after rebooting it stops with a bootloop. And by the way under all this TWRP gets replaced with the default Android recovery .. no matter what I do - the internal SD card is no longer encrypted tho so I guess the multidisabler has done its thing.
Only thing I have NOT tried yet is a complete factory reset.. but I don't know if that would make any difference ?
So ended up with a full wipe and installing BeyondROM .. now the phone is rooted and booting with twrp functioning.
O well.. the fun begins restoring everything again..
Has anyone experienced freezing screen on their pixel 6 pro?
I just faced the issue and force rebooted by holding power and volume up until it rebooted.
I have darkliv substratum theme, latest canary magisk on latest Jan update.
I got a bootloop after installing a magisk module 'nabarswap' and had to wipe the device with Android flashtool
You should not have wiped. If you boot your phone in safe mode, no magisk modules will be activated and you can remove them.
I could be wrong here, but I believe that you need to disable verity and verification for most Magisk Modules so that this doesn't occur.
NippleSauce said:
I could be wrong here, but I believe that you need to disable verity and verification for most Magisk Modules so that this doesn't occur.
Click to expand...
Click to collapse
You don't need to disable verity & verification as long as you use Canary Magisk 23016 or later. Most Magisk mods won't modify the boot image header, at least that I know of.
fil3s said:
I got a bootloop after installing a magisk module 'nabarswap' and had to wipe the device with Android flashtool
Click to expand...
Click to collapse
In addition to what @foobar66 said about safe mode, you can also remove modules by this method, but it's easier just to disable them in safe mode like foobar66 said:
1. Turn off device
2. adb wait-for-device shell magisk --remove-modules in command prompt
3. Connect your phone to computer and turn it on.
4. Phone tries to boot and the command should be accepted
5. Wait until the command worked and the phone boots up without issues
Also, there is a Magisk Mod that will automatically disable mods if you are in a bootloop. I have it installed but haven't tested it since I haven't been in a bootloop. The developer said it supports Android 12. I've seen at least 1 person who said it works.
GitHub - Magisk-Modules-Alt-Repo/HuskyDG_BootloopSaver: Protect your system from bootloop caused by Magisk modules.
Protect your system from bootloop caused by Magisk modules. - GitHub - Magisk-Modules-Alt-Repo/HuskyDG_BootloopSaver: Protect your system from bootloop caused by Magisk modules.
github.com
Thanks for the replies. Didn't receive any notification from the XDA app.
NippleSauce said:
I could be wrong here, but I believe that you need to disable verity and verification for most Magisk Modules so that this doesn't occur.
Click to expand...
Click to collapse
No apparently you just flash normally , no need to disable verification etc , then fastboot flash boot the magisk boot image.
foobar66 said:
You should not have wiped. If you boot your phone in safe mode, no magisk modules will be activated and you can remove them.
Click to expand...
Click to collapse
I tried to not wipe but android flashtool wouldn't proceed, atleast the phone wouldn't , it just got stuck on a screen asking me to factory reset. I figured the only fix was to wipe. And since I've cloud backups of my data, it was no big deal to wipe
Cheers
I now use 'bootloop saver' which can be found on this app