maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   briked N900 with strange loop boot (https://talk.maemo.org/showthread.php?t=91791)

ehsantlk 2013-11-13 12:42
briked N900 with strange loop boot
 
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 )

freemangordon 2013-11-13 12:49
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by ehsantlk (Post 1385984)
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.

ehsantlk 2013-11-13 14:04
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by freemangordon (Post 1385985)
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 2013-11-13 14:19
Re: briked N900 with strange loop boot
 
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.

freemangordon 2013-11-13 15:08
Re: briked N900 with strange loop boot
 
@ehsantlk - did you follow the flashing guide on maemo wiki?

ehsantlk 2013-11-13 15:19
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by Mitrigol (Post 1386012)
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 2013-11-13 15:24
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by freemangordon (Post 1386024)
@ehsantlk - did you follow the flashing guide on maemo wiki?
yes , I think
and I got the messages about the images flashed successfuly

freemangordon 2013-11-13 16:16
Re: briked N900 with strange loop boot
 
how's the battery condition?

ehsantlk 2013-11-13 16:24
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by freemangordon (Post 1386037)
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 2013-11-13 16:28
Re: briked N900 with strange loop boot
 
ACT_DEAD means it is charging

ehsantlk 2013-11-13 16:33
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by freemangordon (Post 1386040)
ACT_DEAD means it is charging
ok. is it ok while I dont plug it into the charger?

is it important to battery has fully charged before flash the device?
or is just for to be sure

nokiabot 2013-11-13 16:35
Re: briked N900 with strange loop boot
 
Yesterday i tried hard to flash one with exact condition could not succed as m lame with terminal then fired up infinity it did the job :) i flashed rootfs only then reset after that flashed both but it stuck then flashed nolo bootloader and then the files it came to life:)

nokiabot 2013-11-13 16:44
Re: briked N900 with strange loop boot
 
@freemango now i have a n900 that shows nokia logo as soon as i put the battery and stays like that so what coud be wrong ? Is it hardware or software any help btw the usb port is ripped off and i also dont know how it happend.

nokiabot 2013-11-13 16:47
Re: briked N900 with strange loop boot
 
@ freemango instruct him in simple way to flash nolo then the file it coud do the job :)

nokiabot 2013-11-13 16:50
Re: briked N900 with strange loop boot
 
Well i found a infinity crack let me check twmorrow if it works via usb without any ufs cyclone or jaf connected.:)

freemangordon 2013-11-13 16:51
Re: briked N900 with strange loop boot
 
nolo is just fine if he can see that device enters ACT_DEAD mode

@ehsantlk - please, follow the flashing guide on maemo wiki and post the result. Flash both fiasco and EMMC

ehsantlk 2013-11-13 16:54
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by freemangordon (Post 1386053)
nolo is just fine if he can see that device enters ACT_DEAD mode

@ehsantlk - please, follow the flashing guide on maemo wiki and post the result. Flash both fiasco and EMMC
ok. but I just want to battery getting fully charged and I will do that
it's maybe take a while .

nokiabot 2013-11-13 17:02
Re: briked N900 with strange loop boot
 
Now do tell me something whats up with the n900 i currently have should i go and solder wires to a rj45 connector or check every lame connections i find for low or high voltages disconections shorts etc. Pretty low on time this week help appreciated.

ehsantlk 2013-11-13 21:07
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by freemangordon (Post 1386053)
nolo is just fine if he can see that device enters ACT_DEAD mode

@ehsantlk - please, follow the flashing guide on maemo wiki and post the result. Flash both fiasco and EMMC
ok. I fully charged the battery

""""""""""""""""""""""""""""""""""""""""""""
sudo flasher-3.5 -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f

flasher v2.5.2 (Oct 21 2009)

