Reply
Thread Tools
Posts: 578 | Thanked: 994 times | Joined on Dec 2012
#11
The most important is second partition. If it's corrupted and you flash fresh rootfs so optification fails and can't boot. Maybe fsck can help or you can flash once again rootfs and before first boot use rescue os to swap emmc with sd card in /lib/udev/mmc_id (1>0, 0>1). It should boot after 1-2 minutes and then you can easy copy yours data.
 

The Following 4 Users Say Thank You to elros34 For This Useful Post:
Posts: 224 | Thanked: 132 times | Joined on Jun 2012 @ Cairo ;Egypt
#12
to get the data out from the eMMC Possible use Parted Magic to solve this problem




Open opt or MyDocs or home Whatever you want I hope it helps you


to Open home or opt You must connect the mobile in case of booting And choose backupmenu then choose "W" red and write


 

The Following 2 Users Say Thank You to amr.fayz For This Useful Post:
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#13
Originally Posted by elros34 View Post
The most important is second partition. If it's corrupted and you flash fresh rootfs so optification fails and can't boot. Maybe fsck can help or you can flash once again rootfs and before first boot use rescue os to swap emmc with sd card in /lib/udev/mmc_id (1>0, 0>1). It should boot after 1-2 minutes and then you can easy copy yours data.
wont rescueos void warranty?
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here
 

The Following User Says Thank You to marmistrz For This Useful Post:
mrsellout's Avatar
Posts: 889 | Thanked: 2,087 times | Joined on Sep 2010 @ Manchester
#14
There is no warranty anymore is there?, and anyway IIRC you only load the rescue os kernel into memory.

Once you have retrieved your data, you should do a full FIASCO + eMMC flash of your device and you'll be back to factory conditions.

http://wiki.maemo.org/Updating_the_firmware

Edit: In fact the wiki makes reference to your issue:
http://wiki.maemo.org/Updating_the_f...k_and_forth.22

Last edited by mrsellout; 2013-04-03 at 13:27.
 

The Following 2 Users Say Thank You to mrsellout For This Useful Post:
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#15
Originally Posted by Wikiwide View Post
initfs - on EMMC, actually - is corrupted
Oh my god! somebody's wrong on the Internet!

As already indicated below by @elros34 the "no initfs \o/" message is always shown when R&D is active.

Look in /sbin/preinit.
 

The Following 2 Users Say Thank You to reinob For This Useful Post:
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#16
Originally Posted by marmistrz View Post
1. Enable & disable R&D mode - no effect. Inbetween "no initfs \o/" was shown
2. Flashing kernel power 51 (using cssu-thumb) - no effect
3. Flashing rootfs - no effect
As the risk of suggesting the obvious: have you tried flashing not only kernel and not only rootfs but the whole combined image?

Flashing the kernel alone won't help because the modules will (likely) be missing. Flashing the rootfs alone won't help because the kernel will (likely) not match.

The problem is that the stock kernel requires modules that are in the rootfs, so you need both to match.

Other than that, *in principle*, the N900/Maemo5 can boot without an eMMC, so if flashing kernel and rootfs goes OK your N900 should boot.
 

The Following 2 Users Say Thank You to reinob For This Useful Post:
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#17
Is it normal that my internal 32G is /dev/mmcblk1? Shouldn't it be /dev/mmcblk0?

/edit: removed the memory card, the internal is back /dev/mmcblk0. Reflashed again, maybe it'll fix. fscking /dev/mmcblk0p1 & /dev/mmcblk0p2 tells that partitions are clean
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here

Last edited by marmistrz; 2013-04-03 at 15:28.
 

The Following 2 Users Say Thank You to marmistrz For This Useful Post:
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#18
Originally Posted by marmistrz View Post
Is it normal that my internal 32G is /dev/mmcblk1? Shouldn't it be /dev/mmcblk0?
For the kernel mmcblk1 is the eMMC (internal) and mmcblk0 is the MMC (extendal).

For Maemo it's the other way around. udev does the swap. Probably for script-compatibility with who knows what ancient tablet

(like the whole upstart-but-also-some-sysvinit we also have).

If I didn't like the N900 so much I would really say that Maemo is a stinking piece of shît.
 

The Following User Says Thank You to reinob For This Useful Post:
Posts: 19 | Thanked: 16 times | Joined on Nov 2011
#19
Hi, this may be just a random guess, but have you tried to boot the N900 without the SIM card?

I don't know if it is the same issue, but about two weeks ago my device was stuck at the five blinking dots, same as yours.
It turned out that the SIM was the problem, without it the N900 boot up regularly.
 

The Following User Says Thank You to Lestat For This Useful Post:
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#20
Originally Posted by Lestat View Post
Hi, this may be just a random guess, but have you tried to boot the N900 without the SIM card?

I don't know if it is the same issue, but about two weeks ago my device was stuck at the five blinking dots, same as yours.
It turned out that the SIM was the problem, without it the N900 boot up regularly.
well it doesnt work even without the sim.
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here
 

The Following User Says Thank You to marmistrz For This Useful Post:
Reply

Tags
nokia n900


 
Forum Jump


All times are GMT. The time now is 06:11.