Related
Hello guys i want to use Crdroid official 4.2 Treble build on my Redmi 3S with Magisk - 16.4 [treble flashable zip. But when flash Magisk 16.4, I was found Error 1 in my Twrp Recovery.
Using Rom : Crdroid official 4.2
Recovery : TWRP 3.2.1.0 (Treble mod), allso I'll trid on Redwolf (treble).
How to fix that issue?? Because I want to root my phone.
Please help me guys. I want to flash treble rom with Magisk
MAH35H said:
Please help me guys. I want to flash treble rom with Magisk
Click to expand...
Click to collapse
oh ,this magisk is not support treble,because,it doesn't mount vendor.so you have to use modify mod magisk。you can serch in xda for more help
MAH35H said:
Hello guys i want to use Crdroid official 4.2 Treble build on my Redmi 3S with Magisk - 16.4 [treble flashable zip. But when flash Magisk 16.4, I was found Error 1 in my Twrp Recovery.
Using Rom : Crdroid official 4.2
Recovery : TWRP 3.2.1.0 (Treble mod), allso I'll trid on Redwolf (treble).
How to fix that issue?? Because I want to root my phone.
Click to expand...
Click to collapse
reflash u boot.img from u rom
then instal again magisk treble
if error. try to download again
maybe ur package zip is eror
Can anybody paste a downloadable link for magisk treble. I am facing the same problem. Please help!!!!
That same problem. I'm trying to flash clean boot.img over and over and no solution
Magisk 16 treble beta
Skys源儿 said:
oh ,this magisk is not support treble,because,it doesn't mount vendor.so you have to use modify mod magisk。you can serch in xda for more help
Click to expand...
Click to collapse
Magisk 16 treble beta is working fine and flashable ..
Install latest TWRP r2.
Hello, I got error: 255 when I tried to flash Magisk 16.4 with TWRP r2 for treble
any ideas ?
aryancol31 said:
Can anybody paste a downloadable link for magisk treble. I am facing the same problem. Please help!!!!
Click to expand...
Click to collapse
http://downloadmirror.co/Wso/Magisk-v16.4.zip
The error occurs because twrp is unable to mount vendor
Use twrp treble mod and
Magisk cust.zip
it worked for me
pavanp1 said:
The error occurs because twrp is unable to mount vendor
Use twrp treble mod and
Magisk cust.zip
it worked for me
Click to expand...
Click to collapse
how i can download twrp treble mod and Magisk cust.zip,my drive is redmi 3s
Sent from my land using XDA Labs
I haven't tested this project, but it seems to work with our treble ROMs.
https://gist.github.com/Jerry981028/b6a7fdfcf1823325c2f94f83677fa554
I am too facing issue with magisk. The phone does not boot after I flash it through twrp (treble supported recovery) and when i many tries to boot it gets soft bricked.
It has been reported many times...
Treble recovery is mandatory, if you have not already install it, pick the R2 version here :
https://sourceforge.net/projects/team-reloaded/files/land/TWRP/Treble/
You can find a working magisk 16.4 here :
https://forum.xda-developers.com/showpost.php?p=77062410&postcount=1322
Magisk issue is due to corrupt file.
Magisk issue is due to corrupt file. First be sure to have a treble compatible recovery and to enable treble if needed.
you can find a working magisk here : https://forum.xda-developers.com/sho...postcount=1322
Flash twrp treble recoveryagain, you must have flashed wrong recovery....
Same happened with me...
Flashed twrp again then flash magisk
Hello. I have LineageOS installed on my SM-G935F. I used to be rooted with magisk 16.0. v17 came out today, I tried to flash it, and got a bootloop. After various installations, uninstallations, and general trauma, I got Magisk 17.1 installed. However, as soon as I try and flash any modules, it says that data/Magisk isn't setup properly, and tells me to install Magisk v14.0+. Any ideas? Thanks in advance.
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
I'll try right away.
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thank you bro, I followed same steps however, I got a bootloop ;(
MaZeNsMz said:
Thank you bro, I followed same steps however, I got a bootloop ;(
Click to expand...
Click to collapse
I can't say what else would help sorry, those are the exact steps I followed and they worked.
Perhaps you could post in the Magisk part of the forums with some info about your device and see if someone could help.
MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
This is a magisk issue and shouldn't be posted here
Sent from my LG-H910 using XDA Labs
I had the same problem till I went to twrp recovery and flashed the zip that magisk downloaded and it works great. Only problem left on the side is trying to get Xposed to work again through the new magisk on H918 Super Rom, it's not working ATM but I think it's fixable somehow I guess. Magisk is effecting all phones, not just V20 btw.
Check out the video about the API and safetynet by the YouTuber HighOnAndroid. That video let's u know what's up with magisk the day before new magisk update came.
Is it possible that someone backup and share with me boot partition, and from my side I recover it ?!
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
I was able to directly install Magisk 17.1 from Magisk itself without issues.
SebTech33 said:
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
Click to expand...
Click to collapse
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
KawaiiNek0 said:
I was able to directly install Magisk 17.1 from Magisk itself without issues.
Click to expand...
Click to collapse
Very locky,
I did the same here by I end up with a nice boot loop
MaZeNsMz said:
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
Click to expand...
Click to collapse
Have you tried another kernel?
Anyone could test sixaxis compatibility checker?
(free on store)
Only on h990ds. 910 and other never were affected by this problem with previous magisk.
Dont know if v17 solved this problem.
Thanks
SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
I'll try today, do you recommend any kernel?
SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
Tried D.O.T.S and failed, bootloop
I am thinking if someone can backup the boot and share it with us. So we can recover it
Regards..
Has anyone found a way to make 17.1 work on the H990DS? It took me several flashes to get it to boot but after a couple restarts it started bootlooping again so I had to downgrade to 16 and 16 works just fine
Just stay on v16 until they can work the bugs out with v17 -- you aren't gaining anything by going to v17.
-- Brian
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thanks, that did the trick for me on lg h910r
MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
Note 26.10.2018 :
I upgraded to Oreo V8.0 from here and everything is fine now
Guys,
Anyone successful so far in setting up Magisk 17.1 on stock B35 A2017U + TWRP 3.2.1.0?
I tried following ways but everytime I flash the Magisk 17.1 using TWRP, it boot loops to recovery mode. I tried clearing Dalvik + cache everytime but in vain.
1. Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop.
2. Flash Super SU, Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop
I cannot use Super SU, blanket root due to bank & workplace apps security restrictions.
Any help/guidance will be is appreciated.
Cheers
Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.
marcdw said:
Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.
Click to expand...
Click to collapse
Thanks.
Thinking of trying with v16.7 first. If that works then great.
mandrax.prime said:
Thanks.
Thinking of trying with v16.7 first. If that works then great.
Click to expand...
Click to collapse
it does. i'm staying on 16.7
It would be nice to always have a working version of Magisk as Google updates their Safety Net. We have to update as they update.
I ran into problems today with Magisk 18.1 on the latest official LineageOS 15.1, nothing I did was able to get magisk to work (no icon, no error messages).
Has anyone else tried?
Magisk should work fine on LOS, I use it (Magisk) when I have to (i.e. when there is a particular use for it, like converting a systemless mod to a system-installed mod).
On B35, no go, phone will bootloop. Magisk should work fine on stock ROMs up to B15 N, maybe also with the B25 and B32 OTAs too. I'm not a ZTE stock ROM fan, I dont spend alot of time rooting stock, but from the few tests I did,those were my results.
If you have an exFAT SD card, installing Magisk on stock ROM may make your SD falsely show up as corrupt, only solution is to use the inferior/antiquated FAT32 filesystem.
Maybe one day I'll write my own open source root solution, just to show the Android community that Magisk isnt the only game in town for rooting modern ROMs on modern devices. I dont need to hide from SafetyNet, I dont need stupid systemless mods, I just need root that work reliably. I know this will fall on deaf ears, but Magisk is more trouble than it's worth, I'd recommend staying unrooted instead of using it. @topjohnwu is a genius and means well, I'm sure, but in the real world Magisk just isnt reliable enough.
I tried Magisk 17.3, 18.0, and 18.1 on Axon 7 B19 and B35- bootloop on every try
Hi All, I was on 9.0.14 and now I installed the latest OOS 9.0.16 through TWRP. All went well except i flashed magisk root.
I flashed the latest magisk 19.3 and 19.1 and all got me stuck on oneplus loading screen the red circle and white circle turning infinitely.
Then i tried magisk 18.1, everything loaded fine but magisk seems to be causing errors and not rooted. as i tried to grant nova launcher root, the app freezed and got stuck and force closed.
Also other apps that requires root are not able to request root.
any help would be appreciated.
Thanks!
What update file did you use? Full?
Did you wipe cache/dalvik?
Did you reapply twrp, then magisk?
At least that's what I did and it worked (and still does).
What twrp version?
OOs 9.016 + Magisk 19.3 (+ xXx 7.7 + Omega Kernel) working here for 2 weeks without any problems.
My suggestion would be to reboot in recovery (TWRP), reflash full OOs.zip, flash TWRP.zip, reboot in recovery (TWRP), repeat all this once more then flash Magisk 19.3 Zip and reboot system.
Shady282 said:
Hi All, I was on 9.0.14 and now I installed the latest OOS 9.0.16 through TWRP. All went well except i flashed magisk root.
I flashed the latest magisk 19.3 and 19.1 and all got me stuck on oneplus loading screen the red circle and white circle turning infinitely.
Then i tried magisk 18.1, everything loaded fine but magisk seems to be causing errors and not rooted. as i tried to grant nova launcher root, the app freezed and got stuck and force closed.
Also other apps that requires root are not able to request root.
any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Use magisk uninstaller in twrp. Then flash magisk 19.4 canary.
elchmartin said:
What update file did you use? Full?
Did you wipe cache/dalvik?
Did you reapply twrp, then magisk?
At least that's what I did and it worked (and still does).
What twrp version?
Click to expand...
Click to collapse
yes i always follow these steps, 3.2.3 twrp
MoHed said:
OOs 9.016 + Magisk 19.3 (+ xXx 7.7 + Omega Kernel) working here for 2 weeks without any problems.
My suggestion would be to reboot in recovery (TWRP), reflash full OOs.zip, flash TWRP.zip, reboot in recovery (TWRP), repeat all this once more then flash Magisk 19.3 Zip and reboot system.
Click to expand...
Click to collapse
I did as you suggested and had the same issue stuck at oneplus circles. I then tried to flash 18.1 it made me boot back into the system but root not working just magisk manager with just 2 options, in the menu side, settings magisk and settings.
Then I would try to start from scratch.
Means wipe everything, flash full OOS and then magisk.
@Shady282
Have you got it fixed? I am in the same situation and its frustrating that I am still unable to get root.
Tried flash magisk 19.4 canary no success. Still stuck in bootloop.
elchmartin said:
What update file did you use? Full?
Did you wipe cache/dalvik?
Did you reapply twrp, then magisk?
At least that's what I did and it worked (and still does).
What twrp version?
Click to expand...
Click to collapse
What twrp version are you using and could you please outline how you updated OOS 9.0.16 so i can follow the same path.
a4abbas said:
What twrp version are you using and could you please outline how you updated OOS 9.0.16 so i can follow the same path.
Click to expand...
Click to collapse
Hmm sorry, do 't remember.
I guess it was the latest Twrp at that time, I switched to op7 non-root for a while now...
the 6t was derooted and given to my s.o.
Shady282 said:
Hi All, I was on 9.0.14 and now I installed the latest OOS 9.0.16 through TWRP. All went well except i flashed magisk root.
I flashed the latest magisk 19.3 and 19.1 and all got me stuck on oneplus loading screen the red circle and white circle turning infinitely.
Then i tried magisk 18.1, everything loaded fine but magisk seems to be causing errors and not rooted. as i tried to grant nova launcher root, the app freezed and got stuck and force closed.
Also other apps that requires root are not able to request root.
any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Have you found any solutions to it yet? Please advice