Help - how to get U-boot command to boot original kernel (as now stucked at loading v44 power-kernel)?

[elric]

Somehow I accidentally upgraded to the latest power-kernel v44 (when updrading ALL in Faster App), and my N900 is now stuck at the boot-up screen (with U-boot) saying "Starting Kernel..."

Is there any command that I can give to U-boot (after interrupting the autoboot) to get it to boot the original OMAP kernel?

At the very least, is there anyway I can access the phone's memory to get back data?

[EDIT, 19 Nov 2010]
Have found solutions, which also include installing v45 of kernel-power, multiboot and even Nitdroid... see last page of this thread: http://talk.maemo.org/showthread.php?t=65411&page=9

[drdrewusaf]

I just made the same mistake and I'm stuck in the same spot...

[DrWilken]

Flash the kernel only (this example flashes the std. kernel).

http://talk.maemo.org/showpost.php?p=869375&postcount=64

[cfh11]

Have you tried this?

To boot maemo instead of meego:

Hit any key to stop the N900 from booting into meego and write this in the console:
Code:

run noloboot

And it will boot into Maemo

- from the meego uboot thread

[drdrewusaf]

@DrWilken: I was already planning to reflash, but I think OP's original intention was to avoid that.

@cfh11: The boot loader is attempting to boot the correct OS, but it stalls at "Starting kernel". So, unfortunately "run noloboot" doesn't work.


Drew

[DrWilken]

The power kernel runs: run noloboot by default I think (You need to boot with open keyboard to override).

drdrewusaf: -> I said "flash the kernel only". That doesn't overwrite anything else than the kernel... ;) If You do it like in the link I posted.

