Re: Only boots up in RD Mode
 

Don't worry, it's pretty cheap. Talk about ~1$. By the way, anyone got an idea what may cause wrong raw BSI value readings + wrong bme battery SoC readings at the same time?...

Also, could You re-try all "{cat /sys/class (...)" again? With full battery?

Re: Only boots up in RD Mode
 

bme state of charge readings depend on correct BSI. If BSI is wrong, bme SOC measurement is also wrong, frozen, or always 0.

Re: Only boots up in RD Mode
 

I retried "cat /sys/class/..."
Have the same results but /charge_full wich gives '2056320' value

Re: Only boots up in RD Mode
 

I just found the time to do this - mind letting me know what options you entered into the compiler command to get it to compile when you got it working?

Re: Only boots up in RD Mode
 

I always run a kernel with framebuffer (as you know by my shell-at-boot thing): However, I just got my N900 into a not booting state, thanks to, of course, my skill at making mistakes in my /sbin/preinit modifications. (I think I forgot to close a "for" loop with a "done" again.) So I'll let you know when I get the device running and flashed to the right kernel, etc, etc, again.)

Re: Only boots up in RD Mode
 

Ah, I figured it out: To use the libcal library, I needed to add the "-lcal" flag to the gcc command. Also, using '-Wall' was making it not compile because of an implicit mention of ioctl or something like that. Without that it compiled fine. I'm gonna test it as soon as the CSSU and busybox-power are installed on my N900 again.

Re: Only boots up in RD Mode
 

You're right.. I forgot to tell how I could finally compile the file!
Just using -lcal flag as you said (compile for armel) is enough...

Re: Only boots up in RD Mode
 

Off the top of my head, I think it's something to do with the battery, obviously, but I don't remember what. One of the watchdogs is at /dev/tw14030_wdt (as you can see in bootmenu, and in my /sbin/preinit boot-shell mod), but that's all I can say. Also, I THINK pali mentions tw14030 in the post where he posted his original getbootstate open-source backport+clone. Speaking of, I'm about to test pali's open source getbootstate. Wish me luck and such. :D

Coming back to this tho:
With R&D mode off and framebuffer running on power kernel 47, I can verify it looks like the correct/normal state is "USER". (Actually I think it's the correct state with R&D mode on too.)

Re: Only boots up in RD Mode
 

You know what else is awesome? This just solved something I didn't know how to do for a couple of months (I was writing a command-line tool to change R&D Mode flags on-device - qwerty12 made one in the old days long forgotten that has a simple GUI, but it's gui-ONLY and not useful from the recovery consoles, which you may want to turn R&D mode on/off from).

ANYWAY - I've just rebooted my N900 using the open source getbootstate and it WORKED. Now, it worked only ONCE, since I have only rebooted with it once. But it worked, no R&D mode on or anything, no errors thrown out. I call that reason to tentatively get our hopes up.

Re: Only boots up in RD Mode
 

Rebooted again a second time. Still boots fine - however I noticed that at first it said "Entering state SHUTDOWN" each time at boot. Since my memory sucks I don't quiet remember if this is the same getbootstate behavior as the closed source getbootstate binary gave after a normal shutdown+turn on...Or if this is the same thing that I just said had the 'correct' state of USER just two posts ago (since USER appears in one place for sure during normal boot, and if I recall correctly it shows up where SHUTDOWN is showing up for me now... Except this time I'm really not sure I recall correctly..).

Re: Only boots up in RD Mode
 

When I couldn't boot in normal mode with closed source binary, the getbootstate log showed up that warning (Entering state: SHUTDOWN).

In R&D mode first boot showed: Entering state: ACT DEAD

Now, with Pali's getbootstate modification, I don't get "SHUTDOWN" warning but only "Entering state: USER"

Re: Only boots up in RD Mode
 

Okay, then I am remembering correctly - it was saying USER with normal getbootstate, and is saying SHUTDOWN with pali's getbootstate. (I haven't tested Estel-modified getbootstate though.)

What's odd is that it still boots for me even though it says "Entering state: SHUTDOWN"

Re: Only boots up in RD Mode
 

Mentalist: It's weird that you get the SHUTDOWN warning but the device starts up... Don't know what could be happening there..

--------------
I don't know this is normal and/or it could be cause of problems:

Every time I take the battery out from the device and then start it up, it asks me to enter date and time configuration. Doesn't the n900 has an internal battery to save this configuration?

The boot log shows some lines with warnings about clock (I will try to be more specific about those warnings and try to post them later).

Re: Only boots up in RD Mode
 

[QUOTE=jvollmann;1056156]
Every time I take the battery out from the device and then start it up, it asks me to enter date and time configuration. Doesn't the n900 has an internal battery to save this configuration?
/QUOTE]

This is perfectly normal. If you unplug battery for short time (~5 seconds max) time and date will remain intact. Otherwise, it reset. Ho ever, if You have "auto update time and date" checked and SIM card inserted, + You unlock PIN on turning on, date and time will be automatically set correctly, yet still you'll see enter time/date prompt (with correct date in it already present).

So, it have nothing to do with Your problem. ho ever, warnings about date and time *may* be interesting (most unlikely, but better safe than sorry), so of course post it here.

---

Still, I think You got charging chip damaged. Probably, most convenient way for You is to mod Your cover (or buy mugen cover and mod it) to contain charging port, + buy cheap small Li-Ion charger (most likely, for small AA-like cells) and mod it to have cable fitting into Your cover new plug. Then, of course, You also need to mod battery a little and connect it with plug inside Your cover ;)

