some information? to repair StoryHD freeze or brick

[ladysveil]

sorry about my english is very low.

i was try to repair freeze from boot of storyhd at iriver c/s of korea.

but failed recovery and find something (three point in PCB<T1, T2, Gnd?>)


iriver's Engineer try to recovery to system area (/dev/mmcblk0p1~3) and bootloader

maybe used sometool (JTAG tool?) the a point in PCB at c/s of iriver.(look at a red box)



i don't know more infomation

[frostschutz]

So basically you are saying that iriver customer service (and not you) soldered T1, T2 and GND? It could be the serial console as that needs three pins (one for sending, one for receiving, and gnd).

That would be interesting news, if they actually succeeded debricking the device with it...

I have my doubts though, as the monstrous blob of solder they put on the GND area looks a lot like someone didn't know whatever the heck he was doing. And T1 and T2 are not just one but two pads each. So that doesn't seem right either.

It could be JTAG but there already are labeled JTAG pins on this board (TCK, TDI, TMS, TDO, TRST) which aren't soldered. I tried soldering those but failed because they are so small.

Does anyone else have a debricked Story HD from customer service and would be willing to open it up and make a good picture of the PCB? https://www.mobileread.com/forums/sho...d.php?t=143798

[ladysveil]

So basically you are saying that iriver customer service (and not you) soldered T1, T2 and GND?

---------------------------------------------------------------------------------------------------


the soldered by iriver's c/s engineer

i am not.

[ladysveil]

.....

[frostschutz]

Originally Posted by ladysveil

the soldered by iriver's c/s engineer

But they didn't fix it?

Thanks for clarifying.

T1 and T2, hmmm

[ladysveil]

Originally Posted by frostschutz

But they didn't fix it?

----------------------------------------------------------------------------------


Iriver Korea officially does not support the Story HD.

only support a story K & a story K HD.


the story K downGrade from the Story HD.
the story K HD almost same the Story HD. but some difference a software(like a partition size)

I think probably anything else that the recovery program


Anyway,

I found a little more signs of soldering from C2



In summary

C2 - VCC
GNC
T1
T2

[frostschutz]

I don't see C2, where is it?

[ladysveil]

Originally Posted by frostschutz

I don't see C2, where is it?

look at attachment

[frostschutz]

Interesting. So that's 6 points in total, possibly for a serial console (GND, CTS, VCC, TXD, RXD, RTS). GND is the blob, VCC is C2, and the others are T1/T2 which are two pads each, exact order yet to be determined.

I guess it's worth a shot. I'll spend another €20 on a serial cable such as this http://www.delock.de/produkte/N_83117/dokumente.html and see if I can ruin my bricked Story HD some more with my horrible soldering skills. Sigh.

the story K HD almost same the Story HD. but some difference a software(like a partition size)

Story HD Basic has 2 partitions Story HD Wifi has 3 partitions.

1 partition for system files (firmware)
1 partition for user files (ebooks)
1 partition for downloaded updates (wifi only)

Software is slightly different for each country, due to different keyboard layout / ebook shop solution.

If the serial console actually works and gives raw access to the internal memory somehow, or even just the shell, unbricking would be possible. Brick in my case is most likely caused by a surplus library file / file in the wrong location as it happened when installing Story HD Basic firmware archive on a Story HD Basic running Story HD Wifi firmware. :^)

[frostschutz]

Originally Posted by frostschutz

I guess it's worth a shot. I'll spend another €20 on a serial cable such as this http://www.delock.de/produkte/N_83117/dokumente.html and see if I can ruin my bricked Story HD some more with my horrible soldering skills. Sigh.

So I bought this, and a Piezo buzzer... and tried using this method here http://wiki.openwrt.org/doc/hardware....buzzer.method on the T1+T2 pads to find out which is which.

For T1, the pad on the right, and for T2, the upper pad, produce the screeching/modem sound. Unfortunately they do so all the time (whether it's booting or not). The other two are silent all the time (also during boot).

I tried to blindly connect just GND and RXD but failed to get output for any of the pads. I got a single "?" for the lower T2 pad, and nothing for the others. Not sure if it's even supposed to work at all with just GND/RXD/TXD but that wiki page suggests it.

I was expecting to find a single pad that produces some noise during boot, instead I found two that produce noise nonstop and two which are completely silent.

So I'm stumped again. I just don't know enough about electronics.

[CJJ]

The fact that you try and persevere puts you in the company of people like Thomas Edison. So good for you. Eventually you may figure something out and we will all benefit.

[ladysveil]

my story hd was broken by mistake of soldering