Replacing/updating files in ROM update zip - Android Q&A, Help & Troubleshooting

Quick scenario: I am working on a Nook Simple Touch UK ROM zip (now obsolete), trying to get from it the essentials that make it "UK" and move them into/replace similar files (mostly images and documents, but maybe one or two system apps) to the current US version of the ROM so that everything will function properly, but the ROM will have the look and feel (and localization options) of the obsolete UK ROM. There's not a lot to change.
The zips don't open for inspection properly in anything I've tried except 7zip. I can move/overwrite files from one ROM to the other, but there does seem to be a slight compression going on and I have no idea how to stop this. In WinRAR I could, but I don't see any similar option in 7zip. Then the zip contents go into a CWM flashable zip.
Preparing the CWM zip with no changes to the current US ROM gives an error-free flash and a functioning result. But if I change even one file (like the boot splash screen--same name, same file size--until moved), the flash fails almost immediately.
I asked someone about internal checksums before ROMs would install but they did not think there were any on these ROMs. Now I wonder. I don't see anything that looks like a checksum or even a "to do" list.
Have I missed some fundamental step or am I using my tools incorrectly (or the wrong tools)? One last thought, these are "update" zips, if that makes any difference, so on their own they would not wipe user data,for example.
Edit: I think I've got it!
1. Unzip (not just "open") both zips with WinRAR (7zip would not extract the update zips for me)
2. Drag alternate versions of files from one folder to the other
3. Zip up with 7zip
4. Open CWM update zip (just has META-INF folder) and ROM update zip with 7zip
5. Drag contents of ROM update zip to CWM zip.
6. Copy new CWM zip to CWM card and flash.
7. SMILE!

nmyshkin said:
Quick scenario: I am working on a Nook Simple Touch UK ROM zip (now obsolete), trying to get from it the essentials that make it "UK" and move them into/replace similar files (mostly images and documents, but maybe one or two system apps) to the current US version of the ROM so that everything will function properly, but the ROM will have the look and feel (and localization options) of the obsolete UK ROM. There's not a lot to change.
The zips don't open for inspection properly in anything I've tried except 7zip. I can move/overwrite files from one ROM to the other, but there does seem to be a slight compression going on and I have no idea how to stop this. In WinRAR I could, but I don't see any similar option in 7zip. Then the zip contents go into a CWM flashable zip.
Preparing the CWM zip with no changes to the current US ROM gives an error-free flash and a functioning result. But if I change even one file (like the boot splash screen--same name, same file size--until moved), the flash fails almost immediately.
I asked someone about internal checksums before ROMs would install but they did not think there were any on these ROMs. Now I wonder. I don't see anything that looks like a checksum or even a "to do" list.
Have I missed some fundamental step or am I using my tools incorrectly (or the wrong tools)? One last thought, these are "update" zips, if that makes any difference, so on their own they would not wipe user data,for example.
Edit: I think I've got it!
1. Unzip (not just "open") both zips with WinRAR (7zip would not extract the update zips for me)
2. Drag alternate versions of files from one folder to the other
3. Zip up with 7zip
4. Open CWM update zip (just has META-INF folder) and ROM update zip with 7zip
5. Drag contents of ROM update zip to CWM zip.
6. Copy new CWM zip to CWM card and flash.
7. SMILE!
Click to expand...
Click to collapse
Nice job!

Related

[Q] AHH!! failed

I got clockworkmod working fine, but I am unable to loan ROMs. Whenever I downloand a ROM it opens in muiltiple files and it also happens with TNT, Thi is where Im stuck
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped, Clockwork will install it from the .zip file as is). trying to get VEGan 5.1 final
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
I cant fiqure how to get the update.zip. When I do open the files i get 3 files
META_INF,boot, and system. I tried to copy and paste all three files in the ROMs, but it never show the update.zip
You don't need an update.zip with clockworkmod recovery... you just need the rom that is zipped and can be named anything.
Stop unzipping the rom you are downloading and just copy it to your device. Install that with clockworkmod recovery.
Sent from my Viewsonic 10" GTab...
novicexda said:
I got clockworkmod working fine, but I am unable to loan ROMs. Whenever I downloand a ROM it opens in muiltiple files and it also happens with TNT, Thi is where Im stuck
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped]/B], Clockwork will install it from the .zip file as is). trying to get VEGan 5.1 final
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
I cant fiqure how to get the update.zip. When I do open the files i get 3 files
META_INF,boot, and system. I tried to copy and paste all three files in the ROMs, but it never show the update.zip
Click to expand...
Click to collapse
you've answered your own question, the rar or zip file you downloaded might be in diff names, but always leave it in zip format. if in rar, unrar and the zip file should be in it.
in clockwork recovery, you can update by update.zip or choose your own zip
tcrews said:
You don't need an update.zip with clockworkmod recovery... you just need the rom that is zipped and can be named anything.
Stop unzipping the rom you are downloading and just copy it to your device. Install that with clockworkmod recovery.
Sent from my Viewsonic 10" GTab...
Click to expand...
Click to collapse
That is my problem, if automaticly unzips when it downloads. I am not sure if its my windows setting becaue I am unable to download TNT lite because I keep getting " windows can no opem" message. Is there a way i can prevent it from unzipping? Thanks BTW
maybe use a diff browser to download or right click on link and "save as"
You might be hitting open instead of save ...
down load it direct to your Gtab
Download the file directly to your tab. Use ES file explorer to move it to your SD card if necessary. Reboot in to clock work - choose file from SD card-select it and install.

