Hi,
Rooted with CM Autoroot but get the following error when using Magisk Manager to intall Magisk:
- Target image: /dev/block/
- Device platform: armeabi-v7a
! Unable to check signature
! Installation failed
All help appreciated!!
myotai said:
Hi,
Rooted with CM Autoroot but get the following error when using Magisk Manager to intall Magisk:
- Target image: /dev/block/
- Device platform: armeabi-v7a
! Unable to check signature
! Installation failed
All help appreciated!!
Click to expand...
Click to collapse
First of all, this thread is wrong section.
When installing magisk, there is no need to root it beforehand, as magisk has built in root. So I suggest you unroot it first, then install magisk from twrp.
myotai said:
Hi,
Rooted with CM Autoroot but get the following error when using Magisk Manager to intall Magisk:
- Target image: /dev/block/
- Device platform: armeabi-v7a
! Unable to check signature
! Installation failed
All help appreciated!!
Click to expand...
Click to collapse
use UnSU script by osmosis in twrp and install magisk also in twrp
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.14 HD65AA (GLOBAL)
Only for OOS 10.0.14 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_14.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_14.img
When finished type
Code:
fastboot reboot
patched boot.img download: https://drive.google.com/file/d/1wZ2TyIi0uUfbRTxPYK_imURBVjHqaA_f/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1R90vvdJEe6NkL2FdqSvuxtk18SmWHYUc/view?usp=sharing
It's still telling me "Root access is not properly installed on this device". I have an unlocked bootloader and OOS 10.0.14 HD65AA (GLOBAL), is there something I'm missing?
EDIT: tried a different root checker and I'm fine. Please disregard.
daaper said:
"Root access is not properly installed on this device"
Click to expand...
Click to collapse
Install Magdisk Manager
Thanks and much appreciate for the patched file!
Hello. No internet after booting.
EU&Asia : https://rom.download.nubia.com/Europe&Asia/NX729J/V312/NX729J-update.zip
EU : https://rom.download.nubia.com/Europe/NX729J/V412/NX729J-update.zip
CN : https://ui.nubia.cn/rom/detail/76
CN <-> Global steps : https://forum.xda-developers.com/t/chinese-rom-to-global-rom-tutorial.4452887/
bestman1069 said:
https://rom.download.nubia.com/Europe%26Asia/NX729J/V312/NX729J-update.zip
Does anybody want to trans CN to Global ??
Click to expand...
Click to collapse
Red magic 8 pro plus can it be installed?
Red magic 8 pro plus can it be installed?
I dont know the model no
bestman1069 said:
EU&Asia : https://rom.download.nubia.com/Europe&Asia/NX729J/V312/NX729J-update.zip
EU : https://rom.download.nubia.com/Europe/NX729J/V412/NX729J-update.zip
ISSUE : fingerprint not work . secure not work
Does anybody want to trans CN to Global ??
Click to expand...
Click to collapse
could anybody extract boot and vendor from eu 4.12 image. i could extract payload.bin on my Smartphone , but the extraction of the images did not work. my pc is at the Moment ill :-(
others would also like to root - i think.
thx in hopefully advance.
i need boot patch for red magic 8 pro v3.12
how to root ???? any one root phone
I need root for red magic 8 pro
V3.12
Any one help me
bestman1069 said:
EU&Asia : https://rom.download.nubia.com/Europe&Asia/NX729J/V312/NX729J-update.zip
EU : https://rom.download.nubia.com/Europe/NX729J/V412/NX729J-update.zip
CN : https://ui.nubia.cn/rom/detail/76
CN <-> Global steps : https://forum.xda-developers.com/t/chinese-rom-to-global-rom-tutorial.4452887/
Click to expand...
Click to collapse
here are
boot.img + vbmeta.img from eu 4.12.
i patched with magisk canary 25.2.
Afterwards i flashed boot with the patched_boot_image.
root is not working.
flashed boot_a + boot_b with patched image - also not working.
i used newest adb on win11.
vbmeta flash + disable dmverity also not working.
any ideas?
berndv01 said:
here are
boot.img + vbmeta.img from eu 4.12.
i patched with magisk canary 25.2.
Afterwards i flashed boot with the patched_boot_image.
root is not working.
flashed boot_a + boot_b with patched image - also not working.
i used newest adb on win11.
vbmeta flash + disable dmverity also not working.
any ideas?
Click to expand...
Click to collapse
Same here with 3.12 global/us.
Patched boot.img, tried flashing both a and b, magisk does not show root.
What happens if you patch init_boot.img (if there is one)?
tlxxxsracer said:
What happens if you patch init_boot.img (if there is one)?
Click to expand...
Click to collapse
Have not tried. The stock boot.img is 98MB, the init_boot.img is 8MB. quite a big difference.
Another interesting fact, there is nothing in the boot_b. Tried booting to it, and the phone went blank. Had to hard shut off, boot into bootloader, then switch back to boot_a, then it booted no problem.
If i had to guess, magisk isn't working with android 13 on the magic 8 pro. I even tried the canary version, no luck.
patching init_boot and trying to flash returns with
Sending 'init_boot' (8192 KB) OKAY [ 0.024s]
Writing 'init_boot' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
BoJaXz said:
patching init_boot and trying to flash returns with
Sending 'init_boot' (8192 KB) OKAY [ 0.024s]
Writing 'init_boot' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
Click to expand...
Click to collapse
what is different with this phone?
i rooted all my phones in the last years without problems.
crawling the internet for a solution...
V3.12 global
Not working:
Magisk patched boot.img (Both regular and canary)
Magisk patched init_boot.img (remote flash failed, not allowed for critical partitions)
Working:
Nothing yet
BoJaXz said:
V3.12 global
Not working:
Magisk patched boot.img (Both regular and canary)
Magisk patched init_boot.img (remote flash failed, not allowed for critical partitions)
Working:
Nothing yet
Click to expand...
Click to collapse
V 4.12 global
magisk alpha 25206 no success
BoJaXz said:
V3.12 global
Not working:
Magisk patched boot.img (Both regular and canary)
Magisk patched init_boot.img (remote flash failed, not allowed for critical partitions)
Working:
Nothing yet
Click to expand...
Click to collapse
fastboot flashing unlock_critical
Then you can flash patched init_boot.img
edzchen said:
fastboot unlock_critical
Then you can flash patched init_boot.img
Click to expand...
Click to collapse
fastboot flashing unlock_critical
but....it wiped my phone. really really really not happy about that!!!
Acted like i just unlocked the bootloader!!!
Edit: tried to install magisk after flashing init_boot.img, only installs v1.0 of magisk, 101kb in size, doesn't open, root checker shows no root
lost all applications, all saved keys with authenticators. everything.
do not unlock critical
Bypass charging/charge separation does not work on EU rom v4.12
berndv01 said:
V 4.12 global
magisk alpha 25206 no success
Click to expand...
Click to collapse
ota eu 4.18 is out
Download failed at 50%
multiple tries
Maybe they withdrew it. I'm showing nothing available
So I would like to root my a505f I installed OrangeFOX Recovery and when I tried to flash Magisk25.2.zip it is installed successfully without any errors but when I rebooting my device into the System Partition and opened Magisk manager I saw:
Magisk:
installed n/a
A/B No
Ramdisk No
SAR Yes
For some reason Magisk can only installed on the Recovery partition and I would like to install it on the system partition because the Recovery partition is very limited.
any knowledge would be appreciated
Model: SM-A505F ILO
AP VERSION: A505FDDS9CWA1
ANDROID VERSION: Android 11, One UI 3.0
SECURITY PATCH LEVEL: 2023-01-01
LoLzX said:
So I would like to root my a505f I installed OrangeFOX Recovery and when I tried to flash Magisk25.2.zip it is installed successfully without any errors but when I rebooting my device into the System Partition and opened Magisk manager I saw:
Magisk:
installed n/a
A/B No
Ramdisk No
SAR Yes
For some reason Magisk can only installed on the Recovery partition and I would like to install it on the system partition because the Recovery partition is very limited.
any knowledge would be appreciated
Model: SM-A505F ILO
AP VERSION: A505FDDS9CWA1
ANDROID VERSION: Android 11, One UI 3.0
SECURITY PATCH LEVEL: 2023-01-01
Click to expand...
Click to collapse
Maybe read Magisk's FAQs about samsung devices
Recovery Root is old method. Use patched-kernel method
Ok thanks
Hello, I want to root my device and install magisk. This is my device:
xiaomi redmi note 8 pro (begonia)
Miui Global Stable 12.5.7.0 (RGGEUXM)
Android Version: 11 RP1A.200720.011
Bootloader: unlocked
I flashed twrp with BRP3.5.2v3.1.
Code:
ECHO Recovery for Miui 12.5 Android 11
fastboot flash recovery BRP3.5.2v3.1.img
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
fastboot reboot recovery
I installed contained Magisk-v22103.zip via twrp > advanced > install magisk. TWRP flashing window shows Magisk 23.0 Installer.
Then Wipe Cache / Dalvic. Then > advanced > close avb 2.0.
Then Wipe Cache / Dalvic. Then Reboot System.
Starting magisk app shows version 23.0 (23000) paket com.topjohnwu.magisk.
Status SafetyNet check: basicIntegrity negative, ctsProfile negative, evalType Hardware.
I followed two guides with loading magisk modules MagiskHide_Props_Config-v6.1.2-v137(75), Riru-v26.1.4.r522.8b379cedb5(522).zip, safetynet-fix-v2.1.1.zip and safetynet-fix-v2.2.1.zip, Busybox_for_Android_NDK-1.34.1(13411).zip.
I installed Termux app, hit commands su + setenforce 0. I did fingerprinting Google Pixel 5 and 4a.
Both these guides not helped passing the safetynet check, since
Status SafetyNet check: basicIntegrity positive, ctsProfile negative, evalType Hardware.
While Magisk-v22103.zip has SafetyNet check, Magisk-25.2.zip doesn't have and Magisk-25.2.zip is not able to load any modules by internet but just by 'install from storage'.
Why is it like that and what should I do to install magisk properly passing the safetynet check?