Home » Articles

Treo 700wx starts to get "custom ROM" treatment!


rom%20ktichen.jpg

Well 2 years into its release and customs ROMs are finally getting the work through for the aging 700wx. Better late than never, eh?

Thanks to Waffles (ppcgeeks), LLC23 (wmexperts) and Ebag333 (wmexperts), we now have a dedicated thread located here to discuss the project and most importantly, the inherit risks of re-flashing your device with a non-standard ROM.

Custom ROMs are nice as they allow users to not only replace unwanted stock carrier apps with their preferred ones, but it also enables the ability for pre-tweaking of the registry.

Plus there is that holy-grail for WM users: flashing with newer versions of Windows Mobile. This means the potential to put WM 6.x on the 700w/wx is only a matter of time, perseverance and assistance form ambitious WM users--so maybe you should pop in and lend a hand to make some history, hmmm?

So far the project is confirmed working on Sprint devices but Verizon and Alltel still need some experimenting. Ebag333 has even created a 700wx ROM-kitchen for easy implementation making the future of this project very promising for those who are not too comfortable with the whole process.

Keep up the great work guys! This will keep us busy till the 800w release ;-)


Comments (87)

700w/wx Custom Roms

History

This was kicked off by Waffles over at PPCGeeks (http://forum.ppcgeeks.com/showthread.php?t=24255).

It was crossposted by LLC23 (http://discussion.treocentral.com/showthread.php?t=163847).



What you need to know

First off, flashing your rom is dangerous. Not blow-up-the-world type dangerous, but you're-out-500-bucks dangerous.

If you brick your phone (render it useless), it's your own fault. At this point the ROM is still what I would consider 'unsafe', in other words it's not at the point where you can follow steps 1 through 10 and achieve success.

Additionally, flashing your phone is completely unsupported by either Palm or your wireless carrier, and may void warrantees, insurance, etc, etc, etc.

I've only tested this with Sprint. Verizon and any other carriers may or may not work, try it at your own risk.



How to flash your phone back to standard settings

The basic method of flashing is essentially the same for any rom (at least with the Sprint update). This is the method of flashing your phone to standard/default settings, allowing you to (hopefully) get back to a standard rom should something go wrong. This is not 100% guaranteed, and may or may not work depending on how badly the flash went wrong.

[LIST=1]
[*]Download the (Sprint) SD card ROM update. (http://www.palm.com/us/support/downloads/treo700wxupdater/sprint_installsd.html as of this posting the update is at 1.15.)
[*]Format your SD card in FAT32 format (any other format will most likely not work). You will need at least a 128 meg SD card, I recommend larger so you can place a few useful programs on it (such as psShutXP) on it.
[*]Extract the SD card ROM update to your SD card. You should see 4 files in the root directory, and a folder named 2577.
[*]Have your power cable handy for your phone.
[*]Hard reset your phone. (The flash is designed to "upgrade" your phone rather than overwriting everything. Nice when everything is working the way you like it, not so nice if it's not. If you don't hard reset your phone you may not see all of the new options. For example, I didn't see the new Wait Cursor until I had performed this step in this order, a straight hard reset or straight flash did not actually seem to clear everything.)
[*]When the Treo splash screen comes up, but before it starts loading: Pull the battery on your phone. (Note: your battery should be nearly or fully charged.)
[*]Place the SD card into your phone.
[*]Hold the volumn up button on your phone.
[*]While holding the volume up button, replace the battery in your phone.
[*]You will see a screen that tells you to press up on your 5-way if you want to flash, or any other key to cancel. If you don't see this, go back to step 6.
[*]Before you press up, plug your power cable into your phone. The red light will not go on as normal, this is expected, but assuming your power cable is plugged in at both ends and working properly, the phone is still on AC power.
[*]Press the up arrow on your phone.
[*]Very carefully (without disturbing anything) place the phone in a safe location. You do not want to move it and risk disrupting the power or accidentally ejecting the SD card. This is a good way to brick your phone.
[*]Wait patiently for the "Download OS + BL" screen to finish.
[*]Once the bar is full, your phone will reset.
[*]If you get stuck on the Treo spash screen, you're bricked your phone. You may be able to recover by going back to step 1.
[*]If you get stuck on the Windows Mobile splash screen...be patient! The first time your phone boots it will take a minute or more to load. If it hasn't loaded after several minutes, go back to step one. You've bricked your phone, but most likely can recover as it's Windows that is not loading, and not the boot loader.
[*]If everything is successful you should be asked to setup your phone again (including calibrating the screen). Congratulations!
[*]You can play around with it at this point, but you will need to soft reset it for everything to take effect (especially recommended if using a custom ROM).
[/LIST]

Note: After you are done flashing--and your phone has reset--you may want to pop out the SD card. This seems to help decrease the amount of time your phone will take to boot the first time (This would be after step 14). Do not remove the SD card before your phone finishes flashing!



How to flash your phone with a custom rom

You will follow the directions pretty much above. The only difference is you will replace the default NapaBoth.nb0 file with your own custom one. This would occur between steps 3 and 4.

Does this work for Verizon WX's?

yes, just be sure to delete firmware.bin before flashing; otherwise you will flash a sprint radio onto your verizon phone, which may cause big problems with the functionality of your phone.




Confirm working on Telus/Bell Treo 700wx

How do I create a custom rom?

You can now use Ebag's Palm Treo 700w Kitchen!

Simply extract the archive to the directory of your choice, place your NapaBoth.nb0 (ROM file) under the \Cooking\ directory, and then pretty much follow each step in order.

Documentation is limited at the moment, and this Kitchen comes with absolutely no guarantees, warantees, or support (though I suppose if you ask a question here I might try and answer :p ).

The Kitchen is subject to being broken/upgraded/broken/changed/removed/broken at any point and without notice (did I mention broken?).

(Linkie at the bottom of this post.)



Where can I find custom rom's?

Ebag's trimmed standard rom

Rom File
File List



Ebag's custom rom - Take 1

Download

Removed:
MSN Instant Messanger
Picsel File/PDF Viewer
Pocket MSN
Software Store
OD
Various help files (pretty much all the ones I could get my hands on)
Various wav/wma files (several you couldn't even use)

Added/Replaced:
MortScript (and cDate script, changes your carrier name into a date line)
PIEPlus 2.2 (Unregistered)
PocketXpdf (replaces Picsel PDF viewer)
psShutXP
regedit (freebie version)
Sprite Backup
Ubuntu style wait cursor
Various popular registry tweaks found on the board
Start Menu\Programs has been cleaned up and streamlined (many programs are in subdirectories)
Radio On/Off sounds are replaced (reduces size from approx 256kb to approx 13kb)
Misc other things I forgot

*

DISCLAIMERS

1) No responsibility can be taken by anyone other than you if your phone is "bricked" (rendered unusable), damaged, or in any other way, shape, or form modified.
2) All files are property of their respective owners.
3a) Yes
3b) No
4) Flashing your phone is dangerous and should be undertaken with great care. Please be sure to follow all appropriate steps as directed.
5) This process is not guaranteed in any way.




(Semi)Useful Questions/Answers/Posts/Suggestions/Etc

Okay I am trying to cook a ROM, but can't figure out how to get a .nb0 file. Can I get some help with that? Thanks.

If you read post 1 (to get the default Sprint ROM) or post 2 (to get one of my custom ones) you'll see where to get them from.




Confirm working on Telus/Bell Treo 700wx




Does this work for Verizon WX's?

yes, just be sure to delete firmware.bin before flashing; otherwise you will flash a sprint radio onto your verizon phone, which may cause big problems with the functionality of your phone.





I've managed to add the test certificate to the HKLM branch, without modifying the default.hv file.

More: http://discussion.treocentral.com/showpost.php?p=1439465&postcount=31



Here's the initflashfiles.dat that goes with the Treo. It's not in the ROM, so standard disclaimers apply. That being said, it works for me.

More: http://discussion.treocentral.com/showpost.php?p=1440505&postcount=41



One thing, the PIE+ expires in 2 weeks, and costs $15. Is there a way to just downgrade back to PIE?

Actually it's always expired for me after the first soft reset. :o

Anyway, once it expires it goes back to the normal PIE, but it still adds a couple of features (in the normal menu) that are useful. I really would recommend dropping the $15, and purchasing it. It's a top notch program that seriously improves your browsing experience, even if you don't use the tabs.

Does this work for Verizon WX's?

Does this work for Verizon WX's?


Good question. This was originally posted by Waffles.
http://pdaphonehome.com/forums/treo-700w-700wx/108832-how-you-make-custom-rom-700wx.html


if you are not using a sprint phone, you will probably want to delete the firmware.bin file (this is the radio).


(In other words, I don't know. I don't have a Verizon phone, nor do I intend to get one. :D )

I wonder if we can recover 700p/755p with this method?

I wonder if we can recover 700p/755p with this method?


My 600p doesn't use quite the same method. You can try it with a 700/755p, and see if it says "checking for SD card" or something similar. The other thing to try is similar, but hold up on the volume and the side button, for my 600p that puts me into the boot loader (now what you do from there, I have *NO* idea).