Image 'mmc', size 255947 kB
Version RX-51_2009SE_10.2010.13-2.VANILLA
USB device found found at bus 002, device address 006.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0
Booting device into flash mode.
Suitable USB device not found, waiting.
USB device found found at bus 002, device address 007.
Raw data transfer EP found at EP2.
Image(s) flashed successfully in 28.737 s (8906 kB/s)!
'''''''''''''''''''''''''''''''''''''''''''''''''' '''''''''''''''''''''''''''''''''''''''''''''''''' '''''''''''''''''
at this point I unplug the usb and taking out the battery for about 10 seconds

"""""""""""""""""""""""""""""""""""""""""""""""""" """""""
sudo flasher-3.5 -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin -f

flasher v2.5.2 (Oct 21 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
Image 'cmt-2nd', size 81408 bytes
Version BB5_09.36
Image 'cmt-algo', size 519808 bytes
Version BB5_09.36
Image 'cmt-mcusw', size 5826 kB
Version rx51_ICPR82_10w08
Image '2nd', size 14720 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Suitable USB device not found, waiting.
USB device found found at bus 002, device address 009.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0
Sending xloader image (14 kB)...
100% (14 of 14 kB, avg. 3625 kB/s)
Sending secondary image (106 kB)...
100% (106 of 106 kB, avg. 13359 kB/s)
Flashing bootloader... done.
Sending cmt-2nd image (79 kB)...
100% (79 of 79 kB, avg. 11357 kB/s)
Sending cmt-algo image (507 kB)...
100% (507 of 507 kB, avg. 20305 kB/s)
Sending cmt-mcusw image (5826 kB)...
100% (5826 of 5826 kB, avg. 22939 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1705 kB)...
100% (1705 of 1705 kB, avg. 13222 kB/s)
Flashing kernel... done.
Sending and flashing rootfs image (185728 kB)...
100% (185728 of 185728 kB, avg. 15946 kB/s)
Finishing flashing... done
CMT flashed successfully
"""""""""""""""""""""""""""""""""""""""""""""" """"
again I unplug the cable and remove the battery for about 10 sec
then I start the N900 phone . I got NOKIA logo and then five dots come for few second , after that screen getting dim(I still can see 5 dots )at this time yellow light blink for 2 time and then vibrate and NOKIA logo come again
I Hope you can find out what's wrong

freemangordon 2013-11-13 21:15
Re: briked N900 with strange loop boot
 
@ehsantlk:
try to flash rootfs, EMMC, rootfs

without reboot in between

EDIT:

you may want to join #maemo on freenode.net and ask for further help there if ^^^ doesn't help

joerg_rw 2013-11-13 21:26
Re: briked N900 with strange loop boot
 
ehsantlk
sounds like your battery might be defect.
OR you got a hw defect
/j

ehsantlk 2013-11-13 21:30
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by freemangordon (Post 1386097)
@ehsantlk:
try to flash rootfs, EMMC, rootfs

without reboot in between

EDIT:

you may want to join #maemo on freenode.net and ask for further help there if ^^^ doesn't help
well i flash rootsfs without problem and without restart the phone I flashed EMMC and without doing any restart i flash rootfs agin but this time :

flasher v2.5.2 (Oct 21 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
Image 'cmt-2nd', size 81408 bytes
Version BB5_09.36
Image 'cmt-algo', size 519808 bytes
Version BB5_09.36
Image 'cmt-mcusw', size 5826 kB
Version rx51_ICPR82_10w08
Image '2nd', size 14720 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
USB device found found at bus 002, device address 012.
Raw data transfer EP found at EP2.
Using flashing protocol Mk II.

the display of the phone is dim and it's show 5 dot's screen without any move in them

freemangordon 2013-11-13 21:33
Re: briked N900 with strange loop boot
 
give it some time, the first boot could take up to ~5 minutes


EDIT:

Unfortunately it seems your device has some HW problem, you flash it in the correct way :(

ehsantlk 2013-11-13 21:35
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by joerg_rw (Post 1386101)
ehsantlk
sounds like your battery might be defect.
OR you got a hw defect
/j
what is hw defect ?
how can I make sure about the battery?
can you explain

freemangordon 2013-11-13 21:37
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by ehsantlk (Post 1386106)
what is hw defect ?
how can I make sure about the battery?
can you explain
Like some chip is broken (wh defect) or your battery is too old and can't hold the charge.

Try to find another battery and try with it, BL5J is pretty common

joerg_rw 2013-11-13 21:39
Re: briked N900 with strange loop boot
 
maybe disabling watchdogs helps, for whatever reason
If neither disabled watchdogs nor new battery helps, console output is the only diagnostic path (not feasible without special hardware equipment, unless maybe you get a powerkernel with modules installed, but I don't see how to accomplish that)

[2013-11-13 22:38:30] <xes> my opinion is batt voltage too low. I can remember the same behavior with my old battery. I enabled framebuffer and the reboot cause was the voltage too low

freemangordon 2013-11-13 21:44
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by ehsantlk (Post 1386106)
what is hw defect ?
how can I make sure about the battery?
can you explain
from #maemo

23:38 <xes> my opinion is batt voltage too low. I can remember the same behavior with my old battery. I enabled framebuffer and the reboot cause was the voltage too low

ehsantlk 2013-11-13 21:59
Re: briked N900 with strange loop boot
 
well I think I should try with another battery
thank you guys . I will reply when I try it

ehsantlk 2013-11-14 22:17
Re: briked N900 with strange loop boot
 
Quote:
Originally Posted by ehsantlk (Post 1386115)
well I think I should try with another battery
thank you guys . I will reply when I try it
I found a new battery and start my N900 but unlucky I'm still in boot loop.
so is it a Hw problem?
is there anything else that I can try?
how can I debug it?


All times are GMT. The time now is 18:43.

vBulletin® Version 3.8.8