PW3 Bricked device with no serial response

[RnJ4]

Hi,
I have just bricked my device.It stucks at the man-under-the-tree picture when boot up and can not be recognized by computer.When I connected it with serial , it has no response.What should I do now?

What I did before it bricks:
1.Mounted the filesystem to rw (and probably forgot to mount it back)
2.Updated the busybox(extracted from https://play.google.com/store/apps/d...ricson.busybox works normally before it bricks)
3.Installed pip using get-pip.py and installed ftpdlib
4.Changed iptables rules(-A INPUT -i wlan0 -j ACCEPT)
5.Transferred some book to it with ftpdlib
6.Put a screenshot in the linkss folder,and enabled screensavers hack
7.Reboot and BOOM

Which step will probably brick the device?I would appreciate it if you can give me some advice.

[NiLuJe]

I'm going to go out on a limb here and say busybox .

You should *never* replace random binaries in a system that's essentially a black box, even if said binaries might appear to come from "standard"/OSS tools.

(Plus, Android is NOT Linux. You can't assume Android binaries will run on Linux, and vice-versa).

[knc1]

The entire system is highly dependent on the version/build of the Busybox it ships with (which, since this is linux, expects the Linux C library to be present).


Replacing that with a version/build of Busybox built to run on the Android C library (Bionic) -- WITHOUT also supplying the expected library ==



three things have saved you:
*) Your Kindle is dual boot and you have not (yet) trashed the alternate (Diags) system.
*) The update images that Amazon posts are complete (Main) system images.
(And our KindleTool will let you unpack that to get at the files you need for a fix).
*) All of the "HowTo" information is already posted, multiple times, enjoy yourself learning the differences between Amazon/Linux and Google/Linux (a.k.a: Android) embedded systems.

PS: First thing to do is fix your serial port interface.
There are only two ways to prevent it from having an output
*) Complete meltdown of the SoC
*) User error in making the connections (current evidence points at this cause).

[RnJ4]

Originally Posted by knc1

The entire system is highly dependent on the version/build of the Busybox it ships with (which, since this is linux, expects the Linux C library to be present).


Replacing that with a version/build of Busybox built to run on the Android C library (Bionic) -- WITHOUT also supplying the expected library ==



three things have saved you:
*) Your Kindle is dual boot and you have not (yet) trashed the alternate (Diags) system.
*) The update images that Amazon posts are complete (Main) system images.
(And our KindleTool will let you unpack that to get at the files you need for a fix).
*) All of the "HowTo" information is already posted, multiple times, enjoy yourself learning the differences between Amazon/Linux and Google/Linux (a.k.a: Android) embedded systems.

PS: First thing to do is fix your serial port interface.
There are only two ways to prevent it from having an output
*) Complete meltdown of the SoC
*) User error in making the connections (current evidence points at this cause).

That might be the problem. I have poor soldering skill,so I just use tape to connect the wires. It worked well before,but I have no luck this time.Or maybe my converter is broken.I will get a new one and try again next time. Thanks for your advice.

[RnJ4]

Update:Problem solved.
It turned out my converter was broken.I bought a new one and managed to debrick it.
For someone has a same condition to me : You can connect the RXD and TXD port of the converter and type to see if you get the same output.If not,your converter is probably broken like mine.