The other odd thing on the 700wx (and I'm assuming the w) is holding down the side button while replacing the battery. Mine reads:

[COLOR="Blue">4.13[/COLOR]
[COLOR="DarkRed">4.13.00[/COLOR]


I'm assuming that's the bootloader version. It doesn't appear I can do anything from this screen (hitting buttons seems to do nothing).

Does this work for Verizon WX's?



yes, just be sure to delete firmware.bin before flashing; otherwise you will flash a sprint radio onto your verizon phone, which may cause big problems with the functionality of your phone.

Third post updated with the first custom rom.

Enjoy. :D

Does this work for Verizon WX's?


(In other words, I don't know. I don't have a Verizon phone, nor do I intend to get one. :D )


OK - I understand that and appreciate the honesty :) The big question I'd have is - if we flash on a vzw wx, can it be flashed back to stock from the vzw updater?

I did a LOT of rom building with my 6700 and have no problem with this and would love to. My main goal, as I mentioned, is html emal (ala wm6 poutlook preferably - flexmail is too erratic). But I'd love to have stuff built in. I had a rom setup on my 6700 that had everything but a few files which were installed in 4 installers (one of which I created ;) Hard-reset to full funcitonal was 10 min... Was a lot of fun. But the ability to go back to stock is really important for many reasons. I'd love to remove the soft-key programs palm built in, but I really love the dialer from the today screen for instance...

The big question I'd have is - if we flash on a vzw wx, can it be flashed back to stock from the vzw updater?


I don't see why not assuming Waffles is correct about removing the firmware.bin preventing flashing the radio.

Then again...even if you flashed the radio I wouldn't think it would be bricked, just you wouldn't be able to use it until you reflashed back to the Verizon radio.

But again, I don't have a Verizon phone so there's no way for me to test it. If you feel lucky (or at least have insurance :D ) go ahead and test it out. Personally, I believe that as long as you don't trash the boot loader then you won't have any problems reflashing back to a standard rom. But then again I'm not entirely sure if you can safely flash from Verizon to Sprint (or vice-versa) and what exactly attempting to do so would do to the phone.

Sorry I can't be of more help, but I just don't have the means to test it to where I would feel comfortable saying one way or the other.

It's really tempting :cool: My family would tease me when I had the 6700 - "what, you didn't rebuild the phone today?" "Not even a hard-reset?" :D

Coming from the 6700, there's really not that much bloat in the wx. I start with 42/43M ram when I soft-reset, and it goes down to about 32/33 after a week or more. With the 6700 - try 21M after s-r and maybe 12-14 after a day of moderate use!

I never keep anything running (quick menu makes the ok button close the app - it's amazing ;) so memory is fine. The only things that would make this perfect is getting rid of the softkey program palm puts in (been trying to find that in the registry with no luck. Found a lot of other things, like having it not make souds/vibrate when you insert/remove the sd card, etc...) and html email - oh, and the three shortcuts it puts in the start menu on a restart are annoying (found them in the windows folder, but they are system files so can't be moved) but not a major annoyance. More room could be nice by putting some stuff in the rom, but I run everything off the phone, no sd card (just having it in drops you 1M in ram btw...)and still have 15M free :)

Still - just being able to rebuild and create new roms is a pretty fun thing :D

:p

oh, and the three shortcuts it puts in the start menu on a restart are annoying (found them in the windows folder, but they are system files so can't be moved) but not a major annoyance.


The above ROM removes those, along with a bunch of help files (who need's em! :p ). The theory that I've seen is the less files you have in your /Windows/ dir, the faster the PPC runs (due to it not having to loop through all the files every time something happens that references the /Windows/ dir).

Die annoying shortcuts! I dance on your grave!

Oh, and this might be a good time to mention I've successfully added files to the rom. I haven't managed to replace a module yet, but hopefully that's forthcoming....

Couple of important bits of news.

First off, you can now download my fancy kitchen from the 2nd post above. As always, no guarantees come with it. It's mostly just the tools that I used to build my customized roms, along with some batch/autohotkey scripts to make it more automated and less painful. Feedback is appreciated.

Secondly, I managed to extract the HKLM and HKCU registry branches. So far I have only been able to successfully flash and boot with a custom HKCU branch, the HKLM one booted into WM, but it was very much not functioning properly. I've included these files into my kitchen, along with a couple of batch scripts to make it easier to convert them back and forth (note: as of this posting, the two batch scripts expect to be in the root directory, so you'll need to move them out of the \Tools\ directory if you want to use them).

I also haven't compiled the Autohotkey scripts I use. To do so would increase the zip size past what can be added to a post (490 kb), so I'm not going to do that at this point. That means to use my handy-dandy file delete script, you need to download Autohotkey.

Speaking of deleting, the script won't try and delete modules. There are two ways to handle this.

1) Place a 'dummy' file in the \ToDelete\ folder (Example, pword.exe to delete the PocketWord module). I would suggest a text file with the same name as the module you want to delete. This will basically "trick" the script into adding that file to the delete script, which actually will delete files or modules without caring which is which (when passing paramaters). It's a limitation of my script that won't delete modules, not the program, so blame me (and no, I likely won't fix it :p ).

2) Delete the modules manually, either through manual calls to delfile (or your own script), or by dumping the files, editing, and recompiling them. For this purpose I've included in an easy way to recompile them as well as finalizing the ROM.

There isn't a lot of error checking in the scripts at the moment, so stuff is still easy to break. If you do...sucks to be you. :eek:

Oh, and maybe we could get a sticky on this? :D

1. Sticky. Yes... please!

2. GREAT progress! I am following along anxiously. I am not quite ready to dive in. Soon, maybe. I am looking for HTML e-mail to be ported over :).

Great work EbaG333. There are a lot of us 700wx users watching closely to see where this goes. I like what is done already.

Great work Ebay333.
:eek:

:eek:


Hey.....it coulda been worse!!!!!:D

combined with the WMExperts front page post.

Nice stuff!


Well 2 years into its release and customs ROMs are finally getting the work through for the aging 700wx. Better late than never, eh?


In all fairness most of that time was waiting for Sprint to release the 1.15 update (released August of last year). So it's really only been 9 months. (Yeah, it's still far too long. :( )

Updated the kitchen in the 2nd post. Really bumping into the filesize limit, only 9 kb away now, hehe.

Quite a few minor bug fixes and changes. AddFile is supported via batch script now (similar method to DelFile, simply drop the files you want to add in .\Cooking\ToAdd\ and run the batch script).

I've also included in the tools a certificate signing program. You can use this to sign your applications/dll's so that they'll be trusted and won't get those annoying popups asking if you want to run them.

The problem is that the reg key to register that certificate is in HKLM. I haven't been able to successfully flash a ROM with a custom (or even extracted) HKLM, WM doesn't load properly at all. I can do the HKCU, which will be nice for a handful of mods, but we either need a way to flash with a custom HKLM, or figure out a way to trigger an autoinstaller after flash that'd install the special reg keys....

This is where I know the XDA community is awesome... I was following you until the HKLM issues. I flashed my phone twice with your kitchen... when it boils down to reg keys and that language in hex, I am a retard.

This is where I know the XDA community is awesome... I was following you until the HKLM issues. I flashed my phone twice with your kitchen... when it boils down to reg keys and that language in hex, I am a retard.


Just curious, but did you make any changes, or was it pretty much a stock flash? I'd be curious to know what you changed (and what you thought of the kitchen). Also, are you on Sprint or Verizon?



Can someone with a Verizon phone dump their HKLM/HKCU from the registry, and either post it here or send it to me? I'd like to do some diffs and make sure that there's nothing unexpected in one vs the other.

Just curious, but did you make any changes, or was it pretty much a stock flash? I'd be curious to know what you changed (and what you thought of the kitchen). Also, are you on Sprint or Verizon?



Can someone with a Verizon phone dump their HKLM/HKCU from the registry, and either post it here or send it to me? I'd like to do some diffs and make sure that there's nothing unexpected in one vs the other.


The Kitchen is VERY simple. Reminds me of the apache kitchen I've used in the past. Def not for the weak of heart but anyone who knows how to manipulate windows files won't have a problem. I did a stock flash just to see if it worked but I didn't dare make any changes due to your warnings as of the last post... Sprint User here. do you think I should do a change? I mean, I didn't get the thing to brick... but I didn't think that was the point. I had a ton of free space, so thats always nice, seemed zippy too. I'd love to put some of my programs in there and have them auto register instead of having to manually put in my serial numbers.

I had a ton of free space, so thats always nice, seemed zippy too. I'd love to put some of my programs in there and have them auto register instead of having to manually put in my serial numbers.


I like the idea of the free space = snappy device, but adding programs is the confusing part. What type of programs do you add? I would think it would be difficult to upgrade, or personalize apps in the ROM (I could be wrong though). I am one of those 'weak at hearts' you mentioned, but if I can find a real cheap WX on ebay, I am definetly giving this a shot!!!!


The Kitchen is VERY simple. Reminds me of the apache kitchen I've used in the past. Def not for the weak of heart but anyone who knows how to manipulate windows files won't have a problem.


Well at this point it's intended to be pretty simple. :)

And if you think you need to know how to manipulate files/folders with this, you should try doing it all by hand. :p



I did a stock flash just to see if it worked but I didn't dare make any changes due to your warnings as of the last post... Sprint User here. do you think I should do a change? I mean, I didn't get the thing to brick... but I didn't think that was the point. I had a ton of free space, so thats always nice, seemed zippy too. I'd love to put some of my programs in there and have them auto register instead of having to manually put in my serial numbers.


To be honest, as long as you follow my steps you probably won't brick your phone. I've been flashing my phone several times a day, every day, and have had no problems that couldn't be fixed by reflashing.

The problems I mentioned in the last few posts were due to me (trying to) use a custom HKLM registry branch (default.hv in the ROM). But all that caused was WM to load funky (and not load completely), a reflash fixed it pretty handily.

In order to have your programs register, you'd need to extract the registry keys they create when registered, and drop them into the registry dump (if they're HKCU keys. If they're HKLM, at the moment you're out of luck).

Auto-registering would be nice, but to me that's not the key point of it. The key point is really two-fold. One, to free up space and hopefully make the device a bit more zippy (which from my completely unscientific test, it does speed it up a bit). The other would be to having programs that you want installed by default on your PPC, so you don't have to reinstall them. Additionally, if a program tends to run slower on your SD Card (but you don't want to take up the room on your PPC), you can drop it into the ROM as a way of essentially extending your storage space.

Anyway, start with the trimmed ROM I posted above, and go from there. :)

Anymore I don't even dump the ROM and rebuild the dump. Takes too long, and once I know what I want to remove/add it's faster to have it in the \ToAdd\ and \ToRemove\ directories, and add/remove them directly. But for learning, dumping it makes it a lot simpler.


I like the idea of the free space = snappy device


Free space does not directly make your device more snappy. What it does do is trim down the \windows\ directory, which means when that dir is parsed by any applications trying to use it, it doesn't take as long. The trimmed ROM I posted above removes approx 4 megs over 330 files. That's a lot of files for a dinky little 312 mhz processor to go through! I can definatly see how having all those files in a core directory would contribute towards slowdowns.



, but adding programs is the confusing part. What type of programs do you add? I would think it would be difficult to upgrade, or personalize apps in the ROM (I could be wrong though).


The ones you'd put in the ROM are the ones you aren't going to upgrade (or at least not upgrade often).

Like, say, the Java runtime. For me I'd probably put the Microsoft Reader there, I use it a lot and the app hasn't been updated in years (and it's a pretty big application, a perfect example of an app to drop in ROM). Other OEM type applications (such at the HTC streaming video player) would also be a good idea.

For upgrading, you could choose one of two paths. One would be to reflash with a new ROM (not so horrible if you do it once or twice a year). The other would be to simply install the updated version over the ROM version.


I am one of those 'weak at hearts' you mentioned, but if I can find a real cheap WX on ebay, I am definetly giving this a shot!!!!


Come on, all the cool kids are doing it! :stick:

Be careful where you host your files, palm might come after you like they did with shadowmite

very interesting stuff...what would be needed to use this process to upgrade the 700wx to WM6?

Be careful where you host your files, palm might come after you like they did with shadowmite


Good point. So far I don't *THINK* I've released anything that they could come after me for, but if they decide to I can always take down the offending material and teach you all how to do this (which is what the kitchen is there for :D ).

You know, "light a man a fire, keep him warm for a night--light a man on fire, keep him warm for the rest of his life" type stuff.

Err, or something like that. :eek:


very interesting stuff...what would be needed to use this process to upgrade the 700wx to WM6?


Not sure it's entirely possible, nor would I personally want it.

The 700wx doesn't have near enough memory for it to run smoothly. The Mogul (which is a faster CPU, same amount of memory) runs like a dog with WM6.

Success!

I've managed to add the test certificate to the HKLM branch, without modifying the default.hv file.

It's actually really simple, and the way that the carriers do it. Simply modify the *.provxml file of your choice, and away you go. I chose the mxip_wpc_4.provxml to use.

As an example, to add the test cert (the one that's now included in my kitchen, so you can "certify" any program you want now), add this code to one of the povxml files.


















Incidentally, the Messaging files included here on the board utilize the test cert. So if you add this cert to the provxml file, you should be able to add the files to the ROM. I'm flashing my phone as I type to test this theory.

Interestingly enough, there's a comment in one of the provxml files (2) that reads:





I was sorely tempted to include the test cert in that section. :D

Is there any way to disable certs stuff completely?

Is there any way to disable certs stuff completely?


For installing, yes. For running apps, I don't believe so. And I've looked far and wide for a method to do so....

For installing, yes. For running apps, I don't believe so. And I've looked far and wide for a method to do so....


ok.

it would be nice if you can find someone who has upgraded an older wm5 unit into wm6 via unoffical methods. then you can shadow his method. if not then it will be big news if someone is able to do it

If wm5 is not that much different than wm6, it might be doable, (ie: like win95 to win98 to winME.... but if its like making win98 into win2000.. that would not be possible)

ok.

it would be nice if you can find someone who has upgraded an older wm5 unit into wm6 via unoffical methods. then you can shadow his method. if not then it will be big news if someone is able to do it

If wm5 is not that much different than wm6, it might be doable, (ie: like win95 to win98 to winME.... but if its like making win98 into win2000.. that would not be possible)


Once again, my interest isn't in upgrading to WM6. :)

The 700wx, as much as I love it, simply doesn't have the resources for running WM6. It'd be like using a 700w, ugh. (Sorry all you poor 700w users. :eek: )

If someone can figure out a way, more power to them. Don't forget though that there are quite a few Mogul users (which has same memory, faster processor) that have downgraded to WM5 because WM6 runs horrible on it. Having used one, I can't blame 'em.

At this point I can easily add proggies and even register them if need be to my ROM, so I've achieved really what I was looking for when I started. Anything else from here on out is gravy. :)

...At this point I can easily add proggies and even register them if need be to my ROM, so I've achieved really what I was looking for when I started. Anything else from here on out is gravy. :)



The gravy I am looking for is WM6's PocketOutlook. :)

Once again, my interest isn't in upgrading to WM6. :)

The 700wx, as much as I love it, simply doesn't have the resources for running WM6. It'd be like using a 700w, ugh. (Sorry all you poor 700w users. :eek: )

If someone can figure out a way, more power to them. Don't forget though that there are quite a few Mogul users (which has same memory, faster processor) that have downgraded to WM5 because WM6 runs horrible on it. Having used one, I can't blame 'em.

At this point I can easily add proggies and even register them if need be to my ROM, so I've achieved really what I was looking for when I started. Anything else from here on out is gravy. :)


ok, I think th task would be to integrate "some" functions from wm6 to wm5

what about install some AKU upgrade so we would have the latest 3.5? aku?
I also can't get "REVERSE" dun working with my unit..
Besides stripping the rom only, is there any working full roms.?

ok, I think th task would be to integrate "some" functions from wm6 to wm5


That I would love to do. I need a file dump of a 750 though to get it to work really, something I haven't been able to find yet. (I've managed to get the ROM, but can't get them to dump with the different tools I've tried.)


what about install some AKU upgrade so we would have the latest 3.5? aku?


The trick there once again is finding the files (and matching registry keys). It's a pain, really (ESPECIALLY the reg keys) to try and get it from someone's kitchen, since all the files are jumbled together.



I also can't get "REVERSE" dun working with my unit..


Reverse DUN? As in your phone using your PC's connection to get to the web from your phone? Not sure I see the point of that.


Besides stripping the rom only, is there any working full roms.?


I have one, though it's not really...working. I mean it works, just fine, but I've tried integrating the 750's threaded SMS, and it doesn't really function the way it does when it's installed seperately. It appears to me that when installed seperately all you're really doing is using the 750's tmail.exe, basically overlaying the threaded functionality over the existing one (so it's still the 700's actually messaging, just you see it in threaded form if that makes any sense).

With it in the ROM, that functionality is gone, so it doesn't work right. It's also extremely laggy and slow, not sure why, it's not a system resource issue. I suspect it's either the 705's messaging stuff screwing up (IE: looking for a file it's missing over and over again) or some of the registry stuff is goofing it up.

Like I said....really need a full dump of the 750's ROM (or even just the \Windows\ directory....and the registry would be nice...). If I had that I could start porting stuff back. Unfortunatly there's no kitchens out there for the 750, just complete ROM's.

Like I said....really need a full dump of the 750's ROM (or even just the \Windows\ directory....and the registry would be nice...). If I had that I could start porting stuff back. Unfortunatly there's no kitchens out there for the 750, just complete ROM's.


Can you ask someone to dump their ROM from a 750 with the grab_it tool I have seen on XDA. That's what I used to dump my 700 ROM.

I would love to just have a stripped ROM, with the threaded SMS, the HTML poutlook, and SDHC compatability.

Has this been confimred to work on a Verizon phone. I know there is speculation that you can flash the ROM using the Sprint tool by removing the firmware.bin file. But is this confirmed working. I would hate to brick my phone.

Has this been confimred to work on a Verizon phone. I know there is speculation that you can flash the ROM using the Sprint tool by removing the firmware.bin file. But is this confirmed working. I would hate to brick my phone.


Not yet. Still waiting for a vict....er...volunteer. :hmm:

I've tried integrating the 750's threaded SMS, and it doesn't really function the way it does when it's installed seperately. It appears to me that when installed seperately all you're really doing is using the 750's tmail.exe, basically overlaying the threaded functionality over the existing one (so it's still the 700's actually messaging, just you see it in threaded form if that makes any sense).

With it in the ROM, that functionality is gone, so it doesn't work right. It's also extremely laggy and slow, not sure why, it's not a system resource issue. I suspect it's either the 705's messaging stuff screwing up (IE: looking for a file it's missing over and over again) or some of the registry stuff is goofing it up.


Bit of update on this.

As I mentioned before, I noticed that the phone was incredibly laggy/slow, while a trimmed ROM (same changes except the 750 messaging stuff) was incredibly quick compared to a stock ROM. Additionally a fully charged battery would drain in under 6 hours (I don't know how fast it drained, just that my phone was dead by the time my alarm was set to go off).

My guess is it's doing one of two things:

1) Looking for new messages, or something, using the radio lots which drains the battery.

2) Running and not able to find the right files (such as messaging.exe, which is missing from the 750 files that have been posted), so it either keeps running or breaks and immediatly goes back to look for it.

I think the 2nd is more likely.


Anyway, on to something new and fresh!

Here's the initflashfiles.dat that goes with the Treo. It's not in the ROM, so standard disclaimers apply. That being said, it works for me.