This way, you can screw bme readings totally (AFAIU, despite low battery warnings, You can use Your device until battery is empty, right?), charge your battery "as normal" using modified charging system - even with device ON (ho ever, I would not charge it to absolutely 100%, due to device sucking power for operation, that may confuse charger - no big deal, N900 internal charger is also confused by it, anyway ;) just not so-healthy for batteries), so you *almost* don't feel downsides of Your problem.

By the way, You may almost "kill two deer by one spear" and make yourself nice dual-scud mod, aka 3000 mAh battery (or much cheaper 2500 mAh alternative). Check my signature for appropriate thread.

---

By the way, writing this reminded me about some thing. IF Your bme isn't working correctly, how device know when to shut down? It shut down properly (bright white diode fading etc, @ little less than 3200 mV), or is it used to ~2800 mV and just die due to low power?

Re: Only boots up in RD Mode
 

I installed power kernel 47 but I haven't found framebuffer/log for this version. Anyone knows how to activate/install framebuffer on power kernel?

If everything fails I will try that!


I attached an image of BatteryGraph wich shows that it measures volts right. When I connect charger while running BatteryGraph, it doesn't change any info about "charge" value, it stays the same...

Re: Only boots up in RD Mode
 

Yes, that's right.. As soon as the device starts up, the battery life keeps low and some minutes later shows "low battery" warning. However, I can use the phone as usual

Re: Only boots up in RD Mode
 

Just FYI, N900's internal battery that preserves time settings gets weaker as time goes on. So while it SHOULD hold enough charge to be certain of correct date, it starts prompting you for date/time confirmation a lot sooner if you compare brand new N900 to an N900 used for a year or two. It does seem to keep the time accurately for a while though, as it takes a while for it to reset the date - usually on my device it prompts you even after a quick pull-in-out of battery, but time and date is the same as it should be if the battery wasn't out for long.

Framebuffer on kernel power v47 (and v48) is enabled by "modprobe fbcon". I personally have it inserted at the (almost) very beginning of /sbin/preinit - I have it inserted after line 28 in that file. Gets framebuffer module loaded early enough to see the getbootstate stuff.

Re: Only boots up in RD Mode
 

