Well, I was seeing that some times people just don't like to manually make scripts, so I had the iniciative to make this software, and after weeks of no sleep, here you go.. I hope you guys like it!
Features:
Installable, now you can choose any folder on PC for building zip! Removed since 1.2
Easily build update scripts for Edify script (Used by most of ClockWorkMod Recovery's)
Configuration for compression
MD5 Calculation for Created Zips
Read from file
Hotkeys
Smart functions (like automatic placeholders for empty system folders only)
Non-repeatable options prompt (for example, formatting data twice)
Device selection (we'll need devices plugins )
Manual edition
Default symlinks for toolbox and busybox
Easy use for starting users
More!...
Simple instructions
Please report bugs, and remember that you need to have java installed for run this, and if you're on windows vista/7, run as administrator
This is a little video when I was building last options, now it's more complete and fast
Cheers,
D4.
10.03.2012 - 1.2r1
Fixed a LOT of bugs
Non installable again
Added EVO 3D prebuilt
Revamped logo, and Customizable themes on options
15.08.2011 - 1.01r2
Fixed this bug, thanks to darkstep for reporting
Improved zip method
13.08.2011 - 1.01r1
Now installable!
Output folder now it's on installation folder
Selection of external folder
Read script from zip
Added more hotkeys
Custom zip comment
Fixed bugs
08.08.2011 - 1.0r2
Implemented location of working directory (now you can work out of update folder)
Fixed bugs
07.08.2011 - 1.0r1
Initial Release.
sweet tool thanks
Excellent job!!!. This app is excellent, now evertbody can make custom zips.
Simple instructions for everybody to build zips:
Our work Folder will be called /update by default, and Update zip maker will create this folder on startup (you can change working folder). Also Update Zip Maker zip this folder when you press "Build package". *NEW* Now you can change working folder!
Copy files to be modded on selected place (for example, if I want to mod /system/build.prop, I'd put build.prop inside /update/system/ folder, which will create Update Zip Maker software) //also something interesting, If you press "Extract system" button, Update Zip Maker will create /system folder, inside /update, and the same for data
Mount our filesystem (for build.prop case, then we need to mount system)
OPTIONAL: Add some notification to user, like "installing build.prop"
Extract files (for build.prop case pressing Extract system)
Set permissions(for build.prop case 0 0 0 644)
Push zip to phone, install and enjoy!
This program is the bestI think this will be usefull for all devices who use ClockWorkMod Recovery so it will be greate to have teseter's with difrend device
btw D4 you are rocking exelent work
EDIT: hey is there any option that you add permissions for framework, bin, xbin, system?
i think when you press Set permissions it pups up like it is but there would be extra space that you just chose perms like for framework
Code:
(0, 0, 0755, 0644, "/system/framework");
this is just my proposal
Eyama said:
This program is the bestI think this will be usefull for all devices who use ClockWorkMod Recovery so it will be greate to have teseter's with difrend device
btw D4 you are rocking exelent work
EDIT: hey is there any option that you add permissions for framework, bin, xbin, system?
i think when you press Set permissions it pups up like it is but there would be extra space that you just chose perms like for framework
Code:
(0, 0, 0755, 0644, "/system/framework");
this is just my proposal
Click to expand...
Click to collapse
for folders like framework you can use "set permissions recursively"
btw, guys, could you press "sumbit to portal", on the top of first post, so everybody can see this please?
Edit, new version it's up, enjoy!
This program like a charm ^^ ,very simple and useful
thanks alot D4 )
This program doesn't create "update-binary", it is a bug or it is volontary ?
EDIT : My mistake ! I didn't use this software correctly... Sorry It work like a charm
Very good job ! Great app
New version it's up!, now installable!, enjoy new features!.
excellent job D4
you're the man this is wery good
First Thanks for Great tool.It's small and easy.
I make an update.zip to install an application.Here is the script:
mount("yaffs2", "MTD", "userdata", "/data");
ui_print("Coping app");
package_extract_dir("data", "/data");
set_perm_recursive(0, 0, 0755, 0644, "/data/app");
Problem is when i open the application it Force close.
Please Help me.
nishan432 said:
First Thanks for Great tool.It's small and easy.
I make an update.zip to install an application.Here is the script:
mount("yaffs2", "MTD", "userdata", "/data");
ui_print("Coping app");
package_extract_dir("data", "/data");
set_perm_recursive(0, 0, 0755, 0644, "/data/app");
Problem is when i open the application it Force close.
Please Help me.
Click to expand...
Click to collapse
Are you sure problem isnt with the app?
also try
set_perm(0, 0 , 755, 644, "/data/app/yourapp.apk")
set_perm_recursive it's for whole folders!
why do i keep getting this message
i set my working folder inside the folder is system/etc/init.d/ and the script i wanna run,i have tryid everything
darkstep said:
why do i keep getting this message
i set my working folder inside the folder is system/etc/init.d/ and the script i wanna run,i have tryid everything
Click to expand...
Click to collapse
Working folder it's main folder, that means /somefolder, you're trying to use /somefolder/system/etc/init.d, then you just need to use main folder, that means, working folder it's where you can see "META-INF", "system", "data", etc...
omg not working for me im not that big of a newbie
darkstep said:
omg not working for me im not that big of a newbie
Click to expand...
Click to collapse
I don't understand you, can you tell me all steps you followed?, also did you run as admin?
edit: and btw, we still don't have your device prebuilt (htc wildfire), can you test with u20?.
i will make a video and post it on youtube later
here is the video,not that great quality,i was in a hurry
Do I need net framework to run this? I'm on XP SP3 and when I try to run nothing happens. Tried opening as admin, no dice.
Related
Hey Ace Users,
I am going to provide you all the guide to create your own CWM Flashable zip file.
The Best Part of this guide is that you wont need your computer to create the CWM Flashable zip file as this guide will teach you all how to create the CWM Flashable Zip file with the help of the Root Explorer App.
The things you will need for this guide are:-
1.Root Explorer App.
2.Your Ace.
3.A little patience.
So without much ado,Lets start the guide.
STEPS:-
1.Download and install the Root Explorer App.
2.Open the Root Explorer App and Navigate to the Root of your SD Card.
3.Create a Folder and name it whatever you like or whatever name you want to give to your Zip File(I will be reffering to the folder as "Main Folder" throughout this guide)
4.In the Main Folder,you will need to have Two Sub-Folders which are as "META-INF" And "system".
5.The META-INF Folder consists of various files and they should be untouched(The only file in the META-INF folder which we are going to edit is the updater-script).
6.The system folder which you put in the Main Folder contains the apps or various other mods which you want to apply to your ace.
Steps on How to Edit the updater-script:-
1.Go to the META-INF Sub-Folder in the Main Folder.
2.open the com folder which you will find in the META-INF Sub-Folder.
3.Then you will see google folder as soon as you enter "com" folder,enter the google folder,now you will see "android" folder,open it.
4.In the android folder,you wll see two files named as update-binary and updater-script.
5.Open the updater-script file by selecting it.
6.You will see various options.
7.Select the Text Editor option and then the updater-script will open in the text editor.
8.Now we need to type some code so as to have the following functions.
Editing the updater-script:-
So once the updater-script is opened in the text editor,you will need to type some code so as to have the following functions.
CODE:-
Case 1:-
To Display the information of the particular Mod when you select to flash it in CWM Recovery(It is the display you see when you flash a particular Flashable zip file. For Example:- if you are flashing beats mod then when you select to flash the zip file and when the flashing starts you see some infomation like "Beats For Ace" and when the flashing is over you can see that the display shows flashing is done and it tells to reboot phone and stuff)
CODE:-
ui_print("The Text you want to display");
For Example if you want to display "beats Mod for Ace" then you must enter the code as ui_print("Beats Mod for Ace");
NOTE:-
semi-colon and the double quotes in the above code are to be put as they are compulsary to execute the code.
Case 2:-
If You want the updater-script to mount the /system partition,then the code is:-
CODE:-
run_program("/sbin/busybox", "mount", "/system");
NOTE:-
semi-colon and double quotes are compulsary.
Case 3:-
Now we need to put the apps in the /system partition and for that we need to type the code as:-
CODE:-
package_extract_dir("system", "/system");
NOTE:-
semi-colon and double quotes are compulsary.
Case 4:-
After typing the mount /system code you will also need to unmount the /system partition and to unmount the /system partition the code is:-
CODE:-
run_program("/sbin/busybox", "unmount", "/system");
NOTE:-
Semi-colon and double quotes are compulsary.
Special Case:-
After each case we need to have a special code.
At the start of updating the updater-script,we mostly write the introduction of the mod/script etc. in the ui_print.
so before you add the name & info of the mod in the ui_print you need to write show_progress(0.500000, 0);
and after writing the name/info of the mod,you will be mostly writing the code to mount the system partition,so after writing the code to mount the system partition,you need to write show_progress(0.500000, 20)
Now once you are done writing the code to mount the system partition the next thing you will be doing is extracting the package from the system partition by writing the code for extracting the system partition contents,so after you are done writing the code for extracting the system partition contents,you need to write show_progress(0.500000, 40)
Now after this,you will be writing the code to unmount the system partition so after writing that code you need to write show_progress(0.500000, 60)
After finishing writing the code to unmount the system partition,
you will add some more lines in the ui_print as for example Done flashing mod,so after writing that lines in the ui_print you will need to write show_progress(0.500000, 80)
After that you will probably write some more lines in the ui_print to notify the user to reboot his/her phone so after you write that code you will need to write show_progress(1.000000, 0)
Basically the show_progress command indicates the progress of the installation of the mod.
Sample of the whole updater-script codes in short:-
ui_print("Battery Mod For SGA");
ui_print("|-----by XYZ-----|");
ui_print("10% starting installation");
show_progress(0.500000, 0);
ui_print("20% mounting /system");
run_program("/sbin/busybox", "mount", "/system");
show_progress(0.500000, 20);
ui_print("40% Extracting Files");
package_extract_dir("system", "/system");
show_progress(0.500000, 40);
ui_print("60% unmounting /system");
run_program("/sbin/busybox", "unmount", "/system");
show_progress(0.500000, 60);
ui_print("|---Mod Flashed Successfully---|");
show_progress(0.500000, 80);
show_progress(1.000000, 0);
ui_print("Please Reboot Your Phone");
If you don't understand the show_progress procedure then check this link:-
http://rootzwiki.com/topic/6761-show...me-flashables/
NOTE FOR CM7 USERS:-
IF THE ABOVE CODE FOR MOUNTING AND UNMOUNTING THE /SYSTEM PARTITION DOESNT WORK FOR YOU,THEN YOU CAN MANUALLY MOUNT /SYSTEM BEFORE FLASHING AND THEN MANUALLY UMMOUNT IT(IF YOU WANT TO) AFTER FLASHIMG.
NOTE:-
AFTER SAVING THE CHANGES DONE TO THE updater-script,A FILE WILL BE CREATED AS "updater-script.bak".DELETE "updater-script.bak" file.
Okay so we are almost done.
Now some information about the system Sub-folder in the Main Folder.
The system Sub-folder contains another Sub-folder(s) like:-
For example if you want to add an app's apk file then the system sub-folder will contain "app" sub-folder and that app folder contains the apk file(s) that you want to put in the system partition of the ROM.
If you want to Put Framework Mods then the system sub-folder will contain "framework" sub-folder and the "framework" sub-folder wil contain the framework Mod(mostly the Framework mods are in Framework-res.apk file.)
If you want to put libs then the subfolder in the system subfolder will be "lib" and it will contain the libs.
If you want to put bin files then the subfolder in the system subfolder will be "bin" and it will contain the bin files.
If you want to add scripts then the subfolder in the system subfolder will be "etc" subfolder and in that "etc" subfolder there will be another subfolder as "init.d" and in the init.d subfolder there you can put the scripts.
After doing all that(i.e editing the updater-script and putting the files in the subfolders in the system subfolder) go back to the directory where you created the Main Folder and in Root explorer long press the Main Folder and you will get various options.
scroll down and select "zip this folder" and after the folder is zipped you can go to /SD Card/speed software/zip and find the flashable zip there.
Here ends my guide
Download Links:-
Sample file dl link
Screenshots of guide
Good..!!Helpful for lot of people:thumbup:
side_effect said:
Good..!!Helpful for lot of people:thumbup:
Click to expand...
Click to collapse
Helpful. Thanks
Sent from my GT-P6200 using Tapatalk 2
great guide :good::good::good:
but AFAIK guides are supposed to b in general...EET will move this soon
-RDR- said:
great guide :good::good::good:
but AFAIK guides are supposed to b in general...EET will move this soon
Click to expand...
Click to collapse
No they are meant to be in Development section.
I have seen many guides in development section of many phones.
Nope. Guides should be in General Section. Guides are not developing project.
This was sent from my impulses, not my Galaxy Ace.
Moving to General
Well we will have to remember alot of things before making a zip..
It will not be so easy
Really great guide....................
Sent from my GT-S6102 using Tapatalk 2
thanks for sharing
helpful
for
newbies
.......
i will try this when i get time.
thanks for this man!!
Sent from my GT-S5830 using xda premium
Thx!!!!!
Thx a lot man !!
Depuis mon Galaxy Ace GT-S5830-SGSII v9 modifié !!!
@Ace King 34
Hahaha...i think that you have forgot of put some things in this guide, and then about the command show_progress i think that you not have understood really how works.
Sent with my Evil GT-S5570 from Hell
EVIL THOR said:
@Ace King 34
Hahaha...i think that you have forgot of put some things in this guide, and then about the command show_progress i think that you not have understood really how works.
Sent with my Evil GT-S5570 from Hell
Click to expand...
Click to collapse
You Surely don't know how to read.
Read the Special Case in the OP Carefully.
It has got the show_progress.
and btw read the OP carefully next time before posting such replies.
Ace King 34 said:
You Surely don't know how to read.
Read the Special Case in the OP Carefully.
It has got the show_progress.
and btw read the OP carefully next time before posting such replies.
Click to expand...
Click to collapse
Surely you don't know read because i know read better than you Ace Chick, at least you know what do the value 40 in the command show_progress? your guide has only some commands copied from others updater-scripts but you don't know not even what they do...pfff...
Sent with my Evil GT-S5570 from Hell
@ EVIL THOR Thanks for Reporting me the issue mate.
I have changed the OP a bit.
Have a Look.
Ace King 34 said:
@ EVIL THOR Thanks for Reporting me the issue mate.
I have changed the OP a bit.
Have a Look.
Click to expand...
Click to collapse
Yes ok but the last show_progress should be 100 not 0 if not the bar of progress show only 80% and then go back to 0%.
Sent with my Evil GT-S5570 from Hell
EVIL THOR said:
Yes ok but the last show_progress should be 100 not 0 if not the bar of progress show only 80% and then go back to 0%.
Sent with my Evil GT-S5570 from Hell
Click to expand...
Click to collapse
mate I have changed the 0.500000 to 1.00000 and then I have written 0 so it changes the progress from 0.500000 to 1.000000 and I have tested it mate
it worked flawlessly.
Hello XDA people,
I'm trying to make a zip file which can be flashed through CWM. The zip file will include:
Code:
a batch of apps in the /system/app folder
The purpose of this zip is to quick install a bunch of apps after installing a new rom.
I'm guessing that simply drag dropping a bunch of apps inside the system/app zip folder will be enough, right?
The problem is that i don't have a dummy flashable zip file to work with. Can someone please help with this?
ps: i've tried app2zip from market, it doesn't work on s5360
its easy,but system partition have a size limit
i've tried making it but keep getting a "status 0 aborted" error.
What is the system size limit?
Will it help if i delete some big apps from system like maps and swype? I already have almost 50mb free on sys partition.
Can you give me the dummy file to test. preferably both for /data/app and /system/app
broadways said:
Hello XDA people,
I'm trying to make a zip file which can be flashed through CWM. The zip file will include:
Code:
a batch of apps in the /system/app folder
The purpose of this zip is to quick install a bunch of apps after installing a new rom.
I'm guessing that simply drag dropping a bunch of apps inside the system/app zip folder will be enough, right?
The problem is that i don't have a dummy flashable zip file to work with. Can someone please help with this?
ps: i've tried app2zip from market, it doesn't work on s5360
Click to expand...
Click to collapse
you need to sign the zip via zip signer (search in themes and apps) and write an updator script (google it)
i dont think size matters much because many rom zips contain only a /system folder
system folder has only 1limitation
the total memory is 222 mb so be carefull about that
your apps should not exceed this size
I got it working... Here is the code for anyone who needs it... found @ META-INF\com\google\android\updater-script file
Code:
ui_print("Partitions mount");
#Properly unmounting to avoid issues
run_program("/sbin/busybox", "umount", "/system");
run_program("/sbin/busybox", "umount", "/cache");
run_program("/sbin/busybox", "umount", "/data");
#Then mounting
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/cache");
run_program("/sbin/busybox", "mount", "/data");
ui_print("System folder application installation");
package_extract_dir("system", "/system");
ui_print("Unmounting partitions");
run_program("/sbin/busybox", "umount", "/system");
run_program("/sbin/busybox", "umount", "/cache");
run_program("/sbin/busybox", "umount", "/data");
ui_print("Finish");
With this code, anyone can load multiple apps from flash in 5 seconds.
There's another problem. While installing apps @ system/app works fine with the above script, a different script for installing apps @ data/app doesn't work at all. I have created a thread for this issue at the following link below:
http://forum.xda-developers.com/showthread.php?p=35698853
broadways said:
Hello XDA people,
I'm trying to make a zip file which can be flashed through CWM. The zip file will include:
Code:
a batch of apps in the /system/app folder
The purpose of this zip is to quick install a bunch of apps after installing a new rom.
I'm guessing that simply drag dropping a bunch of apps inside the system/app zip folder will be enough, right?
The problem is that i don't have a dummy flashable zip file to work with. Can someone please help with this?
ps: i've tried app2zip from market, it doesn't work on s5360
Click to expand...
Click to collapse
I think its better to make a backup using CWM and restore only data.
copy the zip from my signature (stock deadexed)
its for flashing bunch of apps to our device
.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ sent using busybox command via Cytherea phone ~
Spoiler
LESSON 1: dont ask for ETA's, the mod-wanna-be-guy will report it
---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------
add or delete any apps from app folder..
dont forget to delete framework folder as u not need it..
.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ sent using busybox command via Cytherea phone ~
Spoiler
LESSON 1: dont ask for ETA's, the mod-wanna-be-guy will report it
Hello guys! Hope you can help me with this.
I want to include some apps in my rom, but this app CANT be in the normal /system/app I want that they install as usar app every time i flash. It upose -i read it- that i should create a folder called "data" in the Root of my ROM. So i will have 3 folders: /META-INF/ /system/ and /data/
Along with this i have to edit with notepad++ the updater-script in the directory META-INF\com\google\android and add just below the line package_extract_dir("system", "/system"); the following:
format("yaffs2", "MTD", "userdata");
mount("yaffs2", "MTD", "userdata", "/data");
package_extract_dir("data", "/data");
set_perm(1000, 1000, 0771, "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
And save the file. So i just have to put the .apk files in the /data/ and they will appear like *****in' magic every time i flash... But no, is not working .
Where is the error or what is the right wat to do it? Thanks
And yeah, english is not my native language
mauriciognr said:
Hello guys! Hope you can help me with this.
I want to include some apps in my rom, but this app CANT be in the normal /system/app I want that they install as usar app every time i flash. It upose -i read it- that i should create a folder called "data" in the Root of my ROM. So i will have 3 folders: /META-INF/ /system/ and /data/
Along with this i have to edit with notepad++ the updater-script in the directory META-INF\com\google\android and add just below the line package_extract_dir("system", "/system"); the following:
format("yaffs2", "MTD", "userdata");
mount("yaffs2", "MTD", "userdata", "/data");
package_extract_dir("data", "/data");
set_perm(1000, 1000, 0771, "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
And save the file. So i just have to put the .apk files in the /data/ and they will appear like *****in' magic every time i flash... But no, is not working .
Where is the error or what is the right wat to do it? Thanks
And yeah, english is not my native language
Click to expand...
Click to collapse
If you want the app to be a system app, have you tried extracting the library files in the .apk? Open the .apk using WinRAR (an .apk is real
y like a .zip file) and open the folder 'lib' (if there is one). The folder within should be called something like 'armv7a' or 'armv6'. If your device is an ARMv6 device (search it up) the app may be incompatible with your device if there is no matching 'armv6' folder. If there is, open the folder and extract the .so file(s) and put them under /system/lib/ on your device, either with a root file browser, or with a .zip via CWM, Anyways, what app are you trying to install
?
Codename13 said:
If you want the app to be a system app, have you tried extracting the library files in the .apk? Open the .apk using WinRAR (an .apk is real
y like a .zip file) and open the folder 'lib' (if there is one). The folder within should be called something like 'armv7a' or 'armv6'. If your device is an ARMv6 device (search it up) the app may be incompatible with your device if there is no matching 'armv6' folder. If there is, open the folder and extract the .so file(s) and put them under /system/lib/ on your device, either with a root file browser, or with a .zip via CWM, Anyways, what app are you trying to install
?
Click to expand...
Click to collapse
Thanks for reply, but I already know that and already did it. Due to my phone have REALLY little rom memory. So my dream was to allow some apps to be instaled along with the rom.zip but as a user app. Im sick and tired already have almost a week like 6 hours day making my mod of a rom and now that is ready and sexy i cant "transfer the data folder from de rom.zip to data. Thanks for replay.
Have you looked into dsixda's kitchen? It will load your ROM and add in the bits needed to do what you want. The only downside is it isn't really updated anymore. You could also find a mod that flashes user apps in your phone's respective forum, then open it up and look at the updater-script.
Sent from a Toasted Devil
netwokz said:
Have you looked into dsixda's kitchen? It will load your ROM and add in the bits needed to do what you want. The only downside is it isn't really updated anymore. You could also find a mod that flashes user apps in your phone's respective forum, then open it up and look at the updater-script.
Click to expand...
Click to collapse
Now here I am with identical problem. In my case,
A. There is no forum with other mods for the TV Stick I am coding.
B. Dxixda's Kitchen chocked up with the AMLOGIC Kernel and refused to help further.
So here's my problem that, I have been breaking my head on this for a week now.
I have a TV Stick with android ICS 4.0.4, and has "yafss2" format. I have attached the mountpoint info, partition info and my updater script.
I am trying to mount the /Data Partition so that I can copy a test APK to /Data/App folder for now. Eventually I need to copy other stuff like app data to /data/data.
Although edify script requires the format
mount(type, device, mountpoint);
I need to do
mount("yafss2","MTD", "/dev/block/mtdblock7", "/data");
for some reason, otherwise the AMLOGIC Recovery gives error of missing parameter.
Anyway, even after following that format, its not working.
The subsequent "package_extract_dir" operation is not successful and I can see the files are not getting copied.
I'd dearly appreciate any pointers and advice.
may be you should set the permission on the /data instead of on the /system/app in you updater script.
hope this can help....
tepar said:
may be you should set the permission on the /data instead of on the /system/app in you updater script.
hope this can help....
Click to expand...
Click to collapse
I should have commented out that statement. I realized it after I posted. No it doesn't really matter anyway. The files didn't get copied to there's no permissions to set.
First I am no Real Developer. So read an test what I say.
In fact this may be a known issue for real developers.
This belongs to GT-P5210
I found my self installing various Zip files in recovery mod that Failed!
After carefully study various ZIP files that work and comparing them with the ZIP files that does not, I found that the ones that work have the "update-binary" with size of 322,688 bytes and the ones that fail have only 194,636!
Tis is for those of you like me that are starting to learn how to develop.
Get an update file that work in P5210: For example go and get
Code:
http://roms.bindroid.com/downloads/viewcategory/11-stock
and download the file : no_bloatware_stock_rom.zip
Now using 7zip or any other compressor, go ahead and decompress the file. You will see the following folders: META-INF\com\google\android
Inside android there is a binary called: update-binary
that I understand interprets the commands inside the script called: updater-script
Is this update-binary the one I am talking about. This is 322,688 bytes!
- - - - - - - - - - - - - - - - - - - - -
Now lest download a zip file that does not work in our P5210.
I been studying a way to back up our partitions. So I been reading on:
Online Nandroid / Nandroid Backup without re-booting
http://forum.xda-developers.com/showthread.php?t=1620255
At the bottom of the first post is the link to the program. This program is install on a rooted device via zip file on recovery mode.
Here is a direct link for "onandroidv9.20.zip" so you to follow me.
http://forum.xda-developers.com/attachment.php?attachmentid=2389865&d=1384355365
Try to install using TWRP by saving the file onandroidv9.20.zip on your Internal memory using the PC.
In TWRP then you will do Install and then search /emmc for onandroidv9.20.zip. Select the file and install.
You will see:
Code:
Updating partition details...
Installing '/emmc/onandroidv9.20.zip' ...
Check for MD5 file ...
Skip MD5 check: no MD5 file found.
[COLOR="Red"]E:Error executing updater binary in zip '/emmc/onandroidv9.20./onandroidv9.20.zip'
Error flashing zip '/emmc/onandroidv9.20./onandroidv9.20.zip'[/COLOR]
Injecting TWRP into boot Image...
TWRP Injection complete.
Updating partition details...
[COLOR="Red"]FAILED[/COLOR]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
So then I thought this has to be with the issue our P5210 is x86. And for sure my friend DutchDanny compiled that "update-binary" special for us.
So since this files have no signature I decide to copy the "update-binary" from the DutchDanny Files and replace the one inside onandroidv9.20.zip and I rename this modified file onandroidv9.20x86.zip
Then I try to install it in TWRP and guess what!!!! Yes it install without any issue.
So this "update-binary" that I saw first on DutchDanny files is been copied on all roms that we see posted here. So this is known to our real developers.
But I thought it should be shown, so that we can force the Failing Zip Files to work in P5210.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Now Here is an Interesting Thing.......
Our GT-P5210 is x86. Not : armeabi or armeabi-v7a nor mips!!!!!
But most of all application in the market are armeabi or armeabi-v7a. They do not have a x86 version.
But when you are running Android normally yesssssss all apks work fine. So how is that possible?
Some people has claim that there are a secondary armeabi processor inside or x86 device. Others think there is emulation!! I do not know.
But I know I had side load many apks really old at the beginning of Android when there was no x86 and they most all work. A few exceptions.
For example MXPlayer requires a special MXPlayer Code Pack. And if you look inside MXPlayer apk that there is a folder "lib" that have sub folders "x86, armeabi or armeabi-v7a and mips". With the applicable libraries that for sure are compiled for each different processor.
If you go into MX Player Codec (x86).apk in lib you will see only "Lib\x86" as expected. It is to be used only in x86.
What I a saying, It is possible that our P5210 have some sort of way of ruining armeabi code while ruining normally. But there are things that require true x86 code like some libraries. This only while you are ruining normally the OS. And I expect that when in Recovery this does not apply making many zip designed for armeabi to fail.
I hope this is useful for you.
Edited:
Correction: There is no second CPU but in fact allmost all apps run under Java Dalvik and libraries via emulation ( houdini library) please see below.
Wow, good info! It also makes me realize just how much I have to learn.
Wow, good troubleshooting. Thank you for taking the time and putting this on paper. I hope with more research somone will crack this x86 product.
Sent from my GT-P5210 using xda app-developers app
imagelost said:
Wow, good troubleshooting. Thank you for taking the time and putting this on paper. I hope with more research somone will crack this x86 product.
Sent from my GT-P5210 using xda app-developers app
Click to expand...
Click to collapse
Next see my post for more info in our OS , x86, armeabi and Java Virtual Machine (Dalvik)
http://forum.xda-developers.com/showpost.php?p=49316921&postcount=51
http://forum.xda-developers.com/showpost.php?p=49324166&postcount=54
Sorry for the slight OT post but the tab 3 10.1 has an intel X86 processor. It is able to run native android apps (compiled for ARM) using something called libhoudini
http://commonsware.com/blog/2013/11/21/libhoudini-what-it-means-for-developers.html
This is just my understanding. sorry if anythin gi've said is wrong.
Thanks
I kow there are many old developers that do not think like me. But I am greatfull of any information that gets to be publis here.
I searched for moths for the answer of how this P52xx where managing old ARM base apk and compiled libraries. No one gave published here an anser . Just A few day I relize that most work becouse of Java Dalvic, and that the libs where handle by this houdini magic.
But please understand that this update.zip are build to run in recovery mode. It is our understanding that there is no houdini magic runing on recovery mode. Thanksfull most is dome on script, but those scrit are translated by update-binary. As I understand this update-binary the is recquired to be compiled for x86. Since no houdini is availabe in recovery mode.
I have to make also clear, that it is my understanding that if an update.zip uses more binary files, they also may be required to be compiled for x86. We can mention busybox, toolbox but may be more!! So if you have an update.zip that keep failng, Bring the atention to the developer and ask him politely to understand that our tablets require this binaries compiled for x86.
Sory for the spelling errors I have no dictionary where I am at know.
Thank you a lot
Thanks a lot OP!that was really heplful thread:good::good::good:,i thought the problem was to rename the update-script to update-binary and delete the other 'update-binary'.
LYandroid;49475925... said:
i thought the problem was to rename the update-script to update-binary and delete the other 'update-binary':
Click to expand...
Click to collapse
I am no expert, but :
update-binary : is the program that interprets the instructions place in the "script", then execute them. Once compiled it never changes excepts for updates or improvements.
update-t or updater-script : is just a script, where we place our set of instructions to perform a task. This change all the time since it will contains different instructions, for every different task we desire to do.
You can not rename one to the other, they are two different things. Normally you need both the binary and the script. But I have seen binaries that do not require the script, I guess they are compile specially to include in them the commands!
I have a motorola xt890 "Razr i" who has also an intel processor atom z580 x86, some developers also try to port first cm for our devices, we already have a build that boot and everything its awesome, but hasnt have sound , also about the updater script, there is a special one for the x86 architechture, some devs on our forum have it already
Maybe you should check the info about, its on the Motorola Razr I development forum from here.
Enviado desde mi XT890 mediante Tapatalk
Thanks for the info on changing the update-binary. I also had to change the line in my updater-script that was trying to run busybox from /sbin to /system/xbin.
Sent from my SM-N900V using XDA Premium HD app
I am trying to install this script with TWRP using your method, but it seems failed.
http://forum.xda-developers.com/showthread.php?p=49903814
would you mind to try it?
I downloaded the script installation zip, changed the update-binary, and it gave an error before executing any of the updater-script. When I changed all lines in the updater-script trying to run programs in busybox from /sbin to /system/xbin, most of the updater-script executed. The one error was my fault in syntax. I know my busybox is installed to /system/xbin, but I don't know anything about busybox itself and it's symlinks. Where is everyone else's busybox installed? Is the location of busybox simply another difference with x86 android builds or am I missing some symlink?
Sent from my SM-N900V using XDA Premium HD app
I been busy. Sorry for the delay.
I am not sure of what I am about to say but here is my understanding. Please keep in mind I am also learning.
1) busybox is an added User binary file that we add to the Android system partition. Most of us did not actually added it ourself, we use an application to add it to Android "system" partition. So when we boot to Android OS it is then there ready for us.
2) But In linux (Yes Android Java Dalvik run on top of Linux) where the User place his own binaries is not well define or implemented. So you will find time after time a problem similar to this situation.
3) So, I confessed I am not sure where busybox binary should really be. I know that normally I will see the Real busybox is in one place and find simlinks ( shorcuts) in the rest of those locations.
4) Now it is important to keep in mind that the folders: /sbin, /xbin, /system, /system\bin, /system/xbin not necessary are the same when you boot in Android OS or when you boot in Recovery!!!!!! Read this 2 or 3 times!!! It is important.
5) In the case of Recovery Partition busybox is there because the developer that created that partition did it for us. Clearly where it is will depend on what the recovery partition's developer decided to place it. I do not know right now where is in CWM that DutchDanny made since I no longer have that in my Tablet. Latter I can try to inspect the recovery.img and tell you.
6) Where is busybox in my P5210:
* I am inspecting my TWRP and I can see that we have a "/bin/busybox". And I do not see folders "xbin" neither in "/xbin" nor in "\system\xbin".
* I am currently testing rom "Bindroid One ver 2.01". In this OS I can see only "/system/xbin/busybox". I have no sysmlinks! Interesting, Not important to me. Keep in mind that I am testing I had no need for it or installing any application that may had require it.
@chchia & @themoneyman It seems both of you are talking about same script but i can be wrong?
Butt....... lets look at the script anyway.
Code:
ui_print(" ");
ui_print("================================");
ui_print("********************************");
ui_print(" ");
ui_print(" T w e a k D r y p t ");
ui_print(" ");
ui_print(" by ");
ui_print(" ");
ui_print(" Team T.D.T ");
ui_print(" ");
ui_print("********************************");
ui_print("================================");
ui_print(" ");
ui_print("Mounting /system /data /cache");
ui_print("");
run_program("/sbin/mount", "/system");
run_program("/sbin/mount", "/data");
run_program("/sbin/mount", "/cache");
show_progress(1, 15);
run_program("/sbin/sleep", "5");
run_program("/sbin/busybox","mv","-f","/system/etc/init.d/50selinuxrelabel","/tmp");
run_program("/sbin/busybox","mv","-f","/system/etc/init.d/90userinit","/tmp");
run_program("/sbin/busybox","mv","-f","/system/etc/init.d/00banner","/tmp");
ui_print("");
ui_print("Deleting old files,please wait..");
ui_print("");
delete_recursive("/data/tombstones");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/boot-cache");
delete_recursive("/data/resource-cache");
delete("/data/system/batterystats.bin");
delete("/system/etc/init.d/00syscleaner");
delete("/system/etc/init.d/01batterytweaker");
delete("/system/etc/init.d/02netweakz");
delete("/system/etc/init.d/03ram_optimize");
delete("/system/etc/init.d/11sdspeedfix");
delete("/system/etc/init.d/05zipalign");
delete("/system/etc/init.d/06gpurender");
delete("/system/etc/init.d/07zipaligndata");
delete("/system/etc/init.d/08kernelTweak");
delete("/system/etc/init.d/09cron");
delete("/system/etc/init.d/10TouchscreenSensitivity");
delete("/system/etc/init.d/04sqlite3");
delete_recursive("/system/etc/init.d");
delete_recursive("/system/etc/cron");
run_program("/sbin/sleep", "5");
ui_print("Installing scripts ");
ui_print("");
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
show_progress(0.200000, 40);
run_program("/sbin/busybox","mv","-f","/tmp/50selinuxrelabel","/system/etc/init.d");
run_program("/sbin/busybox","mv","-f","/tmp/90userinit","/system/etc/init.d");
run_program("/sbin/busybox","mv","-f","/tmp/00banner","/system/etc/init.d");
ui_print("Fixing permissions");
ui_print("");
set_perm_recursive(0, 2000, 0777, 0777, "/system/etc/init.d");
set_perm(0, 0, 0777, "/system/bin/uninstall");
set_perm(0, 0, 0777, "/system/bin/scan");
set_perm(0, 0, 0777, "/system/bin/tweakd");
set_perm(0, 0, 0777, "/system/xbin/sqlite3");
set_perm(0, 0, 0777, "/system/xbin/openvpn");
set_perm(0, 0, 0777, "/system/xbin/zipalign");
set_perm(0, 0, 0777, "/system/lib/libncurses.so");
set_perm(0, 0, 0777, "/system/lib/libsqlite.so");
set_perm(0, 0, 0777, "/system/lib/libsqlite_jni.so");
set_perm(0, 0, 0777, "/system/etc/init.d/01syscleaner");
set_perm(0, 0, 0777, "/system/etc/init.d/02cpu_kernel_gov");
set_perm(0, 0, 0777, "/system/etc/init.d/03sqlite3");
set_perm(0, 0, 0777, "/system/etc/init.d/04zipalign");
set_perm(0, 0, 0777, "/system/etc/init.d/05zipaligndata");
set_perm(0, 0, 0777, "/system/etc/init.d/06cron");
set_perm(0, 0, 0777, "/system/etc/init.d/07storage");
set_perm(0, 0, 0777, "/system/etc/init.d/08batterytweak");
set_perm(0, 0, 0777, "/system/etc/init.d/09VM");
set_perm(0, 0, 0777, "/system/etc/init.d/10Ksm");
set_perm(0, 0, 0777, "/system/etc/init.d/11Touch_Sens");
set_perm(0, 0, 0777, "/system/etc/hosts");
set_perm(0, 0, 0777, "/system/etc/gps.conf");
set_perm(0, 0, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
set_perm_recursive(0, 2000, 0777, 0777, "/data/tweakdrypt");
run_program("/sbin/sleep", "3");
ui_print("Unmounting partitions...");
ui_print("");
run_program("/sbin/umount", "/system");
run_program("/sbin/umount", "/data");
run_program("/sbin/umount", "/cache");
ui_print("Installation Completed !!!!");
ui_print("");
ui_print("| Reboot System Now |");
themoneyman said:
... I also had to change the line in my updater-script that was trying to run busybox from /sbin to /system/xbin....
Click to expand...
Click to collapse
Wao!!! to me this is strange since I have not seen or recall a "\system\xbin" folder in the Recovery. But I may be wrong. But I may bee misunderstanding you too. I will explain.
in the updater-script there are line that are to be run at recovery. For example:
line 21
Code:
run_program("/[COLOR="Blue"]sbin[/COLOR]/busybox","mv","-f","/system/etc/init.d/50selinuxrelabel","/tmp");"
You see zip installation files is executed in Recovery. Waooo here is what happen, think In this:
I am going to assume that you are wrong. There is no \system\xbin folder in Recovery. So if there is no folder much less a bussybox in that folder.....
So in order for the previos code line to execute busybox in recovery will have to be in "/sbin/busybox". But you said it work for you in "/system/xbin". To me it should not work. But lets see.
You are sugesting to change "/sbin" fir "/systen/xbin" line 21 should look like:
Code:
run_program("[COLOR="Red"]/system/xbin[/COLOR]/busybox","mv","-f","/system/etc/init.d/50selinuxrelabel","/tmp");"
Normally if you try to execute that las one, It wont work because there is no folder "/system/xbin" in recovery.
But look at Line 16
Code:
run_program("/sbin/mount", "/system");
Because this script mount the Android /system partition now all files that should only be available at Android are ready to be use in the Recovery!!! End result: What you are doing works in this particular script Only because the Android /system partition is mounted!!! But keep an eye in other script that may not mount /system before using /xbin/busubox!!!!
chchia said:
I am trying to install this script with TWRP using your method, but it seems failed.
http://forum.xda-developers.com/showthread.php?p=49903814
would you mind to try it?
Click to expand...
Click to collapse
Uff, I do not have time for this now I am really busy. I downloaded as you see I posted the script.
Here is what I think is the problem
Unzip "TDT_V4.1_(jb_kk).zip" ( I am assuming you are using jb in your tablet)
You will see in it: data , META-INF, system and a readme.txt
Browse those folders.
You will see there are binaries there!!!!!
now read the script /META-INF/com/google/android/updater-script (yes the same I show before)
line 49 reads
Code:
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
What those line do is copy and overwriting ALL the binaries inside the packages system and data folders and deposit them in your Android partitions!!!!
Here is the sad part for all us users of a x86 device. Our original binaries where compile and optimize for x86 device. The binaries this developer and many other you will try to use in the future most likely where not made for x86!!! Copying over our original binaries may be wrong!!!!!!!
In fact I am learning with your request. I never thought on this problem we have. Waoooo!
My best suggestion is go to the developer and ask him to create this packakes for an x86 device. All binaries should be compile specialy for x86......
In any case: Guys PLease report to us if this package "TDT_V4.1_(jb_kk).zip" was finally installed? Did it work?
Whats the easiest way to install a rom on the device. Because what the op states its a sht load of steps just to get one zip to install
Sent from my SM-N900T using Tapatalk
Disclaimer
I will not be responsible if you screw up with your device.
Do make a Nandroid backup first.
Before we start
Downloads
WinRAR
Notepad++
Template Zip
Lets get started
I have provided you with the template zip inside which by making changes we can create our flashable zips. All necessary files are inside Template zip
Open up the template zip. There you will see two folders "META-INF" and "system". [In "META-INF" all the coding stuff resides and in "system" all your apps and media files resides.]
META-INF
In META-INF have one folder "com" and three files [We don't have to edit these three files]
Now open "com" folder and inside it open "google" folder then "android" folder.
Now inside "android" folder you will see two files "update-binary" [We don't have to edit this file, leave it as it is.] and "updater-script"[It is the file which is used to tell custom recovery what to do with the flashable zip ].
We have to edit "updater-script" file by using notepad++. [Scroll below to see how to edit updater-script]
System Folder
It is the folder where all of your apks, zips, libs reside.
Inside System Folder make folders as following:
If you want to flash an app and make it system app create "app" folder and if not a system app make "priv-app" folder. You can also make "lib" folder along with "app" folder if your apps uses libs.
If you want to flash a bootanimation or ringtones etc make "media" folder.
If you want to flash something else ask it below.
How to edit "updater-script"?
What is updater-script?
updater-script is a file written in edify script language which instructs the recovery to perform certain tasks.
updater-script is located in /META-INF/com/google/android/updater-script in flashable zip
Some basic rules:
Every statement must end with a semicolon (; )
Comments must start with #
Strings must be delimited by double quotes (” “)
Commands
Now i will try to explain commands used in updater-script in very easy language or noob language.
Code:
format("yaffs2", "MTD", "system", "/system");
The above command is used to format the specified partition
Syntax explanation:
format - The main command to direct the recovery to format using the following parameters
"yaffs2" - Filesystem type used in the device
"MTD" - Type of the partition used in the file system
"system" - Name of the partition to be formatted
"/system" - Location of the partition to be formatted
======================================================================================================
Code:
ui_print("Format Completed");
The above command directs the recovery to display the following text enclosed in double quotes in the user interface (display).
After successful formatting it displays "Format Completed" in the device screen.
======================================================================================================
Code:
mount("yaffs2", "MTD", "system", "/system");
The mount command directs the recovery to mount the following file system and the following partition
The text syntax is same as format command as instead of formatting it mounts.
======================================================================================================
Code:
package_extract_dir("system", "/system");
This command searches for the directory (folder) named "system" in the root of the zip file and copies all the content of the "system" folder from the zip file into the "/system" partition which is already mounted by the previous mount command ie it copies all the folder items inside system folder like apps, media etc as explained above.
======================================================================================================
Code:
package_extract_file("autoroot.sh", "/tmp/autoroot.sh");
This command searches for the file named "autoroot.sh" in the root of the zip file and copies the file to "/tmp" folder and names it as "autoroot.sh" (here it does not change the name)
======================================================================================================
Code:
symlink("mksh", "/system/bin/sh");
The above command creates a symlink.
What is symlink?
Symlink is nothing but shortcuts, for example if a file is required in two different places instead of copy pasting the file in two different locations, the file is copied to one of the two locations and in the other location a shortcut to the file(symlink) is created. The source and the symlink can have different names (actually this is the prime use of symlinks).
Let me explain it in a noob friendly manner.
Take the above symlink, it creates a shortcut(symlink) for the command "mksh" and places it in the path of the operating system. The shortcut(symlink) directs to the file "/system/bin/sh" , so whenever the os gets a request to execute the "mksh" command, the actual
binary that gets excuted will be "/system/bin/sh" .
Creating symlinks saves a lot of space because instead of copying the whole file and placing it in requiered places we are just creating shortcuts which directs to the source file which can be placed anywhere in the file system (generally placed in the path of the os).
======================================================================================================
Code:
set_perm_recursive(0, 0, 0755, 0644, "/system");
The above command is used to set permission recursively for the files and folders present inside a folder (in this case for "/system" folder).
Explanation of syntax:
0 - uid - It defines that the following permission is set for the user id 0 .
0 - gid - It defines that the following permission is set for the group id 0 .
0775 - Dirmode - It defines that 0775 permission to set to directories contained within the specified directory.
0644 - Filemode - t defines that 0644 permission to set to files contained within the specified directory.
"/system" - Target directory to set the above mentioned permissions.
======================================================================================================
Code:
set_perm(0, 3003, 06755, "/system/bin/ip");
The above command is used to set permission for a individual file (in this case for "/system/bin/ip" file).
syntax explanation:
0 - uid - It defines that the following permission is set for the user id 0 .
3003 - gid - It defines that the following permission is set for the group id 3003 .
06775 - It defines that 06775 permission to set to the specific file.
"/system/bin/ip" - Target file to set the above mentioned permissions.
Other Permission commands:
Use to push new files to /data partition and /system partition.
ui_print(“Setting permissions…”);
set_perm_recursive(1000, 1000, 0771, 0644, “/data/app”);
set_perm_recursive(0, 0, 0755, 0644, “/system”);
set_perm_recursive(0, 0, 0777, 0777, “/system/etc/init.d”);
set_perm_recursive(0, 2000, 0755, 0755, “/system/bin”);
set_perm(0, 3003, 06755, “/system/bin/ip”);
set_perm(0, 3003, 02750, “/system/bin/netcfg”);
set_perm(0, 3004, 02755, “/system/bin/ping”);
set_perm(0, 2000, 06750, “/system/bin/run-as”);
set_perm_recursive(1002, 1002, 0755, 0440, “/system/etc/bluetooth”);
set_perm(0, 0, 0755, “/system/etc/bluetooth”);
set_perm(1000, 1000, 0640, “/system/etc/bluetooth/auto_pair_devlist.conf”);
set_perm(1002, 1002, 0440, “/system/etc/dbus.conf”);
set_perm(1014, 2000, 0550, “/system/etc/dhcpcd/dhcpcd-run-hooks”);
set_perm(0, 2000, 0550, “/system/etc/init.goldfish.sh”);
set_perm_recursive(0, 0, 0755, 0555, “/system/etc/ppp”);
set_perm_recursive(0, 2000, 0755, 0644, “/system/vendor”);
set_perm_recursive(0, 2000, 0755, 0644, “/system/vendor/etc”);
set_perm(0, 2000, 0755, “/system/vendor/lib”);
set_perm(0, 2000, 0755, “/system/vendor/lib/hw”);
set_perm_recursive(0, 2000, 0755, 0755, “/system/xbin”);
set_perm(0, 0, 06755, “/system/xbin/su”);
set_perm(0, 1000, 0755, “/system/xbin/busybox”);
======================================================================================================
Code:
unmount("/system");
This command just unmount the system.
======================================================================================================
iflesh Command:
Code:
Ifelse(condition),(do_this),(else_do_this);
Example:
Code:
ifelse mount("yaffs2", "MTD", "system", "/system") == "system", ui_print("Mounted!"), ui_print("Mount Failed!");
Ifelse command can be explained simply as asking the system to do something based on the result of a condition.
From example:
The ifelse command would attempt to mount the MTD partition named "system" to "/system".
If the mounting process succeeds (the condition), the script will display "Mounted!", else it will display "Mount Failed!"
======================================================================================================
Code:
abort()
It just abort's the script execution.
Note: It is usually paired with some other command for example the getprop command or with ifelse. Independently specifying abort() in the updater-script will kill the script abruptly right there so use this command carefully.
======================================================================================================
Code:
show_progress(fraction,duration)
Code:
show_progress(0.2,5);
fraction = a fraction of the bar (more on that in a moment)
duration = seconds
The "seconds" part just means how long the progress bar should take to fill up to the new level. It will not delay your script in any way: it will only take this much time if something else in the script is also taking that much time.
For example, if you run this snippet, you can watch the progress bar partially fill up pieces at a time. Each piece will take 5 seconds to fill, then pause for 2 seconds before the next piece starts (sleep command is for 7, so after the progress bar is done its 5 seconds of movement, there are 2 seconds of sleep left until the next command)
======================================================================================================
ALWAYS LEAVE TWO BLANK LINE AT THE END OF THE update-script (if the code contains 50 lines then 52 lines should be visible in the notepad++ including two blank line after the end of the script)
======================================================================================================
HOPE I HELPED YOU GUYS..... IF I MISS SOMETHING PLEASE LET ME KNOW.... AND DON'T FORGET TO PRESS THANKS....:good:
For More Info visit: http://forum.xda-developers.com/wiki/Edify_script_language
Reserved
Reserved
Excellent guide!!, thanks , it will help me a lot.
xxkirianxx said:
Excellent guide!!, thanks , it will help me a lot.
Click to expand...
Click to collapse
Its good that it helped you!!!
If I want to remove system folder and data folder so is it possible without any wrong effects
Sent from my Symphony V80 using XDA-Developers mobile app
lkdevil said:
If I want to remove system folder and data folder so is it possible without any wrong effects
Sent from my Symphony V80 using XDA-Developers mobile app
Click to expand...
Click to collapse
Whole system folder or a folder inside /system
META-INF Folder
hi. @TheRoyalSeeker
we only edit what in "updater-script" ( to make it flashable via recovery )
now my question is :
1. is (update-binary) always suitable for all android platform - KK, LP, even MM ?
2. or is it (update-binary) always suitable for any devices ?
if no.. so..
I believe I can make "META-INF" Folder or "updater-script" by myself, but for "CERT.RSA" , "CERT.SF" , "MANIFEST.MF" and "update-binary" could you tell me how or from where can I take or pull those file ?
I'm stuck on those 4 files
if yes.. so..
I dont really bother anymore, I just download any "template.zip" which is containing those files, and only editing "updater-script"
thank you very much for your reply. I'm kindly appreciate anyhelp.
maz izaackovich said:
hi. @TheRoyalSeeker
we only edit what in "updater-script" ( to make it flashable via recovery )
now my question is :
1. is (update-binary) always suitable for all android platform - KK, LP, even MM ?
2. or is it (update-binary) always suitable for any devices ?
if no.. so..
I believe I can make "META-INF" Folder or "updater-script" by myself, but for "CERT.RSA" , "CERT.SF" , "MANIFEST.MF" and "update-binary" could you tell me how or from where can I take or pull those file ?
I'm stuck on those 4 files
if yes.. so..
I dont really bother anymore, I just download any "template.zip" which is containing those files, and only editing "updater-script"
thank you very much for your reply. I'm kindly appreciate anyhelp.
Click to expand...
Click to collapse
"update-binary" is pretty much universal and the only problem that might occur is with x86 devices.
For extracting "update-binary" and other files you can use your ROM's zip.
Use template zip, i don't think any problem will occur.
TheRoyalSeeker said:
Disclaimer
For More Info visit: http://forum.xda-developers.com/wiki/Edify_script_language
Click to expand...
Click to collapse
bundle of thanks brother i really really appricate your hard work, today XDA successfull coz XDA have your kind of peoples
brother its help me alot,
i want to know something , i extracted the lollipop rom , the format it system,img,ext4 ........now i change the some permissions
now i want to again repack the rom so how can i repack it? pack in img,ext4
and 2nd Q is that,
i create a zip file , from stock system,img,ext4 and after create with meta folder, during installation in end its says , end with error 7 etc
after i reboot so it take 5 minuts and after BB is unknown with null imei, why?
Mr Hassan said:
bundle of thanks brother i really really appricate your hard work, today XDA successfull coz XDA have your kind of peoples
brother its help me alot,
i want to know something , i extracted the lollipop rom , the format it system,img,ext4 ........now i change the some permissions
now i want to again repack the rom so how can i repack it? pack in img,ext4
and 2nd Q is that,
i create a zip file , from stock system,img,ext4 and after create with meta folder, during installation in end its says , end with error 7 etc
after i reboot so it take 5 minuts and after BB is unknown with null imei, why?
Click to expand...
Click to collapse
Sorry, but I don't know how to repack system.img.ext4, i have never made a rom before or edited yet, so i will be unable to help about that.
Error 7 generally occurs due to some wrong scripting in updater-script or by using incompatible update-binary.
You can share your updater-script here, so i can check it.
TheRoyalSeeker said:
Sorry, but I don't know how to repack system.img.ext4, i have never made a rom before or edited yet, so i will be unable to help about that.
Error 7 generally occurs due to some wrong scripting in updater-script or by using incompatible update-binary.
You can share your updater-script here, so i can check it.
Click to expand...
Click to collapse
thanks for reply, check it
Mr Hassan said:
thanks for reply, check it
Click to expand...
Click to collapse
Sorry for replying too late, I have been too much busy lately and that's why I haven't been using XDA since last 20 days.
I am sure you might have fixed the problem by yourself as it has been many days since you posted the above post.
Again just want to apologise for not being able to reply.
TheRoyalSeeker said:
Sorry for replying too late, I have been too much busy lately and that's why I haven't been using XDA since last 20 days.
I am sure you might have fixed the problem by yourself as it has been many days since you posted the above post.
Again just want to apologise for not being able to reply.
Click to expand...
Click to collapse
thanks for again your reply ,
now i,m in next step, kindly if you have time so please visit and share your experience
https://forum.xda-developers.com/android/help/repack-img-giving-error-odin-invalid-t3577719