K3 with broken display to give away - Page 2

ixtab · 01-08-2012, 05:49 AM

@geekmaster: ouch... stupid me. Thanks for the pointers! I got usbnetwork running now and am logged in on the device. The reason for asking these stupid questions was actually quite simple: I didn't have physical access to the device, so much of it was written in "thin air".

@cscat: I think that porting android to the Kindle is a nice project (though I personally don't see a need for it and wouldn't have time). Keep in mind though that this is a K3, not a KT. Because the display is broken, it can also only be used as either a USB drive, or via network. If you're into running android on it, none of these would work (because you have to replace the entire kernel etc., so the only access would be via serial cable or so.

@all: any other hints concerning what to delete or change (besides /mnt/us/documents obviously) in order to remove all personal registration info is appreciated.

geekmaster · 01-08-2012, 06:03 AM

Quote:

Originally Posted by ixtab

@all: any other hints concerning what to delete or change (besides /mnt/us/documents obviously) in order to remove all personal registration info is appreciated.

You can reformat mmcblk0p2 (the /var/local persistent store) and it will get rebuilt on next boot (I think). Check the startup scripts. That should be where cached passwords and such get stored. You can also whack the user partition /mnt/us and it gets rebuilt too.

Yifanlu and NiLuJe understand the details of that stuff better than I do.

giorgio130 · 01-08-2012, 06:19 AM

Hi, I'm in Italy. I'd like the spare device since I was trying to backport the firmware found on the new keyboard-less kindles, but I stopped for the fear of bricking the device. This way I could test my 2.6.31 kernel by my own, and get the project going again. My karma is low but I've got the good will to make the device useful. I don't see the point in porting Android to the Kindle 3 but I could help with that as well, just for fun. I already worked in a project that ported Android 2.2 to the LG GW620, and I still make minor work on HTC HD2 (porting newer linux kernels). Please consider my entry.

NiLuJe · 01-08-2012, 11:46 AM

AFAICR, the factory reset *does* kill /var/local (via dd if=/dev/zero).

(Check /usr/sbin/factory_reset

).

Off the top of my head, I can't think of anything else that might be of concern...

.

geekmaster · 01-08-2012, 11:52 AM

Quote:

Originally Posted by NiLuJe

AFAICR, the factory reset *does* kill /var/local (via dd if=/dev/zero).

(Check /usr/sbin/factory_reset

).

Off the top of my head, I can't think of anything else that might be of concern...

.

Doesn't factory reset break the jailbreak and usbnet hacks he has installed?

I have not done a factory reset on mine lately...

NiLuJe · 01-08-2012, 12:03 PM

Since it also kills the userstore (the same way it kills /var/local), it effectively disables anything relying on stuff being there (so, yeah, all of my stuff ^^), but simply putting the stuff back there (using the appropriate directory from the latest source packages) after the factory reset should ensure everything will work fine after a restart

. (Provided he has a recent enough version of usbnetwork [>= 0.26.N, to be exact], one that checks/fix the test/bin folder during init, and not only install, because a factory reset will also kill the /test directory, which breaks usbnetwork).

ixtab · 01-08-2012, 01:00 PM

Thanks for all the suggestions so far. Nuking mmcblk0p4 would indeed also kill the usbnetwork hack (which is direly needed at the moment), so I'm refraining from it. I did walk through the files in /mnt/us, and there are loads of hacks installed, but nothing really personal (anymore).

