Hi there,
I've recently taken the plunge and decided to root my phone. I followed all the instructions and everything went fine except I can't get Magisk to install. When I run root checker it confirms my phone is successfully rooted, see screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I go into Magisk it fails the installation saying 'Unable to check signature'. See screenshots below
Looking at the installation instructions here https://topjohnwu.github.io/Magisk/install.html I believe as Ramdisk is 'Yes', then my phone is ready to install Magisk. I believe that if I patch my phone with a boot.img file then I should be able to successfully install Magisk. However, 1) I'm not sure it will given the error I'm getting and 2) wherever I search I cannot seem to download the correct firmware for my phone to be able to get the correct boot.img file that I need. Here are the screenshots showing the installed software version.
I'd be super appreciative to anyone that can advise me as to what to do next to try and resolve the installation issues so that I can benefit from the wonders of Magisk.
Thank you
f19fox said:
Hi there,
I've recently taken the plunge and decided to root my phone. I followed all the instructions and everything went fine except I can't get Magisk to install. When I run root checker it confirms my phone is successfully rooted, see screenshot.
View attachment 5290275
But when I go into Magisk it fails the installation saying 'Unable to check signature'. See screenshots below
View attachment 5290281View attachment 5290283
Looking at the installation instructions here https://topjohnwu.github.io/Magisk/install.html I believe as Ramdisk is 'Yes', then my phone is ready to install Magisk. I believe that if I patch my phone with a boot.img file then I should be able to successfully install Magisk. However, 1) I'm not sure it will given the error I'm getting and 2) wherever I search I cannot seem to download the correct firmware for my phone to be able to get the correct boot.img file that I need. Here are the screenshots showing the installed software version.
View attachment 5290293View attachment 5290297
I'd be super appreciative to anyone that can advise me as to what to do next to try and resolve the installation issues so that I can benefit from the wonders of Magisk.
Thank you
Click to expand...
Click to collapse
Flash magisk zip in via recovery
Austinredstoner said:
Flash magisk zip in via recovery
Click to expand...
Click to collapse
Hi. Thank you for your reply and advice. I flashed Magisk using TWRP recovery but it still won't install. Here is the screenshot. I also uninstalled the App and re-downloaded as per these instructions https://bit.ly/32P3Z9z but I still get the same error
Do you or anyone else have any more suggestions please?
Thanks!
@f19fox: Apologies to be hijacking your thread.
Build Number: NMF26X.J510FNXXU2BRJ4
Android Running Version: 7.1.1
I downloaded the IMG file of the BRJ4 raw boot image from firmware.mobi, successfully patched it via the Magisk app, and subsequently flashed the patched boot image via TWRP (selecting the boot partition within TWRP).
However, the Magisk card within the app still displays N/A within the app.
Related
Yep it's out.
For those of you in need to manually update read below.
Download: cm-bacon-d22b777afa-to-0428073396-signed.zip (KTU84P, XNPH30O)
Install: To install the update, flash a custom recovery (TWRP recommended), boot into it, then sideload using adb sideload - if you've ever updated a Nexus device before, then you'll feel right at home, as the steps are exactly the same. TWRP will ask if you want to re-root at the end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wtf is this thread....anyways has anyone tried a clean flash yet?
just flashed it. thanks man!
Why can you flash the zip, why do you have to sideload it ?
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
I flashed it through TWRP, NO ISSUES
doalittledanse said:
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
Click to expand...
Click to collapse
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
clipcarl said:
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
Click to expand...
Click to collapse
yep. on both the stock cm recovery and twrp i get this error:
Code:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
If you've flashed any mods or made any changes to the system. It will fail.
Exclusive Member of the OnePlus One Club
If you guys flashed my Smooth Scrolling Mod, flash the revert and then try the OTA
http://forum.xda-developers.com/one...scrolling-mod-mahdi-rom-t2840934/post54762296
Basically when you're on stock ROM and if you did any changes to your /system/ then it will not update because its been modified.
does this include removal of apps ? Mine failed to sideload as well.+
Edit 1: I did do some modding of the build.prop as well this morning.
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
doalittledanse said:
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
Click to expand...
Click to collapse
Same problem here, fails at:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
Everything is stock, except Recovery. Tried with original recovery and it still fails...
Got mine to update even though the system partition was updated with a modified updater-script.
I will upload the entire zip with the updated script. For those that know what they are doing the updater-script is attached.
Edit 1: Note you do loose root. You have to install supersu again if you did have it previously (if you modified system then you did)
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Anyone tried custom kernels with ota?
Sent from my A0001 using XDA Free mobile app
C-4Nati said:
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Click to expand...
Click to collapse
look at my post.
I guess the update.zip factory image from the official site isn't truly stock. so i went with the nuclear option and just reflashed everything via fastboot. update worked perfectly now haha.
Please go to the thread here to continue the conversation....http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689
Hi all, well I think I have all but fubarred my 16gb shield tv. I unlocked bootloader, installed twrp and rooted, all was working fine. Then I decided to flash the full android rom that is on the forum . before doing so, i used twrp and made a backup. I installed the full android rom, although it seemed to work fine, i was not crazy about it and decided to go back to the original OS, so I booted up in twrp and went to the restore function, there were no backups to restore , I guess when I installed the system img for the full android it erased my backup somehow. anyway, moving right along, I next went to nvidia website and downloaded the restore image for the 16gb shield tv, i booted in to bootloader and was following the instructions to restore the shield. all seems to go fine until I try to flash the system img, then I get the error "invalid sparse file format at unknown block 0000" it tries to continue but fails, afterwards the system will not boot at all, I can get back to twrp recovery an flash the full android rom just fine, but am not able to flash back the original os without that error. any suggestions would be greatly appreciated, as I am stuck at this point as what to attempt next. thanks
Here is an image of the error I get, I am no longer able to write to the system partition,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cdsn99 said:
Here is an image of the error I get, I am no longer able to write to the system partition
Click to expand...
Click to collapse
Just going to go out on limb here, but are you sure the downloaded image isn't corrupted? You could try to download it again, if available do a MD5 hash check to verify it downloaded correctly and then retry flashing it.
d-dragon said:
Just going to go out on limb here, but are you sure the downloaded image isn't corrupted? You could try to download it again, if available do a MD5 hash check to verify it downloaded correctly and then retry flashing it.
Click to expand...
Click to collapse
thanks d-dragon, I re downloaded the image from nvidia and was able to successfully flash it, thanks for the reply and help
Glad to hear my suggestion helped you out Enjoy the shield!
Sent from my Nexus 5 using Tapatalk
send the link
cdsn99 said:
thanks d-dragon, I re downloaded the image from nvidia and was able to successfully flash it, thanks for the reply and help
Click to expand...
Click to collapse
can send the link for stock rom
ahm3336 said:
can send the link for stock rom
Click to expand...
Click to collapse
https://developer.nvidia.com/gameworksdownload
Hello friends, please guide me.
First I tried to install Phronesis rom in my note 3 but failed. Then I tried to install "Norma Rom Note 5 V29" but again it failed just like before.
When I click "install" option in the TWRP recovery main menu it open a new menu where it asks me to select the zip. When I select zip file it asks me to "swipe to install". When I swipe it open a new window where few commands starts appearing on screen and a blue bar starts moving at the bottom of screen. After a few seconds a command appear saying "starting aroma installer". and after this phone restarts and get stuck on note 3 logo.
Please help me in this regard. All the information about my phone is given below.
TWRP recovery version that I have is "twrp-3.0.1-0-hlte".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No one?
Some using the search function and you find out that TWRP 3 does not work with Aroma Installers. ^^ Use 2.8.7.0 and you are set.
waqar bukhari said:
No one?
Click to expand...
Click to collapse
You have already been given instructions but are to lazy to read and require spoonfeeding .
emuandco said:
Some using the search function and you find out that TWRP 3 does not work with Aroma Installers. ^^ Use 2.8.7.0 and you are set.
Click to expand...
Click to collapse
JJEgan said:
You have already been given instructions but are to lazy to read and require spoonfeeding .
Click to expand...
Click to collapse
Thanks to you. If I knew that TWRP is causing it then surely I would have searched. By the way I have been trying to use search option but due to not-knowing of what to search this option is not very helpful. That's why I have to create new thread. If I am violating any rules of the forum then I apologize.
I got the solution for this problem before you "SpoonFeeded" me. Instead of being rude you should have mentioned this at the moment when I asked this question for the first time? And I was not given any instructions to do this.
Thanks to you. If I knew that TWRP is causing it then surely I would have searched.
As i said read Questions and Answers its all posted but you refused to read .
2.2 Question:Why is it unable to flash the Rom? After flashing the Rom Zip File from TWRP, the AROMA Installer wan't open and the Phone would just reboot.
I try to flash the Rom but now i stuck on Samsung Boot Animation. Phone don't boot. What to do? Answer:
1. Have you checked the MD5 Checksum? Sometimes a Download is corrupt and a Instalation fails. You find the MD5 Checksum behind the Downladlink.2. Which Recovery you using? Sometimes the Recovery make problems install a Rom with Aroma Installer.
For now TWRP V3.0 makes trouble and don't let you instal the Rom. Try a earlier version or a different Recovery.
Hi there, I've been having problems with the Titanium Backup recently and tried some troubleshooting method such as unticking Mount namespace separation in SuperSU. They didn't work until i get to the point on updating the SuperSU from Play store. Then asked me to update the binary which i selected TWRP and it rebooted. After the installation from TWRP, it only boots to recovery. Tried turning off the phone and it still go to recovery even if i select reboot system.
Now i tried re-flashing the 'CF-Auto-Root-a7lte-a7ltexx-sma700fd.tar' via Odin3. It completed but then it's only boot looping. Sure i know it would reset multiple times but it has been more than 30mins doing like that over and over again. Tried to flash the TWRP again via Odin and wiped data/system/cache. And tried installing the Ressurection rom but it fails it gives me error "E:Error executing updater binary in zip '/external_sd/A7 Root and all/Roms/RessurectionRemix........"
Error flashing zip........
Then tried rebooting system. It said no OS installed proceed to reboot then saying device does not appeared to be rooted and asked me to install SuperSU which I did and it just restarted and still on boot loop....
Any help, please? TIA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happen when i try to flash the firmware that i downloaded from sammobile... please help.
On the recovery, whenever i try to reboot, it says No OS installed. Then SuperSU installation. Whenever i try to install a custom rom, it fails. Giving me error: error executing updater binary in zip...
gsmtec said:
flash latest version for you model, should work
Trimis de pe al meu SM-G920F folosind Tapatalk
Click to expand...
Click to collapse
which one? CF auto root? firmware? thanks for replying..
btw im flashing the latest ones. except the SuperSU which I will try later. But the No OS installe would be the problem i think?
gsmtec said:
flash latest 6.0.1 version for your region or for the one that phone came
Click to expand...
Click to collapse
not sure but when i clicked earlier it was all china versions. and on first click on something it selects other something like samsung camera. but now i was able to see the firmwares. guess the site have some bugs. imma try it.
there's no 6.0.1 on my region. only 5.0.2 and lower versions.. i take the 5.0.2?
Hello, I have a root issue. I have an Axon 7 2017G V1.2.0B08 with unlocked bootloader and TWRP. Anyway, when I try to flash SuperSU (2.82), it does not give to me the root access. I mean, when I open the app of SuperSu, it alert to me "Root undetected". Can you help me?
Thanks,
youngz
Try Magisk 14
youngz89 said:
Hello, I have a root issue. I have an Axon 7 2017G V1.2.0B08 with unlocked bootloader and TWRP. Anyway, when I try to flash SuperSU (2.82), it does not give to me the root access. I mean, when I open the app of SuperSu, it alert to me "Root undetected". Can you help me?
Thanks,
youngz
Click to expand...
Click to collapse
Version 2.82 is crap. Users of my toolkit had bootloops because of it. Use 2.79 instead.
Hi, I tried to flash supersu 2.79 and the result is the same.
In order to flash magisk 14, I have to do some particular procedure o I have to just flash it?
Edit: furthermore, I want to modify the host file in system partition. But if I use only magistik, I suppose to be not able to modify that partition.
youngz89 said:
Hi, I tried to flash supersu 2.79 and the result is the same.
In order to flash magisk 14, I have to do some particular procedure o I have to just flash it?
Edit: furthermore, I want to modify the host file in system partition. But if I use only magistik, I suppose to be not able to modify that partition.
Click to expand...
Click to collapse
Just wipe system, reflash your ROM and then flash Magisk. I didn't understand what you said about the 'host file', if you mean that you wanna use adaway then yes you should be able to use it
Yes, I means adaway. Thanks for your reply! Another information. I have to wipe also the data partition? It will be boring install again all my apps, SMS, and stuffs..
youngz89 said:
Yes, I means adaway. Thanks for your reply! Another information. I have to wipe also the data partition? It will be boring install again all my apps, SMS, and stuffs..
Click to expand...
Click to collapse
Your phone is encrypted if you didn't install magisk or supersu. If you want to install a new ROM you will have to format data (which means losing the internal storage too). But you don't need to wipe anything to instal Magisk. Just a suggestion, make a system backup
Thank you for your suggestions. I had reinstalled the system and I flash magisk 14. Anyway, now, when I open the application and I start the check, the app return:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Furthermore, when I try to install some software, it return an error about the partition mount:
Have you any solution about these problems?
Thanks
youngz89 said:
Thank you for your suggestions. I had reinstalled the system and I flash magisk 14. Anyway, now, when I open the application and I start the check, the app return:
Furthermore, when I try to install some software, it return an error about the partition mount:
Have you any solution about these problems?
Thanks
Click to expand...
Click to collapse
Alright. What did you do to install the system again with magisk? Tell me step by step
Ok, my steps:
1) Wipe caches, system, and data with twrp
2) flash the bootstack
3) flash the rom
4) flash magisk 14
5) flash again twrp (as precaution)
6) boot the os and config it
7) update magisk app mannualy with the last version
I also use a command (reboot disemmcwp) from twrp shell to enable the writing on system partition but the result was the same.
Maybe I have a solution (maybe). In twrp, I set the system partition as read only. Anyway, could I remove it without risk (as an overwriting of recovery or bootloader)?
Thank you.