Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 04-13-2019, 12:38 PM   #1
RnJ4
Junior Member
RnJ4 began at the beginning.
 
Posts: 9
Karma: 10
Join Date: Apr 2019
Device: Kindle Paperwhite3
Bricked device with no serial response

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.
RnJ4 is offline   Reply With Quote
Old 04-13-2019, 01:54 PM   #2
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
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).
NiLuJe is offline   Reply With Quote
Advert
Old 04-13-2019, 06:18 PM   #3
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
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).

Last edited by knc1; 04-13-2019 at 06:22 PM.
knc1 is offline   Reply With Quote
Old 04-14-2019, 12:56 AM   #4
RnJ4
Junior Member
RnJ4 began at the beginning.
 
Posts: 9
Karma: 10
Join Date: Apr 2019
Device: Kindle Paperwhite3
Quote:
Originally Posted by knc1 View Post
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 is offline   Reply With Quote
Old 04-19-2019, 10:08 AM   #5
RnJ4
Junior Member
RnJ4 began at the beginning.
 
Posts: 9
Karma: 10
Join Date: Apr 2019
Device: Kindle Paperwhite3
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.
RnJ4 is offline   Reply With Quote
Advert
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Troubleshooting Kindle PW3 bricked "DIAGS EXIT Please use serial port" neverthesane Amazon Kindle 2 05-20-2018 02:27 PM
Aura H2O Device bricked? Apofis Kobo Developer's Corner 3 06-04-2017 06:13 AM
In case your PW got "bricked" / stuck in Diags Exit please use serial port justaheadsup Kindle Developer's Corner 1 05-02-2017 07:40 PM
Can I rescue a bricked Kindle Paperwhite 3 without serial port? Mr.Samuel Kindle Developer's Corner 10 12-31-2016 04:29 PM
K4 Mac or PC No Kindle Device. Does He Have a Serial Number? CrossReach Amazon Kindle 1 08-10-2016 05:47 AM


All times are GMT -4. The time now is 10:44 AM.


MobileRead.com is a privately owned, operated and funded community.