Original info here (https://wiki.maemo.org/Updating_the_tablet_firmware#Flashing_only_the_ker nel_from_a_FIASCO_image).

[gamowar]

The power kernel runs: run noloboot by default I think (You need to boot with open keyboard to override).

drdrewusaf: -> I said "flash the kernel only". That doesn't overwrite anything else than the kernel... ;) If You do it like in the link I posted.

Original info here (https://wiki.maemo.org/Updating_the_tablet_firmware#Flashing_only_the_ker nel_from_a_FIASCO_image).

Then you will reinstall all the programs for me?? (that was the true point) damn this u-boot... could not update some apps.. used apt-get update.. and this auto-installed... ****-off... it SHOULD NOT be instaled by upgrade even with extra-devel...

[fpp]

Please read the advice that's given you carefully, even if you're understandably under stress :-)

Flashing ONLY THE KERNEL as shown will NOT require that you reinstall apps or restore data. Just allow you to boot again as before.

[sophocha]

welcome to my world of yesterday!.....I had to do a fresh install after I updated to v.4.2...I had multiboot installed as well.I`m sure there is a way to recover it , but I`m not a God concerning Linux, so the easy solution, format and do a backup restore.

[drdrewusaf]

drdrewusaf: -> I said "flash the kernel only". That doesn't overwrite anything else than the kernel... ;) If You do it like in the link I posted.

Original info here (https://wiki.maemo.org/Updating_the_tablet_firmware#Flashing_only_the_ker nel_from_a_FIASCO_image).

Yeah, I understood that, it was still a PITA though...guess that's what I get for having a 64-bit OS.

It came back just fine after the kernel flash. Now I'm wondering if I should even attempt to reinstall Kernel Power...


Drew

[kyllerbuzcut]

Sorry to be a bit thick here, but how do you either get xterminal to open through a uboot command, or get uboot to accept commands that will lead to running flasher. I'm just getting unknown command errors all over the place

[kyllerbuzcut]

Ok sorry- I got it to do something ( boot from mmc) BUT now I have to figure out a way to get a boot image on the mmc ( unless someone can kindly explain how to get to xterm)

[gamowar]

yes.. whit this sh1tty u-boot.. how can i get update-mode with u-boot ?? if I hol the u button.. its stay in update-mode for a split-second then u-boot load.... damn man... should test it before this nearly-early-alfa boot management version..

[kyllerbuzcut]

phew. Managed to get just the basic kernel back on and it loads fine.
If anyone else ends up here looking for an answer, you need to get flasher on your pc and download PR1.3 image into the same directory where flasher is then run a command prompt, go to flasher directory and type:

flasher-3.5 -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R

That will flash the boot kernel only, allowing you to keep all settings etc and only the boot returns to basic.

[kyllerbuzcut]

PS- gameowar- Make sure your battery has some power in it or it won't go into update mode.

Oops just realised I forgot to mention that you need to plug your phone into the PC, holding the U button before you run that flasher command



EDIT_ Just tried rebooting again and it will let me load nitdroid without having to do anything extra, so it's just the power kernel that needs sorting out on multiboot. That's no biggie, as I only installed it recently and hadn't even played around with it yet except to experiment what it was like at a setting of MAX: 805 instead of 600. It DID seem a nicer experience though, so I will try again soon I am sure.

[gamowar]

PS- gameowar- Make sure your battery has some power in it or it won't go into update mode.

Oops just realised I forgot to mention that you need to plug your phone into the PC, holding the U button before you run that flasher command



EDIT_ Just tried rebooting again and it will let me load nitdroid without having to do anything extra, so it's just the power kernel that needs sorting out on multiboot. That's no biggie, as I only installed it recently and hadn't even played around with it yet except to experiment what it was like at a setting of MAX: 805 instead of 600. It DID seem a nicer experience though, so I will try again soon I am sure.

with u-boot or multiboot (to be able to boot nitdroid) ?
And how do i know if its charging? i connect the charger and bang.. u-boot loads ¬¬ damn annoying thing...

[RobbieThe1st]

Look, guys. You generally -never- have to press U!

All you have to do is:
With your n900 OFF and unplugged, run the flasher command.
With the flasher "waiting", plug your n900 into USB. It will automatically boot, then flash. NO U KEY NEEDED.

[craftyguy]

I think Titan did this on purpose ;)

[vertyogo]

как мне удалить u-boot? flasher не видит n900, при старте грузится u-boot пишет starting kernel и все, желательно прошить только ядро на стандартное

[kyllerbuzcut]

with u-boot or multiboot (to be able to boot nitdroid) ?
And how do i know if its charging? i connect the charger and bang.. u-boot loads ¬¬ damn annoying thing...

Flashing the standard kernel gets rid of uboot, so it's just ultiboot that shows up. Just take the battery out, then back in, then plug charger in and wait. It might start the uboot thing but with no backlight but will eventually charge. It should let you do the whole connect to pc thing after that

[vertyogo]

How do I remove u-boot? flasher does not see the n900, at startup to boot u-boot wrote starting kernel and all, it is advisable to flash the kernel to the standard

[kyllerbuzcut]

The n900 will only go into update mode if the battery is sufficiently full. IT worked for me by charging it for a bit then, making sure it was off, holding the u key while plugging in the pc connector

[vertyogo]

battery is full all the way, but the flasher wrote expectation and from the wire n900 turn and run u-boot on the new

[vertyogo]

USB device found found at bus 001, device address 009.
Error claiming USB interface: Operation not permitted

[vertyogo]

USB device found found at bus 001, device address 009.
Error claiming USB interface: Operation not permitted

[Stskeeps]

Guys, you do know that it's not for fun that on http://wiki.meego.com/ARM/N900/Install/Dual_Boot we write exactly this:

WARNING: This guide is experimental and everything you do with this guide is at your own responsibility and risk

WARNING: DO NOT RELY ON WALL CHARGER, ONLY USB CHARGING FOR 1.1 IMAGES, see meego bug #2260

This is a simplified guide for dual-booting with u-boot on Nokia N900.

You must be using the PR1.3 kernel and nothing else. You will likely end up in a reboot loop if you don't have this otherwise. To check this, in Maemo X-Terminal, type "uname -a" and make sure you see:

Linux Nokia-N900 2.6.28-omap1 #1 PREEMPT Fri Aug 6 11:50:00 EEST 2010 armv7l unknown

and "dpkg -l | grep kernel-modules" should show 2.6.28-20103103+0m5.

If there's guides that doesn't have this warning, blame those people.

[Straycat]

Guys, you do know that it's not for fun that on http://wiki.meego.com/ARM/N900/Install/Dual_Boot we write exactly this:

WARNING: This guide is experimental and everything you do with this guide is at your own responsibility and risk

WARNING: DO NOT RELY ON WALL CHARGER, ONLY USB CHARGING FOR 1.1 IMAGES, see meego bug #2260

This is a simplified guide for dual-booting with u-boot on Nokia N900.

You must be using the PR1.3 kernel and nothing else. You will likely end up in a reboot loop if you don't have this otherwise. To check this, in Maemo X-Terminal, type "uname -a" and make sure you see:

Linux Nokia-N900 2.6.28-omap1 #1 PREEMPT Fri Aug 6 11:50:00 EEST 2010 armv7l unknown

and "dpkg -l | grep kernel-modules" should show 2.6.28-20103103+0m5.

If there's guides that doesn't have this warning, blame those people.

So to avoid problems with u-boot on the upgrade of kernel-power we have to be on stock kernel??

Did I have well understood??

Thanks in advance.

[Stskeeps]

So to avoid problems with u-boot on the upgrade of kernel-power we have to be on stock kernel??

Did I have well understood??

Thanks in advance.

Generally:

* Installation of kernel-power -after- uboot-pr13 install will wipe out uboot, as expected
* Installation of kernel-power -and then- install uboot-pr13 WILL cause a reboot loop (You're installing a kernel where the modules doesn't match).

Someone can make a uboot-kernel-power if they want. We're doing the uboot-pr13, matching the officially released PR1.3 kernel.

[vertyogo]

so how to fix it?

[Matan]

Here's a guide for people who got "starting kernel" heng with power44.

http://my.svgalib.org/770/n900/u-boot/u-boot-n900.zip

1 - Expand attached archived on SD (must be on third Fat partition)
2 - Start N900 and enter on u-boot interactive console (by booting with open keyboard and pressing any key).
3 - Type mmc init and press enter
4 - Type run loadbootscript and press enter
5 - Type run bootscript and press enter

This should run maemo with stock PR1.3 kernel (included in the zip file).

After booting I suggest downgrading to power43 kernel with the command (as root):

apt-get install kernel-power=2.6.28-maemo43 kernel-power-modules=2.6.28-maemo43 kernel-power-flasher=2.6.28-maemo43

And I request that people will tell me about having this problem, including the HW revision of their device.

[Kenny1001]

Look, guys. You generally -never- have to press U!

All you have to do is:
With your n900 OFF and unplugged, run the flasher command.
With the flasher "waiting", plug your n900 into USB. It will automatically boot, then flash. NO U KEY NEEDED.
doens't work here.
actually nothing works...
for me the command
flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f -R also doesnt work.
I don't want to nag on dev to be clear.

[Matan]

Generally:

* Installation of kernel-power -and then- install uboot-pr13 WILL cause a reboot loop (You're installing a kernel where the modules doesn't match).


This should not really be a problem. kernel-power does not remove the modules of the stock kernel, and it uses a different uname, so its modules are in a different directory, not overwriting stock modules.

[009N]

okay I've exhausted all combinations:

Command: flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R

(Windows 7, cmd with administrator previlege)

#1
Battery out => battery back in => slide open keyboard => press "U" => start flasher on PC => plug n900 via usb => greetings, "starting kernel"

#2
Battery out => battery back in => keyboard not slide open => start flasher on PC => plug n900 via usb => greetings, "starting kernel"

#3
Battery out => battery back in => slide open keyboard => press "U" => plug n900 via usb => start flasher on PC => greetings, "starting kernel"

#4
Battery out => battery back in => keyboard not slide open => plug n900 via usb => start flasher on PC => greetings, "starting kernel"


so uboot loads no matter how.
as some hinted above perhaps it has to do with the battery and use PC usb to charge instead of the wall charger. hmm maybe. this is the last method I've seen so far. so let's see what happens when the battery is fully charged via PC USB (with no high hope though ... :-x )

[vertyogo]

ERROR: can't get kernel image!

[vertyogo]

"so let's see what happens when the battery is fully charged via PC USB (with no high hope though ... :-x )"

nothing

[009N]

Here's a guide for people who got "starting kernel" heng with power44.

http://my.svgalib.org/770/n900/u-boot/u-boot-n900.zip
....

Now trying...
Matan, should the microsd be fat16 or fat32 and with or without boot flag? Thanks.

Also should the device be plugged into PC USB or charger or nothing?

[vertyogo]

n900 and should work without batteries, just connected to the charge? works for me .. actually it's the only plus

[009N]

okay here is my initial result.

microsd as mmc, fat 16@3rd partition, matan's stuff@3rd partition

open the keyboard

plug in the charger

device power up itself

press some key to intercept booting to get the prompt

Here is what I saw. It's dam painful to stare at those tiny prints, and without backlight ....
MAP3 RX-51 # mmc init
mmc1 is available

MAP3 RX-51 # run loadbootscript
reading boot.scr

133 bytes read


MAP3 RX-51 # run bootscript
Running bootscript from mmc ...
Executing script at 82000000
mmc1 is available
Loading uImage

1746752 bytes read
## Booting kernel from legacy Image at 82000000
Image name : Kernel PR1.3
Image type : ARM Linux Kernel Image (uncompressed)
Data size : 1746688 bytes = 1.7 MiB
Load address : 80008000
Entry point : 80008000
Verifying checksum : ok
Loading kernel image : ok

Image existing stage at 0x80000100

Starting kernel ...


It's the same story. Still stuck at uboot. So what's next? :)

