can't install Magisk - G4 Q&A, Help & Troubleshooting

tried to replace SuperSU with Magisk via TWRP.
Magisk won't take by itself.
Removed SuperSU. Tried again. Still NG.
"adb reboot recovery" back to TWRP and flashed SuperSU. I have root back, though I don't see SuperSU in the app drawer.
The info to install Magisk leave a bit to be desired.
"install manually" what does that mean?
Remove root (SuperSU) seems to prevent one from installing Magisk, though I did "adb reboot recovery" to get the re-install of SuperSU done.
In the long run, I want to update our other H811 to 20x from 20q. Thats' what started me down this track.
Any input?

Did Magusk Zip Got Trough without any issues in TWRP?
Did you have the magisk App in drawer after flashing Magisk?
Magisk manager is sometimes an older version, so you have to go to magisk manager (app) open ist and click on upgrade or install upgrade.
sometimes my device needed 2installations. one in twrp an another in MAgisk app. but both were v16.0 zip.

no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.

metropical said:
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
Click to expand...
Click to collapse
You should Always search the TWRP errors you have, that gives you more info.
Error 1 means on your system partition is not enough space anymore, so delete or Freeze some bloatware/apps and it should go trough.
boot.IMG files are containt in KDZ (firmware files).
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.

uweork said:
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
Click to expand...
Click to collapse
went and posted in digeridoohan original thread.
https://forum.xda-developers.com/showpost.php?p=76980632&postcount=25580
all is well.. thanks very for the help. and I installed the Xposed module that works with TextAid and MM.
also your link won't doesn't seem to work. I've found that a I've had to use shortened links of late or they don't fire on XDA.

Guys I can't run Magisk on my LG G4 H815 with Nougat v29a. After removing Supersu and flashing magisk 17.1 with twrp, the phone doesn't boot normally. It reboots recovery when I click reboot system. It always reboot recovery. I don't know why.
Do you have any Idea?

Related

[Q] Find 7: "no su binary installed and supersu cannot install it"

Hi folks,
I've follow ParotZ's Recovery Installer process to root and am having SuperSu issues.
I install recovery (option 5), then reboot to recovery (option 0), system > reboot > swipe to install > and then once it loads I'm greeted with
"no su binary installed and supersu cannot install it"
I've put UPDATE-SuperSU-v2.16 on internal storage and tried earlier versions and flashed, with the same result.
The SuperSu app is installed. I attempted a manual update on the Play store, but the 'no su binary' message is still there.
I can't uninstall supersu, either with an uninstaller app or through Play (it does not show 'uninstall', just shows 'open')
It persisted after I factory reset and wiped (not through recovery).
Any help? Keen to get on Cyanogen.
My phone specs.
Model
Oppo x9076
ColorOS
v2.0.0i
Android version
4.4.2
Build number
FIND7WX_12_141017
Kernel
3.4.0-S3753
Baseband
Q_V1_P14
I've seen others with the question, but none with answers for the Find 7 :/
Cheers!!
solved
Hi folks,
I've solved the issue. I could not root using that method because I had updated the OS and there was some form of conflict that stuffed the SuperSu binary.
So I downgraded back to stock (the earlier ColorOS) and reapplied the root process.
For those with the same issue follow these steps http://theunlockr.com/2014/08/22/how-to-unroot-the-oppo-find-7-video/
Then reattempt the root.
Note that step 6. "Using the volume buttons to navigate and the power button to select the option you want, select Wipe Data and Cache." will erase the OS you just copied over, so do this prior to copying the OS or you'll just need to do it again.
When the OS loads and you come to the update SuperSu step, my Play store wouldn't load due to I think a delay in the accept terms of use popup. So I used the TWRP method and it worked fine.
Good luck.
Darren.

"superuser binary is out of date" but wont update

i just rooted my s6, and i DO have root access, but when i try to open superuser (that was installed along with the root) it says "superuser binary out of date" and asks how i want to update it. The only options it gives me is Cancel and Recovery. If i choose recovery it boots into recovery then does nothing. I found the updated version of superuser online and transeferred it to my phone and flashed it thorug TWRP. Still says it. I tried installing supersu and when i open it it says "su binary is occupied" so i used an uninstaller to uninstall superuser, and supersu still says binary is occupied. So i reinstalled superuser but now i dont know what else to do to get my superuser app to work? Any ideas? TIA
I don't know how comfortable you would feel about this, but a lot of us have moved on to using Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
There are two parts, Magisk itself and the Magisk Manager.
Recommended path is to return to Stock, install TWRP via Odin but don't reboot. Instead shut down, reboot directly to Recovery and flash Magisk. Usually on first boot you will get a prompt to install Magisk Manager, do that and you are set.
Before you do that, take some time to read about Magisk. It is similiar to SusperSu, but allows you to conceal that you are rooted. (A feature that you enable within the manager.) I find it a great improvement.
ohhhh. i get it now. the method i used to root was with magisk. it prompted me to install it when it booted up so i did but didnt really go look at the magisk manager. i didnt realize that was what handles the su. thats why it says its occupied

