Related
REQUIREMENTS:
- any file that you want to replace or add to your phone;
- an existing cwm flashable zip file to use as a base - I've attached one below;
- 7-zip;
- Notepad++.
STEPS:
DIRECTORY STRUCTURE:
(1) Download and place the sample.zip anywhere on your desktop;
(2) Right-click on it and choose: "7-Zip / Open archive" [*DO NOT extract; just *Open archive*];
Now you should see two folders: one called "system" and one called "META-INF".
I - FILES AND FOLDERS:
Let's start with the "system" one, so double-click on it:
In there, will go all files that what you want to add or replace to the system. So let's say for example that you want to replace the bootanimation and bootsound. To do so, we have to create sub-directories in the /system/ folder by following this easy method:
- On your desktop, right-click on an empty spot and select "New / Folder" then edit the name to "etc" (no " ") using no CAPS or space at the end;
- repeat the process to make another folder called "media";
- drag those two new empty folders into the /system/ folder of the 7-zip opened archive [just click yes on the popup dialogs];
- now simply drop the two files in their respective place: the sanim.zip file should go in '/system/media' folder and the PowerOn.wav into '/system/etc' folder.
.. If you have more files to add, just follow the logic above; I'm sure you get the idea by now..
/system/app - all the system apps (SystemUI.apk etc)
/system/framework/ -framework-res.apk, twframework-res.apk, android.policy.jar
/system/etc - vold.fstab, PowerOn.wav(bootsound)
/system/media - sanim.zip (bootanimation) (only for custom ROMs)
/system/lib - libraries (*.so)
II - UDATER-SCRIPT
The other folder included in the opened archive is named "META-INF" and all the file in it should be left unchanged.
That's it !!
Congratulations you've done your first CWM patch !!!
NOTE: Always backup your existing system file that you are going to replace by the patch(zip).
Good Guide!!
There are many more here. Check them
EDIT: Added your Post there. As CWM Flashable Zip Guide.
Hope you are Fine with it.
Thnx so much pankaj.........
Great guide man awesome, thanks!
I've got some questions which I believe you can answer:
1. I come from another device's forum [SAMSUNG Galaxy S II I9100] so I'm not sure, will this method work with any device, or at least with mine?
2. What I'm trying to do is to take the nandroid backup I made for the ROM my device is currently running (whole ROM, along with all the MODs, themes & changes I have on it) and convert it into a CWM flashable .zip file, so:
A. Is this even possible with this method?
B. If it is, just to verify that I got it all right up until now: I decompress the 'system.ext4.tar' file from the nandroid' backup folder and then I push the decompressed system folder into the 'sample.zip' file that I've downloaded from this thread, right?
3. I know for a fact (correct me, if I'm wrong) that a nandroid backup doesn't include a backup of the modem (at least not in my device), so how do I add my currently installed modem to the .zip file?
4. What about the recovery and bootloader, how do I add them?
5. What about "cache.ext4.tar" & "data.ext4.tar", are they necessary in any way?
Itzik68 said:
Great guide man awesome, thanks!
I've got some questions which I believe you can answer:
1. I come from another device's forum [SAMSUNG Galaxy S II I9100] so I'm not sure, will this method work with any device, or at least with mine?
2. What I'm trying to do is to take the nandroid backup I made for the ROM my device is currently running (whole ROM, along with all the MODs, themes & changes I have on it) and convert it into a CWM flashable .zip file, so:
A. Is this even possible with this method?
B. If it is, just to verify that I got it all right up until now: I decompress the 'system.ext4.tar' file from the nandroid' backup folder and then I push the decompressed system folder into the 'sample.zip' file that I've downloaded from this thread, right?
3. I know for a fact (correct me, if I'm wrong) that a nandroid backup doesn't include a backup of the modem (at least not in my device), so how do I add my currently installed modem to the .zip file?
4. What about the recovery and bootloader, how do I add them?
5. What about "cache.ext4.tar" & "data.ext4.tar", are they necessary in any way?
Click to expand...
Click to collapse
(1) This method will work with any device as long as the device has custom recovery (CWM).
(2) a. yes, it is possible
b. decompress system.ext4.tar and push all the files/folders in the system folder to the system folder in the sample.zip
You must add the line in BOLD/italic to the META-INF/com/google/android/updater-script file
Code:
run_program("/sbin/busybox", "mount", "/system");
[B][I]delete_recursive("/system");[/I][/B]
package_extract_dir("system", "/system");
This line has to be added only when you want to replace all the system files/folders
otherwise no need to add.
drag updater-script from sample.zip (open via 7zip, do not extract) to the desktop, make modifications, save & then push it back to the same locations in sample.zip
(3) To include modem.bin :
first drag modem.bin & this file to sample.zip
now the directory structure of sample.zip is as follows
FOLDERS - system, META-INF
FILES - modem.bin, flash_image
add following lines to the META-INF/com/google/android/updater-script file
Code:
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
ui_print("Installing modem...");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p7", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
delete("/tmp/flash_image");
(4) Don't know about bootloader, but for recovery, similar step as above:
drag recovery.img to sample.zip
add these lines to updater-script
Code:
package_extract_file("recovery.img", "/tmp/recovery.img");
run_program("/sbin/busybox", "dd", "if=/dev/zero", "of=/dev/block/mmcblk0p8");
run_program("/sbin/busybox", "dd", "if=/tmp/recovery.img", "of=/dev/block/mmcblk0p8");
run_program("/sbin/busybox", "sync");
run_program("/sbin/busybox", "rm", "-f", "/tmp/recovery.img");
(5) No these files are not needed.
Thanks man, you're awesome!!!
I still have several questions though:
pankaj88 said:
b. decompress system.ext4.tar and push all the files/folders in the system folder to the system folder in the sample.zip
You must add the line in BOLD/italic to the META-INF/com/google/android/updater-script file
Code:
run_program("/sbin/busybox", "mount", "/system");
[B][I]delete_recursive("/system");[/I][/B]
package_extract_dir("system", "/system");
This line has to be added only when you want to replace all the system files/folders
otherwise no need to add.
drag updater-script from sample.zip (open via 7zip, do not extract) to the desktop, make modifications, save & then push it back to the same locations in sample.zip
Click to expand...
Click to collapse
OK, puling / pushing files / folders from / to the .zip / .tar files is no problem, but I don't really get the part with this: "updater-script" file...
1. Let's say I've pulled it:
A. What is this file?
B. How can I open and edit it?
C. You say to add those code lines, but I'm guessing there are already several other code lines in it, where do I add those line? Above something else? Below it? Where?
2. Except for this: "updater-script" file, there are also:
META-INF\CERT.RSA
META-INF\CERT.SF
META-INF\MANIFEST.MF
META-INF\com\google\android\update-binary
A. What about those, what are they?
B. Don't they need to be changed as well?
I have more questions about the other parts of your answer, but for now let's live it at that.
I'm really sorry I'm bugging you, but I really like to understand what I'm doing before doing it...
Itzik68 said:
Thanks man, you're awesome!!!
I still have several questions though:OK, puling / pushing files / folders from / to the .zip / .tar files is no problem, but I don't really get the part with this: "updater-script" file...
1. Let's say I've pulled it:
A. What is this file?
B. How can I open and edit it?
C. You say to add those code lines, but I'm guessing there are already several other code lines in it, where do I add those line? Above something else? Below it? Where?
2. Except for this: "updater-script" file, there are also:
META-INF\CERT.RSA
META-INF\CERT.SF
META-INF\MANIFEST.MF
META-INF\com\google\android\update-binary
A. What about those, what are they?
B. Don't they need to be changed as well?
I have more questions about the other parts of your answer, but for now let's live it at that.
I'm really sorry I'm bugging you, but I really like to understand what I'm doing before doing it...
Click to expand...
Click to collapse
(1) It is updater-script file.
CWM flashes the zip file according to the steps mentioned in this file.
lets say
updater-script contains following lines:
Code:
ui_print("| Writing System |");
run_program("/sbin/busybox", "mount", "/system");
delete_recursive("/system");
package_extract_dir("system", "/system");
Explanation of all the lines:
first line just print "Writing System"
next, mounts system partition so that files can be copied to it
deletes system folder
extract the system folder in the sample.zip to the device system partition
I hope now you have understand what updater-script is all about
You can use notepad++ to edit this file
(2) All the other files should be left as they are. No need to edit those files.
But their presence is necessary in the sample.zip
(these files serve as signature of the zip file)
Download this updater-script file to study more code.
OK, so now my "updater-script" file is looking like that:
Code:
ui_print("SAMPLE CWM FLASHABLE PACKAGE");
run_program("/sbin/busybox", "mount", "/system");
delete_recursive("/system");
package_extract_dir("system", "/system");
run_program("/sbin/busybox", "umount", "/system");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
ui_print("Installing modem...");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p7", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
delete("/tmp/flash_image");
Is that right so far?
Itzik68 said:
OK, so now my "updater-script" file is looking like that:
Code:
ui_print("SAMPLE CWM FLASHABLE PACKAGE");
run_program("/sbin/busybox", "mount", "/system");
delete_recursive("/system");
package_extract_dir("system", "/system");
run_program("/sbin/busybox", "umount", "/system");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
ui_print("Installing modem...");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p7", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
delete("/tmp/flash_image");
Is that right so far?
Click to expand...
Click to collapse
you should study the updater-script file, the link for which I provided in the last reply.
Code:
run_program("/sbin/busybox", "umount", "/system");
this line should come at the last when all the copying & flashing has been done.
It unmount the system partition.
Also you need to set permissions & create symbolic links.
I suggest you to study the updater script file first.
If you found any problem, post here.
pankaj88 said:
you should study the updater-script file, the link for which I provided in the last reply.
Code:
run_program("/sbin/busybox", "umount", "/system");
this line should come at the last when all the copying & flashing has been done.
It unmount the system partition.
Also you need to set permissions & create symbolic links.
I suggest you to study the updater script file first.
If you found any problem, post here.
Click to expand...
Click to collapse
what are symbolic links for? i have studied the updater script you posted.. and did some on my custom rom, both have many symbolic links, what it is for? is it necessary? or just for custom roms?
draiyan said:
what are symbolic links for? i have studied the updater script you posted.. and did some on my custom rom, both have many symbolic links, what it is for? is it necessary? or just for custom roms?
Click to expand...
Click to collapse
for understanding what symbolic links are:
http://en.m.wikipedia.org/wiki/Symbolic_link
it is necessary to have symbolic links for every ROM that you are going to flash via CWM.
Sent from my GT-I9103 using xda app-developers app
pankaj88 said:
- On your desktop, right-click on an empty spot and select "New / Folder" then edit the name to "etc" (no " ") using no CAPS or space at the end;
- repeat the process to make another folder called "media";
- drag those two new empty folders into the /system/ folder of the 7-zip opened archive [just click yes on the popup dialogs];
- now simply drop the two files in their respective place: the sanim.zip file should go in '/system/media' folder and the PowerOn.wav into '/system/etc' folder.
.. If you have more files to add, just follow the logic above; I'm sure you get the idea by now..
/system/app - all the system apps (SystemUI.apk etc)
II - UDATER-SCRIPT
The other folder included in the opened archive is named "META-INF" and all the file in it should be left unchanged.
Click to expand...
Click to collapse
So i followed these steps with Phone.apk. Made an "app" folder inside the already existing "system" folder. moved my modified "Phone.apk" inside that folder. put on SD card, reboot recovery, choose to install from zip, choose correct zip, and get...
Error: in /sample.zip
(Status 0)
Installation aborted
Any idea. those are my exact steps, i left nothing out.
baldypal said:
So i followed these steps with Phone.apk. Made an "app" folder inside the already existing "system" folder. moved my modified "Phone.apk" inside that folder. put on SD card, reboot recovery, choose to install from zip, choose correct zip, and get...
Error: in /sample.zip
(Status 0)
Installation aborted
Any idea. those are my exact steps, i left nothing out.
Click to expand...
Click to collapse
Try do Mount/System and then flash it. Still if u get some prob, please attach ur cwm zip. Will try to help u buddy.
baldypal said:
So i followed these steps with Phone.apk. Made an "app" folder inside the already existing "system" folder. moved my modified "Phone.apk" inside that folder. put on SD card, reboot recovery, choose to install from zip, choose correct zip, and get...
Error: in /sample.zip
(Status 0)
Installation aborted
Any idea. those are my exact steps, i left nothing out.
Click to expand...
Click to collapse
Do not extract the zip file.
Use "7zip" to open it & make a new folder named as "app" inside the system directory.
Also mount /system in CWM recovery.
Has anyone succeeded in making an update.zip for our device that can be flashed through stock recovery? If yes how to make one?
OK the "mount /system in CWM recovery" is did not do. I did not extract the files. I did use 7zip.
Sent from my Galaxy Nexus
Had the chance to try this last night. Mount /system in CWM didn't allow it either. Same error.
Sent from my Galaxy Nexus using xda app-developers app
I will upload a cwm zip with modified updater script soon.
Sent from my GT-I9103 using xda app-developers app
OP updated with modified "sample.zip".
Thanks !!
somehow i got "installatin aborted"
Hi!
I have a problem with my update.zip. Now my zip file has a jar file, xml file, and an apk file. in meta-inf folder : com/android/google/ updater-binary and updater-script. I copied the updater-binary from other rom for my device. Now, I wanna put my jar file to system/framework, put the xml file to system/etc/premissions and put the apk file to data/app. I wrote script but it only puts jar file to system/framework, not all files.
I flashed it in all recoveries, no abort. so how to fix ?
here is my updater-script file :
Code:
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("com.playstation.playstationcertified.xml", "system/etc/premissions");
package_extract_file("com.playstation.playstationcertified.jar", "/system/framework");
mount("yaffs2", "MTD", "userdata", "/data");
package_extract_file("psmobile.apk", "data/app");
ui_print("message");
ui_print("message");
yashade2001 said:
Hi!
I have a problem with my update.zip. Now my zip file has a jar file, xml file, and an apk file. in meta-inf folder : com/android/google/ updater-binary and updater-script. I copied the updater-binary from other rom for my device. Now, I wanna put my jar file to system/framework, put the xml file to system/etc/premissions and put the apk file to data/app. I wrote script but it only puts jar file to system/framework, not all files.
I flashed it in all recoveries, no abort. so how to fix ?
here is my updater-script file :
Code:
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("com.playstation.playstationcertified.xml", "system/etc/premissions");
package_extract_file("com.playstation.playstationcertified.jar", "/system/framework");
mount("yaffs2", "MTD", "userdata", "/data");
package_extract_file("psmobile.apk", "data/app");
ui_print("message");
ui_print("message");
Click to expand...
Click to collapse
You should add your recovery mount points too!!! or you want to just download a CWM flashable zip files from one of the forum
Techix18 said:
You should add your recovery mount points too!!! or you want to just download a CWM flashable zip files from one of the forum
Click to expand...
Click to collapse
What and how?
Galaxy Nexus cihazımdan Tapatalk 4 ile gönderildi
yashade2001 said:
What and how?
Galaxy Nexus cihazımdan Tapatalk 4 ile gönderildi
Click to expand...
Click to collapse
First download a custom rom for your device then open the updater script.The updater script will show a line called format('ext4'...... Dev block/.......) which is actually for your device recovery mount points and write the line in your own updater script with the reference of the other updater script.
Click Thanks if i helped!
Techix18 said:
First download a custom rom for your device then open the updater script.The updater script will show a line called format('ext4'...... Dev block/.......) which is actually for your device recovery mount points and write the line in your own updater script with the reference of the other updater script.
Click Thanks if i helped!
Click to expand...
Click to collapse
Ok i do that everytime. But i wanna make UNIVERSAL update. Zips.
Sent from my Galaxy Nexus using Tapatalk 4.
yashade2001 said:
Ok i do that everytime. But i wanna make UNIVERSAL update. Zips.
Sent from my Galaxy Nexus using Tapatalk 4.
Click to expand...
Click to collapse
If you want to make update zips,i suggest you to go download the flashable zip in XDA forums becuase those flashable zips support anything
Click Thanks if i helped!
As we know, Cyanogenmod has released official nightlies for the Samsung Galaxy S5 Sprint (or kltespr in their words). I tried to flash the latest nightly and it fails with the statement "This is for kltespr devices. This device is a klte." So I am wondering... if the nightlies are for the Sprint Galaxy S5, what is the difference between the klte and kltespr? Also, how can I flash this "safely" if I can at all?
Delete the top section of the updater script so that the first line starts withe the word mount
vinman12 said:
Delete the top section of the updater script so that the first line starts withe the word mount
Click to expand...
Click to collapse
Sorry, I'm not on that level yet. How would you do that?
Still Doesn't Work
ethomas94 said:
Sorry, I'm not on that level yet. How would you do that?
Click to expand...
Click to collapse
Normally, you would extract the zip file of the rom, then navigate /META-INF/com/google/android/updater-script (open with Notepad++ or Sublime Text) and then delete the first couple of lines until the first word is mount. I've tried this and it doesn't seem to work though. The installation is still aborted with no error messages whatsoever.
All you need to do is remove the following from the "META-INF\com\google\android\" folder. It's the first line, just remove it and it will install.
Line to remove:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
MorningStarGG said:
All you need to do is remove the following from the "META-INF\com\google\android\" folder. It's the first line, just remove it and it will install.
Line to remove:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Click to expand...
Click to collapse
This doesnt work. Ive removed that code and continue to get other errors. I will try to upload a log. Im not familiar with twrp but cwm doesnt have an official recovery for this phone yet. Ill post back if I can get the log or if I can solve the problem.
---------- Post added at 01:14 PM ---------- Previous post was at 12:42 PM ----------
God I hate twrp. So after editing the zip file I get "error flashing zip (gives the location of zip here)
Updating partition details
Failed.
After copying the recovery log to the phone I open it up and its blank. Just wish there was a cwm recovery that had backup and restore options. I can care less if its touch.
hastack97 said:
Normally, you would extract the zip file of the rom, then navigate /META-INF/com/google/android/updater-script (open with Notepad++ or Sublime Text) and then delete the first couple of lines until the first word is mount. I've tried this and it doesn't seem to work though. The installation is still aborted with no error messages whatsoever.
Click to expand...
Click to collapse
weinerwad3000 said:
This doesnt work. Ive removed that code and continue to get other errors. I will try to upload a log. Im not familiar with twrp but cwm doesnt have an official recovery for this phone yet. Ill post back if I can get the log or if I can solve the problem.
---------- Post added at 01:14 PM ---------- Previous post was at 12:42 PM ----------
God I hate twrp. So after editing the zip file I get "error flashing zip (gives the location of zip here)
Updating partition details
Failed.
After copying the recovery log to the phone I open it up and its blank. Just wish there was a cwm recovery that had backup and restore options. I can care less if its touch.
Click to expand...
Click to collapse
MorningStarGG said:
All you need to do is remove the following from the "META-INF\com\google\android\" folder. It's the first line, just remove it and it will install.
Line to remove:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Click to expand...
Click to collapse
I've done it multiple ways with multiple programs on multiple operating systems. I still only the "error" message and the "Failed" message in red on top. It doesn't tell me why either. I wonder if it's just a 900P thing. It does suck, though.
I used a Mac and used Gedit, EZ7z, Zipeg and it didn't work. On my phone, I used Es File Explorer and Winzip for Android. Both didn't work. This is getting to be very annoying.
ethomas94 said:
I've done it multiple ways with multiple programs on multiple operating systems. I still only the "error" message and the "Failed" message in red on top. It doesn't tell me why either. I wonder if it's just a 900P thing. It does suck, though.
I used a Mac and used Gedit, EZ7z, Zipeg and it didn't work. On my phone, I used Es File Explorer and Winzip for Android. Both didn't work. This is getting to be very annoying.
Click to expand...
Click to collapse
The file is called "updater-script" it is in the "META-INF\com\google\android\" folder inside the nightly zip file. Just remove the first line in that file the line to remove should read the following:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
You have to extract the file, remove that line, and then put the modified file back into the zip file. It works I have done it several times now. If it is indeed failing saying you need a kltespr device and you do have a Sprint S5(AKA SM-G900P) this is the only thing that is preventing your install.
MorningStarGG said:
The file is called "updater-script" it is in the "META-INF\com\google\android\" folder inside the nightly zip file. Just remove the first line in that file the line to remove should read the following:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
You have to extract the file, remove that line, and then put the modified file back into the zip file. It works I have done it several times now. If it is indeed failing saying you need a kltespr device and you do have a Sprint S5(AKA SM-G900P) this is the only thing that is preventing your install.
Click to expand...
Click to collapse
I'll try that and get back to you. I was extracting the entire zip and altering it, then re-zipping the whole thing.
I fixed it.
What I was doing wrong was that after I extracted everything from the zip and edited the updater-script file, I would zip the extracted folder with all of the files in it, thus making a zip file, then a folder, then all of the files and stuff inside. That prevented the phone from flashing it, so it gave me the "error" message with no description (probably because it didn't know why it failed).
I was supposed to only zip the files that were in the extracted folder together into one zip, not the entire extracted folder with everything in it.
Also, a lot of people were saying that the edited updater-script file would not stay saved and would just revert as soon as you left the editor no matter what. I've got around this by using Gedit (for linux or mac, I don't know about pc) and hitting "save as...", keeping the original name, then simply replacing the original file with the edited one.
It would be nice if one of these sharp guys would post them already altered.
ethomas94 said:
I fixed it.
What I was doing wrong was that after I extracted everything from the zip and edited the updater-script file, I would zip the extracted folder with all of the files in it, thus making a zip file, then a folder, then all of the files and stuff inside. That prevented the phone from flashing it, so it gave me the "error" message with no description (probably because it didn't know why it failed).
I was supposed to only zip the files that were in the extracted folder together into one zip, not the entire extracted folder with everything in it.
Click to expand...
Click to collapse
Im sorry but this is very hard to understand. I still cant get it flashed. Step by step this is what I did.
1.) Extract the zip file.
2.) Locate the updater script file.
3.) Edit script file so mount is the first word in the code.
4.) Save edited script file.
5.) Rezip the entire extracted file.
What am I doing wrong? It will not flash.
mempho69 said:
It would be nice if one of these sharp guys would post them already altered.
Click to expand...
Click to collapse
weinerwad3000 said:
Im sorry but this is very hard to understand. I still cant get it flashed. Step by step this is what I did.
1.) Extract the zip file.
2.) Locate the updater script file.
3.) Edit script file so mount is the first word in the code.
4.) Save edited script file.
5.) Rezip the entire extracted file.
What am I doing wrong? It will not flash.
Click to expand...
Click to collapse
I'm only a new member (well, I was inactive for a long time) so I can't post large files.
Here's what you do.
1. Extract the zip file.
2. Navigate to the updater-script.
3. Edit it so that "mount" is the first thing it says (delete everything before that word).
4. Save it (or replace the file with the new one, which is how I got the save to stick)
5. ZIP ONLY THE FILES INSIDE THE MAIN FOLDER INTO ONE FILE. Don't zip the folder that came about after the extraction, only zip the files inside the folder (meta, img, etc) into one zip. If you zip the folder also, it will create a zip file, then the folder, then the contents. It will confuse the flash, that expects the contents to be directly after the zip layer, and not a zip, then a folder, then the contents; and the flash will fail without reason.
6. After the zip, it's ready.
If that did not work, then try only extracting the updater-script, then editing it, then putting it back in the zip (you may have to replace the original, do it)
The former is how it worked to me. Also, if you are using the 900P (Sprint Variant), get KT Recovery! It worked for me and now I can flash directly from cyanogenmod without editing the updater-script. There is a link in the KLTESPR general forum (It says Cyanogenmod is officially supporting us!). Simply flash it and it will replace the current recovery for your rooted phone as long as it already has a custom recovery. KT Recovery is a modded TWRP, just so you know. It works!
Also, it may not look like there is a folder after the zip if you zip the folder, but it won't flash if you zip the folder. That's why i say only zip the contents (meta, img, etc) into one zip!
KT Recovery is a modded TWRP, just so you know. It works!
ethomas94 said:
I'm only a new member (well, I was inactive for a long time) so I can't post large files.
Here's what you do.
1. Extract the zip file.
2. Navigate to the updater-script.
3. Edit it so that "mount" is the first thing it says (delete everything before that word).
4. Save it (or replace the file with the new one, which is how I got the save to stick)
5. ZIP ONLY THE FILES INSIDE THE MAIN FOLDER INTO ONE FILE. Don't zip the folder that came about after the extraction, only zip the files inside the folder (meta, img, etc) into one zip. If you zip the folder also, it will create a zip file, then the folder, then the contents. It will confuse the flash, that expects the contents to be directly after the zip layer, and not a zip, then a folder, then the contents; and the flash will fail without reason.
6. After the zip, it's ready.
If that did not work, then try only extracting the updater-script, then editing it, then putting it back in the zip (you may have to replace the original, do it)
The former is how it worked to me. Also, if you are using the 900P (Sprint Variant), get KT Recovery! It worked for me and now I can flash directly from cyanogenmod without editing the updater-script. There is a link in the KLTESPR general forum (It says Cyanogenmod is officially supporting us!). Simply flash it and it will replace the current recovery for your rooted phone as long as it already has a custom recovery. KT Recovery is a modded TWRP, just so you know. It works!
Also, it may not look like there is a folder after the zip if you zip the folder, but it won't flash if you zip the folder. That's why i say only zip the contents (meta, img, etc) into one zip!
Click to expand...
Click to collapse
Thank you. I installed the recovery and the file worked. I tried downloading the recovery a few days ago but I got a 404 error from the link. I couldn't stand the stock os so you helped me out tremendously. Thanks again.
No problem!
Sent from my SM-G900P using XDA Free mobile app
So, now I'm stuck. I was rooted, had plain old cwm installed and was able to flash the nightlies of CM11 to my lil hearts content. Then, for... reasons, I had to Odin back to stock and reroot, reflash recovery. Upon flashing Philz touch using Odin, and trying to flash 10/3 nightly, I start getting the error message I am seeing in this thread. First: I'd like to not have to do the fix shown in here. Is there a version of CWM that I can flash that will bypass all of this unpleasantness? Second, I tried, using Notepad++ to remove this line, ya know, the one that is supposedly the fix for all of this?. I highlight it, and nothing works to get rid of it. I hit cut, delete, kb shortcuts, you name it. Nothing works. So, either fix would be helpful, although my first choice would be just going back to the CWM that worked without all this added aggravation. Thanks in advance guys.
AuGmENTor said:
So, now I'm stuck. I was rooted, had plain old cwm installed and was able to flash the nightlies of CM11 to my lil hearts content. Then, for... reasons, I had to Odin back to stock and reroot, reflash recovery. Upon flashing Philz touch using Odin, and trying to flash 10/3 nightly, I start getting the error message I am seeing in this thread. First: I'd like to not have to do the fix shown in here. Is there a version of CWM that I can flash that will bypass all of this unpleasantness? Second, I tried, using Notepad++ to remove this line, ya know, the one that is supposedly the fix for all of this?. I highlight it, and nothing works to get rid of it. I hit cut, delete, kb shortcuts, you name it. Nothing works. So, either fix would be helpful, although my first choice would be just going back to the CWM that worked without all this added aggravation. Thanks in advance guys.
Click to expand...
Click to collapse
May be a little late, but i put up a custom version of TWRP that will allow installing, and updating via their update section in settings. Its in the dev section of sprint gs5 here at xda. Will try to post a link if i remember.
http://forum.xda-developers.com/showthread.php?p=52260413
miked63017 said:
May be a little late, but i put up a custom version of TWRP that will allow installing, and updating via their update section in settings. Its in the dev section of sprint gs5 here at xda. Will try to post a link if i remember.
Click to expand...
Click to collapse
I flashed PacMan ROM, which for some reason worked. So for now I'm stable. But I will be looking to go back to my first true love.... Cyanogenmod!
Thank's to this forum I have phone with 16gb memory, fastboot , TWRP and rooted - this is really great, thank you!
There is new update for 6039H - - 010 07p ~55Mb the of size, waiting for installation.
1st - where is this the file? Where "System updates" app is hiding it?
2nd - should we check update.zip somehow before flashing or just modify, flash and see results.?
Thank you.
Sent from my 6039H using Tapatalk
Just found where is ota hidden : /data/data/com.tcl.fota/.fotadownload
You need to have "Show hidden files" enabled in file manager to see/find it.
I tried use ota_modifier.sh get error:
ota_modifier.sh update.zip
The provided file is not a zip file!
then:
file update.zip
update.zip: Java Jar file data (zip)
In my system LXLE 14 witch is actually Ubuntu there is "zip" not a "Zip" witch is expected from script. I had to change this - editing script. One letter - big difference for linux.
Flashing update_modified.zip filed...
"/system/bin/app_process32" has unexpected contents.
E: Error executing updater binary in zip .... [path to my modified zip]
Error flasing zip [path]
[edit]
If you see this error reason is - root. Need to be fully unrooted!
Now everything went fine. Flashed thru TWRP, rerooted. Whole process takes quiet of time be patient.
Some people with this device have problems installing a ROM including me. That's because there is some difference in devices even though it seems like they are all the same.
After installing a ROM, if you have these type of messages:
"unable to mount /system"
"unable to mount /lost+found"
You should continue reading because somehow, no one else was able to fix this.
It's a partition issue. Not all devices are partitioned the same, for some reason.
To fix this, we have to change the ROM's installation script (updater-script) and do the script's work ourselves.
Pre-reqs:
7zip
Notepad++
First, extract the updater-script file from zip file with 7zip:
/META-INF/com/google/android
Now, open the updater-script file with Notepad++.
Press Ctrl+F and find these lines:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p21", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p21", "/system");
Delete these lines and save the file.
Move the file you saved into the zip file, in /META-INF/com/google/android.
Replace it.
When installing a ROM from TWRP, you should enter Wipe > Advanced Wipe and select Dalvik Cache, Cache, Data, System and wipe it.
Than, in Mount, remount System.
After that, install the ROM.
Letzen said:
Some people with this device have problems installing a ROM including me. That's because there is some difference in devices even though it seems like they are all the same.
After installing a ROM, if you have these type of messages:
"unable to mount /system"
"unable to mount /lost+found"
You should continue reading because somehow, no one else was able to fix this.
It's a partition issue. Not all devices are partitioned the same, for some reason.
To fix this, we have to change the ROM's installation script (updater-script) and do the script's work ourselves.
Pre-reqs:
7zip
Notepad++
First, extract the updater-script file from zip file with 7zip:
/META-INF/com/google/android
Now, open the updater-script file with Notepad++.
Press Ctrl+F and find these lines:
Delete these lines and save the file.
Move the file you saved into the zip file, in /META-INF/com/google/android.
Replace it.
When installing a ROM from TWRP, you should enter Wipe > Advanced Wipe and select Dalvik Cache, Cache, Data, System and wipe it.
Than, in Mount, remount System.
After that, install the ROM.
Click to expand...
Click to collapse
Bro thank you for the nice guide.
Is new twrp recovery (3.0.2) works for your device???
Sheref said:
Bro thank you for the nice guide.
Is new twrp recovery (3.0.2) works for your device???
Click to expand...
Click to collapse
As far as I remember it worked nicely, but I reverted back to the older one.
Letzen said:
As far as I remember it worked nicely, but I reverted back to the older one.
Click to expand...
Click to collapse
No New TWRP also has this problem you have to reboot recovery after every system format
Gautam Maini said:
No New TWRP also has this problem you have to reboot recovery after every system format
Click to expand...
Click to collapse
Can you explain it detail please.
Sheref said:
Can you explain it detail please.
Click to expand...
Click to collapse
The problem of unable to mount /system is still there in new TWRP . After you perform
1).System Partition Format
2).and Install Rom After System partition Modifications
You still have to follow @Letzen's Guide or reboot after modifications to system partition before installing anything from recovery
Conclusion:- New TWRP is good but still have the old problems