Related
Hi all.
I was wondering to install some Xposed modules, but after successful installation of Framework and successful install of wanted modules, i rebooted phone and nothing happened they just didn't worked. I tried multiple of them so it cant be in modules ...
Can you help me someone?
Mondop said:
Hi all.
I was wondering to install some Xposed modules, but after successful installation of Framework and successful install of wanted modules, i rebooted phone and nothing happened they just didn't worked. I tried multiple of them so it cant be in modules ...
Can you help me someone?
Click to expand...
Click to collapse
Have you marked them like enabled? like here:
http://prntscr.com/623xp4
and then just restart phone. This worked for me..
yop they were enabled for sure :/
Working fine for me.. Stock flash everythying and try again.
Has anyone had any luck getting Magisk installed and working on a custom rom yet? I tried it on the CM13 Rom but root would just turn back on within a second. link for Magisk install http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Thank you
Wait until Magisk V7 is released.
Its states under known issues "HTC One M9 (yes, this particular device): sepolicy issues, should be fixed in v7" .
If you have a twrp backup of a rom that has the last build in it go to the app store and download an apk backup app and backup the pokemon go.apk and reinstall it in a newer rom build and don't do the update. Older version is still working until they finish rolling out the update.
Just to give an update on this....
I used BadBoys rom and I went into SuperSU and did UNINSTALL UNROOT... Which is the first step you need to do for Magisk.... This allowed me to PASS the Safetynet TEST... I can reverse this in moments since I am S-OFF by reinstalling SuperSU and reflash the binary from TWRP
*****So I am under the impression that when Magisk v7 comes out and works for this phone. It "Should" work with BadBoys. Until then I am just reinstalling SuperSU when I need it
I've gotten magisk to boot up once with phh superuser. However as soon as I tried to flash the systemless xposed from twrp. I would get stuck in a boot loop. I was unable to get it to boot up anytime I flash magisk now. I am S on but I don't think that should do anything with the rom.
Magisk works great on my Nexus 7
tws101 said:
Just to give an update on this....
I used BadBoys rom and I went into SuperSU and did UNINSTALL UNROOT... Which is the first step you need to do for Magisk.... This allowed me to PASS the Safetynet TEST... I can reverse this in moments since I am S-OFF by reinstalling SuperSU and reflash the binary from TWRP
*****So I am under the impression that when Magisk v7 comes out and works for this phone. It "Should" work with BadBoys. Until then I am just reinstalling SuperSU when I need it
Click to expand...
Click to collapse
This is what Ive ended up doing. Thank you
Another update
http://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
As you can see above today we still only have Magisk v6 and not v7 which we need to work with this phone model.... I will update again as soon as I can test v7 which they are still working on.
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
bskov said:
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
Click to expand...
Click to collapse
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
Yeah, im going to back it all up once I get home and wipe it clean to flash DFE and flash the ROM on top.
Also, I flash Magisk Uninstaller, it told me it couldn't find a stock boot image (and then proceeded to generate one), and then once I restarted the phone I went to CPU-Z to check root access and it changed to "No", so something was taking effect.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
So, I tried decrypting, but I can't, because of something with Android Pie. Doesn't matter now, I wiped every storage partition clean and flashed the firmware twice, then flashed Magisk on top, now it's working. Thanks anyway!
That prompt not showing up and magisk manager not showing in app drawer is a common issue for me even though I've never installed MultiROM on my device. You can ignore both.
Here's what I do to resolve the issue:
1) Install Magisk Manager apk.
2) Go to settings, scroll down to "automatic response", click that, click either grant or deny, then click it again and this time set it as prompt.
That should show the superuser prompt.
So again I tried to install EdXposed on the Umidigi F1. I tried a newer Beta version but unfortunately it did not work. I got stuck on bootloop but when I got out of it the system was hanging, not to mention it shut down completely the cellphone function and deleted the camera app. So I guess it's a no go, unless someone has manged to make it work I would like to hear how they did it. I think our phone would improve a lot with Xposed and Gravity Box. considering how simple the Pie version it is running. BTW still running UMIDIGI _F1_V1.0_20190124
David C.
Hi Dave, don't understand your problem, maybe it's the ROM version or something with rooting went wrong. Anyway, here is the procedure which worked for me: Install ROM 20190316, unlock the phone, install TWRP, reboot and clear data an caches, install Magisk V19.3, now install Riru-Core from Magisk download menu, reboot, install Riru Sandhook, install EdXposed manager apk (download from Github), reboot, start EdXposed manager and install Gravitybox from EdXposed download menu. Don't forget to activate the plugin in "modules" and reboot. After that you have to re-install all your programs. Well the procedure took me at least 3 hours, but finaly it worked for me (see attached screenshots), your miles may vary...
AP756 said:
Hi Dave, don't understand your problem, maybe it's the ROM version or something with rooting went wrong. Anyway, here is the procedure which worked for me: Install ROM 20190316, unlock the phone, install TWRP, reboot and clear data an caches, install Magisk V19.3, now install Riru-Core from Magisk download menu, reboot, install Riru Sandhook, install EdXposed manager apk (download from Github), reboot, start EdXposed manager and install Gravitybox from EdXposed download menu. Don't forget to activate the plugin in "modules" and reboot. After that you have to re-install all your programs. Well the procedure took me at least 3 hours, but finaly it worked for me (see attached screenshots), your miles may vary...
Click to expand...
Click to collapse
Ok, I'll try it your way (although doesn't seem as different from what I've been doing) Here goes nothing....Thanks man!!
David C.
Did you get it to work as I'm getting installation failed every time I try
Dear all,
I have read quite few post about this issue. I have installed magisk and my phone has booted. After installing a magisk module it asked me to reboot. I did it. I ended up stucking in bootloop. I opened TWRP again and Installed a custom global rom (without factory reset) So it healed my phone. Root access has gone and my phone was working again with Al my settings and files. What can I do differently to get my Xiaomi rooted? Btw.... After flashing magisk zip, I also installed lazy flasher and I deleted cache.
Thank you very much in advance for any suggestions or solutions.
Which magisk modules? Compatible problem maybe...
Is that maybe ur fix
https://forum.xda-developers.com/mi-8/help/install-magisk-bootloop-t3824481
He solved it. Read the his first post to the end...
joke19 said:
Which magisk modules? Compatible problem maybe...
Is that maybe ur fix
https://forum.xda-developers.com/mi-8/help/install-magisk-bootloop-t3824481
He solved it. Read the his first post to the end...
Click to expand...
Click to collapse
Dear Joke 19,
First of all thank you for the answer. At the beginning I tried v17. After booting there was a message saying that I need to install at least v18. So I flashed v19. I booted my phone I opened magisk and it was running. But at the first reboot I stuck in boot loop.
Thanks,
Attila
Attilagubanyi said:
Dear Joke 19,
First of all thank you for the answer. At the beginning I tried v17. After booting there was a message saying that I need to install at least v18. So I flashed v19. I booted my phone I opened magisk and it was running. But at the first reboot I stuck in boot loop.
Thanks,
Attila
Click to expand...
Click to collapse
I have read through the whole post. I have seen this quote... ("And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!")
Unfortunately I have not found the solution to be able to use rot access, be able to install modules and do not stuck in bootloop...