ok i'm having issues with the 2.04 upgrade on my PPC6600
heres what i've done step by step
1. disable activesync
2. put device in bootloader mode with record+power+reset
3. run romupdate.exe
4. connect to \\wcblahblah...
5. type d2s and hit enter (ive also done "d2s 80000000 02000000" got that idea here)
Code:
USB>d2s
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SD:Detected one card
SD:ready for transfer OK
pc->drive.total_lba=F1F00
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=A95C
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=1E3E0000
*******************************************************************************************************************************
Store image to SD/MMC card successful.
USB>
6. when its done, I remove the 6600 from the cradle (device switches from USB to Serial but still displays "CheckSum is OK!")
7. remove the card and put it in the reader and store it in a file with ntrw
Code:
C:\rom204>ntrw.exe read current203.nb1 f:
NTRW v2.00
Removeable media
Cylinders: 0:61
TracksPerCylinder: 255
SectorsPerTrack: 63
BytesPerSector: 512
bufsize is 65536
507379712 bytes written bytes: 0
ReadFile(): current203.nb1 -- The parameter is incorrect.
8. use hex editor to copy first 416 bytes mine was
Code:
48 41 52 52 49 45 52 20 20 20 20 20 20 20 20 20
30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
31 2e 30 32 20 20 20 20 20 20 20 20 20 20 20 20
1c b9 2f 63 d9 23 d1 55 90 38 28 d1 d9 6c a1 66
5e 4e e1 30 9c fe d9 71 9f e2 a5 e2 0c 9b b4 47
65 38 2a 46 89 a9 82 79 7a 76 78 c2 63 b1 26 df
da 29 6d 3e 62 e0 96 12 34 bf 39 a6 3f 89 5e f1
6d 0e e3 6c 28 a1 1e 20 1d cb c2 03 93 35 f8 0d
0f 14 05 65 1b 28 61 c9 c5 e7 2c 8e 46 36 08 dc
f3 a8 8d fe be f2 eb 71 ff a0 d0 3b 75 06 8c 7e
87 78 73 4d d0 be 82 be db c2 46 41 2b 8c fa 30
7f 70 f0 a7 54 86 32 95 aa 5b 68 13 0b e6 fc f5
ca be 7d 9f 89 8a 41 1b fd b8 4f 68 f6 72 7b 14
99 cd d3 0d f0 44 3a b4 a6 66 53 33 0b cb a1 10
b0 19 57 57 df cd 6c 10 8d 74 6f 66 43 16 d6 08
a5 59 d0 47 f7 ea 15 b8 e0 84 60 8f 6e d0 b1 f4
cd 8c 87 20 23 64 b8 a6 87 95 4c b0 5a 8d 4e 2d
99 e7 3d b1 60 de b1 80 ad 08 41 e9 67 41 a5 d5
9f e4 18 9f 15 42 00 26 fe 4c d1 21 04 93 2f b3
8f 73 53 40 43 8a af 7e ca 6f d5 cf d3 a1 95 ce
5a be 65 27 2a f6 07 ad a1 be 65 a6 b4 c9 c0 69
32 34 09 2c 4d 01 8f 17 56 c6 db 9d c8 a6 d8 0b
88 81 38 61 6b 68 12 62 f9 54 d0 e7 71 17 48 78
0d 92 29 1d 86 29 99 72 db 74 1c fa 4f 37 b8 b5
48 54 43 53 41 30 30 34 30 30 30 30 30 31 46 43
30 30 30 30 36 33 32 46 42 39 31 43 fe 03 00 ea
i've also used bytecopy.exe (attached)
EDIT: this is where i went wrong -read on to find out where to get the correct file
9. open "TELUS_CDMA_2.04.00WWE.nb1" (132,775,936 bytes, md5 a34d4dc7b38c19dcd2c0e704bcbc8c01) paste the 416 bytes from the current203.nb1 and save file as target.nb1
10. use ntrw to write the target.nb1 to the sd again
Code:
C:\rom204>ntrw.exe write target.nb1 f:
NTRW v2.00
Removeable media
Cylinders: 0:61
TracksPerCylinder: 255
SectorsPerTrack: 63
BytesPerSector: 512
bufsize is 65536
132775936 bytes written
i've also used this utility to write the image to the disk
11. reinsert card and wait for the update prompt that isnt coming (screen still reads Serial and "CheckSum is OK!")
12. wait 10 minutes, put device in cradle, wait 10 minutes, take device out of cradle, eject card, reinsert card, wait 10 minutes, curse
13. finally give up and reset to bootloader again
14. wait until the prompt comes up to flash
most of the time i get "Sections=3" == "Not allow update!" but occasionally "Sections=0" and it updates to 100% then gives a CRC fail message
I've used a 128MB and a 512MB sd card.
I've reverted to the 1.36 rom and used its header -same results
I know i'm missing something here.
I don't even care about getting the 2.04 rom on the device anymore but i can't let this stubborn piece of crap beat me.
__________________
Create DialPad Skins for your 6600 with SkinGen
Last edited by Disgruntledtech : 08-28-2005 at 03:20 PM.
I think it would be easier to use the lower sized cards because the error would be quicker.
On the 1.3x versions, the offsets for the CE ROM are documented. It's only on the 2.04 where they only succeeded with the whole dump.
My theory is you're not getting the dump off your device successfully. I suspect when you can get it to set bytes written: nonzero that would be a success.
I haven't followed the threads other than reading them as they happenned (because I thought to myself that I didn't want to go that route just yet). So pardon me if I say something stupid or stale...
But what is it SUPPOSED to say when you successfully dump the rom to the sd card?
14. Wait for the program to finish. This can take a few minutes, and will create a file (in the directory with NTRW) with a size up to the SD Card’s capacity (256Mb on mine). Ignore any error messages
i think i've donr everything -i even tried to find a way to turn the telus*.nb1 file to an NK.nbf file to do it via activesync.
__________________
Create DialPad Skins for your 6600 with SkinGen
Just read them. Wondering maybe if you should copy the first 420 bytes not first 416. It suggests that some 0's will indicate the end of the data... and the last of your 416 is ea. Were there 00000000 after that one?
10. Unplug your ... ppc and leave it on. I assume you did this.
25. put the [modified] card in... wait 5 mins for it to be recognized. You could also hard reset it with card in and see if it recognizes it.
and finally unedited #28:
28. You’re in trouble. Like me, you’ll have to try different combinations of steps 25, 26, and 27 until you get the prompt to upgrade. Try plugging USB in, out, restarting your PC, USB in again, all waiting 5 minutes just to be sure. EVENTUALLY you will get it. It took me 40 minutes until it worked for me, but work it will
I just dumped 2.03 to the 512 and the 128 i tried reflashing from the 128 but got a message about rom file isnt big enough but i was able to get it to attempt to reload it as i type this -just to test the dump
the loader would not start until i did a bootloader reset with the card in at boot -then it took about 60 seconds for it say "Sections=0" press power to flash
ok the 2.03 reflash just finished and checksum read OK so its not the dump (a more accurate test woulda been rolling back to 1.36 and reflash to 2.03 with the card alone but this test satisfies me)
now im gonna modify the image, write it to the card, redump it to a new file and compare them -see if the write process is corrupting it
__________________
Create DialPad Skins for your 6600 with SkinGen
i gotta figure this thing out its killing me -just hex edited the first 416 bytes on the 512 image that worked and used the bytecopy app on a copy of the file and they are identical according to beyond compare so it not my bad hex editing skills that are to blame...
__________________
Create DialPad Skins for your 6600 with SkinGen
This is much more interesting than For Your Eyes Only on AMC
E
Lmao I almost spit my beer on my screen! Anyway, I was the one to help with the initial dump and one of the first couple of us getting this update to work on our devices. One key thing you have to make sure of is that the device is in bootloader when you insert the card, then power it off and back on (in other words, have the device power on fresh with the card already in). I succeeded with a 1GB card, so the card size is not the issue. It's also definitely the first 416 bytes. If you're using a hex editor you'll be able to see where the header stops anyway because after the header is a big gap of zero bytes. If this does not work, then my guess would be that you aren't getting your header from your device correctly for whatever the reason. If you open your rom dump, the header you're grabbing should be somewhat comprehensible at the beginning (device ID, etc.). Let me know how things work out.
EDIT: The other thing that might help (but not likely) is a clean format on the SD card first. You never know..
__________________
AT&T iPhone 8GB, Belkin leather case
I know when I did mine I had to use a 64 meg sd card. With my 1 gig sd card the image would transfer to the card but my device wouldn't read it.
__________________
Eric Hicks, Microsoft MVP, Mobile-Devices
My Devices
Four PPC6600's, One PPC6700, Three PPC6800's,One Treo 700w,One Jas Jar,One Pantec Duo,One T-mobile Dash...Do I have too many devices?
i used a 256 meg card and it worked for me...make sure your dumping the right part of the rom. i believe the first time i tried it i dumped everything but i think you need the first 416 from only the ce rom dump. also make sure you have the right file download as there were multiple attempted dumps but the one with the ce rom only is the one you want...if i remember correctly
Originally posted by gimpdog i used a 256 meg card and it worked for me...make sure your dumping the right part of the rom. i believe the first time i tried it i dumped everything but i think you need the first 416 from only the ce rom dump. also make sure you have the right file download as there were multiple attempted dumps but the one with the ce rom only is the one you want...if i remember correctly
This is *very* correct. You need the first 416 bytes from ONLY d2s (NO parameters). When you use the parameters to grab more than one rom (besides the CE rom), the header ends up different and incompatible with other dumps that are just the CE rom. I bet that's your problem. Sorry I didn't mention it before, as that was what kept us from initially getting this to work ourselves.
__________________
AT&T iPhone 8GB, Belkin leather case
I believe you are using the wrong file. I had the same problem until I used the telusd2s.rar file. That other file appears to be a corrupt image. I found this file here ftp://ftp.xda-developers.com/Uploads/Blueangel/.
Good luck.
Originally posted by phat78boy I believe you are using the wrong file. I had the same problem until I used the telusd2s.rar file. That other file appears to be a corrupt image. I found this file here ftp://ftp.xda-developers.com/Uploads/Blueangel/.
Good luck.
Also true. The first dump was not just the CE, and nobody was able to get that working. We had him redump just the CE image, and that's what ended up working for us. The other dump should just get deleted.
__________________
AT&T iPhone 8GB, Belkin leather case
The biggest issue I had was, when rewritting the modfied image back to the SDcard, the ntrw.exe program would leave like the first 512 bytes to be the FAT32 header. The Harrier would never see it as a flashable image. The way to check this is to write the modified image back to the card using ntrw.exe, then use WinHex to do a "Raw Open" from the SDCard. The first line should be
If it is not the first line at location 00000000, then do a search for HARRIER to find it. The start a copy paste from this line to the end, then raw right it back to position 00000000 WinHex will tell you this could corrupt the card, etc. but it is fine. It will overwrite all the fat32 headers. Then pop the card in the Harrier, do a bootloader reset and it finds the image right away.
I just did the 2.04 upgrade today for the hell of it, just because I like tinkering with technology. I had time and knew what i was doing and I mainly wanted the 3600 BT stack as I was tired of the inability to transfer a call from the headset to the handset on 3900 or 3900B, and I didnt like the static I got with 3500 that came with 2.03 (even got static on that with my HBH-660 I used to have). The new bluetooth stack works beautifully, best stack yet with my BT-250v. Just finished reinstalling all my programs.
As far as the actual upgrade process, everything went without a hitch until the very end of the process. When I loaded the 2.04 ROM off of the SD Card, I received a checksum error and another error (write error i believe?) after it had hit 100%. I figured I may have copied the header over wrong (I copied bytes 0-415), but I performed a hard reset, and discovered that it did indeed work and I had 2.04. I also received a couple errors here and there from NTRW.exe or the romupdate.exe utility but everything seems to be fine. I used a 256MB SD card. The update itself took less time than I thought it would. If you know your way around bootloader and a hex editor, need WMP10, and have bluetooth issues, I would definitely recommend giving this a try. Anyone who does, be sure to post your results and notes on the upgrade process.
Yeah thats what I figured...if it was bad it wouldnt have worked But thought I'd post them anyways in case anyone else ran into the same problem and started to panic.
Anyway, I was the one to help with the initial dump and one of the first couple of us getting this update to work on our devices. One key thing you have to make sure of is that the device is in bootloader when you insert the card, then power it off and back on (in other words, have the device power on fresh with the card already in). I succeeded with a 1GB card, so the card size is not the issue. It's also definitely the first 416 bytes. If you're using a hex editor you'll be able to see where the header stops anyway because after the header is a big gap of zero bytes. If this does not work, then my guess would be that you aren't getting your header from your device correctly for whatever the reason. If you open your rom dump, the header you're grabbing should be somewhat comprehensible at the beginning (device ID, etc.). Let me know how things work out.
Login
Panel
