![]() |
Community request - what are your boot options (instructions provided)
Hi.
So I recently bricked my phone (it wasn't booting). I'm guessing I would able to recover from this situation if: 1. I would have a copy of preinit script. 2. I would know what boot options to use. So. Now I'm wondering if all clean Harmattans boot with (more or less) the same options or are there differences that are significant. So, unless there is some doc about this (and I haven't found one) - I need you :-). Please do the following: 1. Run SDK Connectivity (let's call it SDK-C). 2. Open PuTTy and connect to your device (IP is in the SDK-C). 3. The user name is always "developer"; and your password is in SDK-C. 4. Copy& paste this command: Code:
sed -r 's/(imei|dbi-uid|SerialNumber)=[0-9A-Z]+/\1=[private]/gI' < /proc/cmdline 6. Paste this in this thread :-) Also please state if you are using NITDroid, Mer, Inception, Open mode or any other system-level modification. So, I'll start :D. I'm currently in Open mode with NITDroid and my boot options are: Code:
init=/sbin/preinit root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw mtdoops.mtddev=log mtdoops.record_size=65536 console=tty0 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),16384k@3840k(kernel),2048k@20224k(log),469248k@22272k(var),32768k@491520k(moslo) bootreason=pwr_key bootmode=normal nolo=2.3.6 product_name=RM-696 dbi-type=V5JW dbi-vendor=1 dbi-size=73 dbi-uid=[private] imei=[private] g_nokia.iSerialNumber=[private] serialnumber=[private] omap_sec.kci=958 gpio=cmt_apeslpx:93:sysfs:output,cmt_en:23:sysfs:init_active:output,cmt_rst_rq:88:sysfs:init_active:output,sleep_ind:92:sysfs:output omapdss.def_disp_enabled=1 vhash=285e93eebfdded180a3ffdf0a42c0d09b0d8ce8a product_model=N9 hwid=1601 |
Re: Community request - what are your boot options (instructions provided)
Code:
init=/sbin/preinit root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw mtdoops.mtddev=log mtdoops.record_size=65536 console=tty0 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),16384k@3840k(kernel),2048k@20224k(log),469248k@22272k(var),32768k@491520k(moslo) bootreason=sw_rst bootmode=normal nolo=2.3.6 product_name=RM-680 imei=[private] g_nokia.iSerialNumber=[private] serialnumber=[private] omap_sec.kci=916 battery-type=BL-4D gpio=cmt_apeslpx:93:sysfs:output,cmt_en:23:sysfs:init_active:output,cmt_rst_rq:88:sysfs:init_active:output,keypad_slide:109:key:inverted,sleep_ind:92:sysfs:output omapdss.def_disp_enabled=1 vhash=0ff64214fdeedc558276b1eae8f3e0e6c9683672 product_model=N950 hwid=1124 |
Re: Community request - what are your boot options (instructions provided)
have you tried fix malf state to get your phone up?
It could also be it isn't booting as the battery level has fallen down to below the reserve level... In that case you would need flasher to charge it to 10% and then charge via wall plug to boot... |
Re: Community request - what are your boot options (instructions provided)
Quote:
Setting boot from flasher would have worked from me if only I had backup preinit script before I messed up. Hence I wanted to gather other people settings to find out if there is a single boot string that could be passed to flasher to help in such situations. |
Re: Community request - what are your boot options (instructions provided)
Vanilla:
Code:
init=/sbin/preinit root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw mtdoops.mtddev=log mtdoops.record_size=65536 console=tty0 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),16384k@3840k(kernel),2048k@20224k(log),469248k@22272k(var),32768k@491520k(moslo) bootreason=pwr_key bootmode=normal nolo=2.3.6 product_name=RM-696 dbi-type=V5JW dbi-vendor=1 dbi-size=73 dbi-uid=[private] imei=[private] g_nokia.iSerialNumber=[private] serialnumber=[private] omap_sec.kci=958 gpio=cmt_apeslpx:93:sysfs:output,cmt_en:23:sysfs:init_active:output,cmt_rst_rq:88:sysfs:init_active:output,sleep_ind:92:sysfs:output omapdss.def_disp_enabled=1 vhash=285e93eebfdded180a3ffdf0a42c0d09b0d8ce8a product_model=N9 hwid=1603 |
Re: Community request - what are your boot options (instructions provided)
N9 PR1.3_PR_LEGACY_005 with Open Mode:
Code:
init=/sbin/preinit root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw mtdoops.mtddev=log mtdoops.record_size=65536 console=tty0 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),16384k@3840k(kernel),2048k@20224k(log),469248k@22272k(var),32768k@491520k(moslo) bootreason=pwr_key bootmode=normal nolo=2.3.6 product_name=RM-696 dbi-type=V5JW dbi-vendor=1 dbi-size=73 dbi-uid=[private] imei=[private] g_nokia.iSerialNumber=[private] serialnumber=[private] omap_sec.kci=958 gpio=cmt_apeslpx:93:sysfs:output,cmt_en:23:sysfs:init_active:output,cmt_rst_rq:88:sysfs:init_active:output,sleep_ind:92:sysfs:output omapdss.def_disp_enabled=1 vhash=285e93eebfdded180a3ffdf0a42c0d09b0d8ce8a product_model=N9 hwid=1501 |
Re: Community request - what are your boot options (instructions provided)
N9 black/64G PR1.3, open mode with nitdroid kernel "Linux RM696 2.6.32.54-dfl61-20121301 #52 PREEMPT Thu Jul 5 02:32:54 MSK 2012 armv7l GNU/Linux"
Code:
init=/sbin/preinit root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw mtdoops.mtddev=log mtdoops.record_size=65536 console=tty0 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),16384k@3840k(kernel),2048k@20224k(log),469248k@22272k(var),32768k@491520k(moslo) bootreason=pwr_key bootmode=normal nolo=2.3.6 product_name=RM-696 dbi-type=V5JW dbi-vendor=1 dbi-size=73 dbi-uid=[private] imei=[private] g_nokia.iSerialNumber=[private] serialnumber=[private] omap_sec.kci=958 gpio=cmt_apeslpx:93:sysfs:output,cmt_en:23:sysfs:init_active:output,cmt_rst_rq:88:sysfs:init_active:output,sleep_ind:92:sysfs:output omapdss.def_disp_enabled=1 vhash=285e93eebfdded180a3ffdf0a42c0d09b0d8ce8a product_model=N9 hwid=1501 |
Re: Community request - what are your boot options (instructions provided)
So I recently had an occasion to try this out and it seems N9 doesn't work with flasher's boot parameter.
Fortunately Coderus gave me a clue which lead me to making a Rescue CD for N9 (and N950). Here is more info: http://wiki.maemo.org/N9/N950_Rescue_CD Of course if you happen to already have Debian as your main system (I have my on VirtualBox) then you could install flasher and download smaller rescue images (available on MeeGo wiki). |
Re: Community request - what are your boot options (instructions provided)
maybe you could simply provide the contend of n9-rescue directory?
not everybody cares about debian crap leave alone uses it |
Re: Community request - what are your boot options (instructions provided)
Quote:
But if you want to use it on whatever Linux you have you can use original instructions. They mention you have to mount rootfs manually so I'm guessing this kind of things might be partially distribution, partially your own settings dependent. Here is a direct link to original instructions. If - for whatever reason - above will not be available you can also get the contents of the directory from linked livecd9-config.7zip. The files are in: Code:
livecd9-config/livecd9/config/chroot_local-includes/etc/skel/n9-rescue/ |
All times are GMT. The time now is 01:06. |
vBulletin® Version 3.8.8