[mankir]

Followed this guide with no problems: http://talk.maemo.org/showpost.php?p=869907&postcount=21
Also reinstalled uboot-pr13, as i got i kernel-panic message when i tried to boot without run noloboot command, but multiboot is working fine!

[Matan]

Now trying...
Matan, should the microsd be fat16 or fat32 and with or without boot flag? Thanks.

Also should the device be plugged into PC USB or charger or nothing?

The files should be on a fat partition that is the third partition /dev/sdb3 in Linux if in usb SD card reader. This is how an SD prepared for meego boot is partitioned. You can use another partition, but then you need to run the commands manually.

It is better that the device is not plugged.

[009N]

And I request that people will tell me about having this problem, including the HW revision of their device.

Just posted the output in my last post.
Where to look for the HW revision?

[009N]

Turned off the device. Found the label under the battery.
As for the 4-digit code, I only see a big 0434 between CE and the ! in circle. Is this what you want to see?

PS I can't boot the device without the charger as the device doesn't wake up on battery alone.
My microsd is a SanDisk 4GB Class2. I made three fat partitions, the 3rd being fat16 with boot flag all done by fdisk on another linux box.

[pak deenz]

is there no easy way to do it...?
my brain is going to blown away...

[moreli]

The files should be on a fat partition that is the third partition /dev/sdb3 in Linux if in usb SD card reader. This is how an SD prepared for meego boot is partitioned. You can use another partition, but then you need to run the commands manually.

It is better that the device is not plugged.

If I use another partition, can you please provide the manual commands?

[009N]

Thanks to another member's tip I got the backlight back (hit some key when uboot loads, enter 'reset'). Now I see the whole output and the correction is in this post (http://talk.maemo.org/showthread.php?p=870315#post870315).

[009N]

