I am using Resurrection Remix.
How can I install Magisk
When I try to flash the magisk zip it terminates with Error 1.
pusansen99 said:
I am using Resurrection Remix.
How can I install Magisk
When I try to flash the magisk zip it terminates with Error 1.
Click to expand...
Click to collapse
Redownload it. Error code 1 is for corrupted zip files; I found this out when I "moved" Magisk from my internal storage to my SD Card through TWRP's file manager, and it ended up being 1kb in size (just to let you know if you used TWRPs file manager)
jcolongo said:
Redownload it. Error code 1 is for corrupted zip files; I found this out when I "moved" Magisk from my internal storage to my SD Card through TWRP's file manager, and it ended up being 1kb in size (just to let you know if you used TWRPs file manager)
Click to expand...
Click to collapse
No its something related to the boot.img
pusansen99 said:
No its something related to the boot.img
Click to expand...
Click to collapse
What happens when you flash it? Either:
A) Magisk appears, does it's stuff, then says error one. No red text.
B) Instantly/a second after swiping to flash, you get red text along the lines of "failed to flash /etc/magisk.zip: error 1".
jcolongo said:
What happens when you flash it? Either:
A) Magisk appears, does it's stuff, then says error one. No red text.
B) Instantly/a second after swiping to flash, you get red text along the lines of "failed to flash /etc/magisk.zip: error 1".
Click to expand...
Click to collapse
B
It also says boot.img is already patched...
pusansen99 said:
B
It also says boot.img is already patched...
Click to expand...
Click to collapse
Have you tried redownloading it? It won't hurt.
jcolongo said:
Have you tried redownloading it? It won't hurt.
Click to expand...
Click to collapse
Yeah
pusansen99 said:
Yeah
Click to expand...
Click to collapse
Can you please post the entirety of the log that is shown? You can save your log in TWRP.
jcolongo said:
Can you please post the entirety of the log that is shown? You can save your log in TWRP.
Click to expand...
Click to collapse
I first flashed SuperSU. After that from the SuperSU app I did full unroot and while doing that i selected the option to restore stock boot.img. After doing that Magisk flashed successfully.
Related
Since I keep getting PM's about the link for the zip, I have put it back up.
(Currently not working)
Nougat beta for SM-G930T:
https://mega.nz/#!dJ41lQSY!27WInCDKAtvlcLbBHe6rHkqDmCbwuOln_eQT_Jh4cQM
This is zip was different attempt at pulling. Still wouldn't flash for me:
https://mega.nz/#!sUo0ERCC!drPmD1Fz_Gd76jDdZjtxIsjrmEsZzvHBT8uLwKXu3F4
It's happening!
Stand by for the update.zip.
delete
Downloading to flash on my 930A via Odin. Will let you know
mrmattolsen said:
Downloading to flash on my 930A via Odin. Will let you know
Click to expand...
Click to collapse
You can't flash this with odin. It's a update zip, you need to use recovery.
billydroid said:
You can't flash this with odin. It's a update zip, you need to use recovery.
Click to expand...
Click to collapse
LOL oh yeah. So I'm going to do that and report back..
Downloading now. Will update as soon as the munchkin goes to bed.
mrmattolsen said:
LOL oh yeah. So I'm going to do that and report back..
Click to expand...
Click to collapse
I updated the instructions
scottricketts said:
Downloading now. Will update as soon as the munchkin goes to bed.
Click to expand...
Click to collapse
I updated the instructions
Any instructions on how to install when tethered? I don't have an sd card installed atm. Thank you.
kalinsky said:
Any instructions on how to install when tethered? I don't have an sd card installed atm. Thank you.
Click to expand...
Click to collapse
You can install via ADB. I think you jsut place it were adb is installed on your pc.
So usually platform-tools, I'm not sure.
http://androiding.how/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/
Skip the irrelevant parts, lol. As you already have the zip.
I've got my card as Adoptable Storage so installing from sdcard didn't work. Tried installing from adb sideload and got "Footer is wrong. Signature verification failed."
scottricketts said:
I've got my card as Adoptable Storage so installing from sdcard didn't work. Tried installing from adb sideload and got "Footer is wrong. Signature verification failed."
Click to expand...
Click to collapse
Did you Rename it as ota.zip when doing adb sidleoad install?
Ah, no. Left it as update.zip. I'll give it another shot. Standby (oh I did confirm md5sums as correct)
Also getting footer is wrong, tried both ADB sideload and installing from SD.
scottricketts said:
Ah, no. Left it as update.zip. I'll give it another shot. Standby (oh I did confirm md5sums as correct)
Click to expand...
Click to collapse
This I why I waites before I did it myself. I didn't want to loose the original copy. I uploaded the one form my wife's sprint edge and it was corrupted and I had to restore her phone. Caused some grief for people.
It's telling me the archive is corrupt. Will try to re-download..
krytikul said:
Also getting footer is wrong, tried both ADB sideload and installing from SD.
Click to expand...
Click to collapse
When you did sideload did you rename it to ota.zip? What method did you try for sdcard install? Did you create a fota folder and place it in it as update.zip?
If no one gets this to work don't freak out. I'll contact someone who can give us hand. I still have the original in the /data/fota folder. The md5 checksum I posted was from the copy. As I couldn't get it for the original. I didn't install superuser, jsut the eng_boot
And failed again. Same errors. Confirmed md5sums again and same errors regarding footer and signature verification. This is also a total stock phone, never rooted or customized.
So this week i hadn't time enough to install the august update since my phone is rooted so i decided to do it now. What i did before trying to download the update :
1.Deleted all magisk modules that i had then rebooted
2.Unistalled magisk using restore image then rebooted
3.Went to sys update downloaded and it says installation failed
What do to? I'm not rooted now and i don't have twrp installed.
PS. don't want to install it via fastboot/miflash
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
emiljano539 said:
PS. don't want to install it via fastboot/miflash
Click to expand...
Click to collapse
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
sipollo said:
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
Click to expand...
Click to collapse
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
emiljano539 said:
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
Click to expand...
Click to collapse
You won't lose your data.
ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
flashed the stock boot image tried to install it but again it shows that error , i guess the only thing i can do is to flash it manually via fastboot/miflash
sipollo said:
You won't lose your data.
Click to expand...
Click to collapse
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
emiljano539 said:
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
Click to expand...
Click to collapse
It doesn't matter. You'll have to reinstall Magisk (if you want to).
sipollo said:
It doesn't matter. You'll have to reinstall Magisk (if you want to).
Click to expand...
Click to collapse
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
emiljano539 said:
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
Click to expand...
Click to collapse
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
sipollo said:
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
Click to expand...
Click to collapse
I installed the zip from twrp and now after reboot i am stucked in bootloop now i can't even boot into twrp. What to do?
After i flashed it in the end says:
Failed to mount /system Invalid argument
Which TWRP did you use?
sipollo said:
Which TWRP did you use?
Click to expand...
Click to collapse
the official one. what version should i use?
its funny now that i flashed the stock rom via mi flash tool and now again the installation shows error..
ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
I'm facing same issue and I was following the guide.
Same here, can't install set Ota, even after remove magisk.
Other thing, cell won't show screen to put pin to boot, previous pin of sim so I think encryption is disable!? Any idea?
Updating MIUI using TWRP gives a zip treble compatibility error. Any solutions?
Shikhar_G said:
Updating MIUI using TWRP gives a zip treble compatibility error. Any solutions?
Click to expand...
Click to collapse
Use a different TWRP, or open the ROM zip and delete compatibility.zip from it.
DarthJabba9 said:
Use a different TWRP, or open the ROM zip and delete compatibility.zip from it.
Click to expand...
Click to collapse
It worked for me, thank you so much!
Requires Bootloader to be unlocked (Tutorial for unlocking T-Mobile bootloader)
INSTRUCTIONS
- Download the latest Magisk.zip from github, it will be an apk file. Rename it to a ".zip" file. (link below)
- Download attached recovery.img and boot into it using fastboot on a PC. (command below)
- Once booted into recovery choose "Apply Update" then "Apply from ADB"
- In adb on your PC, push the magisk.zip with the command "adb sideload Magisk-vXXX.zip" Make sure the magisk zip file is in your fastboot folder if you don't have fastboot system-wide.
- It will give signature verification error on your phone, choose "INSTALL ANYWAY"
- Reboot to system and install the Magisk Manager app. Choose install at the top, select direct install, and allow the app to install and reboot.
To flash recovery
Code:
fastboot boot recovery recovery.img
DOWNLOADS
- Latest Magisk
- Recovery.img
Awesome easy as can be, worked great. Thank you!
Does it need unlocked bootloader?
remialfa said:
Does it need unlocked bootloader?
Click to expand...
Click to collapse
Yes sir
So simple & fast... no fussy boot.img patching with specific Magisk versions, etc!
How will you install updates?
Thanx
mobile_sensei said:
So simple & fast... no fussy boot.img patching with specific Magisk versions, etc!
How will you install updates?
Thanx
Click to expand...
Click to collapse
Can we update magisk from the magisk app?
TeamHackura said:
Can we update magisk from the magisk app?
Click to expand...
Click to collapse
Yes my friend working like a charm
FoxyDrew said:
Yes my friend working like a charm
Click to expand...
Click to collapse
Excellent! Thank you.
For others when installing oos update; disable magical modules, install oos update, before restarting install Magisk to both slots using the app, reboot, enable modules if any.
Using tmobile oneplus 8 unlocked bootloader
Can you break this down a bit more? So I'm on a mac I downloaded both files. Typed the command into the terminal and get disk image is corrupted
Rms44 said:
Using tmobile oneplus 8 unlocked bootloader
Can you break this down a bit more? So I'm on a mac I downloaded both files. Typed the command into the terminal and get disk image is corrupted
Click to expand...
Click to collapse
No experience with fastboot on mac, but try to re-download the image.
FoxyDrew said:
No experience with fastboot on mac, but try to re-download the image.
Click to expand...
Click to collapse
it worked thank you
I'm stuck on the part where you have to side load the magisk file in recovery. When i do the command i get his error
adb: failed to read package block: Is a directory
Rms44 said:
I'm stuck on the part where you have to side load the magisk file in recovery. When i do the command i get his error
adb: failed to read package block: Is a directory
Click to expand...
Click to collapse
Are you sideloading the zip, or maybe when you downloaded the magisk zip, your Mac automatically unzipped it so you now have a directory.
I haven't used this root method, but I use Macs once in a while, and that's one of my annoyances with one of the Macs I use.
trinidude4 said:
Are you sideloading the zip, or maybe when you downloaded the magisk zip, your Mac automatically unzipped it so you now have a directory.
I haven't used this root method, but I use Macs once in a while, and that's one of my annoyances with one of the Macs I use.
Click to expand...
Click to collapse
What would I do to remove the directory just delete the file ?
Rms44 said:
What would I do to remove the directory just delete the file ?
Click to expand...
Click to collapse
You have to just make sure you have the magisk zip file instead of an unzipped version. Next time I'm working on a mac, I can play around to see if I can replicate your problem.
Rms44 said:
What would I do to remove the directory just delete the file ?
Click to expand...
Click to collapse
I finally had some time to try this out on a Mac and everything worked out for me. I couldn't get the same error message you were getting. I did use Magisk v22 though. The only thing you'll have to do is rename the .apk to .zip.
Hey there, bro. seems like the Recovery link is down, please help me out
aperisimo said:
Hey there, bro. seems like the Recovery link is down, please help me out
Click to expand...
Click to collapse
Nvm i extracted recovey.img from the crdroid rom myself. hope it works
Thank you.
Works on OnePlus 8 India.
Since the recovery link in OP is deleted, I extracted the latest one myself.
Here's the recovery from crDroidAndroid-11.0-20210517-instantnoodle-v7.6
This didn't work for me, I got this error after running sideload. Any idea how to resolve this?
"E: Failed to find update binary META-INF /com/google/android/update-binary"
Device - SM-A205FN.
Firmware - A205FNXXSACVB1.
Custom ROM - AospExtended-v9.0-a20-UNOFFICIAL-20220225-2212.
TWRP version - 3.6.1_9-0 [official].
I can’t install this ROM in any way, because when flashing into TWRP, error 1 pops up. I tried to clear various partitions and also deleted the first two lines of the updater-script file.
ANFOR7 said:
Device - SM-A205FN.
Firmware - A205FNXXSACVB1.
Custom ROM - AospExtended-v9.0-a20-UNOFFICIAL-20220225-2212.
TWRP version - 3.6.1_9-0 [official].
I can’t install this ROM in any way, because when flashing into TWRP, error 1 pops up. I tried to clear various partitions and also deleted the first two lines of the updater-script file.
Click to expand...
Click to collapse
Is that latest stock already?
Used "format data" as well?
Changing file system to and fro helped me once when formatting didn't help.
bmwdroid said:
Is that latest stock already?
Used "format data" as well?
Changing file system to and fro helped me once when formatting didn't help.
Click to expand...
Click to collapse
Did you change the file system of the system and did it help you avoid error 1?
I use the latest official firmware and the latest version of the official TWRP and also format the data before installing a custom ROM.
ANFOR7 said:
Did you change the file system of the system and did it help you avoid error 1?
Click to expand...
Click to collapse
Yes. To f2fs and back to ext4.
ANFOR7 said:
I use the latest official firmware and the latest version of the official TWRP and also format the data before installing a custom ROM.
Click to expand...
Click to collapse
bmwdroid said:
Yes. To f2fs and back to ext4.
Click to expand...
Click to collapse
Did you reboot?
ANFOR7 said:
Did you reboot?
Click to expand...
Click to collapse
Yes to TWRP
bmwdroid said:
Yes to TWRP
Click to expand...
Click to collapse
Did not help(
ANFOR7 said:
Did not help(
Click to expand...
Click to collapse
Sorry to hear that.
Last thing I would try is flashing latest stock ROM and start from scratch.
bmwdroid said:
Sorry to hear that.
Last thing I would try is flashing latest stock ROM and start from scratch.
Click to expand...
Click to collapse
This is what I do before every attempt to install a custom ROM.
bmwdroid said:
Sorry to hear that.
Last thing I would try is flashing latest stock ROM and start from scratch.
Click to expand...
Click to collapse
Should I try to lock and then unlock the bootloader back? I heard it clears partitions completely. By the way, in the TWRP tar-archive, not only custom recovery.img, but also custom vbmeta.img to bypass protection. Could this be causing error 1?
ANFOR7 said:
Should I try to lock and then unlock the bootloader back?
Click to expand...
Click to collapse
can't give you any advice here. I'd search other threads before to learn more what happens then.
ANFOR7 said:
I heard it clears partitions completely.
Click to expand...
Click to collapse
afaik it's only doing a factory reset.
ANFOR7 said:
By the way, in the TWRP tar-archive, not only custom recovery.img, but also custom vbmeta.img to bypass protection. Could this be causing error 1?
Click to expand...
Click to collapse
Probably but I'm not sure
Edit: just had a look inside the official twrp-3.6.1_9-0-a20.img.tar and I see only recovery.img
Where did you get the TWRP you're using from.
bmwdroid said:
just had a look inside the official twrp-3.6.1_9-0-a20.img.tar and I see only recovery.img
Where did you get the TWRP you're using from.
Click to expand...
Click to collapse
Someone on another forum gave me an archive with recovery.img, boot.img and vbmeta.img. I extracted only vbmeta.img from there and put it in the archive with the official twrp.
Link to the file: https://ru.files.fm/f/wdzcpqbjd
ANFOR7 said:
Someone on another forum gave me an archive with recovery.img, boot.img and vbmeta.img. I extracted only vbmeta.img from there and put it in the archive with the official twrp.
Link to the file: https://ru.files.fm/f/wdzcpqbjd
Click to expand...
Click to collapse
I c
bmwdroid said:
I c
Click to expand...
Click to collapse
Sorry, I can't speak English, I communicate through Google Translate. I don't understand what "I c" means.
ANFOR7 said:
Sorry, I can't speak English, I communicate through Google Translate. I don't understand what "I c" means.
Click to expand...
Click to collapse
I c = I see