First firmware rewrite success

First firmware rewrite success
Could I be wrong twice in a row? Does anyone wish to kill a worthless 200 or 220. Oisin proved my guess wrong but my logic right. The next -*test*-('") is almost as easy as the upload to p2 (no point in doing that again and the capability should be removed in the next OPS release). Warning before performing the following make sure that BillW agrees that OPS 20 assigns the wrong partitions to the menu items and that selecting p0 will result in a upload of entire flash as indicated in UploadFlash.cpp: uploadtype_index=0; //we init to entire flash m_ctl_uploadtype.InsertString(0,"p0, NO_NAME partition"); Note the whole flash option that was in release 11 was intended to be removed in release 13 but the renumbering seems to still allow a 0 index which is interpreted as whole flash by camcorder.cpp. If true more serious cautions about using upload flash are long overdue. If I am wrong about BillW's bug then wait for BillW (or someone else) to offer a whole flash upload capability. The following are steps toward a possible firmware rewrite success using OPS buttons: 0. Prepare to celebrate or drown sorrows 1. Download whole flash as s1.img 2. Issue send monitor with "nanderase" 3. Download whole flash as s3.img (note differences from s1 if any) 4. If the result of s3.img contains all 0xFFs cross your fingers 5. Only if 8 is true then upload whole flash from s1.img 6. Flip a coin and decide whether to unplug or click OPS powerdown. I believe benefit of success outweighs the risk of another kill (as long as it isn't one of my cams). Either way we increase our hacking knowledge.

Re: First firmware rewrite success
Warning before performing the following make sure that BillW agrees that OPS 20 assigns the wrong partitions to the menu items and that selecting p0 will result in a upload of entire flash as indicated in UploadFlash.cpp: uploadtype_index=0; //we init to entire flash m_ctl_uploadtype.InsertString(0,"p0, NO_NAME partition"); I don't agree. The index numbers don't get passed to the cam routines without a bit of fiddling in the UploadFlash and DownloadFlash functions. Search for the text "we repurpose 0" in Camcorder.cpp to see what I mean. (Also Note: UploadFlash doesn't have a memory patch to enable whole flash write, unlike DownloadFlash) I'd like to hear about the steps that brought you to your list of reset commands... was another cam bricked? Basically I'd like to be sure there's something real here before turning on the upload whole flash ability. A whole bunch of cams were bricked the first time "upload whole flash" was added. (but I'd be willing to provide an unofficial build to someone willing to become a brick layer)

I will try it. Just give me the ability, how, and I will be the who

Re: First firmware rewrite success
I don't agree. The index numbers don't get passed to the cam routines without a bit of fiddling in the UploadFlash and DownloadFlash functions. I'd like to hear about the steps that brought you to your list of reset commands... was another cam bricked? Basically I'd like to be sure there's something real here before turning on the upload whole flash ability. A whole bunch of cams were bricked the first time "upload whole flash" was added. (but I'd be willing to provide an unofficial build to someone willing to become a brick layer) Sorry I didn't notice the index+2 in OpsDlg::OnUploadflash(). Oisin's bricked cam and my St Patrick's day bricked cam seem to confirm a need for contiguous blocks for firmware. Starting with an erased flash may result in an upload flash occupying contiguous blocks.

to download whole flash should i choose the said p0 or all accesible flash?

No, forget p0 - you want all accessible flash, but wait till BillW can provide the same option in upload flash.

to download whole flash should i choose the said p0 or all accesible flash? "all accesible flash" is the one that will attempt to restore the whole flash image, in the experimental Ops. (I sent the new version to him, brite)

8. If the result of s7.img contains all 0xFFs cross your fingers I am not there yet but In what exactly am I looking for?

You are looking for a complete erase of the flash which should reset all bytes to hex FF. Do you have a hex editor and know how to use it? If the s7.img still is the same as s1.img then I would not try the upload.

DEBUG: OPS v0.20 (libusb 0.1.10.1) - Use this software at your own risk.The author takes no responsibility for any damages. "Are you ready to download another video of the Kiddos...Please Stand-By...Proceed." Found the camcorder: Pure Digital Inc. Saturn , VID:167B PID:0101 Found camcorder. Connected to camcorder. succeeded in unlocking camcorder Camcorder unlocked monitor command succeded. flash download was 131072000 bytes Success retrieving s1.img monitor command succeded. Monitor succeded monitor command succeded. flash download was 0 bytes Success retrieving s3.img monitor command succeded. Monitor succeded monitor command succeded. flash download was 131072000 bytes Success retrieving s5.img monitor command succeded. Monitor succeded monitor command succeded. flash download was 131072000 bytes Success retrieving s7.img I compared S1 and S7 and they are the same. oh well.

Thanks, hold off for more analysis. Odd that after the nanderase download flash produced an empty file but after ssdfcerase it all came back. The time to try an upload might be after the nanderase - but I suggest waiting for others to express some ideas. If your cam still works can you repeat up to step 8 with the same results?

I will try again tomarrow evening/night and post results.

Attempt #2 DEBUG: OPS v0.20 (libusb 0.1.10.1) - Use this software at your own risk.The author takes no responsibility for any damages. "Are you ready to download another video of the Kiddos...Please Stand-By...Proceed." Found the camcorder: Pure Digital Inc. Saturn , VID:167B PID:0101 Found camcorder. Connected to camcorder. External key file, saturnkeys.txt was found and will be loaded Camera revision retrieved from camcorder: 03.40 Good news everyone... the retrieved challenge doesn't match response. Attempting unlock succeeded in unlocking camcorder Camcorder unlocked monitor command succeded. flash download was 131072000 bytes Success retrieving s1.img monitor command succeded. Monitor succeded monitor command succeded. flash download was 0 bytes Success retrieving s3.img monitor command succeded. Monitor succeded monitor command succeded. flash download was 131072000 bytes Success retrieving s5.img monitor command succeded. Monitor succeded monitor command succeded. flash download was 131072000 bytes Success retrieving s7.img No dice "s7" Is the same as "s1" DEBUG: OPS v0.20 (libusb 0.1.10.1) - Use this software at your own risk.The author takes no responsibility for any damages. "Are you ready to download another video of the Kiddos...Please Stand-By...Proceed." If you notice I did not use the Brickmaker Version. I used the regular version. But I tried the Brickmaker and this is the debug on the same camera. BEBUG FROM BRICKMAKER: OPS v0.20.brickmaker (libusb 0.1.10.1) - Use this software at your own risk.The author takes no responsibility for any damages. "I don't feel good don't bother me. I won't write my poem till I'm in my right mind."...Ginsberg Found the camcorder: Pure Digital Inc. Saturn , VID:167B PID:0101 Found camcorder. Connected to camcorder. External key file, saturnkeys.txt was found and will be loaded Camera revision retrieved from camcorder: 03.40 Good news everyone... the retrieved challenge doesn't match response. Attempting unlock succeeded in unlocking camcorder Camcorder unlocked monitor command succeded. flash download was 0 bytes Success retrieving s1.img monitor command failed Monitor failed I attempted twice, this happened twice, I did not go futher then this step. Brickmaker also fails to download videos. Any new ideas

OP20 with a M220 Attempt #1 DEBUG: OPS v0.20 (libusb 0.1.10.1) - Use this software at your own risk.The author takes no responsibility for any damages. "Are you ready to download another video of the Kiddos...Please Stand-By...Proceed." Found the camcorder: Pure Digital Inc. Saturn , VID:167B PID:0101 Found camcorder. Connected to camcorder. External key file, saturnkeys.txt was found and will be loaded Camera revision retrieved from camcorder: 33.19 monitor command succeded. flash download was 131072000 bytes Success retrieving s1.img monitor command succeded. Monitor succeded monitor command succeded. flash download was 131072000 bytes all bytes to hex FF Success retrieving s3.img monitor command succeded. Monitor succeded monitor command succeded. flash download was 131072000 bytes all bytes to hex FF Success retrieving s5.img monitor command succeded. Monitor succeded monitor command succeded. flash download was 131072000 bytes Success retrieving s7.img all bytes to hex FF exited out of ops20(I did not use the close button I closed the window). opened, unlocked, w/brickmaker, upload flash, program appeared to lock up...I closed program (I should have waited) with the result of a dead 220 :? Does anyone wish to kill a worthless 200 or 220 Why not M230's I would attempt again but I am out...I am going back to CVS tonight I will try to find another.

Why not M230's If you enjoy bricking better cameras M230's are fine also, but I think BillW stopped updating OPS at m230 revision 53.05. Please give the OPS guru a chance to fix the brickmaker - your 220 might have been a success except for using OPS 20 which can't upload whole flash. Hopefully you or someone else will try again once BillW figures out the problem with brickmaker. At least you proved the monitor erase commands work on 220s and not on 200s. Please wait for better software before killing anymore.

View Full Version: First firmware rewrite success