Hi guys, I have a quick question.
I want the newest Magisk version, to install every time I update my system, using CyanDelta. This however, requires that I manually move each update to the CyanDelta folder and edit the app setting to install the newest version with each update.
I would like to have a dummy zip, with an installer-script, that will use wild cards, to flash the newest magisk-**.zip
Something like
install("/sdcard/MagiskManager/Magisk-v****.zip")
Essentially, CyanDelta will "flash" this dummy zip. This dummy zip will then call the newest Magisk zip, to install.
Is this possible? Has anyone already done this? If so, mind linking me to the zip file already made (or the code already typed out)?
Alternatively, any tasker task to easily rename and move the latest update, automatically, once the new update is downloaded?
mkhcb said:
Hi guys, I have a quick question.
I want the newest Magisk version, to install every time I update my system, using CyanDelta. This however, requires that I manually move each update to the CyanDelta folder and edit the app setting to install the newest version with each update.
I would like to have a dummy zip, with an installer-script, that will use wild cards, to flash the newest magisk-**.zip
Something like
install("/sdcard/MagiskManager/Magisk-v****.zip")
Essentially, CyanDelta will "flash" this dummy zip. This dummy zip will then call the newest Magisk zip, to install.
Is this possible? Has anyone already done this? If so, mind linking me to the zip file already made (or the code already typed out)?
Alternatively, any tasker task to easily rename and move the latest update, automatically, once the new update is downloaded?
Click to expand...
Click to collapse
I dunno if a zip can call another zip...
However with Tasker... You can use RUN SHELL with a 'su -c' in front of the command to rename and move your magisk zip to your flashaftetupdate directory...
Then just call on it with your recovery
Sent from my Nexus 6 using Tapatalk
Related
Hey all, I'm currently in RA after flashing the recovery image , and I'm trying to install the FRESH rom on there but for some reason when I try to "Flash zip from sdcard" it's telling me "No zip files found." Why is that? I have the whole zip folder placed in the main SD card, so why is it telling me it's not found?
BOOGIE_BOTZ said:
Hey all, I'm currently in RA after flashing the recovery image , and I'm trying to install the FRESH rom on there but for some reason when I try to "Flash zip from sdcard" it's telling me "No zip files found." Why is that? I have the whole zip folder placed in the main SD card, so why is it telling me it's not found?
Click to expand...
Click to collapse
I responded to you on http://GeekFor.Me, but the reason is because RA looks in the root of sdcard, the zips can't be inside of any folders.
So does that mean I have to take out all the individual files and place them directly into the root of the sdcard? Because I just basically copied the download folder and dropped it into the root. Thanks for the reply
BOOGIE_BOTZ said:
So does that mean I have to take out all the individual files and place them directly into the root of the sdcard? Because I just basically copied the download folder and dropped it into the root. Thanks for the reply
Click to expand...
Click to collapse
You need to leave the files in a .zip, but yea that zip needs to be on the root of the sdcard.
The only file you need to install the rom is fresh-cdma-hero-20d.zip (for fresh rom 2.0d). Any other zips are just addons or tweaks or whatever they may be.
flipzmode said:
You need to leave the files in a .zip, but yea that zip needs to be on the root of the sdcard.
The only file you need to install the rom is fresh-cdma-hero-20d.zip (for fresh rom 2.0d). Any other zips are just addons or tweaks or whatever they may be.
Click to expand...
Click to collapse
Hmm, I'm on a Mac and maybe it's me but the link I download from gives me an actual folder rather than a zip. And when I rename the folder to a zip, it gives an error. Is there a mirror link to download an actual zip folder?
Boogie when you download it dont opening after it finishes downloading .. just use the finder to navigate to where its at and then copy that to your sd .. when you open it on a mac it will automatically create the extracted folder .. hope this helps ...
Sounds like your using Safari to download it. To make this easier in the future go to Safari > Preferences > General and make sure that "Open safe files after downloading" is NOT check-marked.
Safari is unpacking the zip file for you. The file you want is in your trash bin, drag it to the root of your SD card and that's it..
Ok I'm gonna give it another go. Since I made it all the way through to the RA stage, there's no reason I shouldn't be able to flash the rom is there?
Thanks for all the help everyone I finally got it to flash the FRESH rom, but once I rebooted it, it's still in the "HTC" branded screen. Is it loading? It's not going anywhere but this screen, although I know it's doing something because the animation shine is moving.
BOOGIE_BOTZ said:
Thanks for all the help everyone I finally got it to flash the FRESH rom, but once I rebooted it, it's still in the "HTC" branded screen. Is it loading? It's not going anywhere but this screen, although I know it's doing something because the animation shine is moving.
Click to expand...
Click to collapse
After flashing a new ROM, it can take up to 10 minutes or so to load.
Nice Everything is all good! Now my last question is how do I get the removed apps from the ROM back onto here? I actually prefer to have some of those programs back onto the phone.
BOOGIE_BOTZ said:
Nice Everything is all good! Now my last question is how do I get the removed apps from the ROM back onto here? I actually prefer to have some of those programs back onto the phone.
Click to expand...
Click to collapse
There is a link in the release notes to download all the removed apk's from Fresh Rom. You will then need to use adb push to push them back to /system/app. Search for how to setup adb on a mac as I honestly don't know.
Some simple (I hope) questions. Let's say I do a full CWM backup and copy the complete backup directory to my desktop. If I now want to change something inside this backup can I simply change the relevant .tar.a file(s), write their new checksums into nandroid.md5, copy everything back to the sd card and expect the whole thing to work?
No 2: I have just let the HD+ update itself to cm-10.1.3-ovation (final) and all went swimmingly. However, I saw that the update is not done incrementally, instead the whole zip is downloaded and the /system tree simply overwritten with its contents. I had put some bits and pieces into /system/app and /system/bin and modified a few files inside of /system, all of which changes were of course gone. So a better update strategy might be to download any new version from the CM website to a desktop machine, patch the .zip file there and then have CWM install it. Can CWM install such an update file like any other .zip or is the update.zip route the correct way?
Or perhaps the best way to update in such a scenario is to download the .zip, sync it with an existing CWM backup (as in the first question) and restore the backup?!
If you get the md5 sum right editing the tar should work.
You can edit the downloaded zip before you flash it and it will still install. But editing after install is about the same amount of work.
What I used to do on the Nook Color was to modify the gapps zip to add the /system changes I wanted and then reflashed the gapps every time I flashed a new ROM. That way gapps were refreshed and the new changes were inserted in /system. Or, you could make your own zip to flash only your changes. The easiest way to make one is to edit the gapps zip to put your changes in and then delete the gapps files from the zip.
Do these zip changes with archive software without totally unzipping and rezipping.
Edit: Since some of my changes were modifications to build.prop, I developed a script to edit the new ROM's build.prop on the fly as part of the zip. That way build date, etc stayed right. If you want, I can use PM to send you a copy of my old edited gapps for you to study. However, since you are on CM10.1 stable, you will probably not be updating again.
Sent from my Nook HD+ running CM10.1 on emmc.
> If you get the md5 sum right editing the tar should work.
Okay, thanks for the confirmation.
> You can edit the downloaded zip before you flash it and it will still install.
But how do I trigger that install, once in CWM? That was my 2nd question.
> But editing after install is about the same amount of work.
Not in my case as I have a) no MTP and b) can easily auto-sync huge directory trees with a powerful command line tool.
I think the best way forward is to ignore the installing of new install .zips via CWM, however this is done. Instead I'll produce a nandroid-compatible backup directory and "restore" that.
Thanks again for your help.
TooMuchSloeGin said:
> If you get the md5 sum right editing the tar should work.
Okay, thanks for the confirmation.
> You can edit the downloaded zip before you flash it and it will still install.
But how do I trigger that install, once in CWM? That was my 2nd question.
> But editing after install is about the same amount of work.
Not in my case as I have a) no MTP and b) can easily auto-sync huge directory trees with a powerful command line tool.
I think the best way forward is to ignore the installing of new install .zips via CWM, however this is done. Instead I'll produce a nandroid-compatible backup directory and "restore" that.
Thanks again for your help.
Click to expand...
Click to collapse
You don't trigger it, you manually boot to CWM and manually install it. Go to install zip from SD and choose where you put it.
And by editing after install, I meant editing /system once it is installed on the Nook.
Sent from my Nook HD+ running CM10.1 on emmc.
i have created a titanium flashable zip v7.1.2 and then flashed the zip using TWRP. Now i want to upgrade the app to v7.2.1.2. When i tried to install the apk it failed to update.
how am i supposed to upgrade the app now?
Try to make another zip and flash it
how to make flashable zip for that version?
sharathkumar said:
how to make flashable zip for that version?
Click to expand...
Click to collapse
I thought you said that YOU made a flashable zip and flashed it. Don't ask me I don't know.
GL
Why don't you just head over to Google Play store, then download and install TB from there?
There are 2 ways. First you make a flashable zip. It's funny that you don't know how to do that, if you've already did that, but the method is to drag&drop the APK into proper folder. However remember that before doing that it should have the exact same name as the older version. And don't try to rename it in the zip later, because the zip won't be flashable anymore.
2nd method is you uninstall old titanium Backup and install a new one.
Sent from Xperia Z2
Luckily not from an iPhone = Yesterdays technology at tomorrows prices
Hey there,
as the title say, I'm on 23.4.A.1.232 with SuperSu root and locked BL.
Today i got the message for a new system update -> 23.4.A.1.264
When i try to load an install it, i get a message "Xperia system Update couldn't be verified".
Does someone know how i can install it, without unroot. Or can someone send me the "update" files?
Thanks in advance
Edit: i think i maybe found the file, but i don't know how to open or convert...
The file is inside the zip and is called "update_package.update_package"
If you have Dualrecovery, download ftf file by Xperiafirm, convert it to zip with PRFCreator, of course adding supersu and dual recovery in zips
1 6 D said:
If you have Dualrecovery, download ftf file by Xperiafirm, convert it to zip with PRFCreator, of course adding supersu and dual recovery in zips
Click to expand...
Click to collapse
yeah, i want to avoid a new system install... I want to convert that update_package to a zip
If you will make this new zip and you will not wipe data in recovery, it will update all without loosing data. It could uninstall apps which you have made as system apps and delete all mods in system partition.
Already installed .264 but i still wanna know how to get that data from the crappy update_package.update_package... :silly:
Any ideas?
Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
DanHoliday said:
Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
Click to expand...
Click to collapse
You should upload your zip.
Thanks for the reply.
I've attached the original WiFi5GhzDisabler-v1(1).zip module downloaded from inside the Magisk app.
I've also attached WiFi5GhzDisabler-v1(1)-re-compressed.zip after downloading, extracting and re-compressing the original module it as described in my first post. I didn't make any changes to the files/folders themselves. I did notice they are different sizes (6.1KB original versus 8.6KB re-compressed).
I'm trying to learn more about the correct compression process/tool for these modules. I searched the forum and found a thread with a similar issue. Basically, the OP shared a .zip file that didn't work and another member did something and uploaded a "fixed" version with minimal insight into how it was done.
[HELP] This zip is not a Magisk Module
I would assume there isn't anything wrong with the files in the original module since it was probably reviewed before it was hosted in the Magisk app. It is also strange that the .zip file downloaded from the github repos for various modules don't work for me either, but that may be a separate issue.
Any ideas? The instructions do not include how to compress the module.
Take a close look at the original zip again, and compare it to the one you recompressed. You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Didgeridoohan said:
You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Click to expand...
Click to collapse
You're exactly right. I was incorrectly zipping the module folder itself rather than the files inside the folder. As you correctly pointed out, this creates a folder inside the zip that adds an extra layer between the files and the root of the zip.
Wow, what a simple mistake. With your help, the recompressed module installs fine now. I was able to install my own module too!
Thank you so much for your help. My issue has been resolved.