Thanks to mentalist I could enable framebuffer, these are the lines that showed errors or warnings during boot up (using Estel's getbootstate):

Re: Only boots up in RD Mode
 

I'm attaching the whole boot log...

By the way: I noticed that when the device is turned off and I connect usb cable, getbootstate shows ACT DEAD.. a little later says ACT DEAD: charger (off?)....

Don't know if that's normal output

Re: Only boots up in RD Mode
 

hello, can anyone help pls.

i'm having battery issues, rapid drain, reboot loops. i dont exactly know what is wrong. i run dmesg and below is what i got.

can someone pls have a look at it for me pls? the charger/or usb is not connected when i ran this. thanks.

/root$ dmesg
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.28.10-power47 (builder1@wml0226) (gcc version 4.2.1) #1 PREEMPT Tue May 3 20:40:52 EEST 2011
[ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Nokia RX-51 board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 65536
[ 0.000000] free_area_init_node: node 0, pgdat c039864c, node_mem_map c03da000
[ 0.000000] Normal zone: 512 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 65024 pages, LIFO batch:15
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] OMAP3430 ES3.1
[ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
[ 0.000000] VRAM: 5357568 bytes at 0x8f578000. (Detected 868352 at 0x8f9c0000)
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: init=/sbin/preinit ubi.mtd=rootfs root=ubi0:rootfs rootfstype=ubifs rootflags=bulk_read,no_chk_data_crc rw console=ttyMTD,log console=tty0 snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6
[ 0.000000] Clocking rate (Crystal/DPLL/ARM core): 19.2/332/500 MHz
[ 0.000000] Reprogramming SDRC
[ 0.000000] GPMC revision 5.0
[ 0.000000] IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
[ 0.000000] Total of 96 interrupts on 1 active controller
[ 0.000000] OMAP34xx GPIO hardware version 2.5
[ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [tty0] enabled
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] allocated 1310720 bytes of page_cgroup
[ 0.000000] please try cgroup_disable=memory option if you don't want
[ 0.000000] Memory: 128MB 128MB = 256MB total
[ 0.000000] Memory: 244924KB available (3312K code, 445K data, 144K init)
[ 0.000000] SLUB: Genslabs=8, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
[ 0.000000] Security Framework initialized
[ 0.000000] Mount-cache hash table entries: 512
[ 0.000000] Initializing cgroup subsys memory
[ 0.000000] Initializing cgroup subsys freezer
[ 0.000000] CPU: Testing write buffer coherency: ok
[ 0.000000] net_namespace: 740 bytes
[ 0.000000] regulator: core version 0.5
[ 0.000000] NET: Registered protocol family 16
[ 2.420715] OMAP DMA hardware revision 4.0
[ 2.420837] Reserving DMA channels 0 and 1 for HS ROM code
[ 2.421936] MUX: setup J21_34XX_I2C1_SDA (0xd80021bc): 0x0100 -> 0x0118
[ 2.421997] MUX: setup K21_34XX_I2C1_SCL (0xd80021ba): 0x0100 -> 0x0118
[ 2.422119] MUX: setup AE15_34XX_I2C2_SDA (0xd80021c0): 0x0100 -> 0x0118
[ 2.422180] MUX: setup AF15_34XX_I2C2_SCL (0xd80021be): 0x0100 -> 0x0118
[ 2.422302] MUX: setup AG14_34XX_I2C3_SDA (0xd80021c4): 0x0100 -> 0x0118
[ 2.422363] MUX: setup AF14_34XX_I2C3_SCL (0xd80021c2): 0x0100 -> 0x0118
[ 2.422821] USB: No board-specific platform config found
[ 2.425872] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2200 kHz
[ 2.427276] TWL5030: Enabling workaround for rev 0x1009002F
[ 2.444824] twl4030: PIH (irq 7) chaining IRQs 368..375
[ 2.444885] twl4030: power (irq 373) chaining IRQs 376..383
[ 2.445190] twl4030: gpio (irq 368) chaining IRQs 384..401
[ 2.446319] regulator: VDAC: 1800 mV normal standby
[ 2.446685] regulator: VUSB1V5: 1500 mV normal standby
[ 2.447021] regulator: VUSB1V8: 1800 mV normal standby
[ 2.447357] regulator: VUSB3V1: 3100 mV normal standby
[ 2.447692] i2c_omap i2c_omap.2: bus 2 rev3.12 at 100 kHz
[ 2.448669] i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
[ 2.450225] console [ttyMTD0] enabled
[ 2.453918] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[ 2.453918] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
[ 2.454437] usbcore: registered new interface driver usbfs
[ 2.454620] usbcore: registered new interface driver hub
[ 2.454925] usbcore: registered new device driver usb
[ 2.454956] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
[ 2.458190] HS USB OTG: revision 0x33, sysconfig 0x2010, sysstatus 0x1, intrfsel 0x1, simenable 0x0
[ 2.458251] musb_hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine (X), bulk split (X), HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[ 2.458282] musb_hdrc: MHDRC RTL version 1.400
[ 2.458282] musb_hdrc: setup fifo_mode 5
[ 2.458312] musb_hdrc: 21/31 max ep, 9312/16384 memory
[ 2.458343] musb_hdrc: hw_ep 0shared, max 64
[ 2.458343] musb_hdrc: hw_ep 1tx, max 512
[ 2.458374] musb_hdrc: hw_ep 1rx, max 512
[ 2.458374] musb_hdrc: hw_ep 2tx, max 512
[ 2.458374] musb_hdrc: hw_ep 2rx, max 512
[ 2.458404] musb_hdrc: hw_ep 3tx, max 512
[ 2.458404] musb_hdrc: hw_ep 3rx, max 512
[ 2.458435] musb_hdrc: hw_ep 4tx, max 512
[ 2.458435] musb_hdrc: hw_ep 4rx, max 512
[ 2.458465] musb_hdrc: hw_ep 5tx, max 16
[ 2.458465] musb_hdrc: hw_ep 5rx, max 512
[ 2.458465] musb_hdrc: hw_ep 6tx, max 512
[ 2.458496] musb_hdrc: hw_ep 6rx, max 512
[ 2.458496] musb_hdrc: hw_ep 7tx, max 16
[ 2.458526] musb_hdrc: hw_ep 7rx, max 512
[ 2.458526] musb_hdrc: hw_ep 8tx, max 512
[ 2.458526] musb_hdrc: hw_ep 8rx, max 512
[ 2.458557] musb_hdrc: hw_ep 9tx, max 512
[ 2.458557] musb_hdrc: hw_ep 9rx, max 512
[ 2.458587] musb_hdrc: hw_ep 10tx, max 512
[ 2.458587] musb_hdrc: hw_ep 11tx, max 512
[ 2.458618] musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
[ 2.458801] Registered /proc/driver/musb_hdrc
[ 2.483673] NET: Registered protocol family 2
[ 2.490356] Switched to high resolution mode on CPU 0
[ 2.552978] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 2.553344] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 2.553649] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[ 2.553863] TCP: Hash tables configured (established 8192 bind 8192)
[ 2.553894] TCP reno registered
[ 2.576446] NET: Registered protocol family 1
[ 2.597930] VFS: Disk quotas dquot_6.5.1
[ 2.598083] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 2.599578] msgmni has been set to 479
[ 2.600250] lowmem: Module initialized.
[ 2.608764] alg: No test for lzo999 (lzo999-generic)
[ 2.609039] alg: No test for stdrng (krng)
[ 2.609161] io scheduler noop registered
[ 2.609558] io scheduler cfq registered (default)
[ 2.609954] OMAP DSS rev 2.0
[ 2.610076] OMAP DISPC rev 3.0
[ 2.610168] OMAP VENC rev 2
[ 2.618011] OMAP3 ROM RNG: initializing
[ 2.620208] Serial: 8250/16550 driver4 ports, IRQ sharing disabled
[ 2.626739] brd: module loaded
[ 2.629089] loop: module loaded
[ 2.629180] i2c /dev entries driver
[ 2.630340] input: triton2-pwrbutton as /class/input/input0
[ 2.654449] triton2 power button driver initialized
[ 2.655059] OneNAND driver initializing
[ 2.656280] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base d0880000
[ 2.656372] OneNAND Manufacturer: Samsung (0xec)
[ 2.656402] Muxed OneNAND 256MB 1.8V 16-bit (0x40)
[ 2.656433] OneNAND version = 0x0121
[ 2.656463] Chip support all block unlock
[ 2.656463] Chip has 2 plane
[ 2.657989] Scanning device for bad blocks
[ 2.684814] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.684875] Bad eraseblock 470 at 0x03ac0000
[ 2.723358] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.723419] Bad eraseblock 1148 at 0x08f80000
[ 2.774505] Creating 6 MTD partitions on "omap2-onenand":
[ 2.774536] 0x00000000-0x00020000 : "bootloader"
[ 2.774932] 0x00020000-0x00080000 : "config"
[ 2.775177] 0x00080000-0x000c0000 : "log"
[ 2.777648] mtdoops: Ready 26, 27 (no erase)
[ 2.777679] mtdoops: Attached to MTD device 2
[ 2.777709] 0x000c0000-0x002c0000 : "kernel"
[ 2.777984] 0x002c0000-0x004c0000 : "initfs"
[ 2.778228] 0x004c0000-0x10000000 : "rootfs"
[ 2.780090] UBI: attaching mtd5 to ubi0
[ 2.780120] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 2.780181] UBI: logical eraseblock size: 129024 bytes
[ 2.780212] UBI: smallest flash I/O unit: 2048
[ 2.780242] UBI: sub-page size: 512
[ 2.780273] UBI: VID header offset: 512 (aligned 512)
[ 2.780303] UBI: data offset: 2048
[ 2.913513] UBI: attached mtd5 to ubi0
[ 2.913574] UBI: MTD device name: "rootfs"
[ 2.913635] UBI: MTD device size: 251 MiB
[ 2.913665] UBI: number of good PEBs: 2008
[ 2.913696] UBI: number of bad PEBs: 2
[ 2.913696] UBI: max. allowed volumes: 128
[ 2.913726] UBI: wear-leveling threshold: 4096
[ 2.913757] UBI: number of internal volumes: 1
[ 2.913787] UBI: number of user volumes: 1
[ 2.913818] UBI: available PEBs: 0
[ 2.913848] UBI: total number of reserved PEBs: 2008
[ 2.913879] UBI: number of PEBs reserved for bad PEB handling: 20
[ 2.913909] UBI: max/mean erase counter: 1790/319
[ 2.913940] UBI: image sequence number: 35
[ 2.914367] usbcore: registered new interface driver libusual
[ 2.914489] UBI: background thread "ubi_bgt0d" started, PID 26
[ 2.936248] input: omap_twl4030keypad as /class/input/input1
[ 2.984863] cpuidle: using governor ladder
[ 2.984924] cpuidle: using governor menu
[ 2.985107] Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
[ 2.985351] ASoC version 0.13.2
[ 2.998901] AIC3X Audio Codec 0.2
[ 3.001464] asoc: tlv320aic3x <-> omap-mcbsp-dai-0 mapping ok
[ 3.002960] asoc: Bluetooth codec <-> omap-mcbsp-dai-1 mapping ok
[ 3.054534] input: RX51 (tlv320aic3x) Jack as /class/input/input2
[ 3.078887] ALSA device list:
[ 3.078918] #0: RX51 (tlv320aic3x)
[ 3.079162] TCP cubic registered
[ 3.079193] Initializing XFRM netlink socket
[ 3.079284] NET: Registered protocol family 17
[ 3.079345] NET: Registered protocol family 15
[ 3.079376] ThumbEE CPU extension supported.
[ 3.079437] Power Management for TI OMAP3.
[ 3.082824] pm_dbg_init()
[ 3.083618] SmartReflex driver initialized
[ 3.089782] Disabling unused clock "gpt2_ick"
[ 3.089874] Disabling unused clock "gpt3_ick"
[ 3.089904] Disabling unused clock "gpt4_ick"
[ 3.089965] Disabling unused clock "gpt5_ick"
[ 3.089996] Disabling unused clock "gpt6_ick"
[ 3.090026] Disabling unused clock "gpt7_ick"
[ 3.090057] Disabling unused clock "gpt8_ick"
[ 3.090087] Disabling unused clock "gpt9_ick"
[ 3.090118] Disabling unused clock "uart3_ick"
[ 3.090148] Disabling unused clock "gpio2_dbck"
[ 3.090209] Disabling unused clock "gpio3_dbck"
[ 3.090240] Disabling unused clock "gpio4_dbck"
[ 3.090270] Disabling unused clock "gpio5_dbck"
[ 3.090301] Disabling unused clock "gpio6_dbck"
[ 3.090332] Disabling unused clock "gpt9_fck"
[ 3.090362] Disabling unused clock "gpt8_fck"
[ 3.090393] Disabling unused clock "gpt7_fck"
[ 3.090454] Disabling unused clock "gpt6_fck"
[ 3.090484] Disabling unused clock "gpt5_fck"
[ 3.090515] Disabling unused clock "gpt4_fck"
[ 3.090545] Disabling unused clock "gpt3_fck"
[ 3.090576] Disabling unused clock "gpt2_fck"
[ 3.090606] Disabling unused clock "uart3_fck"
[ 3.090667] Disabling unused clock "wdt2_ick"
[ 3.090698] Disabling unused clock "wdt2_fck"
[ 3.090728] Disabling unused clock "gpio1_dbck"
[ 3.090759] Disabling unused clock "rng_ick"
[ 3.090820] Disabling unused clock "ssi_ick"
[ 3.090850] Disabling unused clock "gpt10_ick"
[ 3.090881] Disabling unused clock "gpt11_ick"
[ 3.090911] Disabling unused clock "uart1_ick"
[ 3.090942] Disabling unused clock "uart2_ick"
[ 3.091003] Disabling unused clock "usbtll_ick"
[ 3.091033] Disabling unused clock "ssi_ssr_fck"
[ 3.091064] Disabling unused clock "uart1_fck"
[ 3.091125] Disabling unused clock "uart2_fck"
[ 3.091156] Disabling unused clock "usbtll_fck"
[ 3.091217] Disabling unused clock "ts_fck"
[ 3.091247] Disabling unused clock "cpefuse_fck"
[ 3.091278] Disabling unused clock "gpt11_fck"
[ 3.091308] Disabling unused clock "gpt10_fck"
[ 3.091369] Disabling unused clock "dpll5_ck"
[ 3.091430] Disabling unused clock "dpll4_m6x2_ck"
[ 3.091461] Disabling unused clock "dpll4_m5x2_ck"
[ 3.091522] Disabling unused clock "dpll3_m3x2_ck"
[ 3.091552] Disabling unused clock "sys_clkout1"
[ 3.091979] Bootup reason: pwr_key
[ 3.092071] OMAP GPIO switch handler initializing
[ 3.094635] slide (GPIO 71) is now closed
[ 3.094696] proximity (GPIO 89) is now open
[ 3.094726] kb_lock (GPIO 113) is now open
[ 3.094757] headphone (GPIO 177) is now disconnected
[ 3.094787] cam_shutter (GPIO 110) is now closed
[ 3.094818] cam_launch (GPIO 69) is now inactive
[ 3.094848] cam_focus (GPIO 68) is now inactive
[ 3.094879] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
[ 3.095489] registered taskstats version 1
[ 3.115600] omapfb: acx565akm rev 8d LCD detected
[ 3.147644] tpa6130a2 2-0060: Headphone amplifier initialized successfully
[ 3.167907] UBIFS: recovery needed
[ 3.211578] UBIFS: recovery completed
[ 3.211639] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.211700] UBIFS: file system size: 254564352 bytes (248598 KiB, 242 MiB, 1973 LEBs)
[ 3.211730] UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[ 3.211791] UBIFS: media format: 4 (latest is 4)
[ 3.211822] UBIFS: default compressor: lzo
[ 3.211853] UBIFS: reserved for root: 4384586 bytes (4281 KiB)
[ 3.212249] VFS: Mounted root (ubifs filesystem).
[ 3.212432] Freeing init memory: 144K
[ 5.772033] Registered led device: twl4030:vibrator
[ 5.789062] tsl2563 2-0029: model 7, rev. 0
[ 5.984741] twl4030_rtc twl4030_rtc: rtc core: registered