If I use another partition, can you please provide the manual commands?

I am also curious about this because I see "mmcboot" in the short list of commands upon booting in uboot.
Issuing mmcboot gives this:
Booting from mmc ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
So would it be possible for someone to create a bootable image so that we can boot off SD and then find ways to repair the system?

[gamowar]

Here's a guide for people who got "starting kernel" heng with power44.

http://my.svgalib.org/770/n900/u-boot/u-boot-n900.zip

1 - Expand attached archived on SD (must be on third Fat partition)
2 - Start N900 and enter on u-boot interactive console (by booting with open keyboard and pressing any key).
3 - Type mmc init and press enter
4 - Type run loadbootscript and press enter
5 - Type run bootscript and press enter

This should run maemo with stock PR1.3 kernel (included in the zip file).

After booting I suggest downgrading to power43 kernel with the command (as root):

apt-get install kernel-power=2.6.28-maemo43 kernel-power-modules=2.6.28-maemo43 kernel-power-flasher=2.6.28-maemo43

And I request that people will tell me about having this problem, including the HW revision of their device.

Damn.. I almost booted this way.. but battery hanged on... it dont charge because u-boot... not pluged int hte wall or the usb pc... don charge... its charges for 2 min... the u-boot loads then stops chagengin.. both ways... man... work more on u-boot before launches and please.. put that if ist not the original kernel it cant be installed...

[gamowar]

Damn.. I almost booted this way.. but battery hanged on... it dont charge because u-boot... not pluged int hte wall or the usb pc... don charge... its charges for 2 min... the u-boot loads then stops chagengin.. both ways... man... work more on u-boot before launches and please.. put that if ist not the original kernel it cant be installed...

Nah... did that...
init mmc
--> mmc available
run loadbootscript
-->boot.scr loaded
run bootscript
--> ...
loading bla bla bla...
check 1 ok
check 2 ok
starting kernel....

>> freeze <<

One day without cellphone.. only because i wanted to update some conversations plugins.. Man.. realy pissd-off

[kureyon]

for me the command
flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f -R also doesnt work.Saying it "doesnt work" doesn't help. Posting any error messages, any observations is of more help.

[jurop88]

okay I've exhausted all combinations:

Command: flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R
...
so uboot loads no matter how.


battery out -> start flasher -> plug usb -> battery in?

[gamowar]

here is the error: RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin

should be the last(newer) one... and not emmc (correct-me if i'm wrong).

[009N]

here is the error: RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin

should be the last(newer) one... and not emmc (correct-me if i'm wrong).

This is the emmc image (= rootfs). Don't mix it up with the kernel, or the device may really got bricked. :eek:

[turbowei]

So if "starting kernel" message got stuck, n900 will -NOT- be charged?

I am having the same problem as being described here.

Is reflashing the stock kernel gonna help?

[ajack]

Auto-update just updated power-kernel to power45, nothing broken so far... BlessN900 still works...

[009N]

So if "starting kernel" message got stuck, n900 will -NOT- be charged?

I am having the same problem as being described here.

Is reflashing the stock kernel gonna help?

In principle, yes, reflashing will solve the stuck-at-uboot problem. But now quite a few of us (including me) can't even get into the flashing mode. You should try anyway. Maybe you are the lucky one. ;)

[gamowar]

So if "starting kernel" message got stuck, n900 will -NOT- be charged?

I am having the same problem as being described here.

Is reflashing the stock kernel gonna help?

here is the problem that I have:

I want to use flahser. to flash the kernel only, BUT it will only get in the update-mode (by pressing "u" key [or not necessarely, like some said]) it MUST have enought battery (I think, at least half charged).
Well it don't have... If i try to chage the battery with n900 with usb cable at pc ou with charger.. it dont charges... Its start to chage then when it have enought to boot, it boots.. with u-boot then, while with u-boot on, stops chagin, then turns off and the process starts again...

I think I will put meego on my micro-sd, boot meego.. chage battery then flash bios, then boot maemo, uninstall u-boot, format micro-sd again to get my nitDroid back...

[vertyogo]

"But now quite a few of us (including me) can't even get into the flashing mode"

and me (

[jotoco]

"But now quite a few of us (including me) can't even get into the flashing mode"

and me (

and me.

The thing is that I don't have a microSD NOR do I have a method to charge the battery handy...

I'm pretty much out of luck. I will probably have to buy an external charger or something...

I will NEVER EVER install ANY Titan Kernel again, I don't need overclock and IPv6 or any of that ****

[babysugar]

Hi,
Someone get something ?
I have same problem.

[cfh11]

http://wiki.maemo.org/Updating_the_firmware

[gamowar]

http://wiki.maemo.org/Updating_the_firmware

Dont work... Like I said in another thread.. This **** u-boot should uninstall the kernelpower (or other, by reinstalling the default one) before its self-install.... damn..

[turbowei]

and me.

The thing is that I don't have a microSD NOR do I have a method to charge the battery handy...

I'm pretty much out of luck. I will probably have to buy an external charger or something...

I will NEVER EVER install ANY Titan Kernel again, I don't need overclock and IPv6 or any of that ****

I will not install any kernel update without checking the forum first. Damn, and I just got nitdroid installed, now I have to do those stuff over again. :(

[gamowar]

I will not install any kernel update without checking the forum first. Damn, and I just got nitdroid installed, now I have to do those stuff over again. :(

1st - if it do **** when intalled with other kernel, why it dont put default kernel before?
2nd - why it was moved from testing to extra when we cannot charge with it?
3rd - was not your fault... some app should already be of extra to normal... but they r not... and then they put this thing there.. like i said.. is not even pre-alpha version yet!! Yes im pissed.. 3rd day without phone/alarm cloc.... PLEASE take it off extra-devels before mora damage! I was unluck cos I updated with only 35% battery... esle.. aready flashed.. and full, if necessary..

[ybtang]

I have a big problem here.
I follow the step give to flash "kernel",but the result is:

"C:\Program Files|maemo\flasher-3.5>flasher-3.5 -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f –R.
flasher v2.5.2 (sep 24 2009)

SW version in image: RX-51_2009SE_20.2010.36-2_PR_MR0
Image 'kernel', size 1705 kB
Version 2.6.28-20103103+0m5
Image 'rootfs', size 185728 kB
Version RX-51_2009SE_20.2010.36-2_PR_MR0
FIASCO subimage data length mismatch"

Can some one please......... help me.

[doonit]

Is anyone finding that they can charge the battery using usb? Or wall charger?
I've had mine connected wiht usb for a couple of hours now. It cycles through u-boot and shows orange charge light periodically but I have no idea if it is in fact charging

[kureyon]

I have a big problem here.
I follow the step give to flash "kernel",but the result is:
...
FIASCO subimage data length mismatch"
Maybe your download is corrupted/incomplete?

The filesize is 200174197 bytes and the md5 checksum (http://www.pc-tools.net/win32/md5sums/) is

b9f8690318a3be61767826d15b8c1784

[titan]

1st - if it do **** when intalled with other kernel, why it dont put default kernel before?
2nd - why it was moved from testing to extra when we cannot charge with it?
3rd - was not your fault... some app should already be of extra to normal... but they r not... and then they put this thing there.. like i said.. is not even pre-alpha version yet!! Yes im pissed.. 3rd day without phone/alarm cloc.... PLEASE take it off extra-devels before mora damage! I was unluck cos I updated with only 35% battery... esle.. aready flashed.. and full, if necessary..

1. noobs should not install software for power users. people should read and understand the warnings
2. the kernel-power versions in extras (v37) and extras-testing (v42) are stable
3. extras-devel is only for developers. if you install software from there you risk damaging your phone and data

uboot works on my device. That's why uploaded the new experimental kernel.
Only this way we were able to find out that it breaks some devices.
Matan and others do a great job in helping to get those broken devices back to a stable kernel.

[009N]

I think it was never titan's intention to make our devices unbootable. The incidence is apparently unexpected, though it seems to be the first time to have situations like this.
I understand uboot is of much interest to devs and ppl who love tinkering with kernels and bootloaders. But as a non-power user, I am afraid I am far from being happy with it. Long before adopting the n900, I was using a zaurus loading an distro which also changed its bootloader to uboot, and then many users ran into trouble as that uboot was too difficult tame with and the ultimate solution is to wipe out everything and do a clean flash. Since then I have tried to stay away from it whenever there is a better (easier) alternative, like kexec.
My impression is that this incidence has more to do with uboot rather than the kernel itself. Or maybe I am mistaken.
Back to this, titan and matan, is there any more remedy work in progress? Yesterday matan offered a kernel which was supposed to be able to boot up the device, however it didn't work as booting still ended up in the forever "starting kernel".
I did enjoy my n900 overclocking. I would still use this kernel if I manage to get it booting again, yet I will do so only if it is just buggy but not unbootable. As regular users we do need some emergency plan when the worst scenario happens.
Now it's no use to point fingers and accuse and bash anyone and hurt our feelings. The most urgent issue is to fix booting.

[doonit]

OK. It really was the battery level that prevented me from being able to reflash. Gave my battery to a freind with a 5800 and he charged it up full and after that flashing wasn't a problem at all. Kept all my data but gotta start installing all those apps again...

[Rach82]

OK. It really was the battery level that prevented me from being able to reflash. Gave my battery to a freind with a 5800 and he charged it up full and after that flashing wasn't a problem at all. Kept all my data but gotta start installing all those apps again...

Same here..:)

[Larswad]

@doonit: Really happy to hear that you're out of the woods. Now I'm curious if this the same reason that everyone else here are unable to reflash. You should spread the word doonit!
It's been said once somewhere that this COULD be the reason, but now we know, don't we? The flasher3-5 wiki page should be updated to say that good battery level is absolutely crucial to be able to do that flashing method.

[Rach82]

The N900 battery is the same as 5800/ 5230/ X6.
Find someone who has a fully charged one and try to flash the kernel again.

[doonit]

@doonit: Really happy to hear that you're out of the woods. Now I'm curious if this the same reason that everyone else here are unable to reflash. You should spread the word doonit!
It's been said once somewhere that this COULD be the reason, but now we know, don't we? The flasher3-5 wiki page should be updated to say that good battery level is absolutely crucial to be able to do that flashing method.

Yes I agree. The thing is that if you don't know then its hard to stop the rising panic.
I wish there was a quick method to hard reset the phone like the 'Green key + hash + 3 + power on' finger gymnastics method from old Symbian S60 phones. That got me out of a lot of problems.

[geneven]

The N900 battery is the same as 5800/ 5230/ X6.
Find someone who has a fully charged one and try to flash the kernel again.

Yet another reason it's good to use an external charger and have some cheap batteries on hand. Total investment: about $20.

[009N]

For those still in trouble:
I have just bought a new spare battery which holds almost full charge already.

THE USUAL FLASH MODE AND REFLASHING JUST WORK.
THE CURE IS VERY SIMPLE: GO GET A FULLY CHARGED BATTERY AND THEN DO THE FLASHING.

I'm not quite sure yet whether uboot is gone witht the flashing, but anyhow the n900 wakes up from coma.

IMHO three things are involved in this non-booting issue:
1) New version of kernel-power (v44): some blame the problem on the kernel. I beg to differ. According to those who flash successfully things are just fine.
2) Uboot: is it really usable at this stage? It's open to unlimited ways of configuration. What works and what doen't, I don't know. So next time if I am about to upgrade the kernel I will definitely check to see if the bootloader is well-behaved.
3) The flashing process: the most critical part is not whether you press "U" or how to plug in the USB port, BUT the battery level at the time of flashing.

I hope the troubled can try out the solution and hope that works for you.

I still think this is not a problem of the kernel but the implementation of uboot in this instance. Yet I would like to express my gratitude to titan and matan for their hard work which just aim at making our n900 experience better. :)

[geneven]

Just for the record, everything works great for me, including uboot, which I just used to restore with. I'm using the latest power kernel, basically latest everything.

[gabby131]

Just for the record, everything works great for me, including uboot, which I just used to restore with. I'm using the latest power kernel, basically latest everything.

awesome!!! Me as well,, and hen usb host mode works. Unfortunately on camera and audio, which is no big deal. :)

[kpihus]

Hi,

I had same problem after upgrade to v44 kernel. Could not reflash, because of empty battery. I saw uboot screen with tux, but it did not go to flashing.

I to took out battery, and charged it with external charger. At the beginning, voltage was 3,45V so totally empty. After charging, voltage was 4.05V so almost fully charged.

But now, device does not show any picture at all, totally blank. When i plug in USB calble, yellow led flashes for a split of second, but device remains blank. And also power button does not do anything.

Any ideas ?

[doonit]

Hi,

I had same problem after upgrade to v44 kernel. Could not reflash, because of empty battery. I saw uboot screen with tux, but it did not go to flashing.

I to took out battery, and charged it with external charger. At the beginning, voltage was 3,45V so totally empty. After charging, voltage was 4.05V so almost fully charged.

But now, device does not show any picture at all, totally blank. When i plug in USB calble, yellow led flashes for a split of second, but device remains blank. And also power button does not do anything.

Any ideas ?

Make sure that it's not just that the backlight is no longer coming on...that caught me for a while too. If it is the problem then
1) remove/replace battery
2) Open keyboard
3) connect usb and press any key when phone vibrates. I think you have about 5 seconds to do this
4) hit enter and type "reset' and hit enter again.

