Magisk General Support / Discussion

[J.Michael]

It's been a long, long time since I've paid attention to how rooting works on a technical level with modern devices.

I have an Android 10 head unit that I'm trying to get a working userspace root solution onto. The bootloader is locked, but I have root via both a wireless ADB shell as well as serial console. I have read/write access to /system. I don't have the ability to unlock the bootloader and flash a patched boot image. Is it possible to get Magisk working?

I'm going to guess "No": If you can't unlock the bootloader, and the bootloader being locked means what I think it means, then you can't possibly patch any of the system.

You could try naming the manufacturer -- somebody might have an idea of how to unlock the bootloader.

Why do you think you need root access?

 

[pndwal]

The combination of app and on device services (root)could be called Magisk The Gathering.

I always thought it best to try to understand / adapt to a Devs parlance / nomenclature if only to avoid reinventing the wheel, which could be considered a bad omen... If the Dev/creator wanted to reinvent the wheel however, I was happy to let 'em...

But let's throw out convention; I'm with you guys... Let's go with the "Magisk The Gathering" app!... @ipdev's a Dead head and The Gathering has been described as 'coming off like a cheap mix between "The Omen" and "The Dead Zone".... Gotta work for all of us no? PW

 

[Telperion]

I'm going to guess "No": If you can't unlock the bootloader, and the bootloader being locked means what I think it means, then you can't possibly patch any of the system.

You could try naming the manufacturer -- somebody might have an idea of how to unlock the bootloader.

Why do you think you need root access?

Respectfully, you either didn't read my whole comment or didn't read it clearly. I already have root access via wireless ADB and using a USB-UART bridge I can connect via Putty to a serial console and I have root. I can read, write, modify, etc, the system partition.

I'm wondering whether I can get Magisk running.

 

[m0han]

.... let's throw out convention.... a cheap mix between "The Omen" and "The Dead Zone"....

I'll take 'The Exorcist' for a change.

 

[J.Michael]

Respectfully, you either didn't read my whole comment or didn't read it clearly. I already have root access via wireless ADB and using a USB-UART bridge I can connect via Putty to a serial console and I have root. I can read, write, modify, etc, the system partition.

I'm wondering whether I can get Magisk running.

The system partition is not the one that needs to be modified to install Magisk. In fact, Magisk's claim to fame is the virtual modification of the system filesystem -- after Magisk has been installed.

You still have not identified your device.

Magisk used to be installed in the boot partition. Sometimes in the recovery partition. Recently new partitions have been invented and one of them might be where Magisk needs to be installed.

If you have no fear of losing your data, try installing Magisk manager app apk and using it to patch a copy of your boot image. Then try to overwrite your boot partition. See if you can boot.

Do you have any idea whether you will still have ADB root access if you are unable to boot Android?

 

[Telperion]

Roco K706.

I've already tried using dd to write a patched boot image. UBoot fails when it kicks off the partition verification process and the device doesn't boot any further, so that isn't a viable option.

 

[meric57]

Hello J.Michael, you are talking about firmware and security updates, I redid the modification with magisk as explained by Johnwu with adb pull and odin.
I hid the magisk app, no worries, I'm going to restore it to see, restoration ok.
The problem comes when I install an application or an update see a module on restarting the device I open magisk is I see application still install my magisk and zygisk not available, I would like to know if I can recover more quickly magisk no available either by flash or adb see other recovery mode.

I haven't yet tested uninstalling the magisk app and restarting, I'm waiting for the new smartphone to experiment with the S10 afterwards.

 

[meric57]

Like I said I have been using Manger apps way too long to not refer to them as the Manager.

Instructions

You can install/update phh's SuperUser in Magisk Manager's Download section​

If you have no root in the first place, please flash the zip in the attachment through custom recovery​

A root solution is part of a proper Magisk installation.​

After phh's SuperUser is installed, please install the SuperUser manager Application through the Play Store​

phh's SuperUser Manager​

Guess I am turning into the "Old Man".
Next I will be yelling at kids to keep of my lawn.

Cheers.

Hello ipdev, you are talking about an application like root checker when I open to see phh's SuperUser I come across page not found.
As explained above hidden magisk app no problem or restored, just losing magisk after restarting my S10.
I will restart it after restoring the magisk app I see not available see magisk capture not the magisk app.

a problem or conflict

 

[pndwal]

Roco K706.

I've already tried using dd to write a patched boot image. UBoot fails when it kicks off the partition verification process and the device doesn't boot any further, so that isn't a viable option.

Looks like others tried, failed, bricked but got new main board from seller:
https://forum.xda-developers.com/t/hizpo-3c-roco-k706-root-and-general-help.4376445/

PW

 

[NEOVerse!XChara]

magisk ruined my wifi (crDroid custom rom (last) | Redmi 8 - olive)

