|
I have given up on it after lots of trying. D:
I started thinking that since knc1 said that USB Downloader was the selected bootup process if the other firmware didn't work or was broken, that it had to be the rootfs. After toggling the powerswitch ~250+ times, I got the kindle to come up in serial mode long enough for me to find out that the userstore was corrupted......
So, that led me to think that /mnt/us got corrupted by a hack somehow (I have no idea which one), and then confused the bootloader, which caused it to boot into USB Download mode.... After 3 days of trying to get the kindle back into usb_serial mode, I gave up and called Amazon..
As I was talking to the CS rep, I voiced aloud that 3.4 (or an OTA update to prepare for it) might have broken the Kindle. After some time, I was told that I was getting a new K3 free of charge, with 2-Day shipping, as long as I sent the broken K3 back to them. I was also told that they were going to make sure someone double checked the K3 they are shipping me for any problems, and that they would put 3.4 on it for me.
I don't think that they will be able to get anything out of that broken Kindle though.....
My new K3 is supposed to arrive Wednesday or Thursday. I will use K3flasher to dump the new kindle as soon as I get it, if it comes with 3.4.
@GM: How does one replace /etc/shadow with the DES mario hash? can I just mount the 3.0.2 image and steal it from there? (provided there are no other changes between the two files)...
|