Active Topics

 


Reply
Thread Tools
Posts: 16 | Thanked: 12 times | Joined on Oct 2012 @ chicago, IL
#1
Hello everyone. Long time lurker and fan here. I recently got an N9 16gb after i lost my n900 to the sim recognition issue (its fixed now ......)

anyways i was trying to flash a dual boot kernel image for nitdroid and i had everything going good until i rebooted. Now my phone isnt recognized under mass storage mode and MyDocs seems to be non existant. Could anyone assist me with this??
 
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#2
Did you re-format the blocks of your mmc partition?

Also paste the output of the following from terminal:

Code:
fdisk -l
fdisk -l /dev/mmcblk0p1
 

The Following User Says Thank You to thedead1440 For This Useful Post:
Posts: 16 | Thanked: 12 times | Joined on Oct 2012 @ chicago, IL
#3
Originally Posted by thedead1440 View Post
Did you re-format the blocks of your mmc partition?

Also paste the output of the following from terminal:

Code:
fdisk -l
fdisk -l /dev/mmcblk0p1
currently dont have access to computer but what i can tell you now is
that i tried erasing user data with the flasher and that the system shows unallocated space o and fsck showed a logical sector is zero message
 
Posts: 16 | Thanked: 12 times | Joined on Oct 2012 @ chicago, IL
#4
alright the output of fdisk -l is:

Disk /dev/sda: 9453 MB, 9453436928 bytes
64 heads, 32 sectors/track, 9015 cylinders, total 18463744 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sda doesn't contain a valid partition table



and mmcblk doesnt output anything



edit: solved by flashing mmc with mmc bin file from navifirm

Last edited by cinnamoncat; 2012-12-06 at 21:19. Reason: forgot critical info
 
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#5
Originally Posted by cinnamoncat View Post
Disk /dev/sda: 9453 MB, 9453436928 bytes
64 heads, 32 sectors/track, 9015 cylinders, total 18463744 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
That looks like your computer's disk.
What thedead wanted you to do would propably have been to take the fdisk from your device, like this;

~ #
~ # /sbin/sfdisk -l

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1760511 1760496 56335872 c W95 FAT32 (LBA)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 0 - 0 0 0 Empty

Disk /dev/dm-0: 0 cylinders, 0 heads, 0 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/dm-0: unrecognized partition table type
No partitions found
~ #
 

The Following User Says Thank You to juiceme For This Useful Post:
Posts: 16 | Thanked: 12 times | Joined on Oct 2012 @ chicago, IL
#6
Originally Posted by juiceme View Post
That looks like your computer's disk.
What thedead wanted you to do would propably have been to take the fdisk from your device, like this;

~ #
~ # /sbin/sfdisk -l

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1760511 1760496 56335872 c W95 FAT32 (LBA)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 0 - 0 0 0 Empty

Disk /dev/dm-0: 0 cylinders, 0 heads, 0 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/dm-0: unrecognized partition table type
No partitions found
~ #
The reason it comes off as a system disk was because I was using fdisk while the phone was on mass storage mode. It wouldnt show up under sdk for some reason.
 
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#7
You could have done it via SSH too

The fdisk -l was required to see what your device shows for that partition; by mounting on PC and doing fdisk -l it serves no purpose actually...

Anyway since you have solved it by flashing the emmc.bin its done and dusted
 
Reply


 
Forum Jump


All times are GMT. The time now is 14:07.