Alternate "Simple" debricking methods for K5-Touch, K4-Mini, & K3-Keyboard

[geekmaster]

Originally Posted by mand

...
I was *this* close to giving up and buying a new Kindle.
But the comatose is returned!

And it's not even going slow as it was for weeks leading up to this.
I couldn't have wifi on without losing it on the first or second page turn.

THANK YOU. ...

I added your success report to the list in the first post.

Does that success report list need a spoiler tag wrapping it? It is getting obscenely large!

[twobob]

If I'm not on it I should be - four or five times now

Thanks to everyone who made unbricking my last utter fubar on the 3 possible.
Without k3flasher that would have definitely been toast fodder.

and GM's assistance with rooting/backing up and unbricking my 5 has also been invaluable.. As has Knc1's knowledge of exactly what to backup and why.

Thanks to all.

And Nah. leave it big heh

[stangri]

Well, this is mainly the question for geekmaster, but if anyone else has a first-hand experience with the Demo K4 NT please chime in.

So I've got two Demo K4 NTs and I was able to get them into DIAGs mode thru MfgTool to flash the rootfs and it's now on 4.0 fw. However:
1. I can't get them to switch to fastboot thru MfgTool. The old device (NS Blank CODEX) disappears from the system but the new one (Kindle in fastboot mode) doesn't connect. Neither I can actually make it boot Kindle main thru MfgTool -- in case of Kindle main even the old device doesn't disconnect, it seems like MfgTool cannot send the correct commands up.

2. When I tried to run the update to 4.1.0 on the freshly loaded 4.0 fw (no registration, no jb) it failed on step 2/2.

My goal would be 4.1.0 running on those Demo K4 NTs and I'd like to be able to update diags partition, diags kernel and regular kernel to the stock K4 versions. Any suggestions?

thanks!

[Mike76]

I've fixed the kernel/partition mismatch on my debricked K4B. I've dumped all needed 4.1.0 version kernel and partition images from a K4S after resetting it to factory defaults. Now the K4B works perfectly except one thing: the Disable diagnostic command is not working in diags menu (it said "pcbID does not match with your DNS"), so I have to manually get out from diags mode using MfgTool. It's not a big problem, but a little bit uncomfortable...Does anybody have idea how to fix it?

Oh, another question: I've a 'virgin' K4B and I would like to get kernel/partition images from it Is it possible to do without flashing the missing diagnostic+SSH partition, for example via data.tar.gz and RUNME.SH?

Thanks!

[NiLuJe]

@stangri:

Can't speak for 1/, but for 2/, some of the 4.0.x backups floating around used the crappy low-level screensavers switch. You'll have to revert it to be able to update.

@Mike76: Yup, JailBreak + USBNet. You'll still have to go through diags *once*, and you'll have usbnet installed on main, so the backups won't be completely vanilla, but for a device on 4.1.x, that's the best we can do.

[stangri]

Originally Posted by NiLuJe

Can't speak for 1/, but for 2/, some of the 4.0.x backups floating around used the crappy low-level screensavers switch. You'll have to revert it to be able to update.

I grabbed what I thought was the stock image. Any hints as to where can I download a fully stock 4.0 image then?

[geekmaster]

On the available 4.0 image, just find the 800x600 backup folder and rename it... Then updates work.

[geekmaster]

CHARGE THE BATTERY! note added to top of first post. All debricking-related threads / wikis / documents need something like that.

There are far too many "debricking failed" posts recently, where the only problem was a severely depleted battery that needed to charge on a wall charger for 20 hours.

[NiLuJe]

@stangri: As GM said, the backup is there, so just revert it. (OTOMH: mv /opt/amazon/screen_saver/600x800_ /opt/amazon/screen_saver/600x800).

@GM: It might be neat to kill the guid file (/etc/guid) from the dumps. AFAIK, it's rebuilt automatically during the boot process if it's missing, but a factory reset won't kill it. I'm not sure as to what extent Amazon uses/rely on this, but it's at least used as an 'anonymous' id for the device when talking to some Amazon services...

[ixtab]

Originally Posted by NiLuJe

@stangri: As GM said, the backup is there, so just revert it. (OTOMH: mv /opt/amazon/screen_saver/600x800_ /opt/amazon/screen_saver/600x800).

@GM: It might be neat to kill the guid file (/etc/guid) from the dumps. AFAIK, it's rebuilt automatically during the boot process if it's missing, but a factory reset won't kill it. I'm not sure as to what extent Amazon uses/rely on this, but it's at least used as an 'anonymous' id for the device when talking to some Amazon services...

Well then, isn't it better to actually leave it in? If there's 10000 people using the same guid, that's actually better anonymity than having a unique ID.

[stangri]

OK, so for some reason /dev/mmcblk0p1 didn't mount as base-mmc in diags mode, so here's what I've had to do once I've SSHed to Kindle:

PHP Code:

[root@[192_168_15_244] /]# mount /dev/mmcblk0p1 /mnt/base-mmc
[root@[192_168_15_244] /]# rm /mnt/base_mmc/opt/amazon/screen_saver/600x800
[root@[192_168_15_244] /]# mv /mnt/base_mmc/opt/amazon/screen_saver/600x800_ /mnt/base_mmc/opt/amazon/screen_saver/600x800 


BTW, how do I fix non-working fastboot tho?

[NiLuJe]

@stangri: main vs. diags . I usually avoid spending time in diags if I can, so the stuff I pasted assumed you were on main, not diags .

(Also, not sure if it's a typo in your message or what you did but there's a '0' missing in the target path of the last command ).

[stangri]

I'm not sure how the SSH over USB works in K4 main mode, so I went to diags where I do know how it works.

And thanks, I fixed the typo.

Still, would love to hear back from geekmaster about fastboot mode on the demo k4.

[geekmaster]

I did not use fastboot on my demo K4. I modified ixtab's method described here"
http://www.mobileread.com/forums/sho....php?p=2202022

Instead of dealing with fastboot and its USB complications, I used dd to copy the main kernel to /dev/mmcblk0 with offset, as described in ixtab's README file, just before I copied the main rootfs to /dev/mmcblk0p1 with dd.

That is great for a K4 (and even a K4 demo), but on a K5 you still need fastboot to get diags+ssh on it.

I did not even use MfgTool, but instead eureka's imx_usb_downloader tool, to boot to diags.

I do not see why fastboot wouldn't work on a K4 demo, but I do not have time to try it right now. Try ixtab's method.

[Mike76]

Originally Posted by NiLuJe

@Mike76: Yup, JailBreak + USBNet. You'll still have to go through diags *once*, and you'll have usbnet installed on main, so the backups won't be completely vanilla, but for a device on 4.1.x, that's the best we can do.

Thanks, it works!