Note that this version I've slightly modified by commenting out the stuff I didn't want (mostly stuff removed in the trimmed ROM I posted above).

By adding this to the ROM, you can move around differnet files, so if something has to reside say in \Program Files\PROGRAM\ you can put it into the ROM, then move it out of the \Windows\ dir and into the \PROGRAM\ dir. Well...I guess it's technically a copy since it'll still reside in ROM....but you get the idea.

Anyway, on to the code.


;
; Copyright (c) Microsoft Corporation. All rights reserved.
;
;
; Use of this source code is subject to the terms of the Microsoft end-user
; license agreement (EULA) under which you licensed this SOFTWARE PRODUCT.
; If you did not accept the terms of the EULA, you are not authorized to use
; this source code. For a copy of the EULA, please see the LICENSE.RTF on your
; install media.
;

;
; Copyright (c) Microsoft Corporation. All rights reserved.
;
;
; Use of this source code is subject to the terms of the Microsoft end-user
; license agreement (EULA) under which you licensed this SOFTWARE PRODUCT.
; If you did not accept the terms of the EULA, you are not authorized to use
; this source code. For a copy of the EULA, please see the LICENSE.RTF on your
; install media.
;


; @CESYSGEN IF WCESHELLFE_MODULES_EXPLORER || SHELL_MODULES_EXPLORER
; @CESYSGEN IF IE_MODULES_IESAMPLE
; @CESYSGEN ENDIF
; @CESYSGEN ENDIF
;
; Copyright (c) Microsoft Corporation. All rights reserved.
;
;
; Use of this source code is subject to the terms of the Microsoft end-user
; license agreement (EULA) under which you licensed this SOFTWARE PRODUCT.
; If you did not accept the terms of the EULA, you are not authorized to use
; this source code. For a copy of the EULA, please see the LICENSE.RTF on your
; install media.
;

; @CESYSGEN IF SERVERS_MODULES_HTTPD
; @CESYSGEN ENDIF SERVERS_MODULES_HTTPD


; @CESYSGEN IF SERVERS_MODULES_P2P
; @CESYSGEN ENDIF SERVERS_MODULES_P2P

; @CESYSGEN IF SERVERS_MODULES_UPNPSVC
; @CESYSGEN ENDIF SERVERS_MODULES_UPNPSVC

; @CESYSGEN IF SERVERS_MODULES_IGD
; @CESYSGEN ENDIF SERVERS_MODULES_IGD


; @CESYSGEN IF SERVERS_MODULES_GENERICUCP
; @CESYSGEN ENDIF SERVERS_MODULES_GENERICUCP


; @CESYSGEN IF SERVERS_MODULES_REMOTEADMIN
; @CESYSGEN ENDIF SERVERS_MODULES_REMOTEADMIN

; @CESYSGEN IF SERVERS_MODULES_PCFILTER
; @CESYSGEN ENDIF SERVERS_MODULES_PCFILTER
;
; Copyright (c) Microsoft Corporation. All rights reserved.
;
;
; Use of this source code is subject to the terms of the Microsoft end-user
; license agreement (EULA) under which you licensed this SOFTWARE PRODUCT.
; If you did not accept the terms of the EULA, you are not authorized to use
; this source code. For a copy of the EULA, please see the LICENSE.RTF on your
; install media.
;

; @CESYSGEN IF DIRECTX_MODULES_IESAMPLE
; @CESYSGEN ENDIF

; @CESYSGEN IF DIRECTX_MODULES_CEPLAYER
; @CESYSGEN ENDIF

; @CESYSGEN IF DIRECTX_MODULES_DVDSAMPLE
; @CESYSGEN ENDIF

; @CESYSGEN IF DIRECTX_MODULES_MEDIARENDERER
; @CESYSGEN ENDIF DIRECTX_MODULES_MEDIARENDERER
root:-Directory("My Documents")
root:-Directory("Program Files")
Directory("My Documents"):-Directory("My Pictures")

:Directory("\My Documents\My Pictures"):-File("Waterfall.jpg","\Windows\Waterfall.jpg")
:Directory("\My Documents\My Pictures"):-File("Flower.jpg","\Windows\Flower.jpg")

Directory("My Documents"):-PermDir("Templates")

Directory("Program Files"):-Directory("Connections")

Directory("\Windows"):-Directory("Help")
Directory("\Windows"):-Directory("Fonts")
Directory("\Windows"):-Directory("Programs")
Directory("\Windows"):-Directory("StartUp")
Directory("\Windows"):-PermDir("Start Menu")
Directory("\Windows"):-Directory("Temporary Internet Files")
Directory("\Windows"):-Directory("AppButtons")
Directory("\Windows"):-Directory("Favorites")
Directory("\Windows"):-Directory("Rings")
Directory("\Windows"):-Directory("AppMgr")

Directory("\Windows"):-PermDir("System")
Directory("\Windows\System"):-PermDir("ConfigMgr")

Directory("\Windows\System"):-PermDir("DumpFiles")
Directory("\Windows\System"):-PermDir("CabQueue")


; Start Menu contents

Directory("\Windows\Start Menu"):-PermDir("Programs")
Directory("\Windows\Start Menu"):-PermDir("Settings")

Directory("\Windows\Start Menu"):-File("Help.lnk","\Windows\help.lnk")
Directory("\Windows\Start Menu\Programs"):-File("Search.lnk","\Windows\search.lnk")

Directory("\Windows\Start Menu"):-File("Phone.lnk","\Windows\cprog.lnk")
Directory("\Windows\Start Menu\Programs"):-File("Tasks.lnk","\Windows\tasks.lnk")

Directory("\Windows\Start Menu\Programs"):-File("Modem Link.lnk","\Windows\ATCIUI.lnk")

Directory("\Windows\Start Menu\Programs"):-File("ActiveSync.lnk","\Windows\sync.lnk")

