Rom customization

[dmitrygr]

hey, so it appears i found how to edit the full rom (as opposed to just the "overflow" that i edited previously)

Overflow is the ROM that gets copied to RAM and lives there after hard reset
This now is the ROM ROM (where Datebook and drivers live).. this allows for a lot of possible customizations.


Furthermore, unlike previous edits, where i used palm Inc.'s updater, this is purely my code, so i can distribute this freely

Cool huh?

[_Em]

Good to hear Dmitry... when do we get to beta test it? :)

[dmitrygr]

beta test?

[juggernaut#2]

C´mon, when do we get this to play ? :)

[dmitrygr]

well...i just killed a TX by flashing it as battery ran out... so maybe as soon as i add a check requiring external power before flashing :-)

BUT, i did manage to throw away half the rom, and add netfront and small fonts and clie organizer on my TX :-)

[Church Punk]

cool? ??? of course! if thats not cool then i dont know what cool means anymore :D

but i would rather play with it until dmitry says its safe to do so... so ill be reading here for a while :)

[dmitrygr]

well...it's not too unsafe...as long as you do not remove something like the DAL or the DMA driver :-)

[_Em]

I'm thinking we should at least compile a post outlining what is NOT safe to remove. What is the bare minimum required to enable a person to boot their TX up and flash it?

[dmitrygr]

all but apps...datebook, calc, can be removed...etc....
anythign might be safe...ask

[Clie Luvr]

Will I be able to (or should I ) remove these apps?

Docs to Go
SMS
Dialer
Language packs
Media
ActiveSync
World Clock

[vovka1965]

Docs to Go is not in ROM

[dmitrygr]

yes, u can

Will I be able to (or should I ) remove these apps?

Docs to Go
SMS
Dialer
Language packs
Media
ActiveSync
World Clock

[dmitrygr]

GRRRRRRRR, why is this the only time nobody on eBay is selling TXs with broken screens?


Anyone has a TX they want to sell for cheap [i swear it's for a good cause]?
i cannot finish this until i have another TX.

[b]EDIT: I bought a new TX from eBay for $173.00 :(

very good news: the space in the ROM is quite free, so there is a lot of freedom ;-)

[pixelpainter]

I want to know more about the clie organizer and how that works on a tx?

[Church Punk]

freedom is what we need, worth fighting for... even dying for -man, to much philosophy classes :D -

looking forward to this!

[phreakonaleash]

Does this leave us with more cache?? :D

[dmitrygr]

well, if you make the rom smaller - yes

[_Em]

I guess the question is: is that possible? We found out with the overflow section that that partition was a fixed size, and wouldn't function reliably if that size was changed.

[BrentDC]

Wow this is really very good news, keep up the good work Dmitry :) Because I'd really like to get rid of a lot of useless ROM apps :)

[ftwitty]

The thought scares me............ if the expert can melt his Tx, what would an idiot like me do? :confused: :eek:

[dump71]

I'd be very happy to dump ROM apps if it gives me more dbcache!!

[alt236]

I'll be aiming for a rom without:
-Versamail (dont use it)
-Docs To Go (I install a later version anyway)
-Addit (obvious :p)
-The sample clips/images. (they just eat up space)
-The language packs. (I just use english)

[cyberdude]

Is it possible just to install our later version of d2g in ROM (I use 10)?

[_Em]

I'll also be deleting Expense, all the T-Mobile stuff, SMS, Phone, language picker, Dialer and Dial.

Plus, I'd replace Memo with ChronMemo, replace Prefs with PREFS, Handedness with the version that actually REMEMBERs your setting, Photos with TCPMP and Solitaire with Patience.

Then there's a few additions I think I'd make as well, including iSecur, NVBackup, and the various patches people have made to fix bugs in the OS.

[BrentDC]

I'd get rid of:

Addit (that is not really part of ROM, it just gets copied over, right?)
Expense
Versamail
All the Media default stuff
Language Packs
Solitaire
Quick Tour
Welcome

EDIT And I'd get rid of all that stuff Em just mentioned, and I forgot

I'd add:
Resco Explorer
NetFront (maybe)

:cool: :D

[cms]

well i guess this solves the "passwords that survive hard resets" issue

[cms]

I would put the files lib from the lifedrive and get rid of the stupid "favorites" app

[_Em]

Actually, I've been trying to figure out what to replace the Favorites app with -- I figure that the toggle feature is useful, so I'd like to double something launcher/file manager-like into that slot. I'm thinking Resco Explorer, except that RE keeps being upgraded. Maybe replace Favorites with FileZ?

If anyone has any suggestions of a file-related feature-stable bug-stable app that could fill the spot currently used by Favorites, I'd love to hear about it. Maybe iPhoneImitation ;)

[scottl]

Would this be done with an application like the old Jackflash (I think) that allowed us to peel out what we wanted to make more room or would it be a Dmitry ROM replacement that would have only the configuration/selection of apps he ultimately selects?

[dmitrygr]

i am making a jack-flash like app, except they let u remove applications as a whole, and only some. i will allow file-by-file removal with no restrictions (read: better read the manual before removing DAL.prc :) )

[dmitrygr]

The thought scares me............ if the expert can melt his Tx, what would an idiot like me do? :confused: :eek:


well, this is just because i am developing the app. If you knew how many devices i killed in process of making my apps, you`d never believe me. I will put in some safeguards when i release the app

[_Em]

...and Dmitry does insane things when developing, like ramping the CPU up to 1170MHz and using a flaky SD card as dynamic memory ;)

He likes to test things out to the extreme so the rest of us don't have to.

So Dmitry... will it be possible to reclaim freed up ROM space as DB Cache?

[dmitrygr]

yes, it will be automatic :-)

[cms]

Sweet! :D

Im guessing this will not be free though, what will the price range be?

[cms]

...and Dmitry does insane things when developing, like ramping the CPU up to 1170MHz and using a flaky SD card as dynamic memory ;)


When can we get Windows XP on our palms Dmitry? lol

[espc31]

I plan to go for minimal apps to see if my TX functions any better. I miss Jack sprat and flash. so this has been a long time need on the palm. Lately it seems Palm has been shoving apps down our throats.

[dmitrygr]

anyone feeling brave to run a little test app for me ? :rolleyes:

[cms]

Dmitry, watch this not appear on the 1src news like when you released your custom rom :D

That would be cruelishly funny :D

*...and im not brave enough >.<*

[_Em]

Well, unlike the custom ROM, this one doesn't contain other people's code (legally obtainable code, but still belonging to others). I think this will show up in the news pretty quickly when it is officially released.

[dmitrygr]

hope so...but for now i await a new TX

[I love my mom]

I'll test something on my old Zire31 if it's eligible :)

[_Em]

Unfortunately, I don't think a TX ROM editor will work on a Zire31 ;)

[dmitrygr]

well anything with nvfs will work, in theory

[John Stanley]

anyone feeling brave to run a little test app for me ? :rolleyes:
As long as you're reasonably sure it's not going to "brick" my TX, sure.

[dmitrygr]

for those who feel like testing for me (after i test on my new tx so that i do not kill someone else's tx) will need an sd card with at least 64MB free space...

[alt236]

On the other hand, will flashing the TX with the ESU return it to its default state?

[2XS]

if so, you made my day dmitry !!! :-)

[drwho]

Hi Dimitry
Sounds like it could be really good. You say that the dbCache will increase if the ROM gets smaller. I have a few questions.

1. My understanding is that roughly 7MB of the 20MB of DB Cache is locked and reserved for OS. How much of that do you envisage could be freed up if you stripped the ROM down to the bare essentials?

2. How will this new application work with UnCache? Could you move programs out from ROM into NVFS (instaed of deleting them), and then use unCache to stop them preloading?

[I love my mom]

You can copy apps out of ROM at will without any special program. But it's useless because you already have it in ROM :rolleyes: So this should fix that

[dmitrygr]

On the other hand, will flashing the TX with the ESU return it to its default state?

no. ESU update only updates the overflow area, not the real rom. But i can probably add an option to do a FULL bit-for-bit backup


1. My understanding is that roughly 7MB of the 20MB of DB Cache is locked and reserved for OS. How much of that do you envisage could be freed up if you stripped the ROM down to the bare essentials?


that is not correct. There is 32 MB ram, 6 MB is heap, so 26 is left, OS uses 15, leaving 11 for dbcache. Or something close to this.

I think the OS can be stripped down to ~ 8Mb, so that 18MB is left for cache


2. How will this new application work with UnCache? Could you move programs out from ROM into NVFS (instaed of deleting them), and then use unCache to stop them preloading?

copy to ram is possible now as is
this app can remove from rom
and then yes, it will not load unless in uncache list

[juggernaut#2]

as said before, this sounds very interesting. but will there be any backup option to restore the original state? i guess that´s what the ESU question was concerned with, too.

i´m not afraid, but i was using jackflash/jacksprat with my older devices and discovered once when selling such a device that no-one but a 1src member would take it with a modified ROM :)

[_Em]

ESU update only updates the overflow area, not the real rom. But i can probably add an option to do a FULL bit-for-bit backup.

I hope this answers your concern :) --although, I guess there'd have to be an option for a bit-for-bit restore as well.

[espc31]

I am willing to test your app on my TX. I have been able to recover my TX from just about any sitro so far...

[bluefishCFC]

Any chance this would work on a TE2.
Having been forced to use one for a few weeks, I can only hope it is possible to free up some DBCache on it some way.

Andy

[_Em]

From what I can gather, it is being designed for the TX, but MIGHT work on other NVFS devices. Maybe after he's got the TX code stable, he'll start testing against other targets.

[alt236]

I can't remember if the rom on the TE2 is flashable or not...

[drwho]

that is not correct. There is 32 MB ram, 6 MB is heap, so 26 is left, OS uses 15, leaving 11 for dbcache. Or something close to this.

I think the OS can be stripped down to ~ 8Mb, so that 18MB is left for cache

Thanks

One further question. If we can reclaim about 7MB, can that be split between the heap and dbCache, or is the heap size unchangeable. Extra heap would be really useful.

[_Em]

That's what UDMH is for ;)

[dmitrygr]

yes, to expand the heap into the cache, get udmh.
as for other devices support...the code currently supports any NVFS rom, then flash code supports TX's motherboard, but others can be added. But i do not see myself buying a T5 just now after just having bought a new TX.

[phreakonaleash]

What is the point of a backup? If you brick the device, I assume there would be no way to get in long enough to run restore on it...? :S
Maybe with some ugly gdb hack?

[dmitrygr]

well, no. if you bork the rom partition contents, you can still restore it using a stub my app will restore and a special cable :-)

[espc31]

Would the TX security update work to restore as well?

[espc31]

cancel that I guess if the palm never boots up you cant use the update...

[phreakonaleash]

well, no. if you bork the rom partition contents, you can still restore it using a stub my app will restore and a special cable :-)
I figured. Coolness...!

[cms]

:D Sweet!!! :D

[drwho]

That's what UDMH is for ;)
Except it seeems to make my sytem unstable. With UDMH enabled I was getting about 3 or 4 crashes a day. Without it, no crashes.

[dmitrygr]

OT: but your problem. works fine on all machines i've seen it on

Except it seeems to make my sytem unstable. With UDMH enabled I was getting about 3 or 4 crashes a day. Without it, no crashes.

[phreakonaleash]

I love UDMH. :) Made my device much more stable.

[juggernaut#2]

I didn´t mean a backup just in case you bork the device. I figure everything will go fine and you´ll live happily with your custom tailored ROM, but one day you´ll try to sell that TX or give it to your spouse or whatever, and then you´ll need some means of putting it into the original state - for one, ´cause not everyone will buy a "tampered-with" device, second, you might have put some regged software into your ROM and don´t want to give that away, too (at least you´re not allowed to, right).

I had that problem with a m505 once - used jackflash/jacksprat heavily and lost my backup ...

[phreakonaleash]

I assume that the initial backup ROM could be saved somewhere (thus restored later) just like any other backup

EDIT: Why would your spouse care if you played with the ROM?

[alt236]

What is the point of a backup? If you brick the device, I assume there would be no way to get in long enough to run restore on it...? :S
Maybe with some ugly gdb hack?

There is also the possibility of someone wanting to send his palm to be serviced. I doubt that palm would look favorably at the ROM mod....
Or if you want to sell it, you might want to return it to its factory default.

[phreakonaleash]

If you are doing a ROM mod, chances are you've voided the warranty somewhere else... ;)
Good point, alt236... :)

[alt236]

Its not the mod that counts, its how well you can hide it! :p

[phreakonaleash]

niiiice :)

[jghanisco]

And beyond that, a good number of us have had our TXs for longer than a year, and don't have a warranty left anyway! So you're either ready to buy something new if it dies, or you purchased it with your Amex card, and you'll get to replace it with their warranty guarantee! Of course, some may argue that is illegal since we did something not allowed, so we'll leave it at that!

If you are doing a ROM mod, chances are you've voided the warranty somewhere else... ;)
Good point, alt236... :)

[juggernaut#2]

Why would your spouse care if you played with the ROM?
My spouse does :)

[phreakonaleash]

My spouse does :)
:) ah too bad :)

[RazrTX]

anyone feeling brave to run a little test app for me ? :rolleyes:

Sure, what the heck, I run a few TXs and the one that fell into a can of paint might be a good candidate ;-)

Razr

[thenrik]

I'll start looking for a TX on Craigslist and if successful will be glad to beta test.

Tom

[BrentDC]

I want to know more about the clie organizer and how that works on a tx?

I didn't even know Clie Organizer worked on the TX. Not to get OT, but Dmitry, could you explain more?

[dmitrygr]

I didn't even know Clie Organizer worked on the TX. Not to get OT, but Dmitry, could you explain more?


glad to explain, but you already did. The question was "does it work", the answer was "Dmitry". :D

[dmitrygr]

anyways i got my new tX, but it has a different flash chip (who knew they made more then one model of motherboard?)... so i'll need someone who is feeling VERY lucky to test the code for the other flash chip. Requirements:

1. TX which verifies as having the right kind of chip
2. SD card with at least 64 MB space
3. Some free time
4. Love for living on the edge, lack of love for your TX, or extreme amount of luck

[espc31]

How do I verify my chip Model?

[dmitrygr]

1. you can open your device and see if you have a chip that says "MX" on it. If so, you have the kind of device I do NOT need testers for.
2. I can make a software tool to test it...

[espc31]

Welll I wish I needed to know the chip model when I replaced my digitizer with a new glass one (digitizer works a thousand times better now if you must know) and after fighting with the wire ribbon for about an hour or so and don't wish to go thru that again so if you have some kind of "get info" software to verify it, it would greatly be appreciated.

[dmitrygr]

There are [at least] two hardware revisions of te TX, one of which has flash, and one does not. The one that does not is newer and bears the ROM timestamp of "Sun 12/04/2005 11:23 PM". This ROM timestamp is not accessible from within PalmOs, so do not run and test your device yet. The older ones do have flash, and bear the timestamp of "Tue 09/13/2005 08:32 PM". Curiously the Blazer app in ROM of those with older timestamp is corrupt (cause for crashes maybe?). Now before I release the app to test to see if you have flash, and thus open a new [more expensive?] segment of the market for TXs, does anyone want to trade TX's with me? Mine has no flash, but besides that is like new? Obviously until I get a flashable TX, I cannot complete the flashing app...

[Pgr]

I have a TX, and a friend of mine has another which seems a bit different.

There is an external difference - I don't know if this could be a sign of the internal difference that Dmitry is talking about. Notice the shape if the white label in the back:

TX Version 1 - like the one my friend has
http://pwp.netcabo.pt/gorod/TX2.jpg

TX Version 2 - like the one I have
http://pwp.netcabo.pt/gorod/TX1.jpg

(I couldn't find a picture like this online, so I just photo-edited the first one roughly to show you the general idea).

The reason I feel this could be the sign of internal difference is because I've seen different behaviors from these two Palms - namely, Dmitry's FastDIA installed easily in mine, and not at all in my friend's TX.

So, maybe I'm just speculating here, or maybe Dmitry has already written an app to tell the difference... :)

[ProfJonathan]

Mine's one of the former, and I too had difficulty installing FastDIA until Dmitry posted instructions. I'm following this thread with interest. {ProfJonathan}

[scottl]

The one that does not is newer and bears the ROM timestamp of "Sun 12/04/2005 11:23 PM".
...
The older ones do have flash, and bear the timestamp of "Sun 12/04/2005 11:23 PM".
:confused: So Dmitry... which of these time stamps is the "older" one? ;)

[alt236]

@dmitry

The timestamps you provided for the two versions are identical :)

[wozofoz]

...namely, Dmitry's FastDIA installed easily in mine, and not at all in my friend's TX...


I have Version 1 like your friend and FastDIA installed easily in mine :confused:

All the best, woz of oz

[alt236]

As I recall, having UDMH made the installation easier, so the difference might be there.

[The New No. Two]

Don't know if it's relevant (or even accurate), but the freeware app PalmInfo 1.1 shows "Flash ROM: Not Present" on my T|X.

It also shows the ROM version as v.5.4.9r40.

The back label has the square white section.

Find PalmInfo at www.freeware-palm.com.

[dmitrygr]

oops, the other timestamp is "Tue 09/13/2005 08:32 PM"

[dmitrygr]

Don't know if it's relevant (or even accurate), but the freeware app PalmInfo 1.1 shows "Flash ROM: Not Present" on my T|X.


i doubt that app has any idea what it's talking about...TX has at least one type of flash-ROM and at least half of it is flashable (the nand part - overflow that my old rom edited). :)

[The New No. Two]

i doubt that app has any idea what it's talking about...TX has at least one type of flash-ROM and at least half of it is flashable (the nand part - overflow that my old rom edited). :)

Figures. What about the ".6" shortcut? Mine shows "9/4/05,2:38 PM".

[juggernaut#2]

that´s the manufacturing date of the whole thing (the TX) which is not neccessarily the same as the one of the chip. But maybe that´s a clue: If the whole thing is manufactured before X, it CANNOT contain the newer chip. If it´s not, you don´t know more, ´cause palm could have easily manufactured the TX with an old chip found somewhere in the closet :)

[dmitrygr]

So anyone willing to trade?

[cyberdude]

So anyone willing to trade?
I have a feeling that most of the people who are reading this thread are waiting to flash their romm with your app when it comes out. Therefore you may not find any takers here. A new thread may be much more successful.


Just my 0.02

[dmitrygr]

Well, unless someone does trade, there will be NO such app :)

Anyways here you go, guys. Run this on your device. It will determine if you have a supported flash chip. If it says "Flash" - you win. If it says "Unknown" does not necessarily mean you lose, perhaps there is a third batch of T|Xs out there. Anyways I need someone whose device says "Flash" To trade with me.

App to test: => [LINK (http://www.palmpowerups.com/priv/RomFlashCheckV3.prc)] <=


Also feel free to run this on any other NVFS devices you have (except the treos please). Tell me if any of those other devices say "Flash".

[The New No. Two]

Mine says "Unknown".

[dmitrygr]

Well, my ROM-tX has the rectangular white serial number label(v2), while the Flash-tX had the folder-shaped white serial number label(v1) on the back...perhaps there is a correlation?

Versions referred to are as posted here (http://www.1src.com/forums/showpost.php?p=1016717&postcount=87)



@Pgr: thanks for pictures...and try to trade TXs with your friend :-)

[ProfJonathan]

Well, unless someone does trade, there will be NO such app :)

Anyways here you go, guys. Run this on your device. It will determine if you have a supported flash chip. If it says "Flash" - you win. If it says "Unknown" does not necessarily mean you lose, perhaps there is a third batch of T|Xs out there. Anyways I need someone whose device says "Flash" To trade with me.

App to test: => [LINK (http://www.palmpowerups.com/priv/RomFlashCheck.prc)] <=


Also feel free to run this on any other NVFS devices you have (except the treos please). Tell me if any of those other devices say "Flash".

Dmitry,

I'm installing the app now and will report when it runs. Question, though: assuming a flash-containing TX owner wanted to trade (and I might), what functionality would be lost by switching to the non-flash version? The ability to use your to-be-released app? The ability to upgrade to another PalmOS? Thanks. {ProfJonathan}

[ProfJonathan]

Darn, I'm an "unknown," and I have the folder-shaped sticker. {ProfJonathan}

[Pgr]

Mine is V2 and the utility says "Unknown".

Unfortunately, I can't test it on my friends' V1 because his digitizer is totally broken, it is simply unusable.

But if other people keep posting their results, we can surely confirm or break this correlation in no time...

EDIT: oops, correlation is now declared broken, by ProfJonathan, while I was typing... :)

[alt236]

Mine is also "Unknown" and its the folder type (v1).
I bought mine about 2 years ago BTW.

Edit: See http://www.1src.com/forums/showpost.php?p=1016813&postcount=119

[cyberdude]

Mine is also unknown and the folder type label. I also bought mine about 2 years ago.

[_Em]

My T|X (folder label) says "Unknown" too. ManufDate (latest version) gives it a date of Nov 29, 2005.

[cyberdude]

OOPS....i uploaded the wrong file, here is a correct checker: http://www.palmpowerups.com/priv/RomFlashCheckV2.prc
got this message when I clicked on that link.

This file has been deleted.
Reason: Deleted by uploader.

Scratch that - I got it.

[dmitrygr]

Everyone, please recheck your devices...

[cyberdude]

Everyone, please recheck your devices...
I got an error.

Assert "flashCanControlModule(state)" failed at MainProg.c:148.

then my device reset.

[strakosko]

Worked!
mapAt=0x00000015
All done!
Mapped at 0x00000015
Flash type "Intel" detected.
8 MB flash with 128 KB block
No unique ID found
Dumping...

[dmitrygr]

that means you do not have flash :-)

[dmitrygr]

Worked!
mapAt=0x00000015
All done!
Mapped at 0x00000015
Flash type "Intel" detected.
8 MB flash with 128 KB block
No unique ID found
Dumping...



you have flash, congrats...

[cyberdude]

that means you do not have flash :-)
Darn!!!!! I really wanted to try this app out when you finished it.

[strakosko]

so r u trading?

[dmitrygr]

I'll trade with you :-)

anyways, here is a better checker, try it please...


http://www.palmpowerups.com/priv/RomFlashCheckV3.prc

[strakosko]

that url does not work for me...

[alt236]

OK.

I got the following:

Worked!
mapAt=0x00000015
All done!
Mapped at 0x01500000
Flash type "Intel" detected.
8 MB flash with 128 KB block
No unique ID found
Dumping...
:):)

Something funny, my and strakosko's 'Mapped at' addresses are different although I suspect a typo. 0x00000015 is a bit low :).

Out of curiosity dmitry, do you want the rom dump? And where is it saved?

[_Em]

Mine failed using v2; can't download v3 yet.

[dump71]

I tried v2, and it just said "unknown".

[dmitrygr]

unknown means no flash.
mapped at addresses are irrelevent and somewhat random.

v3 checker tell anyone "flash"?

[dmitrygr]

ok v3 tester reuploaded..should work now


http://www.palmpowerups.com/priv/RomFlashCheckV3.prc

[sgosnell]

V3 on a Lifedrive just says "ROM", FWIW. V2 crashed and caused a reset.

[Pgr]

V3 checker tells me "ROM". I suppose this means not-flash... :(

[espc31]

Mine Said "ROM" too.

[_Em]

My TX just says ROM on v3. That can't be right, can it?

[dmitrygr]

why can't it?

[strakosko]

it says "Flash" on my TX

[_Em]

I'd be interested to hear results from everyone regarding what happens if you run ManufDate... Dmitry has stated that only the first run or two of TXes have the NOR Flash, and all following devices are all mask ROM (which, incidentally, prevents the memory corruption bug that killed my first two TXes).

[Maverick_[GER]]

RomFlashCheckV3 says "Flash" on my TX


timestamp (:shortcut: .9) returns "Tue 09/13/2005 08:32 PM"
jaPalmMade says "Tuesday, 20 Sep 2005"

[FerdFerd]

My TX, purchased in December, 2005, says ROM. jaPalmMade says it was manufactured on Tuesday, November 1, 2005.

[alt236]

Mine (a flash) was made on Saturday, 1 October 2005.

[dmitrygr]

So who's trading with me?

[ftwitty]

I'm fairly certain my Tx was one of the first manufacturered as I bought it the first date it was available; but I am curious what PalmMade would say. Where would I find such an application?

[ProfJonathan]

Sorry, Dmitry, mine was a ROM rather than a Flash, so I can't trade with you. Good luck finding a buddy, and I look forward to seeing your new project finished. {ProfJonathan}

[cms]

CRAP! Mine is a ROM too... bummer...

JaPalmMade shows that my palm was made: Sat, Aug 26 2006

I was thinking about getting a centro in the future anyways... (my Digitizer is getting worse and worse on this TX)

[cms]

I'm fairly certain my Tx was one of the first manufacturered as I bought it the first date it was available; but I am curious what PalmMade would say. Where would I find such an application?

Get JaPalmMade here: JaPalmMade (http://www.nexave.de/forum/index.php?page=Attachment&attachmentID=6102&h=96235facd07171260cbaf2f3a7d5a0ac3a7c7459)

[FerdFerd]

I'm fairly certain my Tx was one of the first manufacturered as I bought it the first date it was available; but I am curious what PalmMade would say. Where would I find such an application?The link is in the first post of this thread (http://1src.com/forums/showthread.php?t=120103).

Edit: The link in that post is dead. Sorry. But I see that while I was composing this, you got a live pointer anyway.

[pokeypda]

My 2006 TX reports ROM, from the replies so far the FLASH models seem rare. Small market.

[dmitrygr]

well i'd do it just for me :-) it's fun project

[Frink]

Mine says 'Flash'

jaPalmMade says Saturday, 1 Oct 2005.
It has the folder type label and is the multi-language model.

I'd rather not trade, sorry, also because I live in Europe.
I'm willing to test if it would be 'reasonably safe'

[juggernaut#2]

Mine says "ROM". It has the folder-type label. Multi-language TX, of which PalmMade says that it was made 12.12.2005.

what a pity... anybody willing to trade a second time ? :)

[alt236]

So it looks like the swich happened around November 2005...

EDIT: Fixed the date :)

[Gwidion]

Mine says "ROM". It has the folder-type label. Multi-language TX, of which PalmMade says that it was made 12.12.2005.

what a pity... anybody willing to trade a second time ? :)
Mine says "Flash" an my Device is 21.Dec.2005
I think, there is something not correct, 13 days difference and juggernauts has a "ROM" VErsion and me a Flash?
We discuss is now at nexave.de, but there is no idea, why our TX are different.

[ziggy]

Mine is ROM, device is from Feb 6, 2006.

[cyberdude]

I'd be interested to hear results from everyone regarding what happens if you run ManufDate... Dmitry has stated that only the first run or two of TXes have the NOR Flash, and all following devices are all mask ROM (which, incidentally, prevents the memory corruption bug that killed my first two TXes).
V3 says "ROM" and japalmMade returns 11/23/2005. ManufDate returns 11/23/2005 also. jaPalmMade is a lot easier to use.

[robitaille88]

Guys, the date JaPalmMade and ManufDate is only the manufacture date (when the pieces were put together).

This is NOT the ROM timestamp.

To easily find your rom timestamp, go to any text entry box, such as Find of Memopad, and enter: :shortcut: .9

That will give you the ROM timestamp and it WILL correspond to one of the two dates Dmitry posted at http://www.1src.com/forums/showpost.php?p=1016701&postcount=86


BTW, mine is the new version, with ROM and the rectangular sticker, with the ROM timestamp of "Sun 12/05/2005 11:23 PM"

[Ohappydaye]

Yippee! Mine says "Flash" and I purchased mine Oct 2005. I'm ready to try this out! :D

Edit: And it has the folder shaped sticker on the back...just in case anyone is wondering.

[ProfJonathan]

Guys, the date JaPalmMade and ManufDate is only the manufacture date (when the pieces were put together).

This is NOT the ROM timestamp.

To easily find your rom timestamp, go to any text entry box, such as Find of Memopad, and enter: :shortcut: .9

That will give you the ROM timestamp and it WILL correspond to one of the two dates Dmitry posted at http://www.1src.com/forums/showpost.php?p=1016701&postcount=86


BTW, mine is the new version, with ROM and the rectangular sticker, with the ROM timestamp of "Sun 12/05/2005 11:23 PM"

Oddly enough, mine shows the 9/13/05 date but shows ROM in Dmitry's v3 test. {ProfJonathan}

[juggernaut#2]

We weren´t trying to get the ROM date, we were just trying to tie down ´till when the old chip was used in manufacturing.

On the .9 stroke mine says "Tue 09/13/2005 08:32 PM", and just like profjonathan posted, that would make my device comply to dmitry´s needs, but his checker tool said "ROM" ...

[wozofoz]

:confused: Ok, I've Googled 'palm rom date shortcut' and get conflicting results.
Some say .9 is ROM date and .6 is Manufacture date
Some say .6 is ROM date and .9 is Manufacture date

I will do both right now on my TX which has the white tab on the back. My results:

.9 = Sun 12/04/2005 11:23 PM
.6 = 09/04/05,2:38 PM

Although I have my time set to Australian standard format which is d/m/y I think this is m/d/y format.

If both these shortcuts are relevant (and I don't know if they are) the time format is not important because obviously the ROM must have been made before the TX was put together.

Which means ROM date must be .6
Manufacture date must be .9

Can anyone explain what is going on :confused:

All the best, woz of oz

[technical1]

Dmitry, what to do if I used your custom ROM & don't have the Palm update to bring it back to original...

[cyberdude]

Guys, the date JaPalmMade and ManufDate is only the manufacture date (when the pieces were put together).

This is NOT the ROM timestamp.

To easily find your rom timestamp, go to any text entry box, such as Find of Memopad, and enter: :shortcut: .9

That will give you the ROM timestamp and it WILL correspond to one of the two dates Dmitry posted at http://www.1src.com/forums/showpost.php?p=1016701&postcount=86


BTW, mine is the new version, with ROM and the rectangular sticker, with the ROM timestamp of "Sun 12/05/2005 11:23 PM"
mine is the folder type sticker and the timestamp is
.9 = 9/13/2005 8:32 PM.
.6 = 9/4/05

Dmitry's tool V3 says ""ROM".

[juggernaut#2]

congrats CD, you got the same one as I have :)

[dmitrygr]

My tool doe snot check dates...it really checks the chips...so it has the final word on whether the device has flash or not.


Anyways wake me up when someone decides they want to trade...

[cyberdude]

congrats CD, you got the same one as I have :)
Only problem is that means neither of us can use this new app. :(

[strakosko]

I can trade with you dmitrygr ( mine TX is "Flash" ). Pls let me know...

[Church Punk]

if you trade your TX, and the app comes out, then how would you be able to use this app if you just traded your Flash TX with a ROM TX? :rolleyes:

mine is ROM btw

[strakosko]

At least I will help the cause. Palm has made it already bad - no new handhelds for ages now. And I am not using my TX that often anyways although I like it very much - no time.

[lichan]

My E2 says "Flash" with a manufactured date of Sunday, Mar 20, 2005.

[dmitrygr]

I can trade with you dmitrygr ( mine TX is "Flash" ). Pls let me know...


PM me please, we can further discuss this deal. Perhaps i can give you a few extras to make it up (Cradle, some software?)




My E2 says "Flash" with a manufactured date of Sunday, Mar 20, 2005.



un-fu cking-believable!!!!!
i will need you to run a few diagnostic apps for me, perhaps my app can support E2s as well. PM me here for more instructions...

[_Em]

Thought I'd add my :shortcut:.6 and :shortcut:.9:

:shortcut:.6: 9/4/05 2:38 pm
:shortcut:.9: 09/13/2005 08:32 PM

These are both quite a while before the November manufacture date of my Palm.

[Another Michael]

My T5 says "ROM" when starting the diagnostic program.

[lemmyslender]

I get a ROM date of 9/13/05 and a Mfg date of 11/2/05. App indicates "ROM"

[scottl]

:mad: CRAP! I REALLY wanted this puppy!

Sticker: Rectangular
RomFlash V3: ROM
jaPalmMade: Wednesday, Aug 9, 2006
:shortcut:.6: 9/4/05 2:38 pm
:shortcut:.9: Sun 12/04/2005 11:23 PM

[dmitrygr]

I am sure this app, once completed, will open up a market for Flashable TXs :-)

[strakosko]

dmitrygr I have sent you PM on icq...

[dmitrygr]

try PM here instead...

[Gwidion]

try PM here instead...
You've got a message ;)

[FerdFerd]

Thought I'd add my :shortcut:.6 and :shortcut:.9:

:shortcut:.6: 9/4/05 2:38 pm
:shortcut:.9: 09/13/2005 08:32 PM

These are both quite a while before the November manufacture date of my Palm.These are exactly my data too. (The .9 result also tells me that the day was TUE.) November 1, 2005 is the reported manufacture date for mine. And to repeat, mine is ROM.

[Wolfgang]

Can those who get from RomFlashV3: ROM post the exact type of the flash/rom chip in their TX? Then we would be able to look up the datasheets from the manufacturer. Somehow I doubt it that Palm really used chips which are only partly (overlay) flashable.

[_Em]

Already covered that with Dmitry... unfortunately, Palm switched from NOR flash ROM to a masked ROM on the later builds. The upside is that it prevents most of the memory-based bricking bugs from having any effect on the later TXes.

[ftwitty]

Get JaPalmMade here: JaPalmMade (http://www.nexave.de/forum/index.php?page=Attachment&attachmentID=6102&h=96235facd07171260cbaf2f3a7d5a0ac3a7c7459)
Thanks.......... Sep 8, 2005 FLASH

[ftwitty]

I am sure this app, once completed, will open up a market for Flashable TXs :-)
Do I hear any bids for my FLASH ROM Tx? :D :rolleyes:

[dmitrygr]

sweet, i think i found someone to trade with... I'll get coding as soon as I get my new flashable TX

[gahenton]

So I downloaded the app and it says that my TX was manufactured Thursday, Oct 13 2005. Is this good? How do I get the flash program?

Thanks Gerry

[=Froggy=]

Crap! :( Mine says "ROM"...
I was soooo excited to see the topic at first. What a disappointment... :( Oh well, at least I had my fun playing with the overflow... :)

[scottl]

Palm switched from NOR flash ROM to a masked ROM on the later builds. The upside is that it prevents most of the memory-based bricking bugs ...Is there a chance a FLASH based unit would become less prone to those memory issues if we peeled apps out of the ROM? Then it's worth trading a later (more "stable") unit for a memory whacked unit, right? Wrong? :confused:

[phreakonaleash]

Are ROM devices going to be impossible to reflash then? :(

[dmitrygr]

pretty much

[juggernaut#2]

So I downloaded the app and it says that my TX was manufactured Thursday, Oct 13 2005. Is this good? How do I get the flash program?
it´s not the date that counts but whatever dmitry´s checker tool says. for this read further down, download, install and start it.

[The New No. Two]

:mad: CRAP! I REALLY wanted this puppy!

Sticker: Rectangular
RomFlash V3: ROM
jaPalmMade: Wednesday, Aug 9, 2006
:shortcut:.6: 9/4/05 2:38 pm
:shortcut:.9: Sun 12/04/2005 11:23 PM

Sticker: Rectangular
RomFlash V3: ROM
jaPalmMade: "Thursday, 2006 Apr 6"
:shortcut:.6: 9/4/05 2:38 pm
:shortcut:.9: Sun 12/04/2005 11:23 PM

[ftwitty]

Are ROM devices going to be impossible to reflash then? :(
This explains why there has been no upgrade for the Tx............ and won't be either.

But is the ROM OS the same as the original FLASH OS?

[dmitrygr]

This explains why there has been no upgrade for the Tx............ and won't be either.

But is the ROM OS the same as the original FLASH OS?


very close..

[alt236]

Any idea what the differences are (apart from the blazer problem)?

[ftwitty]

Any idea what the differences are (apart from the blazer problem)?
Does this mean that the Tx ROM OS doesn't have a Blazer problem?

[alt236]

Does this mean that the Tx ROM OS doesn't have a Blazer problem?

According to this post (http://www.1src.com/forums/showpost.php?p=1016701&postcount=86) by dmitry, the earlier ROM version has a currupted Blazer app.

So one of them could potentialy be prone to crashes or other stuff :).

Now, I tried extracting the images of my Blazer a while ago and PFCD craps out, so that might be it.

[dmitrygr]

no, not that. the zip file containing it fails the CRC check, that is how i guessed it is corrupt..

[alt236]

I guessed thats how you figured it out.
I'm just saying that I got a probable corruption a few days back and I was curious :)

[drc54]

Just to add, my TX bought here in Singapore:
:shortcut:.9 Tue 09/13/2005 08:32 PM
:shortcut:.6 9/4/05, 2:38 PM
RomFlash: FLASH

So maybe many more flashable TX's are outside the US :)

[dmitrygr]

can someone go other this tread and put together the following two pieces of info?

1. the LATEST manufactured Tx to have flash
2. The REALIEST manufactured Tx to have ROM

[cyberdude]

can someone go other this tread and put together the following two pieces of info?

1. the LATEST manufactured Tx to have flash
2. The REALIEST manufactured Tx to have ROM
Unfortunately not everyone provided all test data or even the same test data.

Aquick analysis shows 8 positive for "Flash" with version 3 of your app. All of the Flash Txs that provided .9 data had a date of 9/13/05, but so did most of the ROM TXs. The earliest TX according to jaPalmMade that has Flash was made 9/8/05.

[Ohappydaye]

Unfortunately not everyone provided all test data or even the same test data.

Aquick analysis shows 8 positive for "Flash" with version 3 of your app. All of the Flash Txs that provided .9 data had a date of 9/13/05, but so did most of the ROM TXs. The earliest TX according to jaPalmMade that has Flash was made 9/8/05.


I just installed jaPalmMade and my TX is said to have been made 9-6-05 and Dmitry's v3 romchecker says I have flash.

[cyberdude]

I just installed jaPalmMade and my TX is said to have been made 9-6-05 and Dmitry's v3 romchecker says I have flash.
That makes yours the earliest and Gwidion's the latest to have Flash (12/21/05 according to jaPalmMade). And , unfortunately, mine is the earliest to have ROM - 11/23/05 according to jaPalmMade.

[Ohappydaye]

That makes yours the earliest and Gwidion's the latest to have Flash (12/21/05 according to jaPalmMade). And , unfortunately, mine is the earliest to have ROM - 11/23/05 according to jaPalmMade.


Yayyy! I'm young again! :p But on a serious note, this is OT, but it makes no sense to me. Why would Palm put out two different ROMs (flash and non flash) during the same time period? Why wouldn't they continue to make them all flash? I guess there must be some financial incentive to doing so. :rolleyes:

[_Em]

It's called having multiple factories and using up inventory :)

FWIW, my TX is a multilanguage. That's the one thing we didn't add to the mix.

[Ohappydaye]

It's called having multiple factories and using up inventory :)

FWIW, my TX is a multilanguage. That's the one thing we didn't add to the mix.
Oooooh, I see. Well that makes me see things in a less than favorable light.
:(

[dmitrygr]

Oooooh, I see. Well that makes me see things in a less than favorable light.
:(


all of mine have been too...i am not sure there is a non-multilanguage TX....
they all ask for language at hard reset...

[FerdFerd]

And , unfortunately, mine is the earliest to have ROM - 11/23/05 according to jaPalmMade.Mine is ROM too and beat yours to the manufacturing bench by about three weeks - 11/1/2005. Not that this is any consolation to either of us, but it might further narrow the temporal window of interest.

[vovka1965]

Mine says
"This device was manufactured on
Friday May 25, 2007"

What does that mean? I am not sure I followed this thread fully..

[vovka1965]

Mine says
"This device was manufactured on
Friday May 25, 2007"

What does that mean? I am not sure I followed this thread fully..
and RomChecker says
ROM

Does that mean that I would not be able to use ROM customization?

[juggernaut#2]

yes

<now long enough>

[alt236]

all of mine have been too...i am not sure there is a non-multilanguage TX....
they all ask for language at hard reset...

I thought that the only difference between the US and International models was the inclusion of a dual-voltage charger and an assortment of international plugs.

There was so S/W difference.

[BrentDC]

I just got a new(er) unit back from the repair center, and JaPalmMade says "March 31, 2006", and RomFlash V3 says "ROM". :(

[Frink]

Apparently there's a 1047NA (North America) and a 1047ML (Multi Language) version of the TX. There is a short discussion about it here: http://forum.brighthand.com/showthread.php?t=98137, but nobody seems to know the exact differences.

For statistics:
RomFlashCheckV3: Flash :)
jaPalmMade: Saturday, 1 Oct 2005
:shortcut:.9: Tue 09/13/2005 08:32 PM
:shortcut:.6: 9/4/05, 2:38 PM
Other: Multi Language, 'Dmitry's T|X2 ROM'

[cyberdude]

Apparently there's a 1047NA (North America) and a 1047ML (Multi Language) version of the TX. There is a short discussion about it here: http://forum.brighthand.com/showthread.php?t=98137, but nobody seems to know the exact differences.

For statistics:
RomFlashCheckV3: Flash :)
jaPalmMade: Saturday, 1 Oct 2005
:shortcut:.9: Tue 09/13/2005 08:32 PM
:shortcut:.6: 9/4/05, 2:38 PM
Other: Multi Language, 'Dmitry's T|X2 ROM'
The latest Flash is still Gwidion's (12/21/05)
The earliest ROM is FerdFerds (11/1/05)

so for almost 2 months so far they were both being manufactured?

[alt236]

Any idiea who is the OEM for the TXs?

[woohooo]

RomFlash V3: Flash
jaPalmMade: Monday, Sep 26 2005

[John Stanley]

These are exactly my data too. (The .9 result also tells me that the day was TUE.) November 1, 2005 is the reported manufacture date for mine. And to repeat, mine is ROM.
VERY interesting...

Same .6/.9 date/time pairs here (9/4/2005 2:38pm and 9/13/2005 8:32pm).

BUT, according to jaPalmMade and RomFlashCheckerv3, my TX was made Sept 6, 2005 and is FLASH.

Obviously, you can't tell if you have ROM or FLASH from the .6 or .9 strings.

Also, the string reported by jaPalmMade can't be 100% right because my .9 date lies one week -after- the jaPalmMade date....

[cyberdude]

VERY interesting...

Same .6/.9 date/time pairs here (9/4/2005 2:38pm and 9/13/2005 8:32pm).

BUT, according to jaPalmMade and RomFlashCheckerv3, my TX was made Sept 6, 2005 and is FLASH.

Obviously, you can't tell if you have ROM or FLASH from the .6 or .9 strings.

Also, the string reported by jaPalmMade can't be 100% right because my .9 date lies one week -after- the jaPalmMade date....
although japalmmade and manufdate are returning the same date (JAmerican's utility is easier to use though).

[alt236]

Also, the string reported by jaPalmMade can't be 100% right because my .9 date lies one week -after- the jaPalmMade date....

jaPalmMade extracts the manufacture date from the serial number (see this article http://forum.brighthand.com/showthread.php?t=17537).
So I'm guessing (which is logical actually) that the h/w was mass produced and labelled before the s/w was installed.

[dmitrygr]

no such luck. These are boot roms, you CANNOT program these once the device is assembled. They are either programmed before being installed on the board, or shortly after, using contacts on board

[_Em]

...and in this case, the board is unlikely to contain a programming header, so they're mounted pre-programmed.

As for the OEM, it's some Chinese firm. Anyone have any more details?

[Gwidion]

Mine says "Flash" an my Device is 21.Dec.2005[JaPalmmade] (

9/4/05,2:38 pm ( :shortcut: .6)
Tue 11/08/2005 12:59 AM ( :shortcut: .9)

[alt236]

Is there a revision number on the board btw? Or the swich was done silently?

[alt236]

Is any of the palms with funny dates refurbished?
There is the chance they are swiching mobos at the service point.

[alegra]

BUT, i did manage to throw away half the rom, and add netfront and small fonts and clie organizer on my TX :-)

Clie Organizer seems the most interesting thing for me... Does it work well? Also possible in RAM?

[thenrik]

Hi:

I've had a cold and slept though the entire thread. That being said my backup T/X came up Flash with RomFlashCheckV3 with Rom dates of:

.6 9/04/05 2.38pm
.9 9/13/05 8:32 PM

soo if it's needed for trading or testing, let me know.

My primary palm came up ROM so I didn't bother running the .6/.9 shortcuts.

Tom

[cms]

I want Clie Organizer...

[BrentDC]

I second that!!!

<crossing my fingers>

[phreakonaleash]

The question posted by alegra stands: does organizer play nicely in RAM?

[alegra]

The question posted by alegra stands: does organizer play nicely in RAM?

I managed it once to get parts of it running on my Tungsten C (with some special software). Installing it in RAM could make problems, but I don't really think so. I rather think that Dmitry patched some files. But I am interested it the whole thing works, or only parts...

BTW, c-j-archer has also a TH55 ROM and will have a look at it. Perhaps it will work soon on all Palms. Nowadays there are almost all kinds of applications for Palm, but Clie Organizer is one of the few I am still missing.

[dmitrygr]

ok, i got my TX, i will resume development soon :-)

[_Em]

The question posted by alegra stands: does organizer play nicely in RAM?

I recently tried it, and the answer is no. I found that it interfered with my alarm program, stepped on a bunch of other apps, and still didn't actually work correctly. Of course, I made no modifications to anything, other than having MaxX and PicselEnhancer installed along with the Clie fonts. Often, the fonts are enough to make something operate that is expecting a Clie, but not in the case of Organizer.

[alegra]

What exactly didn't work?

[_Em]

Well, for starters, the front end app won't launch, making it pretty useless.

[dmitrygr]

guys, please if you plan to branch off on that tangent, make a new thread for it, and for the record with ~2000 bytes total in various components modified, and two extra libraries written by me, it runs perfectly on the TX

[alegra]

guys, please if you plan to branch off on that tangent, make a new thread for it, and for the record with ~2000 bytes total in various components modified, and two extra libraries written by me, it runs perfectly on the TX

I will start a new thread in the T|X forum. It would be good if you could publish your patches / libs there.

[dmitrygr]

Anyone feeling lucky enough to test a version that writes a new rom? (it is just a test, the new rom is the same as old, with addition of a small game "another bottle"

All you need if a flashable TX and an SD card with 16MB free space...

[BarsMOnster]

Anyone feeling lucky enough to test a version that writes a new rom? (it is just a test, the new rom is the same as old, with addition of a small game "another bottle"

All you need if a flashable TX and an SD card with 16MB free space...

I am feeling licky :-).

[thenrik]

Hi:

My flashable T/X is available as well.

Tom

[FerdFerd]

I am feeling licky :-).Licky?! Sounds messy.

[dmitrygr]

You need to make the following folder on card: /palm/rd
into it, put this file, renamed to "new.bin" [LINK (http://www.palmpowerups.com/priv/NEW.bin)]

then put this in /palm/launcher, named RomFlash.prc [LINK (http://www.palmpowerups.com/priv/RomFlash.prc?ver=4)]

Card should NOT be write-locked, as the app will write a log into /palm/rd/Log.txt

I will need a copy of this log when you're done

then connect palm to external power, insert card, and run the RomFlash app. It should finish successfully. After that comes the luck/no luck part: reset. If all worked your device will reset fine, if not, it will get stuck on the orange palm logo without the black progress bar on bottom.


By doing this you agree to be the sole person responsible for any consequences, be they good or bad.

[thenrik]

Hi:

I'm ready to run the romflash from my card. Should I be using any particular launcher? Is LauncherX ok or should I install a trial version of another?

Thanks,

Tom

[dmitrygr]

anything is ok

hope all goes well for you

[Modnar]

anything is ok

hope all goes well for you
I know the risks involved with any rom flashing but got to ahve a chuckle from your reply :P

[BarsMOnster]

FAILED, PalmTX is not destroyed.

I had to manually create directory for log to get this.
Also, when there were no log directory, I was having lots of message boxes, and log file was not created. Also, there was a reset after operation.

Mapping HW of length 0x00000000
Slot found
All done!
Mapped at 0x01300000
Flash type "Intel" detected.
8 MB flash with 128 KB block
Unique ID: 0546B2019E456CA7
Dumping...
SECTOR 0:
*loading from card
Error 0x2A08 on line 173
Assert "0" failed at MainProg.c:173.

[BarsMOnster]

SUCCESS after placing .bin file to /palm/rd instead of /palm/launcher/rd. I assert/error in the log anyway.

God bless your program had enough validations to not to write all 0s to the rom :)

After flashing I did reset (clicked reset on the back). After that I've seen new game, was able to launch it. After in-game message "Tap screen to start" I've got reset.

Mapping HW of length 0x00000000
Slot found
All done!
Mapped at 0x01300000
Flash type "Intel" detected.
8 MB flash with 128 KB block
Unique ID: 0546B2019E456CA7
Dumping...
SECTOR 0:
*loading from card
Error 0x2A08 on line 173
Assert "0" failed at MainProg.c:173.
Mapping HW of length 0x00000000
Slot found
All done!
Mapped at 0x01300000
Flash type "Intel" detected.
8 MB flash with 128 KB block
Unique ID: 0546B2019E456CA7
Dumping...
SECTOR 0:
*loading from card
*checking for changes
*nothing to write
SECTOR 1:
*loading from card
*checking for changes
*nothing to write
SECTOR 2:
*loading from card
*checking for changes
*will write
SECTOR 3:
*loading from card
*checking for changes
*will write
SECTOR 4:
*loading from card
*checking for changes
*will write
SECTOR 5:
*loading from card
*checking for changes
*will write
SECTOR 6:
*loading from card
*checking for changes
*will write
SECTOR 7:
*loading from card
*checking for changes
*will write
SECTOR 8:
*loading from card
*checking for changes
*will write
SECTOR 9:
*loading from card
*checking for changes
*will write
SECTOR 10:
*loading from card
*checking for changes
*will write
SECTOR 11:
*loading from card
*checking for changes
*will write
SECTOR 12:
*loading from card
*checking for changes
*will write
SECTOR 13:
*loading from card
*checking for changes
*will write
SECTOR 14:
*loading from card
*checking for changes
*will write
SECTOR 15:
*loading from card
*checking for changes
*will write
SECTOR 16:
*loading from card
*checking for changes
*will write
SECTOR 17:
*loading from card
*checking for changes
*will write
SECTOR 18:
*loading from card
*checking for changes
*will write
SECTOR 19:
*loading from card
*checking for changes
*will write
SECTOR 20:
*loading from card
*checking for changes
*will write
SECTOR 21:
*loading from card
*checking for changes
*will write
SECTOR 22:
*loading from card
*checking for changes
*will write
SECTOR 23:
*loading from card
*checking for changes
*will write
SECTOR 24:
*loading from card
*checking for changes
*will write
SECTOR 25:
*loading from card
*checking for changes
*will write
SECTOR 26:
*loading from card
*checking for changes
*will write
SECTOR 27:
*loading from card
*checking for changes
*will write
SECTOR 28:
*loading from card
*checking for changes
*will write
SECTOR 29:
*loading from card
*checking for changes
*will write
SECTOR 30:
*loading from card
*checking for changes
*will write
SECTOR 31:
*loading from card
*checking for changes
*will write
SECTOR 32:
*loading from card
*checking for changes
*will write
SECTOR 33:
*loading from card
*checking for changes
*will write
SECTOR 34:
*loading from card
*checking for changes
*will write
SECTOR 35:
*loading from card
*checking for changes
*will write
SECTOR 36:
*loading from card
*checking for changes
*will write
SECTOR 37:
*loading from card
*checking for changes
*will write
SECTOR 38:
*loading from card
*checking for changes
*will write
SECTOR 39:
*loading from card
*checking for changes
*will write
SECTOR 40:
*loading from card
*checking for changes
*will write
SECTOR 41:
*loading from card
*checking for changes
*will write
SECTOR 42:
*loading from card
*checking for changes
*will write
SECTOR 43:
*loading from card
*checking for changes
*will write
SECTOR 44:
*loading from card
*checking for changes
*will write
SECTOR 45:
*loading from card
*checking for changes
*will write
SECTOR 46:
*loading from card
*checking for changes
*will write
SECTOR 47:
*loading from card
*checking for changes
*will write
SECTOR 48:
*loading from card
*checking for changes
*will write
SECTOR 49:
*loading from card
*checking for changes
*will write
SECTOR 50:
*loading from card
*checking for changes
*will write
SECTOR 51:
*loading from card
*checking for changes
*will write
SECTOR 52:
*loading from card
*checking for changes
*will write
SECTOR 53:
*loading from card
*checking for changes
*will write
SECTOR 54:
*loading from card
*checking for changes
*will write
SECTOR 55:
*loading from card
*checking for changes
*will write
SECTOR 56:
*loading from card
*checking for changes
*will write
SECTOR 57:
*loading from card
*checking for changes
*will write
SECTOR 58:
*loading from card
*checking for changes
*nothing to write
SECTOR 59:
*loading from card
*checking for changes
*nothing to write
SECTOR 60:
*loading from card
*checking for changes
*nothing to write
SECTOR 61:
*loading from card
*checking for changes
*nothing to write
SECTOR 62:
*loading from card
*checking for changes
*nothing to write
SECTOR 63:
*loading from card
*checking for changes
*will write
SECTOR 2:
*erasing
*writing
*verifying
SECTOR 3:
*erasing
*writing
*verifying
SECTOR 4:
*erasing
*writing
*verifying
SECTOR 5:
*erasing
*writing
*verifying
SECTOR 6:
*erasing
*writing
*verifying
SECTOR 7:
*erasing
*writing
*verifying
SECTOR 8:
*erasing
*writing
*verifying
SECTOR 9:
*erasing
*writing
*verifying
SECTOR 10:
*erasing
*writing
*verifying
SECTOR 11:
*erasing
*writing
*verifying
SECTOR 12:
*erasing
*writing
*verifying
SECTOR 13:
*erasing
*writing
*verifying
SECTOR 14:
*erasing
*writing
*verifying
SECTOR 15:
*erasing
*writing
*verifying
SECTOR 16:
*erasing
*writing
*verifying
SECTOR 17:
*erasing
*writing
*verifying
SECTOR 18:
*erasing
*writing
*verifying
SECTOR 19:
*erasing
*writing
*verifying
SECTOR 20:
*erasing
*writing
*verifying
SECTOR 21:
*erasing
*writing
*verifying
SECTOR 22:
*erasing
*writing
*verifying
SECTOR 23:
*erasing
*writing
*verifying
SECTOR 24:
*erasing
*writing
*verifying
SECTOR 25:
*erasing
*writing
*verifying
SECTOR 26:
*erasing
*writing
*verifying
SECTOR 27:
*erasing
*writing
*verifying
SECTOR 28:
*erasing
*writing
*verifying
SECTOR 29:
*erasing
*writing
*verifying
SECTOR 30:
*erasing
*writing
*verifying
SECTOR 31:
*erasing
*writing
*verifying
SECTOR 32:
*erasing
*writing
*verifying
SECTOR 33:
*erasing
*writing
*verifying
SECTOR 34:
*erasing
*writing
*verifying
SECTOR 35:
*erasing
*writing
*verifying
SECTOR 36:
*erasing
*writing
*verifying
SECTOR 37:
*erasing
*writing
*verifying
SECTOR 38:
*erasing
*writing
*verifying
SECTOR 39:
*erasing
*writing
*verifying
SECTOR 40:
*erasing
*writing
*verifying
SECTOR 41:
*erasing
*writing
*verifying
SECTOR 42:
*erasing
*writing
*verifying
SECTOR 43:
*erasing
*writing
*verifying
SECTOR 44:
*erasing
*writing
*verifying
SECTOR 45:
*erasing
*writing
*verifying
SECTOR 46:
*erasing
*writing
*verifying
SECTOR 47:
*erasing
*writing
*verifying
SECTOR 48:
*erasing
*writing
*verifying
SECTOR 49:
*erasing
*writing
*verifying
SECTOR 50:
*erasing
*writing
*verifying
SECTOR 51:
*erasing
*writing
*verifying
SECTOR 52:
*erasing
*writing
*verifying
SECTOR 53:
*erasing
*writing
*verifying
SECTOR 54:
*erasing
*writing
*verifying
SECTOR 55:
*erasing
*writing
*verifying
SECTOR 56:
*erasing
*writing
*verifying
SECTOR 57:
*erasing
*writing
*verifying
SECTOR 63:
*erasing
*writing
*verifying
Done

[dmitrygr]

the game itself was just the first file i found in my palm folder, it need not acutally work to prove this works. If you want to restore your rom to its original state, i can provide you with a different "new.bin" file



thank you for being my guinea pig :-)

[thenrik]

Hi:

Dmitry, would it still be helpful for me to flash my T/X or did you just need one person to prove it works?

Tom
On the West coast and gettin' up later

[BarsMOnster]

the game itself was just the first file i found in my palm folder, it need not acutally work to prove this works. If you want to restore your rom to its original state, i can provide you with a different "new.bin" file



thank you for being my guinea pig :-)

No need for default bin file. I'll wait till official release ;-)

[dmitrygr]

no need, just wanted to make sure it worked, i flashed mine BEFORE i made the final adjustment, so mine is now a nice brick (UGH!), but after that it should have worked, and it did. now i can continue development with any tx, not necessarily a flashable one, and will begin by making a recovery rom app, so that no other TX is ever bricked!

[thenrik]

Hi:

Let us know if you need more testers in the future. Anything to get Pa1m OS II off the ground.


Tom

[2XS]

Hi:

Let us know if you need more testers in the future. Anything to get Pa1m OS II off the ground.


Tom

I second this !!

[Deceptitech]

Mine has a date of SUN 12/04/2005 for the .9 check
And a second date of 9/4/5 for the .6 check.

I just got this TX today from Palm.

Looks like they put new and old into the mix.

[gahenton]

well mine flashed ok, now I have a game that doesnt work. Whats the next step??

GerryH

[dmitrygr]

next step is waiting for me to get another TX :-)

[ftwitty]

next step is waiting for me to get another TX :-)
Problem is those with the flash Tx devices don't want to give them up in case you develop something they want........... :D

[dmitrygr]

well, i can test without a flash TX, the problem then is that i might miss something that bricks the flash ones, hence why i prefer to test myself - if i brick mine - nobody but me is at a loss.