META-INF problem.. N7100 ROM making.. - Galaxy Note II, Galaxy S III Developer Discussion

Hi everyone..
I'm new for android developing, so it is my first attempt in making a ROM..
So my problem I'm pretty sure it is in META-INF folder..
After I have configured aroma installer things, and everything is done in the ROM.. I tried to flash it but it gives an error (which means aroma installer did not start) , I saw the log but it seems like it didn't flash anything, it just gave that there is an error in the zip.. So it's a META-INF problem..I think..
So anyone have an idea of what I forgot to do?
Sorry If this the wrong section..

What error does it give? Can you post the recovery.log?
Also, make sure you do not replace the update-binary with one for your device because that one is a modded binary that starts up AROMA. You CAN, however, replace the update-binary-installer with the update-binary for your device (renaming to update-binary-installer of course), because thats the one that actually gets called by AROMA to parse your updater-script
And if you have signature checking enabled did you make sure to sign it?

APK
CNexus said:
What error does it give? Can you post the recovery.log?
Also, make sure you do not replace the update-binary with one for your device because that one is a modded binary that starts up AROMA. You CAN, however, replace the update-binary-installer with the update-binary for your device (renaming to update-binary-installer of course), because thats the one that actually gets called by AROMA to parse your updater-script
And if you have signature checking enabled did you make sure to sign it?
Click to expand...
Click to collapse
I have got a zip file after unpacked got the apk whiche I need then added the apk to system.img , but the apk can't run after I have installed the ROM , I think cuz of the META-INF folder problem still don't know how to solve it

chaselxm said:
I have got a zip file after unpacked got the apk whiche I need then added the apk to system.img , but the apk can't run after I have installed the ROM , I think cuz of the META-INF folder problem still don't know how to solve it
Click to expand...
Click to collapse
you ve got to check your updater and aroma installer for typos.
Even a comma prevent aroma form starting.
You have to keep in mind that recovery first run all scripts inside aroma and then display them unless you make an option error whch will gives you the error right befor page display..
A common issue to most new builders is the comma on all options of aroma.Last option has to end without it..
As pervious said you have to provide the error number.
Hope that helps

thanks
that's great

Mohammed779 said:
Hi everyone..
I'm new for android developing, so it is my first attempt in making a ROM..
So my problem I'm pretty sure it is in META-INF folder..
After I have configured aroma installer things, and everything is done in the ROM.. I tried to flash it but it gives an error (which means aroma installer did not start) , I saw the log but it seems like it didn't flash anything, it just gave that there is an error in the zip.. So it's a META-INF problem..I think..
So anyone have an idea of what I forgot to do?
Sorry If this the wrong section..
Click to expand...
Click to collapse
paste the log?
---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------
sotmax said:
you ve got to check your updater and aroma installer for typos.
Even a comma prevent aroma form starting.
You have to keep in mind that recovery first run all scripts inside aroma and then display them unless you make an option error whch will gives you the error right befor page display..
A common issue to most new builders is the comma on all options of aroma.Last option has to end without it..
As pervious said you have to provide the error number.
Hope that helps
Click to expand...
Click to collapse
it sounds like a binary problem aroma runs the updater script through aroma, but if aroma doesnt even start it would have something to do with aroma-config or corrupt aroma binary

Related

[Q] Editing zip before flashing a ROM