Directory("\"):-File("Print Screen.lnk","\Windows\prtscrn.lnk")

Directory("\Windows\Start Menu"):-File("Calendar.lnk","\Windows\calendar.lnk")
Directory("\Windows\Start Menu"):-File("Contacts.lnk","\Windows\addrbook.lnk")
Directory("\Windows\Start Menu"):-File("Internet Explorer.lnk","\Windows\pie.lnk")


Directory("\Windows\Start Menu"):-File("Messaging.lnk","\Windows\tmail.lnk")
; turn off the OLD inbox later
; put the OLD inbox to the program floder (temporary)

Directory("\Windows\Start Menu\Programs"):-File("Notes.lnk","\Windows\notetake.lnk")
;Directory("\Windows\Start Menu"):-File("Record.lnk","\Windows\voice.lnk")

;Directory("\Windows\Start Menu\Programs"):-File(0409_WORLDCLOCKLNK,"\Windows\clock.lnk")
Directory("\Windows\Start Menu\Programs\Office"):-File("Word Mobile.lnk","\Windows\pword.lnk")
Directory("\Windows\Start Menu\Programs\Office"):-File("PowerPoint Mobile.lnk","\Windows\ppt.lnk")
Directory("\Windows\Start Menu\Programs\Office"):-File("Excel Mobile.lnk","\Windows\pxl.lnk")

Directory("\Windows\Start Menu\Programs"):-File("Pictures & Videos.lnk","\Windows\pimg.lnk")

Directory("\Windows\Start Menu\Programs"):-File("Download Agent.lnk","\Windows\dlagent.lnk")

; This link represents the SIM Toolkit application -- it should NOT be localized
Directory("\Windows\Start Menu\Programs"):-File("Sim Toolkit.lnk","\Windows\SimTkUI.lnk")


Directory("\Windows\Start Menu\Programs"):-File("Calculator.lnk","\Windows\calc.lnk")
Directory("\Windows\Start Menu\Programs"):-File("File Explorer.lnk","\Windows\fexplore.lnk")

Directory("\Windows\Start Menu\Programs"):-Directory("Games")
Directory("\Windows\Start Menu\Programs\Games"):-File("Solitaire.lnk","\Windows\solitare.lnk")
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\gamesico.lnk")
Directory("\Windows\Start Menu\Programs\Games"):-File("Bubble Breaker.lnk","\Windows\BubbleBreaker.lnk")




; App Button default links
Directory("\Windows\AppButtons"):-File("Calendar.lnk","\Windows\calendar.lnk")
Directory("\Windows\AppButtons"):-File("Contacts.lnk","\Windows\addrbook.lnk")
Directory("\Windows\AppButtons"):-File("Tasks.lnk","\Windows\tasks.lnk")
Directory("\Windows\AppButtons"):-File("Record.lnk","\Windows\voice.lnk")

; Startup Folder
Directory("\Windows\StartUp"):-File("coldinit.lnk","\Windows\coldinit.lnk")

Directory("\Windows\StartUp"):-File("bugtrap.lnk","\Windows\bugtrap.lnk");
Directory("\Windows\StartUp"):-File("poutlook.lnk","\Windows\poutlook.lnk")

Directory("\Windows\StartUp"):-File("Welcome.lnk","\Windows\welcome.lnk")

Directory("\Windows\Start Menu\Programs"):-File("Terminal Services Client.lnk", "\Windows\mstsc.lnk")


Directory("Program Files"):-Directory("Windows Media Player")
Directory("\Windows\Start Menu"):-File("Windows Media.lnk","\Windows\WindowsMedia.lnk")
Directory("\Program Files\Windows Media Player"):-File("Default(Portrait).skn","\Windows\portrait.lnk")
Directory("\Program Files\Windows Media Player"):-File("Default(Landscape).skn","\Windows\landscape.lnk")
Directory("\Program Files\Windows Media Player"):-File("Default(Square).skn","\Windows\square.lnk")
Directory("\Program Files\Windows Media Player"):-File("Welcome To Windows Media.wma","\Windows\wm_start.lnk")

; Help .LNK files

Directory("\Windows\Help"):-File("ActiveSync.lnk","\Windows\h_sync.lnk")


; Transcriber available for USA, FRA & GER
Directory("\Windows\Help"):-File("Transcriber.lnk","\Windows\Transcriber.lnk")


Directory("\My Documents\Templates"):-File("Blank Note.pwi","\Windows\blank.pwi")
Directory("\My Documents\Templates"):-File("Meeting Notes.pwi","\Windows\meeting.pwi")
Directory("\My Documents\Templates"):-File("Memo.pwi","\Windows\memo.pwi")
Directory("\My Documents\Templates"):-File("Phone Memo.pwi","\Windows\phone.pwi")
Directory("\My Documents\Templates"):-File("Sample Note.pwi","\Windows\sample.pwi")
Directory("\My Documents\Templates"):-File("To Do.pwi","\Windows\todo.pwi")

Directory("\My Documents\Templates"):-File("Blank Document.dot","\Windows\blank.dot")
Directory("\My Documents\Templates"):-File("Meeting Notes.dot","\Windows\meeting.dot")
Directory("\My Documents\Templates"):-File("Memo.dot","\Windows\memo.dot")
Directory("\My Documents\Templates"):-File("Phone Memo.dot","\Windows\phone.dot")
Directory("\My Documents\Templates"):-File("0409_SAMPLE_DOT","\Windows\sample.dot")
Directory("\My Documents\Templates"):-File("To Do.dot","\Windows\todo.dot")



:Directory("\My Documents\Templates"):-File("Vehicle Mileage Log.xlt","\Windows\VehicleML.xlt")



Directory("My Documents"):-Directory("Personal")
Directory("My Documents"):-Directory("Business")
Directory("My Documents"):-Directory("My Music")

Directory("\Windows\StartUp"):-File("voice command.lnk","\Windows\voicecommand.lnk")
Directory("\Windows\Help"):-File("Voice Command.lnk","\Windows\h_voicecommand.lnk")





; Add link to Sounds and Notifications
Directory("\Windows\Start Menu\Programs"):-File("Sounds.lnk","\Windows\Sounds.lnk")

; Add Camera link.
; 9/1/05: Removed to support cameraless devices. See InstallCameraShortcut.cpp in BootApp
; Directory("\Windows\Start Menu\Programs"):-File("Camera.lnk","\Windows\Camera.lnk")

; Add link to QuickTour
:Directory("\Windows\Start Menu\Programs"):-File("Quick Tour.lnk","\Windows\Quick Tour.lnk")

; Add link to USBSwitch
Directory("\Windows\Start Menu\Programs"):-File("UsbSwitch.lnk","\Windows\UsbSwitch.lnk")

:Directory("\Windows\Start Menu\Programs"):-File("PDF Viewer.lnk","\Windows\Picsel.lnk")

Directory("\Windows\Start Menu\Programs"):-File("Wireless Sync.lnk","\Windows\WirelessSync.lnk")

Directory("\Windows\Start Menu\Programs"):-File("Downloads.lnk","\Windows\Downloads.lnk")

;START SPCS DEVICES
;Following links need to be created for SPCS devices
:Directory("\Windows\Start Menu\Programs"):-File("My Treo.lnk","\Windows\MyTreo.lnk")
; Mobile link icon
Directory("\Windows\Start Menu\Programs"):-File("Modem Link.lnk","\Windows\ATCIUI.lnk")
; Add link to GetGood
:Directory("\Windows\Start Menu\Programs"):-File("Get Good.lnk","\Windows\GetGood.lnk")

:Directory("\Windows\Start Menu\Programs"):-File("On Demand.lnk","\Windows\OnDemand.lnk")
:Directory("\Program Files"):-Directory("Picsel"):-Directory("File Viewer")
:Directory("\Program Files\Picsel"):-Directory("File Viewer")
;END SPCS EDVICES



;We want the Indigo theme to be the default theme after a hard-reset.
;Originally in the jam file there were the two files, stwater.gif and tdywater.gif. When you
;switch to another theme, windows couldn't delete the these files because they were in ROM.
;Instead, we added Indigio_*.gif in the jam file and copy these two files
;to the \windows directory as stwater.gid and tdywater.gid (so that deletion can succeed).
;TODO: The problem with this solution is that this fix assumes that the default theme is
;Indigo. Also, this solution works only when we do a hard-reset, for soft-reset
;cases (possibly after an image update), this solution won't work. We need to remove the following
;lines and do this conditionally in bootapp only if the theme is set to Indigo.
Directory("\Windows"):-File("tdywater.gif","\Windows\Indigo_tdywater.gif")
Directory("\Windows"):-File("stwater.gif","\Windows\Indigo_stwater.gif")



And if anyone's concerned with the safety of this (as far as Sprint phones are concerned...plus I make no guarantees regardless) here's a copy of my flash log (DC.log). Note that I actually at one point deleted this log, IIRC it had approx 12-15 flashes in it. The times are funny because sometimes I've re-flashed my phone without ever turning the radio on, so those 2006 dates are based on the clock that hasn't been updated, though they're all in order, so you can still get an idea of how many times I've flashed.

No serious problems flashing yet, either. Anyone with a (Sprint) phone that's worried about this, I personally believe that the worst that might happen is you have to do a hard reset and start from scratch. (Insert standard disclaimers here.)

Please post your results if you've tried flashing, and any suggestions/comments/questions.


FEB 8 2006 00:01:47 : AutorunPath: \Storage Card\2577\
FEB 8 2006 01:18:27 : AutorunPath: \Storage Card\2577\
FEB 8 2006 01:24:12 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:45 : AutorunPath: \Storage Card\2577\
MAY 3 2008 11:35:40 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:26 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:52 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:03:19 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:07:58 : AutorunPath: \Storage Card\2577\
MAY 4 2008 10:56:24 : AutorunPath: \Storage Card\2577\
MAY 4 2008 14:37:48 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:02:01 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:02:01 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:02:22 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:03:09 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:02:15 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:46 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:27:42 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:04:02 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:04:41 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:15:27 : AutorunPath: \Storage Card\2577\
MAY 4 2008 22:46:50 : AutorunPath: \Storage Card\2577\
MAY 5 2008 07:42:11 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:46:34 : AutorunPath: \Storage Card\2577\
MAY 5 2008 19:02:34 : AutorunPath: \Storage Card\2577\
MAY 5 2008 19:18:13 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:29:12 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:34 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:03:08 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:03:55 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:02:24 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:38 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:09:00 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:35 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:02:41 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:00:56 : AutorunPath: \Storage Card\2577\
MAY 7 2008 23:16:32 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:23 : AutorunPath: \Storage Card\2577\
MAY 8 2008 02:53:29 : AutorunPath: \Storage Card\2577\
MAY 8 2008 21:48:15 : AutorunPath: \Storage Card\2577\
MAY 10 2008 13:02:17 : AutorunPath: \Storage Card\2577\
MAY 10 2008 13:06:53 : AutorunPath: \Storage Card\2577\
MAY 10 2008 13:12:14 : AutorunPath: \Storage Card\2577\
MAY 10 2008 14:24:38 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:09 : AutorunPath: \Storage Card\2577\
FEB 8 2006 00:01:11 : AutorunPath: \Storage Card\2577\
MAY 11 2008 12:01:13 : AutorunPath: \Storage Card\2577\
MAY 11 2008 13:19:36 : AutorunPath: \Storage Card\2577\

Not yet. Still waiting for a vict....er...volunteer. :hmm:



I have a 700wx that is possibly bricked. It comes on and stays at the white Treo screen. If we can recover it from there I'm willing to load whatever you want on it. It was my old company phone.

I have a 700wx that is possibly bricked. It comes on and stays at the white Treo screen. If we can recover it from there I'm willing to load whatever you want on it. It was my old company phone.


Sprint or Verizon? (Assuming it's Verizon here. :) )

Feel free to try either the default ROM or my trimmed one.

If it's a Verizon phone, then make sure you delete the firmware as recommended (first post I believe).

Some of your phone settings may not work since some stuff might be configured for Sprint, instead of Verizon. But if the phone account isn't active, not sure how to test for that.

Hmm, that gets me thinking. We might need a Verizon "package" to reset some registry settings and whatnot back to Verizon defaults. Also I need to replace the splash screen when turning on/off the radio as it says Sprint....

A little update here.

First off, I updated my first post with an extra step for a really-truely-honest-it-works-this-time clean flash.

Seems if you just do a hard reset, then let WM load, not everything gets cleared. And flashing simply upgrades what you have currently, so if it's not stock (it's been modified), it won't touch it.

The solution (or at least one that's worked for me, YMMV) is to do a hard reset and before the bootloader kicks in (that is before you see the bar scrolling across the screen, at the Treo splash screen) pull the battery, and then continue with the flash as normal.

I had to do this exactly in this order to get everything to work. Darth Pooh did not however.... :confused:

Additionally you may have to do a soft/hard reset after the flash to get everything working properly. Since MortScript gets registered after cDate tries to run, you're going to have to do a soft reset anyway to get that working. (That's in my custom ROM, see below.)


I've just about completed my custom ROM. Here's a list of the changes.

Removed:
MSN Instant Messanger
Picsel File/PDF Viewer
Pocket MSN
Software Store
OD
Various help files (pretty much all the ones I could get my hands on)
Various wav/wma files (several you couldn't even use)

Added/Replaced:
MortScript (and cDate script, changes your carrier name into a date line)
PIEPlus 2.2 (Unregistered)
PocketXpdf (replaces Picsel PDF viewer)
psShutXP
regedit (freebie version)
Sprite Backup
Ubuntu style wait cursor
Various popular registry tweaks found on the board
Start Menu\Programs has been cleaned up and streamlined (many programs are in subdirectories)
Radio On/Off sounds are replaced (reduces size from approx 256kb to approx 13kb)
Misc other things I forgot


Darth Pooh (as mentioned above) has tested a beta version of this with only one issue (which I've resolved).

As always no guarantees and I've only tested this on Sprint.

I'm not *QUITE* done with it yet (almost). When I'm finished I'll upload it. That is.....if anyone's interested in it. :D

Great stuff!

I hacked the heck out of my ROM on the 650, and I look forwrad to doing the same here.

Of course, by the time I get it all figured out it will be time to move on... :(

My phone is starting to shows signs of age - small cracks in the case, etc.

Great stuff!

I hacked the heck out of my ROM on the 650, and I look forwrad to doing the same here.

Of course, by the time I get it all figured out it will be time to move on... :(

My phone is starting to shows signs of age - small cracks in the case, etc.


I did a lot with my 650 as well. Thought I'd bricked it more than once. :eek:

I plan on adoptingthe 800w once I'm sure it's stable and there are no major issues. The 700wx will be going to the Mrs though, so it's not a total loss. :)

Plus, in theory, this development should speed up custom ROM's for the 800w. Hopefully (*crosses fingers*) Sprint uses the same format for the 800w ROM. Of course we'll still need to wait for a ROM update, which could be a year after the release....

@ Ebag

I have a Verizon ROM from my phone. I dumped using grab_it. I can send you a dumb.bin, imgfs files, or the ROM dump. Let me know what you want and I'll send it to you.

Ebag,

Very much looking forward to your new Custom ROM. I've already flashed using the one you posted earlier and it worked just fine, as far as I can tell. And as soon as you get the new one up I'll flash it quick as I can.

I would encourage you though, if there is any way to replace Pocket Outlook with the WM6 Pocket Outlook that would be great. And, of course, please keep working on the threaded SMS incorporation into the custom ROM as well.

Keep up the good work, you've got a lot of 700wx users sitting on the edge of our seats waiting to see where this goes. :D

Ebag,

I'm very interested to know if your custom rom fixes the freeze issue when connected via BT DUN. can you test this? basically it happens when there is a lot of data being transferred, such as downloading attachments. it happens using PDANet, USB Modem, or straight DUN, all when connected via BT. When connected via USB, the problem doesn't happen. The problem is well reported in this forum.

thanks!

@ Ebag

I have a Verizon ROM from my phone. I dumped using grab_it. I can send you a dumb.bin, imgfs files, or the ROM dump. Let me know what you want and I'll send it to you.


Feel free to send over what you have to my e-mail (ebagola [at] gmail com). I would especially like to get my hands on the Verizon HKLM and HKCU registry branches to see if there's anything different there.


I would encourage you though, if there is any way to replace Pocket Outlook with the WM6 Pocket Outlook that would be great. And, of course, please keep working on the threaded SMS incorporation into the custom ROM as well.


That's the plan. I *JUST* got the 750 reg dump (finally!) so I hopefully can start making some headway on it.

I'm very interested to know if your custom rom fixes the freeze issue when connected via BT DUN. can you test this?


I don't use BT DUN (when you have a Redfly, BT DUN seems somewhat redundant :D ) but if you have Sprint feel free to try flashing the stripped ROM I posted above, and see if it works any better for you.


I will say this as far as speed of the device goes (in general). With a stock ROM I used XCPUScaler to speed up the device and make it feel 'snappy' in day to day use. With the trimmed (or my custom) the speed feels about the same (or even faster) as with XCPUScaler at 520. I loaded XCPUScaler after flashing to the latest version, bumped it up to 520...and didn't notice a difference. While I'm sure it'll make a difference for CPU hungry applications, for regular use it's no longer required for me. Darth Pooh as well mentioned that the device felt far snappier.

Not only does the rom feel snappier, with the same amount of applications (if not more) I have less lag. It's almost if I have a completely different device at times. It's no PALM OS snappy... but then again, PALM OS doesn't do half of the things WM does good. So, take that for what it's worth.

is there a way to save my current rom image before trying your custom rom? i'm on sprint 1.14 and don't want to upgrade to the latest 1.15 if i don't have to.

is there a way to save my current rom image before trying your custom rom? i'm on sprint 1.14 and don't want to upgrade to the latest 1.15 if i don't have to.


Not without a ROM of 1.14, which AFAIK doesn't exist.

ROM posted!

Check second post for link.

There is one small "bug" in it. Mortscript launches every time (should only launch first time, then remove itself). You can either remove reg_Mortscript.lnk from the startup or just hit OK on the message that pops up. It's not a big deal to me since it only comes up after a soft/hard reset, so I just hit OK.

i keep getting a rom not found error once i get to the part where is ask if i want to flash the rom. i'm trying a alltel treo but i WANT it to be sprint after the flash is that possible?

i keep getting a rom not found error once i get to the part where is ask if i want to flash the rom. i'm trying a alltel treo but i WANT it to be sprint after the flash is that possible?


No idea, you'll be in untested waters. :)

What step is it failing on (follow the steps in the first post)? Which ROM are you using? Need more info and more details.

Also, make sure you format your card first into FAT32 format. FAT, FAT16, NTFS, or RAW formats won't work.

Okay I am trying to cook a ROM, but can't figure out how to get a .nb0 file. Can I get some help with that? Thanks.

Okay I am trying to cook a ROM, but can't figure out how to get a .nb0 file. Can I get some help with that? Thanks.


If you read post 1 (to get the default Sprint ROM) or post 2 (to get one of my custom ones) you'll see where to get them from.

Custom ROM - Take 1 works great!

So far so good, ebagg333. I'm quite impressed. I like the way you organized the Programs.

One thing, the PIE+ expires in 2 weeks, and costs $15. Is there a way to just downgrade back to PIE? If not, I can figure something out. After all, this is Your ROM, not mine. :) Thanks for sharing it with the community.

One thing, the PIE+ expires in 2 weeks, and costs $15. Is there a way to just downgrade back to PIE?


Actually it's always expired for me after the first soft reset. :o

Anyway, once it expires it goes back to the normal PIE, but it still adds a couple of features (in the normal menu) that are useful. I really would recommend dropping the $15, and purchasing it. It's a top notch program that seriously improves your browsing experience, even if you don't use the tabs.

So let me see if I got this right...
The only con to this is you could brick your phone if you are not careful...

The pluses are... Faster phone... (Less looking it has to do...)
Loading programs into the ROM will free up memory in the RAM of the machine..

With the programs in ROM when you do a hard reset you can have the phone back up and running in a short period of time with minimal additional steps needed. (Syncing your contacts etc and maybe adding any new programs since last burn..)

I am assuming then if I were to take my phone as is.. Strip down the ROM, add the programs I use into it... Then the Free Ram is increased which by its self should help speed up the phone as well?

Just trying to see if I am catching the drift here...

Thanks!

Oh and how do you install programs into the ROM? Is there a way to install the CABS or something or how is it done?

Thanks!

Rodney

OK...this is starting to sound good here, I have 2 quick questions before I try one of the custom ROM's posted here:

1-Has anyone tried this with a Verizon device yet? If so, what was the outcome?

2-If I have a current backup of my device, do I just run the backup file after the flash, or is that an instance where that is a 'no-no'???

Thanks guys, some great work being done here!!

If you read post 1 (to get the default Sprint ROM) or post 2 (to get one of my custom ones) you'll see where to get them from.


Thanks for the quick reply and maybe I am dense, but I don't see it. I see where I can download your Sprint .nbo files, but I am on Verizon. I have a ROM dump from my phone and would like to cook that one. Is there any documentation to take my dump and convert it into a .nb0 file? Is there even a way to do that?

OK...this is starting to sound good here, I have 2 quick questions before I try one of the custom ROM's posted here:

1-Has anyone tried this with a Verizon device yet? If so, what was the outcome?

2-If I have a current backup of my device, do I just run the backup file after the flash, or is that an instance where that is a 'no-no'???

Thanks guys, some great work being done here!!


As far as Q1 goes, I do not think anyone in this thread has tried this on VZW phone. I have asked the same question and gotten no reply. I do not have the balls to be the first either. And I don't think you are the guy. Which means we have to convince someone else to try it first.

As far as Q1 goes, I do not think anyone in this thread has tried this on VZW phone. I have asked the same question and gotten no reply. I do not have the balls to be the first either. And I don't think you are the guy. Which means we have to convince someone else to try it first.


Should I take offence to that??????? LOL :eek:

Your right though, I'm NOT the guy!!!!!! Hopefully a VZW user in here WILL get the nerve up to try sometime!!!!


I am assuming then if I were to take my phone as is.. Strip down the ROM, add the programs I use into it... Then the Free Ram is increased which by its self should help speed up the phone as well?


No. Removing programs does not free up RAM. If you have a W you still only have 32 megs, if you have a WX you still only have 64 megs.

The working theory behind the snappyness of the device after flashing is that you can remove over 350 files, and that when you run a program/function that parses the \Windows\ directory, it has hundreds of less files to go through so it runs quicker. That's the theory, I have no idea if it's true or not but I can say that for me, my device runs significantly quicker.



Oh and how do you install programs into the ROM? Is there a way to install the CABS or something or how is it done?


You can install the CAB's but that defeats the point. All that would do would store the installers in ROM, you'd still have to install them.

What you do is add the actual files (the ones the CAB's install) to the ROM. Then you might need to add some reg keys. If you open the .CAB with an archive program (WinRAR works) it might have a _setup.xml. That'll show you exactly what you need to add to get it working (usually). You can then add that to the .PROVXML of your choice. If it doesn't have a _setup.xml, then things get a bit more complex.

I won't go into more detail on it at the moment mostly because there's a lot of complexity to it. If you want to cook your own ROM, I suggest you start with programs/files that don't require registry settings (MortScript and Sprite Backup are two examples, they set themselves up the first time they are run).

Basically you have to understand the .PROVXML and initflashfiles.dat in order to install programs. You can also look at my reg_ files (such as reg_PIEPlusDLL.lnk) to see how I registered DLL's for PIEPlus (normally DLL's are registered on extraction). That's a cool little tool someone came up with, and has come in handy.

If you have a specific question about it, feel free to post it. Your specifics may or may not get answered though until we get more people in here who are comfortable with cooking ROM's.


1-Has anyone tried this with a Verizon device yet? If so, what was the outcome?


Not yet that I've heard.

2-If I have a current backup of my device, do I just run the backup file after the flash, or is that an instance where that is a 'no-no'???


You can run your backup to restore after the flash. A couple of things to be aware of.

1) Your backup may overwrite files in the \Windows\ directory.
2) Your backup may (probably will) overwrite the registery, meaning some of my changes there will be lost.

My recommendation is if you can, just restore non \Windows\ files and your personal DB (contacts). Then reinstall the proggies you want, and then make a new backup. This way you don't overwrite the registry or any files in \Windows\.

Overwriting either isn't the end of the world, and if you don't care about the Reg hacks I did, go for it.

Thanks for the quick reply and maybe I am dense, but I don't see it. I see where I can download your Sprint .nbo files, but I am on Verizon. I have a ROM dump from my phone and would like to cook that one. Is there any documentation to take my dump and convert it into a .nb0 file? Is there even a way to do that?


If you're on Verizon and not familiar with the basics of cooking a ROM, I'd recommend that you hold off until someone else has blazed the trail. It sounds like you're not very familiar with the process, and I'd hate to see you brick your device. :)

To answer your question more specifically, you can't just take a handful of files, throw them in a pot, cook it up, and come out with a ROM. You have to have a ROM to start with. There are lots of required files that you won't have with your dump.

If you feel gutsy, download the Sprint ROM updater, delete the firmware file, and flash away. Just be prepared to go buy another Treo (or at least exchange yours under insurance) if something goes wrong.

Should I take offence to that??????? LOL :eek:


I don't know, should you? I did not mean to offend. I am really anxious to try this. I was a ROM cooking fool with my T650. Loved it. Half of my apps where in the ROM and I could hard reset and not lose anything. I am still unclear about how to put Program Files into my ROM if they belong in the Program Files folder rather than the Windows folder. Programs such as AEButton+, Resco File Explorer, and Wisbar Advanced.

I had zLauncher, Backupman, and all sorts of other programs in my 650 ROM. And making those ROMS was soooooo easy. I have not tried actually even cooking a VZW ROM yet, since I don't have a VZW .nbO file. Can I use the Sprint one? I don't know. I am trying to find a way to get Ebag my ROM and maybe he can tell us the differences between Sprint and VZW concerning the ROM and the Registry.

EDIT: I just saw Ebag response and it looks as though, I will have to wait longer for someonemuch smarter than me who has Verizon to figure this out first. Damn. I am itching to cook a ROM with at least SDHC in it. Hard resets have now become slightly more of a pain without it in the ROM.

I am still unclear about how to put Program Files into my ROM if they belong in the Program Files folder rather than the Windows folder. Programs such as AEButton+, Resco File Explorer, and Wisbar Advanced.


That's the purpose of initflashfiles.dat. But many programs don't *HAVE* to be in \Program Files\, that's just where they get installed to. Even if they have reg keys pointing there, you can probably just point those keys at the \Windows\ dir and call it good.

I setup Sprite Backup to copy some files to the \Program Files\ dir, but that was A) part lazyness, so I didn't have to setup the registry differently and B) the files copied were fairly small, so it's not a big impact.


