Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

After Flash Patched boot.img Magisk not installed #5437

Closed
ASIMKHAN222 opened this issue Feb 11, 2022 · 34 comments
Closed

After Flash Patched boot.img Magisk not installed #5437

ASIMKHAN222 opened this issue Feb 11, 2022 · 34 comments
Labels
not enough info Not enough info to fix stale No response for a long time

Comments

@ASIMKHAN222
Copy link

ASIMKHAN222 commented Feb 11, 2022 •
edited
Loading

Device: vivo s1
Android version: 11
Magisk version name: magisk canary 25
Magisk version code: 24102

i patched boot.img with latest canary after flash boot.img via fastboot i reboot the device but magisk is not installed
my device have
MT6768 Chipset

Attaching some files;
Magisk install log
magisk_install_log_2022-02-10T00_03_57[2].log
Magisk log
magisk_log_2022-02-11T17_06_07[1].log

stock boot.img
boot[1].zip
@canyie
Copy link
Collaborator

canyie commented Feb 11, 2022

Seems Magisk is working but does not mount /system

[init.svc.UJOzq6Pi]: [stopped]
[init.svc.Yi86JkCAtCpN]: [stopped]
[init.svc.xP3Bw7bdrFX]: [stopped]
3647 3645 0:21 / /dev/uqVV rw,relatime master:4 - tmpfs tmpfs rw,seclabel,size=1911908k,nr_inodes=477977,mode=755
3648 3647 0:38 / /dev/uqVV/.magisk/pts rw,nosuid,noexec,relatime master:11 - devpts devpts rw,seclabel,mode=600,ptmxmode=000
3649 3647 259:6 / /dev/uqVV/.magisk/mirror/vendor ro,relatime master:12 - ext4 /dev/uqVV/.magisk/block/vendor ro,seclabel
3650 3647 259:9 / /dev/uqVV/.magisk/mirror/data rw,relatime master:13 - ext4 /dev/uqVV/.magisk/block/data rw,seclabel,discard,noauto_da_alloc,inlinecrypt,resuid=10010,resgid=1065,errors=panic,data=ordered
3651 3647 259:7 / /dev/uqVV/.magisk/mirror/system_root ro,relatime master:40 - ext4 /dev/uqVV/.magisk/block/system_root ro,seclabel
3652 3647 259:9 /adb/modules /dev/uqVV/.magisk/modules rw,relatime master:13 - ext4 /dev/uqVV/.magisk/block/data rw,seclabel,discard,noauto_da_alloc,inlinecrypt,resuid=10010,resgid=1065,errors=panic,data=ordered

@yujincheng08
Copy link
Collaborator

Need a full bootlog

@canyie
Copy link
Collaborator

canyie commented Feb 11, 2022

Oh, that's a vivo device. I believe this is a duplicate of #5148.

@ASIMKHAN222
Copy link
Author

Need a full bootlog

logcat.txt

@yujincheng08
Copy link
Collaborator

Need a full bootlog

logcat.txt

Too late. We need a logcat since phone boots.

@ASIMKHAN222
Copy link
Author

ASIMKHAN222 commented Feb 12, 2022 •
edited
Loading