[kpihus]

Make sure that it's not just that the backlight is no longer coming on...that caught me for a while too. If it is the problem then
1) remove/replace battery
2) Open keyboard
3) connect usb and press any key when phone vibrates. I think you have about 5 seconds to do this
4) hit enter and type "reset' and hit enter again.

No, its not backlight issue. Phone does not vibrate and screen is actually blank.
Since battery is not 100% full, it shouldt at least start charging, but it does not. Seems that even battery charging is controlled by some software, and if this software does not run then its not charging. Correct ?

Should device come up without battery, when i just plug in USB cable ?

I will buy a new battery i try with that.

[chan_98]

Hi,

I had same problem after upgrade to v44 kernel. Could not reflash, because of empty battery. I saw uboot screen with tux, but it did not go to flashing.

I to took out battery, and charged it with external charger. At the beginning, voltage was 3,45V so totally empty. After charging, voltage was 4.05V so almost fully charged.

But now, device does not show any picture at all, totally blank. When i plug in USB calble, yellow led flashes for a split of second, but device remains blank. And also power button does not do anything.

Any ideas ?

even i am facing the same problem.. :(

[Kenny1001]

even i am facing the same problem.. :(

another one here.
https://wiki.maemo.org/Updating_the_tablet_firmware#Flashing_only_the_ker nel_from_a_FIASCO_image non of those commands did get me closer.

I get
Image 'xloader', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2601, 2602, 2603
Version 1.4.14.9+0m5
Suitable USB device not found, waiting.
in dos

[gleydsonpr]

How to do ' Expand attached archived on SD (must be on third Fat partition)' ? Do you mean copy the zip file on the memory card? On my N900 PR1.2 after upgrade the Kernel only keeps Starting Kernel and nothing happens, please help me. Thank you.

Here's a guide for people who got "starting kernel" heng with power44.

http://my.svgalib.org/770/n900/u-boot/u-boot-n900.zip

1 - Expand attached archived on SD (must be on third Fat partition)
2 - Start N900 and enter on u-boot interactive console (by booting with open keyboard and pressing any key).
3 - Type mmc init and press enter
4 - Type run loadbootscript and press enter
5 - Type run bootscript and press enter

This should run maemo with stock PR1.3 kernel (included in the zip file).

After booting I suggest downgrading to power43 kernel with the command (as root):

apt-get install kernel-power=2.6.28-maemo43 kernel-power-modules=2.6.28-maemo43 kernel-power-flasher=2.6.28-maemo43

And I request that people will tell me about having this problem, including the HW revision of their device.

[sethkha]

It is not (always?) the battery. After lots of tries, I ran the flasher command as root in ubuntu. It worked. My battery is nearly empty.


edit:
wiki :"Execute the following command (in Linux you have to be root!): " ;)

[kpihus]

My phone is also OK now. It did not power up, because external charger f****d battery pin's.

[crissison]

okay here is my initial result.

microsd as mmc, fat 16@3rd partition, matan's stuff@3rd partition

open the keyboard

plug in the charger

device power up itself

press some key to intercept booting to get the prompt

Here is what I saw. It's dam painful to stare at those tiny prints, and without backlight ....
MAP3 RX-51 # mmc init
mmc1 is available

MAP3 RX-51 # run loadbootscript
reading boot.scr

133 bytes read


MAP3 RX-51 # run bootscript
Running bootscript from mmc ...
Executing script at 82000000
mmc1 is available
Loading uImage

1746752 bytes read
## Booting kernel from legacy Image at 82000000
Image name : Kernel PR1.3
Image type : ARM Linux Kernel Image (uncompressed)
Data size : 1746688 bytes = 1.7 MiB
Load address : 80008000
Entry point : 80008000
Verifying checksum : ok
Loading kernel image : ok

Image existing stage at 0x80000100

Starting kernel ...


It's the same story. Still stuck at uboot. So what's next? :)


