| dotcomma | hey,can someone help me with my n900? | 04:45 |
|---|---|---|
| dotcomma | it only boots in r&d mode | 04:45 |
| dotcomma | despite after being reflashed twice | 04:46 |
| dotcomma | booting in normal mode would end up in five dots for 10 secs then reboot | 04:47 |
| Maxdamantus | dotcomma: I suspect it's not meant to be disabled by just reflashing. You probably have to use `--disable-rd-mode`. | 07:03 |
| Maxdamantus | dotcomma: ie, run `flasher_3.5 --disable-rd-mode` and plug in the N900 while it's off. | 07:04 |
| Maxdamantus | Oh, nvm, misunderstood the problem. | 07:05 |
| Maxdamantus | So that behaviour probably means the watchdog is rebooting the device. | 07:06 |
| sixwheeledbeast | ~bootloop | 08:54 |
| infobot | extra, extra, read all about it, bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device. | 08:54 |
| sixwheeledbeast | is flashing definitely completed? | 08:55 |
| KotCzarny | ~flatbat | 08:57 |
| KotCzarny | ~flatbatt | 08:57 |
| KotCzarny | ~flatbatrecover | 08:58 |
| infobot | Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber shut off -> start over again with ~flatbatrecover while already searching for a new battery. CAVEAT! Only works when ~rootfs OK (no ~bootloop) | 08:58 |
| KotCzarny | also might come handy | 08:58 |
| dotcomma | sixwheeledbeast:flashing completed just fine and normally,but the phone still bootlooped | 10:19 |
| sixwheeledbeast | see above maybe flat battery? what makes you think rdmode is on? | 10:20 |
| dotcomma | about batteries,I have 3 and have all charged them via a Lumia 520 | 10:20 |
| dotcomma | I enabled rd mode after looking up threads on the forum | 10:22 |
| sixwheeledbeast | are you flashing both the emmc and the rootfs? | 10:22 |
| dotcomma | yes | 10:23 |
| dotcomma | i got the phone in that state so i guess it's a hardware problem then | 10:23 |
| KotCzarny | define 'bootloop' | 10:24 |
| KotCzarny | there are few different kinds | 10:24 |
| KotCzarny | how far does it boot? | 10:24 |
| sixwheeledbeast | maybe but I would assume there is something else | 10:24 |
| KotCzarny | no 5dots, 5dots, desktop | 10:24 |
| Maxdamantus | So just to be clear, it basically works fine as long as R&D mode is enabled? | 10:24 |
| sixwheeledbeast | especially if you get to five dots | 10:24 |
| dotcomma | 5 dots moving for 10 seconds,then froze and reboot | 10:24 |
| Maxdamantus | Seems fairly feasible to me that for whatever reason, the watchdog is triggering a reboot. | 10:25 |
| KotCzarny | once i had a 'bootloop' because because /home/user wasnt accessible | 10:25 |
| Maxdamantus | Since afaik that's normally disabled in R&D mode. | 10:25 |
| dotcomma | it works just fine minus charging and battery indicator | 10:25 |
| dotcomma | in r&d | 10:25 |
| Maxdamantus | Mm. I think one of the two watchdogs has to do with charging. | 10:26 |
| sixwheeledbeast | also if batteries are tired when the modem starts you have a lot more load. | 10:26 |
| sixwheeledbeast | ~bootreason | 10:27 |
| infobot | [bootreason] cat /proc/bootreason also see https://wiki.maemo.org/Troubleshooting_boot_issues#Reporting_reboot_issues for details | 10:27 |
| sixwheeledbeast | that would show if watchdog? | 10:27 |
| dotcomma | the phone's reporting 1 bar and 1/1mAh too which makes me think it's hardware | 10:28 |
| KotCzarny | maybe bad batteries/contacts? | 10:28 |
| dotcomma | they all work on the 520 and are all Nokia new old stock so nah | 10:29 |
| KotCzarny | battery contacts in phone? | 10:29 |
| KotCzarny | you can get battery info in terminal | 10:30 |
| sixwheeledbeast | even if they work it's load at boot that hasn't been ruled out | 10:30 |
| KotCzarny | wouldnt be half bad if you pastebin'ed it | 10:30 |
| KotCzarny | there is a possibility that charging circuit is fried too | 10:30 |
| KotCzarny | ~bc2900 | 10:32 |
| KotCzarny | ~bc2700 | 10:32 |
| KotCzarny | ~bc2700.sh | 10:32 |
| KotCzarny | hrm | 10:32 |
| KotCzarny | ~listkeys bq27 | 10:33 |
| infobot | Factoid search of 'bq27' by key (5): calibratebq27200 #DEL# ;; bq27200 ;; bq27 ;; bq27k-detail ;; bq27k-calibration. | 10:33 |
| Maxdamantus | dotcomma: might be worth showing your kernel messages (`dmesg`) after booting in R&D mode, since that's easy to obtain. | 10:34 |
| Maxdamantus | (reading /proc/bootreason would probably require modifying some init scripts to log it, or loading a rescue system on reboot) | 10:34 |
| KotCzarny | ~bq27 | 10:34 |
| infobot | rumour has it, bq27 is http://maemo.cloud-7.de/maemo5/usr/local/sbin/ bq27*, or http://maemo.cloud-7.de/maemo5/patches_n_tools/ | 10:34 |
| KotCzarny | ~bq27200 | 10:35 |
| infobot | from memory, bq27k-detail is http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2, or ~bq27 | 10:35 |
| KotCzarny | http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27200.sh | 10:35 |
| KotCzarny | infobot: #maemo bq27 is also http://wiki.maemo.org/N900_Hardware_Charge_Meter | 10:36 |
| infobot | okay, KotCzarny | 10:36 |
| KotCzarny | ~bq27 | 10:36 |
| infobot | well, bq27 is http://wiki.maemo.org/N900_Hardware_Charge_Meter | 10:36 |
| KotCzarny | darn. | 10:36 |
| KotCzarny | infobot: forget #maemo bq27 | 10:36 |
| infobot | i forgot #maemo bq27, KotCzarny | 10:36 |
| KotCzarny | infobot: bq27 is also http://wiki.maemo.org/N900_Hardware_Charge_Meter | 10:36 |
| infobot | okay, KotCzarny | 10:36 |
| KotCzarny | ~bq27 | 10:36 |
| infobot | i guess bq27 is http://maemo.cloud-7.de/maemo5/usr/local/sbin/ bq27*, or http://maemo.cloud-7.de/maemo5/patches_n_tools/, or http://wiki.maemo.org/N900_Hardware_Charge_Meter | 10:37 |
| sicelo | why not write it in full ... i think we are more like toly to search bq27200 than bq27 | 10:37 |
| sicelo | at least i wouldn't search bq27 alone | 10:37 |
| KotCzarny | feel free to fix that, i was having trouble remembering which controller model it was | 10:38 |
| KotCzarny | :) | 10:38 |
| KotCzarny | also, seems those might be compatible with any bq27x00 controller | 10:41 |
| dotcomma | monitoring with lshal -m gave me charging status=error,probably there's my issue since RD mode should still have working charging and indicator right? | 10:42 |
| KotCzarny | lshall probably uses dbus approximation | 10:42 |
| KotCzarny | bq script will inquire battery controller directly | 10:42 |
| KotCzarny | and when you switch batteries capacity is 100% wrong, because it wasnt calibrated | 10:43 |
| KotCzarny | rd mode probably just disables watchdog, it doesnt prevent charging | 10:46 |
| KotCzarny | i bet that something is wrong with battery controller in your n900 | 10:47 |
| dotcomma | https://talk.maemo.org/showpost.php?p=1181666&postcount=130 this completely fits what I have | 10:55 |
| dotcomma | probably previous owner used a dodgy charger and fried the sense circuit | 10:55 |
| KotCzarny | yup, part of the battery controller fried | 10:56 |
| dotcomma | I'll try finding a broken touch/lock code n900 around my area then probably | 10:58 |
| KotCzarny | there is a plenty with broken usb | 10:58 |
| KotCzarny | although that doesnt help if you cant solder tiny part | 10:58 |
| KotCzarny | broken lcd might be also a good one to swap | 10:59 |
| KotCzarny | because it's easiest to just swap whole display part | 10:59 |
| KotCzarny | or you can hack around and maybe you can get it to charge | 10:59 |
| dotcomma | I got this for free from a phone shop saying "what do you know it's another untested but turns out to be dead n900" | 11:00 |
| KotCzarny | seeing the guy in that thread managed to do it with restarting bmi | 11:00 |
| KotCzarny | free is always nice | 11:00 |
| KotCzarny | :) | 11:00 |
| dotcomma | voltages do go up when i check so it works for the time being I guess | 11:00 |
| KotCzarny | check that battery script i've pasted earlier | 11:01 |
| dotcomma | n900s with toast baseband/bootloop are more common than working ones somehow | 11:02 |
| dotcomma | well it's Vietnam,what did you expect | 11:02 |
| KotCzarny | that's because modem chip gets desoldered from heavy presses on keyboard | 11:03 |
| KotCzarny | if you can reflow it, it will go back to life | 11:03 |
| dotcomma | sounds like the iPhone 4 to me,lol | 11:04 |
| KotCzarny | :) | 11:04 |
| dotcomma | I just heard sad news,my local phone shop threw a N9 screen instead of a dead Lumia 800 screen on accident,whoops | 11:06 |
| KotCzarny | arent those the same? | 11:06 |
| dotcomma | the screens for the N9 are starting to get harder to find it seems | 11:06 |
| KotCzarny | i thought they only differ in software | 11:06 |
| dotcomma | technically,yes | 11:07 |
| dotcomma | the 800 have the extra display space blocked by the printed keys | 11:07 |
| dotcomma | on the glass | 11:07 |
| dotcomma | and no front camera cutout | 11:08 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!