peterleinchen | # 1031 | 2013-12-30, 23:11 | Report

Maybe juiceme (or rainisto?) can tell more?

peterleinchen | # 1032 | 2013-12-30, 23:15 | Report

Either in /var/log/syslog (same under nitdroid?) or just nowhere.

Is preinit_nitdroid executable? (was most common problem)
If so, you have all those echos as debug logging to see where it goes nuts...
--
send/post your preinit and tell once more where your rootfs and home and nitdroid partition/folder is

---

Last edited by peterleinchen; 2013-12-30 at 23:20.

taixzo | # 1033 | 2013-12-31, 04:55 | Report

Thank you! Chmodding /sbin/preinit_nitdroid to 755 fixed the problem and now it boots fine!

juiceme | # 1034 | 2013-12-31, 07:29 | Report

I have exactly the same version as you have, 1501, and that is the device I looked up the MTD2 information from.

On the kernel command line you can see the partition table of the MTD flash that is given by NOLO to the booting kernel. My line looks like this:

mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),1638 4k@3840k(kernel),2048k@20224k(log),469248k@22272k( var),32768k@491520k(moslo)

Does your device have a different line there? (you can see it by "cat /proc/cmdline")

peterleinchen | # 1035 | 2013-12-31, 08:50 | Report

Just for completeness:
mine is 1601.
And cmdline looks exactly like juiceme's.

That is really strange!

--
also for completeness (to fetch more information):
your device is a 64GB?
the firmwares match your product code?
they are PR1.3 firmwares?
...?

---

Last edited by peterleinchen; 2013-12-31 at 08:55.

juiceme | # 1036 | 2013-12-31, 11:08 | Report

Yes, I did not think about that but your PR level could actually matter
It's been so long since I had anything else than PR1.3 I cannot remember how it was (if I ever even looked, really), but in theory it is possible that the MTD assignments could be changed between the releases. For BOOT and CAL partitions I doubt it, but for the other ones, it is a possibility.

So, for completeness sake, please tell the variant and PR level.

fejd | # 1037 | 2013-12-31, 12:04 | Report

My cmdline looks a bit different:

mtdparts=omap2-onenand:512k(bootloader),1408k@512k(config),8192k@ 1920k(kernel),1024k@10112k(log),496768k@11136k(var ),16384k@507904k(moslo)

Yes, it's the 64GB version and in "About device" I see version:
PR1.3 (40.2012.21-3.339.2_PR_339)
If I pull out the SIM card and peek within, it says RM-696 and so I flashed this variant:
059L7N6_N9 RM-696 Country Variant Sweden SE Black 64GB
Before that I flashed:
059H2M6_RM-696 NDT 64GB ROW BLACK

peterleinchen | # 1038 | 2013-12-31, 12:53 | Report

Did you flash only rootfs (firmware.bin)?
Or also eMMC ?

In latter case I am fully out of ideas. In first case it might be a try to flash both in one command!? [another wild guess]

btw: why did you voluntarily switched from ROW to country variant?
What is your product code?

juiceme | # 1039 | 2013-12-31, 13:47 | Report

That is just crazy, I have no idea how and why your commandline defines the kernel partition as 8MB. I have never seen anything like that!

Probably @rainisto is the only one who could explain that...

fejd | # 1040 | 2014-01-01, 11:11 | Report

You might be on to something there, I checked the SIM tray and it says 059J187, which is "059J187_RM-696 NDT NORTH EUROPE BLACK 64GB" (which I did not try to flash)! For some reason I thought the differences of the ROW/variant images were only the pre-loaded stuff, like maps, but it seems like there are more fundamental differences. Thanks, I'll try to flash it and see if it works better!