**** BEGIN LOGGING AT Mon Sep 05 02:59:59 2016 Sep 05 15:39:34 so, i got another n900 (im addicted or what). what does nonpulsing orange mean after connecting charger? Sep 05 15:39:44 (i didnt try to turn it on yet) Sep 05 15:40:06 is it flatbat case or something else? Sep 05 15:40:44 (right now i'll try to charge it for 30 minutes and see what will happen) Sep 05 15:44:00 KotCzarny: I'd say yes Sep 05 15:44:20 and/or no kernel/rootfs to boot from after a few mins Sep 05 15:44:56 still steady orange, so i guess rootfs/kernel b0rken. but battery is charging, right? Sep 05 15:45:54 why You don't swap batteries. With another working n900 :) Sep 05 15:46:52 will do, just wanted to make sure what steady orange means Sep 05 15:47:55 steady orange means that bq24150 is not getting any instructions on what to do Sep 05 15:47:59 for one reason or another Sep 05 15:48:16 so after 30(?) seconds it'll default to a slow charging mode Sep 05 15:48:20 up to a point Sep 05 15:50:29 oh. something happened Sep 05 15:50:46 turned on for a moment, showed 'nokia' logo, screen went crazy and turned off Sep 05 15:51:32 welcome to flat battery boot loop Sep 05 15:51:42 (with broken rootfs bonus) Sep 05 15:51:49 yup, apparently Sep 05 15:51:50 ~bootloop Sep 05 15:51:54 ~flatloop Sep 05 15:51:56 err Sep 05 15:52:10 it has been said that 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. Sep 05 15:52:10 whatever the spelling is, I kinda remember doc talking about that Sep 05 15:52:13 oooh Sep 05 15:52:17 rescueos should boot still Sep 05 15:52:20 lets see Sep 05 15:52:44 KotCzarny: not sure Sep 05 15:53:05 booting from usb with an empty battery has always been touchy Sep 05 15:55:11 ~flasher Sep 05 15:55:12 extra, extra, read all about it, flasher is at http://www.jedge.com/n810/flasher/maemo_flasher-3.5_2.5.2.2.tar.gz (also .exe!), or http://www.chakra-project.org/ccr/packages.php?ID=5027 or generally http://www.google.com/search?q=maemo_flasher-3.5_2.5.2.2.tar.gz. HARMattan(N9): https://aur.archlinux.org/packages/fl/flasher-harmattan/flasher-harmattan.tar.gz, or -- list of filenames/md5sums: http://pastebin.com/sYKdNJSH, or http://galif.eu/nokia/ Sep 05 16:06:02 ~flashing Sep 05 16:06:03 it has been said that maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh; or see ~flashing-cmdline, or see ~lazyflashing Sep 05 16:08:37 ok, rescueos booted with diff. battery Sep 05 16:08:45 i guess i'll just flash it Sep 05 16:10:11 Found device RX-51, hardware revision 2204 Sep 05 16:10:11 NOLO version 1.4.14 Sep 05 16:10:11 Version of 'sw-release': RX-51_2009SE_21.2011.38-1_PR_MR0 Sep 05 16:10:16 so far so good Sep 05 16:10:55 why is it erasing cmt twice? hum Sep 05 16:11:51 Erasing CMT: 98%CMT flashing failed Sep 05 16:11:51 sorry, flashing RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin (NOLO, rootfs, modem-fw) failed with errorcode 0 Sep 05 16:11:53 o.o Sep 05 16:12:12 does it mean modem is shot? Sep 05 16:12:24 not necessarily iirc Sep 05 16:12:51 i think last time it flashed on 98% cmt, it was with broken modem board Sep 05 16:12:54 it probably wont work if it failed at 98% though Sep 05 16:13:03 try again Sep 05 16:13:10 or try to use 0xFFFF Sep 05 16:13:20 huhu, Pali reads in my mind :) Sep 05 16:13:41 (hey there btw, long time no "see") Sep 05 16:13:44 i think its in bootloop now Sep 05 16:13:52 doesnt even show nokia logo Sep 05 16:14:08 1. make sure you have fully charget battery Sep 05 16:14:16 (if not use external charger, etc) Sep 05 16:14:27 2. do full reflash again Sep 05 16:14:31 does it have to be fully charged? Sep 05 16:14:48 should be Sep 05 16:15:15 or at least half, but working battery, not some old Sep 05 16:15:47 dont remember how much juice my testing spare had, will try flashing again, then will charge it if it fails Sep 05 16:15:50 so voltage does not decrease under some value Sep 05 16:16:13 pity device doesnt charge during flashing Sep 05 16:16:14 modem cannot operate if voltage is low Sep 05 16:16:14 KotCzarny: I'd just leave it alone for a few hours :) Sep 05 16:16:48 and so it can defunct when trying to flash modem part Sep 05 16:17:13 nah, i'll use my primary phone batt if it fails again, its almost full today Sep 05 16:17:39 btw, modem is own "system" and their bootloader refuse to downgrade modem firmware Sep 05 16:18:08 pali, hw revision is 2204, could it be the reason? Sep 05 16:18:22 so I can imagine that lossing or memory or damaging some data in modem memory can lead that modem refuse to flash because of that "downgrade" restriction Sep 05 16:18:28 hw revision should not be reason Sep 05 16:19:00 just use correct firmware for it (both 0xFFFF and flasher-3.5 choose correct from FIASCO binary) Sep 05 16:19:11 im using doc's script Sep 05 16:19:26 should be OK Sep 05 16:19:38 do not experiment and use fully charget battery Sep 05 16:19:44 *charged Sep 05 16:19:56 yeah, im just doing that Sep 05 16:21:28 btw, flashing cmt images is implemented in NOLO :-( so 0xFFFF is just wraper around NOLO Sep 05 16:21:38 there is no direct communication with modem Sep 05 16:21:48 same error Sep 05 16:21:49 :/ Sep 05 16:21:57 can you post output? Sep 05 16:22:16 http://pastebin.com/raw/xWG1Jw0N Sep 05 16:23:36 thats bad Sep 05 16:23:52 can i flash without modem part? Sep 05 16:24:15 can you try to preload libusb-sniff-32.so (from 0xFFFF) for flasher-3.5? Sep 05 16:24:24 and flash only cmt parts? Sep 05 16:24:44 that will print looong output (dump usb packets) Sep 05 16:25:03 shall i redirect output or its not that much? Sep 05 16:25:08 ~0xFFFF Sep 05 16:25:09 somebody said 0xffff was https://github.com/pali/0xFFFF, or http://talk.maemo.org/showthread.php?t=87996 Sep 05 16:25:13 and there maybe could be some text error message from NOLO Sep 05 16:25:31 redirect to file Sep 05 16:25:35 both stdout and stderr Sep 05 16:25:48 it print every one usb packet Sep 05 16:26:10 go to src/ Sep 05 16:26:14 $ make libusb-sniff-32.so Sep 05 16:27:21 http://pastebin.com/raw/4mN0VEgD Sep 05 16:28:15 hm... you have gcc5 Sep 05 16:28:25 probably they broke something... argh! Sep 05 16:28:28 i can downgrade, no problem if its the only thing Sep 05 16:28:37 I used only gcc4 and it worked fine Sep 05 16:28:56 maybe sure that you have gcc multilib Sep 05 16:29:08 how do i check? Sep 05 16:29:13 resp. you have 32bit libs for -m32 Sep 05 16:29:18 32bit os Sep 05 16:29:29 then you have it :-) Sep 05 16:38:20 what i love about slack is that i can just install old gcc packages without dependency hell Sep 05 16:38:35 k, compiled now Sep 05 16:40:30 what was the flashing cmdline? Sep 05 16:41:24 use flasher-3.5 Sep 05 16:41:35 just preload that built library Sep 05 16:41:38 yes, but with which args Sep 05 16:42:28 --flash-only=cmt Sep 05 16:42:36 looks like this will do that Sep 05 16:42:55 other args? (if you know out of the head) Sep 05 16:42:57 at least --help say that Sep 05 16:43:05 normal args Sep 05 16:43:11 its combined or vanilla image? Sep 05 16:43:11 -F for fiasco image Sep 05 16:43:16 combined image Sep 05 16:43:38 and -f (which will flash) Sep 05 16:43:49 LD_PRELOAD=./libusb-sniff-32.so ./maemo_flasher-3.5_2.5.2.2/flasher-3.5 --flash-only=cmt -f -F RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin Sep 05 16:43:55 anything else? Sep 05 16:44:06 I think thats all, do not remember Sep 05 16:44:19 plus redirect output (stdout + stderr) to file Sep 05 16:44:57 and watch what is in file Sep 05 16:45:11 lots of output Sep 05 16:45:17 lets wait Sep 05 16:45:52 44M log already Sep 05 16:45:53 he he Sep 05 16:46:06 I wrote that :-) Sep 05 16:47:28 btw. why does it erase cmt twice? Sep 05 16:47:37 do not know Sep 05 16:47:52 IIRC operations are done by NOLO itself Sep 05 16:48:21 via usb you just send headr + image and then tell command "flash" Sep 05 16:48:34 and after that you can ask for flash status Sep 05 16:48:46 and NOLO tell you what it is doing now with modem Sep 05 16:48:51 i assume you are interested in ~2 last pages of output? Sep 05 16:48:56 or everything? Sep 05 16:49:11 it could be in end of output Sep 05 16:49:21 http://pastebin.com/raw/xeCBwWz1 Sep 05 16:49:25 but do not know if 2 pages will be enough Sep 05 16:50:21 hm... nothing :-( Sep 05 16:50:27 just "error" Sep 05 16:50:44 yup, what can i do now? Sep 05 16:50:46 fucking NOLO, it does not forward error messgae Sep 05 16:51:31 no idea :-( Sep 05 16:51:59 looks like internal memory of modem is broken Sep 05 16:52:11 as erasing is faling (for unknown reason) Sep 05 16:52:27 might be broken modem Sep 05 16:52:43 i have the same failure at 98% in one other board Sep 05 16:53:00 but at least it was working (- modem functions) Sep 05 16:53:08 DocScrutinizer05: ^^^^ any idea? Sep 05 16:53:21 is there any way to "hard" reset/clear N900 modem? Sep 05 16:53:24 this one probably needs some flashing, how do i flash user space only? Sep 05 16:53:27 sorry in a meeting, give me the telegram pls Sep 05 16:53:28 ie. emmc Sep 05 16:53:35 hmm Sep 05 16:53:51 KotCzarny: flash only rootfs Sep 05 16:53:57 proven theoretical or practical? Sep 05 16:54:10 or even "reset to factory"? Sep 05 16:54:30 NOLO for unknown reason cannot erase modem when flashing Sep 05 16:54:40 ugh Sep 05 16:54:58 pali: rootfs is in combined? Sep 05 16:55:10 then you're out of luck to a degree where all you could try is check if modem answers via pnatd Sep 05 16:55:24 most likely it's a hw defect Sep 05 16:55:44 modem implements same ARM coldflashing like OMAP3 Sep 05 16:55:52 and is too shy to tell us why Sep 05 16:56:05 just it's NOLO doing that for the modem, or even maemo userland Sep 05 16:56:47 is there some way to do that coldflash? Sep 05 16:56:59 KotCzarny: yes rootfs is in combined Sep 05 16:57:09 I *think* each modem firmware update is coldflashing Sep 05 16:57:20 rootfs isnt cutting it (not even nokia/5dots) Sep 05 16:57:33 KotCzarny: and flash also kernel Sep 05 16:58:15 maemo can update modem FW too Sep 05 16:58:17 anyway I think modem flashing is even done by userland, so obviously to flash modem you need a working maemo userland first Sep 05 16:58:32 but for that is needed DEB package Sep 05 16:58:36 not all sure but would be plausible Sep 05 16:58:39 from nokia repository :-( Sep 05 16:58:52 plus that DEB package remove modem image after flashing Sep 05 16:59:02 so even you have installed it, you do not have image anymore Sep 05 17:06:42 hmm Sep 05 17:07:06 how do i reset user data (emmc) ? Sep 05 17:07:14 its in bootloop still Sep 05 17:07:17 ~bootloop Sep 05 17:07:21 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. Sep 05 17:10:10 also weird thing is, at first i was getting output on the screen (during boot or in rescueos) Sep 05 17:10:37 now i dont. what could be the reason? is there some display firmware somewhere that got broken during flash? Sep 05 17:11:26 after flashing emmc you need to flash rootfs Sep 05 17:12:05 stupid question, how do i flash emmc? Sep 05 17:12:15 via flasher-3.5 Sep 05 17:12:26 but which image/params Sep 05 17:12:26 pass fiasco emmc image Sep 05 17:12:40 vanilla, yes? Sep 05 17:12:43 fiasco emmc binary contains only mmc image Sep 05 17:12:46 yes Sep 05 17:12:49 k Sep 05 17:24:04 afair, missing display (bad cable/screen) could also be the bootloop reason Sep 05 17:35:16 do you see nokia logo? Sep 05 17:36:11 nope Sep 05 17:37:05 and can you identify device via flasher-3.5? Sep 05 17:37:13 display/cable/chip might be the reason Sep 05 17:38:01 yes, i can flash it/boot rescueos. just nothing on screen (and as i said, it was working earlier) Sep 05 17:38:38 hm... maybe problem with display Sep 05 17:38:47 wow, 9usd for display ribbon Sep 05 17:38:56 in flash mode you should see NOKIA log Sep 05 17:39:05 anyone got a cheap source for them? Sep 05 17:39:46 http://www.ebay.com/p/Fake-Camera-Flex-Cable-Ribbon-for-Nokia-N900-a-355/1331819378 Sep 05 17:39:47 wtf? Sep 05 17:54:00 ~bootlog Sep 05 17:54:04 hmm Sep 05 17:55:24 http://wiki.maemo.org/User:Joerg_rw/PC_syslog_of_USB_enum Sep 05 17:55:41 ~listvalues PC_syslog_of_USB_enum Sep 05 17:55:44 Factoid search of 'PC_syslog_of_USB_enum' by value returned no results. Sep 05 17:56:19 ~#maemo PC_bootlog is http://wiki.maemo.org/User:Joerg_rw/PC_syslog_of_USB_enum Sep 05 17:56:19 okay, DocScrutinizer05 **** ENDING LOGGING AT Tue Sep 06 02:59:58 2016