Re: Only boots up in RD Mode
 

this is the concluding part, i split it into two becos of the size...


struct_module
[ 6.597045] isp_mod: Unknown symbol iommu_restore_ctx
[ 6.597503] isp_mod: Unknown symbol iommu_vfree
[ 6.598236] isp_mod: Unknown symbol iommu_put
[ 6.598724] isp_mod: Unknown symbol iommu_save_ctx
[ 6.599151] isp_mod: Unknown symbol iommu_vunmap
[ 6.599670] isp_mod: Unknown symbol iommu_vmalloc
[ 6.608856] isp_mod: Unknown symbol iommu_get
[ 6.609497] isp_mod: Unknown symbol iommu_kmap
[ 6.610015] isp_mod: Unknown symbol da_to_va
[ 6.610565] isp_mod: Unknown symbol iommu_vmap
[ 6.610931] isp_mod: Unknown symbol iommu_kunmap
[ 6.611297] isp_mod: Unknown symbol videobuf_to_dma
[ 6.990417] i2c_omap i2c_omap.2: controller timed out
[ 7.047088] lp5523 2-0032: got interrupt from led chip
[ 7.047637] lp5523 2-0032: interrupt from led chip 4f
[ 7.047668] lp5523 2-0032: all engines configured
[ 7.047729] lp5523 2-0032: disabling engines
[ 7.048309] Registered led device: lp5523:kb1
[ 7.048461] Registered led device: lp5523:kb2
[ 7.048583] Registered led device: lp5523:kb3
[ 7.048736] Registered led device: lp5523:kb4
[ 7.048858] Registered led device: lp5523:b
[ 7.048980] Registered led device: lp5523:g
[ 7.049102] Registered led device: lp5523:r
[ 7.049255] Registered led device: lp5523:kb5
[ 7.049377] Registered led device: lp5523:kb6
[ 7.049957] bq27x00-battery 2-0055: support ver. 1.2.0 enabled
[ 7.103363] TSC2005 driver initializing
[ 7.108001] input: TSC2005 touchscreen as /class/input/input3
[ 7.123168] Bluetooth: Core ver 2.15
[ 7.140136] radio-si4713 2-0063: Detected Si4713 (0x0d) Firmware: 3.0 Patch ID: 00:00 Component: 3.0 Chip Rev.: unknown
[ 7.175781] NET: Registered protocol family 31
[ 7.175842] Bluetooth: HCI device and connection manager initialized
[ 7.175872] Bluetooth: HCI socket layer initialized
[ 7.396697] hci_h4p hci_h4p: Registering HCI H4P device
[ 7.428253] cfg80211: Using static regulatory domain info
[ 7.428283] cfg80211: Regulatory domain: US
[ 7.428283] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 7.428314] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 7.428314] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428344] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428344] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428375] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428375] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 7.428405] cfg80211: Regulatory domain changed to country: US
[ 7.428436] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 7.428436] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 7.428466] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428466] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428497] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428497] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428527] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 7.577697] nokia-av nokia-av: accessory detect module initialized
[ 7.758911] omap_wdt omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec, nowayout is on
[ 7.771728] SSI DRIVER Version 1.1-rc2
[ 7.772247] omap_ssi omap_ssi: SSI Hardware REVISION 1.0
[ 7.778900] smc91x: not found (-19).
[ 8.113250] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
[ 8.113403] mmc0: cover is open, card is now inaccessible
[ 8.132934] phy0: Selected rate control algorithm 'minstrel'
[ 8.139831] CMT speech driver v0.2.0
[ 8.225372] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
[ 8.455352] wl1251: loaded
[ 8.456054] wl1251: initialized
[ 8.458435] NET: Registered protocol family 35
[ 8.492736] SSI McSAAB PROTOCOL Version: 2.0-rc1
[ 8.625366] dspbridge_init: 412800 bytes @ 80600000
[ 8.662475] mmc1: new high speed MMC card at address 0001
[ 8.670166] mmcblk0: mmc1:0001 MMC32G 29.8 GiB
[ 8.670440] mmcblk0: p1 p2 p3
[ 8.895935] omap-iommu omap-iommu.1: isp registered
[ 9.091644] isp_mod: disagrees about version of symbol struct_module
[ 9.170013] omap-iommu omap-iommu.1: isp: version 1.1
[ 9.375946] smia-sensor 2-0010: firmware: requesting smia-sensor-01-022b-04.bin
[ 9.397155] smia_reglist_import: meta_reglist version 2009-07-27
[ 9.397247] smia_reglist_import: type 10 w 648 h 488 fmt 30314142 ival 100/1502 ptr d0d982a0
[ 9.397247] smia_reglist_import: type 10 w 648 h 488 fmt 30314142 ival 100/3003 ptr d0d98228
[ 9.397277] smia_reglist_import: type 1 w 0 h 0 fmt 30314142 ival 100/0 ptr d0d98090
[ 9.397277] smia_reglist_import: type 0 w 0 h 0 fmt 30314142 ival 100/0 ptr d0d98038
[ 9.413757] et8ek8 3-003e: firmware: requesting et8ek8-0002.bin
[ 9.434265] smia_reglist_import: meta_reglist version V4 alma 10.10.10
[ 9.434326] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314142 ival 100/399 ptr d0d9b464
[ 9.434356] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314442 ival 100/1292 ptr d0d9b204
[ 9.434387] smia_reglist_import: type 10 w 1728 h 1312 fmt 30314142 ival 100/11792 ptr d0d9b884
[ 9.434387] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/13000 ptr d0d9b7ec
[ 9.434417] smia_reglist_import: type 10 w 1296 h 984 fmt 30314142 ival 100/501 ptr d0d9b58c
[ 9.434448] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/3000 ptr d0d9b29c
[ 9.434448] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/2500 ptr d0d9b624
[ 9.434478] smia_reglist_import: type 10 w 864 h 656 fmt 30314142 ival 100/13584 ptr d0d9b754
[ 9.434478] smia_reglist_import: type 10 w 864 h 656 fmt 30314142 ival 100/2988 ptr d0d9b334
[ 9.434509] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/499 ptr d0d9b4f4
[ 9.434539] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/14779 ptr d0d9b6bc
[ 9.434539] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/2993 ptr d0d9b3cc
[ 9.434570] smia_reglist_import: type 1 w 2592 h 1968 fmt 30314142 ival 100/1207 ptr d0d9b05c
[ 10.214050] g_file_storage gadget: File-backed Storage Gadget, version: 7 August 2007
[ 10.214141] g_file_storage gadget: Number of LUNs=2 Number of buffers=16
[ 10.214172] musb_hdrc musb_hdrc: MUSB HDRC host driver
[ 10.216156] /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file 'devices'
[ 10.216217] /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '001'
[ 10.218261] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[ 10.218444] usb usb1: default language 0x0409
[ 10.218811] usb usb1: uevent
[ 10.220550] usb usb1: usb_probe_device
[ 10.220581] usb usb1: configuration #1 chosen from 1 choice
[ 10.220672] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[ 10.220825] usb 1-0:1.0: uevent
[ 10.221984] hub 1-0:1.0: usb_probe_interface
[ 10.222015] hub 1-0:1.0: usb_probe_interface - got id
[ 10.222045] hub 1-0:1.0: USB hub found
[ 10.222167] hub 1-0:1.0: 1 port detected
[ 10.222198] hub 1-0:1.0: standalone hub
[ 10.222198] hub 1-0:1.0: individual port power switching
[ 10.222229] hub 1-0:1.0: no over-current protection
[ 10.222229] hub 1-0:1.0: power on to power good time: 10ms
[ 10.222259] hub 1-0:1.0: local power source is good
[ 10.222290] hub 1-0:1.0: enabling power on all ports
[ 10.225341] /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '001'
[ 10.225708] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 10.225769] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 10.225830] usb usb1: Product: MUSB HDRC host driver
[ 10.225860] usb usb1: Manufacturer: Linux 2.6.28.10-power47 musb-hcd
[ 10.225891] usb usb1: SerialNumber: musb_hdrc
[ 10.309967] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[ 10.318664] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[ 10.387084] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[ 11.013061] NET: Registered protocol family 10
[ 11.013885] lo: Disabled Privacy Extensions
[ 11.014434] ADDRCONF(NETDEV_UP): phonet0: link is not ready
[ 12.319732] hub 1-0:1.0: hub_suspend
[ 12.319763] usb usb1: bus auto-suspend
twl4030_rtc as rtc0
[ 5.985076] twl4030_rtc twl4030_rtc: Power up reset detected.
[ 5.988403] twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
[ 5.993743] lp5523 2-0032: LP5523 Programmable led chip found
[ 5.994110] Linux video capture interface: v2.00
[ 6.082214] I2C driver for Si4713 FM Radio Transmitter
[ 6.396911] isp_mod: disagrees about version of symbol
[ 12.562469] Adding 786424k swap on /dev/mmcblk0p3. Priority:-1 extents:1 across:786424k
[ 12.765136] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use)
[ 15.854736] EXT3 FS on mmcblk0p2, internal journal
[ 15.854797] EXT3-fs: recovery complete.
[ 15.860900] EXT3-fs: mounted filesystem with writeback data mode.
[ 15.894195] kjournald starting. Commit interval 1 seconds
[ 17.252777] McSAAB: ACWAKE DOWN
[ 17.252807] McSAAB: ACWAKE UP
[ 17.252868] McSAAB: WAKELINES TEST OK
[ 17.253173] ADDRCONF(NETDEV_CHANGE): phonet0: link becomes ready
[ 17.370178] Bluetooth: L2CAP ver 2.13
[ 17.370208] Bluetooth: L2CAP socket layer initialized
[ 17.459289] Bluetooth: SCO (Voice Link) ver 0.6
[ 17.459320] Bluetooth: SCO socket layer initialized
[ 17.507995] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
[ 17.976257] Bluetooth: RFCOMM socket layer initialized
[ 17.976318] Bluetooth: RFCOMM TTY layer initialized
[ 17.976348] Bluetooth: RFCOMM ver 1.11
[ 21.939178] misc iphb: Module registered in 2.6.28.10-power47, built May 3 2011 20:42:30
[ 25.045288] slide (GPIO 71) is now open
[ 30.994293] pvr: osso_startup_wi: cleaning up 97 unfreed resources
[ 46.207611] cfg80211: Regulatory domain changed to country: EU
[ 46.207641] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 46.207641] (2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 46.207641] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 46.207672] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 46.207672] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 46.207672] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 46.207702] (5490000 KHz - 5710000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 47.537567] wl12xx spi4.0: firmware: requesting wl1251-fw.bin
[ 48.856964] SCSI subsystem initialized
[ 48.990997] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[ 49.006195] wl1251: firmware booted (Rev 4.0.4.3.7)
[ 49.232879] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 49.490997] Driver 'sd' needs updating - please use bus_type methods
[ 50.107849] wl1251: down
[ 52.115539] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[ 52.131164] wl1251: firmware booted (Rev 4.0.4.3.7)
[ 52.350097] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 53.225006] wlan0: authenticate with AP 00:03:7f:fe:00:00
[ 53.227600] wlan0: authenticated
[ 53.227630] wlan0: associate with AP 00:03:7f:fe:00:00
[ 53.246246] wlan0: RX AssocResp from 00:03:7f:fe:00:00 (capab=0x411 status=0 aid=2)
[ 53.246276] wlan0: associated
[ 53.303283] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 63.966949] wlan0: no IPv6 routers present

