Database Info

Success to port CM7 to XT701!

Hi guys!
I have successfully port CM7 to XT701
Here is the ROM
http://www.rayfile.com/zh-cn/files/6ac67519-7669-11e0-9deb-0015c55db73d/
Most of the functions work well.
But several problems are not fixed yet.
1.The camara focus and the flash work but when it save pictures. It will crash down.
2.The FM doesn't work
3.The DSP works but not so well
...
I think the xt720 xt701 xt711 have the same hardwares and systems. So I need cooperation to fix these problems. So if you want to help me or cooperate with me , just PM me.
Thanks

Good news, have you compiled cm from source or just ported from already compiled port?
Is there any journal about your work?
Will try to help with everything i can.

mirror plsss

videi\o please
Please post a video for proof!

mirror from Russia =)

So does this working xt720 as is? Idc if some stuff is broke I've been using miui and some stuff is broke but it works

Multiupload mirror:
http://www.multiupload.com/PQQ7SR57TE
I haven't tested it on XT720 yet. Stlifey's github is here: https://github.com/stlifey
BRB (hopefully), bleaching computer following RaySource.

I'm gonna try it out ill let u know how it goes

easye420 said:
So does this working xt720 as is? Idc if some stuff is broke I've been using miui and some stuff is broke but it works
Click to expand...
Click to collapse
Agreed. Not everything has to work, but I'll wait till the camera works before I try CM 7. The camera is one of the things I use a lot on this phone.

Great to hear this good news! As I know at the same time a new version of MIUI rom will also release soon.

fails....
code 4 aborted

hellmonger said:
fails....
code 4 aborted
Click to expand...
Click to collapse
I'm not going to have a chance to try this until next week (traveling, stupid work), but the updater script has a check for board name and refuses to install unless you're on choles. You should be able to unzip the files and edit META-INF/com/google/android/updater-script to remove this line:
assert(getprop("ro.product.device") == "choles" || getprop("ro.build.product") == "choles" || getprop("ro.product.board") == "choles");
Then delete the signature files META-INF/CERT.RSA META-INF/CERT.SF META-INF/MANIFEST.MF and rezip. It should then apply in OpenRecovery because it doesn't require signed updates.
Nevertheless, it probably won't boot until system/etc/rootfs/init.choles.rc is ported and merged with our init.mapphone_umts.rc to create a new system/etc/rootfs/init.mapphone_umts.rc
I think that's where we need to start anyway.

Mioze7Ae said:
I'm not going to have a chance to try this until next week (traveling, stupid work), but the updater script has a check for board name and refuses to install unless you're on choles. You should be able to unzip the files and edit META-INF/com/google/android/updater-script to remove this line:
assert(getprop("ro.product.device") == "choles" || getprop("ro.build.product") == "choles" || getprop("ro.product.board") == "choles");
Then delete the signature files META-INF/CERT.RSA META-INF/CERT.SF META-INF/MANIFEST.MF and rezip. It should then apply in OpenRecovery because it doesn't require signed updates.
Nevertheless, it probably won't boot until system/etc/rootfs/init.choles.rc is ported and merged with our init.mapphone_umts.rc to create a new system/etc/rootfs/init.mapphone_umts.rc
I think that's where we need to start anyway.
Click to expand...
Click to collapse
Please complete the rom to xt720/xt711
Sent from my XT720 using XDA Premium App

Mioze7Ae said:
I'm not going to have a chance to try this until next week (traveling, stupid work), but the updater script has a check for board name and refuses to install unless you're on choles. You should be able to unzip the files and edit META-INF/com/google/android/updater-script to remove this line:
assert(getprop("ro.product.device") == "choles" || getprop("ro.build.product") == "choles" || getprop("ro.product.board") == "choles");
Then delete the signature files META-INF/CERT.RSA META-INF/CERT.SF META-INF/MANIFEST.MF and rezip. It should then apply in OpenRecovery because it doesn't require signed updates.
Nevertheless, it probably won't boot until system/etc/rootfs/init.choles.rc is ported and merged with our init.mapphone_umts.rc to create a new system/etc/rootfs/init.mapphone_umts.rc
I think that's where we need to start anyway.
Click to expand...
Click to collapse
I noticed that too and you;re right i modified the Choles to Sholes pushed a Sholes config from another deleted certs reziped and did not boot...
Then i remembered the RAMDISK and of course right again the init.mapphone_umts.rc is different on xt701 so have to mod some more

hellmonger said:
I noticed that too and you;re right i modified the Choles to Sholes pushed a Sholes config from another deleted certs reziped and did not boot...
Then i remembered the RAMDISK and of course right again the init.mapphone_umts.rc is different on xt701 so have to mod some more
Click to expand...
Click to collapse
thanks for lookin at it. i took a look and i have no idea. hopefully you can get it working for us.

