Iolite ROM porting

[vonmolk]

Just had a few questions to the cooks out there maybe can help me solve why porting the Iolite rom to the tilt is becoming an epic failure for me. I have tried xip porting three different ways with all the same results. First two i get a double beep than tap screen, but i can not tap the screen to get it to go on. Third way got single beep than tap screen and once again no response from the screen. I copied the sys over and g'relocd it. I have tried this with the 3.34 base. Do i need anything else? Is it necesarry to have the manila 2d included? Also on another note I tried with the AT&T rom as a base which works fine except the folders are empty and I can not make any data connections.

[mbarvian]

how did you port the SYS?

sounds like an SYS issue :)

[vonmolk]

I copied the SYS from the Iolite rom and ran g'reloc to the proper values. Unless im doing something wrong there. I have done the same when porting the blackstone roms minus the dpi192 folders. For this I just copied it all. Must i keep the dpi96 folders from the original rom for it to work. If so I feel noobish lol. on another note I also did try just copying the gwes.exe and the other per your sys porting guide (Thanks Mbarvian) and had the same results. Unless my XIP porting is not happening correctly.

[KMFM$]

Just had a few questions to the cooks out there maybe can help me solve why porting the Iolite rom to the tilt is becoming an epic failure for me. I have tried xip porting three different ways with all the same results. First two i get a double beep than tap screen, but i can not tap the screen to get it to go on. Third way got single beep than tap screen and once again no response from the screen. I copied the sys over and g'relocd it. I have tried this with the 3.34 base. Do i need anything else? Is it necesarry to have the manila 2d included? Also on another note I tried with the AT&T rom as a base which works fine except the folders are empty and I can not make any data connections.

Well, I can confirm this issue. See my post here.
http://forum.xda-developers.com/showthread.php?t=478647
I thought it was a SYS issue as well. However, I re-ported the SYS, didn't change anything in it. Just g'relocd, and went on. There is just one difference, I only had the touch screen not respond once. Every other time, no problems. Just still receiving that stupid double beep before the tap screen message. I can up a zip of my kitchen for anyone that wants to take a look at it. :/

[vonmolk]

Hey KMFM$

Yeah the double beep thing is weird. The only time I did not get the double beep was when I used the XipportEx thats posted on the forums, but every single time im getting no response from the touchscreen :( Really want to get a rom going. I want to develope a nice rom for the community to use, but I have much learning to do before I release something out. Currently I want to do release something with both a HTC and an AT&T base rom.

[KMFM$]

Hey KMFM$

Yeah the double beep thing is weird. The only time I did not get the double beep was when I used the XipportEx thats posted on the forums, but every single time im getting no response from the touchscreen :( Really want to get a rom going. I want to develope a nice rom for the community to use, but I have much learning to do before I release something out. Currently I want to do release something with both a HTC and an AT&T base rom.

Yeah, that double beep is just driving me nuts. Off hand, do you know if you're using the XIP porting utility from ervius' (from the XIP Porting Tutorial in Dev&Hacking) or the similar one posted by lennysh? Also, are you using the SYS supplied in anryl's kitchen thread?
Hopefully, we can find an answer for this soon. I would like to release this ROM, but this is just one bug that I cannot deal with. :)

[vonmolk]

Yeah, that double beep is just driving me nuts. Off hand, do you know if you're using the XIP porting utility from ervius' (from the XIP Porting Tutorial in Dev&Hacking) or the similar one posted by lennysh? Also, are you using the SYS supplied in anryl's kitchen thread?
Hopefully, we can find an answer for this soon. I would like to release this ROM, but this is just one bug that I cannot deal with. :)

The three i have used are lenny's which produces the double beep
The manual from post http://forum.xda-developers.com/showthread.php?t=438676 also has the double beep.
Finally the one from ervius does not do the double beeping.
I extracted the iolite rom using htrcie than the packagebuilder. It has worked for me many times.
Still can't figure out why with the HTC rom no touchscreen, but the AT&T rom base works, but is seriously crippled.

[KMFM$]

Interesting. I'm using the XIPPorterEX from Ervius' and I'm receiving the double beep. I'm currently using the XIP and SYS supplied from anryl's kitchen thread. I'm having the hardest time finding the original files for porting. I don't know if I'm just searching the wrong thing or what. Oh well.

[vonmolk]

Interesting. I'm using the XIPPorterEX from Ervius' and I'm receiving the double beep. I'm currently using the XIP and SYS supplied from anryl's kitchen thread. I'm having the hardest time finding the original files for porting. I don't know if I'm just searching the wrong thing or what. Oh well.

I downloaded it from this post here http://forum.xda-developers.com/showthread.php?t=476828

Unless I extracted the XIP incorrectly or the rom itself. Not sure. Could go with the AT&T base and have no data connection and empty folders :(

[mbarvian]

alright,

I just manually ported the XIP and the SYS from the same ROM that you mentioned, and posted them here:

http://forum.xda-developers.com/showthread.php?p=2953748

please give it a try and let me know if it works :)

good luck cooking ;)

[KMFM$]

alright,

I just manually ported the XIP and the SYS from the same ROM that you mentioned, and posted them here:

http://forum.xda-developers.com/showthread.php?p=2953748

please give it a try and let me know if it works :)

good luck cooking ;)

Thanks, mbarvian! I'll give it a go and report back.

[vonmolk]

alright,

I just manually ported the XIP and the SYS from the same ROM that you mentioned, and posted them here:

http://forum.xda-developers.com/showthread.php?p=2953748

please give it a try and let me know if it works :)

good luck cooking ;)

Thanks mbarvian! I'll give it a shot once I get home from work

[KMFM$]

