thanks to a friend @Frazercrib(who likes to be my lab rat )... The Infinix Hot 2 has been rooted on Marshmallow and Xposed is successfully installed.
Pre-Requisites:
A PC
Infinix Hot 2 on Android 6.0
Recovery Enabler
TWRP
SUPER SU for Marshmallow
Xposed Framework for Marshmallow (Optional)
SP or Infinix Flash Tool
Your Brain
STEPS:
- Place BETA-SU-2.66.zip and xposed-v79-arm-sdk23.zip in your Internal/External SD Card.
- Install MT65xx/VCOM Drivers
- Download and Extract Infinix Flash Tool, TWRP Recovery, Recovery Enabler (place folders in your desired location)
- Open Infinix Flash Tool, click on browse and navigate to folder containing Recovery Enabler, select MT6580_Android_Scatter file and click start.
- Connect your phone to your PC (battery removed)
- Reboot after flashing.
- Do the same process for TWRP Recovery but do not reboot after flashing. Boot straight to Recovery
- Flash SuperSU
- On reboot, TWRP Prompts a message that SuperSU is not installed and asks to install it. Do not accept. Hit the back button and reboot normally.
(OPTIONAL FOR THOSE WHO NEED XPOSED)
- Install Xposed Installer apk and reboot to recovery
- Perform a Nandroid Backup
- Install xposed-v79-arm-sdk23.zip and reboot. (Do not clear anything)
- On reboot, TWRP Prompts a message that SuperSU is not installed and asks to install it. Do not accept. Hit the back button and reboot normally.
DOWNLOAD LINKS:
Infinix Flash Tool: https://mega.nz/#!YUVQESJI!yg0i_YquG7JLx8YTkUr-wkToLOU4Hr50AN931s4tBlY
Recovery Enabler: https://www.androidfilehost.com/?fid=24269982086997892
TWRP Recovery: https://mega.nz/#!lMchVCRR!-a8cQWiYO8k0XqIdr74vlNwAvWBBxz5-VoEPOp8NJSw
Special thanks to @Frazercrib for teaming up with me to get Marshmallow rooted + get xposed working on Marshmallow.
PS: Please see attached file below for SuperSU and Xposed zip, and Xposed Installer apk
SCREENSHOTS:
{
"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"
}
Here are attached files
Also check this thread to know which modules works on marshmallow to avoid bootloops
forum.xda-developers.com/xposed/unofficial-list-modules-xposed-t3249162
Frazercrib said:
Also check this thread to know which modules works on marshmallow to avoid bootloops
forum.xda-developers.com/xposed/unofficial-list-modules-xposed-t3249162
Click to expand...
Click to collapse
Lol.. Partner in crime!
iAmWiz said:
Lol.. Partner in crime!
Click to expand...
Click to collapse
Bro... How do I remove root on the hot 2 SuperSU was flashed In.?
Sent from my Infinix X510 using Tapatalk
Merlve said:
Bro... How do I remove root on the hot 2 SuperSU was flashed In.?
Sent from my Infinix X510 using Tapatalk
Click to expand...
Click to collapse
According to @Chainfire the root method on 6.0 is systemless and removing root will require flashing your boot.img only. I'm not sure we have that yet on this device
iAmWiz said:
According to @Chainfire the root method on 6.0 is systemless and removing root will require flashing your boot.img only. I'm not sure we have that yet on this device
Click to expand...
Click to collapse
Well, a normal factory reset unroots the hot 2, tested it yday...
Does anyone know why am still getting the 6.0 update of 823mb even wen am already on 6.0??
Merlve said:
Well, a normal factory reset unroots the hot 2, tested it yday...
Does anyone know why am still getting the 6.0 update of 823mb even wen am already on 6.0??
Click to expand...
Click to collapse
Possibly some bug fixes.
iAmWiz said:
Possibly some bug fixes.
Click to expand...
Click to collapse
Then, that's a lot of bugs [emoji6]
Sent from my Infinix X510 using Tapatalk
Merlve said:
Then, that's a lot of bugs [emoji6]
Sent from my Infinix X510 using Tapatalk
Click to expand...
Click to collapse
Uhm here's the difference. The 62x MB update is an incremental update which requires one to be in December build before flashing. The 83xMB update doesn't require. You can make the path to 6.0 regardless of the build you're on.
iAmWiz said:
Uhm here's the difference. The 62x MB update is an incremental update which requires one to be in December build before flashing. The 83xMB update doesn't require. You can make the path to 6.0 regardless of the build you're on.
Click to expand...
Click to collapse
Now I understand... A lot of guys been getting errors tryna flash with stock recovery
Sent from my Infinix X510 using Tapatalk
Merlve said:
Now I understand... A lot of guys been getting errors tryna flash with stock recovery
Sent from my Infinix X510 using Tapatalk
Click to expand...
Click to collapse
That explains it
can this way work on zero3 if i put its recovery
Mido Enab said:
can this way work on zero3 if i put its recovery
Click to expand...
Click to collapse
Yeah, it should.
iAmWiz said:
thanks to a friend @Frazercrib(who likes to be my lab rat )... The Infinix Hot 2 has been rooted on Marshmallow and Xposed is successfully installed.
Pre-Requisites:
A PC
Infinix Hot 2 on Android 6.0
Recovery Enabler
TWRP
SUPER SU for Marshmallow
Xposed Framework for Marshmallow (Optional)
SP or Infinix Flash Tool
Your Brain
STEPS:
- Place BETA-SU-2.66.zip and xposed-v79-arm-sdk23.zip in your Internal/External SD Card.
- Install MT65xx/VCOM Drivers
- Download and Extract Infinix Flash Tool, TWRP Recovery, Recovery Enabler (place folders in your desired location)
- Open Infinix Flash Tool, click on browse and navigate to folder containing Recovery Enabler, select MT6580_Android_Scatter file and click start.
- Connect your phone to your PC (battery removed)
- Reboot after flashing.
- Do the same process for TWRP Recovery but do not reboot after flashing. Boot straight to Recovery
- Flash SuperSU
- On reboot, TWRP Prompts a message that SuperSU is not installed and asks to install it. Do not accept. Hit the back button and reboot normally.
(OPTIONAL FOR THOSE WHO NEED XPOSED)
- Install Xposed Installer apk and reboot to recovery
- Perform a Nandroid Backup
- Install xposed-v79-arm-sdk23.zip and reboot. (Do not clear anything)
- On reboot, TWRP Prompts a message that SuperSU is not installed and asks to install it. Do not accept. Hit the back button and reboot normally.
DOWNLOAD LINKS:
Infinix Flash Tool: https://mega.nz/#!YUVQESJI!yg0i_YquG7JLx8YTkUr-wkToLOU4Hr50AN931s4tBlY
Recovery Enabler: https://www.androidfilehost.com/?fid=24269982086997892
TWRP Recovery: https://mega.nz/#!lMchVCRR!-a8cQWiYO8k0XqIdr74vlNwAvWBBxz5-VoEPOp8NJSw
Special thanks to @Frazercrib for teaming up with me to get Marshmallow rooted + get xposed working on Marshmallow.
PS: Please see attached file below for SuperSU and Xposed zip, and Xposed Installer apk
SCREENSHOTS:
View attachment 3605089
View attachment 3605095
View attachment 3605096
Click to expand...
Click to collapse
The recovery in the mega has been removed help me upload again thanks
Akorstayblessed said:
The recovery in the mega has been removed help me upload again thanks
Click to expand...
Click to collapse
Check here. I don't use the device anymore.
iAmWiz said:
Check here. I don't use the device anymore.
Click to expand...
Click to collapse
that not cool u can help me
Akorstayblessed said:
that not cool u can help me
Click to expand...
Click to collapse
https://twrp.me/devices/infinixhot2.html
iAmWiz said:
thanks to a friend @Frazercrib(who likes to be my lab rat )... The Infinix Hot 2 has been rooted on Marshmallow and Xposed is successfully installed.
Pre-Requisites:
A PC
Infinix Hot 2 on Android 6.0
Recovery Enabler
TWRP
SUPER SU for Marshmallow
Xposed Framework for Marshmallow (Optional)
SP or Infinix Flash Tool
Your Brain
STEPS:
- Place BETA-SU-2.66.zip and xposed-v79-arm-sdk23.zip in your Internal/External SD Card.
- Install MT65xx/VCOM Drivers
- Download and Extract Infinix Flash Tool, TWRP Recovery, Recovery Enabler (place folders in your desired location)
- Open Infinix Flash Tool, click on browse and navigate to folder containing Recovery Enabler, select MT6580_Android_Scatter file and click start.
- Connect your phone to your PC (battery removed)
- Reboot after flashing.
- Do the same process for TWRP Recovery but do not reboot after flashing. Boot straight to Recovery
- Flash SuperSU
- On reboot, TWRP Prompts a message that SuperSU is not installed and asks to install it. Do not accept. Hit the back button and reboot normally.
(OPTIONAL FOR THOSE WHO NEED XPOSED)
- Install Xposed Installer apk and reboot to recovery
- Perform a Nandroid Backup
- Install xposed-v79-arm-sdk23.zip and reboot. (Do not clear anything)
- On reboot, TWRP Prompts a message that SuperSU is not installed and asks to install it. Do not accept. Hit the back button and reboot normally.
DOWNLOAD LINKS:
Infinix Flash Tool: https://mega.nz/#!YUVQESJI!yg0i_YquG7JLx8YTkUr-wkToLOU4Hr50AN931s4tBlY
Recovery Enabler: https://www.androidfilehost.com/?fid=24269982086997892
TWRP Recovery: https://mega.nz/#!lMchVCRR!-a8cQWiYO8k0XqIdr74vlNwAvWBBxz5-VoEPOp8NJSw
Special thanks to @Frazercrib for teaming up with me to get Marshmallow rooted + get xposed working on Marshmallow.
PS: Please see attached file below for SuperSU and Xposed zip, and Xposed Installer apk
SCREENSHOTS:
View attachment 3605089
View attachment 3605095
View attachment 3605096
Click to expand...
Click to collapse
Thanks for inspiring me, now we can do it simpler (magisk required) with https://github.com/Magisk-Modules-Repo/xposed i've successfully installed framework and some module with it, because I have been tried like your explained on this thread, working well-installed Xposed framework but when try to install module always got boot loop.
Now I'm used magisk-xposed on infinix x510.
Related
Oxygen OS 4.0 Nougut Mirror Links:
{
"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"
}
HTML:
Thanks is Appreciated :)
Main Mirror
MEGA :
https://mega.nz/#!KoAiWIRR!gG4wjTg37bzHc4Q_OXqjYVSZOCTuvL1zNGGy1iIwB8w
EXTRA Mirrors(Tested 01/01/2017 4:15 AM IST)
Google Drive Mirror:
https://drive.google.com/file/d/0BzS3nWITUqU_Sk5yQkRqWkhFY3c/view
Official from OnePlus site:
http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Modified TWRP:
twrp-3.0.2-1.28-oneplus3.img
Flashing Instructions :
With TWRP Recovery(Make sure you are in F2Fs to avoid DM-verity Error)
HTML:
1. Download the Full Zip on your phone internal memory.
2. Download the Latest SuperSU 2.79 SR1
4. Reboot To TWRP (Modified 28) & Take a Nandroid of your existing ROM
5. Go to Wipe > Advance Wipe > Select Dalvik & Cache & Swipe to Wipe
6. Install Menu > Select Rom Zip > Swipe to Flash
7. Wipe Dalvik & Cache
8. Flash SuperSU to maintain root
9. Reboot System and Enjoy
Side Load:
HTML:
Download the zip file for your device by using above any link.
Make sure you have all necessary adb files installed on your computer.
Reboot your phone into recovery mode. To do this, shut down your device and turn it back on while holding the power and volume down buttons simultaneously.
Choose “Install from USB†option in the recovery screen, tap OK to confirm. A screen with “You are in sideload mode†will be displayed.
If you are not using the original Oxygen Recovery. View instructions for TWRP Recovery to flash OxygenOS Recovery .
Connect your device to PC/Mac, run following command in command prompt / terminal
For Windows: “adb sideload <filename>â€
For Mac/Linux: “./adb sideload <filename>â€
Wait a while, your phone should now update to the selected build and reboot automatically to take you into OxygenOS.
Clean Flash:
HTML:
Put Zip anywhere in Internal Storage.
Power Off Your Phone.
Reboot into recovery by pressing Power + Volume down button .
Select English.
Select Wipe Data and Cache. It might take some time.
Go to recovery home.
Select Install from Local.
Select the Zip.
Click on Install
Wait for it to Install
Reboot.
You are Done.
Dirty Flash:
HTML:
Put Zip anywhere in Internal Storage.
Power Off Your Phone.
Reboot into recovery by pressing Power + Volume down button .
Select English.
Select Install from Local.
Select the Zip.
Click on Install
Wait for it to Install
Reboot.
You are Done.
NS. S Dirty Flash is working from OpenBeta 10 to OxygenOS 4.0
Thanks
I can't download from this links
vagelis74 said:
I can't download from this links
Click to expand...
Click to collapse
Uploading MEGA Also..will share soon
full zip ?
akuma48465 said:
full zip ?
Click to expand...
Click to collapse
Yes
ansaziz777 said:
Oxygen OS 4.0 Nougut Mirror Links:
NS. S Dirty Flash is working from OpenBeta 10 to OxygenOS 4.0
Click to expand...
Click to collapse
Please post the link for TWRP recovery users also... and do mention all the steps.... Please, please, please...
Links dont working.
submundo said:
Links dont working.
Click to expand...
Click to collapse
Mega upload is going on 75%, will update the link soon
Normas Interruptor said:
Please post the link for TWRP recovery users also... and do mention all the steps.... Please, please, please...
Click to expand...
Click to collapse
Done
submundo said:
Links dont working.
Click to expand...
Click to collapse
vagelis74 said:
I can't download from this links
Click to expand...
Click to collapse
Mega Link is live now
Found a strange problem.
I did what you wrote in the description about installing the rom through twrp. But i get Dm-verity.
I have .28 twrp version . F2Fs done. and still i get the thing? Dont know why? :S
I am on open beta 10. Can i flash this update via stock recovery?
Can you add into your instructions how to get f2fs via TWRP. For those of us who are either on 2.2.8 or beta 10 and running ext4.
nfremd said:
Can you add into your instructions how to get f2fs via TWRP. For those of us who are either on 2.2.8 or beta 10 and running ext4.
Click to expand...
Click to collapse
Instruction:
NB: Changing to f2fs will erase all data. Take nand backup and keep it safe somewhere like PC/usb
Ext4 will show DM-verity error
1.Install Titanium backup
2.Backup settings and user apps
3. Copy to PC
4. Goto wipe-- system -- repair and change to f2fs
5. Repeat the step for data also
6. Mount and copy rom.zip and supersu2.79 sr1
7.flash from and flash SuperSU
8.reboot and complete.install Titanium and restore data back
Best way to install:
1. flash oxygen recovery
2. adb sideload Rom.zip
3. boot to fast boot and flash twrp28
4. Boot to recovery and install supersu2.79sr1
5.reboot and enjoy
Zero errors in second method.working like charm
mabmed said:
I am on open beta 10. Can i flash this update via stock recovery?
Click to expand...
Click to collapse
You can sideload
Did download the mega file twice, but my command line in windows says "cannot read file" while using adb sideload. anyone else having this problem?
christophs01 said:
Did download the mega file twice, but my command line in windows says "cannot read file" while using adb sideload. anyone else having this problem?
Click to expand...
Click to collapse
I am also having this problem, I was previously on 3.2.8. @ansaziz777 any suggestions?
Where can I find superSu 2.79?
Enviado do meu ONEPLUS A3003 através de Tapatalk
salomaoa said:
Where can I find superSu 2.79?
Enviado do meu ONEPLUS A3003 através de Tapatalk
Click to expand...
Click to collapse
google is ur friend
{
"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"
}
Latest Stable Magisk Version : v14.0 [2017.9.6]
Latest Magisk Manager Version : v5.3.0 [2017.9.6]
Hello, welcome to the official Magisk Release For Zenfone 2 Z00A/Z008 taken from 4pda.ru forum!
Magisk can ROOT your device, along with standard common patches.
It packs with a super powerful Universal Systemless Interface, allowing unlimited potential!
Magisk modifies boot image and add files to /data and /cache
It touches your /system partition only if root installed in /system is detected!
Features
100% fully open source and easy to build!
Magic Mount :
Allow you to do any system (vendor) modification without actually tampering the partitions.
Anything can be loaded with Magisk systemless-ly!
MagiskSU : Open Source Root Solution
Root your device with MagiskSU, based on phh's Superuser, which is based on CM Superuser.
Magisk Manager :
MagiskSU Root Management, Upgrade Magisk in-app,
Manage, Upgrade, Download, Install Magisk Modules from the community driven online Magisk Module Repo.
Magisk Hide :
Hide Magisk from detection, mainly targeting Google's SafetyNet
Resetprop :
Allow you to do any modifications to system props (build.prop), including read-only props.
It is also used along with magiskhide for tricking various device states
Multiple Entry Points :
Provide several entry points to developers, reliably pausing the boot process before everything is done.
Include post-fs (cache) mode, which happens even earlier than data is mounted (used to replace Boot Animation etc.)
Standard Stuffs :
Remove dm-verity, forceencrypt, unlock partitions blocks to support remount to rw
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager Through TWRP Recovery
For installing Magisk the first time!
(never update magisk through application it will caused bootloop)
(If you have Xposed safetynet won't work)
Install Lastest Magisk Manager Apk
Reboot To TWRP Recovery
Select Lastest Magisk ZIP, then flash it
Reboot To Systems (wipe cache and dalvik is'nt needed if you want it then go for it)
Downloads
Lastest Magisk : https://drive.google.com/file/d/0B_t_ymFu4cH4eDNaYkhjU3lJb28/view
Lastest Magisk Uninstaller : https://drive.google.com/file/d/0B_t_ymFu4cH4bktMb2xTdk10Yzg/view
Lastest Magisk Manager Apk : https://drive.google.com/file/d/0B_t_ymFu4cH4dkpNUHh3NXVuOWc/view
Credits & Specials Thanks To All Developer XDA Forum & 4PDA Forum!
where to get uninstaller?
Arerive said:
where to get uninstaller?
Click to expand...
Click to collapse
haha forget to add it, wait bro
nice, thanks you so much, btw i had Magisk 13.3 installed, do i need to remove my module before flashing the new Magisk?
sushuguru said:
nice, thanks you so much, btw i had Magisk 13.3 installed, do i need to remove my module before flashing the new Magisk?
Click to expand...
Click to collapse
no just reflashed is ok bro no problem, same source.
mine from 12.0 to 14.0 without anyproblem
FYI : if you have xposed installed, safetynet won't work or gone
Thanks for the update! just relating here a mess i did:
You noticed the update today 2:15am XDA time, so i did wrong, opened Magisk Manager, and did the update.
what do i did to fix it:
1 -Once having Viper OS 3.0 on pc, i downloaded magisk installer, plus last HoloN kernel i was using. Taking advantage of that I was doing a dirty flash, i also down'ed last Gapps (but down'ed wrong version . . .)
Turned off phone, toke SD & plug on PC, put all downloadeds in external SD card;
2 - My Z00AD was in bootlop, so i reboot it in recovery and:
3 - Advanced Wipe > Wipe DAlvik/art cache + System + cache (JUST IT ONES!);
4 - Install ROM > Install last HoloN 6s0 version > flash Gapps and ... I downloaded x86-x64 version. Stopped here. . .
. . . So i had a previous Gapps version on PC, then . . .
Turn off Phone > pull out SD card & place x86pico 7.1 gapps version on SD
reboot ZF2 in recovery > did all step by step again:
1 - Advanced Wipe > Wipe Dalvik/art cache + System + cache (JUST IT ONES!);
2 - Install ROM > Install last HoloN 6s0 version > flash Gapps > flash Magisk > reboot.
So, i hope no other ones pass thrught that, keep attention with root stuffs . . .
El Cruz said:
Thanks for the update! just relating here a mess i did:
You noticed the update today 2:15am XDA time, so i did wrong, opened Magisk Manager, and did the update.
what do i did to fix it:
1 -Once having Viper OS 3.0 on pc, i downloaded magisk installer, plus last HoloN kernel i was using. Taking advantage of that I was doing a dirty flash, i also down'ed last Gapps (but down'ed wrong version . . .)
Turned off phone, toke SD & plug on PC, put all downloadeds in external SD card;
2 - My Z00AD was in bootlop, so i reboot it in recovery and:
3 - Advanced Wipe > Wipe DAlvik/art cache + System + cache (JUST IT ONES!);
4 - Install ROM > Install last HoloN 6s0 version > flash Gapps and ... I downloaded x86-x64 version. Stopped here. . .
. . . So i had a previous Gapps version on PC, then . . .
Turn off Phone > pull out SD card & place x86pico 7.1 gapps version on SD
reboot ZF2 in recovery > did all step by step again:
1 - Advanced Wipe > Wipe Dalvik/art cache + System + cache (JUST IT ONES!);
2 - Install ROM > Install last HoloN 6s0 version > flash Gapps > flash Magisk > reboot.
So, i hope no other ones pass thrught that, keep attention with root stuffs . . .
Click to expand...
Click to collapse
as I said on the post, dont update magisk from apk stuff you will get bootloop hehe
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Andy1N said:
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Click to expand...
Click to collapse
Try flashing Uninstaller zip first, and then flash the proper magisk package for your mobile... If you look at the title, you will see here "... for Zenfone" [emoji52]
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
Andy1N said:
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Click to expand...
Click to collapse
bro its for zenfone 2 hahaha ??
Does it work with BORETS rom? And can i just flash it via recovery with borets rom?
@indunrise bro., i think the zip missing a file when installed.,the "busybox" file should be in /data/magisk/ since the newest magisk module uses that file to run.,but its absent.,so im keep getting error 1 when flashing any new v14.0 modules through twrp...it works fine now after i've put the "busybox" file at the proper place i've mentioned above...can u include the busybox file into the zip n give it proper permission ? Thanks
Here u go @indunrise
sushuguru said:
Does it work with BORETS rom? And can i just flash it via recovery with borets rom?
Click to expand...
Click to collapse
yes you can, im using borets roms
Luq4dmin said:
@indunrise bro., i think the zip missing a file when installed.,the "busybox" file should be in /data/magisk/ since the newest magisk module uses that file to run.,but its absent.,so im keep getting error 1 when flashing any new v14.0 modules through twrp...it works fine now after i've put the "busybox" file at the proper place i've mentioned above...can u include the busybox file into the zip n give it proper permission ? Thanks
Click to expand...
Click to collapse
thanks for report bugs, if i have some time will add it soon
Luq4dmin said:
Here u go @indunrise
Click to expand...
Click to collapse
if you guys needed module on magisk download and copy this to data/magisk
I've installed this, root working and satefynet passing. How can install xposed now? I've tried with app and xposed-v87.3-sdk23-topjohnwu.zip file, neither worked.
I flash magisk on lineageos and success, work fine.
But then I switch to XOSP rom of nilac and can't flash magisk. I did the same steps.
Do you know how to make it work? Thanks in advance @indunrise
ketrooo said:
I've installed this, root working and satefynet passing. How can install xposed now? I've tried with app and xposed-v87.3-sdk23-topjohnwu.zip file, neither worked.
Click to expand...
Click to collapse
Which version of Android are you using
Sent from my Z00A using XDA Labs
If you have managed to root your phone with Magisk, getting updates after that for the stock ROM isn't always a smooth thing. Here are some steps to be successful with updates.
1. Open Magisk Manager and disable all installed modules by unchecking the circle for each.
{
"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"
}
Please note that steps 2-4 can be done with the stock 1+ updater so long as it senses that you are rooted and offers to download a full rom. So a note about magisk hide which is used to hide root. Make sure you haven't managed to hide root for any process related to the 1+updater or it won't know you are rooted and will offer incremental updates.
2. Install Oxygen Updater (This app may become abandoned in 2019 requiring the use of the stock updater which is slower or manually downloading roms.) https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
3. Open the app, verify that your device is identified correctly. Open it's settings and set Update Method to "Full Update"
4. Check for an update and download it. Make sure you end up with a full 2GB ROM image not an incremental small one. It will be in the root of internal storage.
DO NOT use Oxygen Updater to update the phone (unless you have TWRP and that is for a different GUIDE)
5. Open the built in OnePlus updater: Settings - System - System Updates - Gear - Local Upgrade and select the newly downloaded update. TAKE NOTE while it is installing which slot it is installing too. It will say something like "inactive slot a". Remember this as it is the "new" slot.
6. After it has installed DO NOT reboot the phone or you will lose root. Open Magisk Manager and install Magisk, even though it says "installed". Select the option when it prompts for "after OTA". This will install magisk in the boot partition of the new slot.
7. Reboot and If all went well you shouldn't boot loop and you'll be running the new slot. If you want TWRP (optional), install the zip now from Magisk->Modules->+ (sign) then select the TWRP zip file and install it. Do NOT reboot. Then do a "Direct Install" of Magisk again, then reboot.
8. Open Magisk Manager and go to the downloads section and reinstall the modules you want to use. Do this from the Downloads screen or using the + button on the Modules screen. This will install them in the current slot.
DO NOT simply reenable the modules with the check mark or you will boot loop. Some modules aren't listed in Magisk and can't be automatically moved from slot to slot. If you installed one of those previously, you must reinstall it with the plus button manually from the modules tab.
You should be done now.
Oh no I'm boot looping: Don't panic.
1. Make sure you have adb/fastboot 1.4.3 or newer on a PC https://forum.xda-developers.com/showthread.php?t=2317790
2. Boot the phone into Bootloader/fastboot either through the recovery menu or VolDn + Pwr
3. If in step 5 above the inactive slot was "a", issue the command from a PC command prompt:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
If you are not sure which to use try one or fastboot getvar current-slot
4. Then: fastboot reboot
This will allow the phone to boot into the last good ROM version. Now you figure out what went wrong.
Another option If your phone didn't retain root, you can stay in the unrooted slot. download a rooted boot image of your firmware version, place it in the your fastboot pc directory, reboot the phone to fastboot and issue the command: fastboot boot boot.img (or whatever the downloaded image is called.) this is a temporary root that is non destructive. Then do a direct install from Magisk manager even though it already says installed. That will permanently root your boot copy. Then install your modules.
Here is the 9.5.11 1917AA rooted boot image https://www.dropbox.com/s/6csxd9zaa4mihwk/boot_a_backup_2019-08-04_19-05-29.img?dl=0
If your phone looped right after flashing, you may not have disabled Magisk modules properly. You can still disable them from the good slot, swap active slots again using fastboot and see if it boots into the new ROM. If not, swap back to the good old slot again and start over flashing again from the beginning.
If you looped after reenabling your modules, it is possible you only enabled one but didn't install it into the new slot. Again swap back to the good slot and disable the modules. Swap back to the new slot and install the modules again even if Magisk thinks they are there.
If all else fails, you can stay in the good old slot until you sort things. If you are looping in both slots then something really went bad and you have to flash back a full ROM from fastboot. See this thread
https://buzzfire.de/xda/t3931424
Then root again using the rooted boot image above.
You may be able to boot into the old rooted slot and root the new slot with the ota option also.
If you have issues where stuff like Wifi doesn't work, then somewhere along the line or previously you flashed a (boot) image that didn't match the /system image in the slot you were working on. This error will persist in that slot every time you use that slot until it gets a fixed set of images.
Hope this helps!
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
If you are on bootloop, just simply flash magisk_uninstaller.zip on twrp
boot into system > then flash magisk on twrp again.
Perfect manual and working great
gtelnet said:
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
Click to expand...
Click to collapse
You Sir are the good damn man i have spent 3hrs trying to update to 9.5.9 cheers boss!!
Will this method work if I was a TMobile OnePlus 7pro which converted to international running 9.5.8 currently?
Yes if you are offered the aa rom in the updater
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
I just start the update under settings, system, syst update
It found new update and tell me he need to download full ROM (I have rmagisk installed).
While it was downloading full ROM I uninstall magisk from magisk app.
After update finish before restart I installed magisk again (option after ota update) and restart.
Now I'm updated and with magisk installed
Inviato dal mio GM1913 utilizzando Tapatalk
SlyUK said:
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
Click to expand...
Click to collapse
Yes I'm thinking, In the worst case it may be possible to use the stock updater as it senses root and downloads the full update now. Simply substitute the step where oxygen updater is used to download with the stock updater.
There may be a slightly longer delay before the stock updater offers an update as 1+ does it in waves. I have to hand it to 1+for even offering updates as most phones won't.
hi experts,
what and where to set or unset to make sure there is NO auto OTA update?
How do I control the update time on my op7p?
I'd like to avoid surprise of getting update in background that would / can remove root, magisk and etc that were manually added?
as example I use xXx over magisk and I's like to be prepared ahead of time to apply the OTA update
thanks for the education.
The 1+ updater has a setting to auto download updates or not. You can change it.
If we have TWRP installed could we get a guide for using the updater app?
kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
This is the method i use. Screenshot it from a thread here on XDA and unfortunately cannot remember the posters name to give credit. But it is the job!
kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Disable all Magisk modules and substratum themes
3.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App (OTA Option) **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
i.Design said:
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
3.) Disable all Magisk modules and substratum themes
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
Click to expand...
Click to collapse
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Pvt WhoOkid said:
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Click to expand...
Click to collapse
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
I had issues of bootloop where I would get past the unlocked message and boot up animation but then would freeze with my background showing only (no launcher, no status bar, etc).
i.Design said:
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
Click to expand...
Click to collapse
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
I was running Riru Core, edXposed and ended up dropping both, it wasn't worth the hassle for me since I run Renovate Ice and it does most of the tweaks I want from GravityBox (reason I was running Xposed).
Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
Try disabling all the modules and see if you can boot into 9.5.10 slot. If it does, reinstall them (then reenable them)
For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
Recommended TWRP from TWRP 3.3.1-xx Unified Unofficial by mauronofrio
**Official TWRP may not allow you to boot twrp.img**
OOSNativeCallRecording Module seems to be one culprit. Make sure to Uninstall before updating.
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
{
"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"
}
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop
you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image
mac796 said:
you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image
Click to expand...
Click to collapse
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.
diaztradeinc said:
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.
Click to expand...
Click to collapse
I will update it shortly, thank you for the feedback.
Bradl79 said:
For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
TWRP from here
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop
Click to expand...
Click to collapse
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...
matze19999 said:
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...
Click to expand...
Click to collapse
It's actually pretty simple, u just have to provide more instructions for people who haven't used twrp. There is no need to flash anything, ik that the uninmod does not work and I thought I tired mm and could not get it working either.
I use MM for TWRP since years and it always worked perfectly.
matze19999 said:
I use MM for TWRP since years and it always worked perfectly.
Click to expand...
Click to collapse
Have u used it with ur 7Pro yet? I tried it yesterday and would not flash along with uninmod would not mount magisk, I think it's issues with dual partition bc it did the same with my OP6
Bradl79 said:
Have u used it with ur 7Pro yet?
Click to expand...
Click to collapse
yeah. Whats not working for you?
matze19999 said:
yeah. Whats not working for you?
Click to expand...
Click to collapse
Got error when flashing, would u mind sharing the file?
Bradl79 said:
Got error when flashing, would u mind sharing the file?
Click to expand...
Click to collapse
I got the one to install from the download section but I've never used it I'm not sure how it works
He's right uninmod and stuff like that doesn't work at all now. It's unable to mount magisk.img it seems to be an issue with our twrp.
As for the statement about the issue being dual partitions that's wrong it's has nothing to do with that. I know he mentioned that uninmod and others did not work on op6 as well.. But it did cause I used uninmod on my 6 and 6T. This is an issue with this device only and possibly the twrp we have currently.
You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:
equlizer said:
You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:
Click to expand...
Click to collapse
Are u using OOSNativeCallRecorder module?
Yes i was using it. Just re-installed it.
Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?
spart0n said:
Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?
Click to expand...
Click to collapse
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson
mlock420 said:
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson
Click to expand...
Click to collapse
Well what I'm getting at is that I deleted all 4 of my magisk mods and fixed the bootloop and then reinstalled all 4 of them and rebooted and everything is fine now. I was asking about should we disable all mods, reboot, update, install magisk, reboot, check root with magisk then reinstall all mods and reboot again?
equlizer said:
Yes i was using it. Just re-installed it.
Click to expand...
Click to collapse
You prob only need to Uninstall that next time b/c that is one that is causing issues. I do not use and I have multiple Modules that survive update not needing to uninstall all modules.
Thanks. I had problem with pernament bootloop after magisk instalation.
Magisk Manager for Recovery Mode v7 202206260
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v19.0 - v25.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
- Source code
- Documentation
- Releases
- Original thread
Note: The GUI "Magisk Manager Recovery Tool" project is a different, stand-alone project.
Which is not affiliated with this CLI "Magisk Manager for Recovery Mode" project.
Edit1: Reported as working on Magisk v23.X! Updated the documentation and released a new version
Edit2: Tested and confirmed working on Magisk v25.X! Updated the module's readme, print lines, inner docs...
I might be doing something wrong but it's not working...
{
"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"
}
Poslano z mojega MI 9 z uporabo Tapatalk
mxxt01 said:
I might be doing something wrong but it's not working... View attachment 4997015
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
Sorry, all clear now [emoji16]
I was just about to try in TWRP...
Thanks!
Poslano z mojega MI 9 z uporabo Tapatalk
Rikj000 said:
Magisk Manager for Recovery v5 202004170
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v20.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
Flash this in TWRP each time you want to use it, not in Magisk itself.
You can download the new release from my GitHub: https://github.com/Rikj000/mm/releases/tag/2020.4.17
Original thread: https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
Click to expand...
Click to collapse
Thanks this will be handy when experimenting some modules
Sent from my Mi A2 using Tapatalk
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork
JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Same here.
Updater process ended with error: 123
Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Sent from my #FlagshipKiller6T using Tapatalk
DarkSJ1998 said:
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Click to expand...
Click to collapse
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.
Rikj000 said:
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork
Click to expand...
Click to collapse
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?
JamesKinds said:
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?
Click to expand...
Click to collapse
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP
Rikj000 said:
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP
Click to expand...
Click to collapse
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?
JamesKinds said:
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?
Click to expand...
Click to collapse
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Magisk v20.4 ERROR 123 ((( for Recovery
Latest Magisk Canary, working like a charm, thanks
Rikj000 said:
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.
Click to expand...
Click to collapse
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Sent from my #FlagshipKiller6T using Tapatalk
DarkSJ1998 said:
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Click to expand...
Click to collapse
Upon further inspection might be due to spaces in the zip file name. But magisk script wasnt up to date anyways. So this version will be supported in Magisk for a longer time then the original due to that.
Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
Bro, uninstall all versions this mod, reboot system, boot to twrp flash zip, go in twrp to terminal write mm, write q and click enter, boot to system, reboot to twrp go to terminal and type sdcard/mm important sdcard/mm, now should work
Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
I found the solution to the installation error eventually. The zip itself MUST be somewhere in internal storage when flashing and cannot be in sd card or otg. And even the old mmfr zip installs for me if I place it in internal storage. So maybe include this in your post. For context, I use Android Q rom with Magisk 20.4.