Related
I'm trying to port WM6 AKU 0.7.0 to Atom Life devices. Almost all XIP modules were relocated well, however, giisr.dll always conflicted with coredll.dll. (hd.dll and oxast0.dll also conflicted with others, but they are not core files and can be deleted to avoid issues.) The same problem happened when people tried to port WM5 AKU 3.5.2 to Dell X51v devices, but they later managed to solve it prefectly. No documents about this problem could be found. Please help me. Thank you very much.
BoomerCE said:
I'm trying to port WM6 AKU 0.7.0 to Atom Life devices. Almost all XIP modules were relocated well, however, giisr.dll always conflicted with coredll.dll. (hd.dll and oxast0.dll also conflicted with others, but they are not core files and can be deleted to avoid issues.) The same problem happened when people tried to port WM5 AKU 3.5.2 to Dell X51v devices, but they later managed to solve it prefectly. No documents about this problem could be found. Please help me. Thank you very much.
Click to expand...
Click to collapse
did you connect device in KITL mode to PC with PB6? How did you trace it to giisr.dll? you can also try to just change single module coredll.dll
Actually, this is my next step for the ATOM, but have not started on it yet.
Thank you very much, Mr. Jiggs
About this problem, seems I can't solve it now... I'm going to study further.
Another question is, how can I change the version information, including OS Version, build, AKU, and Language of the ROM file? (Read by bepe's package tool as shown in the picture, not in Version.TXT. I heard that this is stored in some DSM files.) Thanks!
BoomerCE said:
Thank you very much, Mr. Jiggs
About this problem, seems I can't solve it now... I'm going to study further.
Another question is, how can I change the version information, including OS Version, build, AKU, and Language of the ROM file? (Read by bepe's package tool as shown in the picture, not in Version.TXT. I heard that this is stored in some DSM files.) Thanks!
Click to expand...
Click to collapse
Although we can change the version in the DSM, the Atom does not reflect it, and only bepe's package tool can detect the change. For me, it is not advisable to change it. Just use the official files, and they will be reflected.
Hey, you have a new package tool. Where did you get it?
Seems that current version of SRPX tools cannot work properly. I just extract Atom Life's original XIP using MSFLSHTOOL, SRPX2XIP it and then XIP2SRPX, then replace it back (note that I didn't edit anything), and flash the image. The device simply don't boot.
BoomerCE said:
Seems that current version of SRPX tools cannot work properly. I just extract Atom Life's original XIP using MSFLSHTOOL, SRPX2XIP it and then XIP2SRPX, then replace it back (note that I didn't edit anything), and flash the image. The device simply don't boot.
Click to expand...
Click to collapse
how did you do it? step-by-step... Did you use format I send breakdown.bat?
All tools (including the package tool) that I used came from Scoter Kitchen, and your batch had some bugs that it couldn't work. Of course I know how to use these tools, and I successfully extracted and dumped Atom Life's original XIP (WM6 AKU 0.2.1).
And I still need your help editing the version info in DSM because if I don't change it, Package Tool will cause trouble in my complete localization in Atom Life's ROM. (Base ROM: 0404 - Chinese Traditional, Object: 0804 - Chinese Simplified. Now all related keys in registry modded, all modules in IMGFS successfully edited, and .0804.MUI files I placed in fully worked. Flashed and worked perfectly.) Thank you very much.
So it proves that XIP2SRPX tool has bugs and cannot be used on Atom Life's XIP2.
Here is the project I'm working on... Please help me with the only file giisr.dll... Thank you very much!
http://rapidshare.com/files/58185699/XIP.rar
DCD if you dont like what im doing just tell me to delete this post and i will.
All credit goes to DCD one of the best kitchen and Rom maker's out there.
If it wasn't for him our 6800's would be almost useless.
This is for the people who are using the titan kitchen. I took DCD's latest build and repackaged it for the PPCKitchen.org Titan Kitchen located
here http://forum.ppcgeeks.com/showthread.php?t=23206
Place it in your BuildOS/Kitchens directory and then extract "Titan_DCD_3.01_Selections.txt" and place it in the BuildOS/Projects directory.
Now you can create your own custom DCD rom using the new kitchen and DCD's latest build.
I've been using this for about 20 hrs and the rom is very stable.
Thanks again DCD u Da MAN!!!!!!!!
Make Sure to remove---> _fixed <---from the end of the file before u place it in the kitchens folder.
Download
http://rapidshare.com/files/108106961/Titan_DCD_3.0.4_FIXED.rar REALLY FIXED this time LOL
thank i'm looking for this. I ran into error error nk.dat
AstronusX said:
thank i'm looking for this. I ran into error error nk.dat
Click to expand...
Click to collapse
Sorry i forgot to change it from os.paylod to nk.fat, im up loading a fix right now thanks.
Errors in PPCkitchen
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
mfrish said:
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
Is this your first time using the kitchen?
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Thanks will try. The BuildOS in the regular kitchen is crashing so I can now cook a kitchen.
Also will my OEMs made for the 3.0.1 rom work if I put them in the build os directory. I didn't use the OEMizer w/ BuildOS. It appears to be the same just w/ a different save directory.
azclown said:
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Click to expand...
Click to collapse
No prob az i forgot about getting rid of those files. I thought i got all of them. I will upload a new file with the fixes for those who haven't downloaded it yet.
NEW FILE UP LOADED
Let me know if its working for you guys
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
drgreenberg said:
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
Click to expand...
Click to collapse
The sliding sounds module is in the DCD OEM's folder......when u open it up in the kitchen it should come up as a selectable OEM. At then point all you have to do is select it.
Bell?
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
jondixon said:
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
Click to expand...
Click to collapse
I don't know if it does.Are you are referring to the ppckitchen or DCD's Kitchen?
What i have provided is just a modified version of DCD's work (all credit goes to him) that will work in the ppckitchen.
You can check over here http://forum.ppcgeeks.com/showthread.php?t=23206
if you are talking about the ppckitchen, and they should be able to answer your questions.
If you asking about the DCD kitchen you can ask over here http://forum.xda-developers.com/showthread.php?t=385336 and im sure he will help you out.
I guess the obvious question is, what's the difference between the two kitchens?
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
gguruusa said:
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
Click to expand...
Click to collapse
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
error
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
azclown said:
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
Click to expand...
Click to collapse
Could be because DCD has only a little to do with what we're talking about (which I gave him credit for). That's Bepe's buildos you're looking at, and essentially what we're comparing is Bepe's buildos w/ DCD integrated against PPCKitchen's buildos w/ DCD integrated.
You can't seriously suggest that Bepe's buildos is easier to use - the interface is practically identical! Both are about the same difficulty to use in their most basic, unaltered configurations, and both can build a basic rom w/ 2 clicks. Installing, configuring, starting, and maintaining is a lot different however...the nod hands down goes to ppckitchen there. Once you get past a basic configuration, PPCkitchen's buildos is unchallenged.
The proxy/firewall thing is fixed (general release this weekend) and it doesn't log IPs (never has).
Bepe's buildos get's the nod for no internet connection required, and the previous version (I don't know about v2) get's the nod for Linux compatible. Bepe's buildos also get's the nod for being more interfaceable to other projects and having more projects using it, but none of that is related to the original question (except maybe linux compatibility). [EDIT: v2 isn't native linux compatible, so no nod there.]
All of this is not too suprising, as PPCkitchen's buildos is, at it's core, an evolution of Bepe's Buildos.
I give credit to all sources DCD's kitchen / PPC Geeks kitchen and more.
They both offer the tools to make a ROM to your likings, some better then other, but the fact of the matter is that it gets the job done.
What PPC Geeks version is doing is making a bit more user friendly ( in my opinion ), but I still used DCD's kitchens because I really don't add any extra OEM's to my ROM's unless it is a specifically Themed ROM and then again I can get it done with both kitchens with ease.
I guess users will just have to test them both out themselves to see if they prefer one or the other.
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Im sure with all the developers on this forum and on ppcgeeks we would be able to get this done some time in the future.
Just an Idea....
[email protected]$ said:
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Click to expand...
Click to collapse
PPCkitchen buildos is actually the closest you can come currently for easily swapping components around, and there's a universal kitchen here on xda that supports many devices (way more devices than PPCkitchen does).
Don't hold your breath on the hardware emulator
lightbiter said:
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
Click to expand...
Click to collapse
You'll have to elaborate a little better. If I had to guess, however, I'd say that you might have an older version of winrar installed. As a workaround, you can manually extract and modify the selections to use the extracted dir instead of the .rar.
Note for Mods: If you feel that this thread belongs to some different forum, feel free to move it (coz i also have this feeling, but i am not clear
Hi Friends,
I have seen this discussion many times that the older GReloc cannot be used for relocating newer, WM 6.5 SYS. While this is partially true, there is a workaround for this that I have been using with last 2-3 WM 6.5 ROMs that i have cooked for myself. So i thought it will be good for all the fellow chefs and wannabes if i share this info with you.
Although the new tool WMReloc can be used in place of GReloc, i don't find it as user friendly as GReloc and since GReloc works for me, there is not enough reason for me to switch over. Also, once or twice i have seen reports of WMReloc doing overlapping of addresses while the relocation process which defy its sole purpose.
So here is the method I use :
1. Download Unlocker from Here. This will help you unlock files that are currently in use by other programs so that you can copy move and delete them. Install it and on every file and folder you'll get a new entry in context menu called "Unlocker".
2. Now start Greloc.exe and fill in proper values if needed. Click "Do It". When it gives Integer Overflow, click OK but dont close it. Press "Do It" again and this time it will show you the file that is givin error in the message box, mostly its a .tmp file.
3. Go to the file, right click on it and select "Unlocker". In the box that opens, on the right hand, choose delete in the dropdown box. Now click Unlock All. This will delete the file.
4. Click "Do It" in GReloc Window again, this time it will complete the process. If the error comes again, for a different file (never happened with me though), repeat this process.
5. To be sure, run GReloc once again and it will complete the process successfully in one go.
Explanation:
Although I don't claim to be an expert on this subject, As far as my understanding goes, the problem lies within the algorithm used in GReloc. It uses integer data typed variables for doing whatever it does during the relocation process and with Wm 6.5, somehow the value stored in one of these variables crosses the upper or lower limit of the allowed range for integer variables.
Now, In the process of relocation, GReloc creates a tmp file based on the contents of the modules it is relocating. When error occurs GReloc stops as it is and doesn't closes the handle to this tmp file. This causes the process of relocation to fail on successive attempts.
What we do is we unlock this file forcefully using unlocker and delete it. This way, GReloc restarts the relocation process from that module again and the problem is solved.
Happy Cooking!
Hi sumit,
Great tutorial. It'll be aplicable not only to wm6.5 but to wm6.1 as well. In some wm6.1 roms i have the same problems.
this is temporally solution if u want to know how to use wmreloc i will tell u
but if you r using ramersonw kitchen it will little bit trick becoz tool folder comes when you start kitchen
i have my own kitchen witch support wmreloc 1.4
@ ramersonw
if u want to add wmreloc support to your kitchen contact me , and what about your visual kitchen ? is it done ? tell me if you want any help .
@Ankit: Yes its a temporary solution, it was working for me for last few roms so i thought it may be of some use to others also. And Yes, Please post the tutorial for using WMReloc.exe either in this thread (I'll rename the title of thread in that case) or in a separate thread, as you find it appropriate. That will be really good. Try to post the necessary tools with it too, like the WMReloc.exe file itself and anyother thing needed to use it.
In Ramerson's kitchen, the tools folder is created at start of the process, and buildos runs for atleast a minute or two, so the files in tools folder can be replaced in that period.
@Ramerson: Ya, the problem can occur in WM 6.1 also. I think it has to do something with the number of files that GReloc is relocating. Actually at the start of the relocation process, GReloc seems to be calculating which files needs to be relocated, and if this number exceeds a certain limit, that i am not aware of yet, it crashes. But when the relocation process is resumed from the point of error, number of files to relocate comes within the range and then GReloc continues. Great thing is that GReloc is a .NET app and exception handling has been done quiet intuitively otherwise there was no chance to resume this process.
Anyways Buddy, These are just assumptions and are working for now but this may not last for long so i think its really the time to update your kitchen. I request you to either you do it, or please share the code with me and i will try to understand and port it to .NET for further development.
krazy_about_technology, hi, put that in the attache a folder tools in their kitchen. And replacement following -" GReloc-doit-dump" on - "start / w "" tools \ WMReloc.exe-g. \ Temp \ dump-lWMReloclog2.txt"
Good luck
@ankit
this is temporally solution if u want to know how to use wmreloc i will tell u
but if you r using ramersonw kitchen it will little bit trick becoz tool folder comes when you start kitchen
i have my own kitchen witch support wmreloc 1.4
Click to expand...
Click to collapse
can u upload ur kitchen for wm6 & 6.5 plz ............
ankit360 said:
this is temporally solution if u want to know how to use wmreloc i will tell u
Click to expand...
Click to collapse
Please can you write tutorial on this?
In my case g'reloc missing S001 file, iam forget which module, so i use wmreloc, it was working well.
Xumit said:
Please can you write tutorial on this?
Click to expand...
Click to collapse
change
G'Reloc -doit -dump
with
wmreloc -gtemp\dump
swapnil_0081 said:
@ankit
can u upload ur kitchen for wm6 & 6.5 plz ............
Click to expand...
Click to collapse
You can download ankit wm6.5 kitchen, edit file build.cmd in the tools folder,
find line
start /w "" Tools\G'Reloc -doit -dump
change it with
start /w "" tools\wmreloc -gtemp\dump
save the file.
copy wmrelox.exe to tools folder
The file missing is in either marketplace or my phone. I got that message too. I removed these two packages and thereafter the process went smoothly. WMReloc skippes these files. Did you checked whether these services are working in your wmreloced rom?
I can't found it in wmreloc log, but it work well in my gene
I will give you solution very soon
I recently have found that to have a rom fit for my needs and to work properly with my exchange server settings, etc. that I need to rebuild roms (easier than starting from scratch). I am not planning on re-distributing them, they are mainly for my use, and others that use a specific exchange server setup like I do.
Anyway onto my main question:
Using the different tools I have found through Google and xda-developers, I have started to extract the radio nb file so that I can build a new NBH with the radio and the rom. I have also toyed with the idea to do the SPL into the NBH so that I don't have to worry if it has been flashed or not. I also will be flashing the roms from my microsd card (which I have been doing with my modified rom already).
Thank you in advance!
Putting an OS and a radio in a single NBH is perfectly acceptable. However, I don't think you can include Hard-SPL in there because it is flashed through SSPL, and it should really be the only thing flashed in that manner.
Trancecoder said:
Putting an OS and a radio in a single NBH is perfectly acceptable. However, I don't think you can include Hard-SPL in there because it is flashed through SSPL, and it should really be the only thing flashed in that manner.
Click to expand...
Click to collapse
Got it, thanks for the quick reply too!
I noticed your signature, and saw that you have the rilphoneauto. I see an EXT and OEM type file, but I am only familiar with cooking in cabs and making minor entries. I wouldn't know where to begin to add in an OEM or EXT to the roms that I modify/re-cook.
They're basically directories with a slightly varied structure that you put in an appropriate kitchen directory and then select inside the kitchen UI. If you're using the new "visual" kitchen, you should use the EXT package; otherwise the OEM. There are tutorials all over the forums explaining how to use them. I'm probably not the best person to do it anyway since I've only been cooking for a little while
I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
I'm not really sure what could be wrong, but if you need the dump set up for Visual, I had no problems dumping it and uploaded the untouched "Kitchen" to my FTP. Its labeled correctly as the build number 5.11.xxxx. I wish Icould help more, as you have helped me out a bunch.
EDIT: I did dump a ROM recently and got the same Version ID with xipporter as you have mentioned, but thought nothing of it. And I dont remember which it was, so sorry still not very helpful.
The ROM Version "garbage" is odd and IMHO should not be like that - your confirmation that you saw the same thing is very helpful ... at least I'm not losing my mind completely.
I'm trying to keep a PkgToolsBuildOS (5.3) and a Visual Kitchen (9.8) going for folks to use.
I had gone through all of the effort to port 21051 (SYS) and 20771 (OEM) in the hopes of posting it up before the end of the weekend ... then I started running into these unexplained issues and ended up scrubbing the lot.
I'm in the midst of recreating a new Visual Kitchen (9.8) and am discovering additional files in the OEM folder that weren't there before in older versions of the Visual Kitchen - not sure what it means yet; sure hope it doesn't mean having to recreate a kitchen everytime there's an update to the tools.
Cheers,
hilaireg said:
I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
Click to expand...
Click to collapse
Several of the new builds are this way. Its because the date info has been moved. Until someone figures out which part needs hex edited we are stuck with stock dat Version changes fine.
Are you saying that we should *no longer* be changing the ROM Version and ROM Date?
In my case the Date "looked" ok but the ROM Version was bogus.
Which leads to these questions:
Does this also mean that PagePool Unlock, NoCert Patching, PagePool sizing are also in jeopardy of moving? (I know you or others won't have an answer for this one as it's in the hands of the OEM).
Does this mean that PkgToolsBuildOS kitchens and supporting tools are now at end-of-life?
Hate that when I forget to read the memo
UPDATE
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
hilaireg said:
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
Click to expand...
Click to collapse
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
B4PJS said:
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
Click to expand...
Click to collapse
The PagePool seems ok on my 6.1 builds at the moment but Da_G could best confirm that as he's been on this "circuit" way longer than I.
An observation I made, while I've been working on this, is that the PP size on the AT&T 5.11.502.2 seems to be set 1MB ... at least that's what XIPPorterEX 1.2 rev32 reports when I issue a change to the PagePool to 16MB on a non-reduced ULDR os.nb.payload.
Hmmm, Wonder why when I change my PP to 0 I still only have 197mb Total instead of about 213mb total? Might have to do a test and set it higher to see if my free space decreases
UPDATE: Direct From Da_Grand Pubba ...
Just had a quick chat with Da_G and he confirms that there's been a change in the XIP modules.
At first glance, he noticed that the NK.EXE module has three (3) new resource strings. So in short, if the ROM Version happens to display [K] InitDr (which is [K] InitDriverGlobals) DO NOT attempt to change the Date/ROM Version.
He also had a quick look for Certificate Patching, PagePool Unlock, and PagePool resizing - these appear to be untouched at the moment.
HTH,