Related
Can anyone confirm or deny that either of the two programs work with the brand new rom?
They didn't with 3.27. There also is a newer version of Card Export out now.
Still not working for me on the official 3.35 ROM. I'd love to get this fixed. That was an essential feature for me and it sucks not having it.
Were you referring to Card Export II 3.08 or WM5torage?
both....
I was running Card Export 3.06, so when I saw your post I was hoping 3.08 would work. Installed it and still no love. This sucks.
Edit: I submitted a bug report at Softick's website. Here's hoping for a resolution
WM5torage 1.75 works with the new rom.
Not working for me. Did you do anything special? What ROM are you running? I'm on the official Sprint 3.35 release.
Also posted at PPCGeeks,
For those interested in Card Export/WM5torage:
I don't know about everyone else, but the ability to use my phone as a flash drive for transfering files is a huge advantage for me. Activesynce/WMDC blows, and is not installed on every computer. Since the update to 3.XX ROMs, neither of these programs has worked (at least for me). I've been in touch with Softick (makers of Card Export) and I think we will have a solution soon. I've run some debug programs for them and they have developed a working version. Not sure when the final release will be, but hopefully soon. I was amazed at how responsive their team was. The day after I emailed them, the developer was in contact with me. I ran some debug programs, and the next day he had a working test version for me to try. Really awesome to see them working that quickly to develop a fix. If I hear anything about the final release I'll post again. Just thought some people might want to know.
atomclock said:
WM5torage 1.75 works with the new rom.
Click to expand...
Click to collapse
is this inaccurate information??
i have both working on dcd 3.01 rom with the new 3.35 radio. I also discovered a way to unhide the extrom in dcd's kitchen and without the bug that happens when u follow this links suggestion : http://forum.xda-developers.com/show...ghlight=EXTRom
I have the phone recognize my extrom as a Mounted Volume or a harddrive for a lack of a better term. This means that since it is recognized as other than an extension of the primary, u could get files to treat it like a 2nd harddrive, maybe have a two OS's installed at 1 time. ( wm5 and then wm6 ) just boot into which 1 u want to use. or im working on trying to get the WM^ to treat it like a swap file for extra 10mb of memory. swap files r treated just like system memory by the Operating system.
any how u just have to make some reg changes and u are in business
bunvilla said:
i have both working on dcd 3.01 rom with the new 3.35 radio. I also discovered a way to unhide the extrom in dcd's kitchen and without the bug that happens when u follow this links suggestion : http://forum.xda-developers.com/show...ghlight=EXTRom
I have the phone recognize my extrom as a Mounted Volume or a harddrive for a lack of a better term. This means that since it is recognized as other than an extension of the primary, u could get files to treat it like a 2nd harddrive, maybe have a two OS's installed at 1 time. ( wm5 and then wm6 ) just boot into which 1 u want to use. or im working on trying to get the WM^ to treat it like a swap file for extra 10mb of memory. swap files r treated just like system memory by the Operating system.
any how u just have to make some reg changes and u are in business
Click to expand...
Click to collapse
would you care to further explain exactly how you got wm5torage and card export working on dcd's 3.01 rom with the new 3.35 radio? cause i jus tried both on the same rom and it's a no go for me, using the computer operating system windows XP. i have seen them work in linux.
well first i have the security and encryption off/ second, my version of both those progs are cracked, so they have been altered and third i thinks got something to do with the fact that i use QPST program which i have both 6700 and 6800 usb drivers on my phone. i use the 6700 usb drivers for that program and possibly thats what is making those programs work. U know because i havent had a problem with them i never thought about it./ but i couldnt but a 100 percent sure, but it would be my best guess. besides from my last post u can see that i have been messing with my extrom in which i use the 2 progs to help me with
how'd u get the 6700 usb drivers on your phone? u cooked it in using dcd's kitchen? where'd u get the 6700 drivers from? the apache kitchen??
card export II seemed to work w/ linux for me (did an "ls" to see the directory listing), However, when used with Server 2003 (my regular desktop that has activesync), it mounted itself, but when I went to see the drive, it was empty.
exactly the same for me. works in linux...and is visible but empty in windows. wonder how bunvilla got it to work. he's the only one so far that's been able to get them working.
says the drivers from the 6700 is on his 6800...sounds very likely to work that way but.....wonder how he got the drivers from the 6700??
Hopefully they will figure out something soon. This program is really helpful.
i want to make sure we are on the same page ok. When i use that program I only have access to my SD card. I cant access my phone folders. So when im at work and i want to save something to my sd card i turn on Card Export II 3.08 and then the little green light comes on and in a minute it shows up when i click "my computer" icon. But u know something ever since i changed the extrom to Mounted Volume ( no i didnt just rename the Extrom to Mounted Volume) it shows up too as a little 9mb removeable drive right below my Sd card.
so in the main directory there are 2 extra removable drives that shows up, and the only thing i can think of is my SDcard is formatted fat32.
Oh and by the way i didnt extract the 6700 usb drivers from a 6700 phone, i got them from a website and i rename my usb drvs for the 6800 and use the 6700 usb drvs and then switch when im done.
someone told me that i was doing it the hard way but it works for me. hope this helps some,
there are those times when stuff jus doesnt work for everyone else. sound like a lucky dude and congrats...cause NO ONE else can get it to work. not even the company who created the program. they're supposed to be working on a fix now.
well u know something else that i have that nobody else seems to have is the extrom , on my version of DCD' 3.01 everyone else seem to have issues with that too. at best they get extrom and extrom2 showing up when they use No2chem unlock extrom in the root directory of thier phone. I include a thumb shot of my root and u will see that i not only fixed that issue i also have the extrom show up as a removable drive and it changed from extrom to Mounted Volume and i didnt rename it that, it happened because of the reg edits i made and flashdrv.dll i used. im surprised that doesnt get your curiosity. I can both read and write to it, might even be able to add it to the pagepool. im working it right so i will let u know if i succeed .
WM5torage 1.8 hacked version working
Hey all. Found this on one of the kaiser forums.
I can verify that I have successfully used this cab on my sprint mogul with OLD stock rom 2.17
The steps required are as follows:
1.Install hacked cab below
http://forum.xda-developers.com/attachment.php?attachmentid=69221&d=1202300677
2.Soft Reset
3.Click yes to install card export and then OK to error messages
4.Open WM5torage and disable rndis
Note:According to thread, this will not work if you have ever installed card export on your system. Not sure why
Note 2: I am using 512microsd card with stock rom. I am about to reflash (for a change) and will repost later with my custom rom based on new 3.35
-Josh
bunvilla said:
well u know something else that i have that nobody else seems to have is the extrom , on my version of DCD' 3.01 everyone else seem to have issues with that too. at best they get extrom and extrom2 showing up when they use No2chem unlock extrom in the root directory of thier phone. I include a thumb shot of my root and u will see that i not only fixed that issue i also have the extrom show up as a removable drive and it changed from extrom to Mounted Volume and i didnt rename it that, it happened because of the reg edits i made and flashdrv.dll i used. im surprised that doesnt get your curiosity. I can both read and write to it, might even be able to add it to the pagepool. im working it right so i will let u know if i succeed .
Click to expand...
Click to collapse
it gets my curisoty as well. one thing i have to say is it appears your level of geekiness is definitely a step above mines. u're a smart guy man. would be nice if you could maybe dump that rom of yours for us and maybe create a bunvilla's rom based off dcd's 3.01 with wm5torage and a mountable extrom working. im almost certain it would get a substantial amount of users.
Hey all. the new stock rom is running perfectly for me. I am however missing most of the customizations I have become used to in my DCD 2.3.2 cooked rom. I have decided at this point that I want to just add my stuff into device memory and run that for a while until all the kinks are worked out. I don't know if this has been covered before but I ran the nueextrom utility on the stock 3.35 rom and it worked!! to unlock the ext rom.
So, what do we need to keep in there and what can I delete. I will edit the config to not run the following from windows directory
1.Audible AIr
2.On Demand
3.Grove Mobile
4.Sprint TSK theme
So, with that in mind I need to know what the following are for please:
1.hidden.cab
2.rilphone2.cab (possibly something with tethering?)
3.chgscutattri.exe
Thanks to my fellow xda-ers...I know I only have two posts but have been on here religiously for 3 years.
Thanks,
Josh
no replies? boo
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.
M-ROM v1.1
ROM Language: Dutch
Based on shipped NLD rom 1.90.404.1
But ROM updated to build 20755.1.4.0 (XIP/SYS ported)
and this has been done...
Updated:
- Net CF v3.5
- GoogleMaps (NLD) v2.2.0.19
Added:
- UC
- Alternate sliding sounds (transformers, star trek, etc)
- Advanced Config v3.3
- TF3D config v6.7
- TomTom Navigator v7.451.903
- Klaxon 2.0.19
- Lightsaber v1.0
- MS Voice command v1.6.19209
- WMRegOptimizer
Removed:
- removed introduction video
- removed customers feedback
- removed autoupdate
- removed Cyberon speeddial
- removed sample music / wallpapers
- removed MP3 Cutter
Tweaks:
- Disabled SMS-threading
- Disabled Security warnings when installing non-certified applications
- Many speed improving tweaks...
!! UPLOADED NEW VERSION (23/10/2008) !!
Working on M-Rom v1.2 (build 20924.1.5.0) Be patient....
Download DOWN! ! updated !
RAR-password: XDA-Forever
notes:
- I'm still deployed in Afrika without my TP so no chance for testing the rom myself!
- This ROM is UNprotected and maybe tweaked by everybody to fit their own needs! background discussion found here
Looks like I've wasted my entire Saturday morning by doing the exact same thing!
Well done though merten3000 - much appreciated!
Great
Good work.... many thanks for the contribution mate...
Anyone feel like adding this to the wiki?
mrvanx said:
Anyone feel like adding this to the wiki?
Click to expand...
Click to collapse
Wait for some reactions first...like I noted I could not test the ROM myself...unfortunatly
Maybe it is full of errors or does not even boot...still a cook no chef...
Excellent. I'm gonna try it tomorrow just to see if I can teach it to speak Czech.. big tu.
And? How the ROM? Anybody tested him?
mattcrow said:
And? How the ROM? Anybody tested him?
Click to expand...
Click to collapse
My thoughts exactly...
i will givde it a try 2morrow. i'll post back here.
I just flashed your ROM but I cant get over the first screen - The one that says the versions in the bottom. Have been waiting to get the phone booted for over 5 mins already.
Back to my Pdaviet ROM I think.
Edit: Yep, flashing previous ROM (Pdaviet) from card.
crocodile010 said:
I just flashed your ROM but I cant get over the first screen - The one that says the versions in the bottom. Have been waiting to get the phone booted for over 5 mins already.
Back to my Pdaviet ROM I think.
Edit: Yep, flashing previous ROM (Pdaviet) from card.
Click to expand...
Click to collapse
So the flashing went well, but after that the reboot did not work? Damn!
It's sh*tty that I can't flash myself to test.
Maybe another cook can take a look as it is unprotected...
tbh it sounds like a symptom of not porting the XIP across correctly, i'll take a look and see if theres some overlap errors.
EDIT:: I see no overlaps in the maps list however i cant be sure the XIP is a functional one. Im wondering did you port the XIP across using the normal technique or was it just a straight copy and paste from the doner device?
mrvanx said:
tbh it sounds like a symptom of not porting the XIP across correctly, i'll take a look and see if theres some overlap errors.
EDIT:: I see no overlaps in the maps list however i cant be sure the XIP is a functional one. Im wondering did you port the XIP across using the normal technique or was it just a straight copy and paste from the doner device?
Click to expand...
Click to collapse
I extracted xip.bin from a functional Raphael 20755 build and merged it in the payload using write2 option in xiptools. Because it was a working Raph rom I thought I did not need to change the device-specific OEMkernel? Maybe I thought wrong?
p.s. When I was looking for the problem myself yesterday I noticed that in boot.rgu (in ROM folder) the the MUI values keep changing back to 409 instead of 413. I changed them many times, but when I build the rom and dump it again, it is changed back to 409??? I already went through the hives and boot.ms.rgu but can not find those entries there...
The only thing you need to do is to put the .nb (which you want to use the XIP from) into the ROM folder, the build process will take the nb and replace only the OEM and SYS components in it, so aslong as you port the SYS across correctly then the XIP will be in the nb correctly.
Just to make sure though did you write the xip into the os.nb.payload?? (you cant write it into os.nb, it must be the payload section of it, also make sure the address is 03200000 instead of 03100000).
mrvanx said:
The only thing you need to do is to put the .nb (which you want to use the XIP from) into the ROM folder, the build process will take the nb and replace only the OEM and SYS components in it, so aslong as you port the SYS across correctly then the XIP will be in the nb correctly.
Just to make sure though did you write the xip into the os.nb.payload?? (you cant write it into os.nb, it must be the payload section of it, also make sure the address is 03200000 instead of 03100000).
Click to expand...
Click to collapse
Thnx again, I will look into it and repost if I succeed..
I did use the payload, but will check the adress to be sure!
! UPDATED FIRST POST !
Downloading and ready to flash
(if RapidS**t will speed up)
edit: The way Rapidshare has been behaving, could you give a md5 / crc check?
I like to be sure to have the right file, without faults.
(I'll test it anyway, got ROMeOs1.13WWE ready, after being happy with 1.12WWE)
edit 1: Flashed perfect, but again no boot, hangs again at the first screen
There is something wrong at boot time, flashing to ROMeOS 1.13 now.
(Just ask me, will try again, I can give you some space to upload to )
edit 2: up and running again
karloe said:
Downloading and ready to flash
(if RapidS**t will speed up)
edit: The way Rapidshare has been behaving, could you give a md5 / crc check?
I like to be sure to have the right file, without faults.
(I'll test it anyway, got ROMeOs1.13WWE ready, after being happy with 1.12WWE)
edit 1: Flashed perfect, but again no boot, hangs again at the first screen
There is something wrong at boot time, flashing to ROMeOS 1.13 now.
(Just ask me, will try again, I can give you some space to upload to )
edit 2: up and running again
Click to expand...
Click to collapse
Thnx for testing man...but WTF is wrong woth this rom??
Need some expert help I think:
- 1) I used a 20755 XIP whitch I manually changed to raphael (Kept original raphael Oemkernel). Used xipport to dump the XIP.bin files, made packages etc. But when recompiling the xip_out.bin each time I got errors that .txt files where missing for some of the package maps. But I did not touch those files. Anyway no luck with recompiling a working xip.bin
- 2) Almost same as above but did not make packages. In dump folder replaced all the right files (kernel + kerneltk) and again kept original OEMkernel files. Then I was able to recompile a XIP.bin but xipport created a file witch was 4/5 the size compared with the original one...that's no good I think also. So no luck this way
- 3) Extracted a xip.bin from a WORKING raphael 20755 rom using the raph kitchen. Merged it into the payload file using xiptools (but could not input adress there 003200000....?) That was the first version I uploaded.
- 4) Yesterday I used the extracted xip.bin again. But this time I merged it directly into the os.nb file to the right adress (003200000 instead of 003100000) using XIPPORT. That is the version I uploaded yesterday
Can somebody tell me what I'm doing wrong?? I'm getting quite desperate right now...
Any help is appreciated!
karloe said:
Downloading and ready to flash
(if RapidS**t will speed up)
edit: The way Rapidshare has been behaving, could you give a md5 / crc check?
I like to be sure to have the right file, without faults.
(I'll test it anyway, got ROMeOs1.13WWE ready, after being happy with 1.12WWE)
edit 1: Flashed perfect, but again no boot, hangs again at the first screen
There is something wrong at boot time, flashing to ROMeOS 1.13 now.
(Just ask me, will try again, I can give you some space to upload to )
edit 2: up and running again
Click to expand...
Click to collapse
Again after some tips (thnx MrVanx) I spent a whole night working at the ROM.
I revised the XIP and SYS totally and I think it maybe will work this time (it would be about time!)
Will upload tonight as I will not be around during the day
Karloe: I wil use rapidshare again, but pm about your privat upload space, thnx
What do you mean with unprotected rom btw
Like rome os with tweaks,other software and stuff,or something special?
Thx in advanced,greetings martijn from the netherlands also
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,