Page 2 of 3 FirstFirst 123 LastLast
Results 21 to 40 of 47
  1. #21  
    Quote Originally Posted by tomtastic View Post
    I definitely did, mainly because the past fixes are now integrated and I can delete the installers from my SD card, secondly because of the possibility of creating a custom ROM to remove software I either don't use or have newer versions of.
    1. Just install all the low-*.pdb to RAM (680 has a large RAM, right?)
    2. Rename RomUpdater.bprc and RomUpdater_enUS.oprc to .prc, run it
    3. Type low and return in the console.
    4. Do a hard reset.
    Bingo, you have the ATT ROM updated.
  2. #22  
    Quote Originally Posted by bright2k View Post
    Bingo, you have the ATT ROM updated.
    Nice!

    I'm tempted to try myself, but I really need the 680 as it is my main (and only) PDA & phone, so I'll probably wait a bit.

    Question for those brave (or foolish ) enough to have already reflashed the ROM only (not the firmware): did you notice any bug or problem? Palm might have changed some stuff in the Firmware and may have updated the ROM accordingly, resulting in potential bugs/problems with a 'new ROM'/'old Firmware' combo...

    Anyway, congratulations for pioneering and thanks for sharing the trick!
  3. #23  
    so does this work on an unlocked phone? more importantly can we use Shadowmites T650 tool to make changes to the ROM (for example i want my 650 phone App instead of the daft 680 phne app)?
  4. #24  
    ..ndcan soeo peasepothe apphee
  5. #25  
    Quote Originally Posted by bright2k View Post
    1. Just install all the low-*.pdb to RAM (680 has a large RAM, right?)
    2. Rename RomUpdater.bprc and RomUpdater_enUS.oprc to .prc, run it
    3. Type low and return in the console.
    4. Do a hard reset.
    Bingo, you have the ATT ROM updated.
    Is this the official way of doing the Palm update?

    I only ask as 2 hours after your posting above, you were posting in another thread that you had just bricked your 680.

    http://discuss.treocentral.com/showthread.php?t=143938

    If so, you should edit your post with a warning to others to not do it.
    Thought of the day :
    No sense being pessimistic, it probably wouldn't work anyway
  6. #26  
    Yup, update is only for ATT. Dont risk it and just wait. Better safe than sorry.
  7. #27  
    I've made what I believe to be the first custom ROM for the 680.

    All the tools you need are already out there on the internet, but using them is far from being the polished experience that grack.com's RomTool gave us for the 650's.

    I was going to link to my blog with rough instructions of how to do this yourself, but seeing as we're already seeing posts where people have bricked their phones, it's better that I don't.

    For those that care, meminfo is showing the following for my custom rom :
    Storage heap: 67616
    Storage free: 65854
    DBCache size : 28207
    DBCache free : 27241
    DBCache chunk : 16383
    Dynamic Heap : 10560
    Dynamic Free : 8117
    Dynamic chunk : 5929
    Last edited by tomtastic; 05/29/2007 at 10:29 AM.
  8. #28  
    What's your blog address?
  9. #29  
    Quote Originally Posted by MFB View Post
    What's your blog address?
    Looks like it's http://web.mac.com/tomtastic/iWeb/inkhorn.net/log/log.html
    V > Vx > m505 > m515 > T/T > T3 > TC > 650 > 680
    <script type="text/javascript" src="http://download.skype.com/share/skypebuttons/js/skypeCheck.js"></script>
    <a href="skype:wwgamble?call"><img src="http://mystatus.skype.com/balloon/wwgamble" style="border: none;" width="150" height="60" alt="My Skype status" /></a>
  10. #30  
    What carrier db does the ATT update have?

    Its 292 for ATT right? Im sure its 355 for Unlocked ROW and 388 for APR.
  11. #31  
    Please understand I accept no responsibility if you brick your lovely 680's
  12. #32  
    355 appears if you just update the ROM and not the phone firmware. If you update both, you should be getting 292 as your carrier db. Its also the perfect match as using other versions slow down the treo.
  13. #33  
    Quote Originally Posted by MFB View Post
    355 appears if you just update the ROM and not the phone firmware. If you update both, you should be getting 292 as your carrier db. Its also the perfect match as using other versions slow down the treo.
    I have to admit I don't fully know what the CarrierDB is or does, what evidence do you have that a particular version could slow the Treo down ?
  14. #34  
    Evidence? I get more freezes when using 388. 355 had less but 292 worked as it should. I also saw some screen shots of an updated att treo and it does show 292.
  15. #35  
    Quote Originally Posted by MFB View Post
    355 appears if you just update the ROM and not the phone firmware. If you update both, you should be getting 292 as your carrier db. Its also the perfect match as using other versions slow down the treo.
    I haven't seen two separate firmware updates, did I miss something?
  16. #36  
    Nope, there's only been one firmware release.
  17. #37  
    Quote Originally Posted by khaytsus View Post
    I haven't seen two separate firmware updates, did I miss something?
    292 comes with the AT&T update
    355 is what is on the Unlocked 680
    PalmIII > PalmIIIx > PalmIIIxe > TRGPro > Handera 330 > Zire71 > Treo600 > Treo650 > Treo680 > Treo750 > Centro > TreoPro > iPhone 32GB 3GS

  18. #38  
    Quote Originally Posted by ChasT View Post
    Is this the official way of doing the Palm update?

    I only ask as 2 hours after your posting above, you were posting in another thread that you had just bricked your 680.

    http://discuss.treocentral.com/showthread.php?t=143938

    If so, you should edit your post with a warning to others to not do it.
    yeah, my 680 bricks,
    not because the update,
    but the combination the "low-palmos.zip.*" to "low-palmos.zip" and the modification to it,

    I update my two non-ATT 680s smoothly,
    and brick one by attempting custom ROM.

    So, the step is safe to just update the ROM, at least for my two 680s

    BTW, I had updated the FW also but after that it didn't find the network,
    so I changed it back, and it's OK now.
  19. #39  
    Quote Originally Posted by bright2k View Post
    yeah, my 680 bricks,
    not because the update,
    but the combination the "low-palmos.zip.*" to "low-palmos.zip" and the modification to it,

    I update my two non-ATT 680s smoothly,
    and brick one by attempting custom ROM.

    So, the step is safe to just update the ROM, at least for my two 680s

    BTW, I had updated the FW also but after that it didn't find the network,
    so I changed it back, and it's OK now.

    Updating the firmware and not getting a signal only happens with users with APR and not ROW unlocked 680.

    I've read this over at treo.net.cn Nope, its not the chinese counterpart site of mytreo.net
  20. treoluv's Avatar
    Posts
    254 Posts
    Global Posts
    259 Global Posts
    #40  
    Quote Originally Posted by ekerbuddy View Post
    where is Shadowmite??
    Got a good news and bad news for you: he is now a GSM subcriber and he is lurking around in PPC/phone forum (to be precisely, Cingular 8525.)
    Treo Maniac?
Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions