First off Here...

item3="This Navi product is intended solely as a driving aid. Review instruction manual and select route before driving. Navi is not a substitute for your attentiveness, judgment, and care while driving or moving your vehicle. Always observe safe driving rules and driving laws, and follow road signs even if they contradict Navi's instructions. By pressing OK key, you accept the license agreement in the instruction manual."

Second now that this had been found we can find a work around for it!!! yay...

Anyway its located in the MainRes.Res file (use whatever zip u got) and its in the main.cfm file...

now to find out a way around it.

Well I went into the MainRes.Res file and edited the message. All I did was change the text. My plan was to see if the text did indeed change on the nav unit, then we'd know for certain we were on the right track. (We've had a few red herrings within the navi software after all.)

So I made my new MainRes.Res file, copied it to the F700 after moving the original to MainRes.bak. Then I rebooted and waited for my new message.

And waited, and waited. The 'starting...' screen was there for ever. Well, big sigh, didn't work, but I figured no worries, it just wasn't reading the new MainRes.Res file. Turn it off, put the testmode card in, turn it on.

And wait. And wait. And wait.

Oh crap it's not going into test mode....

I start thinking, what do I do? Kill power totally? Cut the yellow line? Hit the reset button? I can't believe I've bricked it. Shit.

Well, I kill power then with crossed fingers, turn it on again. Huge sigh of relief, it goes into test mode. I delete my modified MainRes.Res and restore the backup. Toggle power and it boots up ok. Well mostly ok. It has definately done a master reset on itself, erased some settings etc. But it isn't bricked!

Yay!

I don't know what I did wrong. Maybe it does a CRC check on the MainRes.Res file. Whatever happened, it gave me a good fright this morning.

Think I'll sit back now and let someone else work on the safety message for a while.

So wait, all you did is change the text? I dont understand how it knows the new file isn't the original if it just looks for the file name, no? and what's a CRC check?

I'll attempt it and see what I can accomplish, but I'd like to know what I"m doing before I mess with some major files.

Cyclic Redundancy Check.... The simple version: does a math problem on the bits that make up a file and come out with a 32 bit result. If you change something in the file it changes that output result. If its different than expected the unit may think its corrupted and not boot.

http://en.wikipedia.org/wiki/Cyclic_redundancy_check

It's possible I messed something up, I've got a cold or flu or something and I'm kind of dizzy and befuddled. But I thought I had done everything ok, all i had changed was the strings table to edit the warning text.

Whatever I did though, it prevented the thing from booting, and made me think it was bricked when testmode failed the first time around.

If they did want to ensure people didn't tamper with the main software though, doing a crc or some other kind of check against the mainres.res file would certainly make that a lot tougher.

As an aside, I wonder if this is part of the reason the thing boots so slowly - it has a lot of compressed files to uncompress before it can actually do anything. That doesn't seem like a good design, IMHO.

Before reading my post, check here first and look at his caution screenshot:

http://www.avic411.com/forum/viewtopic.php?t=17590

if a CRC check goes by a certain exact number created by the caution file, then wouldn't changing the background of it too change that number??

Before reading my post, check here first and look at his caution screenshot:

http://www.avic411.com/forum/viewtopic.php?t=17590

 

if a CRC check goes by a certain exact number created by the caution file, then wouldn't changing the background of it too change that number??

no the background is in the image.res they might not of put a security on that... mainres.res could be different i was looking in that file but didnt try any changes so :/

Well how exactly does a CRC make sure everything is in check? does each character have a certain value? does it count how many characters are in the actual text? It has to follow a certain guideline to know that the file is not the original, even when the new one has been renamed, or it could maybe be as simple as a hidden file within the original that hasn't eben included in the new one...

"Cyclic Redundancy Check

Definition: (1) A method to detect and correct errors by adding bits derived from a block or string of bits to the block. (2) An algorithm to compute bits characteristic of a block based on the algebra of polynomials over the integers, modulo 2. (3) The characteristic bits of a block.

Also known as CRC.

Note: Large blocks may be probabilistically compared by precalculating the CRC for each block, then comparing their CRCs. If the CRCs are different, the blocks are different. If the CRCs match, there is a small chance that the blocks are actually different. This probability may be made arbitrarily smaller with more CRC bits. "

From what I've read, crc mainlly concerns data transmission, and reception??????????????????????????????????????????

CRC was used in the past for data transmission (Usually the methods used in communications are much more complex than CRC and sometimes will involve a combo of horizontal and vertical redundancy checks along with CRC), but it is also used a lot to check the integrity of a file.

Example: Automatic error recovery.

Your computers operating system tries to start up and fails. Next startup it runs a CRC check on all important files and finds one that does not match the correct CRC. Next, the operating system replaces the bad file with a known good copy. Voila the system will now start up.

CRC is basically a universal "make sure the file is good" checker.

CRC's aside, I might have messed something up. Sick, drugged, befuddled, etc.

I'm still a little gunshy about playing with the .res files however, so I'm not going to try again -- at least, not for a while.

Has this topic been dropped? Interesting to find out what happened.

were pretty sure the caution msg is built into an .exe which means you would need to reverse engineer it and remove it... dont think any of us have any of those skills so sorry but were outta luck

In executable's disassembly there is a reference to the UI state that displays legal message. If anyone knows ARM assembler, it should be possible to jump around it...

I know a guy who does this sort of programming but i cant convince him to work on it for me because he doesnt use the it so its useless to him he says maybe i can bribe him

Buy him a beer

umm never mind that did you see the guy on here "leetcoder" i'm sure he could do it in due time seems very knowledgeable

To me this would be the best hack for this avic hu. I hate seeing that startup screen and having to press OK while I'm driving, it's more hazardous than the message itself.

If he knows how to hack executables in ARM assembler, he should be able to do it.

I'm new to the Pioneer F series but definitely not new to disassembling or programming. What's a quick run-down of getting my unit into test mode so that I can pull the files and start hacking. I assume I'll need to use my SD card for this.

I'm new to the Pioneer F series but definitely not new to disassembling or programming. What's a quick run-down of getting my unit into test mode so that I can pull the files and start hacking. I assume I'll need to use my SD card for this.

Shafty,

Start here "Guide to Mods"

http://www.avic411.com/forum/viewtopic.php?t=18327

Testmode file are available for your SD card here

http://www.avic411.com/forum/viewtopic.php?t=17542

After you got there, interesting files would be ezrider.exe in APL2/igo directory (that's the main iGO executable) and MainMenu.exe and AV.exe in the /APL directory

After you got there, interesting files would be ezrider.exe in APL2/igo directory (that's the main iGO executable) and MainMenu.exe and AV.exe in the /APL directory

Just to be clear, the test mode files are only used to boot the deck into test mode correct? They are not all of the files that I will find on the unit itself once I boot into test mode? Once in test mode, will I be able to copy all of the files onto my SD card or onto a USB drive or both? Thanks guys/girls

That's right. Testmode files allow the unit to boot straight to WinCE desktop without launching the AVIC shell.

Once in Windows, close the Copying messagebox, launch Windows Explorer from Start button, and you have access to AVIC's file structure.

My Flash Disk\APLxxx directories are where main executables are.

If you have a laptop, I ewas told that you can connected it to AVIC's USB cable, switch AVIC to USB Client mode (Control Panel\USB CLient Switch) and copy files ditrectly to your computer. Otherwise, use Explorer on the AVIC to copy files to SD Card or a USB drive.

Has anybody been able to solve this? I hate that warning screen.