Re: Only boots up in RD Mode
 

I can't help you with that, maybe you could find someone who knows whats the problem is in this thread:
http://talk.maemo.org/showthread.php?t=73315

Re: Only boots up in RD Mode
 

I installed nitdroid and it still shuts down when booting!

Red led starts to blink and device shuts down. If I plug the charger while booting nitdroid, the system starts up fine but battery icon shows empty and tells me to connect charger...

It's weird that when charger (or usb) is plugged in, the device "forgets" about low battery (although battery is full).

Re: Only boots up in RD Mode
 

It's really strange, but i can only assume, that Nitroid got own means of "decision making", working much different than bme.

You can ask about it in Nitroid thread. Apparently, it got nothing to do with getbootstate (in Nitroid)

Re: Only boots up in RD Mode
 

I would suppose the only moment getbootstate is relevant for NITDroid is the part right before NITDroid is actually loaded (i.e. the part where you boot into multiboot/bootmenu and switch OSs). Although, multiboot has its own /sbin/preinit file, as well as a /sbin/preinit-real file, in its package, so idk what that does - it might just ignore getbootstate until after multiboot menu is skipped.

At any rate, since Android has completely seperate battery monitoring internals, there's no doubt the actual battery problem will manifest in both OSs seperately and will need seperate fixes.

