<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Hacking N810 After Firmware Update</title>
	<atom:link href="http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/</link>
	<description>Ripping mobility from the clutches of telecom</description>
	<pubDate>Wed, 17 Mar 2010 07:44:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: robo12</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-263793</link>
		<dc:creator>robo12</dc:creator>
		<pubDate>Mon, 21 Apr 2008 09:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-263793</guid>
		<description>I have tried everything with no luck

not able to umount :( I have a checkbox checked to extend internal memory and I cant unchek it :(

so I have "BUSY" message everytime

/home/user # umount /dev/mmcblk0p1
umount: cannot umount /media/mmc2: Device or resource busy

/home/user # lsof /dev/mmcblk0p1
gets nothing :(

please take a look at this, I think there is something wrong as I am not too deep into linux yet, I just made using your and other forums instructions - but no luck againe

/ # sfdisk -f /dev/mmcblk0p1
Checking that no-one is using this disk right now ...
BLKRRPART: Invalid argument
OK

Disk /dev/mmcblk0p1: 61439 cylinders, 4 heads, 16 sectors/track
Old situation:
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/mmcblk0p1p1          0       -       0          0   0  Empty
/dev/mmcblk0p1p2          0       -       0          0   0  Empty
/dev/mmcblk0p1p3          0       -       0          0   0  Empty
/dev/mmcblk0p1p4          0       -       0          0   0  Empty
Input in the following format; absent fields get a default value.
     
Usually you only need to specify  and  (and perhaps ).

/dev/mmcblk0p1p1 :0,,b
/dev/mmcblk0p1p1          0+  61438   61439-   1966047+   b  W95 FAT32
/dev/mmcblk0p1p2 :
/dev/mmcblk0p1p2          0       -       0          0   0  Empty
/dev/mmcblk0p1p3 :
/dev/mmcblk0p1p3          0       -       0          0   0  Empty
/dev/mmcblk0p1p4 :
/dev/mmcblk0p1p4          0       -       0          0   0  Empty
New situation:
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/mmcblk0p1p1          0+  61438   61439-   1966047+   b  W95 FAT32
/dev/mmcblk0p1p2          0       -       0          0   0  Empty
/dev/mmcblk0p1p3          0       -       0          0   0  Empty
/dev/mmcblk0p1p4          0       -       0          0   0  Empty
Warning: no primary partition is marked bootable (active)
This does not matter for LILO, but the DOS MBR will not boot this disk.
Do you want to write this to disk? [ynq] y
Successfully wrote the new partition table

Re-reading the partition table ...
BLKRRPART: Invalid argument

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
/ # mkdosfs /dev/mmcblk0p1
mkdosfs 2.11 (12 Mar 2005)
mkdosfs: /dev/mmcblk0p1 contains a mounted file system.
/ #</description>
		<content:encoded><![CDATA[<p>I have tried everything with no luck</p>
<p>not able to umount :( I have a checkbox checked to extend internal memory and I cant unchek it :(</p>
<p>so I have &#8220;BUSY&#8221; message everytime</p>
<p>/home/user # umount /dev/mmcblk0p1<br />
umount: cannot umount /media/mmc2: Device or resource busy</p>
<p>/home/user # lsof /dev/mmcblk0p1<br />
gets nothing :(</p>
<p>please take a look at this, I think there is something wrong as I am not too deep into linux yet, I just made using your and other forums instructions - but no luck againe</p>
<p>/ # sfdisk -f /dev/mmcblk0p1<br />
Checking that no-one is using this disk right now &#8230;<br />
BLKRRPART: Invalid argument<br />
OK</p>
<p>Disk /dev/mmcblk0p1: 61439 cylinders, 4 heads, 16 sectors/track<br />
Old situation:<br />
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0</p>
<p>   Device Boot Start     End   #cyls    #blocks   Id  System<br />
/dev/mmcblk0p1p1          0       -       0          0   0  Empty<br />
/dev/mmcblk0p1p2          0       -       0          0   0  Empty<br />
/dev/mmcblk0p1p3          0       -       0          0   0  Empty<br />
/dev/mmcblk0p1p4          0       -       0          0   0  Empty<br />
Input in the following format; absent fields get a default value.</p>
<p>Usually you only need to specify  and  (and perhaps ).</p>
<p>/dev/mmcblk0p1p1 :0,,b<br />
/dev/mmcblk0p1p1          0+  61438   61439-   1966047+   b  W95 FAT32<br />
/dev/mmcblk0p1p2 :<br />
/dev/mmcblk0p1p2          0       -       0          0   0  Empty<br />
/dev/mmcblk0p1p3 :<br />
/dev/mmcblk0p1p3          0       -       0          0   0  Empty<br />
/dev/mmcblk0p1p4 :<br />
/dev/mmcblk0p1p4          0       -       0          0   0  Empty<br />
New situation:<br />
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0</p>
<p>   Device Boot Start     End   #cyls    #blocks   Id  System<br />
/dev/mmcblk0p1p1          0+  61438   61439-   1966047+   b  W95 FAT32<br />
/dev/mmcblk0p1p2          0       -       0          0   0  Empty<br />
/dev/mmcblk0p1p3          0       -       0          0   0  Empty<br />
/dev/mmcblk0p1p4          0       -       0          0   0  Empty<br />
Warning: no primary partition is marked bootable (active)<br />
This does not matter for LILO, but the DOS MBR will not boot this disk.<br />
Do you want to write this to disk? [ynq] y<br />
Successfully wrote the new partition table</p>
<p>Re-reading the partition table &#8230;<br />
BLKRRPART: Invalid argument</p>
<p>If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)<br />
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1<br />
(See fdisk(8).)<br />
/ # mkdosfs /dev/mmcblk0p1<br />
mkdosfs 2.11 (12 Mar 2005)<br />
mkdosfs: /dev/mmcblk0p1 contains a mounted file system.<br />
/ #</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PLeBlanc</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-242666</link>
		<dc:creator>PLeBlanc</dc:creator>
		<pubDate>Fri, 22 Feb 2008 23:37:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-242666</guid>
		<description>Thanks all,
I just ran into this same pernicious problem today after updating to the firmware they just released (from 42-19 to 51-3 on the n8100).

The only thing that NB didn't cover above was for folks who have extended their memory, you need to turn it off first.  From the thread at ITT, before running 'umount' - 
1. Open the Control Panel and click the Memory Icon.
2. UN-check the "extended memory box" (this is what is using the internal card)

(Plus I'd add a brief caveat that sfdisk will wipe everything off your internal card, so if there is anything you want to keep on there better copy it someplace else.)

Considering that I updated my n800 at the same time (well, first actually), it was very confusing when the internal memory on the n810 started saying everything was read only, and the n800 didn't have a problem.  I was despairing I had a flash failure before googling and finding your site here!  Thanks all!</description>
		<content:encoded><![CDATA[<p>Thanks all,<br />
I just ran into this same pernicious problem today after updating to the firmware they just released (from 42-19 to 51-3 on the n8100).</p>
<p>The only thing that NB didn&#8217;t cover above was for folks who have extended their memory, you need to turn it off first.  From the thread at ITT, before running &#8216;umount&#8217; -<br />
1. Open the Control Panel and click the Memory Icon.<br />
2. UN-check the &#8220;extended memory box&#8221; (this is what is using the internal card)</p>
<p>(Plus I&#8217;d add a brief caveat that sfdisk will wipe everything off your internal card, so if there is anything you want to keep on there better copy it someplace else.)</p>
<p>Considering that I updated my n800 at the same time (well, first actually), it was very confusing when the internal memory on the n810 started saying everything was read only, and the n800 didn&#8217;t have a problem.  I was despairing I had a flash failure before googling and finding your site here!  Thanks all!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-230995</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Fri, 25 Jan 2008 02:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-230995</guid>
		<description>Thanks guys.  You really helped me out with this information.</description>
		<content:encoded><![CDATA[<p>Thanks guys.  You really helped me out with this information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nb</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-222460</link>
		<dc:creator>nb</dc:creator>
		<pubDate>Fri, 04 Jan 2008 22:54:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-222460</guid>
		<description>Finally fixed the problem with these instructions found on internettablettalk:
First install "becomeroot" - becomeroot_0.1-2_armel.deb from:
http://eko.one.pl/maemo/index.php?path=dists%2Fbora%2Fuser%2Fbinary-armel/
- Just use application manager's "install from file" option to install, selecting the .deb file.
 
Then from xterm:

sudo gainroot
umount /media/mmc2
then
sfdisk /dev/mmcblk0 
0,,b  


 (hit enter until get back to main # prompt)

mkdosfs /dev/mmcblk0p1

--- and then reboot the device. Problem solved. Really gotta thank the guy who provided this info for some of us novices (with 30+ years of non-linux o/s and development experience).</description>
		<content:encoded><![CDATA[<p>Finally fixed the problem with these instructions found on internettablettalk:<br />
First install &#8220;becomeroot&#8221; - becomeroot_0.1-2_armel.deb from:<br />
<a href="http://eko.one.pl/maemo/index.php?path=dists%2Fbora%2Fuser%2Fbinary-armel/" rel="nofollow">http://eko.one.pl/maemo/index.php?path=dists%2Fbora%2Fuser%2Fbinary-armel/</a><br />
- Just use application manager&#8217;s &#8220;install from file&#8221; option to install, selecting the .deb file.</p>
<p>Then from xterm:</p>
<p>sudo gainroot<br />
umount /media/mmc2<br />
then<br />
sfdisk /dev/mmcblk0<br />
0,,b  </p>
<p> (hit enter until get back to main # prompt)</p>
<p>mkdosfs /dev/mmcblk0p1</p>
<p>&#8212; and then reboot the device. Problem solved. Really gotta thank the guy who provided this info for some of us novices (with 30+ years of non-linux o/s and development experience).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nb</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-222411</link>
		<dc:creator>nb</dc:creator>
		<pubDate>Fri, 04 Jan 2008 20:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-222411</guid>
		<description>Update:  I needed to execute:  "umount -l /media/mmc2"  to unmount my internal media card.

Unfortunately, the fsck.vfat command returned:
"dosfsck 2.11, 12 Mar 2005, FAT 32, LFN
Seek to 2055200256:Invalid Argument".

I rebooted and sought to use the control panel/memory  to disable virtual memory (that resides on the IMC). It showed a 64mb VM setup. Unclicking the check box to disable/remove the VM and oddly it said it couldn't undo the VM. I tried changing it to 128mb VM and that doesn't work. I'm going to assume it was trying to delete the VM file and couldn't.  I had hoped that after removing the VM I could use file manager to reformat the IMC. Oh well.</description>
		<content:encoded><![CDATA[<p>Update:  I needed to execute:  &#8220;umount -l /media/mmc2&#8243;  to unmount my internal media card.</p>
<p>Unfortunately, the fsck.vfat command returned:<br />
&#8220;dosfsck 2.11, 12 Mar 2005, FAT 32, LFN<br />
Seek to 2055200256:Invalid Argument&#8221;.</p>
<p>I rebooted and sought to use the control panel/memory  to disable virtual memory (that resides on the IMC). It showed a 64mb VM setup. Unclicking the check box to disable/remove the VM and oddly it said it couldn&#8217;t undo the VM. I tried changing it to 128mb VM and that doesn&#8217;t work. I&#8217;m going to assume it was trying to delete the VM file and couldn&#8217;t.  I had hoped that after removing the VM I could use file manager to reformat the IMC. Oh well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nb</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-222378</link>
		<dc:creator>nb</dc:creator>
		<pubDate>Fri, 04 Jan 2008 17:42:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-222378</guid>
		<description>I'm having the same problem with my N810 after an upgrade - MMC2 is read only.  Because its mounted and read-only you cannot reformat it from the file manager as the format command is as a result not available.

So I tried the suggestions above. However, on my windows XP I tried executing "flasherGui.exe -enable-rd-mode" as I don't have "flasher-3.0-static" there. It just wanted to reflash my system. Apparently this version  doesn't recognize the "-enable..." command line option.

I did however simply install "becomeroot" on my N810. I can execute "sudo gainroot" successfully. However, each time I attempt to execute "umount /media/mmc2", it fails with a "device busy" message.

I've disabled all applets, I uninstalled the "map" application (that puts its maps on mmc2) and the tutorial applet. I only have becomeroot and osso-xterm apps installed. Still the "device busy" persists.</description>
		<content:encoded><![CDATA[<p>I&#8217;m having the same problem with my N810 after an upgrade - MMC2 is read only.  Because its mounted and read-only you cannot reformat it from the file manager as the format command is as a result not available.</p>
<p>So I tried the suggestions above. However, on my windows XP I tried executing &#8220;flasherGui.exe -enable-rd-mode&#8221; as I don&#8217;t have &#8220;flasher-3.0-static&#8221; there. It just wanted to reflash my system. Apparently this version  doesn&#8217;t recognize the &#8220;-enable&#8230;&#8221; command line option.</p>
<p>I did however simply install &#8220;becomeroot&#8221; on my N810. I can execute &#8220;sudo gainroot&#8221; successfully. However, each time I attempt to execute &#8220;umount /media/mmc2&#8243;, it fails with a &#8220;device busy&#8221; message.</p>
<p>I&#8217;ve disabled all applets, I uninstalled the &#8220;map&#8221; application (that puts its maps on mmc2) and the tutorial applet. I only have becomeroot and osso-xterm apps installed. Still the &#8220;device busy&#8221; persists.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-221484</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Tue, 01 Jan 2008 23:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-221484</guid>
		<description>@Tom: See "read-only" and try again</description>
		<content:encoded><![CDATA[<p>@Tom: See &#8220;read-only&#8221; and try again</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-211521</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 11 Dec 2007 11:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-211521</guid>
		<description>Or, you could just have used the "Format memory card" option in the File Manager (in the Tools submenu).</description>
		<content:encoded><![CDATA[<p>Or, you could just have used the &#8220;Format memory card&#8221; option in the File Manager (in the Tools submenu).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: timsamoff</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-211184</link>
		<dc:creator>timsamoff</dc:creator>
		<pubDate>Mon, 10 Dec 2007 20:12:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-211184</guid>
		<description>The maemo folks think that they have solved the read-only MMC bug (with the latest OS2007 update)... But, it appears that it still exists for many people... Could you add the steps in this post to the bugzilla report?</description>
		<content:encoded><![CDATA[<p>The maemo folks think that they have solved the read-only MMC bug (with the latest OS2007 update)&#8230; But, it appears that it still exists for many people&#8230; Could you add the steps in this post to the bugzilla report?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miker</title>
		<link>http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/comment-page-1/#comment-211175</link>
		<dc:creator>miker</dc:creator>
		<pubDate>Mon, 10 Dec 2007 19:29:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/2007/12/10/hacking-n810-after-firmware-update/#comment-211175</guid>
		<description>There's already a bug in there about MMC cards getting set read-only, sounds like the cause hasn't really been isolated yet though.</description>
		<content:encoded><![CDATA[<p>There&#8217;s already a bug in there about MMC cards getting set read-only, sounds like the cause hasn&#8217;t really been isolated yet though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
