Rockbox mail archiveSubject: Re: iRiver On button Problem
Re: iRiver On button Problem
From: Liberman Shachar <Road_Runner_at_barak.net.il>
Date: Thu, 28 Jul 2005 13:59:00 +0200
My experience is based not as an engineer, but as one that had his player
crashed five times (that is 5 times!) at the one warranty-year... : /
(I've fried my player using 12 AC voltage, It bricked after two separate
times of bad firmware upgrades... one time the main lcd screen broke...)
Anyways, I really don't think this is caused by the battery - as if it was
you just couldn't use it at all. If it's really fried it's all the way DEAD.
Bad firmware upgades can cause lots of stuff. for me at the 1st bricked
player it was because a firmware upgrade didn't turned off the player after
waiting for more then 5 minuts. I reset the player and it worked for one
last time. after turning off it never came back on.
Please make sure that you are using the right origin upgrade for your
player, I believe that was a factor.
try to update with the bootloader installed/uninstalled - whatever you
didn't do the last time.
F.Y.I, Iriver still fixes bricked players, Even after warranty voides.
Usually they don't charge you for nothing But they only fix them in Japan...
other way, Try finding someone with a BDM controller and reflash the
firmware. I think this is way cooler ;)
"Mat Holton" <mathew.holton_at_surface-inspection.com> wrote in message
> Hi there,
> Can anyone help me?
> I recently recieved a 'broken' iRiver H120 from my brother. He had been
> charging it with a Nokia charger.
> I've looked into the spec of the Nokia charger and the polarity is the
> same as iRiver charger (center positive).
> The difference is the voltage and current, both less than the proper
> It's now charged fully using the proper charger.
> The problem is that it doesn't come on! Well, it does by only by pressing
> the reset button.
> My brother also mentioned that he tried to re-flash the firmware but it
> froze half(?) way, i.e. it didn'y gracefully exit in the correct way.
> This sounds like it may have caused the problem (I neglected to ask if the
> problem was there beforehand).
> And the same thing happens if I try and re-flash now. But it still boots
> up with reset.
> Does anybody have any clue as to how to solve the problem or does it sound
> like it's a hardware fault, perhaps causes by a faulty firmware upgrade
> Perhaps if it was low on current, the firware didn't flash completely? Or
> would it just not work at all?
> any help would be great,
Received on 2005-07-28