Hello, this morning I thought I'd try to apply Oneplus OTA update, but while keeping Magisk and its modules installed.
So I googled it and I was candid enough to follow this tutorial.
Here are the exact steps I followed:
Apply the Oneplus OTA update (download & install) BUT did not reboot
Magisk Manager → Uninstall → Restore Images (Maybe that's where I screwed up as I should have run this before above step?)
installed TWRP A/B Retention Script from Magisk Manager (installed module but did not reboot).
Magisk Manager → Install Magisk → Install to Inactive Slot
Pressed the reboot button in Magisk Manager
Now the phone rebooted, oneplus boot logo, then phone unlock screen and automatically "restarted" as shown on this picture:
{
"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"
}
And then it rebooted into TWRP, asking for my password. After I enter the password, TWRP decrypt my partition and then I don't know what to do.
I flashed magisk again, but with no luck.
Thanks a lot in advance for your help and suggestions!
[EDIT] here is what happen when I flash twrp zip installer
Shoud I flash FULL oneplus firmware from this link?
I solved it by flashing oneplus full update image, then directly flashing twrp (from twrp), then flashing magisk, and finally rebooting.
I spoke too fast.
I was able to boot into oneplus system, but Magisk was not there anymore.
So I booted into recovery (twrp), flashed magisk (it said flashing on slot A this time), rebooted: Bam, same bootloop issue than before!!
Is it related to magisk modules that were not disabled? Or what?
Any feedback would be much appreciated! Thanks
Ok, so finally I did identified the root problem : Magisk module incompatibility! The faulty module is LOS Call Recorder, so I had to do this:
Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Yes the guide specifies you disable modules. If you skip that you will boot loop. You could have gone back to the other slot and disabled them or disabled them from TWRP and then booted the new slot.
larsdennert said:
Yes the guide specifies you disable modules. If you skip that you will boot loop. You could have gone back to the other slot and disabled them or disabled them from TWRP and then booted the new slot.
Click to expand...
Click to collapse
I agree, and to elaborate one step further than this, I had the exact same issue and found that you don't just have to disable the modules, but you have to fully remove them (using the little trash icon in Magisk). I've heard the call recording module causes issues, but from now on I remove all of them to avoid the issue.
The way that I solved it post-bootloop was by booting to TWRP (either your phone retained it or use Fastboot boot with the .img file), and then using the function in TWRP 'Advanced > File Explorer' browsing to access 'Data\adb\modules'. For each offending module, browse into the module folder, then hit the blue folder icon on the bottom right to select and delete the entire folder. Be sure to only do this to the specific modules, I don't want you accidentally removing anything core to the OS.
That's the steps that worked for me I hope this helps you!
You actually don't have to trash them but it makes it clearer to most people. The issue is that after the update, Magisk thinks a particular module is installed when it isn't. If you simply disabled it previously, you can boot no problem after the OTA however if you then reenable the module, your next boot will loop because the module isn't there. Confusing so really the best advice is to uninstall modules and reinstall them so that nobody will simply reenable a dead module.
I'm having this exact issue, except I DON'T HAVE ANY MODULESSS
I don't know what to do... I've completely factory reset and it still didn't help
Have you flashed full stock without root?
larsdennert said:
Have you flashed full stock without root?
Click to expand...
Click to collapse
Haha, I actually did and that was the fix... After many Magisk Uninstaller flashes and Magisk installations, I realised the issue was with the OS itself, and flashing the stock image replaced the boot image which was causing the problem (I think... Idk if I'm right about this)
Depending on the phone model you'll need another rooted boot image. If you need a current one for the 1917, I can get you one.
Hi so i'm having this exact problem. Is there any solution that doesn't include a factory reset? Currently I'm stock os android 10 and was running magisk 20.4. had a bootloop uninstalled all modules etc and still bootloop. Only when I uninstall magisk does my phone boot to system. Reflash and we get a bootloop. Does anyone know what could be corrupted etc to stop magisk from rooting my phone? I'm sure a factory wipe will fix this but surely theres a better way.
Again,works perfectly without magisk installed. Then install magisk and we get a bootloop. Please help.
Try removing magisk manager and then flash magisk. How are you doing magisk? With an image or twrp? Could be you are using a bad boot image.
larsdennert said:
Try removing magisk manager and then flash magisk. How are you doing magisk? With an image or twrp? Could be you are using a bad boot image.
Click to expand...
Click to collapse
Magisk has been fully removed by flashing the zip file in twrp. Everything is deleted. When I reflash the zip in twrp I get a bootloop. It's the same steps as I originally used to root the phone without issue.
You understand that magisk is two parts? Boot code and an apk to manage settings. Was the apk also removed?
larsdennert said:
You understand that magisk is two parts? Boot code and an apk to manage settings. Was the apk also removed?
Click to expand...
Click to collapse
Yes when you run the installer it removes the apk also. So when I can boot back to the os there is no trace of the manager apk.
Bxperiaz3 said:
Yes when you run the installer it removes the apk also. So when I can boot back to the os there is no trace of the manager apk.
Click to expand...
Click to collapse
Try checking the /data/adb/modules to see if any modules is present,magisk don't result in bootloop unless it's one of the modules that you installed.
Uninstaller should have removed the modules,just check in twrp
You can also try flashing magisk after flashing stock boot image(use the correct versions one),maybe boot image might be corrupted
Joker123## said:
Try checking the /data/adb/modules to see if any modules is present,magisk don't result in bootloop unless it's one of the modules that you installed.
Uninstaller should have removed the modules,just check in twrp
You can also try flashing magisk after flashing stock boot image(use the correct versions one),maybe boot image might be corrupted
Click to expand...
Click to collapse
All modules have been removed. I might try flashing the stock boot image and see if that helps. my other plan was to dirty flash the stock rom and the magisk again to see if this repairs the problem.
---------- Post added at 10:49 PM ---------- Previous post was at 10:23 PM ----------
SOLVED!
In case anyone runs into this issue in future. I'm guessing something must have happened to the boot image because I fired up TWRP, cleared Dalvik, flashed the stock os, booted straight back to recovery, flashed TWRP again, then magisk 20.2. Then I switched slots and did the same thing and then rebooted. Now I have everything working again, magisk updated to 20.4 and no data or app loss. Very happy
Related
How to root samsung j max [sm-t285yd] ???
Pls help...!!!
Plz help me... I can't root my Samsung {t285yd} J max.
:crying:
i also want to root this device. i try all things like king root,towel root everything but no luck.. devloper plz help us to root this device.
Nothing Work
I have been working on a root for this device for the last 6 months. The only place I have made any headway was CF Auto-root. I'm not able to post links yet so just search cf auto root. On the page type sm-t285yd and two options will pop up. Choose one and look for your firmware build. I have not been able to root as of yet, even with this site. It gives you boot/recovery/cf auto-root package. Most of the problems I have faced are due to not being able to get to the recovery once it is flashed in Odin. I will be searching for answers and root until I find one. Of course, I will post it here when I finally break my phone.
Some Light in the Tunnel
I have made some headway with Magisk. I have never used any of the software associated with Magisk, but it seems at least for now, it will do the trick. I will dive into it further tonight and try to post an update shortly.
-Two sites to jump to.
Search Magisk for the best step-by-step
magiskmanager(dot)com - Has great info about magisk
UPDATE: Rooted!! WooHoo!
{
"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"
}
TalokiN said:
I have made some headway with Magisk. I have never used any of the software associated with Magisk, but it seems at least for now, it will do the trick. I will dive into it further tonight and try to post an update shortly.
-Two sites to jump to.
Search Magisk for the best step-by-step
magiskmanager(dot)com - Has great info about magisk
UPDATE: Rooted!! WooHoo!
Click to expand...
Click to collapse
In order to flash Magisk you need to have a custom recovery right?. So may I know how you did it?.
You don't need a custom recovery for Magisk. From here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) you follow the odin steps.
there are two ways to install, first was "via custom recovery" and the other "via Magisk Manager v14.0+"
This method does not require root or custom recovery.
you'll need a stock boot image you can extract from tar or md5
Here are the instructions from XDA not my work "By topjohnwu, Recognized Developer / Recognized Contributor on 3rd October 2016, 06:00 PM"
"This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually"
Hope this helps!
Modules working now
I have had a hard time trying to get modules to work in magisk.
Steps taken:
completely removed magisk
re-installed everything
i decided to try a few things
BOOM!! busybox install fixed it all.
Samsung Galaxy Tab J Max SM T-285YD Root with Magisk
I am using magisk for last 5 months. Everything was just fine except one problem.Though my internal storage was blank but it showed that there was no space for new app installation. I had 3 GB blank in internal storage whichi managed to get by linking apps and OBB data to external storage . Please help me if anyone knows any way to get apps installed. Screenshots are attached. Regards
Magisk not working
I also have SM-T285YD and tried magisk flashing the patch boot via odin yesterday ....... i did twice but both the times my device stucked on boot loop please any one help me why it is happening or any other way to root I also found that the twrp builders have created the TWRP file for this device but while flashing via odin i found that the file is in .img format so m not getting the option to flash that please someone help me out through this
Hi,
I have found a twrp for this device in twrp builder.
How ever there is no custom rom it...
Best regards......
j max said:
Hi,
I have found a twrp for this device in twrp builder.
How ever there is no custom rom it...
Best regards......
Click to expand...
Click to collapse
Yes I also found that but thatz in .img format i cant do that via odin ??
AhteVirus said:
Yes I also found that but thatz in .img format i cant do that via odin ??
Click to expand...
Click to collapse
I already have flashed the twrp.
Just you need to make it flashable tar
twrp
yes made it flashable and flashed successfully as per instructions but now when i open it dat shows in red recovery is not seandroid and stucks there only ......and then i have to restart the device
Root Samsung J Max SM-T285YD
Sir Try to many app many proccess but not install TWRP,also Use CF Auto Root,Magisc,king root,kingoroot,dr.foneroot,etc. But Not root my Phone Pls Help me..................
Samsung Galaxy tab J SM-T285YD Dual Sim ROOTED
Hello everyone, this is my first post on XDA, I hope I won't be boring anyone. But it seems that there is no complete guide or tutorial to root the SM-T285YD. I will post here what I did to root it, I followed the lead of some of the other users in this thread and some from other sources.
My device is the SM-T285YD Dual Sim. Here is what I did;
I checked which rom I had installed on my device, it was stock rom from Taiwan, ****T285YDZTU0APL2, android version 5.1.1
I googled for the rom and found it somewhere, it wasn't difficult. I went with Magisk. The instructions were: copy the rom to your device. Here comes the problem, the rom is 2GB it will take up the little free storage left on your internal. So I copied it to my SD card instead. Next instruction, install the magisk apk, version 7. Go to settings in magisk and change the output format to what you intent to use to flash it with after you're done. You have two options; *.img or *.tar. I intended to use Odin to flash when I was done, so I chose *.tar.
When you open Magisk, it will tell you it is not installed, so click install, after which two options appear. Choose "patch rom", select the downloaded rom you saved to your sd card and wait. It will produce a patched boot image in *.img or *.tar file of about 8MB and saves it in your download folder in your internal storage. It may save it in the Magisk folder, just look for it once it is done patching. Copy this patched boot file back to your PC and put the tablet in download mode, then flash it, I had a tar and flashed it with odin 3.10.6
A problem that occurred with me was, although I copied the stock rom I downloaded to the SD card, I still didn't have enough space on my internal storage for Magisk to do it's job, so I had to delete EVERYTHING I could. Flashing went lightning fast and the reboot only took a minute or so longer than normal. ROOTED!!!
Good luck everybody. Hope it helps.
(I edited the text here to make it hopefully clearer and easier to understand, some people didn't quite get it, hope it is clearer now. Of course, as always, if you're not sure about it, or new to it, leave it alone. There is always the risk to brick your device)
It should work if you do it right. Good luck!
This doesn't help.
What didn't work, exactly?
Doctorrico said:
What didn't work, exactly?
Click to expand...
Click to collapse
It does not work, after flashing when I restart the tablet a red text appears in the left corner saying "KERNEL SEANDROID IS NOT ENFORCING" and it stucks on there. I tried to restart it lots of times also did a factory reset but nothing is 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"
}
Greetings M2 Note users,
Welcome to simple guide for installing,rooting Lineage 14.1 and installing Dolby Atmos sound mod for better sound.
Code:
[SIZE="3"]#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
*/[/SIZE]
So LET'S BEGIN.
Step 1. DOWNLOAD ROM AND GAPPS
*ROM*
You need to download Lineage 14.1 rom from its thread and Gapps package which you can find below.
LINEAGE OS 14.1 THREAD
*OPEN GAPPS*
CHOOSE ARM64 platform,Android 7.1.1 version, and VERSION of package you want ( i recommend downloading pico version)
OPEN GAPPS PROJECT OFFICIAL WEBSITE
Step 2. DOWNLOAD MAGISK AND DOLBY ATMOS MODULE
*MAGISK*
Go to official Magisk thread HERE and download Latest Magisk zip (for now latest stable version is v14.0)
*DOLBY ATMOS MAGISK MODULE*
Download Lenovo A7000 [6.5] Atmos (1.1.4) from module thread HERE
Mirror download link with older version that is compatible with Magisk 14.0 *HERE*
Step 3. FLASHING ROM,GAPPS,MAGISK AND DOLBY MODULE
1. Reboot to TWRP 3.1.1.0 recovery (if you dont have this version you must flash it,download it from HERE)
2. Go to Wipe,choose Advanced wipe and check Cache,dalvik-Cache,System and Data. After wiping is done go to Install.
3. First choose Rom zip(flash it,then wipe cache,dalvik-cache),then install Gapps,then Magisk .zip and in the end flash Dolby Atmos module.
4. After you done flashing everything mentioned above, WIPE cache,dalvik-cache and reboot to system.
5. Wait for system to boot (it may take few minutes,be PATIENT!!!) and enjoy your now flying phone
6. After you setup phone open Dolby Atmos app and turn equalizer ON,and set it like on picture in Attachment.
THATS IT!
You now have lag free phone with loud speakers.
ENJOY!!
Is it necessary to use magisk..
Can i use super su?
Darryl3d said:
Is it necessary to use magisk..
Can i use super su?
Click to expand...
Click to collapse
You can.
I just prefer Magisk over Supersu.
Sent from M2Note
Hi, after I managed to install it step by step... but why this takes a lot of time. The time has run more than thirty minutes and my device stays in boot lineage logo. Is it taking this much time or am I getting a bootloop or brick?
I cant install the dolby atmos package. I already have lineage 14.1 and magisk 14.0. When I install the dolby package from recovery it says installation succesful but nothing shows up in my apps or magisk modules.
jepu said:
I cant install the dolby atmos package. I already have lineage 14.1 and magisk 14.0. When I install the dolby package from recovery it says installation succesful but nothing shows up in my apps or magisk modules.
Click to expand...
Click to collapse
Try downloading the dolby atmos via magisk manager then flash it there. It worked for me. And don't forget to turn off the default android audiofx (i managed to force close it, then turn on the dolby atmos).
Thank you for this great guide, I have installed LineageOS, Magisk and Dolby Atmos succesfully on my m2note. However, root access provided by Magisk can't allow root apps like apps2sd or other to work.
Shoul I install supersu to gain root access like in my previously flymeos rom?
jatzio said:
Thank you for this great guide, I have installed LineageOS, Magisk and Dolby Atmos succesfully on my m2note. However, root access provided by Magisk can't allow root apps like apps2sd or other to work.
Shoul I install supersu to gain root access like in my previously flymeos rom?
Click to expand...
Click to collapse
Dont install supesu(no point of instaling 2 superuser apps).
And which version of Magisk you flashed 14.0 or 15.3.
Root permissions on 15.3 doenst work on LOS atm,so flash magisk 14.0 and you will have proper root access for all root apps you want.
n0p3zz said:
Dont install supesu(no point of instaling 2 superuser apps).
And which version of Magisk you flashed 14.0 or 15.3.
Root permissions on 15.3 doenst work on LOS atm,so flash magisk 14.0 and you will have proper root access for all root apps you want.
Click to expand...
Click to collapse
Ok thank you. I Flashed Magisk 15.3, then I tried reflashed it to Magisk 14.0. Now root access worked. Anyway, what if I wan to revert back to meizu stock rom/flymeOS, should I flash update.zip immediately or should I uninstall magisk first? This is just my curiosity
jatzio said:
Ok thank you. I Flashed Magisk 15.3, then I tried reflashed it to Magisk 14.0. Now root access worked. Anyway, what if I wan to revert back to meizu stock rom/flymeOS, should I flash update.zip immediately or should I uninstall magisk first? This is just my curiosity
Click to expand...
Click to collapse
DONT flash Flyme update.zip from TWRP recovery. You will get bricked phone. You can flash Flyme from SPFlash tools or download TWRP flashable .zip from 4pda and flash it in TWRP.
Because some work-related urgency, I flashed update.zip from TWRP, carelessly swipe to reboot when a dialog of 'No OS installed, are you sure want to reboot' appeared. So I got my m2 soft-bricked yesterday.
However I'm lucky enough to revert back to flyme OS using SPflash tools and just checked preloader option while flashing. Now my phone 'usable' again. I will wait for Lineage OS future update, and stay on flyme at the moment, and no PKMN go for me again.
Thank you
Hi, When i Want to flash the rom, an error appeared : Updater process ended with ERROR: 7 Error installing zip file '/sedcard/lineage-14.1-20180117-UNOFFICIAL-m2note.zip
What cause this error ?
Now when I connect my phone, it says that the device is not recognized :/
I been able to install LineageOS, I fixed it by pressing home and menu button, it disconnect and reconnect and i been able to Re-flash it with the recovery and when i tried to install Lineage, my error was gone (error 7)
Is there a way to root the phone ?? because I have magisk installed but when I go to the developper option, the root option is greyed out
Can I install Dolby Atmos withoug gapps?
herishere said:
Can I install Dolby Atmos withoug gapps?
Click to expand...
Click to collapse
Yes you can. Just skip flashing gapps step.
Hello, I can't install Dolby Atmos on LineageOS 14.1. If I flash it in TWRP, it shows I need Magisk 15.3 or higher but any Magisk version above 14 is not properly working. I downloaded older version from MEGA. Thanks for help in advance.
I installed the Lenovo Atmos file as suggested... but now I have all the time a screen message "Dolby cannot start" or something like that. So no working and need to do full wipe, as the message is re-appearing continuously :'(
Will keep trying.
Anyone knows how to do (increase volume) it manually? I don't have the "mixer_paths.xml" anywhere, neither the /etc/sounds folder
Thanks
mdabar said:
I installed the Lenovo Atmos file as suggested... but now I have all the time a screen message "Dolby cannot start" or something like that. So no working and need to do full wipe, as the message is re-appearing continuously :'(
Will keep trying.
Anyone knows how to do (increase volume) it manually? I don't have the "mixer_paths.xml" anywhere, neither the /etc/sounds folder
Thanks
Click to expand...
Click to collapse
Hi guys,
I wiped everything and start from scratch... Now I'm with Lineage 14.1-20180523 and despite I followed all the steps (Magisk + Dolby...) The sound is still way too low :crying:
I've tried manually searching the files and sound config, but nothing, they're not. And even tried modifying some of the existing files related to volume... But no changes either.
So I'll keep looking and trying for the moment.
Any ideas? How do you use the Dolby app?
I read that we have to disable the system's Audio FX app. I can't force stop it, but not disable it. And when I open and configure Dolby like in the picture, I don't perceive any changes.
Help please!
Thanks
You need to download older version from GitHub... When I find a link I will provide it
mdabar said:
Hi guys,
I wiped everything and start from scratch... Now I'm with Lineage 14.1-20180523 and despite I followed all the steps (Magisk + Dolby...) The sound is still way too low :crying:
I've tried manually searching the files and sound config, but nothing, they're not. And even tried modifying some of the existing files related to volume... But no changes either.
So I'll keep looking and trying for the moment.
Any ideas? How do you use the Dolby app?
I read that we have to disable the system's Audio FX app. I can't force stop it, but not disable it. And when I open and configure Dolby like in the picture, I don't perceive any changes.
Help please!
Thanks
Click to expand...
Click to collapse
This is tutorial how to install XPOSED on POCO F1 MIUI global 10 and 11
This is a guide for experienced users ONLY!.
These are the steps for a phone that has already been rooted .
This is new full working Xposed method tested by me.
Download all files from the attachment and copy it to your phone.
Delete all previous old xposed modules
1. Open Magisk application on your phone
2. Go to Modules, and press +
3. Install first magisk-riru-core v18, after installation of the module press close. Then press + again and install magisk-EdXposed-SandHook-v0.4.1.2_beta-release, press close again and reboot your phone.
4. Install EdXposedInstaller_v2.2.4-release normally AND DON'T UPDATE IT. You can update modules but not installer..
5. You can do update via Magisk Manager.
Open Xposed app, and you should see this on your screen:
{
"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"
}
Another must have tool is Magisk Manager for Recovery made by VR25.
How to use MM (magisk manager) for recovery in TWRP.
1. Download file form provided link and put it on your phone memory.
2. Enter to recovery mode , go to Install and flash the file mm20190404.zip and do not reboot, just go back to main menu.
3. Go to Advanced, then open terminal
4. Write mm and pres enter
5. Pres l to get list of installed modules
6. You can disable or remove modules form here.
You must repeat all these steps every time you want to start MM
It will look like this:
If someone have trouble with SafetyNet check, just add Google play services to Black list in EdXposed.
1. Enable Black/White list in EdXp Settings
2. Add Google services to black list
3. You will pass SafeyNet Check
You can update to MIUI Global 11.0.5. Everything works fine. Just follow my update steps.
1. Open Magisk
2.Go to uninstall than choose RESTORE IMAGES
3. Reboot phone
4. Go to settings/about phone/system update
5. Download update and install it.
6. After update, go to fastboot, pwr+volume down
7. Connect your phone to PC, open cmd or power shell with admin privileges and go to platform tools folder , then type like first time fastboot flash recovery twrp-3.2.3.0-beryllium.img, then fastboot boot twrp-3.2.3.0-beryllium.img ( change the name of image file if it is different on you PC)
8. Flash Magisk again
9. Reboot
10. All should be like before update
Wrong place to post. You should move to the themes and mods section. But GJ.
Thread updated.
Sent from my POCO F1 using Tapatalk
Will this pass safetynet in magisk?
what xposed-mods do you use?
ctsuresh said:
Will this pass safetynet in magisk?
Click to expand...
Click to collapse
Edit: Safetynet is passing, so there is no issue using this xposed.
MechaNarutoSucks said:
Wrong place to post. You should move to the themes and mods section. But GJ.
Click to expand...
Click to collapse
It's a guide. Technically, it is a mod but the post shows guide and installation.
ctsuresh said:
Edit: Safetynet is passing, so there is no issue using this xposed.
Click to expand...
Click to collapse
OMG! Xposed + Safetynet? I'll try today
I'm really excited
if i use it on lineage do i need to turn off modules before OTA update to prevent bootloop or its fine ?
In order to apply OTAs, you have to open Magisk Manager go to Uninstall \Restore Images. Don't reboot or you will have Magisk uninstalled. This will restore your boot and back to 100% untouched stock images in order to pass pre-OTA block verifications.
Cara... Você salvou a minha vida... Obrigado !!
You is the best....
Working like a charm on Poco F1 running stable 10.3.4.0. Thanks!
Edit: sometimes when I turn on the phone, it go into bootloop. I need to restart manually one or more times to start correctly. I have updated to riru core and edxposed lastest versions.
Edit 2: looks like to be related to minminGuard module. After uninstall it, everything is working as expected.
Yes.You must be careful when you choose a modul. You have update for minminguard.
Sent from my POCO F1 using Tapatalk
bixirulo said:
Working like a charm on Poco F1 running stable 10.3.4.0. Thanks!
Edit: sometimes when I turn on the phone, it go into bootloop. I need to restart manually one or more times to start correctly. I have updated to riru core and edxposed lastest versions.
Edit 2: looks like to be related to minminGuard module. After uninstall it, everything is working as expected.
Click to expand...
Click to collapse
I tested new 2.0.9 version and everything works good. No bootloop. But i found that minminGuatd is not very effective in removing ads. I recomand that you use lucky patcher instead. Inapp purchase option.
But something is buggy with this modul...avoid it.
Sent from my POCO F1 using Tapatalk
@delevic Have you tried "customiuizer" module? Also stuck at boot screen randomly...
Which edxposed version you use ?
Just tested customiuizer. No bootloops no bugs. Write me all your installed versions from magisk riru edxposed ...
Sent from my POCO F1 using Tapatalk
Thanks for sharing.i am use 9.3.21 eu beta weekly and working well.no bootloop everything is okey now
I am testing now magisk-EdXposed-SandHook-v0.4.2.3_alpha-release.zip So far so good
4. Install EdXposedInstaller_v2.2.4-release normally.
Click to expand...
Click to collapse
what is meant by "normally"?
Just install apk fille like all other app. Find apk fille and press enter
Sent from my POCO F1 using Tapatalk
Just got it this morning on my stock version 9
{
"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"
}
Dude+ said:
Just got it this morning on my stock version 9
View attachment 4874129
Click to expand...
Click to collapse
I cant root this version
GabrielBPereira said:
I cant root this version
Click to expand...
Click to collapse
Oooooooof I thought it was only me and I was doing something wrong!!!
Was just about to do it ! Glad I read this....I assume you tried with magisk 20.1 ?
I'm not rooted and haven't tried yet. I'm no help there.
buddy96 said:
Was just about to do it ! Glad I read this....I assume you tried with magisk 20.1 ?
Click to expand...
Click to collapse
I yes, 20.1 dont work... I have bootloop ...
buddy96 said:
Was just about to do it ! Glad I read this....I assume you tried with magisk 20.1 ?
Click to expand...
Click to collapse
You can do it. You just need to root with magisk 19.3 and use the forceencrypt disabler file from 8/8/20 not the recent one and it will work.
Jemec26 said:
You can do it. You just need to root with magisk 19.3 and use the forceencrypt disabler file from 8/8/20 not the recent one and it will work.
Click to expand...
Click to collapse
ok ! do you keep it as 19.3 or do you then update it to 20.1 using magisk manager ?
buddy96 said:
ok ! do you keep it as 19.3 or do you then update it to 20.1 using magisk manager ?
Click to expand...
Click to collapse
Keep it 19.3.
Jemec26 said:
You can do it. You just need to root with magisk 19.3 and use the forceencrypt disabler file from 8/8/20 not the recent one and it will work.
Click to expand...
Click to collapse
Forceencrypt 8/8/20 ? You have link ?
I dont have bootloop ?
GabrielBPereira said:
Forceencrypt 8/8/20 ? You have link ?
I dont have bootloop ?
Click to expand...
Click to collapse
No bootloop. Don't have a link sorry, I got it from the Telegram group
Magisk 20.1 does work. No bootloops. If you are starting fresh, just install TWRP and do the usual 2 full wipes, then flash Magisk 20.1 and boot to system. The Dm-Verity file is no longer needed, as Magisk does it for you. That's where I was having problems rooting it. The Dm-Verity_ForceEncrypt was the cause of the bootloops.
UPDATE : The removal of Forced Encryption is needed. Just Remove the "Dm-Verity" from the zip file name. I'm using the 10.20.2019 version. The filename should be changed to "Disable_ForceEncrypt_10.20.2019.zip". I didn't use the file at all the first time, and recovery was unable to mount data because of it. But the Dm-Verity part of that zip is what was causing all of my bootloops.
Did you have "Preserve avb 2.0/dm-verity" checked in magisk manager before re-flashing ? Default is unchecked, I'm wondering what would trigger encryption to remain disabled during the first reboot.
buddy96 said:
Did you have "Preserve avb 2.0/dm-verity" checked in magisk manager before re-flashing ? Default is unchecked, I'm wondering what would trigger encryption to be remain disabled during the first reboot.
Click to expand...
Click to collapse
I didn't change any of the default Magisk settings. I have no clue why it allowed the 1st reboot to have no encryption, but it was definitely encrypted on the 2nd reboot. Everything was working fine, then I tried to go to recovery again after I had everything setup the way I like it and make a backup, and that's when TWRP was showing the encryption dialog. I had to reset and start over because of that.
Just seen your edit to #12, makes sense now. Encryption occurs during first boot if not disabled.
xfrobex said:
Magisk 20.1 does work. No bootloops. If you are starting fresh, just install TWRP and do the usual 2 full wipes, then flash Magisk 20.1 and boot to system. The Dm-Verity file is no longer needed, as Magisk does it for you. That's where I was having problems rooting it. The Dm-Verity_ForceEncrypt was the cause of the bootloops.
UPDATE : The removal of Forced Encryption is needed. Just Remove the "Dm-Verity" from the zip file name. I'm using the 10.20.2019 version. The filename should be changed to "Disable_ForceEncrypt_10.20.2019.zip". I didn't use the file at all the first time, and recovery was unable to mount data because of it. But the Dm-Verity part of that zip is what was causing all of my bootloops.
Click to expand...
Click to collapse
what would be the correct procedure? twrp, after the two wipe on "data", flash "Disable_ForceEncrypt_10.20.2019.zip", then magisk? without rebooting?
dont start telephone ...
xfrobex said:
Magisk 20.1 does work. No bootloops. If you are starting fresh, just install TWRP and do the usual 2 full wipes, then flash Magisk 20.1 and boot to system. The Dm-Verity file is no longer needed, as Magisk does it for you. That's where I was having problems rooting it. The Dm-Verity_ForceEncrypt was the cause of the bootloops.
UPDATE : The removal of Forced Encryption is needed. Just Remove the "Dm-Verity" from the zip file name. I'm using the 10.20.2019 version. The filename should be changed to "Disable_ForceEncrypt_10.20.2019.zip". I didn't use the file at all the first time, and recovery was unable to mount data because of it. But the Dm-Verity part of that zip is what was causing all of my bootloops.
Click to expand...
Click to collapse
I tried these steps immediately after flashing the oct 1 patch and couldn't get it working. I tried both Magisk 19.3 as the other comment suggested, and the latest 20.1 - both resulted in bootloops. Any idea what might fix this, or some mistake I overlooked?
today launched december patch, brazillian phone
I don't understand why everyone is using this awful Disable_Dm-Verity_ForceEncryption.zip??
As xfrobex already said the disable dm-verity option is no longer needed thanks Magisk. But to disable the encryption of your device you don't need to flash the .zip, too!
Open the fstab.qcom file and edit the mount flags of /userdata like this:
Instead of "forceencryption" => "encryptable"
That's all!
As I red many times in several threads this .zip causes more problems instead of being an advantage...
Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really 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"
}
StyleM said:
Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really appreciated.
View attachment 5324283View attachment 5324285View attachment 5324287
Click to expand...
Click to collapse
try using magisk 20.4 n dont update just keep the 20.4 version
howdeedodat said:
try using magisk 20.4 n dont update just keep the 20.4 version
Click to expand...
Click to collapse
Hey man thanks for the tip. I first wiped data, cache, dalvik and system, then flashed lineageos 15.1 with magisk 20.4 and gapps. I setup magiskhide and changed the package name. I also installed the magisk hide props. What am i missing
I noticed on a forum somewhere that for magisk hide module you're supposed to open a terminal and run props command... What do you do from there? I'm so confused, i have no clue whats wrong.
Fyi the error is still the same see below images.
One thing i did differently now was that i didnt reflash stock first (just flashed lineage magisk and gapps after wiping)... Do you think it makes a difference?
I'll give it a try tomorrow as i was in a rush.
StyleM said:
Hey man thanks for the tip. I first wiped data, cache, dalvik and system, then flashed lineageos 15.1 with magisk 20.4 and gapps. I setup magiskhide and changed the package name. I also installed the magisk hide props. What am i missing
I noticed on a forum somewhere that for magisk hide module you're supposed to open a terminal and run props command... What do you do from there? I'm so confused, i have no clue whats wrong.
Fyi the error is still the same see below images.
One thing i did differently now was that i didnt reflash stock first (just flashed lineage magisk and gapps after wiping)... Do you think it makes a difference?
I'll give it a try tomorrow as i was in a rush.
Click to expand...
Click to collapse
the 5th picture which is show the emulator function, it will help u to change device fingerprint, just make sure u found the correct one for ur phone n u will be totally succesfull passing the safety net, but before u do that might be this thread could fix ur safety net without using the terminal emulator ?
howdeedodat said:
the 5th picture which is show the emulator function, it will help u to change device fingerprint, just make sure u found the correct one for ur phone n u will be totally succesfull passing the safety net, but before u do that might be this thread could fix ur safety net without using the terminal emulator ?
Click to expand...
Click to collapse
Do i need to sideload this on the rom, or is it a magisk module (magisk didnt like thst zip tile)
StyleM said:
Do i need to sideload this on the rom, or is it a magisk module (magisk didnt like thst zip tile)
Click to expand...
Click to collapse
flash it in magisk or sideload theres no different as long u have tha magisk on ur phone because its a magisk module