logs: (may be helpful)
02-07 15:26:31.123 E/AudioSystem-JNI(2886): AudioSystem::listAudioPorts error -19
02-07 15:26:31.123 W/AudioManager(2886): updateAudioPortCache: listAudioPorts failed
02-07 15:26:31.125 W/DPMJ (4352): |SERVICE| DPM received unexpected action: android.intent.action.ANY_DATA_STATE
02-07 15:26:31.126 I/Telephony(2142): isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
02-07 15:26:31.126 I/Telephony(2142): isRttSupported: false
02-07 15:26:31.126 I/Telephony(2142): alwaysAllowWhileRoaming: false
02-07 15:26:31.126 I/Telephony(2142): isRoaming: false
02-07 15:26:31.126 I/Telephony(2142): isOnWfc: false
02-07 15:26:31.134 I/CarrierServices(7608): [43] faf.handleMessage: RcsEngineImpl[DUAL_REG]:[d8be370e-3c66]>Handler: handleMessage processing message:[NOTIFY_UPTIME_IGNORE_STATE_CHANGED] with [non-null]:RcsEngineImpl reference
02-07 15:26:31.138 I/CarrierServices(7608): [44] egs.c: Connected state: [1], networkType: [MOBILE]
02-07 15:26:31.141 I/TetheringManager(1995): startTethering caller:com.android.systemui
02-07 15:26:31.147 I/CarrierServices(7608): [43] ewq.f: No RCS Configuration was found in Bugle for simID: redacted-pii:sim_id[chars:20,last3:918]
02-07 15:26:31.149 I/SystemUpdate(3994): [Execution,ExecutionManager] Action pending executed for 0.05 seconds.
02-07 15:26:31.159 I/Telephony(2142): isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
02-07 15:26:31.159 I/Telephony(2142): isRttSupported: false
02-07 15:26:31.159 I/Telephony(2142): alwaysAllowWhileRoaming: false
02-07 15:26:31.159 I/Telephony(2142): isRoaming: false
02-07 15:26:31.159 I/Telephony(2142): isOnWfc: false
02-07 15:26:31.161 I/WifiService(1263): startTetheredHotspot uid=1073

 

[pndwal]

magisk ruined my wifi (crDroid custom rom (last) | Redmi 8 - olive)

logs: (may be helpful)
02-07 15:26:31.123 E/AudioSystem-JNI(2886): AudioSystem::listAudioPorts error -19
02-07 15:26:31.123 W/AudioManager(2886): updateAudioPortCache: listAudioPorts failed
02-07 15:26:31.125 W/DPMJ (4352): |SERVICE| DPM received unexpected action: android.intent.action.ANY_DATA_STATE
02-07 15:26:31.126 I/Telephony(2142): isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
02-07 15:26:31.126 I/Telephony(2142): isRttSupported: false
02-07 15:26:31.126 I/Telephony(2142): alwaysAllowWhileRoaming: false
02-07 15:26:31.126 I/Telephony(2142): isRoaming: false
02-07 15:26:31.126 I/Telephony(2142): isOnWfc: false
02-07 15:26:31.134 I/CarrierServices(7608): [43] faf.handleMessage: RcsEngineImpl[DUAL_REG]:[d8be370e-3c66]>Handler: handleMessage processing message:[NOTIFY_UPTIME_IGNORE_STATE_CHANGED] with [non-null]:RcsEngineImpl reference
02-07 15:26:31.138 I/CarrierServices(7608): [44] egs.c: Connected state: [1], networkType: [MOBILE]
02-07 15:26:31.141 I/TetheringManager(1995): startTethering caller:com.android.systemui
02-07 15:26:31.147 I/CarrierServices(7608): [43] ewq.f: No RCS Configuration was found in Bugle for simID: redacted-pii:sim_id[chars:20,last3:918]
02-07 15:26:31.149 I/SystemUpdate(3994): [Execution,ExecutionManager] Action pending executed for 0.05 seconds.
02-07 15:26:31.159 I/Telephony(2142): isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
02-07 15:26:31.159 I/Telephony(2142): isRttSupported: false
02-07 15:26:31.159 I/Telephony(2142): alwaysAllowWhileRoaming: false
02-07 15:26:31.159 I/Telephony(2142): isRoaming: false
02-07 15:26:31.159 I/Telephony(2142): isOnWfc: false
02-07 15:26:31.161 I/WifiService(1263): startTetheredHotspot uid=1073

Are you patching boot.img or recovery.img?... How did you obtain boot image to patch?... PW

 

[NEOVerse!XChara]

Are you patching boot.img or recovery.img?... How did you obtain boot image to patch?... PW

i'm having no ramdisk, i'm having root via recovery.img and boot.img patched with root, i have the recovery.img from the unofficial forum TWRP in latest version, it is patched via magisk manager with turned on recovery mode opnion

 

[NEOVerse!XChara]

btw, while i'm opening whatsapp and trying to Make a call Whatsapp crashes...

 

