Kindle 5.3.2 stuck at reboot

[tommytomtom]

Hi,

I have a Kindle Touch 5.3.2 which is stuck at reboot. Since I don't have a Windows Version handy at the moment, I would like to know if there is another possibility than using MfgTools. I tried to install imx_usb_loader, but I was not able to install it on Mac OS X 10.8.1 because first of all I got the message "imx_usb.c:27:10: fatal error: 'sys/io.h' file not found" and after changing "sys/io.h" to "sys/uio.h", I got 11 warnings and one error "imx_usb.c:509:4: error: non-void function 'find_imx_dev' should return a value [-Wreturn-type]".
Unfortunately, the ENABLE_DIAGS does not work anymore on the new firmware, so easy flashing is not possible. I thought since I have Duokan in the newest version installed, there is a possibility to use that to run a *.sh file? Maybe change the uninstall files to run something, but I am scared that when I run uninstall in Duokan that it doesn't actually use the *.sh files in DK_System/install.
Thank you in advance for your hints!

[tommytomtom]

I can run shell scripts inside of the Duokan installation script. So I can get log files etc. However I do not know how to flash my kindle. Could I somehow force my kindle into diag or fastboot mode or could I downgrade to 5.1.2 with dd?
is it possible to run update_*.bin files with "lipc-set-prop com.lab126.ota startUpdate 1" from a *.sh file?
There must be a way!

Furthermore (might be stupid?), to install something like DuoKan would possible enable something like an artificial ENABLE_DIAG: We could just do the same as Duokan does and use for its updates to run scripts and have a file like DISABLE_DUOKAN to not use it.

[eureka]

Originally Posted by tommytomtom

is it possible to run update_*.bin files with "lipc-set-prop com.lab126.ota startUpdate 1" from a *.sh file?
There must be a way!

It should be possible. You can also try /usr/sbin/otaup /mnt/us/some_update_bundle.bin .

I think, you should definitely try again to getting imx_usb_loader to compile. It will give you control over KT booting independently of firmware behavior, so it's worth more than other ways. Try to replace return; at the error line to return NULL;

[tommytomtom]

Thank you eureka, now I just get 12 warning and imx_usb has been created. However, I guess I am unable to find my kindle in usb_download_mode. Do I have to put any special commands so that the kindle is used in the right way on my mac (of course I hold down the power key until the lamp goes of, then hold down menu key, then release the power key and finally release the menu key)?
by just using imx_usb, I get:
$ ./imx_usb fastboot.bin
parse mx50_usb_work.conf
15a2:0052(KindleTouch) bConfigurationValue =1
Claim failed

[aditya3098]

This imx_usb_loader?
https://github.com/aditya3098/imx_usb_loader

On ubuntu, do:

sudo apt-get install build-essentials libusb-1.0.0 libusb-1.0.0-dev zenity whiptail
git clone https://github.com/aditya3098/imx_usb_loader.git
cd imx_usb_loader
################### If you prefer GUI #################
./imx_gui

######################### Else if you like Tui############
./imx_tui

[knc1]

Originally Posted by aditya3098

This imx_usb_loader?
https://github.com/aditya3098/imx_usb_loader

On ubuntu, do:

sudo apt-get install build-essentials libusb-1.0.0 libusb-1.0.0-dev zenity whiptail
git clone https://github.com/aditya3098/imx_usb_loader.git
cd imx_usb_loader
################### If you prefer GUI #################
./imx_gui

######################### Else if you like Tui############
./imx_tui

Poster is using MacOSx - may be missing the libusb

[eureka]

Originally Posted by tommytomtom

Thank you eureka, now I just get 12 warning and imx_usb has been created. However, I guess I am unable to find my kindle in usb_download_mode. Do I have to put any special commands so that the kindle is used in the right way on my mac (of course I hold down the power key until the lamp goes of, then hold down menu key, then release the power key and finally release the menu key)?
by just using imx_usb, I get:
$ ./imx_usb fastboot.bin
parse mx50_usb_work.conf
15a2:0052(KindleTouch) bConfigurationValue =1
Claim failed

imx_usb_loader is based on libusb. Googling for libusb macos claim failed took me to libusb ticket #89 saying that HID devices aren't supported by libusb on recent MacOS X. USB downloader mode protocol (used by imx_usb_loader) is HID-based and KT in USB downloader mode is recognized as HID device. Ticket is 2 years old, but it's closed as wontfix. (There is also related libusb ticket #33.)

So, I guess, you must to boot into other OS to work with imx_usb_loader. Maybe Ubuntu LiveCD?...

[tommytomtom]

Thank you eureka! That is what I thought. So it would be nice if somebody could write somewhere so that there are not other people like me trying!
Attention imx_usb_loader does NOT work on Mac OS X!
So I now downloaded Kubuntu Live DVD (maybe Ubuntu would be better but I just Kubuntu until a few month ago...) and booted into it.
Thank you aditya3098 for your github and your instructions, just to be easier on freshly installed (K)Ubuntu, there was a typo (no "s" in build-essential) and a few more packages are needed: pkg-config and git
Furthermore, I still need to do "make", don't I?

Anyhow, I am in USB_download_mode:
$ lsbusb
Bus 003 Device 032: ID 15a2:0052 Freescale Semiconductor, Inc. i.MX50 SystemOnChip in RecoveryMode

However, it does not work:
$ ./imx_gui
imx_gui version 1.0
main:Could not open device vid=0x15a2 pid=0x52 err=-3
Booted kindle

What does that mean and what do I have to do?

[eureka]

Originally Posted by tommytomtom

Anyhow, I am in USB_download_mode:
$ lsbusb
Bus 003 Device 032: ID 15a2:0052 Freescale Semiconductor, Inc. i.MX50 SystemOnChip in RecoveryMode

However, it does not work:
$ ./imx_gui
imx_gui version 1.0
main:Could not open device vid=0x15a2 pid=0x52 err=-3
Booted kindle

What does that mean and what do I have to do?

imx_usb_loader requires administrative rights to access USB device. I think running it from root shell (or with sudo command) should solve the problem with err=-3.

[tommytomtom]

Thank you again eureka! But I just figured that out by myself :P