Hmm. Just tried your port, mbarvian. It put me in the same boat as vonmolk. It doesn't make it past the splash screen. I'll try another kitchen and test again. Just for info, I'm using the 3.34 OEM and cmonex's 3.29Hard2 SPL.

@mbarvian: Note, I just took the folders as you had them, mbarvian, and added the OEM. Did you G'reloc the SYS folder? I didn't so I'll give that a try and test next.

EDIT After g'relocing, the ROM works. HOWEVER, I'm still getting the two chimes (beeps) before "Tap screen to setup device" displays. I'm going to try anryl's or abusalza's ports and see if those give the double beep before the "Tap screen" text. Thanks for the help, mbarvian. :)

[mbarvian]

Hmm. Just tried your port, mbarvian. It put me in the same boat as vonmolk. It doesn't make it past the splash screen. I'll try another kitchen and test again. Just for info, I'm using the 3.34 OEM and cmonex's 3.29Hard2 SPL.

@mbarvian: Note, I just took the folders as you had them, mbarvian, and added the OEM. Did you G'reloc the SYS folder? I didn't so I'll give that a try and test next.

Yes, I started with the 3.34 SYS folder, ported over the SYS (everything except the .VM folder), G'Reloc'ed it, and ported the XIP.

that's weird that it doesn't work, I'll look into it

[talonz55]

Hmm. Just tried your port, mbarvian. It put me in the same boat as vonmolk. It doesn't make it past the splash screen. I'll try another kitchen and test again. Just for info, I'm using the 3.34 OEM and cmonex's 3.29Hard2 SPL.

@mbarvian: Note, I just took the folders as you had them, mbarvian, and added the OEM. Did you G'reloc the SYS folder? I didn't so I'll give that a try and test next.

EDIT After g'relocing, the ROM works. HOWEVER, I'm still getting the two chimes (beeps) before "Tap screen to setup device" displays. I'm going to try anryl's or abusalza's ports and see if those give the double beep before the "Tap screen" text. Thanks for the help, mbarvian. :)

Just my $0.02, tested Hyperdragon's version of the Iolite ROM and the two beeps before is present...

[vonmolk]

Just my $0.02, tested Hyperdragon's version of the Iolite ROM and the two beeps before is present...

Yeah noticed that when I tried his ROM out. Just no idea what is going on that is preventing a successful port over of this rom to the kaiser. I see two roms the hyperdragon and anryl's rom out there. Tried your port mbarvian and I get the same results :(

[mbarvian]

Yeah noticed that when I tried his ROM out. Just no idea what is going on that is preventing a successful port over of this rom to the kaiser. I see two roms the hyperdragon and anryl's rom out there. Tried your port mbarvian and I get the same results :(

you have to G'Reloc the SYS again for some reason, before cooking and flashing it ;)

[parleyp]

you have to G'Reloc the SYS again for some reason, before cooking and flashing it ;)

Thanks for posting another base...something else to work with while we wait for 6.5.

[vonmolk]

you have to G'Reloc the SYS again for some reason, before cooking and flashing it ;)

Okay so run g'reloc once close and re-run it or just click do it and than do it again?

I'll give it a shot when i get home tonight.

Thanks Mbarvian for the help and the inspiration to get me start cooking when the tutorial post.

[mbarvian]

Okay so run g'reloc once close and re-run it or just click do it and than do it again?

I'll give it a shot when i get home tonight.

Thanks Mbarvian for the help and the inspiration to get me start cooking when the tutorial post.

yes, just Open G'Reloc, and click "Doit!" until all of the modules are relocated (shown at the bottom of the window). You may have to do it twice or thrice.

No problem, I'm glad to be of assistance where I can be :)

good luck cooking ;)

[vonmolk]

yes, just Open G'Reloc, and click "Doit!" until all of the modules are relocated (shown at the bottom of the window). You may have to do it twice or thrice.

No problem, I'm glad to be of assistance where I can be :)

good luck cooking ;)

Still a no go :( Still have no touch screen on it. Not sure what to do at this point. Really wanted to get a nice iolite port made out. When i g'reloc it says 302 relocated. I closed it and try again same result. Did it thrice sometimes four times. I am at a loss. Never had this much problem porting before untill this rom came around.

[anryl]

u have to depending on kitchen but u have to change metadata default.hv and user.hv from kaiser and extract from iolite registry just what u need as if the kitchen is using them u rom wont boot properly as well with wince.nls dont forget in xip or sys

only new kitchen from bepe dont uses metadata :D

[vonmolk]

u have to depending on kitchen but u have to change metadata default.hv and user.hv from kaiser and extract from iolite registry just what u need as if the kitchen is using them u rom wont boot properly as well with wince.nls dont forget in xip or sys

only new kitchen from bepe dont uses metadata :D

Thanks Anryl. Will give it a shot. I use mbarvian's kitchen both v1 and the new v2. I may give bepe's new kitchen a shot.

[Dany72]

Ok i use KaiserChef v1 and v2. I have same problem of vonmolk.
Please halp me : what is the exact metod to porting xip and sys of iolite on kaiser.
I try many time but touch screen not responding.
Please explain me if there is some tips.
Thanks

Daniele

[raiisak]

As I mention in another post :) when it comes to porting it depends on build ver. ect ect. Its a big try and fail operation for moust of us when thing doesnt work as planned. But to get a true port you have to use m'relloc and manual change values in the modules, there is alot of guides on how to.

On dump of nbh in kitchen it unpacks diffrently (provider to provider or if its a "pure" HTC nbh), anyway the cue is that some of the chef`s use xip files in the ROM folder while other make mxipkernel + mxipkernelLTK in SYS and oemxipkernel in OEM then os.nb+ a folder named XIP in ROM and THAT contains boot.rgu I use the last method which for some reason works best for me.