[J.Michael]

Roco K706.

I've already tried using dd to write a patched boot image. UBoot fails when it kicks off the partition verification process and the device doesn't boot any further, so that isn't a viable option.

Were you able to recover?

Did Magisk say "Ramdisk: Yes"?

 

[NEOVerse!XChara]

Were you able to recover?

Did Magisk say "Ramdisk: Yes"?

me?

 

[NEOVerse!XChara]

anyway if you said it to me it said no

 

[martyfender]

magisk ruined my wifi (crDroid custom rom (last) | Redmi 8 - olive)

logs: (may be helpful)
02-07 15:26:31.123 E/AudioSystem-JNI(2886): AudioSystem::listAudioPorts error -19
02-07 15:26:31.123 W/AudioManager(2886): updateAudioPortCache: listAudioPorts failed
02-07 15:26:31.125 W/DPMJ (4352): |SERVICE| DPM received unexpected action: android.intent.action.ANY_DATA_STATE
02-07 15:26:31.126 I/Telephony(2142): isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
02-07 15:26:31.126 I/Telephony(2142): isRttSupported: false
02-07 15:26:31.126 I/Telephony(2142): alwaysAllowWhileRoaming: false
02-07 15:26:31.126 I/Telephony(2142): isRoaming: false
02-07 15:26:31.126 I/Telephony(2142): isOnWfc: false
02-07 15:26:31.134 I/CarrierServices(7608): [43] faf.handleMessage: RcsEngineImpl[DUAL_REG]:[d8be370e-3c66]>Handler: handleMessage processing message:[NOTIFY_UPTIME_IGNORE_STATE_CHANGED] with [non-null]:RcsEngineImpl reference
02-07 15:26:31.138 I/CarrierServices(7608): [44] egs.c: Connected state: [1], networkType: [MOBILE]
02-07 15:26:31.141 I/TetheringManager(1995): startTethering caller:com.android.systemui
02-07 15:26:31.147 I/CarrierServices(7608): [43] ewq.f: No RCS Configuration was found in Bugle for simID: redacted-pii:sim_id[chars:20,last3:918]
02-07 15:26:31.149 I/SystemUpdate(3994): [Execution,ExecutionManager] Action pending executed for 0.05 seconds.
02-07 15:26:31.159 I/Telephony(2142): isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
02-07 15:26:31.159 I/Telephony(2142): isRttSupported: false
02-07 15:26:31.159 I/Telephony(2142): alwaysAllowWhileRoaming: false
02-07 15:26:31.159 I/Telephony(2142): isRoaming: false
02-07 15:26:31.159 I/Telephony(2142): isOnWfc: false
02-07 15:26:31.161 I/WifiService(1263): startTetheredHotspot uid=1073

From my experience having to wifi or other devices may mean you didn't patch the boot image from the new rom. Did you by chance use an older boot.img from a previous rom. the rom and kernel versions must match.

 

[NEOVerse!XChara]

From my experience having to wifi or other devices may mean you didn't patch the boot image from the new rom. Did you by chance use an older boot.img from a previous rom. the rom and kernel versions must match.

i have just opened the .zip file of my ROM and putted it in magisk :|

 

[pndwal]

i'm having no ramdisk, i'm having root via recovery.img and boot.img patched with root, i have the recovery.img from the unofficial forum TWRP in latest version, it is patched via magisk manager with turned on recovery mode opnion

Bit confusing what you did... You extract and patch one boot image only; either boot.img (WITHOUT selecting Recovery mode) or recovery.img with Recovery mode set, NOT both! ... To access rooted system in recovery mode you will always need to boot via recovery with recovery key combo but release all buttons at splash screen to bypass recovery and boot to system with root...

Nb. Recovery mode means Magisk in recovery ramdisk... It has nothing to do with flashing via custom recovery (TWRP etc), and can't be flashed that way in any case...

In your case you can simply ignore Ramdisk = No! This is because Xiaomi bootloaders are (inexplicably) compatible with ramdisk in boot partition despite the OEM not installing one in A-Only legacy SAR devices, and Magisk always installs basic ramdisk where OEM Randisk is missing... (Magisk continues to display Ramdisk = No to indicate No OEM Ramdisk in boot.)

This means you extract and patch your boot.img (Ensure Recovery mode is NOT selected) and flash the resulting image to boot partition.

To fix you device, simply fastboot flash both unpatched boot.img and recovery.img then check device boots/operates normally again.

Next, ensure you have ROM package corresponding exactly to current running OS version and extract boot.img to patch/flash as above... Alternatively, you can install TWRP and make a backup of boot partition, obtain that from Backups and use this image. You may not even need to rename .win extension as .img, but can if you wish...

Please read John's Installation Instruction page carefully also because all necessary information is actually treated there...

Hope this helps... Please report results. PW

 

[pndwal]

anyway if you said it to me it said no

He was talking to the Roco user... PW