03-25-2012, 04:58 PM
|
#1 |
|
Member
 Posts: 19
Karma: 10
Join Date: Apr 2011
Device: pocketbook 603a
|
unbrik kindle3
It seems to me that the usb is defective. How can I fix Kindle without usb or where am I wrong?
Fdisk Spoiler:
mkfs.ext3 /dev/sdb1 Spoiler:
Windows XP,usb: 3,72gb, 4 partition: 650mb(active), 24mb,8mb,3,06mb When I connect usb connector, then the errors are com-port several minutes: (Approximately 5000 lines, each sector is repeated 6 - 64 times.) Spoiler:
Help me plz. root@ubuntu:~# dd if=/media/APACER/mmcblk0p1.dmp of=/dev/sdc1 dd: writing to `/dev/sdc1': Input/output error 9+0 records in 8+0 records out 4096 bytes (4.1 kB) copied, 0.291976 s, 14.0 kB/s root@ubuntu:~# Last edited by ed007; 03-26-2012 at 04:26 PM. |
|
|
|
03-25-2012, 05:38 PM
|
#2 |
|
Carpe diem, c'est la vie.
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Last edited by geekmaster; 03-25-2012 at 05:42 PM. |
|
|
|
| Advert | |
|
|
|
03-26-2012, 05:18 AM
|
#3 |
|
Member
Posts: 19
Karma: 10
Join Date: Apr 2011
Device: pocketbook 603a
|
All my actions are based on this video.
Unfortunately, after connecting the usb-connector, the results are: many errors. for example: ubuntu@ubuntu:~$ dmesg Spoiler:
root@ubuntu:~# mkfs.ext3 /dev/sdc1 Spoiler:
root@ubuntu:~# dd if=/media/APACER/mmcblk0p1.dmp of=/dev/sdc1 Spoiler:
|
|
|
|
|
03-26-2012, 08:26 AM
|
#4 |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
*nix basics
Are the three "spoilers" included in your most recent post suppose to represent things you did, in the order you did them?
For instance, "spoiler 1" reads a lot more like the result of trying to format (or other write activity) the device discovered as sdc. Not all of that as the result of plugging in the cable. Please clearify what messages are the result of what actions. With all of the device errors shown in "spoiler 1" - What did you have in mind trying to format it in "spoiler 2"? Was there some reason to doubt the errors being reported in "spoiler 1"? Then in "spoiler 3" you try to use the dd command to over-write the contents of a partiton, including any formatting recorded there. The dd command works at the device level, not the file system level. You can read that in your own command where you have to use the name of a device rather than the name of a mounted file system. So if your command in "spoiler 3" had worked, even a little bit, it would have made your efforts shown in "spoiler 2" a waste of time. But since "spoiler 1" reported that the device wasn't working properly - what did you expect to achive by not finding and fixing the cause of that problem before continueing? |
|
|
|
|
03-26-2012, 09:00 AM
|
#5 |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quickly, before GeekMaster slams me (again) for not writing a helpful post.
Before connecting the usb cable, what do you expect to see in the kernel message buffer? You must be able to answer that question if you are going to do any problem solving. Here is a starting point to help you answer that question: (the '-c' option clears the message buffer, which requires 'root' privledges) sudo dmesg -c Insert a removable USB device, a USB stick if you have one dmesg Cut & paste the result somewhere you can refer to it later. If your desktop automation auto-mounted the USB stick, unmount it. sudo dmesg -c Remove the USB stick dmesg Cut & paste the result somewhere you can refer to it later. Now carefully follow the directions GeekMaster directed you to, upto and just prior to inserting the USB cable. sudo dmesg -c insert the USB cable dmesg Cut & paste the result somewhere you can refer to it and compare with the expected result you saved above. What are the differences? Can you account for the differences? (ans: the only significant difference might be the device name, which is dynamically picked in "discovery order" unless your re-naming it with a udev rule). Are there any error messages or warning messages included in the kernel messages from inserting either the USB stick or (later) insterting the USB cable? What are they? (there should not be any warnings or errors) Can you account for the differences? You must have a properly recognized device before going any further. |
|
|
|
| Advert | |
|
|
|
03-26-2012, 10:53 AM
|
#6 |
|
Member
Posts: 19
Karma: 10
Join Date: Apr 2011
Device: pocketbook 603a
|
Recorded video of the process. Please look at.
http://youtu.be/lUoW8Cpik_w |
|
|
|
|
03-26-2012, 11:15 AM
|
#7 | |
|
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
I only get upset about posts that I feel are doubting my own personal credibility without sufficient evidence. I think that my defensive reaction is a common reaction to "aggressive listening" (as defined here: http://c2.com/cgi/wiki?AggressiveListening). It really is just a way of learning and interacting in a way that upsets some people, and I think there are a few people here who fall into the aggressive listener category and who have triggered defensive posturing from me. Sorry about that. 
Last edited by geekmaster; 03-26-2012 at 12:09 PM. |
|
|
|
|
|
03-26-2012, 11:48 AM
|
#8 | |
|
Member
Posts: 19
Karma: 10
Join Date: Apr 2011
Device: pocketbook 603a
|
Quote:
|
|
|
|
|
|
03-26-2012, 11:51 AM
|
#9 | |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Would you try following my directions next? First step in capturing useful information from the kernel message buffer: sudo dmesg -c Which clears the message buffer after reporting the current contents. You can see that if you do: sudo dmesg -c sudo dmesg -c And the second command will have nothing to report because the first one cleared the buffer. At this point take the single action that you expect the kernel to recognize, such as plugging in or unplugging a removable device (the K2 USB connection is one such thing). Then examine the message buffer - which you know was empty before your single action - meaning whatever is in there now is the result of your single action. Highlight the desired information in the command terminal, copy, paste into a text editor (not a word processor) such as gedit. No need to waste anyone's time with a meaningless, 10 minute video. Question: What was that "usb connect" command that you typed in the terminal? Your system did not recognize it, but what did you intend by typing it? Note: Video shows you running as 'root' in the command line terminals. An extremely bad idea even for someone who knows what they are doing. |
|
|
|
|
|
03-26-2012, 11:59 AM
|
#10 |
|
Member
Posts: 19
Karma: 10
Join Date: Apr 2011
Device: pocketbook 603a
|
This is not a team, this is a comment for you - shows that now I plug my usb connector.
You do not look a video? Views counter = 0 I understood the meaning of the command "sudo dmesg-c", but it is not clear to me what gives? Errors with the name of the device there. root no problem - LiveCD. add: 10 minutes to spend watching video is not necessary: the time of the important points mentioned in the comments. Last edited by ed007; 03-26-2012 at 12:11 PM. |
|
|
|
|
03-26-2012, 12:15 PM
|
#11 | |
|
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
|
|
|
|
|
|
03-26-2012, 12:19 PM
|
#12 |
|
Member
Posts: 19
Karma: 10
Join Date: Apr 2011
Device: pocketbook 603a
|
Unfortunately my knowledge of English is approximately equal to my knowledge of Linux.
|
|
|
|
|
03-26-2012, 12:19 PM
|
#13 | |
|
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
|
|
|
|
|
|
03-26-2012, 12:25 PM
|
#14 |
|
Member
Posts: 19
Karma: 10
Join Date: Apr 2011
Device: pocketbook 603a
|
I completely repeat the action from video seaniko7, he works out of -su
|
|
|
|
|
03-26-2012, 12:26 PM
|
#15 | |
|
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
|
|
|
|
|
 |
«
Previous Thread
|
Next Thread
»
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Could Kindle3 be updated on PC ? | superium | Kindle Developer's Corner | 4 | 09-26-2011 10:54 PM |
| Troubleshooting My kindle3 got frozen, help me | schechow | Amazon Kindle | 8 | 07-11-2011 11:51 AM |
| Kindle3, FW 3.1 - Caliber not seeing it | loximuthal | Devices | 2 | 02-20-2011 03:59 PM |
| Classic Okay I Looked at the Kindle3 | Pomtroll | Barnes & Noble NOOK | 52 | 10-01-2010 10:31 AM |
| Troubleshooting kindle3 gmail | desrtfreak | Amazon Kindle | 6 | 09-22-2010 10:28 PM |
All times are GMT -4. The time now is 07:11 AM.