I know I have done this before and this is a noob question, but lately I've been having trouble with this.
If I make changes to the zip file of a ROM (eg replace a few existing files, and remove some unwanted system APKs, but not add anything new), do I need to sign the zip before flashing or just flash straight after editing? Also what's the best tool to use to replace the files within the zip? I trust WinRAR will do the trick...
djsubtronic said:
I know I have done this before and this is a noob question, but lately I've been having trouble with this.
If I make changes to the zip file of a ROM (eg replace a few existing files, and remove some unwanted system APKs, but not add anything new), do I need to sign the zip before flashing or just flash straight after editing? Also what's the best tool to use to replace the files within the zip? I trust WinRAR will do the trick...
Click to expand...
Click to collapse
I've never added anything (yet!), just deleted un-wanted APK's and altered some system files (ie build,prop etc). I've never signed anything and I used IZArc although only as that's what's installed on my XP system.
This is something that I too would like to do more so that I can further personalize and tweak some of these already great ROMS, so I'm also curious for some pointers from more the experienced.
Check the portal, there's an app to create flashable zips there.
PS - POST QUESTIONS IN THE GENERAL SECTION !!!!!!!!
You can set a flag in recovery to check for signatures or not. When it is not set you can flash any zip file
Sent from my HTC Desire S using XDA App
jorgen2009 said:
You can set a flag in recovery to check for signatures or not. When it is not set you can flash any zip file
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
I tried this once, and then I flashed the zip. It was a CM7 zip which would normally take at least 20-30 seconds to complete, but this modified zip flashed in less than ten seconds. It said successfully flashed but when I rebooted nothing had actually happened. Hence I was wondering what went wrong?

[Q] :)

i've got a big doubt.........does the updatescript in meta inf folder depends on the apps in the apps folder????? or is it just enough to copy the meta-inf folder from any other rom??? (if im trying to mod an a system app)) plz do help me!!
D33J3Y said:
i've got a big doubt.........does the updatescript in meta inf folder depends on the apps in the apps folder????? or is it just enough to copy the meta-inf folder from any other rom??? (if im trying to mod an a system app)) plz do help me!!
Click to expand...
Click to collapse
i am not a genius on this, but upon seeing what is "inside" updatescript, it's more or less a program that dictates which installs, like say, the boot.img, or the busybox.... but of course i can be wrong...
---------- Post added at 01:09 AM ---------- Previous post was at 01:03 AM ----------
D33J3Y said:
i've got a big doubt.........does the updatescript in meta inf folder depends on the apps in the apps folder????? or is it just enough to copy the meta-inf folder from any other rom??? (if im trying to mod an a system app)) plz do help me!!
Click to expand...
Click to collapse
you can try to read this though...
According to Geekfor.Me
"This script is required for an “update.zip” style flash in Android so that it knows what it is actually supposed to do."
D33J3Y said:
i've got a big doubt.........does the updatescript in meta inf folder depends on the apps in the apps folder????? or is it just enough to copy the meta-inf folder from any other rom??? (if im trying to mod an a system app)) plz do help me!!
Click to expand...
Click to collapse
Hi!
The META-INF/com/google/android/update-script file inside an "update".zip archive is just a normal text file you can open with any text editor and edit it to your needs. It doesn't depend on any files, so you can safely copy it from another CWM update.zip file and put it in your newely created update.zip file for CWM flashing. Oh, and "update-binary" is also in the same folder as the "update-script" is.
The "update language/syntax" is a little bit strange, but nothing major to fuss about.
Hope you can do it!
reikableu said:
i am not a genius on this, but upon seeing what is "inside" updatescript, it's more or less a program that dictates which installs, like say, the boot.img, or the busybox.... but of course i can be wrong...
---------- Post added at 01:09 AM ---------- Previous post was at 01:03 AM ----------
you can try to read this though...
According to Geekfor.Me
"This script is required for an “update.zip” style flash in Android so that it knows what it is actually supposed to do."
Click to expand...
Click to collapse
thaanks for that link!!
yani2000 said:
Hi!
The META-INF/com/google/android/update-script file inside an "update".zip archive is just a normal text file you can open with any text editor and edit it to your needs. It doesn't depend on any files, so you can safely copy it from another CWM update.zip file and put it in your newely created update.zip file for CWM flashing. Oh, and "update-binary" is also in the same folder as the "update-script" is.
The "update language/syntax" is a little bit strange, but nothing major to fuss about.
Hope you can do it!
Click to expand...
Click to collapse
so i guess the updater-script works for ext4 partitions and update script for .rfs....right?

[MOD] DSIXDA kitchen v0.202 updated tools 24.09.2012 NEW option to use SuperSU NEW