I came on here, though, to say something odd that I found - pali's replacement getbootstate randomly started showing the correct value - "USER" - I just noticed today, but I haven't looked for the last few days when my device was rebooting.

I'd say that's even more evidence that pali's getbootstate works correctly, although the odd "SHUTDOWN" state 'bug' from earlier may still have to do with it.

Re: Only boots up in RD Mode
 

If nitdroid has completely different monitoring system, i guess that the battery status chip is really damaged.
Correct me if I'm wrong, but even if I mod my n900 to use different batteries, nitdroid won't boot because it would also give "low battery" warning. If this is the case I think I will have to stay using maemo or look for a possible/similar solution with nitdroids boot state....

Mentalist: Just to know, have you tried to use Estel's getbootstate?

Re: Only boots up in RD Mode
 

I would try to find someone who can help with the latter - kinda how Estel modified Pali's getbootstate to make it always return the right boot state.

No, I haven't as of yet. No need for me personally, since all Estel's mod did was make it report the "USER" state all the time. I was going to test it to confirm his mod still worked on a normally functioning device, but I haven't had the time to do so.

Re: Only boots up in RD Mode
 

Also, as jvollmann already managed to boot device in USER state with my ugly hack, testing it on working device is quite pointless, as we already know it works. I would go for Mentalist suggestion, to ask someone used to Nitroid (nitroid thread?), is similar ugly hack can be done to some nitroid script.

