I think the target now is to get a HV20 and not decide the future of something we don't have.
I think the target now is to get a HV20 and not decide the future of something we don't have.
I finally got the new Flip Hack to work on my HV30. Thank you jolly and herbert for the previous replies and help.
Can anybody tell me how to make a donation for these efforts. I apologize if it's already been listed in this thread, I just haven't been able to find any info on it.
Thanks again guys.
Hello Cabism, I am glad to hear the hack works correctly.Originally Posted by Cabism
The donations have been suspended a few months ago, so there isn't any way to donate at this point in time, I appreciate your thought!
Jolly
So what was wrong? We thought (I thought) partialy-working HV20 is being sent to Jolly to try hacked software, but it seems it is not...
It was, but it was too broken even for that. Haven't you read all previous posts?
Thanks for answer. I haven't red everything, Im afraid.
Here we go. $240
http://www.hv20.com/showthread.php?38566-FS-Canon-HV20
any luck with a flip for the hv40? its annoying, ive already bought a monitor but i really hate waiting! lol
You're just gonna have to wait... Jolly has other priorities.but i really hate waiting! lol
Read the damn thread... The hack is currently only for the HV30. So you'll either have to strap a mirror to your LCD, or mount your monitor upside down...
What good does it do to tell people to read the thread when they clearly don't read the thread to know they're supposed to read the thread? But seriously, it'd be great if people would read the thread.
So Phil, here's the scoop: All hack work is being done on the HV30 because that's the only model for which Canon released a firmware patch. It MAY be determined that the hacked HV30 firmware can be flashed on an HV20, but if you were to do that to an HV40 you'd lose native 24P, which would be kinda dumb. Unless you can find someone to make a super tiny (and reliable) JTAG connector, the HV40 will likely remain unhacked, or potentially downgraded to an HV30, but don't hold your breath. Oh, and if you don't know what the JTAG port is, use the search function in this thread to enjoy that drama.
Jolly - go for it!
I have PM'd the person selling the cam as well as SDeming, the problem is this person only has one post and there are no pictures which usually results in someone getting ripped off.
I have also made a post in the buy/sell area about wanting to purchase a HV20 for the hack.
Current bid is $255 US. A little over 1 day left in the auction.
http://cgi.ebay.ca/Canon-HV20-barely..._Video_Cameras
Bird
I would be willing to put my hv20 on the line if we all made an agreement that in the event that it was bricked, the fund would buy me a replacement. There are 2 good things about this: We could test it now, and if it worked the fund would remain untouched.
I offered the same thing a couple weeks ago, the concensous was there is no reason to test on a fully working cam, the problem is it is taking forever to find one that is not totally functional at a decent price. The one currently on ebay that has a faulty lens cover is already priced more than I paid for my last HV20.
> an agreement that in the event that it was bricked,
> the fund would buy me a replacement.
Good idea. I can't see any better solution! As finding/buying/sending a suitable, partly-broken HV20 could be endless. So what now - voting? Well, my hand is up!
Jolly, could you work with someone over the internet on this? Or would you need their camera?
The hack fund cannot guarantee that we'd be able to replace your camera. I mentioned how much is still in the fund above. Just a quick view of ebay tells me the buy it now price is $550.00. That's more than we have in the hack right now. So we may not have enough to replace your hv20 outright. We could give you what's left in the fund, but that may not be enough. So on the one hand we may gain everything by trying this, on the other (if the camera bricks) then we may loose everything and you would have to foot the bill for buying the rest of your camera back. Just saying.
This sounds like a good solution, but if Jolly needs to mess with the camera himself, it may not be so great. I'm surprised how expensive these cameras are now. Who would pay that much?
My preference as you can guess would be to have the camera here, as the method I intend to use to try flashing the HV20 with the HV30 firmware is completely untested.
I suppose I could give someone else the instructions, again though this has a very good chance of bricking the camera, so please think carefully about it and let me know if you want me to go ahead and prepare the "package".
I would need to at least talk to the HV20 owner over skype when he/she attempts the update...
Jolly
> I mentioned how much is still in the fund above.
So lets rise the funds. If some of us would offer a donation of lets say 10USD, we could easily afford that. I could donate by PayPal if there will be more volunteers like me. Any more hands up..?
I can do this. I live in Poland. My camcorder is HV20 NTSC. I have got a PayPal account and I have got Skype. I assume that in the event of fail, I will get $521.37 , right ? If so, I am more than happy to do this. Of course, sending my cam from Poland to Canada is not worth, but I can update my cam with HV30 sofware provided by jolly. I am just not a patient type of guy, I want to know if that hack will work on HV20 or not right away. Just let me know if you want to do this.
If more money is needed, there are a lot of people willing to donate who did not had a chance to do so (me included).
Though, I reckon it would be much more productive for jollyrogerxp to have the camera in his hands: in case of a brick, he can go back to trying the JTAG port again.
It appears a HV 20 won't accept the hack, read this thread:
http://www.hv20.com/showthread.php?3...859#post348859
Hi Janke,
using the normal firmware update procedure is not the way to try flashing the HV20 with the HV30 firmware.
The Canon PC-based uploader checks the camera model and compares it to a string contained in a configuration file, so it doesn't work.
Even changing the configuration file, the HV30 firmware still doesn't work on a HV20 using the normal update procedure; the HV20 checks it and ignores it as not compatible.
I have studied the HV30 firmware update procedure in detail in the disassembly, and there are a few checks the camera does to decide whether an update file is valid.
One or more of these steps must be a little different on the HV20, otherwise the update file would be recognized.
While disassembling the code I discovered a hidden firmware update procedure that uses unencrypted firmware files and skips a few of the checks.
One single check remains though, and it seems to be related to a specific two-bytes code that is probably different for each camera model.
The main issue is that we do not know this particular code for the HV20, so if I had a HV20 here I could run some attempts to detect this code before trying to use the hidden update procedure.
The big problem we face is that there are two separate firmware files to use with the hidden procedure, one for each of the two main processors; the hidden procedure performs some checks only on one of the two files, the other one is flashed without checking.
This is a concern: if running the hidden procedure we flash only one of the two files because the other is discarded due to the check, then the chance of bricking the HV20 increases by a factor, as those two pieces of firmware are supposed to work together...
I hope this is clear enough to explain what we are facing.
Jolly
No offense vwrafi, but having someone other than jolly do the HV20 firmware "test" is not a very good option.
I suggest patience, and a way to get a cam into jolly's hands.
Here's a deal for 2 hv20's going fast!
http://cgi.ebay.com/2-Canon-HV20-Min...item4cf135dbdf
I almost jumped on that auction myself, 2 HV20's for $650 with extras. Not a bad deal.
Reply With Quote