1st post: updates by others
2nd post: updates by me
I present you my package of recent updates for DSIXDA kitchen v0.202
This package is for Windows, Linux and Mac.
To use the updates, replace kitchen files with files from package.
Dk202u23092012; this package includes:
* added support for endeavoru credits to theintelligent
* updated wireless tether to v3.2-beta2 credits to harald
* updated busybox to v1.20.2 credits to Denys Vlasenko
* updated Superuser to v3.2-RC3 credits to ChainsDD
* updated zipalign to vR20.0.3 credits to Google
* updated apps2sd to v2.7.5.3 Beta 04 credits to tkirton
* updated unyaffs to v0.9.4 credits to ehlers
Click to expand...
Click to collapse
I take NO credits for these tools, only for sharing my package with the community, happy cooking!
Here you'll find experimental mods made by me. Please test it and give me some feedback.
NEW em2Dk202u24092012; this package includes:
* NEW added option to root your rom with chainfire's SuperSU v0.96 NEW
* removed option "old" incl. Superuser.apk and su binary
Click to expand...
Click to collapse
To use this update, replace su_files folder and do_root file from your kitchen with su_files folder and do_root file from package.
Plz test and report me back, enjoy!
emDk202u24092012+; this package includes:
* added support for primo aka HTC One V
* added support for ville aka HTC One S
Click to expand...
Click to collapse
To use the updates, add files from package in kitchen folder.
Remember these updates are experimental! I don't own these devices so can't test them myself!
I hope this helps you !:angel:
updated post 2, enjoy!
I can use this to build for the Samsung galaxy tab 2 7.0
Sent from my SGH-T679 using Xparent Blue Tapatalk 2
hatememarkz said:
I can use this to build for the Samsung galaxy tab 2 7.0
Sent from my SGH-T679 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Samsung Galaxy Tab 2.7.0 not supported yet...
updated 2nd post, added a great new experimental option! plz test it and give me feedback.
i dont know what im doing wrong here.. im getting this error
E: Error in /sdcard/Arquivo/roms/MIUI_X/MIUI_X_2.9.21_RC1.zip
(Status 6)
Installation aborted.
ill descrive my steps
1. Copyed endeavoru (without .txt extension) to tools/edify_defs/
2. Extracted ROM and converted updater-script to update-script like kitchen recomends
3. Made my changes
4. Builded ROM in interactive mode (1) in kitchen
5. Kitchen converted automaticaly to updater-script
6. Selected option "Proceed: updater-script and update-binary will be moved to the ZIP file.."
7. sign, copy to phone, etc
and when i go to flash it, i got that error ...
im using your kitchen...
this in HTC ONE X (enderavou)
any clue about this ?
3. Made my changes
Click to expand...
Click to collapse
What changes? tell me in detail plz
im using your kitchen...
Click to expand...
Click to collapse
not mine, kitchen owner is DSIXDA
l3inky said:
What changes? tell me in detail plz
not mine, kitchen owner is DSIXDA
Click to expand...
Click to collapse
nothing special ... deleted some apks in system/app (bloatware) and added some (gaaps) and edited build.prop with notepad++ just to change timezone
sorry .. your kitchen mod
im going now to build and untouched rom .. just to see if the problem is from my changes .. but i didnt changed anything special .. so i supose thats not the problem .. but just in case.. im going to test it ..
im going to extract the rom "miuiportugal_OneX_2.9.21_Signed.zip" and build it with kitchen defaults
convert updater like it recomends on extract..
and convert again to updater in building like it recommends
just to see if the problem is in the kitchen or my changes
---------- Post added at 07:48 PM ---------- Previous post was at 07:24 PM ----------
same problem .. same error ...
didnt change anything this time ...
just extracted rom and build it again with kitchen defaults
dont understand .. kitchen recognizes the device when converting scripts ...
maybe because the source rom its MIUI ? i tryed miui eng / pt / ch / rd .. and same problem ..
maybe java path invalid (\Java\jre7\bin) dont know if kitchen uses java ..
maybe cygwin version ?
lol .. what a strange thing ... do i need to change more files in kitchen ? i just downloaded the last kitchen release and applyed your mod ...
btw i founded this on changelog
Version 0.190 (March 26, 2012):
Change end-of-line characters in update(r)-script to proper format when building ROM. This gets done in case a noob modified the file with non-Unix compliant editor. Prevents 'Status 6' error when flashing ROM in custom recovery.
but it doesnt make sense because im not doing edits and i dont have < 0.190 kitchen
ruizit0 said:
nothing special ... deleted some apks in system/app (bloatware) and added some (gaaps) and edited build.prop with notepad++ just to change timezone
Click to expand...
Click to collapse
You don't need the kitchen for these changes mate!
+ I don't know what goes wrong with you, aosp and kitchen not a good match i guess
Mayb you can contact dsixda for your problem but again, if these are the only changes you wanna make you don't need the kitchen!
l3inky said:
You don't need the kitchen for these changes mate!
+ I don't know what goes wrong with you, aosp and kitchen not a good match i guess
Mayb you can contact dsixda for your problem but again, if these are the only changes you wanna make you don't need the kitchen!
Click to expand...
Click to collapse
yeah i know .... but i dont plan to make only that changes
it was only to test the kitchen ... i cant contact dsixda he stopped development of the kitchen :\
dont know what to do .. do you have an HOX ? i need to find someone with an hox to zip me the kitchen folder and send me just to see if it works ... or if its from my computer setup ...
i installed everything with a tutorial i saw here on forum .. maybe it wasnt the best tutorial to setting up the kitchen .. dont know :| damn
just in case someone can give me a clue...
here's some info and logs .. i think kitchen is converting wrong the updater-script... but why .. i dont know.. differente HOX versions ?
the part of flashing
Code:
-- Installing: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Finding update package...
I:Update location: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Opening update package...
Installing update...
line 4 col 20: syntax error, unexpected STRING, expecting $end
1 parse errors
E:Error in /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
(Status 6)
Installation aborted.
and here's the full log
https://www.dropbox.com/s/f5b97a4tt2rlbqu/recovery.log
and here's the updater-script created by the kitchen
https://www.dropbox.com/s/7h8wl5a5vizen08/updater-script
For now use this workaround: when rom is builded replace meta inf folder with original, when im home i,ll take a look at it.
Sent from my HTC One X using xda app-developers app
l3inky said:
For now use this workaround: when rom is builded replace meta inf folder with original, when im home i,ll take a look at it.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks l3inky!
detailed problem in here if you can check logs and specs etc
i didnt mentioned your mod in there to not cause more confusion .. but using your mod or not, the problem is the same, so the problem is not from your mod
http://forum.xda-developers.com/showthread.php?t=1906605
thanks again
Can u plz send me this: original updater-script, converted update-script and final updater-script.
Problem solved thanks to "backfromthestorm" hint!!
The problem is the Kitchen update to updater conversion.
The kitchen doesnt make correctly the conversion.
So the solution is:
not give any script to kitchen for conversion, remove META-INF folder from original zip and let kitchen create a fresh updater..
It doesn't fix the converting problem does it, also very interesting you prefer removing meta inf en make a new one then just changing 2 lines in updater script, 2 workarounds in my opinion, anyway can u send me those 3 files i asked for cause i wanna fix this problem.
Sent from my HTC One X using xda app-developers app
l3inky said:
It doesn't fix the converting problem does it, also very interesting you prefer removing meta inf en make a new one then just changing 2 lines in updater script, 2 workarounds in my opinion, anyway can u send me those 3 files i asked for cause i wanna fix this problem.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
you are right .. but i prefer to create a new one because its less work, i have to remove the ui_print and other symlinks, so for me its easyer create a new one.
but the perfect is if the kitchen can make correctly the conversion ...
here it is what you asked
https://www.dropbox.com/s/7fd3kboz0htiur7/updaters.zip
it will be great if you can fix that.. if you need something from me just ask!
thanks
made another test .. but this time with other rom...
the kitchen converts the updater bad again but with other errors ..
this time it add spaces to lines
here is the files from the another test ...
https://www.dropbox.com/s/vim2rpgrgmij3j9/updaters_2.zip
the kitchen is all messed up when converting updater .. i think the best is to stick to the original updater dont make conversion and make manual changes on the end ..
and hope DSIXDA gets back to kitchen development, or maybe someone makes another kitchen and give support to it :\
EDIT: found some bugs when removing META-INF folder from original zip and let kitchen create updater by his own .. for example in MIUI rom some functions stop working ... like theme applying etc... i think kitchen jumps something maybe permissions .. when creating updater
for now, and for me, the best option is to let META-INF in original zip, and when extrating rom when kitchen asks to convert updater to update, dont convert, and after edit original updater mannualy and make the changes
ruizit0 said:
made another test .. but this time with other rom...
the kitchen converts the updater bad again but with other errors ..
this time it add spaces to lines
here is the files from the another test ...
https://www.dropbox.com/s/vim2rpgrgmij3j9/updaters_2.zip
the kitchen is all messed up when converting updater .. i think the best is to stick to the original updater dont make conversion and make manual changes on the end ..
and hope DSIXDA gets back to kitchen development, or maybe someone makes another kitchen and give support to it :\
EDIT: found some bugs when removing META-INF folder from original zip and let kitchen create updater by his own .. for example in MIUI rom some functions stop working ... like theme applying etc... i think kitchen jumps something maybe permissions .. when creating updater
for now, and for me, the best option is to let META-INF in original zip, and when extrating rom when kitchen asks to convert updater to update, dont convert, and after edit original updater mannualy and make the changes
Click to expand...
Click to collapse
You probably have a problem with mount points & update binary. Make sure your device is supported by kitchen else manually create edify_defs for your device or Replace update binary in kitchen cooked meta inf folder with the one from original rom and edit kitchen updater script - change the lines with mount(...........) in new updater script to look exactly like the one in original rom's updater script. You can search xda forum for more info on edify language used in updater scripts. Most of changes you need make in updater sript will be within first 5lines. You can pm me if problem but also post response here
Sent from my GT-B5512 using Tapatalk 2