Re: Only boots up in RD Mode
 

I thought I remembered you or someone else being interested in seeing if I got it working on my device - may have been before jvollmann confirmed it worked for him though...

Yep, as a totally unbiased third party I agree with you agreeing with me. :)

I'd actually suggest going to the NITDroid forums and seeing what you can get over there from the NITDroid devs in terms of help. That's who'll know the NITDroid boot-up code the best.

Re: Only boots up in RD Mode
 

After reading through the massive amount of work done here by everyone regarding this problem i think i better stick my oar in and SUGGEST you check the fuze in the charging circuit and also for any dry joints on the usb port ??.

It does sound consistent given all the circumstances and i got the clue from the post that said Nokia flashed using the data pads under the battery.

Please this is only a suggestion do not take it i am correct here in any way or form.

Re: Only boots up in RD Mode
 

Hello All,

I have a similar problem, I have successfully flashed my N900 (booth rootfs and eMMC). But it does not boot up in either normal mode or the R&D mode. I have read this tread but I think my problem is different since my device never boots up in any of the modes, It just hangs on to the NOKIA logo then goes blank.

Please help... I have been trying different flashing sequences and have even cleaned up the device with contacts cleaner but all in vain.

Regards,

Re: Only boots up in RD Mode
 

Too few details. How Your device came to this state? Have You tried flashing framebuffer kernel to check on which point it crashes?

