Related
Hello everybody!
Even if this is my first post on this forum, I use to visit this useful place since years, I tried many of those great WM6 ROMs made by our ROM cookers (thanks to all), then I tried to cook my own ROMs using tools recommanded in the Wiki.
But those kitchen tools weren't conveignent for my use, it was a lot of work and patience for making ROMs, we need to use many different programs and scripts, and I thought that the cooking process could be really simplified using an unified graphical interface like dutty's tool. I was patiently waiting for his Hermes Rom Koch V2, but finally I started to develop my own kitchen tool!
Here are some features of this program:
- ROM file manager (to add/delete/extract files or to create shortcuts)
- ROM layout editor (to edit init flash files)
- Registry editor (to modify/import/export default & user registry)
- CAB install files integration
- ROM creation from original OS image or dump directory
I posted some screenshots for better explanations.
This program simply use aWaiter and ImgFS tools for ROM creation/extraction.
For now I still have a lot of work on it, but I would like some advises from experienced developers on this forum, because even if my program works, I would like to know if the cooking process is porper and safe, and how I could improve it (for example using internal functions for ROM creation/extraction instead of external programs, implementing NBH tools,...).
If some of our XDA-developers are interested, I would really like to make this project an Open Source "all-in-one" ROM cooking program, gathering all the others kitchen tools in an unified graphical interface offering the easiest way to cook nice ROMs for our Hermes and certainly for other devices.
I know that I didn't give many details about my program but don't hesitate to ask me about it. I would also have few questions for developers.
Developers and ROM cookers, I'm waiting for your feedback!
Thanks.
This looks very user friendly, I will be watching closely. Good work.
What language is it in? (programming language that is)
Midget_1990 said:
What language is it in? (programming language that is)
Click to expand...
Click to collapse
I developed this program in C# (using .NET framework 2.0).
Thx for your work! It would be better if the tool support packages.
http://forum.xda-developers.com/showthread.php?t=296861
Where to download??
Thanks for the link. I already thought about working with packages because it seems to be a better way to make "clean" ROMs, but I couldn't find enough information about how to extract/build packages in ROM.
I tried bepe's package tool on my own cooked ROM and I noticed that removed files were marked as missing in packages, and all the files I added weren't moved from dump directory. There is nothing surprising, but I wondered if adding/deleting manually files from ROM, causing "corrupted packages", can have any effect on final ROM. If not then why packaging information (like .dsm and .rgu files) are still present in ROM after all packages were merged? What exactly contains .dsm files, and how to create them for adding new packages?
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Thanks
I'm still working in this project, so I didn't plan any release yet.
Good idea and nice project.
Go on dude !
Good work.
Great work so far - I fullly support this project.
Lookign forward to the release.
schaps said:
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Click to expand...
Click to collapse
Great project - and I agree, it definitely should support packages. If you've had a look at bepe's kitchen, you already know how much easier it is to understand the purpose of all the files in a ROM if they are organized in packages.
.rgu files are Registry "source code". They are not part of the package mechanism. And yes, when cooking a ROM you can leave them out, as they are not needed at run time. Saves a bit of space.
The .dsm files, otoh, are needed at run time.
When I cooked my ROM, I did find some information (written by bepe) here in the forum about how to make your own packages. Can't remember where that was, but I found it on my hard disk, so I simply quote it here again:
How-To build ur own OEM Package:
An OEM Package is just a simple folder containing files and registry settings for the ROM
First of all you'll need a GUID number for your Package.
Go to http://www.famkruithof.net/uuid/uuidgen to get one.
In my case:
283b9db7-cb03-4c1b-820e-ca49b2c3b5db
Necessary steps:
1. Create a new folder:
Dev/OEM/[Your package name]/
2. Create a empty text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.dsm
(CreateOS.exe will finish this file for you)
If needed:
3. Create an UNICODE text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.rgu
This file could be used to add registry entries to the ROM
First line is:
REGEDIT4
...
and there MUST be a empty line at the end!!
4. Create an UNICODE text file:
Dev/OEM/[Your package name]/initflashfiles.txt
This file could be used to create folders or copy files, shortcut on the ROM.
For Example/ Ilustration: Open or read Dev/LOC/initflashfiles.dat using a text editor or any premake initflashfiles.txt at one of the OEM folder.
and there MUST be a empty line at the end of iniflashfiles.txt also!!
Copy all files you need to Dev/OEM/[Your package name]/
Click to expand...
Click to collapse
Hope that helps. If I remember correctly, bepe told me that the OEM folder is treated a bit differently from the SYS folder, so it might be you can't create packages there. But then, you probably also shouldn't.
Oh, and about the initflashfiles.dat: you are aware that the initflashfiles.dat just copies files and does not move them? Using this feature extensively uses up ROM space very quickly, so it should be done for small files (like the start menu shortcut files) only.
Cheers
tadzio
Thanks a lot for your help tadzio!
I also read the different steps about how to add a new OEM package, I found information on this Wiki if someone is interested : http://wiki.ppcgeeks.com/index.php?title=Kitchen.
I think I know enough about it but what I would know is how to extract packages then to merge them for creating a ROM image, like do bepe's tools?
I confirm I also heard that OEM folder processing is different from SYS folder.
Concerning the initflashfiles.dat I guessed that files were copied from ROM to storage memory, good to have a confirmation. So it means that if we want to include a new program in ROM, we should better to let it in Windows folder than to put it in a Program Files folder, right? I have another question about initflashfiles.dat, I saw that it sometimes uses variables for directories instead of strings (for example Directory(LOC_XXX), Directory(0409_XXX),...), where could I find those variable declarations?
schaps for president
schaps said:
Thanks for the link. I already thought about working with packages because it seems to be a better way to make "clean" ROMs, but I couldn't find enough information about how to extract/build packages in ROM.
I tried bepe's package tool on my own cooked ROM and I noticed that removed files were marked as missing in packages, and all the files I added weren't moved from dump directory. There is nothing surprising, but I wondered if adding/deleting manually files from ROM, causing "corrupted packages", can have any effect on final ROM. If not then why packaging information (like .dsm and .rgu files) are still present in ROM after all packages were merged? What exactly contains .dsm files, and how to create them for adding new packages?
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Thanks
Click to expand...
Click to collapse
Hi Schaps,
you can have a look in this link:
http://forum.xda-developers.com/showthread.php?t=312985
it's a tool to re-build DSM file, which is better than just creat an empty .dsm file when making new package.
hope this help. It will be cool if your new tool support package.
i need help with 2 oems s2u2 v.99c and s2v v0.32.
problem 1: s2u2 clock and weather has same png file names
problem 2: any oems i found install everything under windows folder I would
rather have them in \program files\ (i'm picky).
problem 3 they both have a file named ac_gd.dll.
I am using dcd's kitchen 1.6.10 (awesome program i have to donate soon, flawleess work keep it up dcd) and personal oemizer(don't know were this came from but also an excellent program). if no one wants to take this task atleast toss me a bone about what to do with all the dupl. file names so that i still get full functionality out of both programs I have made many successful oems and roms and as soon as i get these files figured out wouldnt mind posting some work for every one to check out. If you need additional info ill be back on about 1am send a mesg or leave post.
thanks in advance.
ps this is for wm6.0 not the 6.1 i love 6.1 but ill wit till les bugs.
1. You need to change the names of the picture files and then create an initflashfiles.txt file that changes the names of the files to the correct ones. FOr an example of this see the S2U2 OEM in the PPCGeeks OEM files for the Apache kitchen.
2. You can move them using an initflashfiles.txt file but then you would have 2 of all of those files using up memory.
3. Remove one.
OEMizer is from tierman from PPCGeeks.
brain fart
ahh ha so in the initflashfiles.txt all the dupl strings like
Directory("\Program Files\s2u2\gfx\clock\"):-File("0.png","\Windows\0.png")
could be changed to
Directory("\ProgramFiles\s2u2\gfx\clock\"):-File("0.png","\Windows\a0.png")
as long as I changed the original file name to a0.png.
so there is no conflict WOW should of seen that myself thanks blazingwolf life saver.
I got my rom done and I am now trying to add a few things to spice it up. The only thing I cant get working is tsowentaskbar. The signal icon does not show the signal bars. They will show if I am on a call but not when phone is not in use. I have read a lot and have seen others post about this problem but cant find a answer. I am cooking the taskbar and sdkcerts in the rom. I have even tried installing sdkcerts then default cabs and get the same thing. Can anyone please help me?
Thank you
Shep
For those icons, you need to make sure that your kitchen is adding the files from your OEM and not from OEMDrivers, QuickGPS, Phone_Canvas_Slider etc... What kitchen are you using?
I use Da_G's Simple Rom kitchen and have made a package for that. His kitchen processes the Packages dir first. You also need to make sure that the reg entries in the rgu are the ones that stick. Check your registry after flashing and make sure that you have:
[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]
"BatteryIconLevels"=dword:00000065
"BatteryIconIdStart"=dword:000003e9
"BaseDll"="phcanOverbmp.dll"
"BaseId"=dword:00000000
If not, then another rgu or provxml is setting that later. You'll need to either find those and remove them, or add an XML to set it in \OEM\OperatorPkg\config_operator.txt.
Good luck.
eras2r said:
For those icons, you need to make sure that your kitchen is adding the files from your OEM and not from OEMDrivers, QuickGPS, Phone_Canvas_Slider etc... What kitchen are you using?
I use Da_G's Simple Rom kitchen and have made a package for that. His kitchen processes the Packages dir first. You also need to make sure that the reg entries in the rgu are the ones that stick. Check your registry after flashing and make sure that you have:
[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]
"BatteryIconLevels"=dword:00000065
"BatteryIconIdStart"=dword:000003e9
"BaseDll"="phcanOverbmp.dll"
"BaseId"=dword:00000000
If not, then another rgu or provxml is setting that later. You'll need to either find those and remove them, or add an XML to set it in \OEM\OperatorPkg\config_operator.txt.
Good luck.
Click to expand...
Click to collapse
Im using Da_G's 21195 kitchen. Can you share your package?
I am using the 6.1 21040 kitchen. I haven't tried much cooking with the 6.5 kitchen as of yet. I don't know if the dll's are the same or not.
You can try dropping this package into \Packages and see if it works. But like I stated before you need to check your reg entries after flash and figure out if they are correct. And compare this package to the one you created and see the differences.
-e
eras2r said:
I am using the 6.1 21040 kitchen. I haven't tried much cooking with the 6.5 kitchen as of yet. I don't know if the dll's are the same or not.
You can try dropping this package into \Packages and see if it works. But like I stated before you need to check your reg entries after flash and figure out if they are correct. And compare this package to the one you created and see the differences.
-e
Click to expand...
Click to collapse
I checked the reg settings and they where right. I am trying your package and if it works I will try to find out whats wrong with mine. Thank you for the help.
Might be another reason for this tsowen battery signal are for cdma and the signalbars are located in a different dll than the normals gsm one. Also we gsmers are not able to modify the signal bars as they are not produced by icons. If you need to know more let me know, 12
This is the kitchen I am currently using to build my rom series, my main reasons for releasing this are to try and progress development of 6.5 builds on the athena.
I am going to assume that if you have in depth knowlege to rom building that you would have probably put your own kitchen together, so please dont post questions etc if you have tried to do something out of your comfort zone i.e porting new builds(this is a bit more involved)
The kitchen contains saved builds of my latest releases, 23060 and 23053, load whichever you wish and add and remove packages etc, I will try and assist as much as I can.
There are many guides on ervius kitchen I would suggest reading them if you are new to it.
My hope is that we can resolve the few remaining issues I have in a more efficient way than me spending 5/6 hours every night building and testing roms, the main existing problems are:
DRM
Manila
Autorotation
All the saved config files have been recmodded to attain max slot 0 memory allocation, I would not advise recmodding any more modules as this will probably cause a non booting rom.
I will try and update with latest versions with a config file as they become available.
Please do not release roms into the forums, my intention is that you use it to learn and build your own spec roms
Download Link!!!!!
http://www.megaupload.com/?d=YI469SR4
***PLEASE NOTE***
THIS IS NOT FOR PEOPLE WHO DO NOT UNDERSTAND WHAT THEY ARE DOING, YOU RUN A HIGHER RISK OF BRICKING YOUR DEVICE IF YOU GO IN BLIND, AS WITH ROMS THIS IS FOR SPL3.5 DEVICES, I AM MORE THAN HAPPY TO ASSIST ANYONE WHO NEEDS IT PROVIDING YOU ACCEPT I CANNOT GIVE ALL MY TIME TO THIS AS I HAVE A FAMILY AND A JOB TO LOOK AFTER, IF YOU NEED HELP I CAN WALK YOU THROUGH IT VIA MSN ETC
******Reserved************
********Reserved*********
Lol, first hurdle, the kitchen is 802mb and sendspace wont allow me to upload more than 300mb
anyone got any ideas
can you upload a torrent?
ZIP > split > upload parts?
Split to 100MB parts and PLEASE upload it to Rapidshare
Thanks
you can rar/zip and split it into 250MB parts (less parts to download than to have each part at 100MB) or you can upload to torrent (but we would need seeders....the dedicated file servers are a better option though)
I managed to reduced the size somewhat and its now on megaupload, the link is now in the first post.
For those wishing a beginers course, I am going to try and do one tomorrow, but will start a seperate post for it.
I have not tested this kitchen but it should work fine.
hey avenger, will you be including the new 23071 build in the kitchen or for additional download? also does the kitchen offer xip and sys porting?
lennie said:
hey avenger, will you be including the new 23071 build in the kitchen or for additional download? also does the kitchen offer xip and sys porting?
Click to expand...
Click to collapse
I will probably build a 23071 rom tonight and see how it looks, then consider releasing it into a kitchen, yes the kitchen offers sys and xip porting, but it needs a couple of things doing to get it to work with the athena kernel
avengerpenguin said:
I will probably build a 23071 rom tonight and see how it looks, then consider releasing it into a kitchen, yes the kitchen offers sys and xip porting, but it needs a couple of things doing to get it to work with the athena kernel
Click to expand...
Click to collapse
As I asked in private messages. can u make a tut for this specially how to work with your kitchen xip/sys porting section?
for some reason the kitchen seems to stop being able to port over a xip...I don't know if the copy I had somehow got corrupted on my drive but I'm going to redownload and try again.
has anyone else been having the problem?
lennie said:
for some reason the kitchen seems to stop being able to port over a xip...I don't know if the copy I had somehow got corrupted on my drive but I'm going to redownload and try again.
has anyone else been having the problem?
Click to expand...
Click to collapse
Lennie, this happened with my x7510 kitchen as well, the fix is to open the xip exporter tool bottom left of kitchen, there should be a button called something like, extract from payload? use that to extract the xip.old and see if that works
avengerpenguin said:
Lennie, this happened with my x7510 kitchen as well, the fix is to open the xip exporter tool bottom left of kitchen, there should be a button called something like, extract from payload? use that to extract the xip.old and see if that works
Click to expand...
Click to collapse
yeah it's there, but doesn't that mean I would have to have the os.payload for the newer rom that I want to get the xip from?
if I get a rom with build 28008 can I then use the kitchen to extract the os.payload and then use that to extract the xip.bin then use the xiporter in the kitchen and extract the xip? if i do that would it mess up the kitchen in anyway?
lennie said:
yeah it's there, but doesn't that mean I would have to have the os.payload for the newer rom that I want to get the xip from?
if I get a rom with build 28008 can I then use the kitchen to extract the os.payload and then use that to extract the xip.bin then use the xiporter in the kitchen and extract the xip? if i do that would it mess up the kitchen in anyway?
Click to expand...
Click to collapse
Sorry I thought you were having a different error relating to xip.old, from your pm I am assuming your not able to port the new xip.
I have used the msxip folder that comes with rom dumps to some success in the past by creating a new folder in kitchen/rom/shared/*create folder with new build number* copy the MSXIP Kernel folder into here for your new xip supplied with dump, and copy the packages.txt file from a working folder from another build.
(This is the new XIP files)
Then go to kitchen/rom/ATHE100/ *create folder with new build number* copy the OEMXIPKernel and packages.txt from a working ATHE100 folder into there.
(This is the old device specific xip part dumped from original rom)
You should find that you now have the new xip in the dropdown box of the kitchen, however I have found this very hit and miss and am currently struggling with porting 28014 using this method. If you search there are bits of advice about other tools able to dump XIP's that VK is not able to do, but I have not had the time to fully research it.
Let me know how you get on as my kitchen is currently crashing whenever I try and do this.
*Just found this http://www.everythingdiamond.info/showpost.php?p=2879&postcount=2 * See if this helps
avengerpenguin said:
Sorry I thought you were having a different error relating to xip.old, from your pm I am assuming your not able to port the new xip.
I have used the msxip folder that comes with rom dumps to some success in the past by creating a new folder in kitchen/rom/shared/*create folder with new build number* copy the MSXIP Kernel folder into here for your new xip supplied with dump, and copy the packages.txt file from a working folder from another build.
(This is the new XIP files)
Then go to kitchen/rom/ATHE100/ *create folder with new build number* copy the OEMXIPKernel and packages.txt from a working ATHE100 folder into there.
(This is the old device specific xip part dumped from original rom)
You should find that you now have the new xip in the dropdown box of the kitchen, however I have found this very hit and miss and am currently struggling with porting 28014 using this method. If you search there are bits of advice about other tools able to dump XIP's that VK is not able to do, but I have not had the time to fully research it.
Let me know how you get on as my kitchen is currently crashing whenever I try and do this.
*Just found this http://www.everythingdiamond.info/showpost.php?p=2879&postcount=2 * See if this helps
Click to expand...
Click to collapse
ok thanks. I'm giving it a try now, I put all the files in the place they're supposed to go however, I forgot what extension to rename BatchRecmod.jpg to (the file you had sent me)
EDIT: if I remember correctly BatchRecmod was a folder that you added the .jpg extension so you could send it to me, however, when I remove the extension I still can't access the contents inside...
lennie said:
ok thanks. I'm giving it a try now, I put all the files in the place they're supposed to go however, I forgot what extension to rename BatchRecmod.jpg to (the file you had sent me)
EDIT: if I remember correctly BatchRecmod was a folder that you added the .jpg extension so you could send it to me, however, when I remove the extension I still can't access the contents inside...
Click to expand...
Click to collapse
A better option than the batchrecmod I sent you would be to search Da_g's thread in dev/hacking for an addition to the kitchen made by user XTEP it adds the recmod function to the extra buttons inside the kitchen.
However if not change the .jpg extension to .zip and then unzip and you should have the files you need
avengerpenguin said:
A better option than the batchrecmod I sent you would be to search Da_g's thread in dev/hacking for an addition to the kitchen made by user XTEP it adds the recmod function to the extra buttons inside the kitchen.
However if not change the .jpg extension to .zip and then unzip and you should have the files you need
Click to expand...
Click to collapse
thank you very much, I think I found the addition by xtep in da_g's thread but I don't see how to add it to the kitchen...so I used the the files from the zip you sent me....I tried to cook and everything seemed as if it was going just fine, then bam! kitchen crashed. I'm going to try and get a working xip.bin to and see if the kitchen can extract it because using the msxipkernel does not seem to be a stable method.
lennie said:
thank you very much, I think I found the addition by xtep in da_g's thread but I don't see how to add it to the kitchen...so I used the the files from the zip you sent me....I tried to cook and everything seemed as if it was going just fine, then bam! kitchen crashed. I'm going to try and get a working xip.bin to and see if the kitchen can extract it because using the msxipkernel does not seem to be a stable method.
Click to expand...
Click to collapse
I have been struggling with this as well, I have not managed to find a portable xip.bin for 28014 as of yet. If you find one let me know please.
as the title implies i am unsuccessful at building the rom with da_g's kitchen, iv made shure iv place the sys and oem were they go, same with my ext's. I even ported the xip.bin witch it is int necessary since da_g post hes new build's with that already done, and even when doing that the rom fails to build, any help would be appreciated, iv attached my build log see if you guys see what im doing wrong.
regards
siulmagic
Remove the sys package SQM; you don't need it (or want it) with dummycustsat included. It's just the error reporting crap for MS.
hmm i deleted them but the rom stil does not build
You need one or the other. Do you have the correct oem stuff for a kaiser?
Also, if you're doing a Kaiser rom, make sure that the real 6.5 aku box is unchecked, and you probably need to recmod a ton of modules. That may be your main problem. You're cooking in pretty much all of the sys folders, and they're filled with modules. I believe that browsingie and bronzeres are two of the packages that people using 6.1 kernels recmod to get a free slot 0.
oh my bad lol i forgot to change my sig i do not own a kaiser anymore, iv got a htc raphael now thats y im posting here XD
Well, my guess is that it's the sqm problem. Note, there's a reason that the mods package is called "DummyCustsat-DisableSQMFirst". You need one or the other. One or the other. Not both or neither. Use dummycustsat.
You should also use the older comm manager. The newer one is buggy as hell (especially in landscape). Don't you need one of the XT9 packages? I'm pretty sure there are major dependencies in there that are needed by a lot of processes (that's where the et9...dll's are, isn't it?).
I'm also not sure what's going on here:
Package: ShareDLL_2.0.070522.0000 Included Into ROM!
ERROR!!! Found File duplicate on Module...
Package: SharedModules_1_01_19142727_00 Included Into ROM!
Click to expand...
Click to collapse
I have sharedll cooked into my builds, but not sharedmodules. It sounds like they're interfering with one another.
hmm i already deleted the sqm oem package so the one left and the ones thats enabled is the dummy one, but it still fails to build
Farmer Ted said:
Well, my guess is that it's the sqm problem. Note, there's a reason that the mods package is called "DummyCustsat-DisableSQMFirst". You need one or the other. One or the other. Not both or neither. Use dummycustsat.
You should also use the older comm manager. The newer one is buggy as hell (especially in landscape). Don't you need one of the XT9 packages? I'm pretty sure there are major dependencies in there that are needed by a lot of processes (that's where the et9...dll's are, isn't it?).
I'm also not sure what's going on here:
I have sharedll cooked into my builds, but not sharedmodules. It sounds like they're interfering with one another.
Click to expand...
Click to collapse
hey i yust fixed the module conflict but it stil wont build, could it be the nk.exe the one i got is from the kitchen da_g posted a long time ago
He posted a newer one in the 6.5 thread (not sure the link is up, though). That's the one you want to use, it's much better than the older one in his full kitchens.
You should try to just cook one of his preconfigured roms and see if it builds properly. Otherwise, you may have a problem in there that's hard to track down.
Farmer Ted said:
He posted a newer one in the 6.5 thread (not sure the link is up, though). That's the one you want to use, it's much better than the older one in his full kitchens.
You should try to just cook one of his preconfigured roms and see if it builds properly. Otherwise, you may have a problem in there that's hard to track down.
Click to expand...
Click to collapse
i would if the links were up thy removed them do to the takedown notice by microsoft, and yes preconfigured roms build just fine only mine is funky and it doesn't build
siulmagic said:
i would if the links were up thy removed them do to the takedown notice by microsoft, and yes preconfigured roms build just fine only mine is funky and it doesn't build
Click to expand...
Click to collapse
Just use one of the pre-configs as a base for your rom. Add a package or two at a time and build (you don't need to flash). See if you can isolate the problem that way.
Now that I think of it, I did have a problem last week doing a build, and it was the first time I've ever had VK crash on me. I use a zip file to install all my apps into \program files. Anyway, I was editting the file; I unzipped it into the files directory of the package, made some changes, and then re-zipped it. But I forgot to delete the actual folder after doing the re-zip. It caused the kitchen to crash. It's possible that you have a stray folder in one of your packages. I've also read that if you get a stray file in a module folder, it can cause the build to fail. So, add things one at a time, and figure out which package is corrupted. Then fix it.
Farmer Ted said:
Just use one of the pre-configs as a base for your rom. Add a package or two at a time and build (you don't need to flash). See if you can isolate the problem that way.
Now that I think of it, I did have a problem last week doing a build, and it was the first time I've ever had VK crash on me. I use a zip file to install all my apps into \program files. Anyway, I was editting the file; I unzipped it into the files directory of the package, made some changes, and then re-zipped it. But I forgot to delete the actual folder after doing the re-zip. It caused the kitchen to crash. It's possible that you have a stray folder in one of your packages. I've also read that if you get a stray file in a module folder, it can cause the build to fail. So, add things one at a time, and figure out which package is corrupted. Then fix it.
Click to expand...
Click to collapse
i found the problem omg i feel stupid, the problem was i named my sys forlder 23071 and then the xip and ext folders 23070, all i had to do was rename sys to 23070 and bam build successfully
siulmagic said:
i found the problem omg i feel stupid, the problem was i named my sys forlder 23071 and then the xip and ext folders 23070, all i had to do was rename sys to 23070 and bam build successfully
Click to expand...
Click to collapse
You should rename them 23081 and step up to a real build.
again i was goin to download that build but due to the takedown notice that build is gone from xdaXD
meh now i cooked the rom fine then i flashed it and it wont boot goh
im prety shure i need the latest nk.exe, the one that has the native kernel, this one i have im shure its the old one tha tneeds rec moding