I don't have, only ADB FASTBOOT...
I have DUMPed android_boot (mmcblk0p3) and i have obtained mmcblk0p3.img.
If i extract it, i see there is a ZIMAGE and not an IMAGE (and more files).
To get Titanium running? Nothing. Titanium was probably the first app I installed after rooting. The only thing that may help figure out what's happening is a logcatI installed "The SELinux Switch" and changed to Permissive.
MyBackupPro now is able to restore backups, but Titanium Backup still hangs on restore.
I tried all the TiBk options for App processing mode:
Auto Direct - hangs with spinning circle forever
Interactive - first displays "There Was A Problem Parsing The Package”, then hangs with spinning circle forever
What else should I look at? Are there some specific Magisk Modules that are needed for TiBk?
What else have you done other than install Magisk, and install Titanium?
I installed "The SELinux Switch" and changed to Permissive.
MyBackupPro now is able to restore backups, but Titanium Backup still hangs on restore.
I tried all the TiBk options for App processing mode:
- Auto Direct - hangs with spinning circle forever
- Auto Indirect - hangs with spinning circle forever
- Interactive - first displays "There Was A Problem Parsing The Package”, then hangs with spinning circle forever
What else should I look at? Are there some specific Magisk Modules that are needed for TiBk?
What else have you done other than install Magisk, and install Titanium?
• Fixed scheduled jobs getting killed on Android 8.0+ if scenario calculations took >5 seconds.
• Minor improvements.
• Updated translations.
@martyfender Starting from mmcblk0p3.img (size 30 Mb) I have obtained through Magisk app this file: patched_boot.img (size 10 Mb).
But now I have not able to install this patched_boot.img through Magisk app.... why?
---------- Post added at 16:17 ---------- Previous post was at 16:17 ----------
[/COLOR @martyfender Starting from mmcblk0p3.img (size 30 Mb) I have obtained through Magisk app this file: patched_boot.img (size 10 Mb).
But now I have not able to install this patched_boot.img through Magisk app.... why?
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
fastboot boot twrp.img
I have this situation...You have copy it to your pc and flash it with fastboot with the tablet in bootloader mode.
I usually copy it to the adb/fastboot folder on the pc. I then shift, right click in an empty space in that folder and choose: open a command prompt here. This is assuming you are on Windows.
If, like me, you instead boot to Linux most of the time, you have to use sudo before all of the fastboot commands listed below, unless you are already running as root.
Hit the enter key.Code:fastboot devices
When you enter the above command you should see your fastboot serial number listed if the device is connected.
Hit the enter key. You should see info that the flash was successful after this.Code:fastboot flash boot patched_boot.img
The above command reboots to Android.Code:fastboot reboot
adb reboot bootloader
You are booted to Android, not fastboot/bootloader mode in that screen shot. The adb devices command indicates that.
On my Nextbook Ares 8A,Intel x86, Android 6.0.1 tablets, from a complete shutdown I hold the volume down key and the power button to boot to fastboot/bootloader mode. The key combos can vary, though to do this.
On my devices, volume up, power button, boots me to the EFI bootmanager.
On my older, now dead, Ares 8 tablet, Intel x86 with Android 5, volume up, power button, booted me to recovery. On your device, how do you reboot to Windows?
I had done some research in the past on Chuwi devices. Is yours an Intel device, also?
I updated my above post also, with more info.
Thank you so much! Now I have root.
But I have two big problem:
1) system set automatically english language after reboot (i am italian, befor magisk root system was italian after reboot);
2) as from pictuers, busybox and init.d modules are not able to install.
How can I solve these problems?
I am afraid I haven't any experience with language. Can you go into Android settings, Language & Input to change it? Magisk Manager has settings also for language.
When you install a module, you have the option to save logs. If you post those logs, someone here may be able to help. I would also suggest posting the magisk.log in /cache/. Attach the logs to the post using the attach function or upload it to a file sharing site such as pastebin and post links. Please don't put the log in the body of a post as it makes it difficult to read, especially for mobile users.
I often find I have to hit the go advanced button option to see the attach button below. That is usually when I later edit my post, though.
1) I think you can change it from device setting (settings > language & input)Thank you so much! Now I have root.
But I have two big problem:
1) system set automatically english language after reboot (i am italian, befor magisk root system was italian after reboot);
2) as from pictuers, busybox and init.d modules are not able to install.
How can I solve these problems?
1) I think you can change it from device setting (settings > language & input)
2) I have no idea, but logs are needed & report it to magisk modules' dev as well will be better
For language before i had not this problem, only now after patched_boot.img flash.
Maybe unzip not works.... and busybox not works.... i am reading online....
I see this error in the magisk.log which I also recently had on one of the recent unofficial builds:
execve /sbin/.magisk/mirror/bin/busybox failed with 8: Exec format error
I've been told it may be that magisk's built in busybox may be detecting the wrong architecture, but I never got a clear answer. It was solved in later builds for me.
I am hesitant to recommend this, as some have had problems, but you might have better luck with beta v19 or the latest Canary build.
I would first try to get it to work with the current stable version.
Hi,
Anyone have issues on app TV Vodafone? Not working on Magisk v18.1. Detects that the smartphone has root (Hide option enabled + APP selected on Magisk).
Note: In the previous version (17.3) of Magisk it was enough to kill the application (Magisk) in recent applications for the application of TV Vodafone to work (do not detect root).
Another application that does not work is PS4 Remote Play, last version 2.7.0, only the v2.6.0 works.
Update:
I jumped from v18.1 (STABLE) to v19.0 (BETA) + Magisk Manager v7.1.0, and the TV Vodafone app its working again (need to close the MM in background). Only the PS4 Remote Play app, v2.8.0 continues to detect the root.
If upgrade the Magisk Manager to v7.1.1, can't pass the SafetyNet and the Magisk Hide not working properly (all apps detect root).
Just my feedback.
Hello,
I have magisk 19 on OP6T installed and every app was running fine.
Sometime in the recent past - may be past couple of days even Vodafone app is detecting the root and warning. Now TV app asks to undo system modifications and try again when I try to play GOT S8E01.. Anyone facing similar issue?
Your phone isn't rooted! The top section of your screenshot shows Magisk "Installed N/A".I can't access superuser and modules they are both lockedView attachment 6081641
Just open another with "version code: 27002" somewhere in first post, explain you tested both but issue is with Canary only, not Debug... Supply logs from broken build and wait for further instructions from Devs... Template requires the version code (or bot closes) + logs (or Devs will often close with comment like "no log no fix")... PWI have always have problems with magisk and bug reports think I have even failed with the debug version lol, although its closed I have added that the bug is not present with the debug version
Write your service.sh script with whatever commands you needHello, I'd like to write a module for magisk to transfer in userspace actions like this:
"echo "16 2048" > /sys/class/leds/aw210xx_led/single_led_br" to allow led control on Nothing Phone 1 to any app, would you suggest me an example module I can take inspiration from?
Not pushed yet according to my magisk app.Not sure if the fix has been pushed yet but looking at GitHub it's been sorted