Stock rom + Magisk - Xiaomi Mi A2 Lite Questions & Answers

Hi I'm have one question.. any way to get TWRP and Magisk on last version of Stock rom?
Thanks for reply

Yes. They work just fine. Use the installation instructions in the appropriate threads. You should install TWRP first because installing TWRP breaks Magisk. If you install Magisk first you'll need to install it again after TWRP.

Related

Rooting problem open beta 17

After Root open beta 17 stook on boot logo
Any solution
Amar5373 said:
After Root open beta 17 stook on boot logo
Any solution
Click to expand...
Click to collapse
Well is it really too hard to explain your problem in proper sentences? So you wanted to root your phone. What did you use? Magisk? SuperSU? Which version? I can't help you if you don't provide information..
I have the same problem. Neither SuperSu nor Magisk works.
persa2011 said:
I have the same problem. Neither SuperSu nor Magisk works.
Click to expand...
Click to collapse
supersu not working please help
Use SuperSu 2.82
2.82 works fine for me! Many thanks!
My Steps For Stock OB17 Zip *Same Steps for Magisk V12 Or SuperSu V2.82*
Code:
Flash latest TWRP From Blu_Spark V35 Or Stock TWRP
Format Data Reboot TWRP
Wipe All
Copy [URL="http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_17/"]OB17[/URL], [URL="https://forum.xda-developers.com/devdb/project/dl/?id=25000"]TWRP V35[/URL], [URL="http://www.supersu.com/download"]SuperSU V2.82[/URL] To Internal Storage
Flash OB17
Select Flash IMG, Install TWRP Reboot TWRP (So Stock Rom Doesn't Replace With Stock Recovery)
Wipe Cache/Dalvik
Flash SuperSU
Reboot = Profit
*Optional*
Take A Backup Of Rooted Boot IMG (If You Flash A Custom Kernel And Run Into Issues You Can Restore Rooted Boot IMG With Ease)
Flash Kernel Of Choice (Beware Because Of No Source Code And Kernel Changes Might Be Some Issues With Custom Kernels)
TO root latest beta an stable version you can follow this guide:

root disappeared? 8.4 sm t320 on lineage 13

I'm on lineage 13, with sm t320. I flashed it this morning with other zips, downloaded apps from the play store, and then updated to the latest nightly (from 6/24). My device booted twice afterwards (the screen that you get right after you first flash lineage where it loads all of the apps) and it turned out that the root had disappeared along with the custom recovery. Not sure what exactly caused it... I've flashed it alone before (without other zips) and it worked fine. Has anyone else had their root disappear before?
So should I use cf auto root and odin and go through the whole connecting it to the computer process? Idk since I don't have the stock ROM anymore. Any help would be appreciated!
Lineage has a own root zip. You can find it under Lineage Downlode Extras. Addon su.ZIP.
You dont need to flash the CF autroot, if you install a customrecovery you can flash the lastest supersu.ZIP or the addon su.ZIP
bierma32 said:
Lineage has a own root zip. You can find it under Lineage Downlode Extras. Addon su.ZIP.
You dont need to flash the CF autroot, if you install a customrecovery you can flash the lastest supersu.ZIP or the addon su.ZIP
Click to expand...
Click to collapse
Thanks for your answer!
But I'd need root to install the custom recovery, right?
Sharksicles said:
But I'd need root to install the custom recovery, right?
Click to expand...
Click to collapse
You can flash a Custom recovery ( TWRP ) directly with Odin 3.09 without Root !
Okay, thanks ?

magisk not working on all OOS OREO ROMS

Hello xda community.
I got some knowledge about flashing stuff on my oneplus 3. But Since I use Android oreo beta 29, 30, or stable 5.0 OOS version even when I use the aroma installer from Freedom OS. Magisk doesn't install propobly. .
Im using latest Twrp from Bluespark 3.2.1 -X
I can flash most off the magisk versions 15.0 - 15.1 - 14.6 without bootloops. I tried alot off them but when I boot the phone magisk is not installed.(there is no Magisk app)
When I install the magisk apk. the magisk is also telling me magisk is not installed.
On beta 29 SuperSU was working didn't try it yet on beta 30 but I really want to use Magisk.
I'm reading the forums here also on the OP community but seems like I'm the only one with this problem.
uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine
theduke7 said:
uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine
Click to expand...
Click to collapse
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....
Ghost123NL said:
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....
Click to expand...
Click to collapse
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....
theduke7 said:
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....
Click to expand...
Click to collapse
Also not working.
same steps with supersu is working only
Ghost123NL said:
Also not working.
same steps with supersu is working only
Click to expand...
Click to collapse
maybe the only way to make sure is to wipe everything , did you try with custom kernel?
try to flash rom reboot to recovery, then derp kernel (tested and works on latest beta) , then flash magisk... that worked for me at 1st try.
Flash magisk 14.0 and boot see magical working and then update magisk15.3 via magisk manager application.
Use OOS debloater from the themes and apps section to remove some apps from the system. Then reinstall magisk. Problem solved. We have a lot less space left in the system partition and that's the reason magisk is silently failing to install.
Facing same issue

Multidisabler is necessary?

I have a rooted exynos note10+ using stock rom and wanted to install TWRP to install a kernel that doesn't need the button combo at boot.
I only found tutorials for install TWRP in android 10 and they install a package called multidisabler. When I used the TWRP to flash the newer versions of multidisabler my phone got stuck at a black screen after the warning.
This package is necessary? I wanted to use TWRP to flash things and make backups.
Thank you.

Question after device restart magisk root lost

hello
I have rooted my device with magisk patch boot image and it work .my device is rooted.
but when I restart my device root has lost.
I have try 3-4 time this process but each time after device restart root has lost.
pls help...
miui version- miui global 14.0.3
magisk version - 26.1
wakram001 said:
hello
I have rooted my device with magisk patch boot image and it work .my device is rooted.
but when I restart my device root has lost.
I have try 3-4 time this process but each time after device restart root has lost.
pls help...
miui version- miui global 14.0.3
magisk version - 26.1
Click to expand...
Click to collapse
I suggest you install the latest Orang fox recovery if you don't have it or if you don't have custom recovery. Ive had issues with magisk "sticking" bc of the installed recovery. Flash Magisk zip via recovery then reboot to system and make sure it's still there. Make a copy of magisk zip and rename it "uninstall.zip" Then reboot to recovery and flash uninstall.zip. Then reboot to system then again to recovery and reflash Magisk zip. You can also try installing magisk alpha
Aserar said:
I suggest you install the latest Orang fox recovery if you don't have it or if you don't have custom recovery. Ive had issues with magisk "sticking" bc of the installed recovery. Flash Magisk zip via recovery then reboot to system and make sure it's still there. Make a copy of magisk zip and rename it "uninstall.zip" Then reboot to recovery and flash uninstall.zip. Then reboot to system then again to recovery and reflash Magisk zip. You can also try installing magisk alpha
Click to expand...
Click to collapse
i don't want to install custom recovery.[ bcz of ota update].
is there any way to fix this issue?
Flash Magisk zip
wakram001 said:
i don't want to install custom recovery.[ bcz of ota update].
is there any way to fix this issue?
Click to expand...
Click to collapse
Most people will have minimum to no experience regarding your situation honestly since its rare to root without the safty of a custom recovery. I think you should ask in the main magisk XDA thread or consider a custom recovery. Its hard to pinpoint the reason in this situation
Aserar said:
Most people will have minimum to no experience regarding your situation honestly since its rare to root without the safty of a custom recovery. I think you should ask in the main magisk XDA thread or consider a custom recovery. Its hard to pinpoint the reason in this situation
Click to expand...
Click to collapse
ok now I will consider custom recovery.( twrp ).

Categories

Resources