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.
Related
Hi folks,
I have two mp3 files that I want to add to a zip file so that when I flash CM's latest nightly ROM, I can then flash this zip to add my two favourite audio files to their respective directories ie: Ringtones and Notifications.
Currently I push them usuing ADB but it would be nice to just have the zip file in the SDCARD and flash it at will. Little assistance?
TIA!
1) Download any update.zip for anything, unzip.
2) Google up "update-script", locate it in the zip.
3) Put your files in /system/media/notifications and /system/media/ringtones folders.
4) Change the update-script - googling it will tell you the instructions.
5) Zip back all the files, putting attention to keep the directory structure just as in original update.zip.
6) Google "sign zip apk", set up the environment to sign the ZIP, and sign it.
7) You're ready to flash.
To make it easier for you, I'm attaching update.zip I use for my own ringtones and notifications - so you'll only have to pack your relevant MP3s into the relevant folders. But you'll need to set up the signing environment - or use a recovery that bypasses verification completely (Amon_RA 1.8 and up).
Jack_R1 said:
- or use a recovery that bypasses verification completely (Amon_RA 1.8 and up).
Click to expand...
Click to collapse
Thanks for the tute. I have Amon's recovery so I will use your update zip.
Many thanks again for your reply.
Here's a tip I've been doing since my early days of rooting and rom'ing. I didn't want to do all the dumb adb steps (they're needed sometimes I know) for getting gapps and oc and build.prop edits..
I did this for internal install, but I suspect you can work it for the SD card as well if you know how.. also please make sure you copy the Froyo uImage file for the OC.
1: Download nokie froyo. Leave it zipped or unzip, its your choice
2: unzip the oc file and drag the uImage file into the correct folder (sorry I can't remember, if someone could post the correct location, ill update)
3: drag and drop the system folder from the gapps download into your nookie. You want to drag it to the area where you see the /system folder but not actually in it. It will automaticly place the sub folders.
3A: (optional) if you have a edited build.prop, you can copy and replace now.
4: (optional if you unzipped) zip the folder using the 'store' option for compression
5: flash using the same method you usually would through CWR
I used winRAR and just dragged and dropped, and it worked great. It automaticly compressed the files to match the destination folder. I recommend drag and drop because winRAR doesn't have a paste option.
You can also place and remove any apps in the system folder at this time. You can make the folder as large as you want with whatever apps you feel should be in the folder.
I personally think its a great way to skip a number of steps. By putting in the files and stuff you want and then flash it saves time.
***** WARNING****** using a high overclock your nook can't support will result in the end of the world... misplacing files can and will result in a non-booting nook... USE AT OWN RISK IF YOU DON'T KNOW WHAT YOUR DOING.... DON'T DO IT
I won't post my file because of two reasons:
1: nookie froyo is not mine and I will not take credit for anything that those people spent hours finely crafting
2: I think distributing files with gapps installed is wrong or something, I'm not too sure
CREDIT: to all the fine developers who slave hours to create awesome roms... THANKS!!!
Sent from one of those missing Droids
If you have an internal eMMC installation of Froyo and want an overclocked kernel then I'd recommend using my Clockwork Mod zip to install.
That's good to use if you have out already installed, but if you are putting the new version on, this is a lot easier. Just put what you want, then flash once
Sent from one of those missing Droids
I was able to install all the gapps correctly. Unfortunately I can't seem to connect to the google servers. I cleared the data and cache from the google framework app but had no success any ideas?
I've got a phone that may or may not be totally frakked due to careless build.prop modding and have been asked to try and recover it without wiping, OS flashing, or any other methods that could potentially lead to a wipe. ADB is a no-go, but I've got CWM access. I've never needed to make a CWM-flashable *.zip before, so I never learned how. I'm crunched for time and could really just use a break. Could somebody please put this build.prop into a CWM-flashable *.zip for me?
i new user, how i can upload my build prop
I would be extremely grateful!
Thanks in advance!
i must get 10 post.. jeez..
Hi, try to use Aroma File Manager. With it you can copy your new build.prop to the appropriate location.
To use the file manager, simply download it to your computer, copy it onto your phone through recovery and then when you are in recovery go for flash zip and choose the file you downloaded.
I found this site on how to root my Touchpad:
http://forum.xda-developers.com/showthread.php?t=1390829
and this one on how to install CM onto it:
http://chrisbryson.blogspot.com/2013/09/how-to-install-android-on-hp-touchpad.html
But nothing mentions when/how to install CWM (or one of the ones listed below) as shown on the CM nightly page found below
-PhilZ Clockworkmod 6.0.4.7 (non-touch)(will backup and restore in both cwm and twrp format)
-Milaq's ClockworkMod 6.0.5.4
-Flintman's TWRP
http://forum.xda-developers.com/showthread.php?t=2592909
At what place would I flash the Recovery?
To install android you will create a folder on the touchpad called cminstall.
This folder contains the three files needed to install android - moboot, cwm and whichever version of android you prefer. Optionally you can flash gapps from this folder too.
There are much better tutorials on the web and this site than the ones you quote - the first is irrelevant to installng android, and there are better ones here on xda than the second.
Also the recoveries you mention are for installing kitkat which requires repartitioning of the file system. Prob best to stick to JB for now
Cheers
chris5s said:
To install android you will create a folder on the touchpad called cminstall.
This folder contains the three files needed to install android - moboot, cwm and whichever version of android you prefer. Optionally you can flash gapps from this folder too.
There are much better tutorials on the web and this site than the ones you quote - the first is irrelevant to installng android, and there are better ones here on xda than the second.
Also the recoveries you mention are for installing kitkat which requires repartitioning of the file system. Prob best to stick to JB for now
Cheers
Click to expand...
Click to collapse
I found a tutorial here:
http://forum.xda-developers.com/showthread.php?t=2147284
But when I attempt to extract the Acme Installer - I downloaded ACMEInstaller5M - but when I try to extract with 7Zip to the Nova Directory it keeps giving me an error?
You don't need to extract the acmeinstaller file, just place it in Program Files/Palm, Inc, open up a terminal window and enter in the command to run it.
Of course, you do this after you have set up your cminstall folder on the touchpad.
A word of advice - I find it useful to have 2 copies of the rom you want to flash - one in the cminstall folder, and one in the root folder of the touchpad. This is because sometimes the flashing process with acme can be a bit funny, and it automatically deletes the files in cminstall once its done. I've flashed a couple of touchpads with acme and Android hasn't installed properly, so having a backup somewhere else on the touchpad is useful.
Cheers
jo15765 said:
I found a tutorial here:
http://forum.xda-developers.com/showthread.php?t=2147284
But when I attempt to extract the Acme Installer - I downloaded ACMEInstaller5M - but when I try to extract with 7Zip to the Nova Directory it keeps giving me an error?
Click to expand...
Click to collapse
It's been awhile since I have had to use acme but I believe it is a jar file so either use a different browser to download or change the file extension from (.zip to .jar).
Unfortunately I am not at my PC but can check later if someone else is unable to confirm this.
sstar said:
It's been awhile since I have had to use acme but I believe it is a jar file so either use a different browser to download or change the file extension from (.zip to .jar).
Unfortunately I am not at my PC but can check later if someone else is unable to confirm this.
Click to expand...
Click to collapse
Its not a .jar or .zip, use as is...
Cheers
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Statue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
-MaoR- said:
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Click to expand...
Click to collapse
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
pryerlee said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Ststue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
Click to expand...
Click to collapse
tetakpatak said:
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
Click to expand...
Click to collapse
Thanks guys.
I actually did flash CM 10.2 just before even seeing the your comments.
It worked great and now I actually think on staying with this ROM lol..
It's very clean and nice.
Thanks again!