I had zLauncher, Backupman, and all sorts of other programs in my 650 ROM. And making those ROMS was soooooo easy.


My kitchen isn't nearly at the point where it is that easy.


I have not tried actually even cooking a VZW ROM yet, since I don't have a VZW .nbO file. Can I use the Sprint one? I don't know. I am trying to find a way to get Ebag my ROM and maybe he can tell us the differences between Sprint and VZW concerning the ROM and the Registry.


AFAIK no one has tried cooking a Verizon ROM yet. The theory is you can use the Sprint one (see first post).

AFAIK no one has tried cooking a Verizon ROM yet. The theory is you can use the Sprint one (see first post).


Thanks for the info. I will have to sit on the sidelines and wait for someone much smarter than I to try this. IM me when you log on again and I can get you the VZW ROM dump I have and maybe we can determine from there how different the Sprint and VZW ROMS are. I IMed you last night and got notice that you IMed me back, but I had unfortunately already logged off. You can find my IM logons in my profile.

My error is happening after step 12. i press up then get the message unable to locate rom image. i am fairly sure my card is fat32 but i am barrowing a friends card reader to try the reformat myself.

Okay, so for kicks and giggles I took the Sprint .nb0 file you uploaded and went through the process of starting a ROM cook. The "1-Tear Down ROM.bat" file created two files, imgfs_raw_data.bin and imgfs_removed_data.bin.

