Hi Guys,
I've been using sokkoban's B596 ROM for a while now and it had Magisk 12 installed already.
Today I got a notification from magisk to update to new version, I downloaded it from app and it installed and prompted for reboot.
After reboot the phone got stuck on Boot Logo for a couple of seconds and then my phone started. I opened magisk to see what's new but what I saw was the old version of Magisk was also uninstalled and now its saying me to download and install magisk 13. When I touch the download button a zip file just got downloaded and nothing else happened.
Can someone please assist me on how to install it again ??
Any help would be greatly appreciated.
{
"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"
}
hbilalshah said:
Hi Guys,
I've been using sokkoban's B596 ROM for a while now and it had Magisk 12 installed already.
Today I got a notification from magisk to update to new version, I downloaded it from app and it installed and prompted for reboot.
After reboot the phone got stuck on Boot Logo for a couple of seconds and then my phone started. I opened magisk to see what's new but what I saw was the old version of Magisk was also uninstalled and now its saying me to download and install magisk 13. When I touch the download button a zip file just got downloaded and nothing else happened.
Can someone please assist me on how to install it again ??
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Magisk 13.1 or 13? 13.1 isn't working on stock roms, only 13.
D1stRU3T0R said:
Magisk 13.1 or 13? 13.1 isn't working on stock roms, only 13.
Click to expand...
Click to collapse
13.1 is showing up
hbilalshah said:
13.1 is showing up
Click to expand...
Click to collapse
I know, but it's not working
hbilalshah said:
13.1 is showing up
Click to expand...
Click to collapse
Let me be clear. The new stable version of Magisk (v13.1) doesn't work on the stock ROM. For me it does boot, just takes a long time, but there's no Magisk Manager and if installed it lets you know Magisk is not installed. Get one of the betas that work (the last one does for me) or v12
Just installed last beta (c4377ed) and all works fine. SN passes and Play Store says my device is certified
Sonofapo said:
Just installed last beta (c4377ed) and all works fine. SN passes and Play Store says my device is certified
Click to expand...
Click to collapse
Link please..??
And a little bit guide on how to install as I have never installed it before
hbilalshah said:
Link please..??
And a little bit guide on how to install as I have never installed it before
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 download last zip file (c4377ed)
Installation is pretty simple restore boot image from recovery to do a clean install and flash this zip file from TWRP. Then download Magisk manager apk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) and install it.
Sonofapo said:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 download last zip file (c4377ed)
Installation is pretty simple restore boot image from recovery to do a clean install and flash this zip file from TWRP. Then download Magisk manager apk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) and install it.
Click to expand...
Click to collapse
Restore boot image..??
How to do that
hbilalshah said:
Restore boot image..??
How to do that
Click to expand...
Click to collapse
if you have never installed any other root method (for example Chainfire's SuperSu zip) you can avoid this step. Otherwise it is safer to restore a stock boot image via TWRP backup or extracting a new one from your rom file (UPDATE.APP or whatever) and flashing it via Fastboot. Make sure to install the correct boot image according to you current rom installed on your device
Sonofapo said:
if you have never installed any other root method (for example Chainfire's SuperSu zip) you can avoid this step. Otherwise it is safer to restore a stock boot image via TWRP backup or extracting a new one from your rom file (UPDATE.APP or whatever) and flashing it via Fastboot. Make sure to install the correct boot image according to you current rom installed on your device
Click to expand...
Click to collapse
I want to add you can flash images in TWRP
JpegXguy said:
I want to add you can flash images in TWRP
Click to expand...
Click to collapse
I don't think web have the dame rom version... Mine is b598 Sokkoban's rom
Go to this link and download the required firmware
After that extract the boot.img from update.app file and flash it... that should do
amageek said:
Go to this link and download the required firmware
After that extract the boot.img from update.app file and flash it... that should do
Click to expand...
Click to collapse
I always recommend this site
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
Sonofapo said:
I don't think web have the dame rom version... Mine is b598 Sokkoban's rom
Click to expand...
Click to collapse
Sokkobans ROM is stock with some more apps and settings changed. You can use the boot image from stock.
You can always get the FULL (and OTA, but we want full to extract) from here: http://hwmt.ru/oth/HWFF/info/view.php?find_model=ale-l21
UPDATE: Magisk v13.2 has been released, it works fine for me
Yes I can confirm it too, magisk 13.2 is all good.
D1stRU3T0R said:
Magisk 13.1 or 13? 13.1 isn't working on stock roms, only 13.
Click to expand...
Click to collapse
Thats why do never update this crap?
Magisk 13.1 doesn't work, but 13.2 and 13.3 works very good
RootingPro-18 said:
Thats why do never update this crap?
Click to expand...
Click to collapse
But 13.2 and 13.3 works
RootingPro-18 said:
Thats why do never update this crap?
Click to expand...
Click to collapse
If you want SafetyNet to pass you should update. Also changes are coming to modules... Anyhow 13.3 passes fine on B602 I presume. Not on B604 because it's not August 1st yet
Related
So Guys ROM twrp Root etc Now available for MI max 2. [oxygen 2]
You can Download official ROM from http://en.miui.com/a-234.html
and Flash it with MI flash.
or if you have dead Device follow deep Flashing Guide Here.https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055
twrp ported From mido Download Here
Flash with fastboot
Code:
fastboot flash recovery recovery.img
Flash magisk From here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
in trouble watch video-
Thank you! TWRP worked as intended, installed root manually. Donated as well.
TiMbl4 said:
Thank you! TWRP worked as intended, installed root manually. Donated as well.
Click to expand...
Click to collapse
ok thanks for Donation..
Lineage OS available https://forum.xda-developers.com/mi-max-2/development/linageos-14-1-mi-max-2-t3634864
Great toolkit but I have a couple questions. In the instructions on your site and youtube video it has a step to flash noverity. Is this really needed or is it just a precaution? Also, could I just flash the recovery via fastboot and then just pull noverity and magisk from their source and flash them? I always like to flash things myself the normal way so I understand what's going on.
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
XN Logos said:
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
Click to expand...
Click to collapse
Thanks for the quick response. I have one more question. Can I substitute SuperSU in place of magisk? After using the toolkit, I tried to update magisk to the latest version (13.2) using magisk manager but instead it gave an error. It didn't brick my phone or anything but when I rebooted and went into magisk manager it showed the phone was still properly rooted but reported that magisk wasn't installed. Not sure if it's a compatibility issue or not. I also tried flashing the latest version of magisk using twrp and got the same error in magisk manager upon reboot.
At any rate, do you see any problem with using SuperSU instead?
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
XN Logos said:
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
Click to expand...
Click to collapse
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Did you have to unlock the bootloader for installing twrp?
ikecomp said:
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Click to expand...
Click to collapse
unlock with developer rom
XN Logos said:
unlock with developer rom
Click to expand...
Click to collapse
Since 5 days i have been trying to unlock bootloader. Every time I get "Device not bound to account". I have tried everything. Can you help me?? I am already on developer rom..
yes that means You have not applied for unlock, First of all apply for unlock then when you receive Confirmation msg wait 72 hrs, then login mi unlock app with same account and then try to unlock
Magisk not detect root
{
"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"
}
I follow all instruction,i flash no verity and flash xnmagisk.zipafter reboot magisk appear like that? Have format but still not detect root, can root manually flash superusu but i want magisk to for hide root. So what next stepp for solve this problem? Let me know. Thanks
Hi guys, any idea why when I flash magisk 14.0 over a fresh 7.9.7 global developer rom I get CTS profile mismatch? It still shows safetynet as passing but android pay refuses to work. Also, is it safe to install OTA updates with magisk flashed?
How to root after flashing the official miui9 ? (my device is rooted miui 8.5)
please help (Device Mi Max 2 )
All I get is the option to patch boot img and the option to install the zip.
{
"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"
}
You can only do direct install if the Manager has superuser access. In other words, if you already have Magisk installed and want to install an update. First install you need to patch the boot image and flash manually, or download the zip and flash in recovery.
Didgeridoohan said:
You can only do direct install if the Manager has superuser access. In other words, if you already have Magisk installed and want to install an update. First install you need to patch the boot image and flash manually, or download the zip and flash in recovery.
Click to expand...
Click to collapse
Thanks so much! boot image has been patched, i think. Now, how do i install magisk via stock recovery? how do i navigate to the
magisk manager folder?
fwng said:
Thanks so much! boot image has been patched, i think. Now, how do i install magisk via stock recovery? how do i navigate to the
magisk manager folder?
Click to expand...
Click to collapse
You can't install it with a stock recovery.
Depending on your device you need to use fastboot, ODIN or whatever is applicable.
If it's a non-Samsung device fastboot usually works. While booted to bootloader and with your device hooked up to your computer:
Code:
fastboot flash boot patched_boot.img
If you don't have adb and fastboot installed, get it here:
https://developer.android.com/studio/releases/platform-tools.html
If you can't get it to work, there's usually plenty of help and info in your device's forum.
Didgeridoohan said:
You can't install it with a stock recovery.
Depending on your device you need to use fastboot, ODIN or whatever is applicable.
If it's a non-Samsung device fastboot usually works. While booted to bootloader and with your device hooked up to your computer:
Code:
fastboot flash boot patched_boot.img
If you don't have adb and fastboot installed, get it here:
https://developer.android.com/studio/releases/platform-tools.html
If you can't get it to work, there's usually plenty of help and info in your device's forum.
Click to expand...
Click to collapse
That worked! thanks so much! sorry to trouble you!
fwng said:
That worked! thanks so much! sorry to trouble you!
Click to expand...
Click to collapse
Awesome! And it's no trouble... I'm here because I like to help. :good:
Hi,
I'm facing a strange issue. My note 8 exynos INS dual SIM has the Ironman rom installed and running. I had magisk root selected and installed. These days I get a notification about a magisk update (v16.0) when I tap the notification it takes me to magisk start screen where it shows magisk as not installed with the option to download the boot image or patch the boot file.
I then download the new zip, get into twrp recovery, flash the zip and reboot. After thd phone starts up and i click the magisc app icon magisk opens and shows me that the latest version is installed.
However in a random duration which can be 15 min or 1 hrs or 3 hrs, the update notification pops up again and tapping it shows magisk as not being installed with an older version in red below the latest version in green.
I have been using magisk on my devices for long and this is the fifth device SM-N950FD that I'm using it now and have seen this the first time on nougat 7.1.1.
Can I get some help regarding this. Apologies for this if it is a noob question or a duplicate but I couldn't find this anywhere so decided to post.
Thanks centaur31
centaur31 said:
Hi,
I'm facing a strange issue. My note 8 exynos INS dual SIM has the Ironman rom installed and running. I had magisk root selected and installed. These days I get a notification about a magisk update (v16.0) when I tap the notification it takes me to magisk start screen where it shows magisk as not installed with the option to download the boot image or patch the boot file.
I then download the new zip, get into twrp recovery, flash the zip and reboot. After thd phone starts up and i click the magisc app icon magisk opens and shows me that the latest version is installed.
However in a random duration which can be 15 min or 1 hrs or 3 hrs, the update notification pops up again and tapping it shows magisk as not being installed with an older version in red below the latest version in green.
I have been using magisk on my devices for long and this is the fifth device SM-N950FD that I'm using it now and have seen this the first time on nougat 7.1.1.
Can I get some help regarding this. Apologies for this if it is a noob question or a duplicate but I couldn't find this anywhere so decided to post.
Thanks centaur31
Click to expand...
Click to collapse
Does the ROM come with Magisk pre-installed? If so, I'd reflash the ROM without Magisk, if possible, make sure that there are no traces of Magisk on the device (Manager included) and install Magisk manually.
A better place for this post would have been the general support thread.
H
fwng said:
All I get is the option to patch boot img and the option to install the zip.
Click to expand...
Click to collapse
How do I install a zip?
{
"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"
}
https://forums.oneplus.com/threads/android-q-developer-preview-5-for-oneplus-7-pro-and-7.1097600/
WORKING fine just testing it for the past few minutes-hour =) enjoy...
*** Update
3/9 https://forums.oneplus.com/threads/oxygen-os-open-beta-1-for-the-oneplus-7-pro-and-7.1099154/
They just release OB (OPEN BETA 1) today not stable beta as they said
***Update 17/9 open beta 2 released
https://www.xda-developers.com/oneplus-7-pro-second-android-10-beta-oxygenos-open-beta-2/
Are there any bugs that you found? on DP4 my 4G signal is often down
I'm updating from 9.5.11
I can't confirm that will erase data or not
So far so good. Android Auto works as well, which is a huge bonus. OnePlus gestures work great too. So far haven't run into any bugs.
Edit: pulling down the notification shade is a bit laggy. But I didn't do a data clear from an original upgrade from Pie. Will try that tomorrow. Reboot cleared it up for now.
Dameon87 said:
So far so good. Android Auto works as well, which is a huge bonus. OnePlus gestures work great too. So far haven't run into any bugs.
Edit: pulling down the notification shade is a bit laggy. But I didn't do a data clear from an original upgrade from Pie. Will try that tomorrow. Reboot cleared it up for now.
Click to expand...
Click to collapse
Thanks for clarifying about Android auto and ... . Was waiting for this to try the 10, the UI design of oos is really outdated and not modern, i was hoping for a more modern look
Is it possible to root this DP?
5G support?
Can I put this on my T-Mobile OnePlus 7 pro
strictlyphat said:
Can I put this on my T-Mobile OnePlus 7 pro
Click to expand...
Click to collapse
Yes. I've bootloader unlocked the T-Mobile ROM and installed TWRP, then I just flashed the version before this one (i.e., DP4) in TWRP. I was pleasantly surprised when all my icons were their same places after reboot! If you haven't bootloader unlocked, you could backup important files to external storage before MSM tool converting to international then updating DP5 locally. TBH, I'd just wait for T-Mobile to OTA their official carrier variant of Android 10.
Runs much smoother than DP4 for me. The settings menu design was also changed I think.
Does the standard installtion method with twrp and magisks still work?
strictlyphat said:
Can I put this on my T-Mobile OnePlus 7 pro
Click to expand...
Click to collapse
Yes if you are sim unlocked and on the international rom. I have the TMobile version also
ibchh said:
Does the standard installtion method with twrp and magisks still work?
Click to expand...
Click to collapse
not for me im unrooted now
Aside from more frame drops than I used to have on stable pie it's running fine! (dirty flashed it so that might cause them) Animations are really sleek.
sille said:
not for me im unrooted now
Click to expand...
Click to collapse
Did you flash magisks before entering the OS?
Diegc5 said:
Is it possible to root this DP?
Click to expand...
Click to collapse
Yes (see attached).
I installed the full DP5 from TWRP, then immediately installed TWRP .52 and Magisk 19.4, rebooted back into TWRP and reinstalled both TWRP and Magisk again.
Rebooted back into TWRP, cleared cache, data and internal storage.
I already had DP4 installed beforehand.
djsubterrain said:
Yes (see attached).
I installed the full DP5 from TWRP, then immediately installed TWRP .52 and Magisk 19.4, rebooted back into TWRP and reinstalled both TWRP and Magisk again.
Rebooted back into TWRP, cleared cache, data and internal storage.
I already had DP4 installed beforehand.
Click to expand...
Click to collapse
I tried before using twrp but error 7...so i flash from system update and then flash magisk on inactive slot....reboot and then back to magisk flash twrp .52 and magisk canary....reboot...and go to recovery and wipe internal data and reboot....
Maybe this a long way but working on u with failed update on twrp....
abhy27 said:
I tried before using twrp but error 7...so i flash from system update and then flash magisk on inactive slot....reboot and then back to magisk flash twrp .52 and magisk canary....reboot...and go to recovery and wipe internal data and reboot....
Maybe this a long way but working on u with failed update on twrp....
Click to expand...
Click to collapse
I try to flash by fastboot, it does the process correctly but in the end it doesn't start in twrp- any solution?
I couldn't flash by twrp as I had error 7
Many thanks
Dameon87 said:
So far so good. Android Auto works as well, which is a huge bonus. OnePlus gestures work great too. So far haven't run into any bugs.
Edit: pulling down the notification shade is a bit laggy. But I didn't do a data clear from an original upgrade from Pie. Will try that tomorrow. Reboot cleared it up for now.
Click to expand...
Click to collapse
Lots of people on the OP Fourms say AA doesn't work for them
abhy27 said:
I tried before using twrp but error 7...so i flash from system update and then flash magisk on inactive slot....reboot and then back to magisk flash twrp .52 and magisk canary....reboot...and go to recovery and wipe internal data and reboot....
Maybe this a long way but working on u with failed update on twrp....
Click to expand...
Click to collapse
It depends which version you come from to DP5, error 7 is usually due to firmware incompatibility.
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705
https://forum.xda-developers.com/v20/how-to/warning-dont-upgrade-version-magisk-20-2-t4028577
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
omega552003 said:
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705
https://forum.xda-developers.com/v20/how-to/warning-dont-upgrade-version-magisk-20-2-t4028577
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
Click to expand...
Click to collapse
I have the same in LG G6.
It only kills boot.img, the system cannot boot and the smartphone remains in fastboot mode.
If you have TWRP recovery and you use Magisk or other boot.img modification tools, you should always have a backup with the latest boot.img
After restoring boot.img from a backup (before upgrading Magisk), you will not have to install any earlier working Magisk.
LG-H870 V30a
Doing the same thing on my Razer Phone 2. Magisk 20.1 working fine.
This is exactly what happened to me. I lost all my data trying to figure out what is going on. Now flashing Stock Root Oreo. Damn it.
BeardKing said:
Doing the same thing on my Razer Phone 2. Magisk 20.1 working fine.
Click to expand...
Click to collapse
You running arter97's kernel?
I just upgraded on my G5, but didnt reboot yet. Can I flash 20.1 and be good?
omega552003 said:
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
...
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
Click to expand...
Click to collapse
slavomes said:
I have the same in LG G6.
It only kills boot.img, the system cannot boot and the smartphone remains in fastboot mode.
If you have TWRP recovery and you use Magisk or other boot.img modification tools, you should always have a backup with the latest boot.img
After restoring boot.img from a backup (before upgrading Magisk), you will not have to install any earlier working Magisk.
LG-H870 V30a
Click to expand...
Click to collapse
totalnoob34 said:
I just upgraded on my G5, but didnt reboot yet. Can I flash 20.1 and be good?
Click to expand...
Click to collapse
I had this happen with my G5 and 20.1 today. Had to boot into TWRP with the hardware buttons and restore the boot partition from my latest TWRP backup to bring the phone back to life.
jdc said:
I had this happen with my G5 and 20.1 today. Had to boot into TWRP with the hardware buttons and restore the boot partition from my latest TWRP backup to bring the phone back to life.
Click to expand...
Click to collapse
I don't have a twrp backup, though. Was it an image file? I think magisk creates one automatically.
Sent from my LG-H850 using XDA Labs
totalnoob34 said:
I don't have a twrp backup, though. Was it an image file? I think magisk creates one automatically.
Sent from my LG-H850 using XDA Labs
Click to expand...
Click to collapse
Check this.
Someone wrote about this backup files. I have 3 folder with different files, so you have to know which is latest backup.
{
"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"
}
LG-H870 V30a
Let's try to figure out why things aren't working... If you're willing to help, take a look here:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post81394545
slavomes said:
Check this.
Someone wrote about this backup files. I have 3 folder with different files, so you have to know which is latest backup.View attachment 4918541View attachment 4918543
LG-H870 V30a
Click to expand...
Click to collapse
It is easy. Just check the date and time files are created. Then identify the file that has a time stamp close to the time you updated Magisk to 20.2. That particular file is the right backup.
Confirm the problem. I own an Lg G3 D855 with the v30o. Fortunately i messed up things one day before trying to fix the fail of safetynet. A module caused my phone bootloop so i manually removed the module with the TWRP from the /data dir. So when i got the update 20.2 my phone had the same issue, my mind directly went to Magisk and installed the 20.1 via TWRP and everything's fine again.
I've installed Magisk 20.1 via Orange Fox Recovery. Still hanging in fastboot. (Official TWRP can't mount /data.)
Any suggestions? LG G6.
Cloonix said:
I've installed Magisk 20.1 via Orange Fox Recovery. Still hanging in fastboot. (Official TWRP can't mount /data.)
Any suggestions? LG G6.
Click to expand...
Click to collapse
G6 here, same issue. I dirty flashed my ROM and Magisk 19.3 and am back in business.
Nothing special about 19.3, it was just the version I happened to have a zip handy.
Latest magisk 20.3 canary (20202) working fine on lg g5 android 9 and 10.
Sent from my LG G5 using XDA Labs
20.3 and still the same issue. Reverted again to 20.1 (LG G3)
leopseft said:
20.3 and still the same issue. Reverted again to 20.1 (LG G3)
Click to expand...
Click to collapse
The problem that this thread is about, for the G5, G6, V20, etc, has been confirmed to be fixed with Magisk v20.3.
So, you might have a different issue and need to figure out what that is and provide details about it.
Didgeridoohan said:
The problem that this thread is about, for the G5, G6, V20, etc, has been confirmed to be fixed with Magisk v20.3.
So, you might have a different issue and need to figure out what that is and provide details about it.
Click to expand...
Click to collapse
It sure works on my G6
omega552003 said:
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705
https://forum.xda-developers.com/v20/how-to/warning-dont-upgrade-version-magisk-20-2-t4028577
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
Click to expand...
Click to collapse
how . pleas tell are we to flash a stock boot image when computer fastboot is not recognised by phone fastboot?
computer see's and id's phone. phone does not see computer.
fast boot is the onlything working on the phone. perioud.
Here you can find several patched boot.img files for various stock rom system versions of Redmi 7A.
https://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Note: The one for xiaomi.eu is custom rom, not stock EU.
If you can't find a patched boot.img for your version, you can also patch it yourself with this tool:
http://www.mediafire.com/file/c5e0idf6cy5ap25/patcher.7z/file
(follow instructions in readme file; credits to Russian 4pda forum)
Where i can find xiaomi.eu ROM for this device?
NV-Dev said:
Where i can find xiaomi.eu ROM for this device?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261652844
Can you please upload patched boot for 11.0.2 indian rom???
Can you make a patched boot for the Mokee rom because when I try to patch it with the patcher it has ramdisk error. Can you help me?
anonymousfun122 said:
Can you make a patched boot for the Mokee rom because when I try to patch it with the patcher it has ramdisk error. Can you help me?
Click to expand...
Click to collapse
Here for you
Mokee_boot.img
{
"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"
}
Not working for me
Auto Reboot to recovery
It worked
sjcbank said:
Here for you
Mokee_boot.img
Click to expand...
Click to collapse
Thank you so much !!! It worked instantly . I was trying weeks to make magisk working on the mokee rom.
Thank you !!
Hey,
I have MIUI v10.2.6.0.PCMINXM(Indian version), actually I downgraded to this version. Please help me install Mokee on my device. Enlist all the steps I need to take from scratch.
Your prompt response would be really appreciated.
Tenome7 said:
Hey,
I have MIUI v10.2.6.0.PCMINXM(Indian version), actually I downgraded to this version. Please help me install Mokee on my device. Enlist all the steps I need to take from scratch.
Your prompt response would be really appreciated.
Click to expand...
Click to collapse
Any rom version can install mokee. It's very easy, anyone can do it.
I am 60 years old, I am Vietnamese, I do not know English, all instructions are available online, I use Google, Google Chrome and Google translate.
sjcbank said:
Any rom version can install mokee. It's very easy, anyone can do it.
I am 60 years old, I am Vietnamese, I do not know English, all instructions are available online, I use Google, Google Chrome and Google translate.
Click to expand...
Click to collapse
I've been toying around with Android since it's Lollipop versions, rooting them, intalling custom ROMs etc. Probably 6 years. More than 7 devices.
As far as installing a custom ROM on this phone (Redmi 7A) is concerned, the different versions, like Indian, Global have different drivers or HAL's.
So, after successfully booting up into MOKEE OS on my variant 3-4 times, Torch, Audio, Video, Calls...... Nothing worked.
And to be very honest, there was nothing mentioned about this in MOKEE OS thread, as to which version of this device is not compatible with the ROM. The only reason I messed up was because the introduction of GSI ROMs has made the custom ROM creation process easier, but introduced a ****load of work in some devices, and ending up causing trouble.
This was the reason I requested all the steps in the thread so I could verify if I was missing some important step as far as the Indian variant is considered.
But thanks to everyone, I successfully booted Mokee ROM with everything working on my variant, including superuser privileges.
Also I messed up partitions in TWRP, and ended up with only 22gigs of Internal storage available, lol.
Thanks.
Tried @Tenome7 patched boot file for latest nightlly mokee OS 10, it bootloops, patched my own boot file, it still boot loops.
It seems impossible to get magisk working in mokee OS.
Ok I figured it out, AFTER you flash the patched boot.img you need to format the data partition, you'll loose all your data, however the ROM will boot.
I'm running Android 10 mokee os, more stable and no bugs compared to lineage os 17 rom
cg730620 said:
Here you can find several patched boot.img files for various stock rom system versions of Redmi 7A.
Click to expand...
Click to collapse
Hi
Do you have a patched boot.img for my 7A 11.0.18.0 (PCMEUXM) ?
Thanks
axy_david said:
Tried @Tenome7 patched boot file for latest nightlly mokee OS 10, it bootloops, patched my own boot file, it still boot loops.
It seems impossible to get magisk working in mokee OS.
Click to expand...
Click to collapse
Sorry for being so late to reply here. I would suggest using MIUI v10.2.10.0 as the base over which the Mokee OS needs to be installed.
As far as root is concerned, I tried Magisk but it gave me bootloops every time. As an alternative to getting root, I flashed the AddonSU installer which I downloaded from the Mokee Official site. You would just need to find it on the website.
I hope this helps. If you have further doubts, I'll stay a bit more active here. :fingers-crossed:
I want to unroot, but when i choose restore images in magisk manager it says stock backup doesnt exist. I downloaded the patched boot and stock boot.img prior to rooting, i didnt use magisk to patch the stock boot. What do i do now, i want to unroot and install ota on my xiaomi mi a3.
Can anybody help me?
I need the new version of patcher and the creator's website doesn't load me correctly.
Anyone have got pine 11.0.7 global patched boot image??? Cz yaalex patcher is down showing internal error
redmi7a
Hi
carried out
bootfromrecovery.bat - Reboot to recovery, connect to PC, install adb driver and run this file. this will extract boot.img from running phone, patch it on the fly and flash back patched boot.img
..but it didn't happen
* Requires internet connection. (it downloads latest Magisk release during process)
..I still don't have root
someone will help
Thank you
I asked the developer about a similar issue with the downloadable patcher, and he suggested me to try with the online one, which is more up to date.
https://patcher.yaalex.xyz/
romam suchanek said:
Hi
carried out
bootfromrecovery.bat - Reboot to recovery, connect to PC, install adb driver and run this file. this will extract boot.img from running phone, patch it on the fly and flash back patched boot.img
..but it didn't happen
* Requires internet connection. (it downloads latest Magisk release during process)
..I still don't have root
someone will help
Thank you
Click to expand...
Click to collapse