Without more specific data, we're unable to help.

/Estel

Re: Only boots up in RD Mode
 

Hey, Thanks for the response..

I purchased this phone from Amsterdam and after some time (2 yrs) came back to Mumbai, India. I used the phone with vodafone n/w for few days, then all of a sudden my phone came to an halt.. it starts to boot using u-boot and after a few seconds waited for some default os image then it wud reboot, sometimes (after i left it off for hours) it wud boot till setting up the regional settings like language/time etc.. then reboot. I rem using internet (in Mumbai) on my phone a day before. I had never used u-boot to boot any other os on my phone but it was lying there (as i intended to use it with Nitdroid). u-boot had been there on my N900 since more than a month without giving me any issues.

Anyways I feel it may be coz of:
-Internet usage (somehow)
-u boot
-some change/fluctuation in power input (while charging), due to change in geography

Then I flashed my phone, it removed u-booot, but it wud start booting and then shut down after waiting at the NOKIA logo for about 30 seconds.

then I gave it to the nokia center, they said that the device is not able to take the s/w update.. And later on after some time they just said that the device looks like to be liquid damaged and they won’t do anything to fix it. But I don’t think it was liq damaged ever.. I even opened it up recently.. But cud not see any calcium formation on the mother board..rather the board looked new!

that’s my story, I have never tried flashing using framebuffer kernel, what does it do ? And meanwhile i will find out how to do it as well.

Re: Only boots up in RD Mode
 

If it had to be downloaded from:

http://maemo.org/packages/source/vie...-framebuffer1/

then I guess it has been removed from the above location, where else can I find it :(

Re: Only boots up in RD Mode
 

Hey... I am not able to find the framebuffer kernel, can any body help?

Thanks

Re: Only boots up in RD Mode
 

It's very weird that neither normal or R&D mode lets your device boot after a successful flash...
I think the best way to know what is happening to your device is flashing it with framebuffer kernel (as Estel suggested).
Keep searching for the file or try to contact Mohammad Abu-Garbeyyeh who is the maintainer of the package.

Good luck!

Re: Only boots up in RD Mode
 

@rocky18tid
you may be interested in using this:
http://wiki.meego.com/ARM/N900/Using_Rescue_Initrd
AIUI, it alllow You to enter mass storage mode (for whole rootfs and optfs)/USB networking etc, without backupmenu installed. This allow You to use plain kp49 and fbcon modprobed early in preinit, to easily get framebuffer output.

Of course, this apply only, if You're able to get into recovery initrd at all, cause we still doesn't know on which part Your booting process fails. It can also be broken NOLO, which would require cold flash.

Re: Only boots up in RD Mode
 

Hi Estell,

I got 'kernel-framebuffer-flasher_2.6.28-20101501+0m5-framebuffer1_armel.deb' the framebuffer kernel today morning, thanks to Jvollmann. I will try the intrd method later on (it looks rocket science to me :-( )

Jvollmann,
But since the above is a .deb file, I have to use a ubuntu machine to flash it to my N900. Can I directly flash a .deb file into my device or do I need to depacakge it to find the .bin file? I do not see any .bin like files when I depackage it on unix. I see the below:

debian-binary
data.tar.gz
control.tar.gz


Or do I need to install it in my ubuntu machine using 'sudo dpkg -i <kernel-framebuffer-flasher............>' and then find the kernel at some location and then flash it using the maemo flasher?

Basically how will I flash a .deb file into my device...

Re: Only boots up in RD Mode
 

You're right.. I forgot that I "installed" framebuffer kernel inside maemo (because my device booted successfully in R&D mode)...
I think you should better PM Mohammad Abu-Garbeyyeh and ask him what could you do!
Sorry I couldn't help you out

Re: Only boots up in RD Mode
 

You need to unpack data.tar.gz and search there a little, for vmlinuz file - it's kernel itself. You then flash the file with flasher, setting it as kernel-only, not fiasco image.

Don't worry, it's not rocket science after all. And, you probably can't break it more than it is already ;)