View Full Version : Firmware V1.15 problem?!!!
I have managed to get the iAudio7 equivalent of the PC "blue screen of death" on my iAudio7.
Below is what happened after attempting to go back from V1.15 to V1.13. When I turned on the unit, it all looked good with the firmware upgrading etc on restart the iAudio7 logo played as normal but the screen turned out as below. Since then I have:
-Tried reflashing, no good
-Tried resetting, no good.
-Tried earlier firmware version which seems to load ok but still ends up as below.
-Tried reformatting and then reflashing, no good still get the same result.
Each time the unit turns on it starts normally and then goes into the white screen. You can scroll up and down but obviously this leads nowhere. And when you turn off the unit is says goodbye as normal
Funny thing is that the all the correct system files and folders show up when the unit is connected to the PC and I can drag and drop music on to it.
Anybody any ideas before I send it back to AMP3? [sad]
Looks like the font is broken.
Try this - download some U3 firmware, the font file there is called data2.dat
Rename that file to I7_FO.BIN and copy to the player.
Looks like the font is broken.
Try this - download some U3 firmware, the font file there is called data2.dat
Rename that file to I7_FO.BIN and copy to the player.
Doesn't work, or make any difference, thanks anyway [no]
This is why I tend to leave testing new releases to the impetuous :-)
BTW has anyone successfully downgraded a firmware release, is this a 1.15 -> 1.13 issue or just a general downgrade issue?
Another thought, perhaps your f/w download is corrupt, get another copy and do a comparison
Another thought, perhaps your f/w download is corrupt, get another copy and do a comparison
Tried that...[no]
Ask customer support at http://support.cowonamerica.com/
They have the answer for U3 for the same problem (in FAQ), so...
Heller_Barde
08-22-2007, 04:30
You tried reflashing it with 1.15, right? and you did delete everything before that, right? Strange thing, that is...
Another question.. Why would you want to downgrade? [confused]
mh I really hope you get your player to work again... Btw, What happens if you just press play in the white screen there?
You tried reflashing it with 1.15, right? and you did delete everything before that, right? Strange thing, that is...
Another question.. Why would you want to downgrade? [confused]
mh I really hope you get your player to work again... Btw, What happens if you just press play in the white screen there?
Tried deleting eveything and reflashing...no good[no]
Tried deleting every and then formatting and then loading firmware...no good[no]
GSV3MiaC
08-22-2007, 04:54
Send it back to AMP3 .. seems like some part of the Flash memory has maybe died, or perhaps the chip itself. Could be related to the Flashing new firmware, or could just be a complete co-incidence.
Does pressing the Master Reset button (under the flap) help at all.
Clutching at straws, I know [sad]
K.
I already explained, it's a font thing, it's not hardware. The bug happens on U3 too, and is easily fixed by re-installing a font file.
Of course, the official i7 firmware contain no font for some reason, but inside the firmware there are strings
I7_FW.BIN
I7_FO.BIN
I7_RS.BIN
That's why I suggested installing a font file named as I7_FO.BIN
If you're sure you done it correctly (extension in indeed .bin and not .bin.dat where .dat is hidden by windows) and it still doesn't work, then ask Cowon.
GSV3MiaC
08-22-2007, 11:53
The only problem is that installing random bits of firmware may not fix the problem, but may well invalidate your warranty. Besides which if it screwed up once, who wants to risk whether it will do it again .. probably when the warranty has just expired ..
Define "random bits of firmware" as I don't understand this term.
GSV3MiaC
08-22-2007, 13:35
Something other than an official Cowon 1.xx firmware release package.
I am returning the unit for a replacement, after spending a while trying all the suggestions in this thread.
Thanks everyone for all you help.
I reckon the unit is defective somehow and in this case this is the best thing to do is to return it for a new one [wink], especially given that it is only 3 weeks old.
Something other than an official Cowon 1.xx firmware release package.
I don't see you complaining about font patch or screen themes for D2.
I'm just trying to help.
I don't see you complaining about font patch or screen themes for D2.
I'm just trying to help.
Wow, touchy! I think he was just pointing out that installing any of these various firmware patches that don't a) come directly from Cowon or b) aren't specifically intended to be used with other devices (like the U3 font files) could invalidate your warranty. Calm down a bit.
GSV3MiaC
08-22-2007, 16:19
I don't see you complaining about font patch or screen themes for D2.
I'm just trying to help.
I'm not complaining, I'm just pointing out that desperate attempts to fix a unit which is well inside warranty are not necessary, and may get you deeper in a hole. If the unit was out of warranty, then anything goes. Yes, I know you were trying to help, and I know it has worked on a U3. That doesn't make it a great idea though.
Screen themes are not a problem as far as I know. The font patch might be, if the unit then died, but that is not likely. However in this case we KNOW we have a DEAD unit .. 100% certain the unit is DEAD right now; that makes doing anything that even 'might' upset the vendor rather risky IMO.
Even if applying a font-only-flash worked, the issue remains that this unit has failed once already. It shouldn't do that. Personally I'd rather send it back now while it is 'dead' and hope to get a new one than 'fix' it and then sit wondering if it might die again (you can no longer send it back for replacement if you manage to get it working again).
Anyway, lighten up and don't take it personally .. you can still do what you like to your units. 8>.
Wow, touchy!
Well, considering that most of those third-party patches are mine...
aren't specifically intended to be used with other devices (like the U3 font files) could invalidate your warranty.
Cowon uses the same font for U3, F2, D2, i6, i7, X5...
However in this case we KNOW we have a DEAD unit .. 100% certain the unit is DEAD right now; that makes doing anything that even 'might' upset the vendor rather risky IMO.
We KNOW the problem happens on U3, and we KNOW it's solved on U3 by installing the font file.
It's in official Cowon FAQ.
Well, considering that most of those third-party patches are mine...
Yes, I know. That was why I thought you were being touchy in the first place.
Cowon uses the same font for U3, F2, D2, i6, i7, X5...
Yes, I know. The point was that in general, installing unofficial/semi-official/modified firmware files will tend to invalidate your warranty. Maybe that isn't the case for the Cowon fonts, but it's the sort of thing you're quite likely to see in the vast majority of warranty agreements.
GSV3MiaC
08-22-2007, 18:29
We KNOW the problem happens on U3, and we KNOW it's solved on U3 by installing the font file.
It's in official Cowon FAQ.
Yes, but you will have probably noticed an I7 is not the same as a U3. The font (as displayed) may be the same, but there is no guarantee that the .bin file for a U3 is going to put the right data in the right place in memory. Yes it might work (turns out it doesn't) but it might screw things up (turns out it doesn't do that either). Why take the risk with a $300 (in the UK) piece of electronics when the vendor (AMP3) will swap it for you by return post?
If/when Cowon provide a similar FAQ for the I7, and an appropriately named font.bin, it will become something that you can try without risk, before RMA'ing your player - today that isn't the case.
[Even on the U3, I'd really like to know WHY the font file gets screwed up, rather than them just saying 'here's how you can fix it' (until the next time).]
Anyway - 'peace'. We were both trying to solve the guy's problem, I was just trying to do it with not even the faintest risk to his warranty.
Yes, I know. That was why I thought you were being touchy in the first place.
And I'm telling you that I have a perfectly good reason for it. So I'm going to ignore your advice.
Yes, but you will have probably noticed an I7 is not the same as a U3.
I noticed it's very similar.
[Even on the U3, I'd really like to know WHY the font file gets screwed up, rather than them just saying 'here's how you can fix it' (until the next time).]
If you ever tried to solve computer problems (software) you know it's exactly the opposite. It's much easier to fix things, then to figure out what exactly went wrong.
Anyway - 'peace'. We were both trying to solve the guy's problem, I was just trying to do it with not even the faintest risk to his warranty.
Well, of course the universal advice "just send the player back" works for every bug, but the guy is probably aware of that method, and he's trying to find something else.
GSV3MiaC
08-22-2007, 19:39
I spent 25+ years fixing software, all the way back to 4-bit calculator chips, all the way up to 308x series mainframes. And I definitely know that 'fixing it' when you don't know why it broke is just a recipe for it breaking again at some more embarrassing time. Yes, it is harder to figure out causes than to patch symptoms - it's also more useful.
'Send it back' is expensive if it is out of warranty .. I'd cheerfully take a screwdriver (or software equivalent) to it under those circumstances, or if it was a cheap bit of kit. If you check the forums you'll note that I regularly suggest all sorts of non-destructive attempts to fix problems rather than just 'send it back', but in some cases, with defects in new and expensive bits of kit, 'send it back' is the sanest answer. The guy was aware that sending it back was AN option, I merely pointed out that (IMO) it was the BEST option.
So anyway, that's my final comment on the subject - keep up the good work on font patches.
And I definitely know that 'fixing it' when you don't know why it broke is just a recipe for it breaking again at some more embarrassing time. Yes, it is harder to figure out causes than to patch symptoms - it's also more useful.
With the modern million-lines-of-code software like Windows, you could spend months just to find out: oh, this particular registry key breaks this particular driver. But you'll never know why, without access to the source code.
But cleaning the registry, reinstalling the software only takes minutes.
The guy was aware that sending it back was AN option, I merely pointed out that (IMO) it was the BEST option.
Asking customer support isn't a bad option either. That's how U3 answer got into FAQ - somebody asked.
So anyway, that's my final comment on the subject - keep up the good work on font patches.
Thanks!
GSV3MiaC
08-23-2007, 15:42
With the modern million-lines-of-code software like Windows, you could spend months just to find out: oh, this particular registry key breaks this particular driver. But you'll never know why, without access to the source code.
But in the case of the 'U3 font breaking' Cowon HAVE the source code (and it ain't even a million lines). Which is why I'd like to know WTF is going on (I wasn't suggesting you/I try to figure it out, I was suggesting Cowon might like to figure it out and fix it).
Which is why I'd like to know WTF is going on
They aren't going to tell us.
Besides, if it happens rarely, they may have trouble finding the bug. So maybe they don't know either.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.