Related
As usual, Am not responsible for you bricking
Your phone or starting a thermonuclear war or blaming for
The action you took by yourself. Flash at your own risk.
I tested it on mine X510 and it worked for me.
Click to expand...
Click to collapse
Finally after a lot of hard work I successfully install
Xposed Framework sdk22 for infinix hot 2 X510
To install you have to first install TWRP for X510
How to install TWRP On Infinix x510 Click here
Download Xposed Framework by Rovo89 Click here
Make sure you select sdk22 for LP 5.1 & 5.1.1
Flash the framework zip
Wipe Cache and Dalvik cache
Reboot System
Install Xposed apk
Enjoy.
If this is helpful please hit the thanks button.....
awesome job! thanks for this!
could you also give us tutorial on how to backup the original recovery and rom, prior to installing TWRP
txpxsx said:
awesome job! thanks for this!
could you also give us tutorial on how to backup the original recovery and rom, prior to installing TWRP
Click to expand...
Click to collapse
OK, Am not ready for a full tutorial now but using
SP flash tool you can do a readback of the original
Recovery.
You can also get it from my other posts about
Stock firmware, download only the stock recovery
And replace it with the one in TWRP folder and
Flash it with SP flash tool or with flashify if you are
Rooted.
Bolumstar said:
Finally after a lot of hard work I successfully install
Xposed Framework sdk22 for infinix hot 2 X510
To install you have to first install TWRP for X510
How to install TWRP On Infinix x510 Click here
Download Xposed Framework by Rovo89 Click here
Make sure you select sdk22 for LP 5.1 & 5.1.1
Flash the framework zip
Wipe Cache and Dalvik cache
Reboot System
Install Xposed apk
Enjoy.
If this is helpful please hit the thanks button.....
Click to expand...
Click to collapse
I tried this but got a bootloop when optimizing applications.
I did forget to wipe the cache after.
I will try again later.
anarchtic said:
I tried this but got a bootloop when optimizing applications.
I did forget to wipe the cache after.
I will try again later.
Click to expand...
Click to collapse
Always wipe Cache and Dalvik cache before flashing
Any zip from recovery and some even wipe again
After flashing as an added precaution. It's a good
Habit and saves you a lot of bugs and boot loops
Bolumstar said:
Always wipe Cache and Dalvik cache before flashing
Any zip from recovery and some even wipe again
After flashing as an added precaution. It's a good
Habit and saves you a lot of bugs and boot loops
Click to expand...
Click to collapse
Yup I was in a rush haha, but after clearing the cache its all good now, my stock android one rom has more custimzation then cyanogenmod haha
Bolumstar said:
Finally after a lot of hard work I successfully install
Xposed Framework sdk22 for infinix hot 2 X510
To install you have to first install TWRP for X510
How to install TWRP On Infinix x510 Click here
Download Xposed Framework by Rovo89 Click here
Make sure you select sdk22 for LP 5.1 & 5.1.1
Flash the framework zip
Wipe Cache and Dalvik cache
Reboot System
Install Xposed apk
Enjoy.
If this is helpful please hit the thanks button.....
Click to expand...
Click to collapse
Tried that and bootloop during optimizing apps and yes I did wipe cache and dalvik cache
D3VI0US said:
Tried that and bootloop during optimizing apps and yes I did wipe cache and dalvik cache
Click to expand...
Click to collapse
It's important to flash SuperSU zip first before
Xposed Framework zip.
I've noticed the system restarting during apps
Optimization once or twice after flashing some zip
But it later completed the optimization after the
Restart so I didn't bother to look at the lst_kmsg
Try clearing cache and Dalvik cache again
If the issue persist, restore your system,
Flash SuperSU clear cache and Dalvik cache
Restart system.
Go into recovery again and flash the xposed Framework
Clear cache and Dalvik cache and restart.
Please always make sure that Md5 checksum is ticked
In TWRP before flashing Any zip or restoring any
Backup
Bolumstar said:
It's important to flash SuperSU zip first before
Xposed Framework zip.
I've noticed the system restarting during apps
Optimization once or twice after flashing some zip
But it later completed the optimization after the
Restart so I didn't bother to look at the lst_kmsg
Try clearing cache and Dalvik cache again
If the issue persist, restore your system,
Flash SuperSU clear cache and Dalvik cache
Restart system.
Go into recovery again and flash the xposed Framework
Clear cache and Dalvik cache and restart.
Please always make sure that Md5 checksum is ticked
In TWRP before flashing Any zip or restoring any
Backup
Click to expand...
Click to collapse
tried all that bootloop nothing's working
D3VI0US said:
tried all that bootloop nothing's working
Click to expand...
Click to collapse
Well, I think you have to give me full details of your
Phone, recovery, Rom, etc
If you can get dmesg, last_kmsg, adb logcat
That will be useful.
I'll suggest you do a backup of your data and try
Flashing my fixed AndroidOne firmware 5.1.1,
Flash TWRP, flash SuperSU and flash xposed Framework
And then flash the mod
Bolumstar said:
Well, I think you have to give me full details of your
Phone, recovery, Rom, etc
If you can get dmesg, last_kmsg, adb logcat
That will be useful.
I'll suggest you do a backup of your data and try
Flashing my fixed AndroidOne firmware 5.1.1,
Flash TWRP, flash SuperSU and flash xposed Framework
And then flash the mod
Click to expand...
Click to collapse
I have the exact same setup as anyone. Hot 2 is short on ROMs and such
So I have the fixed version of the Android One ROM you released, TWRP and SuperSU flashed from TWRP
and all I'm getting is android optimizing apps and tons of restarting in between and then start again from the beginning. it's just not working
D3VI0US said:
I have the exact same setup as anyone. Hot 2 is short on ROMs and such
So I have the fixed version of the Android One ROM you released, TWRP and SuperSU flashed from TWRP
and all I'm getting is android optimizing apps and tons of restarting in between and then start again from the beginning. it's just not working
Click to expand...
Click to collapse
At what point did the phone come up?
Flash it step by step; ie flash recovery reboot system
Flash SuperSU reboot system, flash xposed reboot system
You might have to Redownload the latest xposed Framework
Which is version 73, put it inside phone memory.
Don't forget to check the md5 checksum before you
Flash any zip.
Try and copy the current last_kmsg from recovery to
External Sdcard and send it to me let me know what's
The cause of your Phone issues.
It could be that one or more of your downloads
Got corrupt
From the link you gave us to download the xposed framework for lollipop rom 5.1.1, I saw xposed framework sdk22-arm.zip, arm64.zip, arm86.zip, *64 or *86.zip which one should we download
Bolumstar said:
Finally after a lot of hard work I successfully install
Xposed Framework sdk22 for infinix hot 2 X510
To install you have to first install TWRP for X510
How to install TWRP On Infinix x510 Click here
Download Xposed Framework by Rovo89 Click here
Make sure you select sdk22 for LP 5.1 & 5.1.1
Flash the framework zip
Wipe Cache and Dalvik cache
Reboot System
Install Xposed apk
Enjoy.
If this is helpful please hit the thanks button.....
Click to expand...
Click to collapse
Pls how we doing all the flashing with external sd inserted? I.e all the .zip file and apk file that would be flash in recovery, how we placing / putting them in the root directory of the phone or sd?
desorockstar said:
Pls how we doing all the flashing with external sd inserted? I.e all the .zip file and apk file that would be flash in recovery, how we placing / putting them in the root directory of the phone or sd?
Click to expand...
Click to collapse
First flash TWRP Recovery with SP Flash tool
Which I put a link of how to beside it.
After that, you can install xposed framework,
SuperSU (root) etc with TWRP from TWRP recovery.
Pls reply the previous post about the type of xposed framework to download
I have successfully installed supersu but encountered this error in the attachments link below...mtk droid tools could not get root permission
https://forum.hovatek.com/attachment.php?aid=1519 (
Bolumstar said:
It's important to flash SuperSU zip first before
Xposed Framework zip.
I've noticed the system restarting during apps
Optimization once or twice after flashing some zip
But it later completed the optimization after the
Restart so I didn't bother to look at the lst_kmsg
Try clearing cache and Dalvik cache again
If the issue persist, restore your system,
Flash SuperSU clear cache and Dalvik cache
Restart system.
Go into recovery again and flash the xposed Framework
Clear cache and Dalvik cache and restart.
Please always make sure that Md5 checksum is ticked
In TWRP before flashing Any zip or restoring any
Backup
Click to expand...
Click to collapse
Boss where can I tick the md5 checksum in twrp recovery? Pls upload the image where md5 checksum is ticked
desorockstar said:
Boss where can I tick the md5 checksum in twrp recovery? Pls upload the image where md5 checksum is ticked
Click to expand...
Click to collapse
Please don't ask same question in multiple threads.
I've answered this question in another thread.
I encountered this error when trying to install the xposed installer framework. See attachments below
Good Day,
After installing Xposed (v80_sdk21_arm64), the Xposed Framework it's detected and it works well; but I can't update or install anything.
I've tryed to mount the system partition from the TWRP recovery; but after reboot it doesn't get mounted.
Please help
Thanks in advice,
I tryed the following:
Uninstall the Xposed Framwork, re-install the Xposed Framework and clean Dalvik/Caché, then reboot. But it doesn't work.
Also, I tryed to mount system from TWRP on the next reboot, but still doesn't work.
Thanks in advice for your help.
The way I fixed it
I've got the M4 Aqua, so I flashed the whole ROM again, then rooted it, and then installed TWRP, and the the Xposed Framework.
Then, right after installing the Xposed Framework did a wipe of the Caché and Dalvik Caché, then booted (waited about 15 mins) and it worked.
Now I'm able to install, uninstall and modify everything in the /System.
NOTE: In Sony devices like mine, you encounter a problem whit the stock camera and/or Album applications; you fix it by de-odex the apk and then but it back again; I fixed it following this post.
Hi,
EDIT: Ok, it seems that the first boot process needs about 10-15min. I just had to be more patient and now it works fine.
just tried to install Xposed on my Z2P (ZUI 2.0; Rooted+Unlocked), but I got into a bootloop and I could only recover my device by restoring a backup done before the Xposed installation (uninstalling Xposed didn‘t help).
What I did:
1. Downloaded Xposed framework (v86-sdk23-arm64), uninstaller and the latest apk.
2. Flashed the framework zip.
3. Cleared dalvik cache
4. Reboot
Result: boot sequence hangs on the blue "ZUK" logo. Wait for about 10-15min and it boots totally fine.
Does anyone else have this problem?
Is there any solution to this?
Thanks in advance and best regards
Tek
I assume it's the dalvik cache being created.
cannot see the apps
Hello,
I wanted to install xposed framework on my Zuk Z2 pro but I don't for which reason, I can't see the apps in my drawer.
I downloaded the zip, started the recovery, install, wipe, restarted but nothing is showing up!!! Even it the apps list...
Am I missing something?
Edit: OK I just forgot to install the apk after the zip install ... Working now!!!!
I used AICP ROM, in case it is an useful info.
I installed xposed with the classic method via TWRP. Just flash the correct sdk version "arm64". (Stock ROM 2.1.120 ST)
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
UPDATE: For now, if no other solution is found, bootloop can be bypassed by dirty installing the rom again. But it has to be an easier workaround...
We know now that the problem is caused because of two factors merging:
1- Using Magisk.zip installer through custom recovery
2-In the case that the custom recovery CMW/TWRP installed in the phone is very old (for instance, CMW automade for MTK6589X or TWRP 2.5.0).
While installing, Magisk tries to send commands to the custom recovery that cant be understood by it, leaving the installation incomplete after some modifications in /system (read below recovery log).
Acording to the recovery, it seems that Magisk did some modifications without running correctly survival script - Adding addon.d survival script ("Unrecognized option '-Xnodex2oat'") and .zip installer is not designed to revert actions in this case.
Also, Magisk couldn't reach the boot modification step, so boot is not damaged, therefore workarounds for restoring boot won't work.
Using Magisk Unistaller.zip is also not possible as the uninstaller is mainly designed for boot backup restoration, and again, this is not the case.
Currently needed: Find what's wrong in system due to the incomplete Magisk installation to revert it back to the original state (before faulty magisk.zip installation).
Recovery log:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
up!
I' also having the same problem. My Samsung J2 Prime stuck at logo after updating to 18.1. Any tips on how to fix it without resetting my phone? Thanks.
Update: Bootloop fixed. I used TWRP to restore boot image. I then update Magisk by flashing zip file from TWRP. Everything went back to normal. Hope this help.
trol_sg said:
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
Click to expand...
Click to collapse
If you have a backup of your boot image, you can just restore it using TWRP. But in case that you have no backup of boot image, you can try to get boot image from the internet and restoring using it. In my case, this is what I did.
1. Go to TWRP and then make backup of boot image of the faulty phone*. (Folder 1)
2. I used another J2 prime to create a boot image backup. (Folder 2)
3. Once that is done, copy and replace the files inside the Folder 2 into Folder 1.
4. Reboot to TWRP again then use that to restore the boot image on my stuck J2.
Tips: make backup in SD card so you can easily swap it in between the bad and good phone.
*This is to create a folder of the backup file. I did tried to directly copy and paste the backup boot image file from another good phone but TWRP didn't detect it. So this is the workaround that I come with. And it worked for me.
Thanks for your answer but I doubt your case is mine. Your device is much newer than mine and according to your comment, you've sucesfully installed previous version of Magisk without issues. This is not a problem while updating, as Magisk v. earlier than 18.1 was not compatible with android 4.2+. I think Magisk is not compatible with MT6589T even if they run 4.2 or 4.4.
I think that it cannot be a boot problem as TWRP/CWM displayed msg 'Boot cannot be found' while installing Magisk, so that I don't think boot was replaced or modified in any ways. Moreover, the bootloop is not in the boot loading, as phone can pass boot image without any problem, but it is stuck in android loading image. I'm thinking in some script or root modification that Magisk did before trying to unpack the boot, however I'm not that deep into the Magisk install to find the proper workaround.
I can restore boot backup and also I can take boot file from the original rom and flash, because in Mediatek-based devices, boot.img is inside de zip, but I dont think it will solve the problem. Anyhow I'll get back ASAP with the answer.
Any more ideas??
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
trol_sg said:
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
Click to expand...
Click to collapse
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Ato09 said:
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Click to expand...
Click to collapse
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Here I attach recovery.log if someone is interested to see the detailed problem.
Also, here below I attach the lines concerning the installation. All other is uninstallation tries and so on:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all,full}
-Xnoquithandler
-Xjniopts:{warnonly,forcecopy}
-Xjnitrace:substring (eg NativeClass or nativeMethod)
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgc:[no]preverify
-Xgc:[no]postverify
-Xgc:[no]concurrent
-Xgc:[no]verifycardtable
-XX:+DisableExplicitGC
-X[no]genregmap
-Xverifyopt:[no]checkmon
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitcodecachesize:decimalvalueofkbytes
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitclass:classname[,classname]*
-Xjitoffsetffset[,offset]
-Xjitconfig:filename
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
-Xjitsuspendpoll
Configured with: debugger profiler hprof jit(armv7-a-neon) smp show_exception=1
Failed to initialize runtime (check log for details)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/bootimg]
No boot image magic found!
! Unable to unpack boot image
- Unmounting partitions
E:Error executing updater binary in zip '/sdcard/Magisk-v18.1.zip'
Error flashing zip '/sdcard/Magisk-v18.1.zip'
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Didgeridoohan said:
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Click to expand...
Click to collapse
Thank you so much for your answer. So it's the recovery, but can't find newer ones, sadly. Too old phones I know, but just curious if I could make Magisk working on them, lol.
I was going into the boot modification manually right now, but in order to patch the boot I need manager installed first, and phone couldn't boot so I did dirty flash of the rom to be able to boot into it again.
Lets see what happens then. I'll be right back.
Anyhow, this is not a solution to fix the problem of bootloop that I am requesting help in case someone could face the same and did not make a backup of the phone and didn't want to make dirty re-flash. Any idea?
Update: After I did dirty flash of the rom, and now Jiayu g3s android 4.4 booted.
UPDATE: So, after patching manually boot and installing (using restore in TWRP 2.5 as image flash is not yet implemented AFAIK), phone booted and yes Magisk is working.
Magisk installation .zip through a very old recovery is making the bootloop. So that, a thing learnt now.
But, for other people facing this bootloop, can we do a research to find what magisk.zip did to the phones to leave them in bootloop? Maybe we can revert without rom flashing easily if we knew what's the issue...
Thanks in advance!
Doing a bit more tests I found that magisk.zip did something in /system so that it is left in bootloop, but still no idea why/whats causing that...
There are delay complete boot like 4 5 second in j7 prime. I didn't love this version
any more help?? up!!
trol_sg said:
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Click to expand...
Click to collapse
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Ato09 said:
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Click to expand...
Click to collapse
Hello, thanks
This method won't work in my case as in the step:
- installed magisk uninstall = gives error
Note 5 is much newer phone with a recent recovery TWRP that allows all Magisk.zips commands, but unluckyly not this case.
Also, this method is for wrong boot installation/damaged boot. In my case what Magisk damage is /system, not boot.
I wish it could be boot, because that is very easy to fix (flashing through fastboot/SP Flash tools in the case of MTK, recovering boot twrp "backup" even if you didn't make backup...) as you mentioned.
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Main post updated with all thread information. Up!
Nothing?? Up!!
trol_sg said:
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Click to expand...
Click to collapse
The only part of the Magisk installation that actually touches /system is if it installs the addon.d survival script. The log you posted earlier shows that it's trying to do this, for some reason, and failiing. I'd start looking there...
Hi, my device reboot after I unlock it, I only have access to my Internal memory of my phone via PC
how to unistall/disable magisk so I can delete the modules?
Is there a folder that I can delete?
I don't have TWRP
albysprx said:
Hi, my device reboot after I unlock it, I only have access to my Internal memory of my phone via PC
how to unistall/disable magisk so I can delete the modules?
Is there a folder that I can delete?
I don't have TWRP
Click to expand...
Click to collapse
How you got magisk to work without flashing it?
PoochyXXX
PoochyX said:
How you got magisk to work without flashing it?
PoochyXXX
Click to expand...
Click to collapse
with patched the boot img of my firmware with magisk manager and then I flashed it with fastboot
albysprx said:
with patched the boot img of my firmware with magisk manager and then I flashed it with fastboot
Click to expand...
Click to collapse
Ohhhhh.... Root is very particular without a custom recovery to get your phone to that exact working state it was in before if you had a custom recovery there could of been a couple modules you could use
PoochyXXX
You can always flash a stock boot image. That will disable Magisk completely, but has the drawback of leaving you without root...
To disable or uninstall modules without removing Magisk you would have to have access to /cache (place a file named .disable_magisk, with the leading dot, in /cache and Core Only Mode will be enabled) or /data/adb (delete the Magisk image file) through recovery. Usually not an option on a stock recovery... If there is no custom recovery for your device you might not have many options, but if there is one available and you don't want to install it, you could at least boot it with "fastboot boot recovery <name_of_recovery_file>".
Didgeridoohan said:
You can always flash a stock boot image. That will disable Magisk completely, but has the drawback of leaving you without root...
To disable or uninstall modules without removing Magisk you would have to have access to /cache (place a file named .disable_magisk, with the leading dot, in /cache and Core Only Mode will be enabled) or /data/adb (delete the Magisk image file) through recovery. Usually not an option on a stock recovery... If there is no custom recovery for your device you might not have many options, but if there is one available and you don't want to install it, you could at least boot it with "fastboot boot recovery <name_of_recovery_file>".
Click to expand...
Click to collapse
Yeah, I got working again with flashing the stock boot.img but after flashed again the pacthed boot.img my phone bootloop again...
I tried to install TWRP and got it working, I typed /cache/.disable_magisk in terminal and rebooted and the device works, went to magisk manager and no modules was there, disabled core magisk and the device bootloop again...
now I'm trying to reinstall the entire firmware and make a factory reset before reinstalling magisk...
Should this remove modules installed?
Didgeridoohan said:
You can always flash a stock boot image. That will disable Magisk completely, but has the drawback of leaving you without root...
To disable or uninstall modules without removing Magisk you would have to have access to /cache (place a file named .disable_magisk, with the leading dot, in /cache and Core Only Mode will be enabled) or /data/adb (delete the Magisk image file) through recovery. Usually not an option on a stock recovery... If there is no custom recovery for your device you might not have many options, but if there is one available and you don't want to install it, you could at least boot it with "fastboot boot recovery <name_of_recovery_file>".
Click to expand...
Click to collapse
Yeah, I got working again with flashing the stock boot.img but after flashed again the pacthed boot.img my phone bootloop again...
I tried to install TWRP and got it working, I typed /cache/.disable_magisk in terminal and rebooted and the device works, went to magisk manager and no modules was there, disabled core magisk and the device bootloop again...
now I'm trying to reinstall the entire firmware and make a factory reset before reinstalling magisk...
Should this remove modules installed?
albysprx said:
Yeah, I got working again with flashing the stock boot.img but after flashed again the pacthed boot.img my phone bootloop again...
I tried to install TWRP and got it working, I typed /cache/.disable_magisk in terminal and rebooted and the device works, went to magisk manager and no modules was there, disabled core magisk and the device bootloop again...
now I'm trying to reinstall the entire firmware and make a factory reset before reinstalling magisk...
Should this remove modules installed?
Click to expand...
Click to collapse
If you got the device booting (in Core Only Mode) and still have root you could just use a file explorer, navigate to /sbin/.magisk/img and delete the offending module directories. Or, you could delete the Magisk image file in recovery (it's in /data/adb). Either of those options would remove the modules.
Didgeridoohan said:
If you got the device booting (in Core Only Mode) and still have root you could just use a file explorer, navigate to /sbin/.magisk/img and delete the offending module directories. Or, you could delete the Magisk image file in recovery (it's in /data/adb). Either of those options would remove the modules.
Click to expand...
Click to collapse
Got my device working again in magisk core only mode but the folder /sbin/.magisk/img is empty .-.
albysprx said:
Got my device working again in magisk core only mode but the folder /sbin/.magisk/img is empty .-.
Click to expand...
Click to collapse
Now that you have your device running, do a complete uninstall from the Magisk Manager and start over. That should remove everything...
Didgeridoohan said:
Now that you have your device running, do a complete uninstall from the Magisk Manager and start over. That should remove everything...
Click to expand...
Click to collapse
ok I deleted the magisk.img from data/adb/magisk, did a complete unistall from magisk manager (after the unistall the phone reboot to the TWRP without doing anything), sideloaded the magisk unistaller and got "ERROR: 1", after that I rebooted, rebooted again in recovery mode and installed magisk, rebooted, removed the core mode and rebooted again..
It works!!
Thanks a lot