Related
Hey Guys,
Yet another sleeples night, looking at something that is probably simple and getting no where.
THE PROBLEM:
APPARENTLY you can change a CAB file into an OEM so that it can be used in Pandora Kitchen, the kitchen thread says its possible, but doesnt really give directions as to how.
Considering this is a new thing to, and there is no info about this on the site (that i can find)
Can someone please tell me step by step how to do this, and by step by step i mean:
1).................
2).................
3).................
4).................
etc etc
Thankyou for your help in advance
Here is a test package I made, but I keep getting a registry errors. Maybe someone can tell me what im doing wrong. I think it was better to keep all this in the kitchen thread personalley but as long as I can figure this out I dont really care.
Extract this file and take the "Remote Desktop" dir and drop it in the OEM dir in the Kitchen, and it shows up and all but when you go to build with teh green arrow I get a registry compiling error.
I also attached the original cab file that I started with when attempting to create this package.
Also attached is the cab manager that Matt uploaded, I am sure its the same as the one posted above but this has a readme and what not.
First Matt told me this:
Using this tool (many out there, this one's free and does a good job), extract the cab to a folder, then click on XML and grab the .rgu contents. Be wary of the format, as you have to delete any spaces between entries, such as "biteme" = dword : 00000001 should read "biteme"=dword:00000001.
Also, ensure that any path in this file (file system, not registry) is in this format: "\\Windows\\Startup" The second slash is required. Also, remove any references like %ce%\Windows, just change it to "\\Windows". You'll get the idea. If it ain't right, BuildOS will fail while creating the registry.
Move all the files into the top level in the folder you made, and remove all the extra crap like the inf file, and sometimes there's an xml file there too - note that you may need to convert to a provxml if the settings in it are required.
Use this site http://www.famkruithof.net/uuid/uuidgen (verion 4) to get a new GUID. I'd suggest coping a .rgu and options.xml file from another package since the file has to originate a certain way - and only use notepad to edit.
Just follow the example in the other packages - you'll find just about every way to do things in there.
As far as more details on using the program, just play with it. It's pretty simple
Then Bennec83 told me this:
what exactly are you trying to do? extract a CAB? if you are, using the file i uploaded earlier:
1)Launch CAB Manager.exe
2)on main screen extract CAB to a folder
3)click on the XML tab in top bar of the main window of CAB Manager.exe
4)in the window that opens, select Registry Keys
5)copy everything from the screen into WORDPAD
6)remove all the spaces
7)save the file as "UNICODE", once saved change the extension to somename.rgu
if you are trying to add an OEM to this kitchen i dont think you can just add them, please correct me if im wrong.
i hope this helps, if not tel me abit more about wat u want to do n ill try to help abit more!!
I understand the INF file as well, I just dont know how to add multiple directories as the destinations for a package, when a cab inf will tell you where there all suppost to go.
--Update--
I removed the NON-WORKING package, as it is now obsolete, see post below I got it working.
Ok then I understand the logic, and then the proper elaborated instructions can be pasted at the first or second topic of the Kitchen thread.
So I guess im doing something wrong with the reg, I have tried it a bunch of diffrent ways by comparing it to existing packages but I still cant seem to get it.
This quote by matt is what leads me to believe that.
Also, ensure that any path in this file (file system, not registry) is in this format: "\\Windows\\Startup" The second slash is required. Also, remove any references like %ce%\Windows, just change it to "\\Windows". You'll get the idea. If it ain't right, BuildOS will fail while creating the registry.
Ok I did it, I was reading an old post of bepe's and he said "add the reg to the end of the file (and the last line must be empty)" and so I hit enter and left the last line blank and BAM it worked so here is my first package contribution.
Maybe you can start adding these to the first post and we can start to make a collection for matt to add and test with his kitchen ?
Here is another one HTCustom 1.7 ready to go package for the kitchen
Damned if I can work it out!
Can anyone please package any of the following cabs?
Ive added JUVS HTC Home because the one included in the kitchen has the coloured icons not the original b&w.
Many many thanks in advance
I am still not able to completly figure out how to make a package where you must put files in diffrent locations other then the windows folder ? I would veyr much like to figure this part out.
I dont think he's having a go at you - he's just as frustrated as you and I with this. I would love to be cooking my own roms and with the wonderful pandoras kitchen I am getting alot further along but I guess I got a lot further to go!
well, by searching you can find how to do this!!!
click on this ftp://xda:[email protected]/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
this pdf file got what you need!!
under "Making a Package from a CAB file"
Look here bennec83, the comment i made was not meant to be a flame at all. If anything, it should have helped you alot with what you were trying to accomplish with the program and, making packages. I mean how much more direct can i be with helping you? As I said to you before, yes some of the chef can be a little vague with explaining the "How To's" of cooking or anything else, but that still didnt stop my progression of learning what i wanted to learn on here. What i explained in the CORE's Kitchen thread, was basically 80% self taught thru reading post & threads on xda, google searching, and trial and error. The other 20% was thru xda forum members input. I have a basic understainding of computers with no type of programming skills, and yet still, i was able to grasp the concept of cooking roms and making packages. Yes sometimes you have to put 2 and 2 together to figure things out on here. How I did it was I looked inside CORE's additional OEM packages and noticed that the files inside all the oem were extracted into the root of the folder's Dir...ok..so I would assume that you spent considerable amount of time trying to figure out that OEM package program(inside CORE's Kitchen its called Cab Analizer), then i would assume that you know that it extracts files within a .cab...ok... with that given....if you look back into an already made OEM package and many others, you'll notice that most ,if not all, carry an "initflashfile.txt"(which i figured out the correct data input) and many packages also carry .rgu & dsm files, so guess what....you need to find out what are .rgu & .dsm files, and there functions(if know no ones whats to tell you in a timely manor then, search or google, like i did!) Once you learn about those then, you'll notice that the OEM package program you have infront of give information about the reg keys of the cab (if available), then you start putting 2 & 2 together! You mention in your quotes that the programs sucks ass, well that program is a key part in making packages, If you can find a better one, please let me know!
NightmarE said:
well, by searching you can find how to do this!!!
click on this ftp://xda:[email protected]/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
this pdf file got what you need!!
under "Making a Package from a CAB file"
Click to expand...
Click to collapse
thankyou so much for this, i actually know what to do now i really appreciate this. you dnt know how much!!!
thanks alot
chrisnash said:
I dont think he's having a go at you - he's just as frustrated as you and I with this. I would love to be cooking my own roms and with the wonderful pandoras kitchen I am getting alot further along but I guess I got a lot further to go!
Click to expand...
Click to collapse
you are right that wasnt flamage!! i have been lookin so long in this forum i totally didnt think the answer would be in the wizard forum.
i have read and understood the instreuctions here:
ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
i just wish i cud have found it earlier
perhaps I'm an utter fool, but I'd like some clarification from those of you who understand this, mind you I do have Faria's PDF:
1) For a .cab with purely registration files (ie, the Cingular WAP Settings) that contains a .inf when extracted, all I would need is the .rgu to put into BuildOS, right?
2) The .dsm file (and iniflashfiles) are only needed if the .cab is an actual application, and the .dsm file that you create can very well be empty (from what I understand from Faria's rom).
Maybe it's a lack of sleep, but I'm just not getting my head around this and am so far using the Install Cabs feature from HTCustom 1.7 after flashing.
I was trying to do the cignular settings and It seemed to me that all those reg entries appear like blank er something was wrong with them, I could be wrong but thats what it appeared like to me.
Bennec, ok then bro, my mistake, I guess I shouldnt of assumed that post was directed towards me, it just felt that way and I know you were frustrated.
Lets make this the best CAB to OEM Package thread ever and start a collection on the first post, also with all you have learned now, have you figured out a way to make a package with a cab like opera where the files must be placed in to diffrent dirs ?
where are you all stuck at?
to move files to a different directory you need to use initflashes. Keep in mind that this copies it to a different directory not actually moves it. The original file will still be in \\windows
If all you want is to add registry entries, add them to an existing packages registry entries. If you create a new package for the registy entries it should have a dsm file as well.
If you want the check box in buildos you will need to create an option.xml file as well.
bennec83 said:
you are right that wasnt flamage!! i have been lookin so long in this forum i totally didnt think the answer would be in the wizard forum.
i have read and understood the instreuctions here:
ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
i just wish i cud have found it earlier
Click to expand...
Click to collapse
I'm glad you found the info you need, and are on your way to making progress. I apologize for not being able to assist more than I did, but I've got my hands full getting v3 ready for release.
Good luck and happy packaging!
NYD - long time, no see!
goto the CORE's kitchen thread. Read my posts and familiarize urself with a program called "compare it". Use this program to compare ur registry when the app is freshly installed, to the registry without the app installed, and pull the reg keys that way!
mattk_r said:
I'm glad you found the info you need, and are on your way to making progress. I apologize for not being able to assist more than I did, but I've got my hands full getting v3 ready for release.
Good luck and happy packaging!
NYD - long time, no see!
Click to expand...
Click to collapse
I understand you have lots to do on your kitchen, congrats BTW!! amazing kitchen, how is touch flo goin?
notyourdaddy said:
where are you all stuck at?
to move files to a different directory you need to use initflashes. Keep in mind that this copies it to a different directory not actually moves it. The original file will still be in \\windows
Click to expand...
Click to collapse
Hmmmmmm.
So its not possible to cook a Rom with custom apps in Progam Files only? I mean if they are always in \\windows too then its better to install the files than to cook it in the rom.
I have always believed you should add as little as possible to Rom:
From Tadzio's 'Want more Storage' Thread.
tadzio said:
...clip...
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size.
...clip... make a ROM as small as at all possible, removing anything that users may not want, and turn every removed feature into a .cab that users can install to Storage...clip...
Cheers
Daniel
...clip...
Click to expand...
Click to collapse
So I'm trying my luck at ROM creation and am learning as much as I can. One thing I haven't been able to find through Googling etc is how to port a ROM from one device to another, or more specifically what folders/files need to be replaced in a ROM to make it work on another device?
Appreciate any guidance, thanks guys!
PS I'm using DsiXDa's Kitchen, but it "doesn't support any devices besides HTC devices" and I want to port a ROM to a Dell Streak from an HTC Nexus One. Is it even possible and what files can I manually replace to get it to run?
dcogen said:
So I'm trying my luck at ROM creation and am learning as much as I can. One thing I haven't been able to find through Googling etc is how to port a ROM from one device to another, or more specifically what folders/files need to be replaced in a ROM to make it work on another device?
Appreciate any guidance, thanks guys!
PS I'm using DsiXDa's Kitchen, but it "doesn't support any devices besides HTC devices" and I want to port a ROM to a Dell Streak from an HTC Nexus One. Is it even possible and what files can I manually replace to get it to run?
Click to expand...
Click to collapse
I'm looking at a Streak ROM right now, and it looks fairly standard for Android. I would search for 'vendor tree' and/or 'extract-files.sh' to get an idea about what files and settings you might need. That will get you started. You have to swap kernels, that's a given. You'll probably need a few additional things from a stock Streak ROM, like:
files in:
/system/usr/keychars
/system/usr/keylayout
/system/lib/hw
/system/lib/modules
/system/etc
some libs in /system/lib
Probably a few things from /system/bin and /system/xbin
Look at the *.rc files in both the N1 ROM and the stock Streak ROM. They will call binaries and make changes. It's all tied together and is quite complex for such a 'small' thing... Get ready to do some research and testing and don't expect it to just work right away. If it does, your lucky.
I use WinMerge to compare ROMs all of the time. It will give you clues as to what is needed for the ROM to work on your device. And logcat will also point you in the right direction on occasion
Thanks a bunch gnarlyc!
Least I have a starting point now, going to get to Googling and see what I can figure out. And WinMerge is an awesome tool, thanks for that. I'll post back here if anything. Thanks again!
Anyone else have some information to share as well that could help?
EDIT: How do I get WinMerge to work? I installed it and tried to compare the two .zip files and it just shows jibberish in each window?
dcogen said:
EDIT: How do I get WinMerge to work? I installed it and tried to compare the two .zip files and it just shows jibberish in each window?
Click to expand...
Click to collapse
Well, it shouldn't show gibberish. I have it up right now with two init.desirec.rc files from two different ROMs. It's not going to be able to compare .zips though. Only text files and folders. You'll have to unzip those.
There are other programs that do the same thing, like 'N-way folder compare' and 'Beyond Compare' and plain old 'diff' in Linux or cygwin. Find what works best for you.
gnarlyc said:
It's not going to be able to compare .zips though. Only text files and folders. You'll have to unzip those.
Click to expand...
Click to collapse
I actually found that they have a .zip plugin to allow you to compare .zips and I tried to install it but it just isn't working. When I try to unzip them and just select the unzipped folder it opens it in the selector window instead of just using the folder.
I'll keep messing with it, thanks again for the starting point at least
I put this in the Q&A but it is really a dev question so....
No bashing please, Im just asking for help
-download dsixda's Kitchen
http://forum.xda-developers.com/showthread.php?t=633246
-install/setup the kitchen
-cd to kitchen directory and type ./menu
-type 1 'setup working folder from ROM' and enter, choose the rom you want to port
-when you get back to the menu type 0 for advanced options and choose '19-porting tools', type a for 'port from another device, then move a rom made for the eris and the rom you want to port to the /kitchen/original_update/ directory, and follow the kitchen's prompts.
-once you completed the previous step, open up build.prop located at /kitchen/WORKING_XXXXXX_XXXXXX/system/build.prop and change the name of the device to desirec or eris (Ex. ro.product.device=desirec), and the carrier to Verizon (unless its a rom from a gsm phone, then you have more things to do). After that do the same thing for the update-script at /Kitchen/WORKING_XXXXXX_XXXXXX/META-INF/com/google/android/update-script.
-after that is done go back to the kitchen, hit 0 for advanced settings, type 20 for unpack or repack a boot.img, type w to extract ramdisk, then go to /kitchen/BOOT-EXTRACTED/boot.img-ramdisk/ and change init.heroc.rc (or whatever the devices name is) to init.desirec.rc
-finally get desirec-keypad.kcm.bin, desirec-keypad.kl, and sensors.desirec.so from an eris rom at /system/usr/keychars, /system/usr/keylayout/ and /system/lib/hw respectively, and copy them to the same location in your working folder.
-now go back to the kitchen, type 99, it will build an update.zip that you can flash of your ported rom
homewmt said:
-download dsixda's Kitchen
http://forum.xda-developers.com/showthread.php?t=633246
-install/setup the kitchen
-cd to kitchen directory and type ./menu
-type 1 'setup working folder from ROM' and enter, choose the rom you want to port
-when you get back to the menu type 0 for advanced options and choose '19-porting tools', type a for 'port from another device, then move a rom made for the eris and the rom you want to port to the /kitchen/original_update/ directory, and follow the kitchen's prompts.
-once you completed the previous step, open up build.prop located at /kitchen/WORKING_XXXXXX_XXXXXX/system/build.prop and change the name of the device to desirec or eris (Ex. ro.product.device=desirec), and the carrier to Verizon (unless its a rom from a gsm phone, then you have more things to do). After that do the same thing for the update-script at /Kitchen/WORKING_XXXXXX_XXXXXX/META-INF/com/google/android/update-script.
-after that is done go back to the kitchen, hit 0 for advanced settings, type 20 for unpack or repack a boot.img, type w to extract ramdisk, then go to /kitchen/BOOT-EXTRACTED/boot.img-ramdisk/ and change init.heroc.rc (or whatever the devices name is) to init.desirec.rc
-finally get desirec-keypad.kcm.bin, desirec-keypad.kl, and sensors.desirec.so from an eris rom at /system/usr/keychars, /system/usr/keylayout/ and /system/lib/hw respectively, and copy them to the same location in your working folder.
-now go back to the kitchen, type 99, it will build an update.zip that you can flash of your ported rom
Click to expand...
Click to collapse
Wow thank you! I have messed with the kitchen before but it all seemed kinda confusing when it came to porting
Completely off-topic but, wow, another Nikolai in this forum
NikolaiT said:
Completely off-topic but, wow, another Nikolai in this forum
Click to expand...
Click to collapse
ten char
Look at Froyolicious and SgShultz. I laid out the steps that I took to get them to where they are. The links are in my sig.
And this one -
http://forum.xda-developers.com/showthread.php?t=723319
gnarlyc said:
Look at Froyolicious and SgShultz. I laid out the steps that I took to get them to where they are. The links are in my sig.
And this one -
http://forum.xda-developers.com/showthread.php?t=723319
Click to expand...
Click to collapse
What happens if i port a rom and the wifi doesnt work?
Nikolai2.1 said:
What happens if i port a rom and the wifi doesnt work?
Click to expand...
Click to collapse
The most common issue is that you have the wrong wlan.ko. You need to have the wlan.ko that is compiled against the kernel that you are using. You can also look in build.prop and make sure you are assigning the correct interface. There are also some wpa_* and dhcp* setting in the init.desirec.rc (in the ramdisk part of the boot.img) that might mess you up. I have had one instance where I could never get it working. Apparently, more than one of us is having the same issue right now. Hopefully, someone will figure that out.
I always use WinMerge to compare build.prop, init.devicenamehere.rc, and init.rc to stock Eris versions to try and catch settings that I would miss otherwise. And then rename init.devicenamehere.rc to init.desirec.rc.
gnarlyc said:
The most common issue is that you have the wrong wlan.ko. You need to have the wlan.ko that is compiled against the kernel that you are using. You can also look in build.prop and make sure you are assigning the correct interface. There are also some wpa_* and dhcp* setting in the init.desirec.rc (in the ramdisk part of the boot.img) that might mess you up. I have had one instance where I could never get it working. Apparently, more than one of us is having the same issue right now. Hopefully, someone will figure that out.
I always use WinMerge to compare build.prop, init.devicenamehere.rc, and init.rc to stock Eris versions to try and catch settings that I would miss otherwise. And then rename init.devicenamehere.rc to init.desirec.rc.
Click to expand...
Click to collapse
Wow thanks alot! I will use all this if I ever decide to port something. Lol I was gonna try porting that 2.2 Sense Rom, but it looks like 2 people with experience beat me to it
Nikolai2.1 said:
Wow thanks alot! I will use all this if I ever decide to port something. Lol I was gonna try porting that 2.2 Sense Rom, but it looks like 2 people with experience beat me to it
Click to expand...
Click to collapse
You should still try, even if you don't release it to the public. I have several ROMs that no one has ever seen but me. It's a good way to learn, and I find that it is easier to please me than me + other people. That's not necessarily a good thing, because I wind up not fixing things that I should.
I would like to add something that I have recently learned about the wifi issues. Apparently, in the past, some devs have had success with hex editing any references to the wifi driver that are in libhardware_legacy.so to make them point to wlan.ko instead of whatever driver the ROM has. So far, this hasn't worked with the 2.2 Sense as far as I know, but it's something else to add to the list.
Well I tried porting an Aria Rom, but when i flashed it, it failed..
I dont mean to resurrect a dead thread that i created, but i cant port anything to save my life. GSM or CDMA (in fact, how do you port a GSM rom?)
Help?
Just got a PM about this and I figured since I spent 30 minutes typing this out I would share. Please click +thanks if this helps anyone. Enjoy
Heres a quick QUICK tutorial. Before we begin have android sdk installed to your computer in the C:/ area. You will want it there, not in the program files area. Next install both java platforms.. Android SDK Setup Tutorial. There is a tutorial on how to set it up.
SBF to stock(BARE BONES STOCK! NOTHING ELSE)>Install ROOT>Install Bootstrap>Make Nandroid Backup of STOCK system(This way you can go back if you mess up)>DEOdex system/app & system/framework(see note 1)>Put deodexed files in correct folders of a flashable .zip(see note 2)>Make/Edit an update-script(see note 3) and put file in the META-INF/com/google/android/ folder>sign the .zip(see note 4)>flash
Tools
Note 1:
Use the tool ultimatex or w/e in the tools provided to deodex your phone. It will pull the system/app and system/framework files from your phone and deodex them for you.
Note 2:
Flashable .zip tree
_Name_.zip
-----data(optional)
--------app
-----META-INF
--------com
-----------google
--------------android
-----system
--------app
--------framework
^^^these are folders in the .zip and the tree will look almost identical to this when you go to flash.
Note 3:
Amend&Edify scripting
There is a good tutorial on how to make the update-script. Make sure you download and install Notepad++ and use that as the text editor. NOT regular notepad! Not Wordpad! Example for update-script for this tutorial is:
Filename: update-script (save as any file or whatever, not RTF or anything else, click down arrow and select all or whatever doesn't have an extension(ie we don't want .rtf or .txt) If you are having trouble saving this file, download a flashable .zip and use its update-script.
Note 4:
Here is the tool I use to sign .zip files to flash, as well as a tutorial.
http://androidforums.com/developer-101/8665-how-signing-roms.html
delete_recursive SYSTEM:app
delete_recursive SYSTEM:framework
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
set_perm_recursive 0 0 0755 0644 SYSTEM:framework
Click to expand...
Click to collapse
after you sign the .zip just flash and you should be set.... hope this helps.
There is some very useful stuff here. I'm glad you have the link to naven's post with android tools. That's where I got started. I have SDK and set up already but always good to check out other ways of getting things done. Thanks.
hedwig34 said:
There is some very useful stuff here. I'm glad you have the link to naven's post with android tools. That's where I got started. I have SDK and set up already but always good to check out other ways of getting things done. Thanks.
Click to expand...
Click to collapse
no problem... Im at work with no way of deving the rom so I'm constantly searching for this or that or looking at different ways to do things. I was going to make a update-script tutorial but I found that one.. Maybe ill do one just on permissions with the provided link to get everything else you would need, maybe compile a super thread... idk im just bored haha
Peperm1nt said:
no problem... Im at work with no way of deving the rom so I'm constantly searching for this or that or looking at different ways to do things. I was going to make a update-script tutorial but I found that one.. Maybe ill do one just on permissions with the provided link to get everything else you would need, maybe compile a super thread... idk im just bored haha
Click to expand...
Click to collapse
I was a work myself when responding to your first post. I tend to look around a lot during the day too. I usually end up emailing links to tutorials or other various to myself so I can check them out later at home.
I see that you have ultimatex on your list too. I used that to deodex my stock 2.3.4. Then I saw your post where you were sharing 2.3.4 already deodex'd. If you would have posted your deodex image sooner I probably wouldn't have tried it myself and just used yours. Good thing though cause I learned to do it for myself.
I'm really starting to get into the android thing now. Keep wanting to learn more about how it runs.
hedwig34 said:
I'm really starting to get into the android thing now. Keep wanting to learn more about how it runs.
Click to expand...
Click to collapse
I've rooted/modded all kinds of other devices(non-phone), but I've never went as in depth as I have with android. I've learned a lot and these tuts/references/roms I have put up are things I was looking for in the beginning. I just would like more development on the x2 and this is, I guess, my way of getting more into it.
I'm Still Looking For The Answer To Creating The "update-binary" I Know The Syntax For Amend And Edify.
Wondering....
I have an old G4 PowerPC Mac I am wanting to repurpose. I have never been able to get the SDK installed and working on my Windows or Linux machines... I want to install Ubuntu PPC on that machine and am wondering if I will have any problems with getting the SDK working since it is not an Intel/AMD processor... Any thoughts?
you get the binary in your system folder
Sent from my DROID X2 using Tapatalk
thanks for perfect tut.
i have some question:
1.i want to add fonts ? just adding to system/fonts ?
2.how to add update binary?
3.How To sign the zip?
thanks.
MikeJ92YJ said:
I'm Still Looking For The Answer To Creating The "update-binary" I Know The Syntax For Amend And Edify.
Click to expand...
Click to collapse
Good to see ya Mike
How's that unlock treating ya?
I decided I'm getting a computer before.a new phone. I really need one lol
How to sign .zip
http://androidforums.com/developer-101/8665-how-signing-roms.html
OP updated.
Tapin the Talk on the xSquared
Peperm1nt said:
you get the binary in your system folder
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I can't find anything there. Where is it peperm1nt?
Preinstall folder...or you can grab the one out of my ROM's .zip
Tapin the Talk on the xSquared
Peperm1nt said:
Preinstall folder...or you can grab the one out of my ROM's .zip
Tapin the Talk on the xSquared
Click to expand...
Click to collapse
What? That is from rerecovery, no others there.
I assume they are the same that's why I suggest it....
Tapin the Talk on the xSquared
Mikey is right we are guessing. Might as well use DKs latest from his 5027 cwr or p3droids prerooted aio.
If I recall correctly, the guys at CWM made edify scripting? I could be WAY wrong on that, and there are several different versions that have different commands within them. But most are generally the same. You can use any of the update-binary files in the uploads... Eclipse doesn't use edify scripting to my knowledge, but the other uploaded ROMs and most of the mods have it... in my GB Battery fix upload, that is the Binary I use.
I am sure it is a lot more than just this but, amend = update-script and has no binary
edify = updater-script and needs a binary.
Forgive me if I'm wrong but we don't have roms or anything that use edify because our BSR will only work with amend...for now
At least that was my understanding
http://rootzwiki.com/topic/3851-cwr-errors/page__view__findpost__p__89813
Our cwr has updater-script and a binary.
I want to use the android kitchen to turn our recently leaked ICS update into a rom. On Dsixda's thread, he states that we need to create a file in the kitchen's /tools/edify_defs folder with the properties of our phone, in the templates file, it is kind of unclear for me how to do this.
Can anyone help me create a file for the HTC Amaze 4G? Thanks
HuskyHamburger said:
I want to use the android kitchen to turn our recently leaked ICS update into a rom. On Dsixda's thread, he states that we need to create a file in the kitchen's /tools/edify_defs folder with the properties of our phone, in the templates file, it is kind of unclear for me how to do this.
Can anyone help me create a file for the HTC Amaze 4G? Thanks
Click to expand...
Click to collapse
Sorry if I am reviving a not quite old thread, but it came up when I was searching for the kitchen to download on my new windows install..
If you want to create a rom you don't really need the kitchen, it can do certain things to a rom- deodex, zipalign, install superuser and busybox, etc.. but within a few days of the leak all of that is available. You can pm a developer as I did and get permission to use their files rather than recreate the wheel.
First, just run the zip file thru the kitchen, don't do anything special with it- we have a superuser zip file you can/should just unpack into the final setup.
Find the updater-script and the binaries(in the same folder), this is what tells it what to install and where, fix permissions, install the files needed for SU(look in the superuser zip files updater script for details) etc..
If you want a deodexed rom you can ask to borrow the system/app directory from a rom that already has deodexed theirs. Literally, this is the best way to do it.
What the kitchen IS better for is pulling apart the kernel, putting it back together, unpacking apks.. it has built in scripts which can be a real time saver than typing in backsmali this, smali that-- simply put a file in a folder, type a number, and magically it all happens for you.. but you won't need ANY of that until you get into the advanced stuff.
I don't know if you were still trying to figure it out or not, but at the very least this may give someone who happened across this thread SOME sort of answer-- I get sick of finding more unanswered posts or posts where people reply with "you should search".. I've searched so much I my fingers should be bleeding.