Related
Hello,
I use Hypercore kitchen. I extract an OEM ROM and build it without any customizations, it boots up. But when I do the same with other cooked ROMs, they never even pass through the splash screen. Any ideas or suggestions for me please?
Regards,
Carty..
plz someone fgure it out.we r in neede for this best kitchen..plz...for elfin.
Hi saurabh88!
Just download the latest shiped rom you find, and dump it with visual kitchen.
Then you can edit your and change OEM/XIP/SYS/EXT.
sandman01 said:
Hi saurabh88!
Just download the latest shiped rom you find, and dump it with visual kitchen.
Then you can edit your and change OEM/XIP/SYS/EXT.
Click to expand...
Click to collapse
first of all thanx my dear friend for the guidance.so if i had visual kitchen for gene and if i dump shipped rom from elfin then ihave had elfin kitchen na!am i right...
Correct!
After dumping an original Rom you have a base kitchen which you can modify step per step.
Download new Base drivers and replace the old.
Replace XIP/SYS with current one (be careful at the moment no native elfin kernel is available so do not set Real WM6.5 AKU)
...
..
i done made the rom but when i flash it it goes u to 89% then says unable to update,follow the imstr. to recover your device.plz help me.
THIS HAPPEN;
after downloading vk from the link u have given and dumping again my rom when i click to select my device while cooking it says me
"os value on NBHUtil.xml for elfo1000 not found.....set 0*4000 as default"
what is it mean?does it affect my rom?
After Dumping an original *.nbh file save the configuration.
That are the right settings for reflashing your Elfin.
I'm not sure if the OS id. effects your rom, but Chunk Size for elf(in) must set to 1024 (acording to nbhutility).
I do not have my Elfin anymore, so I cant test different settings.
At first download a cooked rom and flash it to get a working device. Or download the latest shiped rom from your provider. Than start dumping ant flashing again to see if the error is still there.
i done using shipped rom....chunk size is ok but now i m stucked at smart mobility.this is also happen with bepes kitchen.
one more thing if i flash shipped rom anything will be wrong?will it brick my device?
I am using ervius to build a rom, Everything works according to the kitchen except that it could not find the ppchanger. But that shouldn't be an issue. However, whenever I load it to the phone. It becomes stuck at boot. What am I doing wrong? Here's the build log.
Update: I moved the wincenls_wwe to my oem to no avail. still stuck at touch pro screen. Here's the latest build log after recmodding some files:
Everything seems to be ok and if it stucks in the first splash screen is issues related to XIP check your OEMxipkernel all the modules.... same format! check the MSXIPkernel all the modules same format!
i see you are addin manila but i couldn saw any manila pkg in OEM or EXT cause you dont have nothing in EXT and you just have OEM and SYS.. where did you get all of this OEm SYS and addons?
Thanks for your reply. All I did was dump a shipped rom. Then I tried to add a 6.5 build. The shipped rom had manila within the oem.
ok... first of all... wich device is it? wich rom was the original rom? 6.1 or 6.5? did you checked 6.5 real aku on the kitchen?
and yes dont forget to check the thread of how to make rom bootable..
+ Que PPC said:
ok... first of all... wich device is it? wich rom was the original rom? 6.1 or 6.5? did you checked 6.5 real aku on the kitchen?
Click to expand...
Click to collapse
Well I tried the Verizon XV6850_MR1_Upgrade_v2.0 for the Touch Pro. I am trying to create the rom for CDMA device (herman correct?) The original rom is 6.1 and I am trying to put the 21903 build. Yes I checked the aku 6.5. I've read the threads from others with the similiar issues. I've tried the recmod.exe in the Ervius tools folder, and I've also tried the recmod auto zip. I've downloaded and went through the list of sys files that can be recmodded with no luck. What steps exactly do I take to make sure that the oemxipkernel and msxipkernel are the same format?
Hi well it seems that you need to know this, if your dumped rom was 6.1 your kernel is not real aku 6.5 so you dont check that box in the kitchen
+ Que PPC said:
Hi well it seems that you need to know this, if your dumped rom was 6.1 your kernel is not real aku 6.5 so you dont check that box in the kitchen
Click to expand...
Click to collapse
oh... so even if I am using 6.5 sys & xip.bin if I am bringing over the oem kernel from the base rom then I should NOT check it... Is that what you are saying?
Exactly!
If you dump the 6.1 STOCK ROM you will have xip.bin payload rromhdr.bin and OEMXIPKERNEL V6.1 and you will not check the the real aku6.5 on the kitchen
If you dump a 6.5 STOCK rom you will have everything in 6.5Version so you can check that checkbox... Why you dont take a look into the main stickie in repositories maybe you can find your Native 6.5 OEMXIPKERNEL and send to the hell the 6.1 version
+ Que PPC said:
send to the hell the 6.1 version
Click to expand...
Click to collapse
+1...man its been probably about 2 yrs since I used a 6.1 ROM! lol
+ Que PPC said:
Exactly!
If you dump the 6.1 STOCK ROM you will have xip.bin payload rromhdr.bin and OEMXIPKERNEL V6.1 and you will not check the the real aku6.5 on the kitchen
If you dump a 6.5 STOCK rom you will have everything in 6.5Version so you can check that checkbox... Why you dont take a look into the main stickie in repositories maybe you can find your Native 6.5 OEMXIPKERNEL and send to the hell the 6.1 version
Click to expand...
Click to collapse
So it doesn't matter if the 6.5 stock rom is not for cdma touch pros? As long as I choose the right dpi and of course remove gsm stufff then I can create a build for it? Am I right in my thinking?
yes the thing that makes the GSM or CDMA rom is in your OEMXIPKERNEL things and in your OEM folders
Wow!! This is some amazing stuff. Ok one more question, of late most builds do not include the oemxipkernels, and I've learned that you can generate this with xipport button in ervius. If i was to use this, and i port the os.payload & the build's xip.bin, should I check the box that this is a native 6.5 kernel?
Touch pro is the FUZE isnt it?
Why you dont ask in Da_G thread for the Native 6.5 TOUCH P kernel
i cant remember well but i guess i saw it
you dont need to do that the kitchen ports the xip.bin payload bal bla bla autopmatically for you
Just want to say thanks for your help. I find your insight very helpful. I will start from scratch and see what happens. Thanks again.
Hi all,
I try to cook rom for my device Samsung M490. I have a Ship rom in Korean language(0412) ( i cannot find the English one).
I build with new WM6.1 SYS/XIP (lang 0409) , the device boot ok, the language changed to Eng, but the setting shortcut not work. I cannot set the rington.
I build with new WM6.5 SYS/XIP (0409) and it cannot boot, the screen turn off after the Anycall logo appear.
Now can you ask me how to make it work with W6.5 build? what thing I will do, what file/folder will be change/edit?
My ship rom here:
Code:
211.189.38.83/umsvcbin/SCH-M490/SCH-M490_CI24_pda.bin
I do follow as below:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN (23662) as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build (23662), repalce initflashfiles.dat by English one. add XIP.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
Thanks very much for your help
There is too little info here to help you. Does your device have a native 6.5 kernel? You will need to have one to be able to flash a 6.5 ROM and make it work on your device.
You mean ''oemxipkerner''? .Samsung didn't release the wm6.5 rom. but i found some cooked wm6.5 rom in Korean and Chinese. can I take it from these rom?
I dont think so. You will first need to dump a stock rom provided by Samsung for your device. Then replace the oemxipkernel with a patched one, which has a 6.5NK.
I dump a ship rom already, I use XIPkithen to make a new xip.bin from a new wm6.1 release, the device boot ok , I do the same way with build wm6.5 but the device can't boot. where can i find a patched oemxipkerner?
You will have to search for it. You will need a 6.5NK for WM 6.5.X to boot on your device.
If Samsung has not released a stock 6.5 ROM for your device, chances are you wont have a native 6.5 kernel.
If you don't have a native 6.5 kernel, you need to recmod a lot of files/folders. This thread @ Mobile Underground has lots of good info.
You said you dumped a stock 6.1 ROM. In this ROM, see if you have a 6.5 Native Kernel by dumping xip.bin. Open nk.exe/s000 in a hex editor. Search for the ASCII string "platform". Near this string there should be the build number that this nk.exe was compiled against.
WM 6.5 builds began around 21100. WM 6.1 and previous builds will be <=21058.
OsKitchen can import the ROM of that phone and also seems able to rebuild it correctly (but make sure the final file is correct for your phone since there are something like ten different BIN file formats) and since it can already suggest the packages to recmod it could also help with 6.5.5 porting if you don't have a 6.5 kernel (which you probably won't find anywhere: the only modded 6.5 kernels I've seen are for htc devices).
thank airxtreme, i use os kitchen before. I dump a Ship rom and build it again, flash rom to phone and it not boot. I try to use new Ervius kitchen but i don't know how to make file OS.NB.PAYLOAD. Now i try a old type Ervius kitchen (5.3).
I just do:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build, repalce initflashfiles.dat by English one. add XI.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
theanh6 said:
thank airxtreme, i use os kitchen before. I dump a Ship rom and build it again, flash rom to phone and it not boot. I try to use new Ervius kitchen but i don't know how to make file OS.NB.PAYLOAD. Now i try a old type Ervius kitchen (5.3).
I just do:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build, repalce initflashfiles.dat by English one. add XI.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
Click to expand...
Click to collapse
Which EXT packages are you using?
anand12 said:
Which EXT packages are you using?
Click to expand...
Click to collapse
I don't use any EXT packages.
theanh6 said:
...-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs....
Click to expand...
Click to collapse
First of all - don't try to dump someones roms to get xip.bin or whatever!
Many guys, including me (does not matter - Chinese or not) - are deleting reloc sections and dsm files while building custom roms to save the space. So if you use such a xip - you will get non-bootable rom.
1. Take the latest OFFICIAL rom
2. Dump it to get original XIP and original OEM
3. Download new build that you want to cook.
4. Port new xip. Use the original XIP as donor of OEMXIPKernel and new xip from downloaded build as a source of MSXIPKernel & MSXIPKernelTLK
5. Take ported xip, OEM (drivers) from official rom, SYS from downloaded new build
6. Start cooking.
Very nice step by step explanation by Andrew. It doesnt get simpler than this!
The most important part - Dump the official rom released for YOUR device NOT for any other. You risk bricking your device.
Thanks AndrewSh & anand12 for your advice, i follow step by step but it only ok for a 6.1 build, and wm 6.5 fail to boot again.
Now I sucess to build an English wm6.5, my way is:
-Dump a cooked Korean ROM build 21815, I have \ROM, \OEM, \SYS, XIP.BIN.
-Remove all file/folder in \SYS but keep .ROM, .VM , Metadata, then copy all from SYS build 21815E(English-0409).
-add XIP.BIN above into OS.NB get from official rom an copy new OS.NB to \ROM.
-Now i have \ROM; \SYS; \OEM, copy them into kitchen an run. Flash new rom to phone and it work ok.
I try to cook a new ROM with last wm6.5 build, but i feel sad because it fail again.
Now i have some quesion, please spend a litle time to help me to clarify:
1. i think my problem is at "Metadata" folder. When we cook a new build, what will we do with "Metadata" (change all folder, change some file/folder or edit some thing) ?
2. I can not set the ringtone for my cook rom, both in 6.1&6.5 build. The "Ringtone" feild is empty as the picture i attached. What thing be wrong here?
Look you must have a 6.5 NK for your device. If not, you must recmod files. Are you doing that? Please be sure and clarify.
@theanh6: Can you upload your cooked here? Thank you very much.
Thank you all, It fully working now (with some small bug but no problem)
@Mrkid: Please send an email to me at [email protected] if you want to try this rom.
How to cook a bootable rom using XIP from one build and SYS from another build of the same branch? All my efforts resulted in non bootable roms.
What kitchen are you using?
What kitchen are you using? I make many of such ROMs for the LG KS20. Even mixing various versions of wm. (I made 1 wm6 ROM with wm6.5.3 styled menus.) Try using xipport. It solved all my bugs.
Thanks for the reply. I use EVK for HTC Gene. I was trying to cook xip from 21899 and sys from 21916. But the rom do not go beyond the first boot screen. Can u elaborate a bit more?
Did it flashed a bit brighter for a while and then went dim again? It would mean XIP started ok, if not - then it's XIP...
Are you sure you have wince.nls SOMEWHERE? (either XIP or SYS)
And another question: are you sure you're implanting XIP into image properly? Generally, mixing SIMILAR XIP and SYS is not a problem at all... some time ago it was everyday practice, as we had more SYS releases and porting XIP was a bit harder than nowadays. Find a XIP porting tutorial here on xda.
Yes it flashed bright and then went dim. the first boot screen comes but afterwards no tapping instructions and remains still. I changed only MSXIPKERNEL. I get a bootable rom with 21899 SYS and XIP as well with 21916, in the same kitchen. Thanks for all the input.