Dear all,
I downloaded the Herald WM6 ROM from:
tupisdin said:
http://uploaded.de/?id=zi6wyz - ROM Ver 4.12
http://uploaded.de/?id=3duxyy - flasher for SuperCID devices only
Click to expand...
Click to collapse
I could extract the XIP and IMGFS section properly.
What I'm wondering is how to port the Herald's XIP so that it will boot on the Wizard. I tried to use msflshtool.exe to swap an original Wizard WM6 (orwell) XIP section for the Herald XIP in OS.nb, but the OS does not boot!
I'm only getting the version numbers for the IPL, SPL and GSM radio!
Do I need to relocate the XIP modules? My instinct would be not to, since I'm re-using the full XIP from the Herald.
However, the location of all files and modules (I checked with Bepe's XIPPort) is different between Herald and Wizard. So I need at least to update the address from where to load the kernel in memory, I believe.
Does anyone know how to do that?
Any hints/ideas on what to do?
Best regards,
eluth.
eluth said:
Do I need to relocate the XIP modules? eluth.
Click to expand...
Click to collapse
yes, but realloc p button always give errors in bepe's XIPPORT utility
donno whts going wrong.
im doubtful itll work as bepe stated here--
http://forum.xda-developers.com/showpost.php?p=1158510&postcount=53
but again he stated in trinity project thread
http://forum.xda-developers.com/showpost.php?p=1162111&postcount=10
that seems only editing works, may be
Hi everybody,
i dealed with many xip before using big chefs tools (itsme, bepe,...), but the problem with Kaiser is that,
when i tried to put MSXIPKernel contents from newer builds to XIP in ROM folder, then applying bepe tool (which insert xip part into OS.nb at the address 0x00320000) all seems to be ok, but when flashed, the device can't pass the first splash (maybe it is because of relocating modules, but bepe new tools can deal with these without problems)
i hope someone can help,
any tips are welcome.
thanks in advance.
I see alot of new roms using 19209 and even a 19588 rom on the forum. Could anyone please point me to the Sys Oem and Rom files if possible.
I have been using Octavoi 19199 to build a personal rom and I am now at the point where i am pretty happy with the stability of the rom but would like to update the XIP and Sys
Any help would be much appreciated
588 on the hermes forum. there is a whole kitchen just search their forums.
Thanks S.V.I. i found some kitchens. I also managed to extract the 19588 found here using Hypercore but i produce a rom which wont boot.
I have followed each extraction step. Any ideas why it wont boot ?
If you extracted the 588 that was already ported for the wizard, then I believe the os.nb is quite small.
Also, remeber that most cooks delete the rgu's to save space.
You may have added too many ingredients as well.
i Added exactly the same stuff that i use in my custom octaivoi rom except for what was already included. If I built the rom i get a 49mb OS.nb and the normal is about 57. I dropped all my OEM's except for registry tweaks and now i have a bootable rom.
Gonna try my luck at cleaning out the sys folder.
Hi All im a noob to cooking. So... I dumpbed the new official rom and used the cooking tutorial to cook my very first rom YAY. BUT when my titl boots it is WM6 not WM6.1 and a few other small issues like the boot screen not showing the verion number i changed it to. I used itsutils to dump and kaiserkitchen to cook. I have searched the forum but can't find anything. Pls help
WHy are you using itsutils to dump the ROM. Just extract the .exe rename it to RUU_signed.nbh and dump it using the kitchen....
Much easier and more fool proof this way.
joerf1115 said:
Hi All im a noob to cooking. So... I dumpbed the new official rom and used the cooking tutorial to cook my very first rom YAY. BUT when my titl boots it is WM6 not WM6.1 and a few other small issues like the boot screen not showing the verion number i changed it to. I used itsutils to dump and kaiserkitchen to cook. I have searched the forum but can't find anything. Pls help
Click to expand...
Click to collapse
Sounds like youve done more work than nessessary! Do like ryncppr said above, use the lastest pagepool patcher to change version number on boot. Don't know why you would want to though!
thank you ryncppr and yardie.spike.. That was just a small issue i wanted to change but the main issue is that the rom created from the kaiser kitchen is WM6 and not the new OS. What am I doing wrong?
[Cooking] Need Help Clearing out the bloatware
ok I solved the issue with the rom being WM6 and not 6.1. I just deleted the ROM, OEM and SYS folders and the os-NEW.nb file. Then I extracted the rom I dumped from the phone and I can now cook a 6.1 rom. BUT the issue I have now is all the bloatware is on there still with the software I selected during the cooking process. How can I remove all the software that came with the ATT rom?
[EDIT] Okay I have been messing around in the OEM, SYS and ROM folders...Is this the right place to remove the oem software and if so how do I go about doing it. I found, in the OEM folder, the EXEs for the shop stuff...can i just remove those or are there othere files I need to edit as well...pls help I just want to learn
OK for those wanting to cook their own rom from the ground up, below is a link to help with cleaning up the BaseROM.
http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
Hi folks,
After messing around for a while, I finally created my own ROM and sucessfully flashed to my wing. It all works, but it has out dated build. I am using Ivan's guide and Hypercore to cook my room. Here my question. In hypercore, when I extracted the XIP, all the files in the XIP folder are binary. However, from the Hermes forum, they posted the base SYS and XIP for the newest build, but they are in package format. Can I use this new SYS and XIP in Hypercore? If so, how? Thanks
As long as you port the XIP and SYS as per my XIP porting guide, then yes. But you can't port the XIP using Hypercore alone. You'd have to use Bepe's extended kitchen. This kitchen will automatically fix the memory addressing for you. The memory addressing of the the SYS you can easily fix by running G'Reloc after following my walkthrough for XIP porting.
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
live4nothing said:
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
Click to expand...
Click to collapse
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
ivanmmj said:
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
Click to expand...
Click to collapse
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
live4nothing said:
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
Click to expand...
Click to collapse
I tired that build as well and it had issues, thats why I went with 20748 instead.
Also, if you compare the size of the sys folder for build 20753 and another version, you will know why it's faster.
Just and FYI,
Good tips. Also, you have to build the ROM from within Bepe's kitchen. That way, it runs G'reloc on the XIP as well. Or, run the G'reloc with the following AFTER running BuildOS but before actually building the ROM. "G'Reloc.exe -doit -dump"
Ivan and Tony, Thanks. One will try the 20748 build later this week if I have time. However, I have one more question. I look around the forum, I saw there are two type of xip like this:
XIP: (bigstorage)
20753_XIP 09/19/2008
20755-XIP 09/23/2008
To Make XIP/ROM Non-BigStorage or Real BigStorage:
Copy this over existing rom folder
What the different between bigstorage and non-bigstorage or real bigstorage? Which one should I use for our wing/herald? Again thanks for your your help.
Those bigstorage do not apply to our ROM's. Our devices do not store data in the same way as BigStorage compatible ROMs. Our BigStorage comes from stripping the extra crap out of our ROMs.
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
live4nothing said:
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
Click to expand...
Click to collapse
You can use any SYS and XIP that isn't a ROM that has been made with certain kitchens... The issue is that you have to G'reloc the OEM, SYS and XIP within the same kitchen while they're in the same directory. G'reloc will only relocate the modules it sees and if it relocates them seperately, it might set the modules to the same memory address as the other G'reloc did with the OEM package.