Like I said before I have a VZW ROM dump. I tore it down and ended up with two files with the exact same names. So in order to cook a VZW ROM, could I not just start with my imgfs files from my ROM dump. Cook, then build it back up to a .nb0 file? Is my theory flawed somehow. I am trying to find something that will compare the Sprint ROM dump to my VZW ROM dump and see if I can determine what the differences are.

Any input on this? Thanks.

My error is happening after step 12. i press up then get the message unable to locate rom image. i am fairly sure my card is fat32 but i am barrowing a friends card reader to try the reformat myself.


My guess is that it's not in FAT32 format. I believe the 700WX will support most formats (probably other than *NIX or NTFS, though I haven't tested that), so it's likely in FAT or FAT16. Most cards come pre-formated with just FAT, as that's the most (usually) compatible.

I got that exact message until I'd reformatted mine with FAT32.


Okay, so for kicks and giggles I took the Sprint .nb0 file you uploaded and went through the process of starting a ROM cook. The "1-Tear Down ROM.bat" file created two files, imgfs_raw_data.bin and imgfs_removed_data.bin.

Like I said before I have a VZW ROM dump. I tore it down and ended up with two files with the exact same names. So in order to cook a VZW ROM, could I not just start with my imgfs files from my ROM dump. Cook, then build it back up to a .nb0 file? Is my theory flawed somehow. I am trying to find something that will compare the Sprint ROM dump to my VZW ROM dump and see if I can determine what the differences are.

Any input on this? Thanks.


Possibly. I just don't know.

Once you have the two IMGFS files, you can then dump the rom (I think I marked it as "raw"). You could then take the default Sprint one, dump that ROM (same method), and then use WinMerge or another program to diff the files. You'll only be able to go off file size to diff, but it should give you a pretty good idea of the changes.

Where did you get your IMGFS files for your Verizon phone from?

Confirm working on Telus/Bell Treo 700wx (But it replaces your trun on/off logo with Sprint)

Confirm working on Telus/Bell Treo 700wx (But it replaces your trun on/off logo with Sprint)


Good news!

I need a new on/off logo/graphic, but I'm not terribly graphically inclined. Anyone around here with the skills to do so? Need a 240x240 image (I can convert as needed).

Which ROM did you use? Did you just do a straight flash, or tweak it any?

I am a WM newbie, (had to read elsewhere how to do a hard reset..), so no tweaks/cooking, I did backup my current rom with r2sd. (I hope it contains a complete backup..)

I used your "Take 1" rom.
The on/off sound is different too.
I tried ##PRI but its still not responding.
Also does it update your 'version' (ie: ROWEN) number.?
Will try using LAN Bluetooth with my picoblue later on. (For reverse DUN)


Do you plan to use the "CAB and left softkey" method for flashing? (It was mentioned somewhere in the forums)

Thanks for your time and effort. I did the similar thing for people with 700p into 755p :) You have better control of organizations/english than me so the positive outcome was better than mines.

this whole process was originally started as a result of my putting a sprint nb0 rom that I customized onto a verizon phone; so, yes, it works on verizon.

ebag333 has been a leader/pioneer here in making this process easier for folks to manage (kitchen), and for keeping everyone updated with project progress reports. great work, ebag333.

the only main difference here is that the sprint rom that we started with is a rom from an SD updater, which is a raw image; verizon only allows for pc-based updates, which use the encrypted rom format ruu. yes, there are slight carrier branding differences, but they are essentially the same rom.

those of you who are trying to use grab_it dumps must beware of the rom structure and offsets if they try to build a rom; it is much safer to use the nb0 as a starting point until more information comes along regarding the rom structure within the actual device itself.

The on/off sound is different too.


That's intentional. It saves almost 250kb of space. :)


I tried ##PRI but its still not responding.


Works for me.


Also does it update your 'version' (ie: ROWEN) number.?


You mean the Phone -> About version number? No, it still thinks it's the 1.15 Sprint update.


Will try using LAN Bluetooth with my picoblue later on. (For reverse DUN)


Let me know how that works out. I've only tested my Redfly with bluetooth after flashing.