----did you fix this problem?...i also have the same problem, and i cant do anything, tried the flashing thingy but im stuck back here... i need help..:confused:

[lalomartins]

stuck too. My battery is full but there's still no way to flash (it goes into u-boot). It won't boot the image from the zip file either (it hangs in the same place as normal boot). Did anyone try booting meego from mmc? I'm backing up an mmc now to try that...

edit: well, meego does boot. So I have a working OS on the phone. But I have no idea how to use that to fix my maemo :D yum doesn't seem to be around... I tried copying fiasco-flasher (with the help of dpkg-deb, tar, and scp) but that doesn't run on meego. Isn't there any way to convince the meego kernel to load the built-in rootfs?

edit 2: trying to install ubuntu now. Yeah, overkill, but I've got nothing better to do, no phone, and it sounds like fun :p if there's even a tiny chance this will let me recover my phone...

edit 3: here's a few remarks for those who think they are in this situation.


No, your battery isn't full. You may think it is, it may report full -- if flasher drops you to u-boot, then it's not “full enough”. Get a charger or a full battery.
Flashing the kernel only takes like a second. That took me a bit by surprise.
This won't reset the data, apps, etc, but it may reset the clock depending on how long you leave the phone without battery.

[elric]

I started the thread...so many posts already.

Anyway, I couldn't get the flashing (using Flasher-3.5 command with U pressed) done on my PC and also couldn't do using the mmc method... But the web is fantastic for finding solutions...

Then I read that Flasher-3.5 has some problem with Windows 7 64-bit...which is what runs my PC.

So I did these to re-flash my bricked N900...

Removed battery from my N900 and waited for 10 minutes before re-inserting battery
Started Flasher (flasher-3.5 -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R) on 32-bit XP laptop instead
Got to the waiting for device message..
Plugged in my N900 to the laptop using the USB cable, while holding down "U" (not holding down "U" did not work for me)
...And voila, N900 is flashed in less than 2 sec and no longer bricked! And all my data, settings, (even the kernel-power uninstall app) etc. were intact.


I realised I could safely do the above over and over, so I decided to *risk* installing Kernel-power again. I uninstalled V44 (using desktop app) and multiboot (using apt-get remove multiboot), then reinstalled V45 (from Faster App) and multiboot (apt-get install multiboot multiboot-kernel-maemo multiboot-kernel-power). Oddly, multiboot kept showing old boot menu with v40 of kernel-power.

So I read around and did these to re-install Kernel-power v45 and multiboot, to get back a working OC'ed multiboot N900:

Uninstalled kernel-power v45 from desktop app
Went to xterm and purged multiboot (root, then apt-get --purge remove multiboot multiboot-kernel-maemo multiboot-kernel-power)
Switched off the N900...then after a while switched back on to default kernel
Installed kernel-power v45 from Faster App
Went to xterm and installed multiboot (root then apt-get install multiboot multiboot-kernel-maemo multiboot-kernel-power)
In xterm still, did apt-get install kernel-power-bootimg kernel-power-modules
Followed by apt-get install --reinstall multiboot-kernel-power
And apt-get update
And apt-get upgrade
Then switched off and on the N900.. and voila! Mulitboot showing omap-1 & V45! Booted fine into v45 and overclocked to 900Mhz...


