Active Topics
-
Error after installing Leste on sdcard (13)
to Maemo 7 / Leste by Maemish - 1 day, 6 hrs ago -
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 1 day, 15 hrs ago -
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 5 days ago -
Maemo repository (3)
to Community by torsen - 5 days, 17 hrs ago - more...
|
2011-02-04
, 17:21
|
|
Posts: 114 |
Thanked: 109 times |
Joined on Nov 2010
@ Finland
|
#2
|
Open N900s terminal and type ls /dev/mmcblk0*
It should give /dev/mmcblk0, /dev/mmcblk0p1, /dev/mmcblk0p2 and /dev/mmcblk0p3.
If they all are present, type mount /dev/mmcblk0p1 as root. If not, then your N900 is broken AFAIK
It should give /dev/mmcblk0, /dev/mmcblk0p1, /dev/mmcblk0p2 and /dev/mmcblk0p3.
If they all are present, type mount /dev/mmcblk0p1 as root. If not, then your N900 is broken AFAIK
|
|
2011-02-04
, 17:37
|
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#3
|
Check the device structure with sfdisk please
There is also testdisk from the recovery-tools package, which could do some heuristic testing of the partition to find traces of former file systems.
Code:
sudo gainroot sfdisk -l
|
|
2011-02-04
, 18:10
|
|
Posts: 8 |
Thanked: 0 times |
Joined on Feb 2010
|
#4
|
sfdisk -l returns
nothing.....
and there are no partitions starting mmc on /dev
I cannot get at recovery tools because I only have a basic rootfs file system...
I think it is broken...
nothing.....
and there are no partitions starting mmc on /dev
I cannot get at recovery tools because I only have a basic rootfs file system...
I think it is broken...
|
|
2011-02-04
, 18:44
|
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#5
|
Maybe
will give you some output?
Code:
lshal | grep mmc lsmod | grep mmc
|
|
2011-02-04
, 19:14
|
|
Posts: 8 |
Thanked: 0 times |
Joined on Feb 2010
|
#6
|
lshal |grep mmc
gives a lot of output I cant type it all in and I cant ssh the device...
lsmod gives..
mmc_block 8964 0
omap_hsmmc 12160 0
mmc_core 46996 2 mmc_block,omap_hsmmc
Thanks for the help..
gives a lot of output I cant type it all in and I cant ssh the device...
lsmod gives..
mmc_block 8964 0
omap_hsmmc 12160 0
mmc_core 46996 2 mmc_block,omap_hsmmc
Thanks for the help..
|
|
2011-02-04
, 19:26
|
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#7
|
You might redirect the output of the lshal command to a file
No output on the screen given, everything is in the file lshal.txt. You might it attach to the post here via 'Go Advanced'
Code:
lshal | grep mmc > lshal.txt
|
|
2011-02-04
, 19:36
|
|
Posts: 8 |
Thanked: 0 times |
Joined on Feb 2010
|
#8
|
I cant think of a way to get the text file off off the phone...
I have no usable disk that I can see from my PC and no way to connect to the n900...no sshd, no connections at all basically..
its in a bit of a limbo unfortunately...
#lshal -s |grep mmc
platform_mmci_omap_hs_1
platform_mmci_omap_hs_1_mmc_host
platform_mmci_omap_hs_0
platform_mmci_omap_hs_0_mmc_host
I have no usable disk that I can see from my PC and no way to connect to the n900...no sshd, no connections at all basically..
its in a bit of a limbo unfortunately...
#lshal -s |grep mmc
platform_mmci_omap_hs_1
platform_mmci_omap_hs_1_mmc_host
platform_mmci_omap_hs_0
platform_mmci_omap_hs_0_mmc_host
|
|
2011-02-04
, 19:42
|
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#9
|
Email, bluetooth not working also?
|
|
2011-02-04
, 20:02
|
|
Posts: 8 |
Thanked: 0 times |
Joined on Feb 2010
|
#10
|
They might work, I dont think it matters though as the phone has no configuration..so the email configs are not going to be there
it is in its most basic form, just a factory configured rootfs.
lshal returned 98 configured devices, if that helps at all. I wish I could think of something, i must admit I didnt think about the HAL db at all..
I even loaded the backupMenu V2 rootfs bin that has an ssh daemon built in but I couldnt get putty to connect to it..I guess it is on the USB interface but I dont know which interface that is on my win7 machine and putty does not bind to it properly automatically. My linux is a VM ware image so I dont know about connections with that.If you can give me any clues to get connected through the USB from putty then I might be able to do something with a reflash of rootfs
it is in its most basic form, just a factory configured rootfs.
lshal returned 98 configured devices, if that helps at all. I wish I could think of something, i must admit I didnt think about the HAL db at all..
I even loaded the backupMenu V2 rootfs bin that has an ssh daemon built in but I couldnt get putty to connect to it..I guess it is on the USB interface but I dont know which interface that is on my win7 machine and putty does not bind to it properly automatically. My linux is a VM ware image so I dont know about connections with that.If you can give me any clues to get connected through the USB from putty then I might be able to do something with a reflash of rootfs
My N900 has had a few problems lately, first the USB came off as per..now the eMMC is unreadable.
I have flashed the thing as I have done countless times before and it is not working. I can flash the rootfs but the vanilla image is giving me the ol'
SU_GET_UPDATE etc error code 1
I have r&d mode'd the phone to check fdisk and try to check the /dev/mmcblk0p1 filesystem but it is simply not present. The rootsfs image is booting up and the phone seems to work, just that the extended memory is not available at all. seems like it is not being mounted at boot time.
I dont really know what to do I have checked the dmesg and all I see is an outdated scsi driver message that could have anything to do with this..
Any diagnostic root images or cool ways to mount or check my eMMC memory would be gratefully received.