Will break boot/recovery and possibly more. Magisk 20.1 and earlier ok. Bug report here. Discussion in the arter97 kernel thread, post 393 and down.
can confirm
same thing just happened to me when trying to update, says it never updated on magisk and recovery doesn't work.
Worked for me, but I'm running stock kernel. The LG V20 on the other hand is an instant fail on all variants
+1 same problem here
After reboot phone get stuck on bootloop, throwing me to fastboot mode later on. Reflashing custom kernel [r12] bring back to life recovery but still no chance to boot neiter boot_a or boot_b
I had the same issue. Flashed Arters kernel through fastboot and reinstalled previous magisk. Booted fine then.
Magisk fixed in latest canary build.
https://github.com/topjohnwu/Magisk/issues/2203#issuecomment-571069311
BeardKing said:
Magisk fixed in latest canary build.
https://github.com/topjohnwu/Magisk/issues/2203#issuecomment-571069311
Click to expand...
Click to collapse
Thanks man. That did it for me.
I had flashed the original 20.2 in both TWRP and the app. It never updated the version in the Magisk app to 20.2 and my TWRP recovery went away. My phone still booted normally and SafetyNet went back to green, but I earned a terrific battery drain.
Today, I flashed the Arter v12 boot.img to the boot partition with fastboot and installed the patched Magisk zip once TWRP came back. Reactivated Riru/Edxposed and all is right with the world. Thanks again.
Looks like a new version of Magisk Manager is up, and Magisk v20.3 to go with it.
Has anyone else run into being unable to use fastboot to reflash the kernel after attempting Magisk v20.2? My RP2's still recognizable while in (stock MR1) OS, but rebooting to bootloader and checking "fastboot devices" gives me nothing. My phone's serial shows up in the bootloader and it still matches what's recognized on ADB.
Edit: I'm on arter97's r12 kernel, using the old Minimal ADB and Fastboot package. To clarify, I'm still able to boot into and use the OS. I hope my bootloader's ok...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Confirmed Magisk 20.3 is fixed.
@Nomyth: Are you using the same USB cord you first flashed arter97's kernel with? I was using a different cord when Magisk 20.2 broke boot and was having the same issue. Went back to the cord I first flashed the kernel with and had no problems.
Also, use the most recent ADB/Fastboot from the Android web site.
BeardKing said:
Confirmed Magisk 20.3 is fixed.
@Nomyth: Are you using the same USB cord you first flashed arter97's kernel with? I was using a different cord when Magisk 20.2 broke boot and was having the same issue. Went back to the cord I first flashed the kernel with and had no problems.
Also, use the most recent ADB/Fastboot from the Android web site.
Click to expand...
Click to collapse
Thanks, I just updated and fixed the issue. Looks like it was a Windows issue with using the wrong USB driver for fastboot mode.
Related
I went to replace framework-res.apk, and now it wont go past samsung logo, please tell me I didn't brick my phone?
Please Help [email protected][email protected]!
What did you flash?, theme kernel? Be specific
I went to flash some circular battery mod, and then it crashed and won't boot.
Never mind. Do you have cwm installed? if so, flash a rom that matches the one you are on. That'll fix that issue. Next time don't flash something that isn't for the rom version that you are on.
Specifially I renamed it framework-re.apk.bak, and then about to replace it it won't boot.
Which rom version are you on? DL09? DJ05? DI01?
Dont have cwm installed, did it through root explorer.
You probably flashed a file that wasn't compatible with our phone, or isn't compatible with the ROM you're running (DI01 mod on DJ05/DL09). Reflash the ROM you're running and it should fix the problem.
Just flash the rom that you are on again.
So there's no way out? I have to loose all my data?
Also next time flash a theme that it's compatible to your rom version.
You don't have to wipe!
you can flash dj05 theme on top of dl09, but remember to flash the dl09 theme fix.
tonu42 said:
So there's no way out? I have to loose all my data?
Click to expand...
Click to collapse
If you flash the same rom you're on now, you don't have to wipe data.
I'm going to win imnuts...
But doesn't odin delete all data?
tonu42 said:
I went to flash some circular battery mod, and then it crashed and won't boot.
Click to expand...
Click to collapse
By any chance, did you make a backup of your old framework-res.apk?
And what version are you on? DI01, DJ05, DL09?
If you have Clockwork, you can use ADB to push a new framework to your phone. Just reboot into recovery, connect to your computer and open up a command prompt (on Windows):
adb push framework-res.apk system/framework/framework-re
Here's mostly stock versions of the framework:
DI01
DJ05/DL09 (works for either, but you have to rename to framework-res.apk)
The only difference in these is that I did my own little battery mod:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you had a theme installed, this will probably screw it up, reverting most stuff back to stock, but hopefully it'll at least get you booting again.
If I reboot into normal samsung recovery will adb work?
I am just gonna reflash with odin..........
tonu42 said:
I am just gonna reflash with odin..........
Click to expand...
Click to collapse
Not sure if ADB works with the stock recovery, I'm using a Voodoo kernel, so the stock recovery is gone.
But if you're flashing with Odin, you could just flash Clockwork recovery and then boot to it and use ADB. Might as well get Clockwork on your phone... with a backup, you could have been back up in just a few minutes.
Wow, this is a fascinating thread with so much confusion.
Yep it's out.
For those of you in need to manually update read below.
Download: cm-bacon-d22b777afa-to-0428073396-signed.zip (KTU84P, XNPH30O)
Install: To install the update, flash a custom recovery (TWRP recommended), boot into it, then sideload using adb sideload - if you've ever updated a Nexus device before, then you'll feel right at home, as the steps are exactly the same. TWRP will ask if you want to re-root at the end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wtf is this thread....anyways has anyone tried a clean flash yet?
just flashed it. thanks man!
Why can you flash the zip, why do you have to sideload it ?
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
I flashed it through TWRP, NO ISSUES
doalittledanse said:
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
Click to expand...
Click to collapse
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
clipcarl said:
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
Click to expand...
Click to collapse
yep. on both the stock cm recovery and twrp i get this error:
Code:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
If you've flashed any mods or made any changes to the system. It will fail.
Exclusive Member of the OnePlus One Club
If you guys flashed my Smooth Scrolling Mod, flash the revert and then try the OTA
http://forum.xda-developers.com/one...scrolling-mod-mahdi-rom-t2840934/post54762296
Basically when you're on stock ROM and if you did any changes to your /system/ then it will not update because its been modified.
does this include removal of apps ? Mine failed to sideload as well.+
Edit 1: I did do some modding of the build.prop as well this morning.
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
doalittledanse said:
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
Click to expand...
Click to collapse
Same problem here, fails at:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
Everything is stock, except Recovery. Tried with original recovery and it still fails...
Got mine to update even though the system partition was updated with a modified updater-script.
I will upload the entire zip with the updated script. For those that know what they are doing the updater-script is attached.
Edit 1: Note you do loose root. You have to install supersu again if you did have it previously (if you modified system then you did)
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Anyone tried custom kernels with ota?
Sent from my A0001 using XDA Free mobile app
C-4Nati said:
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Click to expand...
Click to collapse
look at my post.
I guess the update.zip factory image from the official site isn't truly stock. so i went with the nuclear option and just reflashed everything via fastboot. update worked perfectly now haha.
Please go to the thread here to continue the conversation....http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689
hello, i just tried to flash cloudyg2 3.3 and i have bricked my d802 16gb. i had stock lp and had rooted and installed twrp did the wipes (no internal), got the right lp bootstack and used the right settings, so i really dont know what went wrong.
the symptom is that lg logo show for a fraction of a second and then a washed out gray on top of screen that fades away slowly. also while connected in pc it reads like many many drives.
on the bright side i can enter recovery/download modes. in my original attempt i used the bumbed sign, on my tries to fix it i also used the loki one, same deal.
seems like i have no recovery file, i thought i did it with one of the programs i installed, but since i am newbie seems like i misunderstood. so no recovery file
any help?
solution found:
1.Download the latest TWRP from blastagator here.
2.Flash it with your current recovery, reboot into that new recovery.
3.Download SRKG2 rom (by somboons) here.
4.This rom is a full stock rom with some debloat and custom camera. Wipe /system/ /cache/ /dalvik-cache/ /data/ and flash it (choose any options, it's not important since you'll be only installing this rom because it also upgrades other partitions to a lollipop supported version.
5.Boot into the rom and reboot into recovery again. (If you are unable to boot or the boot is taking too long like 10 minutes, shut down, go to recovery again and perform a factory reset, the one that makes you type 'yes' in the keyboard and you should be fine).
6.Download CloudyG2 3.1 and wipe /system/ /cache/ /dalvik-cache/ /data/ again.
7.Flash the rom choosing the correct version of your phone (among other preferences) in the aroma installer.
8.Boot and enjoy!
i cant post link of the solution cause i am new, but many thanks to him. i still dont understand what went wrong, but my hypothesis is that i shouldnt install the lp bootloader since i was in lp anyway.
i hope it helps anyone with similar problem.
cheers
you are in qhsusb bulk 9006 souse srktool to unbrick
---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------
that becuase wrong bootleader u must use bump kk bootleader then reboot recovery and flash rom
Can not change lte to 3g can someone please...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-D800 using Tapatalk
I have flashed stock MM rom , now whenever i try to flash any kernel twrp freezes and phone restarts to recovery, I've used this armoa supported TWRP https://forum.xda-developers.com/galaxy-j5/development/3-customs-recoverys-galaxy-j5-2015-t3560266
latest official TWRP and also latest Orangefox, all had the same issue, what should I do?
UPDATE: Problem resolved after reflashing the stock and debloating it, not sure which one did the trick but anyways it worked!
A.Rahman96 said:
I have flashed stock MM rom , now whenever i try to flash any kernel twrp freezes and phone restarts to recovery, I've used this armoa supported TWRP https://forum.xda-developers.com/galaxy-j5/development/3-customs-recoverys-galaxy-j5-2015-t3560266
latest official TWRP and also latest Orangefox, all had the same issue, what should I do?
Click to expand...
Click to collapse
If you can flash rom, Gapps or any other things expect kernel, then your twrp works fine and you flash the wrong kernel for that one(you flashed the another model)
And maybe it's bc of your twrp that can't flash kernel and need the special one that the kernel dev should be mentioned
Would you please share the link or give me more details?
amirizad_7436 said:
If you can flash rom, Gapps or any other things expect kernel, then your twrp works fine and you flash the wrong kernel for that one(you flashed the another model)
And maybe it's bc of your twrp that can't flash kernel and need the special one that the kernel dev should be mentioned
Would you please share the link or give me more details?
Click to expand...
Click to collapse
yes, I can flash everything else except kernels.
the issue is all TW 6.0.1 kernels here have their links removed so I just have them from re-uploaders outside of xda forums, here is a kernel of a total of 3 kernels that don't even flash no matter what recovery I'm using
http://www.mediafire.com/file/040tj212gjqfzzp/J500H-Kraken-R4_Nyell.zip/file
and thanks for the reply
update: the recovery doesn't freeze in the middle of the procedure. it freezes at the very beginning like "checking digest files" and things like that
A.Rahman96 said:
yes, I can flash everything else except kernels.
the issue is all TW 6.0.1 kernels here have their links removed so I just have them from re-uploaders outside of xda forums, here is a kernel of a total of 3 kernels that don't even flash no matter what recovery I'm using
http://www.mediafire.com/file/040tj212gjqfzzp/J500H-Kraken-R4_Nyell.zip/file
and thanks for the reply
update: the recovery doesn't freeze in the middle of the procedure. it freezes at the very beginning like "checking digest files" and things like that
Click to expand...
Click to collapse
How do you install kernel?
Would you explain
It's img file or zip file
amirizad_7436 said:
How do you install kernel?
Would you explain
It's img file or zip file
Click to expand...
Click to collapse
it's a zip flashable file
A.Rahman96 said:
it's a zip flashable file
Click to expand...
Click to collapse
That's the problem. Unpack the zip and there should be a boot.img inside. No wonder it wasn't working.
garylawwd said:
That's the problem. Unpack the zip and there should be a boot.img inside. No wonder it wasn't working.
Click to expand...
Click to collapse
already tried that, but have you looked at the file? it has patches for wifi and things like that, when I extracted the zip file and flashed only the boot.img the rom worked but without wifi and with a lot of bugs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A.Rahman96 said:
I have flashed stock MM rom , now whenever i try to flash any kernel twrp freezes and phone restarts to recovery, I've used this armoa supported TWRP https://forum.xda-developers.com/galaxy-j5/development/3-customs-recoverys-galaxy-j5-2015-t3560266
latest official TWRP and also latest Orangefox, all had the same issue, what should I do?
Click to expand...
Click to collapse
Try using an earlier TWRP, the 3.3 version has trouble flashing some zips
Problem resolved after reflashing the stock and debloating it, not sure which one did the trick but anyways it worked!
Hi there,
I've recently taken the plunge and decided to root my phone. I followed all the instructions and everything went fine except I can't get Magisk to install. When I run root checker it confirms my phone is successfully rooted, see screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I go into Magisk it fails the installation saying 'Unable to check signature'. See screenshots below
Looking at the installation instructions here https://topjohnwu.github.io/Magisk/install.html I believe as Ramdisk is 'Yes', then my phone is ready to install Magisk. I believe that if I patch my phone with a boot.img file then I should be able to successfully install Magisk. However, 1) I'm not sure it will given the error I'm getting and 2) wherever I search I cannot seem to download the correct firmware for my phone to be able to get the correct boot.img file that I need. Here are the screenshots showing the installed software version.
I'd be super appreciative to anyone that can advise me as to what to do next to try and resolve the installation issues so that I can benefit from the wonders of Magisk.
Thank you
f19fox said:
Hi there,
I've recently taken the plunge and decided to root my phone. I followed all the instructions and everything went fine except I can't get Magisk to install. When I run root checker it confirms my phone is successfully rooted, see screenshot.
View attachment 5290275
But when I go into Magisk it fails the installation saying 'Unable to check signature'. See screenshots below
View attachment 5290281View attachment 5290283
Looking at the installation instructions here https://topjohnwu.github.io/Magisk/install.html I believe as Ramdisk is 'Yes', then my phone is ready to install Magisk. I believe that if I patch my phone with a boot.img file then I should be able to successfully install Magisk. However, 1) I'm not sure it will given the error I'm getting and 2) wherever I search I cannot seem to download the correct firmware for my phone to be able to get the correct boot.img file that I need. Here are the screenshots showing the installed software version.
View attachment 5290293View attachment 5290297
I'd be super appreciative to anyone that can advise me as to what to do next to try and resolve the installation issues so that I can benefit from the wonders of Magisk.
Thank you
Click to expand...
Click to collapse
Flash magisk zip in via recovery
Austinredstoner said:
Flash magisk zip in via recovery
Click to expand...
Click to collapse
Hi. Thank you for your reply and advice. I flashed Magisk using TWRP recovery but it still won't install. Here is the screenshot. I also uninstalled the App and re-downloaded as per these instructions https://bit.ly/32P3Z9z but I still get the same error
Do you or anyone else have any more suggestions please?
Thanks!
@f19fox: Apologies to be hijacking your thread.
Build Number: NMF26X.J510FNXXU2BRJ4
Android Running Version: 7.1.1
I downloaded the IMG file of the BRJ4 raw boot image from firmware.mobi, successfully patched it via the Magisk app, and subsequently flashed the patched boot image via TWRP (selecting the boot partition within TWRP).
However, the Magisk card within the app still displays N/A within the app.