Seems Magisk is working but does not mount> ```

Seems Magisk is working but does not mount /system

[init.svc.UJOzq6Pi]: [stopped]
[init.svc.Yi86JkCAtCpN]: [stopped]
[init.svc.xP3Bw7bdrFX]: [stopped]
3647 3645 0:21 / /dev/uqVV rw,relatime master:4 - tmpfs tmpfs rw,seclabel,size=1911908k,nr_inodes=477977,mode=755
3648 3647 0:38 / /dev/uqVV/.magisk/pts rw,nosuid,noexec,relatime master:11 - devpts devpts rw,seclabel,mode=600,ptmxmode=000
3649 3647 259:6 / /dev/uqVV/.magisk/mirror/vendor ro,relatime master:12 - ext4 /dev/uqVV/.magisk/block/vendor ro,seclabel
3650 3647 259:9 / /dev/uqVV/.magisk/mirror/data rw,relatime master:13 - ext4 /dev/uqVV/.magisk/block/data rw,seclabel,discard,noauto_da_alloc,inlinecrypt,resuid=10010,resgid=1065,errors=panic,data=ordered
3651 3647 259:7 / /dev/uqVV/.magisk/mirror/system_root ro,relatime master:40 - ext4 /dev/uqVV/.magisk/block/system_root ro,seclabel
3652 3647 259:9 /adb/modules /dev/uqVV/.magisk/modules rw,relatime master:13 - ext4 /dev/uqVV/.magisk/block/data rw,seclabel,discard,noauto_da_alloc,inlinecrypt,resuid=10010,resgid=1065,errors=panic,data=ordered

so what should i do now?
i am trying to Root My Device from since 3 months
but failed.
How can i Get Proper Access of Root?
can you help me please

@ASIMKHAN222
Copy link
Author

Too late. We need a logcat since phone boots.

how to get that log again?

@yujincheng08
Copy link
Collaborator

Shut down the phone, run adb wait-for-device logcat > log, and then start up the phone. After the phone starts, stop the command and send log.

@ASIMKHAN222
Copy link
Author

Shut down the phone, run adb wait-for-device logcat > log, and then start up the phone. After the phone starts, stop the command and send log.

log.txt

@yujincheng08
Copy link
Collaborator

still too late

@yujincheng08
Copy link
Collaborator

Please increase your log buffer size to a large one

@ASIMKHAN222
Copy link
Author

ASIMKHAN222 commented Feb 12, 2022 •
edited by yujincheng08
Loading

Please increase your log buffer size to a large one

After increase buffer size to 16M
bootlog.txt

@yujincheng08
Copy link
Collaborator

yujincheng08 commented Feb 12, 2022 •
edited
Loading

still wayyyyyyyyy too late

@yujincheng08
Copy link
Collaborator

Your log only takes 1M so I think you didn't change your buffer size correctly.

@ASIMKHAN222
Copy link
Author

Your log only takes 1M so I think you didn't change your buffer size correctly.

okay. i shut down device,
then run this cmd adb wait-for-device logcat > log.txt
and start device i got this
log1.txt

i increased buffer size from developer option

@yujincheng08
Copy link
Collaborator

Maybe you should also need to set the log level to verbose in dev option.

@PUKAVEC38

This comment was marked as spam.

Sign in to view
@Hurairah0
Copy link

I have also same problem on my Vivo device.Plz solve it

@ASIMKHAN222
Copy link
Author

ASIMKHAN222 commented Feb 16, 2022 •
edited
Loading

Maybe you should also need to set the log level to verbose in dev option.

Sorry I tried Too Much But Not Succeed.
I Also Tried That CMD to Get BootLog on Another An oppo Device and Yes It's Working i Got Different Bootlog.
But On My Vivo Device It's Failed.
Seems its Only my vivo Device Fault.😑

Have You Any Other Idea?

@yujincheng08
Copy link
Collaborator

I notice your device does not produce debug log. Maybe thats the problem.

@aIecxs
Copy link

aIecxs commented Feb 19, 2022

similar issue after several downgrades - solved by uninstall + delete /data/adb

@ASIMKHAN222
Copy link
Author

similar issue after several downgrades - solved by uninstall + delete /data/adb
please guide how to find or access that /data/adb ?

@aIecxs
Copy link

aIecxs commented Feb 22, 2022

what do you mean? It's the directory where Magisk place stuff. boot in TWRP and remove it

@patpolster
Copy link

Seems Magisk is working but does not mount /system

[init.svc.UJOzq6Pi]: [stopped]
[init.svc.Yi86JkCAtCpN]: [stopped]
[init.svc.xP3Bw7bdrFX]: [stopped]
3647 3645 0:21 / /dev/uqVV rw,relatime master:4 - tmpfs tmpfs rw,seclabel,size=1911908k,nr_inodes=477977,mode=755
3648 3647 0:38 / /dev/uqVV/.magisk/pts rw,nosuid,noexec,relatime master:11 - devpts devpts rw,seclabel,mode=600,ptmxmode=000
3649 3647 259:6 / /dev/uqVV/.magisk/mirror/vendor ro,relatime master:12 - ext4 /dev/uqVV/.magisk/block/vendor ro,seclabel
3650 3647 259:9 / /dev/uqVV/.magisk/mirror/data rw,relatime master:13 - ext4 /dev/uqVV/.magisk/block/data rw,seclabel,discard,noauto_da_alloc,inlinecrypt,resuid=10010,resgid=1065,errors=panic,data=ordered
3651 3647 259:7 / /dev/uqVV/.magisk/mirror/system_root ro,relatime master:40 - ext4 /dev/uqVV/.magisk/block/system_root ro,seclabel
3652 3647 259:9 /adb/modules /dev/uqVV/.magisk/modules rw,relatime master:13 - ext4 /dev/uqVV/.magisk/block/data rw,seclabel,discard,noauto_da_alloc,inlinecrypt,resuid=10010,resgid=1065,errors=panic,data=ordered

@ASIMKHAN222
Copy link
Author

what do you mean? It's the directory where Magisk place stuff. boot in TWRP and remove it

My device have not any custom recovery, i tried to get but didn't find any compitable Recovery.

@aIecxs
Copy link

aIecxs commented Feb 23, 2022

just do factory reset? afaik for Mediatek chipset one can just port TWRP from other device

@ASIMKHAN222
Copy link
Author

just do factory reset? afaik for Mediatek chipset one can just port TWRP from other device

Tried factory Reset Many times But Not worth..
also tried to port TWRP for my Device but not Succeed.
i also tried Hovatek mediatek Auto TWRP porter good tool for many but not Worked For MT6768 Chipset.
when i flash recovery and try to go to TWRP mode
its just stuck at vivo logo and booted to bootloader/fastboot after a few minutes
i observed there is NO one single TWRP available for MT6768 Chipset.

If you can help
this is recovery logcat after flashing TWRP
recoverylogcat.txt

@aIecxs
Copy link

aIecxs commented Feb 25, 2022

If you already factory reset your device it means you already deleted /data/adb therefore your issue is different from mine.
mine was No daemon is currently running! after Magisk downgrade

@yujincheng08 yujincheng08 added the not enough info Not enough info to fix label Mar 2, 2022
@arch-user-france1
Copy link

Maybe you flashed it to boot_a instead of boot_b?

@ASIMKHAN222
Copy link
Author

ASIMKHAN222 commented Mar 7, 2022 •
edited
Loading

Maybe you flashed it to boot_a instead of boot_b?

No Device Have Not A/B partition it's A/Only

@ASIMKHAN222
Copy link
Author

ASIMKHAN222 commented Mar 7, 2022 •
edited
Loading

I notice your device does not produce debug log. Maybe thats the problem.

Sir, Is There any method for boot.img to Produce debug or Init Log?
Actually I Read Somewhere similar issue
init doesn't Start on Boot

@yujincheng08
Copy link
Collaborator

Maybe you should also need to set the log level to verbose in dev option.

@shivagnihotri
Copy link

Shut down the phone, run adb wait-for-device logcat > log, and then start up the phone. After the phone starts, stop the command and send log.

Good morning and greetings from Germany to everyone! I am facing the same Issue on my wonderful SHIFT6mq running LineageOS 18.1 and hope that my SHIFT6mq.log will help to confirm and solve this Issue. Namasté. 🙏

@canyie
Copy link
Collaborator

canyie commented Mar 30, 2022

@shivagnihotri I cannot find anything about Magisk in your log, so I think your issue is new. Maybe you should open a new issue for that.

@osm0sis osm0sis closed this as completed Mar 30, 2022
@yujincheng08 yujincheng08 added the stale No response for a long time label Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
not enough info Not enough info to fix stale No response for a long time
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@osm0sis @yujincheng08 @canyie @aIecxs @arch-user-france1 @Hurairah0 @patpolster @shivagnihotri @ASIMKHAN222 @PUKAVEC38