Page 2 of 3 FirstFirst 123 LastLast
Results 21 to 40 of 55
  1. hall316's Avatar
    Posts
    333 Posts
    Global Posts
    334 Global Posts
    #21  
    what exactly does Palmone's update do? Is it only if my car has built in BlueTooth? Has anyone just tried uninstalling Shadow's Dun fix and then trying the update from Palmone?
  2. #22  
    Ok, let me give some pointers here. As pointed out, the original is no where near as big as the rom update. The reason is that original is ONLY the original phone software, NOT the rom. It backs up whatever you have in rom and replaces it afterward.

    So, to restore your phone to the original ROM, etc:

    1) Flash the The Original patched ROM as released from Palm or with DUN if you feel lucky!
    2) Run the The Original ROM (if you need it) prc file, and leave it be. MAKE SURE TO BE PLUGGED IN!
    3) Hard reset and try the bluetooth update...
  3. #23  
    Quote Originally Posted by bcaslis
    I hard reset, installed the original ROM file (it seemed to go fine), hard reset, restored my data, ran the updater and still got the device incompatible message. I had only installed the original ROM update, not any of the custom ROMs.
    Nevermind, if you didn't have a custom rom, then it wouldn't make a difference. Sounds like something is left changed, and I think it's the bootloader! Give me a bit of time to try and extract the update so we can use it with the custom roms.
  4. #24  
    Ok, now that I look at it, it's not encrypted, just compresed...
  5. #25  
    so why isnt it working?
  6. #26  
    Quote Originally Posted by michael82574
    so why isnt it working?
    Easier asked than answered... Give me time my friend...

    I've extracted the first compressed file... It's, bleh, yet another installer with more compressed files! Ack! Palm, do you like torturing me!?!?

    I can now tell you it's a 7 file update, just BT files...
  7. #27  
    Well, I think I got it... Anyone want to try it? I make no promises... It murders the simulator... IF you want to try it, I'll have it at my website in a moment, it'll be at the BOTTOM of the page called test link. If it works let me know. But I don't want to give you hope, this is completely untested and as I said, it murders the sim. So if you try it, I'd say 50/50 chances of working or killing a phone.

    Seriously, I hope this works now, but I am away from home and can't get this to my phone to try it. So... I'd hope if it does cause a reset loop that a hard reset or system reset will bring it back.
    Last edited by shadowmite; 12/24/2004 at 02:18 AM.
  8. #28  
    Quote Originally Posted by dzenc
    Shadowmite,

    The "Original 650 firmware" file that you have on your site is interesting (for one, it seems to contain the entire Qualcomm CDMA firmware and includes a lot of references to GPS ), but it's *way* too small to actually contain the original 650 FLASH ROM image, and there are too many readable strings in it for it to be compressed (and even ZIP compressed, the faisal rom was close to 8 megabytes).

    I'd like to find a way to get back to the original 650 ROM. Do you know the location of the ROM in the 650 address space? Maybe we can write a little utility to dump the entire ROM from a virgin 650 to a file on an SD card? Obviously, it's a little bit trickier to get it written back to the device, but the first step seems to be to get a good dump of a virgin ROM...
    - I don't believe any of the old standby apps (like GetROM) will provide you with a readable ROM dump from Palm's current Treo ROM architecture. But Palm "accidentally" (again) providing a ROM flasher makes the reflashing a much simpler process that it otherwise would have been.

    - I believe the ROM is stored compressed and then is actively expanded with use.

    - Flashing with the beta ROM likely removed a signature file that the Genuine Palm™ Bluetooth update checks for. Running the equivalent of a checksum on the beta Vs. a fresh, unflashed ROM would confirm this.

    - If Palm wakes up, from now on they will both compress AND encrypt the ROMs to prevent any further hacks. They will also start playing hardball by letting Sprint Stores know how to check to see if an unauthorized flash was performed on returned units and disallow warranty claims. Palm can't afford to keep paying for replacement phones for every wannabe hacker that messes up their phone with unauthorized ROM flashes and then finds out they need some lost some functionality.
  9. #29  
    Quote Originally Posted by Guns and Roses
    - If Palm wakes up, from now on they will both compress AND encrypt the ROMs to prevent any further hacks. They will also start playing hardball by letting Sprint Stores know how to check to see if an unauthorized flash was performed on returned units and disallow warranty claims. Palm can't afford to keep paying for replacement phones for every wannabe hacker that messes up their phone with unauthorized ROM flashes and then finds out they need some lost some functionality.
    Hey, could you please leave well enough alone? I have done my best in ensure people here use a flash that won't kill their phones, and to perfect a method of recovery so we don't need replacements.

    Furthermore, the method of recovery WILL allow flashing and reading the rom without the loader app. We would have found this without faisal's leak eventually.

    Finally, I believe palm has ALWAYS compressed most loaders to keep the size down. This is standard practice, and after thinking about it I don't believe it was a attempt at "hardball".

    Just try and get along ok? If I am asked to remove files from my site, I will. Everyone knows that.
  10. #30  
    Quote Originally Posted by shadowmite
    Well, I think I got it... Anyone want to try it? I make no promises... It murders the simulator... IF you want to try it, I'll have it at my website in a moment, it'll be at the BOTTOM of the page called test link. If it works let me know. But I don't want to give you hope, this is completely untested and as I said, it murders the sim. So if you try it, I'd say 50/50 chances of working or killing a phone.

    Seriously, I hope this works now, but I am away from home and can't get this to my phone to try it. So... I'd hope if it does cause a reset loop that a hard reset or system reset will bring it back.
    What is the total size of these files? Do you think Palm is so lazy as to have made this simple? Don't answer that.

    Are you capable of loading a "safe" (proven) ROM onto a phone that has has a corrupt/incorrect ROM already loaded and refused to boot? If not, I'd question how wise it is to be posting non-Palm rolled ROMs.
  11. #31  
    Update, it appears to have worked! I don't have a car kit to test it... But feel free to use it, it's safe. If anything a hard reset would get rid of it. Enjoy, I'll move it to a full fledged link at my site now!
  12. #32  
    amazing! Hopefully someday you'll have time to figure out why using a BT headset messes with the volume on the 650 and the mute/unmute trick in necessary.
    “There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order.”
    — Ed Howdershelt
    "A government big enough to give you everything you want, is big enough to take away everything you have."- Thomas Jefferson
  13. #33  
    Thanks for all the work!

    However, I'm guessing you are installing the new BT files with this prc, correct? Do you know why the P1 one won't install? I'd really like a way to fix the ROM to avoid the whole issue.

    Quote Originally Posted by shadowmite
    Update, it appears to have worked! I don't have a car kit to test it... But feel free to use it, it's safe. If anything a hard reset would get rid of it. Enjoy, I'll move it to a full fledged link at my site now!
    Main Phone: Treo 270/600/650/700w/700p/750v/Motorola Q/iPhone
    Tried but sold: Motorola Q/Nokia E61/700wx/HTC TyTN/Treo 680
  14. #34  
    Quote Originally Posted by bcaslis
    Thanks for all the work!

    However, I'm guessing you are installing the new BT files with this prc, correct? Do you know why the P1 one won't install? I'd really like a way to fix the ROM to avoid the whole issue.
    I just pulled the file out of the checker program they use. It appears to be standard in the nutshell install tool they use. Here is the function that doesn't like our rom/update:

    00000210 4e56ffdc L14 LINK A6,#-36 ; IsDeviceOKToUpgrade
    00000214 48e71e30 MOVEM.L D3-D6/A2/A3,-(A7)
    00000218 7002 MOVEQ #2,D0
    0000021a 2d40ffdc MOVE.L D0,-36(A6)
    0000021e 4244 CLR.W D4
    00000220 7cff MOVEQ #-1,D6
    00000222 486effdc PEA -36(A6)
    00000226 42a7 CLR.L -(A7)
    00000228 3f3c0087 MOVE.W #135!$87,-(A7)
    0000022c 3f3c0027 MOVE.W #39!$27,-(A7)
    00000230 4e4fa349 TRAP #15
    00000234 DC.W sysTrapOEMDispatch
    00000234 4227 CLR.B -(A7)
    00000236 48780020 PEA $0020.W
    0000023a 76e0 MOVEQ #-32,D3
    0000023c d68e ADD.L A6,D3
    0000023e 2f03 MOVE.L D3,-(A7)
    00000240 4e4fa027 TRAP #15
    00000244 DC.W sysTrapMemSet
    00000244 42a7 CLR.L -(A7)
    00000246 2f03 MOVE.L D3,-(A7)
    00000248 3f3c0006 MOVE.W #6,-(A7)
    0000024c 3f3c00b5 MOVE.W #181!$b5,-(A7)
    00000250 4e4fa349 TRAP #15
    00000254 DC.W sysTrapOEMDispatch
    00000254 4fef001e LEA 30(A7),A7
    00000258 4a40 TST.W D0
    0000025a 6666 BNE L19
    0000025c 2f03 MOVE.L D3,-(A7)
    0000025e 4e4fa0ce TRAP #15
    00000262 DC.W sysTrapStrAToI
    00000262 2a00 MOVE.L D0,D5
    00000264 588f ADDQ.L #4,A7
    00000266 47edffc8 LEA -56(A5),A3
    0000026a 3044 L15 MOVEA.W D4,A0
    0000026c 2008 MOVE.L A0,D0
    0000026e e988 LSL.L #4,D0
    00000270 2208 MOVE.L A0,D1
    00000272 242effdc MOVE.L -36(A6),D2
    00000276 b4b30800 CMP.L 0(A3,D0.L),D2
    0000027a 661a BNE L16
    0000027c bab30804 CMP.L 4(A3,D0.L),D5
    00000280 6514 BCS L16
    00000282 bab30808 CMP.L 8(A3,D0.L),D5
    00000286 620e BHI L16
    00000288 3b44fffc MOVE.W D4,-4(A5)
    0000028c 3c04 MOVE.W D4,D6
    0000028e 3606 MOVE.W D6,D3
    00000290 5243 ADDQ.W #1,D3
    00000292 60000026 BRA L18
    00000296 3604 L16 MOVE.W D4,D3
    00000298 5243 ADDQ.W #1,D3
    0000029a 2801 MOVE.L D1,D4
    0000029c e98c LSL.L #4,D4
    0000029e 41edffc8 LEA -56(A5),A0
    000002a2 45e8000c LEA 12(A0),A2
    000002a6 2f324800 L17 MOVE.L 0(A2,D4.L),-(A7)
    000002aa 2f3c6170706c MOVE.L #1634758764!$6170706c,-(A7)
    000002b0 6100fe66 BSR L7
    000002b4 508f ADDQ.L #8,A7
    000002b6 4a40 TST.W D0
    000002b8 67ec BEQ L17
    000002ba 3803 L18 MOVE.W D3,D4
    000002bc 0c440002 CMPI.W #2,D4
    000002c0 6fa8 BLE L15
    000002c2 3006 L19 MOVE.W D6,D0
    000002c4 4cee0c78ffc4 MOVEM.L -60(A6),D3-D6/A2/A3
    000002ca 4e5e UNLK A6
    000002cc 4e75 RTS
    000002ce 93 DC.B #147
    000002cf 49734465766963654f4b DC.B 'IsDeviceOKToUpgrade'
    000002d9 546f55706772616465

    What it does, I'll save for another time...
  15. #35  
    Quote Originally Posted by Guns and Roses
    Are you capable of loading a "safe" (proven) ROM onto a phone that has has a corrupt/incorrect ROM already loaded and refused to boot? If not, I'd question how wise it is to be posting non-Palm rolled ROMs.
    That's the point of the procedure I am developing. Yes, I can, no, currently everyone can not. But they will with a serial cable in a while.
  16. #36  
    Quote Originally Posted by shadowmite
    Hey, could you please leave well enough alone? I have done my best in ensure people here use a flash that won't kill their phones, and to perfect a method of recovery so we don't need replacements.

    Furthermore, the method of recovery WILL allow flashing and reading the rom without the loader app. We would have found this without faisal's leak eventually.

    Finally, I believe palm has ALWAYS compressed most loaders to keep the size down. This is standard practice, and after thinking about it I don't believe it was a attempt at "hardball".

    Just try and get along ok? If I am asked to remove files from my site, I will. Everyone knows that.
    It's nice to hear you're trying to help, but remember how clueless the typical user is.

    If you think you could have worked back to the point where you could have successfully reflashed the ROM without the aid of faisal's "beta", you either:

    a) are delusional
    b) are very talented
    c) have a LOT of free time
    d) all of the above

    I know which answer I'm choosing.

    I think Palm's programmers are too lazy to anticipate possible hacks by hardcore users. In fact, they have had so many problems just (barely) achieving basic functionality that I can't see them implementing hack roadblocks unless the carriers become angered by the loss of ROM control and threaten to stop buying Treos unless ROM security is significantly beefed up. Do you want to try your hand in breaking encrypted code? Can't hear you.

    Putting an amateurish "disclaimer" on an obscure website and then saying that Palm should tell you if they mind these files being hosted is just plain silly. That kind of puerile rationalizing is surprising from someone intelligent enough to have done what you have done over the past few weeks. If you want to be legit, simply ask PalmOne + Sprint if you can host the files. Otherwise, please cut out the specious statements and the attempts to justify what you're doing.

    Again, I actually admire what you've done and think if PalmSource had a few more people like you coding for them, they wouldn't be near death like they are now.
  17. #37  
    Quote Originally Posted by shadowmite
    That's the point of the procedure I am developing. Yes, I can, no, currently everyone can not. But they will with a serial cable in a while.
    If you can do this, I'd suggest you be very careful about how the process gets into "the wild".

    Instructions? Yes.

    Providing an actual generic loader? No. But maybe someone could steal it from you and upload it to Treocentral under a different name. shadowflea, perhaps?
  18. #38  
    WORKED FOR ME!!! I wish i waited an hour instead of hotsyncing my phone. Now i have all kind of problems!
  19. #39  
    Shadow by any chance to you know the master subsidy lock code. So i can modify my vision password. I forgot what it was. I know when you go on the phone screen you hit ##3282# to get to the screen. I changed my vision password and it wont update so i need to change it manually.
  20. #40  
    Shadow, thanks AGAIN!!! It worked
Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions