Does anyone have a link to an empty .zip preferably with the correct file structure for SGSIII already there Of course it should work with CWM. I want to replace some files but it isnt working with my old update zip that i used for DHD.
thx in advance!
Or is there a simpler method of pushing files to you device?
Related
Hi all devs and xda people, since i cannot post on the dev forum i have to ask here...
[Q]: How Do i Install the New CWM without having xrecovery installed?
I just cleaned my phone by flashing it with SEUS, wich i normally do before i'm about to install a new rom, i just rooted my phone and installed the newest version of Root Explorer from market. Also have downloaded the CWM zip provided from the first post by D4rKn3sSyS at: http://forum.xda-developers.com/showthread.php?t=1106146
However, that zip contains two folders, not any single files that you just copied over to /system/bin like you did with xrecovery. so what am i suppsoed to do? wich files, where and what permission should they have?
CWM can be installed only manually using Root Explorer.
Extract files from bin folder in the zip and copy to respective folder with correct permissions (755).
It is missing one file (bin/charge) that can be found on xrecovery.zip file.
Another way is to install xRecovery Mini Pro .apk Unified Installer and after that use cwr_xrecinstall!
DanielFran said:
CWM can be installed only manually using Root Explorer.
Extract files from bin folder in the zip and copy to respective folder with correct permissions (755).
It is missing one file (bin/charge) that can be found on xrecovery.zip file.
Another way is to install xRecovery Mini Pro .apk Unified Installer and after that use cwr_xrecinstall!
Click to expand...
Click to collapse
Could you tell me exactly what file that is missing? the xRecovery-minipro-0.1.1beta contains three files: busybox, chargemon and xrecovery.tar
I could assume that its the busyboxfile that is missing, but i really dont want to chance and take a risk.
Hawake said:
Could you tell me exactly what file that is missing? the xRecovery-minipro-0.1.1beta contains three files: busybox, chargemon and xrecovery.tar
I could assume that its the busyboxfile that is missing, but i really dont want to chance and take a risk.
Click to expand...
Click to collapse
I believe it is missing bin/charger
Hi!
I want to update apk's on my phone and I wonder if I take out apks, edit them (yeah I remember to decompile and compile) and put them in a update.zip, move it to my SD-card, boot into recovery and choose apply sd-card: update.zip (or something like that), will the apk files in the zip folder update the apk's with the same name on my phone?
I want to update apk files by flashing. Can I do that by following what I wrote above?
Thanks in advance!
Regards,
Simen
It should work. But u need to give in zip info about direction (eg. System/app) and permissions (for system apps)
And i think that u should use install .zip from sd card (or similar) not update.zip
Look here: Create your own UPDATE.ZIP maybe it helps u
Sent using r800i with DoomKernel v11 (1.21ghz)
Hey Guys,
I'm in need of some really n00b friendly advice.
When you flash a new ROM (i.e. CM9) in CWM the tutorials tell you to flash the file named Update.zip. My problem is that I can't seem to find one in the zip file I downloaded for my xperia mini.
I downloaded FXP131, and found the zip file to contain a boot.img, which will be the kernel. And 2 other folders named META-INF and System.
I know how to flash the kernel and expect it was just left in there for easy transportation.
But where in the world is 'update.zip'?
Am I meant to unpackage the kernel then re-zip the META-INF and System folder and then call that 'Update.zip'?
I've flashed roms for some of my other devices before, but they've always used flashtool or samsungs flashtool.
Please help me guys, I don't like sounding this inexperienced
update.zip
I'm wondering if the ROM I am trying to flash needs to be renamed as update.zip in order to work. It is krook's v.6 of JB for the Lenovo K1 tablet. Since the download site has to distinguish between wifi and 3G versions, as well as nvflash versions there are a number of different filenames, however does it need to be renamed after putting it on my SD card?
Generally speaking "update.zip" is used as a generic name. For example the update.zip I just flashed is actually named "rascarlo_maguro_ota_2012-11-01.zip". When you flash a custom ROM in a custom recovery you should be able to browse & flash whichever file you need.
The FXP131.zip file that contains the boot.img and 2 other folders named META-INF and System is the "update.zip"
solved
My problem was an incomplete download. I compared file sizes, and checked md5sums and determined the correct ROM and it is now in the middle of finishing the upgrade/optimization process.
Thx
Hi,
The company Ainol release their latest updates as img files which we than have to flash using a program called livesuit. Does anyone know the process (or have any tips) on converting these img files to clockworkmod zip files?
I can extract the system and kernel files using something similar to this tutorial: http://www.techknow.t0xic.nl/forum/index.php?topic=1679.0
That tutorial explains how to modify the img file and then repack as img. I tried moving the system directory and the kernel & ramdisk over into a clockworkmod zip that i know works and overwrote the files in that with the one i had extracted.
when i try to install it, i get the e: cant open cwmzip.zip
(bad)
any ideas? Maybe i need to get the updater binary from the extracted files somehow?
Trugglepunts said:
Hi,
The company Ainol release their latest updates as img files which we than have to flash using a program called livesuit. Does anyone know the process (or have any tips) on converting these img files to clockworkmod zip files?
I can extract the system and kernel files using something similar to this tutorial: http://www.techknow.t0xic.nl/forum/index.php?topic=1679.0
That tutorial explains how to modify the img file and then repack as img. I tried moving the system directory and the kernel & ramdisk over into a clockworkmod zip that i know works and overwrote the files in that with the one i had extracted.
when i try to install it, i get the e: cant open cwmzip.zip
(bad)
any ideas? Maybe i need to get the updater binary from the extracted files somehow?
Click to expand...
Click to collapse
It really all depends, how many images? What are the images called? What are in each of the images if there is more then one?
thanks for replying, i think i have it right. I ran a log and saw that there was an invalid filename in my zip and sure enough, i looked in the app folder and saw a file with a lot of chinese characters. Deleting this file has sorted this problem
Thanks for replying anyways!
I have CM 10.1.3 installed on my i9100 and I flashed the ZIP file from the thread at the bottom of this post through CWM Recovery. Now, my phone is stuck at the boot screen.
I would realllly hate to reinstall my ROM and all apps, so I'd just like to fix the problem. The ZIP makes changes to the 'SurfaceFlinger' library. Could I reflash a ZIP of the original library? Any idea how I could get the file?
surfaceflinger-fix.zip
http://forum.xda-developers.com/galaxy-nexus/development/fix-lag-fix-cm10-based-roms-cm10-t1875490
SOLUTION:
The only file that surfaceflinger-fix.zip affects is libsurfaceflinger.so. So, I tried extracting this file from a copy of the CM 10.1 zip file. libsurfaceflinger.so is located in system/lib. I then created a flashable ZIP using this guide:
http://forum.xda-developers.com/showthread.php?t=2163974
I flashed the ZIP after pushing it via 'ADB push sample.zip /sdcard'. I installed the ZIP via CWM Recovery. Clear caches, reboot. STILL DIDN"T WORK.
So then I took a look a look in the META-INF folder of surfaceflinger-fix.zip and noticed some additional files that I did not have in my custom 'sample.zip'. So, I just took the libsurfaceflinger.so file that I extracted from CM 10.1 and put this file in surfaceflinger-fix.zip, replacing the original one in the ZIP file. Pushed this ZIP via ADB, everything works.
Had you taken a backup prior to flashing the zip it would've been five minutes work fixing your problem, I'm sure there's a lesson for all of us there.
ghostofcain said:
Had you taken a backup prior to flashing the zip it would've been five minutes work fixing your problem, I'm sure there's a lesson for all of us there.
Click to expand...
Click to collapse
This was definitely easier and this is a better fix than using a backup, but I absolutely agree with you.