briked N900 with strange loop boot - maemo.org

ehsantlk | # 1 | 2013-11-13, 12:42 | Report

Hello all
I got a briked N900 that was in loop boot
I flashed both emmc and OS using this article :
http://wiki.maemo.org/Updating_the_firmware
and there wasn't any problem during the procces

but still in boot loop .
I also tried zImage-fb-omap1-pr13 to see what's going on and why is geting restart but it's too fast and I didn't undrestand it very well but usually in final it's says
"rebooted in 1 second" or " starting camera demond"
and start from over

and sometime it's getting dim during this process
is anyone has idea how can I fix it?
(and also sorry for my bad english )

Last edited by ehsantlk; 2013-11-13 at 12:47.

freemangordon | # 2 | 2013-11-13, 12:49 | Report

Originally Posted by ehsantlk View Post

Hello all
I got a briked N900 that was in loop boot
I flashed both emmc and OS using this article
file:///home/strawberry/Downloads/Updating%20the%20firmware%20-%20maemo.org%20wiki.html
and it wasn't any problem in it

but still has boot loop problem .
I also tried zImage-fb-omap1-pr13 to see what's going on and why is geting restart but it's too fast and I dont undrestad it very well and usually in final it's says
"rebooted in 1 second" or " starting camera demond"

and sometime it's getting dim during this process
is anyone has idea how can I fix it?
(and also sorry for my bad english )

make sure to correctly follow the guide here http://wiki.maemo.org/Updating_the_firmware#N900

If it still doesn't boot, try to enable R&D mode:

Code:

./flasher-3.5 --enable-rd-mode
./flasher-3.5 --set-rd-flags=no-lifeguard-reset
./flasher-3.5 --set-rd-flags=no-omap-wd
./flasher-3.5 --set-rd-flags=no-ext-wd

If it still doesn't boot, post again here.

The Following User Says Thank You to freemangordon For This Useful Post:
ehsantlk

ehsantlk | # 3 | 2013-11-13, 14:04 | Report

Originally Posted by freemangordon View Post

make sure to correctly follow the guide here http://wiki.maemo.org/Updating_the_firmware#N900

If it still doesn't boot, try to enable R&D mode:

Code:

./flasher-3.5 --enable-rd-mode
./flasher-3.5 --set-rd-flags=no-lifeguard-reset
./flasher-3.5 --set-rd-flags=no-omap-wd
./flasher-3.5 --set-rd-flags=no-ext-wd

If it still doesn't boot, post again here.

thank you . but still in boot loop .
for --enable-rd-mode

I got this :
flasher v2.5.2 (Oct 21 2009)

Suitable USB device not found, waiting.
USB device found found at bus 002, device address 032.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': <no version>
The device is now in R&D mode

for other I got this:
flasher v2.5.2 (Oct 21 2009)

USB device found found at bus 002, device address 032.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': <no version>

Mitrigol | # 4 | 2013-11-13, 14:19 | Report

What did you have as a config on your phone before you bricked it? I mean, did you manually configure any special settings or something?

Did you multi boot? did you play with bootloader?

What were you doing when you bricked it?

Does it still boot but restart when you try something or does it reboot at the white dots? do you see maemo at all? ( i ask because of the message you receive about camera)

EDIT: Ok, forget the last part, i did not notice the framebuffer kernel at first.

Last edited by Mitrigol; 2013-11-13 at 14:46.

The Following User Says Thank You to Mitrigol For This Useful Post:
ehsantlk

freemangordon | # 5 | 2013-11-13, 15:08 | Report

@ehsantlk - did you follow the flashing guide on maemo wiki?

The Following User Says Thank You to freemangordon For This Useful Post:
ehsantlk

ehsantlk | # 6 | 2013-11-13, 15:19 | Report

Originally Posted by Mitrigol View Post

What did you have as a config on your phone before you bricked it? I mean, did you manually configure any special settings or something?

Did you multi boot? did you play with bootloader?

What were you doing when you bricked it?

Does it still boot but restart when you try something or does it reboot at the white dots? do you see maemo at all? ( i ask because of the message you receive about camera)

EDIT: Ok, forget the last part, i did not notice the framebuffer kernel at first.

actually I bought this and it has this problem
I ask about this problem from seller and he told me that he was taking out battery when device was connected to TV and after that it has this problem . ( I don't know if he liying )
i dont see maemo at all just rebootet in white dots
I also saw some other messegage before it getting rebootet like this:
"""""""""""""""""""""
ACT_DEAD
hello act_dead
change state : ********************
**
**
shutdown in 2 second
"""""""""""""""""""""""""""""""""""""""""""""" "

ehsantlk | # 7 | 2013-11-13, 15:24 | Report

Originally Posted by freemangordon View Post

@ehsantlk - did you follow the flashing guide on maemo wiki?

yes , I think
and I got the messages about the images flashed successfuly

freemangordon | # 8 | 2013-11-13, 16:16 | Report

how's the battery condition?

The Following User Says Thank You to freemangordon For This Useful Post:
ehsantlk

ehsantlk | # 9 | 2013-11-13, 16:24 | Report

Originally Posted by freemangordon View Post

how's the battery condition?

I usually make it fully charged with an external universal charger

I have question about "act_dead" and "hello act_dead "
these messages are normal?

freemangordon | # 10 | 2013-11-13, 16:28 | Report

ACT_DEAD means it is charging

The Following User Says Thank You to freemangordon For This Useful Post:
ehsantlk