Thread: Damn Reboot using the shell
View Single Post
Old 06-19-2012, 06:02 PM   #55
wlaf
Enthusiast
wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.
 
wlaf's Avatar
 
Posts: 44
Karma: 40820
Join Date: Jun 2012
Device: Kindle 3 WIFI
Quote:
Originally Posted by dasmoover View Post
I have a K3G on firmware 3.3. I can provide a simple dd img backup if you would like.
I would be thankful if you send me link of a zipped version of the dd backup via PM. Any suggestions for a good dd backup, guys?

Btw, I found this page, that has great information about Kindle 3. The title of the post is:
"Kindle 3 Discovery Tour: Kernel Config, Processes, Programs, Modules, /proc, cpuinfo, dmesg, meminfo, mounts, fstab and other Inside Information (Firmware 3.1)"

http://linux-tipps.blogspot.com/2011...el-config.html
Quote:
Originally Posted by knc1 View Post
For the purposes of this thread (with a working u-boot and a working kernel+initramfs) ....
In u-boot, add: rdinit=/bin/sh (or /bin/ash if that doesn't work) and then tell u-boot to continue the boot process.
That will give you a busybox ash shell rather than run the initramfs shell scripting.
Then you can "rescue and bring up" the system from the memory resident system that is known to run "by hand".
This is the first thing I should try. Working with bash is much easier than recompiling the kernel and changing boot scripts and transfering it to the device.
Last edited by wlaf; 06-19-2012 at 06:04 PM.
wlaf is offline   Reply With Quote