Recovering from a bad magisk module on 7.2.2

so I've installed magisk on 7.2.2 by creating a patched boot.img and flashing via fastboot.
All nice, until I installed a module that ended in bootloop.
I managed to recover by flashing the original boot.img, but I end up with no magisk/no root, and no means to uninstall the module, So if i reflash magisk, I end up with the bootloop.
Is there a new recovery compatible with 7.2.2 or anyone knows a way out of this?
There is no twrp for 7.2.2 yet. You can either delete /data/adb/magisk.img and install all your modules again
or
copy it to your phone while in recovery, rename the original (assuming you have magisk on your phone), copy it to the same location as above, flash the attachment to mount it, remove module from /magisk/, reboot to recovery (don't reboot to system!), cut the file off of the phone and rename the original back to magisk.img, you can then boot your phone.
thecoolkid said:
There is no twrp for 7.2.2 yet. You can either delete /data/adb/magisk.img and install all your modules again
or
copy it to your phone while in recovery, rename the original (assuming you have magisk on your phone), copy it to the same location as above, flash the attachment to mount it, remove module from /magisk/, reboot to recovery (don't reboot to system!), cut the file off of the phone and rename the original back to magisk.img, you can then boot your phone.
Click to expand...
Click to collapse
problem is I can't flash anything as I don't have a custom recovery.
do you mean flash the zip you posted via stock recovery? will it flash? what does it do? where does it go?
thanks
xd4d3v said:
problem is I can't flash anything as I don't have a custom recovery.
do you mean flash the zip you posted via stock recovery? will it flash? what does it do? where does it go?
thanks
Click to expand...
Click to collapse
I meant flash it on your phone, the second solution involves a second device as a surrogate. The zip just mounts magisk image to /magisk/ so you can browse it manually.
thecoolkid said:
I meant flash it on your phone, the second solution involves a second device as a surrogate. The zip just mounts magisk image to /magisk/ so you can browse it manually.
Click to expand...
Click to collapse
Sorry mate, not following you, why do I need a phone?
I'd be happy deleting magisk.img on the shield and loosing magisk config, but I can't access it without root or recovery.
xd4d3v said:
Sorry mate, not following you, why do I need a phone?
I'd be happy deleting magisk.img on the shield and loosing magisk config, but I can't access it without root or recovery.
Click to expand...
Click to collapse
Ok, I researched a little and the only thing that comes to mind, that isn't wiping the whole data position, is downgrading to 7.1 firmware and installing twrp. After you fix your issues you can update again.
yeah, good one, I was considering that as well, might try flashing just boot.img and blob from 7.1 and trying TWRP, then reflashing 7.2.
wish me luck
Heres an easier way, create a blank .disable_magisk file and place it in /data/cache
Then reboot, this will force magisk to start with "Magisk Core Only Mode" , which means magisk hide and modules will be disabled.
Then you can disable "magisk core only mode" when booted up, so modules and magiskhide is enabled again.
Then uninstall the module that is being the issue.
mLgz0rn said:
Heres an easier way, create a blank .disable_magisk file and place it in /data/cache
Then reboot, this will force magisk to start with "Magisk Core Only Mode" , which means magisk hide and modules will be disabled.
Then you can disable "magisk core only mode" when booted up, so modules and magiskhide is enabled again.
Then uninstall the module that is being the issue.
Click to expand...
Click to collapse
You need root or TWRP for that. I was thinking about it too, but he has no access to twrp in the new update and can't boot with root.
thecoolkid said:
You need root or TWRP for that. I was thinking about it too, but he has no access to twrp in the new update and can't boot with root.
Click to expand...
Click to collapse
You only need to use the developer boot without patching magisk to it, then through adb create a file there.
You can get root access through adb which allows you to create a file there
That's a brilliant idea. So the developer image allows root via adb?
xd4d3v said:
That's a brilliant idea. So the developer image allows root via adb?
Click to expand...
Click to collapse
Yep, hence why they call it "rooted" even though its not it dosnt have the su binaries by default, its more like unlocked compared to the ota builds.
You should be able to do the command "adb root" and then enter shell with root access.
I can't remember but you might need to do "adb disable-verity" and reboot before you can put stuff into the root partition "/system", "/data/cache" and so on.
Just remember when you patch the boot image with magisk again, you either first need to do "adb enable-verity" and then patch with "preserve avb 2.0/dm-verity" checked in magisk or keep dm-verity disabled then patch with "preserve avb 2.0/dm-verity" unchecked, else you gonna end up in a boot loop.

[SM-A520F][8.0] Problems installing Root with A5 2017

Today I've installed the stock firmware version of Android Oreo 8.0 (the December Update) with Odin.
After that I've installed the TWRP also with Odin, the 3.2.3 version.
Then I wanted to root the devide so I start with the installation of Magisk (because I need to hide the root form some apps like Netflix), but it keeps failing with the ERROR 1. I've searched in this forum but none of the solutions worked. One solution requires the boot.img of the rom, but I can only get a boot.img.lz4 from the AP md5 file which i have no idea how to use.
Then I tried to install SuperSU (v2.82 SR5 version). I followed a guide but once I finished the flash of RMM State Bypass and SuperSU I rebooted only to be locked out of my phone. A message informed me that the integrity of the phone could not be checked (or something like that) and so I had to re-flash the stock firmware and the recovery with Odin.
Am I missing something? Am I doing something wrong? And where can I find the boot.img from the stock firmare?
I hope somebody can help me because I spent a lot of hours looking for a solution without having a working result...
lolovato said:
Today I've installed the stock firmware version of Android Oreo 8.0 (the December Update) with Odin.
After that I've installed the TWRP also with Odin, the 3.2.3 version.
Then I wanted to root the devide so I start with the installation of Magisk (because I need to hide the root form some apps like Netflix), but it keeps failing with the ERROR 1. I've searched in this forum but none of the solutions worked. One solution requires the boot.img of the rom, but I can only get a boot.img.lz4 from the AP md5 file which i have no idea how to use.
Then I tried to install SuperSU (v2.82 SR5 version). I followed a guide but once I finished the flash of RMM State Bypass and SuperSU I rebooted only to be locked out of my phone. A message informed me that the integrity of the phone could not be checked (or something like that) and so I had to re-flash the stock firmware and the recovery with Odin.
Am I missing something? Am I doing something wrong? And where can I find the boot.img from the stock firmare?
I hope somebody can help me because I spent a lot of hours looking for a solution without having a working result...
Click to expand...
Click to collapse
Try again and redownload magisk.
Also, did you wipe data?
iloveoreos said:
Try again and redownload magisk.
Also, did you wipe data?
Click to expand...
Click to collapse
I tried re-downloading Magisk (the latest and the version before) but nothing changed.
Yes I wiped the data.
I've added that I'm working on a A5 2017 SM-A520F.
lolovato said:
I tried re-downloading Magisk (the latest and the version before) but nothing changed.
Yes I wiped the data.
I've added that I'm working on a A5 2017 SM-A520F.
Click to expand...
Click to collapse
Hmm, did you reinstall stock firmware on it and try again? Error 1 happens when the zip is corrupted. What version of TWRP are you using, 3.2.3-0?
Um, did you flash no-verity 6.0.zip? https://forum.xda-developers.com/sa...velopment/recovery-galaxy-a5-a7-2017-t3815931
iloveoreos said:
Hmm, did you reinstall stock firmware on it and try again? Error 1 happens when the zip is corrupted. What version of TWRP are you using, 3.2.3-0?
Um, did you flash no-verity 6.0.zip? https://forum.xda-developers.com/sa...velopment/recovery-galaxy-a5-a7-2017-t3815931
Click to expand...
Click to collapse
I'm using 3.2.3-1.
I've tried to reflash with Odin the whole stock firmware, then I flashed the TWRP recovery 3.2.3-1 (I redownloaded every file), I entered the recovery and I flashed the no-verity 6.0.zip, only to be once againt cut out from my phone with the same message as yesterday saying that the integrity of the phone could not be checked and that I need to restore the phone.
I really don't understand what is going wrong...
I think I've made it? I don't know what I did differently this time, I'll post the solution here if someone needs it:
0a. MAKE A BACKUP OF YOUR DATA!
0b. Put in your SD-Card the version of Magisk you want to install and the no-verity-opt-encrypt-x.x zip file.
1. Flash the stock firmware with Odin, when the PASS! message appears and the phone starts to reboot unplug the device and quickly re-enter in download mode.
2. Flash the TWRP recovery with Odin, when the PASS! message appears and the phone starts to reboot unplug che devide and quickly enter in recovery mode.
3. In recovery click Wipe and select Format Data. Then go back, click Install and select from the SD-Card the no-verity-opt-encrypt-x.x zip file.
4. Reboot your phone to system, configure the devide (account, ecc.).
5. Turn-off the phone and go in recovery, click Install and select from the SD-Card the Magisk zip.
6. Reboot your phone to system, install Magisk Manager and you're done!
TWRP and no-verity-opt-encrypt zip file: click.
Magisk zip and Magisk Manager: click.
lolovato said:
I think I've made it? I don't know what I did differently this time, I'll post the solution here if someone needs it:
0a. MAKE A BACKUP OF YOUR DATA!
0b. Put in your SD-Card the version of Magisk you want to install and the no-verity-opt-encrypt-x.x zip file.
1. Flash the stock firmware with Odin, when the PASS! message appears and the phone starts to reboot unplug the device and quickly re-enter in download mode.
2. Flash the TWRP recovery with Odin, when the PASS! message appears and the phone starts to reboot unplug che devide and quickly enter in recovery mode.
3. In recovery click Wipe and select Format Data. Then go back, click Install and select from the SD-Card the no-verity-opt-encrypt-x.x zip file.
4. Reboot your phone to system, configure the devide (account, ecc.).
5. Turn-off the phone and go in recovery, click Install and select from the SD-Card the Magisk zip.
6. Reboot your phone to system, install Magisk Manager and you're done!
TWRP and no-verity-opt-encrypt zip file: click.
Magisk zip and Magisk Manager: click.
Click to expand...
Click to collapse
That is how you are supposed to do it.

Question How to reflash OrangeFox due to missing Magisk addon?

I've been trying to reflash OrangeFox without success (ofoxginna2). I assume it's not reflashed because i had deleted the magisk addon folder while trying to solve the "missing magisk. quitting! " error when trying to install it (see orangefox thread post ) and after i "fastboot flash recovery2.img i get the same magisk manager error described here:
the install addon manager says "File Doesn't exist! Please reflash recovery using the installation zip"). If i then go to /sdcard and pick ofoxginna2.zip, i run into the same "magisk is missing error".
At this point, i'm trying to get back to the original issue (after first time flash) of the magisk manager install giving an error due to corrupt zip (somethng deeper about missing keys).
Should i try to:
1) fastboot flash the ofoxginna.zip (without touchscreen support) and then flash ofoxginna2,zip again?
2) blank flash the recovery ( haven't found the steps to do this)
3) flash the recovery from the stock rom (here again not sure how to do this).
thanks.
Wow, that's hard to follow.
If the recovery zip is giving you trouble, don't use it. Take ofoxginna2.img and boot it with fastboot. You can try flashing it as well, but it's really a waste of time bothering.
If your having trouble flashing the magisk recovery installer, don't use it either. Dump your boot image, patch it in Magisk Manager, and flash it in fastboot.
You seem to be getting caught up on little steps. Can you give me a better idea of where your at and what works and what doesn't? Your still trying to boot the nogapps build, and you just have no idea how to place that file, or what?
For your question on how to get back, boot recovery
Code:
fastboot boot ofoxginna2.img
Then format data, reflash lineage, and reboot.
If you wanted to get touch working through Magisk, you'd need an OTG cable and mouse to do it easily. You'd install Magisk Manager, patch that image I shared, and then flash it.
Code:
fastboot flash boot magisk_patched.img
Then you'd install the module I shared and reboot.
But if you don't have have an OTG cable, flash the boot image, Magisk is optional. Boot ofoxginna2, press the button on the bottom right, choose mount, and check the box for vendor. Then you pull up a root shell on your computer with "adb shell".
Code:
mount -o rw,remount /vendor
Then you can extract the module and push the firmware to the phone.
Code:
adb push chiptone-tianma-ICNL9911C-0288-0000-ginna.bin /vendor/firmware/
And reboot.
Please don't make any more threads. Ask questions or for help instead.

Categories

Resources