can't mount fs back to ro

[geekmaster]

Originally Posted by encol

i had only 3 books in it

I was talking about the rootfs full. The "too many books" problem was just an example of code "quality" we have seen from lab126. It is common to leave out error checking in tutorial or demo code, but not real live production code. Except on the kindles, when it breaks...

[encol]

i'm desperate

[geekmaster]

Originally Posted by encol

i'm desperate

Then buy a 1.8v TTL serial port adapter, and follow the serial "debricking" procedure to flash a factory fresh root filesystem. And be more careful with that "mntroot rw" command next time. Most of us have been in your shoes for the same reason, when the serial port was the only way to fix it. In fact, that is the REASON that I (and others) developed the steps needed to debrick a kindle in the first place (to fix our own mistakes).

In fact, now that my PW2 upgraded to a recent firmware without a jaibreak, I need to do the serial port "thing" too...

[encol]

After 4 days battery finally discharged, and the screen with "battery low" appeared.
I connected the kindle in this state and i get:

[   85.113091] usb 2-2: new full-speed USB device number 3 using ohci-pci
[   85.586183] usb 2-2: New USB device found, idVendor=1949, idProduct=dead
[   85.586193] usb 2-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   85.586199] usb 2-2: Product: USB Charger 
[   85.617238] input: USB Charger  as /devices/pci0000:00/0000:00:06.0/usb2/2-2/2-2:1.0/0003:1949:DEAD.0002/input/input8
[   85.673390] hid-generic 0003:1949:DEAD.0002: input,hidraw1: USB HID v1.11 Device [USB Charger ] on usb-0000:00:06.0-2/input0
[   87.732576] usb 2-2: USB disconnect, device number 3

Then, after a long press i get:

[  157.302834] usb 1-1: new high-speed USB device number 2 using ehci-pci
[  157.607932] usb 1-1: New USB device found, idVendor=1949, idProduct=0004
[  157.607942] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  157.607948] usb 1-1: Product: Amazon Kindle
[  157.607952] usb 1-1: Manufacturer: Amazon
[  157.607956] usb 1-1: SerialNumber: G090G1XXXXXXXXXX
[  157.688008] usb-storage 1-1:1.0: USB Mass Storage device detected
[  157.690138] scsi host3: usb-storage 1-1:1.0
[  157.690336] usbcore: registered new interface driver usb-storage
[  157.709684] usbcore: registered new interface driver uas
[  158.700882] scsi 3:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
[  158.702383] sd 3:0:0:0: Attached scsi generic sg2 type 0
[  158.760943] sd 3:0:0:0: [sdb] Attached SCSI removable disk

but i can't mount the disk:

no medium found on /dev/sdb

note the idProduct=dead in the first dmesg

[knc1]

That is correct as far as it goes.

The initialization system exports a 'fake' USB storage until it is ready to provide the actual export.

The first post is also normal for a Kindle without enough battery charge to run normally - that is the "re-charge me" state.

= = = =

Why did you want to intentionally run down the battery?
What was your goal in doing that?

[encol]

Originally Posted by knc1

Why did you want to intentionally run down the battery?
What was your goal in doing that?

i want to see if i can enter in diags mode.

With the battery charged i don't see any usb device when i plug in or when i do the "long press".
Now, at least, usb device was recognised

[knc1]

Originally Posted by encol

i want to see if i can enter in diags mode.

With the battery charged i don't see any usb device when i plug in or when i do the "long press".
Now, at least, usb device was recognised

Nope.
That is the blank 'fake' device, provided when the system can not do anything else before recharging the battery.

Before it passed through these states too quickly for them to be recognized or did not need to enter these states.

It is time for a serial port connection and recover your Kindle over that.

[encol]

Originally Posted by SteveJordan

EDIT : I've set a passcode to unlock the kindle, it's for that ?

I don't know if this can be related to the problem i had, but i also had a passcode when i mounted the fs to rw.
Just to prevent that from happening to someone else

[knc1]

Originally Posted by encol

I don't know if this can be related to the problem i had, but i also had a passcode when i mounted the fs to rw.
Just to prevent that from happening to someone else

I can't think of a reason why but maybe it was related.

I can see that it might get in the way of recovering from an abnormal situation.

So that is probably a good bit of 'safety advice' to anyone messing around with the internals.

[geekmaster]

Originally Posted by knc1

I can't think of a reason why but maybe it was related.

I can see that it might get in the way of recovering from an abnormal situation.

So that is probably a good bit of 'safety advice' to anyone messing around with the internals.

Agreed. Get rid of a passcode before changing anything on rootfs, until you are done and it is proven to be reliable. This makes it easier to repair if you break something on rootfs. I never passcode mine though, so the thought of this extra step did not occur to me until learning it from somebody who does use a passcode.

[knc1]

I put it into the 'preparations' section just as a matter of principle.