Need some help regarding Odex Files and corresponding apks

Hi guys, I got this problem in my odexed stock rom, I have this problem in sysui, gallery and calculator.
I downloaded 4.2.2 style sysUI, pushed it in the respective folder by replacing with its stock sysUI.
I rebooted my core, the statusbar was gone, so I deleted 'SystemUI.odex" file, then rebooted it worked!
In the same way, I replaced stock gallery with note3 gallery, and stock SecCalculator2
Luckily note3 gallery worked, but it doesn't support Sim2 so I can't change Sim2's wallpaper or make it same as Sim1's.
In the statusbar, I can't see most notification cuz its completely transparent, and also its a bit laggy.
Calculator never worked
So I wanted to replace these with stock, when I pushed it in system>apps> I noticed that there were no .odex files for .apks
I replaced them with their stock odex files, none of 'em worked, I guess cuz of the odex thing, so I again deleted odex files and rebooted, nothing worked..
Now, I need some developer's advice, plz don't tell me to "Flash Stock Rom via Odin" I can't do it...
Is there any other left way to make them work plz I need help..
You are saying 'in my deodexed rom' and then you said 'deleted. Odex file for systemUI'
How could this be possible?
If you have .Odex files in system/apps folder then your ROM is not odexed.
Deodex it first using xUltimate tool
And yup Don't forget to set permissions = rw--r--r--
M_E_G_A_T_R_O_N said:
You are saying 'in my deodexed rom' and then you said 'deleted. Odex file for systemUI'
How could this be possible?
If you have .Odex files in system/apps folder then your ROM is not odexed.
Deodex it first using xUltimate tool
And yup Don't forget to set permissions = rw--r--r--
Click to expand...
Click to collapse
Sorry bro, huge typo. I meant in my odex rom and yes I set the proper permissions...
Well, it seems to me that you have messed up your phone alot.. Flashing stock rom via odin would've been the correct solution to this problem. It's not as difficult as you think, and you're capable of doing it. Follow thecoreguy's tutorial for that.
CoreGuy said:
Sorry bro, huge typo. I meant in my odex rom and yes I set the proper permissions...
Click to expand...
Click to collapse
Then you have done wrong.
Not every apk can be used by just deleting the .odex file.
You need to deodex the apps in system/app and system/framework folder then you can easily replace the apks.
1.First restore back to any working backup.
2.Download xUltimate Tool.
3. Run it.
4. Then just run commands with options 1,2,3,4 (You just need to type 1 and then enter, then 2 and then enter, so on upto option 4.)
5. Exit after executing 4th option.
6. Download ADB tool(don't download the complete package, you will get a 1-2MB ADB.exe from the from itself) - Use it to push the deodexed files made from xultimate.
---------- Post added at 09:47 AM ---------- Previous post was at 09:22 AM ----------
If you find it difficult then Better you upload the apks with their respective odex file. I will deodex those apks
M_E_G_A_T_R_O_N said:
Not every apk can be used by just deleting the .odex file.
Click to expand...
Click to collapse
Not even the stock apks? I want to replace the ported/modded apks with the stock ones..
No you can't because almost all stock apks have their respective odex files and every odex file contains resources that are needed to run those apks. Also there exists dependencies in system/framework folder. So just deleting odex file won't work all time.
Finally got it! Special thanks to megatron
Solution if u r screwed in my situation: don't panic, what I found why I cant do it was bcuz my phone has dat "newest" update of samsung ota. So b4 u take someone's apk and odex file always cross check this(image)
And then you are gud to go!!! U wont even need to restart it'll come automatically(my dad has same phone and same updated version as mine so I copied everything needed frm his phone to mine) @AnsleyC at times, the answer should not be "flash stock rom via ODIN" if u have a crappy pc, u can either repair faulty parts(easier and efficient) or buy a new one(bullcrap)
Have fun everyone!
Sent from my GT-I8262 using XDA Premium 4 mobile app

[Resolved] [FIX]Status 7 error while installing ROM & GApps

I do not take responsibility if you brick or break or do whatever with your phone , iam just trying to help those who follow the instructions carefully :good: you are doing this on your own risk! (though the chances of bricking your phone with this are extremely low) aaand the chances are that you are here cuz u bricked ur phone XD
Hi guys this is my first post on xda hope you like it
Now, we all "flashers" must have come to an irritating point of life (status 7) which doesn't seem to fix itself, well, here to help!
For status 7 while flashing ROM:
1.open the rom zip using a zip file explorer (preferably winrar or 7zip)
2.go to this directory: >>META-INF>>com>>google>>android>>update-script and open using note-pad++
3.Delete the line which says assert (getprop) bla bla (you will figure out where it ends) remember to remove the whole line or until where the assert ends
4.click save, transfer file to phone and it should work with no status 7 error (a status 6 error might occur write it in the comments if it does)
now,why did that status 7 error occur?
the answer is that status 7 means that the rom was not made for your phone , the assert line checks the model no. and even though it the rom might have been made for your phone but sometimes it happens cuz of simple typos by devs.
for status 7 while flashing GApps
1.open the GApps zip file using a file explorer (preferably winrar or 7zip)
2.go to this directory: >>META-INF>>com>>google>>android
3.see that update-script file? thats the bug. REPLACEit with thismg xda wont let me put links cuz i need atleast 10 posts rlly :crying: try to find a file on google called update bin. cheers and good luck!:good::good:
4. thats it! it should work now.
now why was it now working?
because you had an older phone/version of recovery which used an older version of decoder and instead of changing your whole phone we just changed a little file that is the older version of the decoding file.
thanks and yeh itz my first post so plz upvote :3 :fingers-crossed:

Categories

Resources