Kubrick: Live CD to debrick Kindle 3, 4, and Touch - Page 4

dsmid · 02-20-2013, 04:44 AM

Quote:

Originally Posted by ixtab

There's still no autologin. Just type "root" when prompted.
(I did try dsmid's suggestion, but the software just wouldn't compile correctly. If anybody is willing to spend the time required to figure this out, feel free to do so. I'll happily include your changes.)

The software can be compiled but has to be patched first.

But you actually don't need it to implement autologin. It's simpler than I originally thought.

Create a new file /root/autologin.sh with these contents:

Code:

#!/bin/sh

exec /bin/login -f root

Modify line starting with "tty1::" of /etc/inittab to look like this:

Code:

tty1::respawn:/sbin/getty -l /root/autologin.sh -n 38400 tty1

Done.
Issue kill -HUP 1 to reload inittab and logout on tty1 (you'll need to kill the java program first) to see it in action.

Tested in VirtualBox with Kubrick 1.1.

BTW Kubrick works in VirtualBox. You need to have the Extension Pack installed and manually select which USB device should be passed through to the machine - once for the USB downloader mode and once again for the fastboot mode.

booklover6 · 02-20-2013, 10:30 AM

Another question, after I have set the computer to boot from the USB stick, and finished everthing with the Kindle, do I have to make any changes to the computer to make it return to booting up normally?

(I've put the image on the USB stick)(If only I had jailbreaked before I upgraded! I just want more margin control LOL)

twobob · 02-20-2013, 10:35 AM

mmm... generally no.

I you changed the boot order in BIOS then it will only select the CD over the Hard drive IF the cd is in...

You can always change it back the original order should you need to. generally MANY machines I come across actually PREFER to boot from CD if one is in the drive... (Kind of makes sense when you think about it)

However: if you didnt do BIOS amends and used the "SLAP FUNCTION BUTTONS TILL BOOTLOADER APPEARS" approach I suggested then that is a one-time deal anyways and will change back the the BIOS defaults next boot.

Cheers

booklover6 · 02-20-2013, 11:26 AM

Thanks, Bob! I'll be trying the slap buttons approach first. Whenever I get up the courage to do so.

ixtab · 02-20-2013, 11:43 AM

New version released, which now features true "autostart" behavior (thanks, dsmid!)

lehbaurd · 02-20-2013, 12:04 PM

Quote:

Originally Posted by dsmid

The software can be compiled but has to be patched first.

But you actually don't need it to implement autologin. It's simpler than I originally thought.

Create a new file /root/autologin.sh with these contents:

Code:

#!/bin/sh

exec /bin/login -f root

Modify line starting with "tty1::" of /etc/inittab to look like this:

Code:

tty1::respawn:/sbin/getty -l /root/autologin.sh -n 38400 tty1

Done.
Issue kill -HUP 1 to reload inittab and logout on tty1 (you'll need to kill the java program first) to see it in action.

Tested in VirtualBox with Kubrick 1.1.

BTW Kubrick works in VirtualBox. You need to have the Extension Pack installed and manually select which USB device should be passed through to the machine - once for the USB downloader mode and once again for the fastboot mode.

@dsmid

After dismal failure of my laptop to boot from the ISO I have got Kubrick working under VirtualBox with extensions as far as the fastboot screen but am stuck at "Waiting for Device". Although my KT is showing up as a USB device but I get an error message that VB can't connect it to the host as the KT is busy with another request. I'd be so grateful if you have any guidance.

knc1 · 02-20-2013, 12:55 PM

Quote:

Originally Posted by lehbaurd

@dsmid

After dismal failure of my laptop to boot from the ISO I have got Kubrick working under VirtualBox with extensions as far as the fastboot screen but am stuck at "Waiting for Device". Although my KT is showing up as a USB device but I get an error message that VB can't connect it to the host as the KT is busy with another request. I'd be so grateful if you have any guidance.

There are TWO (2!) vendor:device IDs that you need to pass to VB, see earlier posts.

booklover6 · 02-20-2013, 01:12 PM

Success with windows 7 64 bit and a 2gb USB stick. I am back to 5.1.2 with jailbreak installed, now to other threads to make sure I have the files I need to do the other stuff.

twobob · 02-20-2013, 01:19 PM

Quote:

Originally Posted by ixtab

New version released, which now features true "autostart" behavior (thanks, dsmid!)

WOOT!

I couldn't think of anything more constructive to say...

If you are looking for input... then Eureka's Fastboot (for FASTBOOT ERASE ALL molested devices) would be a nice addon

dsmid · 02-20-2013, 02:38 PM

Quote:

Originally Posted by lehbaurd

After dismal failure of my laptop to boot from the ISO I have got Kubrick working under VirtualBox with extensions as far as the fastboot screen but am stuck at "Waiting for Device". Although my KT is showing up as a USB device but I get an error message that VB can't connect it to the host as the KT is busy with another request. I'd be so grateful if you have any guidance.

My host OS is Linux thus I don't have any experience with running VirtualBox on Windows.
I suppose that you tried to check the device in VirtualBox USB device list after booting to fastboot mode.
If that gives you the error you mentioned then I guess some driver/app holds the ownership of the fastboot USB device and you need to convince Windows to get their hands off the Kindle in fastboot mode somehow.
In Linux I'd just rmmod the driver but in Windows ... who knows.

ixtab · 02-20-2013, 02:39 PM

Quote:

Originally Posted by twobob

WOOT!

I couldn't think of anything more constructive to say...

If you are looking for input... then Eureka's Fastboot (for FASTBOOT ERASE ALL molested devices) would be a nice addon

It's already there. You just have to use it manually.

( /mnt/kubrick/resources/imx_usb_img/fastboot_standalone.bin )

I wanted to use this one, but it can't be used for the wizard, because it can't reboot the device.

twobob · 02-20-2013, 02:48 PM

AH!!!!

doh! well, I know now

much obliged!

lehbaurd · 02-20-2013, 03:29 PM

Quote:

Originally Posted by dsmid

I suppose that you tried to check the device in VirtualBox USB device list after booting to fastboot mode.
If that gives you the error you mentioned then I guess some driver/app holds the ownership of the fastboot USB device and you need to convince Windows to get their hands off the Kindle in fastboot mode somehow.
In Linux I'd just rmmod the driver but in Windows ... who knows.

Thanks @dsmid

Yep that's just what I did - as soon as I got to the fastboot screen it unchecked the kindle USB device and no way could I get it back. Pity - the SliTaz distro really doesn't like my BIOS so I'll just have to go the long way round to reflash if I need to.

Just so I understand if I did dual-boot my laptop with Linux and ran Kubrick under Virtual Box and got the same error how would I force it to release the Kindle get to fastboot?

cheers

dsmid · 02-20-2013, 04:32 PM

Quote:

Originally Posted by lehbaurd

as soon as I got to the fastboot screen it unchecked the kindle USB device and no way could I get it back.

Beware that a USB downloader mode Kindle and a Fastboot mode Kindle are actually two different USB devices.
After booting to fastboot mode the first device (VendorID Freescale Semiconductor [15a2] in my case) "disappears" from USB bus and a new device appears as connected (VendorID Amazon [1949] in my case).
If, for some reason, the USB downloader mode Kindle is still present in the USB device list after entering fastboot mode, then checking it cannot work and could produce an error.
You need to check a different device in that phase.

Quote:

Originally Posted by lehbaurd

Just so I understand if I did dual-boot my laptop with Linux and ran Kubrick under Virtual Box and got the same error how would I force it to release the Kindle get to fastboot?
cheers

You won't experience such problems in Linux. It just works supposed you have enough privileges to access usbfs.

ixtab · 02-20-2013, 04:56 PM

Just to add to this: You will also have to make sure that once the device is in USB network mode, that one is properly "forwarded" to the VM (not handled by the host). Kubrick expects the default network configuration (192.168.15.*) on interface usbX . On a Linux host, rmmod cdc_ether should make the host system unaware of usb networking devices.

There are 3 different modes that the device enters (USB download, fastboot, and USB network). You'll have to make sure that the VM gets to see all the 3 "devices".

02-20-2013, 11:43 AM	#50
ixtab (offline) Posts: 2,907 Karma: 6736094 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	Version 1.2 New version released, which now features true "autostart" behavior (thanks, dsmid!)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Use regular DX(i) to debrick a DXG	craziskata	Kindle Developer's Corner	10	07-16-2013 09:10 AM
How to debrick a demo DXG?	xcomme	Kindle Developer's Corner	0	02-14-2013 04:06 PM
Trying to debrick, but connection keeps dropping	Zolyx	Kindle Developer's Corner	6	12-10-2012 08:04 AM
Help to Unbrick KT with simple debrick Method.	Loko_bielsa	Kindle Developer's Corner	2	07-16-2012 08:26 AM
A easy and offical way to debrick k3.	xueyou2	Kindle Developer's Corner	3	05-01-2012 09:42 AM

02-20-2013, 10:30 AM	#47
booklover6 Grand Sorcerer Posts: 6,540 Karma: 14008730 Join Date: May 2008 Location: PA (USA) Device: Kobo Clara, 2E, Libre 1, PW4, PW5, 2022 Kindle, Kobo Libre Colour	Another question, after I have set the computer to boot from the USB stick, and finished everthing with the Kindle, do I have to make any changes to the computer to make it return to booting up normally? (I've put the image on the USB stick)(If only I had jailbreaked before I upgraded! I just want more margin control LOL)

02-20-2013, 10:35 AM	#48
twobob ( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr Posts: 6,586 Karma: 6299991 Join Date: Jun 2012 Location: uti gratia usura (Yao ying da ying; Mo ying da yieng) Device: PW-WIFI\|K5-3G+WIFI\| K4\|K3-3G\|DXG\|K2\| Rooted Nook Touch	mmm... generally no. I you changed the boot order in BIOS then it will only select the CD over the Hard drive IF the cd is in... You can always change it back the original order should you need to. generally MANY machines I come across actually PREFER to boot from CD if one is in the drive... (Kind of makes sense when you think about it) However: if you didnt do BIOS amends and used the "SLAP FUNCTION BUTTONS TILL BOOTLOADER APPEARS" approach I suggested then that is a one-time deal anyways and will change back the the BIOS defaults next boot. Cheers

02-20-2013, 11:26 AM	#49
booklover6 Grand Sorcerer Posts: 6,540 Karma: 14008730 Join Date: May 2008 Location: PA (USA) Device: Kobo Clara, 2E, Libre 1, PW4, PW5, 2022 Kindle, Kobo Libre Colour	Thanks, Bob! I'll be trying the slap buttons approach first. Whenever I get up the courage to do so.

02-20-2013, 01:12 PM	#53
booklover6 Grand Sorcerer Posts: 6,540 Karma: 14008730 Join Date: May 2008 Location: PA (USA) Device: Kobo Clara, 2E, Libre 1, PW4, PW5, 2022 Kindle, Kobo Libre Colour	Success with windows 7 64 bit and a 2gb USB stick. I am back to 5.1.2 with jailbreak installed, now to other threads to make sure I have the files I need to do the other stuff.

02-20-2013, 02:48 PM	#57
twobob ( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr Posts: 6,586 Karma: 6299991 Join Date: Jun 2012 Location: uti gratia usura (Yao ying da ying; Mo ying da yieng) Device: PW-WIFI\|K5-3G+WIFI\| K4\|K3-3G\|DXG\|K2\| Rooted Nook Touch	AH!!!! doh! well, I know now much obliged!

02-20-2013, 04:56 PM	#60
ixtab (offline) Posts: 2,907 Karma: 6736094 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	Just to add to this: You will also have to make sure that once the device is in USB network mode, that one is properly "forwarded" to the VM (not handled by the host). Kubrick expects the default network configuration (192.168.15.*) on interface usbX . On a Linux host, rmmod cdc_ether should make the host system unaware of usb networking devices. There are 3 different modes that the device enters (USB download, fastboot, and USB network). You'll have to make sure that the VM gets to see all the 3 "devices".

Advert

Advert