no2chem nueROM Thread

[sfaure03]

I like this one.. gonna flash my phone w/ it momentarily.. Thx no2chem.

[no2chem]

Originally Posted by dcd

no2chem,

i beleive the dpad issue and the lockups are both attributed to nk.exe from 2.16. Any chance of a 2.14 based XIP? I think (hope) this would fix the few remaining issues.

Thanks for this update though, anxious to try it!!

also, for a cleaner mms fix, feel free to borrow my browser.dll, which will falsely report IEMobile 6.12 in order to render sprint pages correctly with a Sprint:PPC6800 user agent string.

dcd, I remember you asked me about this earlier, and I'll try releasing a XIP with nk from the alltel rom. I wonder if this will reintroduce the alarm issue as well...

Although, to be honest, it seems weird that the issue would be with nk, unless it had to do with how interrupts are handled ... Actually, now that I think of it, maybe it is an issue with how interrupts are handled. When they fixed the alarm, maybe they broke the dpad...

[mdecker79]

But I also had lockup's with the Alltel rom when I was using BT. I guess maybe with the new drivers this might not be the case?

.02

[no2chem]

Originally Posted by mdecker79

But I also had lockup's with the Alltel rom when I was using BT. I guess maybe with the new drivers this might not be the case?

.02

Did the dpad lock up, or did something else lockup?

[dcd]

Originally Posted by no2chem

Although, to be honest, it seems weird that the issue would be with nk, unless it had to do with how interrupts are handled ... Actually, now that I think of it, maybe it is an issue with how interrupts are handled. When they fixed the alarm, maybe they broke the dpad...

ya know, i hadnt thought about it, but im sure you're right that this would reintroduce the alarm issues. i guess atm were stuck choosing between the lesser of 2 problems. ill take another stab at xip porting tonight and maybe this time, i can save you the time

[cykococo]

Just installed and having no issues whatsoever
I also installed Mogul Big Button and 10 button Comm Manager as well MMS and a couple of other programs and no hangups, D pad or BT issues.
Very Stable
Great ROM

[mdecker79]

Originally Posted by no2chem

Did the dpad lock up, or did something else lockup?

I wasn't having the issue with your rom I was just stating the issues I was having with the Alltel rom. Just thinking that the Alltel lock up issue might come back if you were to go down that route.


Sorry for the confusion.

Just to chime in. I haven't tried this Rom yet but I've tried your other Roms and I did have the d-pad lockup issue and it was always on a 2.16 rom/mix. It may just be coincidence but that's been my observation. You guys are doing a great job so I know you'll figure out something. My preference would be to have the Alarm issue vs. the d-pad issue...(I don't use the alarm anyway). Thankx guys.

[no2chem]

Originally Posted by dcd

ya know, i hadnt thought about it, but im sure you're right that this would reintroduce the alarm issues. i guess atm were stuck choosing between the lesser of 2 problems. ill take another stab at xip porting tonight and maybe this time, i can save you the time

maybe I should do a little write-up on how to port xip. essentially:

don't dump with rommaster (manually extract the rom)
to do this, first nbsplit, then on payload...
run imgfsfromnb. write down the imgfs start location.
open os.nb.payload with hex editor. go to the imgfs start location, and delete to end. go to the beginning of the file, and search for FE 03 00 EA (unconditional branch to 00 03 FE), and find the second / last occurance. (this is the second xip).
delete everything from the beginning to just before the second branch.
save this as your xip.bin

open xipport. press dump xip.bin. move stuff around, checking the maps between the donor xip and your xip. when you're done, press realloc p, and write maps. if any area shows !!!, fix it. (usually, modify realaddress[r] in imageinfo.txt, where r is the xipregion).

technically, you might need to check the nk.exe pointer in S000 of nk.exe, but i think realloc p fixes that (maybe). if you're worried, from the old map of the xip (not from the donor, but your device), search for the rom_00 header, look at where it starts, check if it matches with the new map If it doesn't you'll have to do this: if the old start address is 8ABCDEF9, search S000 of nk.exe for F9 DE BC 8A (just an example), because of the endianess of arm. replace with new start address, be sure to reverse it as well.

once you're done, write xipout.bin, and write it to os.nb.payload at the right xip2 address (for the titan, its 3200000) (sleepy and not sure if i put the right amount of zeros, but the default is 3100000, so change the 1 to a 2.)

hopefully everything boots up after this. I've used this technique to change everything except nk.exe... which is device dependent, so you'll have to do other stuff...

http://www.airscanner.com/pubs/fogieDC11.pdf is a good reference for arm assembly opcodes

[no2chem]

Originally Posted by cykococo

Just installed and having no issues whatsoever
I also installed Mogul Big Button and 10 button Comm Manager as well MMS and a couple of other programs and no hangups, D pad or BT issues.
Very Stable
Great ROM

you know that the dialer and 10 button comm manager are built into the rom, right?