Do you plan to use the "CAB and left softkey" method for flashing? (It was mentioned somewhere in the forums)


I know you can run the update off of the SD card from the program. I personally prefer the hardware version of it.

I'm not sure what you're referring to by "CAB and left soft key" method though.

Another Successful flash using your custom rom and instructions on a sprint treo 700wx, love what i see so far :P, will def block off some time this weekend to play around with the cooker and see what i can come up with.

Thanks for all your efforts ebag and everyone involved in this project, i will be watching this thread very closely

:cheers:

Once you have the two IMGFS files, you can then dump the rom (I think I marked it as "raw"). You could then take the default Sprint one, dump that ROM (same method), and then use WinMerge or another program to diff the files. You'll only be able to go off file size to diff, but it should give you a pretty good idea of the changes.

Where did you get your IMGFS files for your Verizon phone from?


From my grab_it dump. I had a dump.bin file. Using the XDA imgfs tools, I was able to prepare the .bin file into the imgfs files. I tried those in your kitchen and was trying to disassemble the registry branches and could not get that to work. I kept getting errors. If we can meet up on AIM, I can get you what I have and you can see what you can do.

this whole process was originally started as a result of my putting a sprint nb0 rom that I customized onto a verizon phone; so, yes, it works on verizon.

those of you who are trying to use grab_it dumps must beware of the rom structure and offsets if they try to build a rom; it is much safer to use the nb0 as a starting point until more information comes along regarding the rom structure within the actual device itself.


Wow. I am sorry if I missed that. So someone has tried this process on a VZW phone and it is confirmed working. Time to start playing for me now. I have the grab_it ROM, but I will probably just stick with the Sprint ROM since it is working. I can put the VZW on/off logos back into the ROM and not have to worry about the Sprint logo there. I just thought if there was a way to use the grab_it dumps, I could work with a VZW ROM. Now the only thing I need to make sure that I do is delete the firmware.bin file from the ROM updater. Right?

You mean the Phone -> About version number? No, it still thinks it's the 1.15 Sprint update.


I wonder what it will do on a VZW phone. Will it leave my version at 1.22 or change it to the Sprint 1.15. Hmmmm. I guess we will find out.

Ebag. Maybe I can get some help. I want to replace two files in Windows with others so that I can use my SDHC card after a hard reset. DO I need to put the original files in the To Delete folder and the new files in the To Add folder? Or do I simply put the files I want in the To Add folder and it will overwrite the originals? Thanks.

DO I need to put the original files in the To Delete folder and the new files in the To Add folder? Or do I simply put the files I want in the To Add folder and it will overwrite the originals? Thanks.


Well, it will add the new ones if you don't delete the old ones, but it adds them a second time and you get unexpected results. Not recommended.

You have to delete the originals before you can add the new ones. That's why Delete is a higher step than Add. :)

But yes, you simple place the files you want in \ToAdd\, the files you want to remove in \ToDelete\, and then your imgfs files should be updated properly.

For modules (files that are in a folder when you do a dump, the folder name is the same as the file name) I always create a text file in \ToDelete\, rename it to module.ext (such as pwo.dll or messaging.exe, etc). That way I have the "file" in \ToDelete\ (all the script cares about is the name, it doesn't have to be the same file size) and I can sort the folder by size to see what I'm deleting by module (file size of 0) and what's sitting in there from the windows directory itself.

You can play with it a few times by dumping the imgfs, running the add batch script, running the delete batch script, then redumping (after renaming the orginal dump folder) and seeing the difference between the two.

I still do not recommend making changes directly to the dump folder and then recompiling the dump folder back to an imgfs file. I've had mixed success with that, which is a shame, because it'd make it a lot easier.

Well, it will add the new ones if you don't delete the old ones, but it adds them a second time and you get unexpected results. Not recommended.

You have to delete the originals before you can add the new ones. That's why Delete is a higher step than Add. :)

But yes, you simple place the files you want in \ToAdd\, the files you want to remove in \ToDelete\, and then your imgfs files should be updated properly.

For modules (files that are in a folder when you do a dump, the folder name is the same as the file name) I always create a text file in \ToDelete\, rename it to module.ext (such as pwo.dll or messaging.exe, etc). That way I have the "file" in \ToDelete\ (all the script cares about is the name, it doesn't have to be the same file size) and I can sort the folder by size to see what I'm deleting by module (file size of 0) and what's sitting in there from the windows directory itself.

You can play with it a few times by dumping the imgfs, running the add batch script, running the delete batch script, then redumping (after renaming the orginal dump folder) and seeing the difference between the two.

I still do not recommend making changes directly to the dump folder and then recompiling the dump folder back to an imgfs file. I've had mixed success with that, which is a shame, because it'd make it a lot easier.


Your last paragraph answered my last question. So if I know the names of the files I want to delete and add, then I do not actually have to dump the rom. I can work it all from the imgfs files right?

Here is what I am trying to accomplish for now. I am trying to add sdbus.dll and sdmemory.dll for the SDHC and then the RadioWelcome and RadioGoodbye images back to Verizon.

So in order to do this. I put the files in the "ToAdd" folder and then create the text files with the same names in the "ToRemove" folder. Run the ToRemove batch file, then the ToAdd batch file. Then rebuild it back to the .nb0 and flash. Do I have this right? Sorry for the multitude of questions.

Alternative Cooked ROMS?

I Successfully flashed my (Sprint) Treo 700wx with Ebag's example ROM and I'm wondering if anyone else out there has created a ROM using the Kitchen utility and would like to share their results?

So in order to do this. I put the files in the "ToAdd" folder and then create the text files with the same names in the "ToRemove" folder. Run the ToRemove batch file, then the ToAdd batch file. Then rebuild it back to the .nb0 and flash. Do I have this right? Sorry for the multitude of questions.


Yup, you got it. :thumbsup:

Creating the text file names in the \ToRemove\ is optional, you can also drag/drop the files (NOT the folders, but the files inside the folder) into the \ToRemove\ directory. Whichever is easier and makes more sense for you. The script that adds\deletes won't recognize folders in the \ToAdd\ and \ToRemove\ folders (which is actually something I like, since then I can have multiple folders in there for different testing purposes or historical purposes).

Okay. Sorry again, but I am having trouble. The batch files do not seem to be working for me. I can run the first one on the .nb0 file and get the imgfs, but it does not create the .nb0 original folder. So when i try to rebuild the ROM it says it can't.

The second problem is that I can remove the stuff just fine, but it does not want to add the two .dll's I want to put in.

So as a last ditch effort, I just used the tools located in the \Tools\ROM\ folder via a command prompt. It all went well there. I got the imgfs files out of the .nb0. I deleted the 4 files and added my 4 files back. However, after doing this I dumped the ROM to see if the changes got made. The graphic files updated fine. The dll's though, are in the ROM, but don't get extracted to folders like the rest of the dll's.

Can I just dump the ROM and replace the files I want in the dump and then just rebuild it all.

Also, in the SD Updater download, acoording to waffles, I need to delete the firmware.bin file. I am assuming I also need to ditch the firmware.md5. Will I need a new .md5 for the .nb0 file? Also, do I need to remove the firmware files in the 2577 folder. Alternatively, could waffles provide an SD updater sip file that includes only what I need to flash my VZW phone.

Thanks for all the help fellas and for bearing with me through this. It is much appreciated.

Okay. Sorry again, but I am having trouble. The batch files do not seem to be working for me. I can run the first one on the .nb0 file and get the imgfs, but it does not create the .nb0 original folder. So when i try to rebuild the ROM it says it can't.


The first batch script should move the .nb0 file out of \Cooking\ and into \Cooking\Original\. If it's not doing that, check to make sure that you've got everything in the right places.




The second problem is that I can remove the stuff just fine, but it does not want to add the two .dll's I want to put in.

So as a last ditch effort, I just used the tools located in the \Tools\ROM\ folder via a command prompt. It all went well there. I got the imgfs files out of the .nb0. I deleted the 4 files and added my 4 files back. However, after doing this I dumped the ROM to see if the changes got made. The graphic files updated fine. The dll's though, are in the ROM, but don't get extracted to folders like the rest of the dll's.


Files you add will not be added as modules (in a folder in the dump). Modules are special, they can't be replaced directly or updated. The best you an do is remove (delete) a module and re-add it as a normal file.

So yor DLL's will show up in the dump folder, and not in their own folder as a module.



Can I just dump the ROM and replace the files I want in the dump and then just rebuild it all.


You can. I don't recommend it however due to errors and odd behaviour I've gotten.


Also, in the SD Updater download, acoording to waffles, I need to delete the firmware.bin file. I am assuming I also need to ditch the firmware.md5. Will I need a new .md5 for the .nb0 file? Also, do I need to remove the firmware files in the 2577 folder. Alternatively, could waffles provide an SD updater sip file that includes only what I need to flash my VZW phone.


You shouldn't need the firmware.md5. The md5 files are a checksum that the updater uses to check the filesize and date of the files it's flashing, that's why the ROM file does not change in date or file size even when you modify it. So no, you don not need a new .md5 for the .nb0 file.

I don't know the answer to your question about the firmware files in the 2577 folder. Waffles may know.

Has anyone got Opera Mobile 8.65 to work with the cooked rom? it seem to have some problems with the "options" screen, can't drag up/down and "full screen"..

Has anyone got Opera Mobile 8.65 to work with the cooked rom? it seem to have some problems with the "options" screen, can't drag up/down and "full screen"..


I could never get it to work right with the stock ROM. *shrug*

Post a new comment

Post a new comment
Close
Cases
Chargers & Cables
Bluetooth
Batteries
Cradles
Screen Protectors
Car Kits
Memory Cards