hellmonger said:
I noticed that too and you;re right i modified the Choles to Sholes pushed a Sholes config from another deleted certs reziped and did not boot...
Then i remembered the RAMDISK and of course right again the init.mapphone_umts.rc is different on xt701 so have to mod some more
Click to expand...
Click to collapse
This ROM uses a slightly "cleaner" hijack than what we've been using (this cleaner hijack seems to be widely used in the Milestone ROMs). If you're familiar with Dexter's XT720 hijack the translations are roughly:
Dexter: 2nd-init controlled by /system/bin/mod_boot_mode.p1.sh
Milestone: 2nd-init managed by /system/bin/sh_hijack.sh
Dexter: ramdisk updated for 2nd-init from /system/ramdisk.tar
Milestone: ramdisk updated for 2nd-init from /system/etc/rootfs/
On the recent Milestone ROMs (including nadlabak's CM6, CM7 and TheFroyoMOD) all the hijacks go through skrilax's /system/bin/sh which is what controls entry to OpenRecovery. /sytem/bin/sh will either boot openrecovery or execute /system/bin/sh_hijack.sh or simply continue with normal boot. On Dexter's ROM the sh_hijack pathway is not used for 2nd-init (Dexter used a mot_boot_mode hijack later in the boot process for 2nd-init instead)
I've been working on porting Dexter's 1.3 to use the sh_hijack.sh instead of mot_boot_mode thinking that will help port Milestone ROMs, but at the moment for some reason I can't get USB to work when using sh_hijack.sh. Probably something simple. But maybe these hints can help someone beat me to the punch.

go guys!!! i will support you!!!

hi guy,i have get a XT720 from a friend

stlifey said:
hi guy,i have get a XT720 from a friend
Click to expand...
Click to collapse
you got xt720? so did you try to port the CM7 to xt720? can you share your experience..

So is this Cyanogen Mod 7 with Gingerbread ??
probably with a port we can get gingerbread on our xt720 even if the bootloader is locked, right?

[Q] Include Bali Kernel in a ROM I'm building?

I'm attempting to build my first ROM and I'm curious how to add a kernel to the ROM.
(more specifically, Bali)
Any help is appreciated.

i cant answer your question, but if you need any help, let me know and i will help out any way i can

In updater script
Code:
set_perm(0, 0, 755, "/tmp/updates/redbend_ua");
ui_print("++ Installing kernel");
run_program("/tmp/updates/redbend_ua", "restore", "/tmp/updates/zImage", "/dev/block/bml7");
You'll need redbend_ua and zImage which you can find in the updates folder of other roms. I'd ask a dev if you can use them. I can't believe it's not butter uses them.

FBis251 said:
In updater script
Code:
set_perm(0, 0, 755, "/tmp/updates/redbend_ua");
ui_print("++ Installing kernel");
run_program("/tmp/updates/redbend_ua", "restore", "/tmp/updates/zImage", "/dev/block/bml7");
You'll need redbend_ua and zImage which you can find in the updates folder of other roms. I'd ask a dev if you can use them. I can't believe it's not butter uses them.
Click to expand...
Click to collapse
Alright, but before doing that...I'm getting an error when trying to flash the custom ROM in CWM.
E: Error in /scard/test1.zip
(status 6)
Installation aborted.
Any ideas?

http://lmgtfy.com/?q=cwm+status+6
First thread 3rd post

FBis251 said:
http://lmgtfy.com/?q=cwm+status+6
First thread 3rd post
Click to expand...
Click to collapse
Yeah I saw that, except I have no idea how to fix it.

If you use notepad++, open the updater script, go to Edit > EOL Conversion > Unix format. Do that for any other text files/scripts you have.

Thanks, but where is the updater script?
hahah sorry this is my first time making a ROM

META-INF\com\google\android\updater-script

Thank you!

DEODEX through recovery I9001 SGS+ | TUT HOW TO CREATE DEODEX UPDATE.ZIP

DEODEX Recovery *.zip - Files for KPU/KPS (see Point One) and BUKP2 - Vodafone (see Point Two)
Tested with FeaModRecovery1.2 / Android Sock-Recovery <e3> and I9001XXKPU / KPS / I9001BUKP2.
BACKUP YOUR PHONE THROUGH RECOVERY BEFORE DEODEXING (IF YOU HAVE FEAMOD) !!
USE IT AT YOUR OWN RISK. I WILL NOT BE RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR PHONE
ATTENTION: ALL YOUR APPS ON INTERNAL SD WILL BE DELETED! EXPORT THEM TO EXTERNAL SD!
Point One, updateKPU.zip for KPU /KPS 2.3.6
3 Apps are not included: GTalk, GMaps and GMail. If you want, you can download them through Android Market
https://rapidshare.com/files/129687079/updateKPU.zip
Point Two, updateVodafone.zip for BUKP2 2.3.5
All Apps (incl. Vodafone) included.
https://rapidshare.com/files/2200081853/updateVodafone.zip
I SWITCHED TO GALAXY NEXUS, SO I CAN'T TEST NEW DEODEXED PACKAGES. HERE IS A TUT "HOW TO CREATE DEODEX UPDATE PACKAGES":
1. The First thing you have to do is to download XUltimate 2.3.3
2.Connect your phone in debugging mode and run Main.exe from XUltimate.
3. Then run option 1 and 2.
4. If done, go to your XUltimate-Directory /origi_app. There are a lot apps without *.odex files.. Move them to another directory, you have created.
5. Do the same with the /origi_frame directory. There are two *.apk's without *.odex-Files in it.
6. Now run option 3 and 4.. If 3 fails, look for the app that causes the fail and delete it from /origi_app . Run 3 again until it completes deodexing.
7. Now place the moved apps from step 4 and 5 to /done_app and /done_frame.
8. Take one of my already done packages and open it with Win-RAR.
9. Now you can see 2 directories: /system and /META-INF
Go to /system/app and delete all *.apk's in it.
10. Copy all *.apk's from your /done_app (XUltimate) to /system/app (*.zip Package)
11. A new window from Win-Rar appears. Now you can choose your Compression Method. Choose Store . Then "OK".
12. Do the same with /system/framework (*.zip Package). Delete all files in it and copy all files from /done_frame (XUltimate).Compression Method: Store.
13. Move your Update.zip to your phone and install it via recovery
GOOD LUCK
YOU CAN ALSO EDIT THE UPDATER-SCRIPT FOR ONLY DEODEXING THE FRAMEWORK OR THE APPS:
(edit with notepad++)
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/system");
delete_recursive("/system/app");
delete_recursive("/system/framework");
package_extract_dir("system", "/system");
unmount("/system");
this code is for Sock-Recovery.. you don't need to mount /system, because the script will do it for you. It deletes /system/app and /system/framework.
After that, the script moves "update.zip/system/*/" to /system on your device.
if you only want to deodex the apps, use this:
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/system");
delete_recursive("/system/app");
package_extract_dir("system", "/system"); //delete uptate.zip/system/framework before. If you do not, the script will replace all framework files.
unmount("/system");
DO NOT WRITE:
package_extract_dir("system/app", "/system");
It will move the content update.zip/system/app/ to /system on your device. I don't think you want *.apk Files in the /system directory :-D
If you have seen the mount command with 3 arguments before, don't worry the reason for this is the updater-binary file.

Hi, i can't get thru megaupload it's broken or something can you fix it or place the zip files here? Thanks..
Sent from my GT-I9001 using xda premium

Links working here. Downloading at the moment, will try later or tomorrow.
Gesendet von meinem GT-I9001 mit Tapatalk

fadzlihellmuth said:
Hi, i can't get thru megaupload it's broken or something can you fix it or place the zip files here? Thanks..
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
megaupload is working now sorry cant place 'em here cuz the max. size is 11,8 MB @ *.zip

Nice, i try to deodex before via pc but cant place the deodex file to phone....
|:BroodRom RC2 Beta
|:Instanet Free Access (no one believe its free)

wow，nice work!
I'll try them later, Thanks a lot!

Just a little warning, these are the deodexed apps and frames from a specific ROM. So if you want to deodex that ROM you'll be fine, but if it's another ROM that may have some additional or changed apps and frames, you will miss some features of that ROM...right?

nikagl said:
Just a little warning, these are the deodexed apps and frames from a specific ROM. So if you want to deodex that ROM you'll be fine, but if it's another ROM that may have some additional or changed apps and frames, you will miss some features of that ROM...right?
Click to expand...
Click to collapse
testet on kpu

it's working very nice!
Sent from my GT-I9001 using xda premium

alex1226 said:
it's working very nice!
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
On which version of android?
Sent from my GT-I9001 using Tapatalk

xxkps .working fine!

Hi! would it work on this? the phone is rooted of course:
PDA: I9001BVKPA
PHONE: I9001BVKPB
CSC: AMNKPB
Thanks!

lusagad said:
Hi! would it work on this? the phone is rooted of course:
PDA: I9001BVKPA
PHONE: I9001BVKPB
CSC: AMNKPB
Thanks!
Click to expand...
Click to collapse
I doubt it - please use the manual way through xUltimate to deodex your ROM

Ok, thanks for your advise. After a secured backup, I'll "deodex" manually an original rom.
A más ver, L.
See you later, L.

Is this working on zskp6? Or xxkps is better?

megaupload link is broken , please provide another link

laurcapa said:
megaupload link is broken , please provide another link
Click to expand...
Click to collapse
not very strange since megaupload has been banned from the internet ^^ (DAMN YOU SOPA/PIPA)

I know , that is why this thread is useless without another link to the package

Okay links updated.
Added a tutorial.

I want to flash my SGS+ with XXKPU (csc XEO) and use broodROM Configurator.
Main requirements for broodROM Configurator are XXKPU (checked), root (checked) and deodexing.
My question is: can I use the zip from the first post (point one) to obtain a dexodexed XXKPU?
Also, can you confirm that this update (zip file) can be applied using stock XXKPU recovery (boot recovery, update from file, restart) ?
Thanks.

[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

META-INF problem.. N7100 ROM making..

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