Devoid.Franco Kernel 14

Been using Franco's Rom and Kernel and it's been great. However, I like to update to his v.14 kernel. I did the format
1. Wipe
2. Partition, etc...
3. Load v5 Rom
4. Restart
My problem is right here, the warning is to delete the tweaks file and the script file (which I don't have one) in File Manager. I use the OI manager that comes with v5 Rom but it just wont' delete, and I don't want to load the new kernel because of all the warnings, please help :-(...
calculus1918 said:
Been using Franco's Rom and Kernel and it's been great. However, I like to update to his v.14 kernel. I did the format
1. Wipe
2. Partition, etc...
3. Load v5 Rom
4. Restart
My problem is right here, the warning is to delete the tweaks file and the script file (which I don't have one) in File Manager. I use the OI manager that comes with v5 Rom but it just wont' delete, and I don't want to load the new kernel because of all the warnings, please help :-(...
Click to expand...
Click to collapse
it wont delete cause of permissions. I use root explorer for this kind of work. In this particular case i had deleted the nececary scrips from the flash zip and i flashed afterwards. (i had a clean install)
I am trying the clean install as well, can you give the instructions or point me to somewhere where I can read more about this, thanks for your time and effort.
Do I just delete it in the Devoid.Franco v5 zip before flashing and then restart the process (the only file that I can find is tweaks.sh)
Sorry, found the init.d file as well. Would I delete those files in the zip, rezip and then start the process over?
you just delete them from the zip and you flash it as usuall. just dont forget to disable verification check on your recovery or else it will give you error
Sorry, just a newb when it comes to this.
I couldn't delete the two files from the devoid.franco.v5.zip file so I did the following:
1. Extract the zip file
2. Deleted the two files
3. Rezipped the files into a new devoid.franco.v5.zip
4. Load the zip into the micro sd card after all the wipe and partition
5. Disabled Signature check
6. Tried the flash and it said it can't open the zip because it's bad :-(...
This can't be that hard when all the other kernels was easy to install...
calculus1918 said:
Sorry, just a newb when it comes to this.
I couldn't delete the two files from the devoid.franco.v5.zip file so I did the following:
1. Extract the zip file
2. Deleted the two files
3. Rezipped the files into a new devoid.franco.v5.zip
4. Load the zip into the micro sd card after all the wipe and partition
5. Disabled Signature check
6. Tried the flash and it said it can't open the zip because it's bad :-(...
This can't be that hard when all the other kernels was easy to install...
Click to expand...
Click to collapse
Extracting a zip and re-zipping it DOESN'T work. You are not supposed to unzip the file. Just flash the rom, delete the offending files using root explorer, and then flash the kernel.
Sent from my LG Optimus One P500 using XDA App
You should't extract the file and rezip it. It corrupts it when it comes to flashing. I personally browse the zip file with winrar and simple delete the files i need. I also add files to zip this way like apks, ringtones etc
Trying winrar and it seems to work, gone to see if I can finish the entire process. Thanks so much for your time again. In the future, can I send the apps that I want directly into this zip? I can to sue something zipsigner before to get calendar, etc... Thanks again!!!
An alternative way for a clean install:
1: wipe everything
2: flash devoid.franco.v5
3: reboot (to check if everything is ok)
4: reboot into recovery
5: mount /system partition under 'mounts and storage' (clockworkmod)
6: from pc type (with phone still in recovery): 'adb shell'
7: in adb shell, type: 'rm /system/etc/tweaks.sh'
8: in adb shell, type: 'rm /system/etc/init.d/00script'
9: flash franco.kernel.v14
10: reboot
I Hope it helps,
Bye
You're welcome m8.
And yes you can have the apps you want inside the rom this way very easilly. just put them in app folder. I did this with some removed apps like browser and calendar and also removed zeam launcher and used adw launcher (personal taste) I even tried that with frameworks (aka themes) and it worked great
Thanks so much to both of your posts, it's working. One last questions, thought setcpu was already implemented in this kernel, but I don't see it anywhere? Again, thanks again for everyone's time and effort, learned so much today (wife is mad though because we need to do house work, lol, lol, better get going)... She said, "who formats their phone 5 times in 1 month, lol, lol"
setcpu is NOT included, you have to install it.
See first post in franco.kernel thread for the link.
Eh! eh! you are not in Europe, I guess if you have to help your wife NOW!!!
Barcelona-ManchesterUTD right NOW...
oh yes the wifes. my gf gets fustrated like "wtf are roms and kernels?? its just a phone!!! you call people and they call you back" rofl
One last note on setcpu. When i was using last version (2.13), every time i rebooted my phone the settings where gone and had to set them again. I switched to v2.1 and it worked like a charm. Have no idea if that is general issue or only me had it. Just thought i should tell you
Done via editing the zip with rar and all worked smoothly.
Thx all
/W

ROMs dont have an update.zip

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

How to sign zips with md5 to flash it with recovery

This is not for noobs or any jackasses who only read others.
As you all know,installing a custom ROM requires data like md5,recovery image and similar extensioned files.They are all packed in a zip package.But not just any zip package.After you generated the other files,zip it normally and flash it,it won't work.You know that the famous update.zips are always signed zips?We'll show you how to do this properly and easy.
First,you must have files like we said above.We don't care where do you get those files.Then,download "ES File Explorer" from Play Store.Hold and select those files after you got into the app.(You also need to know where those files are.For example Download or Android)Click the three dots icon under the screen and choose "Compress".Name the zip file and let it compress.After it is finished,choose"Add"and choose File.Name it update.zip.After that,download another app from Play Store called "Zip Signer".Open it,select the input file is the zip which isn't update.zip.Then select update.zip as output file,choose "Sign" or whatever.Wait until it's finished.Then boot into recovery mode.If you use TWRP,go to Install>choose update.zip and flash.If you don't have any custom recovery,first wipe cache partition>install zip from sdcard and go until you find update.zip.Install it and reboot your phone!Done!

How to create flashable zip from system.img?

I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Just off the subject slightly...but Eliminater74 already has a flashable zip (thought TWRP) for the 20J release. Its a 2 Part System.
Eliminator74's zip is modified. I want to take a 100% pure stock system.img (extracted from stock firmware) and put it into a zip that can be flashed in TWRP. When I say stock, that's what I mean. No root, no Xposed, no BusyBox, nothing. This has already been done for Lollipop on the v10, but I have MM. I have already explained why I want to do this. I'm currently looking into whether Superr's Kitchen can accomplish this.
He has a Fully Stock 20J release..just gotta read the thread..
AnonVendetta said:
I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Click to expand...
Click to collapse
What tool did you use to extract the KDZ? I am trying to get a stock boot.img for the H901J build and I cannot seem to find it. I used the WindowsLGFirmwareExtract 1.2.5.0 release and all I see are a ton of .bin files and system.img. Is boot.img inside system.img?
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
AnonVendetta said:
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
Click to expand...
Click to collapse
It's been a while from this post... But I'm looking after the same goal you were and got the same error 6 trying the same things you described in your previous posts. Despite of these long 4 years, let me try: did you finally achieve to make the flashable zip with system.img?
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
AnonVendetta said:
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
Click to expand...
Click to collapse
Thank you for your reply. My device is Lenovo Z6 Pro but I thought this wouldn't make a difference.
Just to be sure, what you get with SuperR's Kitchen is a zip including system.img file and not the /system folder, right? Thank you in advance.
Edit: I had tried with other kitchen softwares with no success but SuperR's Kitchen did the job as you said, like a charm. Tons of thanks.
@descarao81: No, SuperR's Kitchen does not include system.img/boot.img, you must provide them yourself. They are device-specific. And system.img is a very large file, so it cannot reasonably be included in the Kitchen zip.
Yeah, maybe I wasn't clear, I meant if the resultant zip would include those raw image files being the original image files provided by the user. It's clear now. Thank you.
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Upytry2 said:
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Click to expand...
Click to collapse
Trying that exactly when im home! Thank you!

Categories

Resources