Related
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,
I've done research on the forum here and found that to unlock the full 576 RAM in HD2 you need two things from the TMOUS ROM. The Radio and nk.exe. I've managed to download the appropriate Radio to unlock the memory but cannot for the life of me understand how to get the nk.exe.
I am using osKitchen Kitchen v1.25 to cook my roms. It uses the following structure under the Sources folder:
EXT
MSXIPKernel
NK
OEM
Other
ROM
SYS
Replacing the NK folder in the TMOUK kitchen from the TMOUS ROM simply does not work the resultant ROM does not boot and just hangs the device.
Could one of our chefs please explain how to port the nk.exe from the US build to unlock the memory in the T-Mobile UK ROM 1.72.
Using the following 576-enabled Radio
RUU_Leo_Radio_15.34.50.07U_2.08.50.08_2
Many thanks in advance
Mod edit: SOLVED
thecrater said:
Hi,
I've done research on the forum here and found that to unlock the full 576 RAM in HD2 you need two things from the TMOUS ROM. The Radio and nk.exe. I've managed to download the appropriate Radio to unlock the memory but cannot for the life of me understand how to get the nk.exe.
I am using osKitchen Kitchen v1.25 to cook my roms. It uses the following structure under the Sources folder:
EXT
MSXIPKernel
NK
OEM
Other
ROM
SYS
Replacing the NK folder in the TMOUK kitchen from the TMOUS ROM simply does not work the resultant ROM does not boot and just hangs the device.
Could one of our chefs please explain how to port the nk.exe from the US build to unlock the memory in the T-Mobile UK ROM 1.72.
Using the following 576-enabled Radio
RUU_Leo_Radio_15.34.50.07U_2.08.50.08_2
Many thanks in advance
Click to expand...
Click to collapse
For the 576MB patch you need only to replace these folders from an 2.07 or 2.02 Stock-Rom:
Rom\XIP\OEMXIPKernel\nk.exe
OEM\OEMDrivers
OEM\OEMDriversHigh
Then you need to replace again with this folder
OEM\OEMDrivers\ddi.dll
with an older Base than 2.07/2.02 (1.72 in your case is recommended)
patensas said:
For the 576MB patch you need only to replace these folders from an 2.07 or 2.02 Stock-Rom:
Then you need to replace again with this folder
OEM\OEMDrivers\ddi.dll
with an older Base than 2.07/2.02 (1.72 in your case is recommended)
Click to expand...
Click to collapse
Why ddi.dll ? mine works fine with new 2.13/2.11/2.10 ddi.dll
patensas said:
For the 576MB patch you need only to replace these folders from an 2.07 or 2.02 Stock-Rom:
Rom\XIP\OEMXIPKernel\nk.exe
OEM\OEMDrivers
OEM\OEMDriversHigh
Then you need to replace again with this folder
OEM\OEMDrivers\ddi.dll
with an older Base than 2.07/2.02 (1.72 in your case is recommended)
Click to expand...
Click to collapse
Thank you very much indeed for your kind help. It worked perfectly
Hi, I'm a newbie for ROM cooking, experienced cookers, please advise.
I'm using HD2/Leo phone, I learned how to use HSPL, flash a cooked ROM, so I'm start thinking of cooking the ROM my own, and what all I need is retain original 1.66 707.1 Asia WWE version of stock ROM, but only to enable 576MB RAM.
I found a kitchen, oskitchen zero 1.31, use the GUI and extracted the stock ROM, and stop here, because I don't know how to cook the ROM...
Experienced cookers, please advise, thanks in advance!!!
patensas posted like 2 posts up from yours which files you need to replace.
which means that i just copy all the folder need, then paste inside the osKitchen Zero folder, and finally click "Start building button" to cook my ROM...?
I also want to know why ddi.dll need to be remain old version?
OEM\OEMDrivers\ddi.dll
hello fellow chefs
i am trying to make a verry smooth rom in dutch for soem friends of mine
it is working out quite well but i want to enable the 576 ram tweak
in patensas his post he says i need to change things from a tmous rom
if i use the tmous 2.13.531.1 as base rom do i still need to change those folders?
thanks in advance
sorry to ask but coul some one upload the files to make the 576 mb tweak?
i have 2.13 tmous as base in the kitchen and it would save me a download and dump
thanks in advance
All you need is in the 2.13 TMOUS.
pkoper said:
All you need is in the 2.13 TMOUS.
Click to expand...
Click to collapse
then i dont get it:-o
i installed Leo_RADIO_15.34.50.07U_2.08.50.08 on the phone but no 576 mb tweak:S
Using 2.13 base you should have 576 anyway.
What did you change?
pkoper said:
Using 2.13 base you should have 576 anyway.
What did you change?
Click to expand...
Click to collapse
to be honest i have no idea why it aint working
when you got the settings tab and scroll down to device info
there you choose hardware info it should also say 576?
the thing i did is dump the tmous 2.13 rom with ervius
then i took out the 0409 folder in oem and replaced it with the the one i use for blackstone(maybe the fault is here) then i replaced the ext packages with the ones i use i blackstone kitchen(compared wich are unnesacary and left those out) and then recooked the rom
i also decided today that i am gonna rebuild the entire kitchen from scratch without copy pasting the 0409 folder in oem and set everything up from there and remake the initflash.dat the way i want it
i havent changed the ddi.dll so that might be the trick why it aitn working
on side note:
wish i whasnt in the middle of moving and had the actual device for a few days
that would definetly make things easier for me
ps: what do you think is the best base to use to build the kitchen on with ervius kitchen
tmous 3.14? it would sound logical that newer is better although there are differences between the american and european leo's
Hi all !
I'm trying to cook a personal custom rom I just want to change the build from 6.5 to 6.5.X of the official htc 3.14 italian rom. I would also like to enable the 576 mb of ram. I have already installed on the phone the 2.15 radio, what files I need to change inside the kitchen ( I use oskitchen ) ? I have a t-mobile.uk hd2 ( I have bought it from england.
so I think that it's the european version )
light_n_roses said:
Hi all !
I'm trying to cook a personal custom rom I just want to change the build from 6.5 to 6.5.X of the official htc 3.14 italian rom. I would also like to enable the 576 mb of ram. I have already installed on the phone the 2.15 radio, what files I need to change inside the kitchen ( I use oskitchen ) ? I have a t-mobile.uk hd2 ( I have bought it from england.
so I think that it's the european version )
Click to expand...
Click to collapse
Take the nk.exe(from oemxipkernel) from 2.13 tmous.I think also the nk.exe from 3.14 tmous should be ok but I havent try it.
Could someone just post an attachment with the modules needed to enable the extra RAM? I'm sure it would make it easier for everyone. I'd do it, but I don't have an hd2.
Farmer Ted said:
Could someone just post an attachment with the modules needed to enable the extra RAM? I'm sure it would make it easier for everyone. I'd do it, but I don't have an hd2.
Click to expand...
Click to collapse
The way that the European Leo device gets the 576 ram enabled is the following:
Replace the nk.exe with the nk.exe from TMOUS rom (in Sources\Devices\HTC Leo\Profiles\default\OEMXIPKernel folder for oskitchen, or \ROM\LEO\build number\OEMXIPKERNEL for ervius kitchen).
I attach the 2.13 tmous and 3.14 tmous nk.exe modules.Both do the trick or enable the 576 ram (for those who believe it).
Personally in my Leo I didnt see any difference with the 576 ram enabled.
After reading the post that transplanting 2.14 nk,2.14 OEM_Misc.dll to 3.04 can solve the problem of FM-radio. But I find another problem that the WIFI MAC address change to xx-xx-xx-xx-xx-xx. Absolutely it's fake,and in some conditions it may do some trouble. So I want to know if there's some ways to solve this problem.
I have solved this problem by myself....
just replace the proper version of bcmsddhd.dll
Thanks xda-developers...
Hi,
which combination do you use?
Base ? and bcmsddhd.dll from ?
with friendly greet
starbase64
starbase64 said:
Hi,
which combination do you use?
Base ? and bcmsddhd.dll from ?
with friendly greet
starbase64
Click to expand...
Click to collapse
I would like to know this too. Thanks!
to fix wifi if you cook a non-asian rom:
take bcmsddhd.dll from a non-asian rom (for example 2.13.531.1 - NOT2.14 because it's asian).
to fix the fm-radio issue in the 3.xx-base you should be able to use the 2.14 asian files.
Thx , i didn't find for FM radio bug in my cook , now it's ok . Thx, Thx , Thx
Use 3.14 drivers as they are. and no need to mix anything.
They work fine for me..
c_shekhar said:
Use 3.14 drivers as they are. and no need to mix anything.
They work fine for me..
Click to expand...
Click to collapse
i think ur referring to Tmo-US leo rom 3.14 drivers..
the 3.14 drivers from original htc rom have issues when used with nk.exe from tmo-US rom (and you'd wanna use tht nk.exe to get rid of the low ram issue)
Only the nk.exe needs to be swopped to fix memory, oemdrivers work fine just as they come.
No problems with the FM radio, nothing needs to be fixed.
jjblaster3 said:
i think ur referring to Tmo-US leo rom 3.14 drivers..
the 3.14 drivers from original htc rom have issues when used with nk.exe from tmo-US rom (and you'd wanna use tht nk.exe to get rid of the low ram issue)
Click to expand...
Click to collapse
jjblaster3 said:
i think ur referring to Tmo-US leo rom 3.14 drivers..
the 3.14 drivers from original htc rom have issues when used with nk.exe from tmo-US rom (and you'd wanna use tht nk.exe to get rid of the low ram issue)
Click to expand...
Click to collapse
@lauretius26 is right. There absolutely no issues at all...
@Laurentius26 and c_shekhar:
i haven't tested but i guess you guys are right.. the only explanation going through my mind is that the 2.13/2.14 nk's from tmo-us were not compatible with the 3.14/3.04/3.02 oemdrivers from Leo S roms, but since there was a 3.14 tmo-us update (meaning a 3.14 nk) it now is compatible with those oemdrivers i guess
hello fellow chefs
since shortly i became aware that bluetooth isnt working on the hd2 rom i made:-o
the thing i did is download the 1.66 dutch rom and dump it with ervius kitchen(i use this ktichen for rom making)
i changed the ext packages to the ones i use for blackstone and changed a few packages with the original 1.66 packages like dshow, concurrence manager, camera, fm radio and comm manager
then i rebuild it and it looks the same as on my blackstone and almost everything works except bluetooth
when i go to start>settings>bluetooth i get the screen that bluetooth isnt on and if i want to turn it on
when i press yes i get the message that the bluetooth stack cant be started
when i flash a kwbr rom bluetooth works so it isnt a mailfunction of the device
also yesterday before the server crash i posted a thread for this and af974 posted that the bleutooth settings whas a package he had never seen in leo roms although i get it from the dump of the dutch leo rom 1.66 and 1.72 vodafone roms so whats up with this package:S
i atach my buildlog and want to thank for any tips on how to solve it
edit: i just checked with other leo roms i have stored and when i looked at 3.01 wwe rom the oemdriver and oemdriverhigh folders are in total 3 mb bigger then the ones i get from the dutch roms
you think i can change it with those? as i dont quite understand the differnece between the american and european leo's:S
And you also played with SYS.
Best to take a look at a SYS from a stock rom. The HD2 has a few things that are in OEM.
You can definatly removing following from your SYS:
Bluetooth Included -> is in OEM
IRDA -> Leo does not have infa red port
SMS_Providers
WinCENLS_WWE -> in XIP
and a few more, just compare an original with yours
pkoper said:
And you also played with SYS.
Best to take a look at a SYS from a stock rom. The HD2 has a few things that are in OEM.
You can definatly removing following from your SYS:
Bluetooth Included -> is in OEM
IRDA -> Leo does not have infa red port
SMS_Providers
WinCENLS_WWE -> in XIP
and a few more, just compare an original with yours
Click to expand...
Click to collapse
thanks mate
never thought there could be bluetooth there:-o
just took the entire sys/xip folders i use in my blackstone kitchen
hey, i had the same problem as you some time ago. it was because of my modifications in initflashfiles.ini, check if
"Directory("\Windows\AutoStart"):-File("BTTrayCE.lnk","\Windows\BTTrayCE.lnk")"
is in yours or any other app.dat
maybe this will help you
lauchi said:
hey, i had the same problem as you some time ago. it was because of my modifications in initflashfiles.ini, check if
"Directory("\Windows\AutoStart"):-File("BTTrayCE.lnk","\Windows\BTTrayCE.lnk")"
is in yours or any other app.dat
maybe this will help you
Click to expand...
Click to collapse
thanks for the tip
dont have this in the 0413 initflash but i do have it in the english one i have:S
will put it in to be sure
also deletd the files from the sys folder wich i compared to the one from the dumps i have from leo roms
only downside is i forgot to take out cmbluetooth so it didtn work
gues you guys dont use that in the leo rom?
didnt see it in the dumps
miniterror said:
thanks for the tip
dont have this in the 0413 initflash but i do have it in the english one i have:S
will put it in to be sure
also deletd the files from the sys folder wich i compared to the one from the dumps i have from leo roms
only downside is i forgot to take out cmbluetooth so it didtn work
gues you guys dont use that in the leo rom?
didnt see it in the dumps
Click to expand...
Click to collapse
Nope don't use it on the Leo and you need bttrayce to start at bootup to be able to enable bluetooth
hmmm
made sure that Directory("\Windows\AutoStart"):-File("BTTrayCE.lnk","\Windows\BTTrayCE.lnk") whas in the initflash.dat file and took out all bluetooth packages out of sys and ext packages but still no bluetooth:S
gonna try changing to 2.13 base
any one knows of fixes are needed there
What error are you getting when you try to start bluetooth?
EpiphanyNL said:
What error are you getting when you try to start bluetooth?
Click to expand...
Click to collapse
de bluetooth stack kan niet gestart worden
or in english the bluetooth stack cant be started
i am trying to make a dutch rom and i wha slooking at the iniflahs again yesterday and i saw i used the english lines in a dutch rom so that whas a little wrong
yesterday evening i changed base drivers to 2.13 and gonna flash it somewhere today as i dont have the actual device myself
edit:
used 2.13 as a base and bluetooth can start now but i cant make it visible
gonna say to my friends they need to wait and ill redo the kitchen again but with alot less copy pasting
and translate the entire initflash.dat(or use one from 1.66 nld base)
miniterror said:
(or use one from 1.66 nld base)
Click to expand...
Click to collapse
That's what I did
thanks
thnx a ton buddy ur trick worked... feeling so relaxed now....