So I have ROM Manager, which I use to boot into ClockWork to do all of my Nandroid backups. I have been customizing my Vibrant with success so far. I would like to try new customizations without waiting for Finals. So I now have a update.zip file located at /SDcard now to boot into ClockWork without having to do it through ROM Manager in case my phone does not boot.
Usually I have been renaming my customizations to update.zip and loading them from /SDcard. My question is how does one apply update.zip's without moving the ClockWork update.zip located at /SDcard? I have renamed my customizations to update.zip, moved them to a different folder name, booted into ClockWork with it's update.zip, and have tried applying the customization update.zip's that are located somewhere other than /SDcard with no success. So how does one apply customizations without moving the CloclWorks update.zip from /SDcard?
Thanks.
Place whatever you want to install someplace else with a different name. Then select install from SD (I think that's it, not sure) and navigate to the file. It works exactly perfectly.
Sent from my SGH-T959 using XDA App
Thats what I was trying to do, but it would just freeze at the screen saying something like "searching for the update" or something like that. Dont' remember what it said exactly, but I was doing it that way. Not sure why it wouldn't install though... Unless there is a link to an updated ClockWork update.zip file?
While trying to use ClockWorkMod to install a update.zip from SDCard it freezes at "Finding update package..."
Any thoughts?
Nevermind. It was a bad download or corrupt file... downloaded same file, and it loaded perfectly. Close or delete this thread, thanks.
I'm getting an error when I try to install a .zip file through CWM recovery.
I get an error saying : E: Can't Open /sdcard/x (No such file or directory exists).
I've looked around and have learned that my best bet is to format my SD card. I can do that just fine, but I don't want to lose my data. I'm not flashing a ROM, it's just a custom lockscreen clock. If I format, I'll have to redo everything and lose all my data, apps, and system files (I'm running CM7 off of my SD card). But I need that for my zip to even be worth it.
I'm running a nightly build. Is there any possibility/plausibility that this could be a ROM-specific bug?
Is there any advice as to what I should do?
Thanks in advance.
SacTappingUni said:
I'm getting an error when I try to install a .zip file through CWM recovery.
I get an error saying : E: Can't Open /sdcard/x (No such file or directory exists).
I've looked around and have learned that my best bet is to format my SD card. I can do that just fine, but I don't want to lose my data. I'm not flashing a ROM, it's just a custom lockscreen clock. If I format, I'll have to redo everything and lose all my data, apps, and system files (I'm running CM7 off of my SD card). But I need that for my zip to even be worth it.
I'm running a nightly build. Is there any possibility/plausibility that this could be a ROM-specific bug?
Is there any advice as to what I should do?
Thanks in advance.
Click to expand...
Click to collapse
If you are running CM7 on SD you do not flash zips to it with ordinary CWM. Ordinary CWM will flash things to emmc. But maybe that is what you are trying to do. You do not say what you have on emmc.
If you want to flash the zip to the SD installation, make sure the zip file starts with update- and put it in the boot partition just like you do for roms. Then boot to SD recovery and the script will install it to SD.
An alternate way to flash things to SD installed CM7 is to use a special CWM modified for use on SD installs. You can read about and get it by looking at my tips thread linked in my signature. Item B5.
If you want to flash to emmc, make sure you are using an ordinary SD to put the zip on. Ordinary CWM always looks for partition one on the sd for the zip file. On your CM7 SD, the file is on partition 4 so CWM cannot find it.
So I'm trying to flash a new clock for my NC's unlock screen. The zip is called HoneyCombClock.zip. So do I just rename it to update.zip? That's not going to mess anything up?
Also yes, I booted into boot menu and selected emmc recovery. I thought that I needed to do CWM recovery.
I'll try the proposed method when I get a confirmation that it's not going to mess up my NC.
SacTappingUni said:
So I'm trying to flash a new clock for my NC's unlock screen. The zip is called HoneyCombClock.zip. So do I just rename it to update.zip? That's not going to mess anything up?
Also yes, I booted into boot menu and selected emmc recovery. I thought that I needed to do CWM recovery.
I'll try the proposed method when I get a confirmation that it's not going to mess up my NC.
Click to expand...
Click to collapse
You need to find out if it is a flashable zip... or if it is an app that has been zipped... I'm betting on the latter.
SacTappingUni said:
So I'm trying to flash a new clock for my NC's unlock screen. The zip is called HoneyCombClock.zip. So do I just rename it to update.zip? That's not going to mess anything up?
Also yes, I booted into boot menu and selected emmc recovery. I thought that I needed to do CWM recovery.
I'll try the proposed method when I get a confirmation that it's not going to mess up my NC.
Click to expand...
Click to collapse
If it is a flashable zip like Dizzy pointed out, you should rename to update-HoneyCombClock.zip. But I agree with Dizzy that it is probably a zipped apk file, not a flashable zip. Try looking at it with a zip program and see what you get.
It is indeed a flashable zip. I extracted it to make sure.
Also, I'm curious as to what you (leapinlar) meant when you instructed me to put the zip in the boot partition. From what I understand, that's the root of the SD card, right? Or has it changed?
SacTappingUni said:
It is indeed a flashable zip. I extracted it to make sure.
Also, I'm curious as to what you (leapinlar) meant when you instructed me to put the zip in the boot partition. From what I understand, that's the root of the SD card, right? Or has it changed?
Click to expand...
Click to collapse
Yes, it is what shows up on your PC when you take the card out of the nook and put it in the PC. Copy the zip there, rename it like I suggested above, put back in nook. When booting hold the n key until the boot menu comes up. Select SD and recovery and finish booting. The recovery script will install the zip.
I'm doing it and I'm not getting any errors, but when I boot into recovery, it runs through and shuts down without installing the zip. I don't understand what I could be doing wrong.
SacTappingUni said:
I'm doing it and I'm not getting any errors, but when I boot into recovery, it runs through and shuts down without installing the zip. I don't understand what I could be doing wrong.
Click to expand...
Click to collapse
And you renamed it like I said with update- on the front? (Don't forget the dash and no spaces.)
The file name is "update-HoneyCombClock". That should work right?
Sorry about these extended questions.
SacTappingUni said:
The file name is "update-HoneyCombClock". That should work right?
Sorry about these extended questions.
Click to expand...
Click to collapse
and .zip at the end?
It's automatically recognized as a zip file. If I put .zip at the end, it will show up on my tablet as "update-HoneyCombClock.zip.zip" Nevertheless, I'll try it and see what I get. I'll laugh if it works.
SacTappingUni said:
It's automatically recognized as a zip file. If I put .zip at the end, it will show up on my tablet as "update-HoneyCombClock.zip.zip" Nevertheless, I'll try it and see what I get. I'll laugh if it works.
Click to expand...
Click to collapse
Even if you get it flashing with your SD setup... it may not work if it requires honeycomb and you're running gingerbread.
It's meant for cm7. Here's a link to the thread I got the zip from: http://forum.xda-developers.com/showthread.php?t=959602
SacTappingUni said:
It's automatically recognized as a zip file. If I put .zip at the end, it will show up on my tablet as "update-HoneyCombClock.zip.zip" Nevertheless, I'll try it and see what I get. I'll laugh if it works.
Click to expand...
Click to collapse
What does the script say when it boots to SD recovery? Does it say install zip not found? And when you take it back out and look at it in the PC, is it still there? If it installed, the script will remove it. I know you can have your PC set to not show known extensions so it looks like it is missing. Temporarily disable that so you can really see the name. The script requires that it be named precisely, update- at the beginning, .zip at the end and no spaces.
The script doesn't mention any .zip installation. The zip file stays on my sd card root after recovery.
I just set my computer to show extensions. I'll retry the installation and make sure that every detail is perfect.
I remember doing something similar when I flashed a nightly on my nook. It was a .zip file. It wasn't flashing, so I looked around and got the impression that it would only instal if it had "update-" at the beginning. So I renamed it and it installed. I don't know what's up with my NC now. Is there any possibility that this could be a bug with the nightly? Or are installations not affected by ROM's.
SacTappingUni said:
The script doesn't mention any .zip installation. The zip file stays on my sd card root after recovery.
I just set my computer to show extensions. I'll retry the installation and make sure that every detail is perfect.
I remember doing something similar when I flashed a nightly on my nook. It was a .zip file. It wasn't flashing, so I looked around and got the impression that it would only instal if it had "update-" at the beginning. So I renamed it and it installed. I don't know what's up with my NC now. Is there any possibility that this could be a bug with the nightly? Or are installations not affected by ROM's.
Click to expand...
Click to collapse
No the existing rom will make no difference. It could be the zip itself. It has to be structured like a rom zip. It needs a /system directory with the files you want to flash. And it needs a META-INF folder with the script file buried in it. Where did you get the zip? Maybe I could look at it for you.
EDIT: I just downloaded and looked at it. It is just adding a single font to your /fonts folder. Nothing else. You can do that manually with root explorer. Just extract the font from the zip and copy to /system/fonts.
I got the zip from here: http://forum.xda-developers.com/showthread.php?t=959602
The clock can be flashed on any device with the following zip in recovery just like before.
http://www.mediafire.com/?b6xpw0pda671ujm
Click to expand...
Click to collapse
The zip has a font file and a meta-inf folder.
Look at my edit above
I replaced the file, but now I'm in an infinite bootloop.It just keeps doing the skateboarding android animation. Please tell me this isn't a problem with permissions. I don't know if I can even edit permissions now.
I am using an unlocked and rooted Nexus 4 and am attempting to install the battery display mod. I have downloaded the zip file to the phone but for some reason CWM (through recovery at boot) is not seeing the file. I have tried moving the file to various locations including the root directory of the sd card but CWM still cannot find it. I've performed this task a zillion times on other phones so I must be missing something real obvious.
Thoughts? Any help would be greatly appreciated!
bump........Anyone?
CWM will only show zip files. Did the file extension get messed up?
estallings15 said:
CWM will only show zip files. Did the file extension get messed up?
Click to expand...
Click to collapse
it is a *.zip extension!
ignore this thread.....problem solved......not sure why but file is now visible!!!???
So i'm trying to modify an image in framework-res.apk but every time I try to push in the new one I get stuck in bootloops and have to format. I have tried a bunch of ways of accomplishing this from using adb wirless to push to the framework folder, to using CWM to install it inside a zip file but they all just cause bootloops. Also I found that if I were to copy framework-res.apk to somewhere else and then not touch it and copy it back, it would still cause a bootloop! So basically the act of trying to replace the current apk is always causing bootloops. Anyone find a fix for this?
There is something wrong with the modification you make to the framework-res.apk which makes it corrupt. Normally, you can copy the file from SD card into /system/framework/ and the NST would just restart. Also mind the rermissions of the file, just make it the same as all the other files in that directory.
To save time when you brick your device, use noogie instead of format. Just copy the old framework-res.apk back in (you should previous make a back of it).
For modification, use the APK-Multi-Tool. This might help you avoid some problems with repackaging.
Hey guys, just wondering how I go about making a flashable zip? Basically I edited my build prop and now my phone wont turn on, I don't want to go and have to wipe my phone as that's just a huge mess about. I did a backup of my build prop and copied over to my computer before editing so I do have the original. I'm rooted with TWRP installed, I've tried to sort it through adb when connected in recovery but the driver wont install so that's not an option at the minute. As I have the original build prop I wanted to know if it's possible to make a flashable zip so I can just replace the broken file with the working one? Cheers guys.
Daley87 said:
Hey guys, just wondering how I go about making a flashable zip? Basically I edited my build prop and now my phone wont turn on, I don't want to go and have to wipe my phone as that's just a huge mess about. I did a backup of my build prop and copied over to my computer before editing so I do have the original. I'm rooted with TWRP installed, I've tried to sort it through adb when connected in recovery but the driver wont install so that's not an option at the minute. As I have the original build prop I wanted to know if it's possible to make a flashable zip so I can just replace the broken file with the working one? Cheers guys.
Click to expand...
Click to collapse
Pretty easy: Copy the unmodified build.prop file to an SD card. Put said card in the phone. Boot to TWRP. Mount both System and SD Card. Then go to ADVANCED and FILE MANAGER. From there you can rename the modified one in /system, copy the original file from the SD card, and then set its perms correctly.
Your phone should boot properly then.
Hope this helps!