(* All the while, for above both sets of steps, I had WiFi connected)


Got to love the Maemo and N900 community...without you, it's only half the fun with the N900 :D


[EDIT: Forgot to mention that unlike some, I have no issue with camera, Panorama, BlessN900 and FCam in V45. All apps appear to be working fine. Sound is good too. Sync with PC Suite is good still. Just installed H.E.N. and will be trying USB hostmode once I get a USB A-A adaptor.]

[J4ZZ]

Thx alot elric, that sounds like a plan.
I was searching for this information a long time.

Do you eventually know how to get nitdroid and meego as 3rd and 4th boot options? That would be perfect for me to mess around with both at work, ehm I meant in my spare time. ;)

Greetz,

..::J4ZZ::..

[elric]

Will try to do Nitdroid soon, but won't be doing Meego. Will update this thread with the steps I take, once I've done it.


Thx alot elric, that sounds like a plan.
I was searching for this information a long time.

Do you eventually know how to get nitdroid and meego as 3rd and 4th boot options? That would be perfect for me to mess around with both at work, ehm I meant in my spare time. ;)

Greetz,

..::J4ZZ::..



[EDIT: Done: Nitdroid installed! And that was fast and painless...

Used a Transcend Class 6 4GB microSD card
Did not use the normal apt-get install nitdroid-installer route..(as I had issues with partitioning of SD card before)
Instead followed instruction from http://forum.nitdroid.com/index.php?topic=316.90
Downloaded nitdroid-installer_0.2.7_armel.deb (from http://talk.maemo.org/attachment.php?attachmentid=15618&d=1289926862) onto N900's MyDocs folder
In xterm, just typed: root
Followed by cd /hone/user/MyDocs
Then dpkg -i nitdroid-installer_0.2.7_armel.deb
Finally nitdroid, and reboot

No need to manually partition SD card or reinstall multiboot. On reboot, N900 went straight into multiboot menu that shows all 3 options for omap-1, v45 and Nitdroid.

I've got working WiFi and Market, so it looks good.

This is addictive...I just might try my luck with installing Meego...if I can read up a bit more about other's experience with u-boot....]

[ing005]

My N900 still can't boot

: (

[elric]

I assume you are using Flasher-3.5?
You've got your Flasher-3.5 started first on command prompt window, before physically connecting the N900?
You can connect physically only after you see the message that says Flasher is waiting for device. You also need to hold "U" down with the keyboard opened (when connecting USB cable) while depressing power button to turn on N900. Once u-boot does not appear to be loading, you can let go of the "U" button. Flashing should be done in 2 sec.
(Do remember Flasher somehow doesn't work with 64-bit Windows)

My N900 still can't boot

: (

[ing005]

I've already did that

but when i've tried to connect usb with holding u key

u-boot just loading everytime

also happen when i charge battery

it will boot an my battery can charge no more

[J4ZZ]

Will try to do Nitdroid soon, but won't be doing Meego. Will update this thread with the steps I take, once I've done it.






[EDIT: Done: Nitdroid installed! And that was fast and painless...

Used a Transcend Class 6 4GB microSD card
Did not use the normal apt-get install nitdroid-installer route..(as I had issues with partitioning of SD card before)
Instead followed instruction from http://forum.nitdroid.com/index.php?topic=316.90
Downloaded nitdroid-installer_0.2.7_armel.deb (from http://talk.maemo.org/attachment.php?attachmentid=15618&d=1289926862) onto N900's MyDocs folder
In xterm, just typed: root
Followed by cd /hone/user/MyDocs
Then dpkg -i nitdroid-installer_0.2.7_armel.deb
Finally nitdroid, and reboot

No need to manually partition SD card or reinstall multiboot. On reboot, N900 went straight into multiboot menu that shows all 3 options for omap-1, v45 and Nitdroid.

I've got working WiFi and Market, so it looks good.

This is addictive...I just might try my luck with installing Meego...if I can read up a bit more about other's experience with u-boot....]


Thx a lot...
Multiboot with

1.omap1
2.power45
3.nitdroid

is working fine here, too ;)

And Meego is also booting properly but from another SD card. So I guess maybe by simply moving the raw Meego image to a new partition on my other sd card (the one with nitdroid on it) could make it possible to boot it, but there won't be an multiboot entry.

we'll see

Greetz,

..::J4ZZ::..

[garrickvanburen]

After trying and failing with every combination of flashing method;
- I charged up my N900's battery with an external charger
- Ran the flasher3.5 kernel only command
- and 2 seconds later my N900 was back, like it hadn't been bricked for a week.

[ing005]

After trying and failing with every combination of flashing method;
- I charged up my N900's battery with an external charger
- Ran the flasher3.5 kernel only command
- and 2 seconds later my N900 was back, like it hadn't been bricked for a week.

good luck for you

but mine still died

[ing005]

Anyone still have this problem ?

[starpalace]

not tried yet but hope that it should work.

[starpalace]

1; fully charge ur n900 battery.
2; take it out frm the phone.
3; connect ur phone via usb.
4; keep holding the u key and put the battery in it.
5; the flashing mode will be active.
6; flash ur phone via maemo flasher.

and its done now
it wil work 100%...