Just thought to let you all know.
I just installed a Nexus 4 with 5.1.1 and installed Magisk v16 along with Manager v5.8.3. It offered to update to 5.9.0 which I did. All ok, it then said Magisk is not installed while current version has bumped up to v17. Cool.
Well that was it, manager hanged permanently and I couldn't even control the device with ADB, reboot shell, nothing worked.
Rebooted manually, hanged the same, could use adb shell, but impossible to do anything.
Only solution: wipe/reinstall. Maybe installing v17 manually would have helped, but I didn't bother.
To all, be careful updating to 5.9.0.
Related
Using a Gionee CTRL V5, which has just been updated to Android 4.4.2. Trying any version after 2.5.1, I can't get Xposed to get installed on this phone. The installer says the files of the correct version are, indeed, installed, but not active, even after rebooting several times. Since this phone does not have any custom recovery, I can't install it via recovery (using stock recovery, the phone says the .zip is not correctly signed or something).
Xposed 2.5.1 installs flawlessly on the other hand, but when accessing the modules page, or anything else on the system for that matter, everything crashes. (Even the Android uninstaller.) What's happening?
I did root it using "KingRoot", and I can't manage to install SuperSU. Is that somehow problematic?
Since updating to Lollipop, my old method of root for this device no longer works, I flashed it in TWRP before, but that stopped working in 5.02, this time I read the only way to root would be to use CR autoroot, it worked but the SU app askes for me to update the binaries every time I launch the app, I've updated selecting normal, that was successful and rebooted, but the update binary pop-up still appears, I then selected to update using TWRP, that launched into TWRP upon reboot, the installation was a success but the pop up still hasn't gone.
Also for the record, I've unroofed and re-rooted, the problem still occurs, I've tried switching SU app to KingUser, that didn't work, I can still perform operations that require root because I'm rooted, but this pop-up will not cease, I've never used SuperSU before, my SU manager has always been KingUser (com.kingroot.KingUser)
Thanks.
My device is BLU Dash X2 ( D110L ) running android 6.0 with Kernel Version 3.18.19.
It's an MTK phone ( MT6580 ).
I managed to port and flash TWRP custom recovery by myself and it's working find. So I decided to flash SuperSU.zip with it. Everything seem to be working perfectly but after the flashing finished and I tried to open SuperSU app a message pop up with text "There is no SU binary Installed, and SuperSU cannot install it. This is a problem. If you just upgraded to android 5.0 you need to manually re-root - consult the relevant forums for your device!".
Please help me find a solution. I tried many version of SuperSU.zip already but the same message still appear. I also tried remove SuperSU app first before re-flash SuperSU.zip. I even tried to perform a clean stock rom flash before flashing latest SuperSU.zip and it's still the same.
I have the same phone, also managed to port TWRP, working fine after edit fstab, but no way I can root this device.
Tried with phh s SuperUser instead supersu, but no avail.
My biggest regret was buy this fone, it works fine but seems impossible to root.
Sorry for late update, you can root this device with magisk, successfully done with magisk v18.00
Super su
Sent from my Samsung Galaxy Note 8 using XDA Labs
I opened my phone today and found that there was an update to magisk, so I downloaded it and let it flash. Now upon turning my phone on, it passes the "your device is now booting screen" and then reboots. After a few times I end up in eRecovery.
The boot loader is unlocked, I was rooted and had systemless xposed installed (the one that works as a magisk module), and was running the Bluewei 5.0 ROM.
I am still able to access TWRP, but I do not have access to a computer. I still have the install package for Bluewei 5.0 on the SD, so I was thinking maybe I could wipe the phone and install that?
I ran a magisk uninstall package but that failed, and I tried installing magisk 14.2 using a zip that was already on the SD. So far nothing is working.
Help? I don't want to lose this phone (parents will kill me)
xMrTROLLIPOPx said:
I opened my phone today and found that there was an update to magisk, so I downloaded it and let it flash. Now upon turning my phone on, it passes the "your device is now booting screen" and then reboots. After a few times I end up in eRecovery.
The boot loader is unlocked, I was rooted and had systemless xposed installed (the one that works as a magisk module), and was running the MagicRainbow v2 ROM.
I am still able to access TWRP, but I do not have access to a computer. I still have the install package for MagicRainbow v2 on the SD, so I was thinking maybe I could wipe the phone and install that?
I ran a magisk uninstall package but that failed, and I tried installing magisk 14.2 using a zip that was already on the SD. So far nothing is working.
Help? I don't want to lose this phone (parents will kill me)
Click to expand...
Click to collapse
Solution was published two days ago in MagicRainbow but v3 thread
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
See from there what you can do. But aim to upgrade to MR v3, it's really again an excellent ROM. Probably you could do a clean installation of v3 instead of trying to repair v2
zgfg said:
Solution was published two days ago in MagicRainbow but v3 thread
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
See from there what you can do. But aim to upgrade to MR v3, it's really again an excellent ROM. Probably you could do a clean installation of v3 instead of trying to repair v2
Click to expand...
Click to collapse
I just realised I was actually on Bluewei, not MagicRainbow. Does this still apply?
Hi,
I need some help
Today I successfully installed the newest stable Xiaomi.eu-ROM on my finally unlocked Mi8, using TWRP from here: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-1110-t3869729
TWRP is working flawlessly, but I didn't succeed in making root with Magisk to work.
What I did:
- I booted into TWRP
- formatted data
- rebooted back into TWRP
- flashed DM-verity disabler from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- flashed Magisk v18.0 right after from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- wiped dalvik cache
- rebooted the phone
But everytime I did it, I didn't had root access (checked with Root Checker app) when the phone finally booted up to MIUI 10.1.2.0 (PEACNFI).
I even didn't have Magisk Manager showed up.
Can you tell me what I did wrong? I don't have a clue
Thanks a lot and best regards
Mischa
what does magisk manager tell you about your magisk installation status?
Strange thing...
After I rebooted the phone, there was no Magisk Manager nor the phone was rooted, what I checked with Root Checker app.
Then I used it a couple minutes before it became really laggy. My chosen theme disappeared back to stock theme, scrolling was nearly impossible and the screen went black.
I was not able to wake up the display again, so I held down the power button a couple seconds until the phone rebooted.
Now I saw that the Magisk Manager was installed, without me doing anything else than rebooting after the phone got unusable.
Weird, right? I read that there might be lags after installing Magisk, but that it's going to be like that was surprising.
Anyway, I have root now, TWRP works, Magisk v18 is installed. Now I only have to find some must-have-modules, e.g. like stereo-mod.
BTW, could it be that Netflix isn't working on rooted phones? I always get error 14 saying that the Netflix-service is not reachable even though I have internet connection.
hey dude i know this isnt a guide
but i followed your kind of direction after spending the whole afternoon and few hours in the evening to figure how to root this phone and finally it worked (so far)
thanks a lot my man
and i didnt even format after flashing twrp i hope it didnt **** up my phone