I also refrained from entirely deleting mmcblk0p3 (probably won't do it either). As it is currently, I'm happy that the device can be accessed remotely via ssh, and will just leave it in the current state. So, consider problem 2 solved as well (at least for me).

Whatever the new owner does to the device is of course up to him/her.

That said, this thread is still open for comments. If you want a broken K3 for free, drop a note here until friday. I'll send it to the person who provided the most convincing argument.

geekmaster · 01-08-2012, 02:41 PM

Quote:

Originally Posted by ixtab

I have a Kindle 3 (Wifi+3G) with a broken display here. Managed to step on it (don't ask...).

Well, now that YOU brought it up, just how DID you step on it?

You can PM me if you do not wish to embarrass yourself in front of the whole world.

lunohod · 01-08-2012, 04:19 PM

I'm trying to port OpenInkpot to the Kindle 3. Right now I have a recent vanilla kernel 3.1 booting on my K3 (just plain kernel and serial console output), but right after the shell promt is shown the device just freezes. I need to solder the JTAG to find out why it doesn't work, but I don't want to destroy a working device. As soon as the problem with freezing kernel is solved, I could send this device to another developer.

ixtab · 01-08-2012, 04:21 PM

Quote:

Originally Posted by geekmaster

Well, now that YOU brought it up, just how DID you step on it?

Well, the procedure is pretty simple: just place any foot on the device and walk on.

geekmaster · 01-08-2012, 04:35 PM

Your "free k3" offer diverted my attention from touch and k4nt. Now I have been looking for exploits in the k3.

The tar bug STILL does not work on the k3 (just like last time I tested it). I found a possible LD_LIBRARY_PATH exploit though. That means payload must be packaged in a .so lib file though. Hard to believe they would try to load native EXECUTABLE code off the user partition, but it sure looks like it though...

rastik · 01-10-2012, 07:58 AM

You can use VNC with K3. Just create ENABLE_VNC file in /mnt/us and after the reboot you can connect to it via vncviewer. And if you alter iptables filter you can connect to it via WiFi too. That's how I use mine sometimes.

geekmaster · 01-10-2012, 05:05 PM

Quote:

Originally Posted by rastik

You can use VNC with K3. Just create ENABLE_VNC file in /mnt/us and after the reboot you can connect to it via vncviewer. And if you alter iptables filter you can connect to it via WiFi too. That's how I use mine sometimes.

Which version of vnc did you install on your k3? Did it install the startup script that looks for /mnt/us/ENABLE_VNC, or did you do that yourself?

rastik · 01-12-2012, 03:36 AM

Quote:

Originally Posted by geekmaster

Which version of vnc did you install on your k3? Did it install the startup script that looks for /mnt/us/ENABLE_VNC, or did you do that yourself?

AFAIR VNC is already there, it is enough to activate it with that file. But unless you modify iptables rules, it is accessible only via USB net interface.

geekmaster · 01-12-2012, 03:50 AM

It did not work on my K3. There also was no file with "vnc" as part of the name on the partition. Adding that trigger file did not cause anything to listen on port 5900 (or anywhere nearby).

There are multiple versions of vnc that you can install. That is why I asked.

I am curious where your vnc came from. Did you install it at one time?

01-08-2012, 12:03 PM	#21
NiLuJe BLAM! Posts: 13,506 Karma: 26047190 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Since it also kills the userstore (the same way it kills /var/local), it effectively disables anything relying on stuff being there (so, yeah, all of my stuff ^^), but simply putting the stuff back there (using the appropriate directory from the latest source packages) after the factory reset should ensure everything will work fine after a restart . (Provided he has a recent enough version of usbnetwork [>= 0.26.N, to be exact], one that checks/fix the test/bin folder during init, and not only install, because a factory reset will also kill the /test directory, which breaks usbnetwork). Last edited by NiLuJe; 01-08-2012 at 12:08 PM.

01-08-2012, 04:35 PM	#26
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773668 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	Your "free k3" offer diverted my attention from touch and k4nt. Now I have been looking for exploits in the k3. The tar bug STILL does not work on the k3 (just like last time I tested it). I found a possible LD_LIBRARY_PATH exploit though. That means payload must be packaged in a .so lib file though. Hard to believe they would try to load native EXECUTABLE code off the user partition, but it sure looks like it though... Last edited by geekmaster; 01-08-2012 at 08:40 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Broken display	corpcd	Amazon Kindle	8	05-23-2011 12:28 PM
Is my kindle display broken	gianpaoloc	Amazon Kindle	8	12-04-2010 04:18 AM
Misteriously broken display	Olenka	Sony Reader	5	01-26-2010 09:01 AM
Display broken?	philippd	Sony Reader	4	06-13-2009 09:09 AM
Broken display	David B	Bookeen	43	02-29-2008 01:27 PM

01-08-2012, 05:49 AM	#16
ixtab (offline) Posts: 2,907 Karma: 6736094 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	@geekmaster: ouch... stupid me. Thanks for the pointers! I got usbnetwork running now and am logged in on the device. The reason for asking these stupid questions was actually quite simple: I didn't have physical access to the device, so much of it was written in "thin air". @cscat: I think that porting android to the Kindle is a nice project (though I personally don't see a need for it and wouldn't have time). Keep in mind though that this is a K3, not a KT. Because the display is broken, it can also only be used as either a USB drive, or via network. If you're into running android on it, none of these would work (because you have to replace the entire kernel etc., so the only access would be via serial cable or so. @all: any other hints concerning what to delete or change (besides /mnt/us/documents obviously) in order to remove all personal registration info is appreciated.

01-08-2012, 06:19 AM	#18
giorgio130 Time Waster Posts: 422 Karma: 289160 Join Date: May 2011 Device: Kobo Glo and Aura HD	Hi, I'm in Italy. I'd like the spare device since I was trying to backport the firmware found on the new keyboard-less kindles, but I stopped for the fear of bricking the device. This way I could test my 2.6.31 kernel by my own, and get the project going again. My karma is low but I've got the good will to make the device useful. I don't see the point in porting Android to the Kindle 3 but I could help with that as well, just for fun. I already worked in a project that ported Android 2.2 to the LG GW620, and I still make minor work on HTC HD2 (porting newer linux kernels). Please consider my entry.

01-08-2012, 11:46 AM	#19
NiLuJe BLAM! Posts: 13,506 Karma: 26047190 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	AFAICR, the factory reset does kill /var/local (via dd if=/dev/zero). (Check /usr/sbin/factory_reset ). Off the top of my head, I can't think of anything else that might be of concern... .

01-08-2012, 01:00 PM	#22
ixtab (offline) Posts: 2,907 Karma: 6736094 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	Thanks for all the suggestions so far. Nuking mmcblk0p4 would indeed also kill the usbnetwork hack (which is direly needed at the moment), so I'm refraining from it. I did walk through the files in /mnt/us, and there are loads of hacks installed, but nothing really personal (anymore). I also refrained from entirely deleting mmcblk0p3 (probably won't do it either). As it is currently, I'm happy that the device can be accessed remotely via ssh, and will just leave it in the current state. So, consider problem 2 solved as well (at least for me). Whatever the new owner does to the device is of course up to him/her. That said, this thread is still open for comments. If you want a broken K3 for free, drop a note here until friday. I'll send it to the person who provided the most convincing argument.

01-08-2012, 04:19 PM	#24
lunohod OpenInkpot developer Posts: 211 Karma: 5627 Join Date: Mar 2008 Location: Stuttgart, Germany Device: N516,V3,PRS505,iLiad,eSlick,E60,K3,K4NT,M90,PB912,KoboMini	I'm trying to port OpenInkpot to the Kindle 3. Right now I have a recent vanilla kernel 3.1 booting on my K3 (just plain kernel and serial console output), but right after the shell promt is shown the device just freezes. I need to solder the JTAG to find out why it doesn't work, but I don't want to destroy a working device. As soon as the problem with freezing kernel is solved, I could send this device to another developer.

01-10-2012, 07:58 AM	#27
rastik Connoisseur Posts: 65 Karma: 4662 Join Date: Feb 2011 Location: CZ Device: Kindle Touch 3G, Kindle Keyboard	You can use VNC with K3. Just create ENABLE_VNC file in /mnt/us and after the reboot you can connect to it via vncviewer. And if you alter iptables filter you can connect to it via WiFi too. That's how I use mine sometimes.

01-12-2012, 03:50 AM	#30
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773668 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	It did not work on my K3. There also was no file with "vnc" as part of the name on the partition. Adding that trigger file did not cause anything to listen on port 5900 (or anywhere nearby). There are multiple versions of vnc that you can install. That is why I asked. I am curious where your vnc came from. Did you install it at one time?

Advert

Advert