|
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Recieved further follow up email from portagadgets, but no additional information. Again, these guys have been great, and I would definitely purchase from them in future.
I now have externel battery charger, and successfully cold flashed device. Here is output: C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -c -h RX-51:2101 -S usb -F RX -51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin -f 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 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, 2 113, 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, 2 113, 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, 2 113, 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, 2 210, 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, 2 210, 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, 2 210, 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 Using serial port usb Suitable USB device not found, waiting. USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0 106. Waiting for ASIC id... Got 69 bytes. ASIC ID: 05 01 05 01 34 30 07 57 13 02 01 00 12 15 01 30 af 1b a5 39 63 46 15 0b bb cd 4e a5 e8 12 8b 64 7f 23 5d 14 15 01 87 3b 4d cd ca f5 44 4d 24 ec b2 ac 95 53 88 41 4f ab cd 66 15 09 01 f7 48 8f 28 a0 27 e5 b3 Sending 2nd image (zu bytes)... done. Sending ping... usb_bulk_read: No error failed. Sending ping... pong. Sending secondary (zu bytes)... done. Suitable USB device not found, waiting. USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0 105. Found device RX-51, hardware revision 2204 NOLO version 1.4.14 Version of 'sw-release': RX-51_2009SE_20.2010.36-2.206.1_PR_206 Overriding revision information given by board. Sending xloader image (14 kB)... 100% (14 of 0 kB, avg. 14 kB/s) Sending secondary image (106 kB)... 100% (106 of 0 kB, avg. 106 kB/s) Flashing bootloader... done. Sending cmt-2nd image (79 kB)... 100% (79 of 0 kB, avg. 79 kB/s) Sending cmt-algo image (507 kB)... 100% (507 of 0 kB, avg. 507 kB/s) Sending cmt-mcusw image (5826 kB)... 100% (5826 of 0 kB, avg. 5826 kB/s) Flashing cmt-mcusw... done. Sending kernel image (1705 kB)... 100% (1705 of 0 kB, avg. 1705 kB/s) Flashing kernel... done. Sending and flashing rootfs image (185728 kB)... 100% (185728 of 0 kB, avg. 185728 kB/s) Finishing flashing... done CMT flashed successfully I then tried to flash emmc, here is output: C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2. VANILLA_PR_EMMC_MR0_ARM.bin -f flasher v2.5.2 (Sep 24 2009) Image 'mmc', size 255947 kB Version RX-51_2009SE_10.2010.13-2.VANILLA USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0 105. 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 bus-0, device address \\.\libusb0-0001--0x0421-0x0 1c8. Raw data transfer EP found at EP2. Image(s) flashed successfully in 28.015 s (9135 kB/s)! Device won't boot, and I am having trouble getting flasher3.5 to see it when connected via USB. Holding 'u' will not put n900 into flash mode, i am going to experiment with live linux distro to gain more control over usb port. I have tried flashing with 2 different notebooks now, one winxp SP3, one vista starter |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
looking at output, i flashed with wrong parameters for device, my device is hardware revision 2204, i flashed 2101
|
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
coldflashing in linux now, i am not sure, i think i should flash mmc again before reboot, for this first time i will flash fiasco with normal flash as well, so will be cold flash -> emmc -> fiasco...
...can't get it to boot, having trouble performing uninterrupted boot between pr1.3 and mmc, dunno. Probably play around later, and then take to repair centre. ...I can flash phone normally now, but holding "u" will not halt phone in flash ready state. When flashing mmc the phone appears to start loading OS, but flash proceeds and is reported successful on laptop. When flashing OS, a green bar appears on the n900 and fills to completion, and flash is reported successful on laptop. I'll post outputs later. Device will not boot, halts on flashing dots after cycling a few times, powers off. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Interesting thread, my N900 also shut down whilst plugged into a car charger. Now in endlessly reboots when connected to pc via usb or mains charger. I can't get it to boot past the 5 dots, it always highlights the middle doot and then shuts down.
I've quickly read this whole thread, is there anything I can do to fix my phone. It's been suggested i try flashing the framebuffer kernel. Does this mean I need to flash 1.3 then flash the emmc? Any help would be greatly appreciated. p.s. I did have backupmenu installed, which allowed me to copy off my files. But when I reflashed 1.3 this has gone. Thanks Steven |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Screw emmc, just flash 1.3 *then* framebuffer kernel - you'll be able to see on which part of booting process something goes wrong.
This way, people have un-puzzled most mysterious problems, like guy, whose device stopped accepting any batteries (via wrong BSI raw values - of course that was conclusion, at the beginning we haven't got a clue what's going on. Long story short, it was semi-fixed by using modified getbootstate). |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
what is and where can I find frame kernelbuffer?
Thanks in advance. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
forum /search
wiki /search I'm not providing "just links", because You need to read about it before using - it's not fool proof. More you read about usage during search, the higher chance of succeeding You have. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
A service centre flash will quite possibly fix (portagadgets flashed my device and fixed). So, maybe flashing with phoenix will fix (long stretch), dunno (I absolutely do not know what im talking about here, but there are a couple of reports on internet of people flashing successfully with phoenix). I'm going to do a few more flashes over weekend (pr1.2) , then send to nokia.
Portagadgets told me no hardware replacement was needed to fix, and they just flashed device. I can't find frame buffer kernel page by searching, there is a link to the file in the first page in this thread, but i can't find any page explaining its use. When I installed it, the text flashed too quickly to see what was going on. here is page describing flashing with phoenix, http://gsmobserver.blogspot.com/2010...h-phoenix.html @ziggadebo, did you encounter problem when turning ignition with n900 plugged in? i did |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
My N900 was happily plugged into car charger, playing ACDC through rockbox at an obscene volume, when it made a pop sound and shutdown.
I'll be returning mine to the service provider today, I beleive it's in warranty as I have a two year contract. I did get it to boot last night in R&D mode, but the battery was critical and after a couple of minutes shutdown Now I can't charge it, so I'm going to have to hope it can be repaired and not replaced with a lesser phone. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
off-topic - your posts, guys, just made me suddenly not willing to plug my N900 into any cheap car chargers...[/off-topic]
I'm just wondering what the hell can make such accidents. N900 contain overvoltage and overcurrent protection... The charger suddenly gave high voltage to data pins, or what? |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
@zigedeboo, don't flash any kernels if you going for warranty repair, I *think* i had voided my warranty prior to this whole thing maybe by enabling extras-devel, or when downloading flash software, but anyway portagadgets couldnt give my phone to nokia to fix because of stuff i had done to phone. If i entered imei into nokia site, it said no warranty information available.
Was your car charger a cheap one or good one? @estel Don't have to worry about posting etiquette too much in this thread, it is a mess. When it finally comes to its conclusion, i'll compile relevant info into first post. I'm wondering if drain on charger (from starter engine pulling current, or stereo pulling current) somehow interacted with phone, but i don't know anything. There are a whole lot of big copper coils in automotive electrics, and probably a lot of weird inductance stuff goes on when engaging and disengaging starter solenoid. Also lots of capacitance in stereo systems (and speakers), stray electrons looking for atoms to call home, battery in n900 to jump to, dunno. I had problem with same charger, 2 different cars (one too old for engine computer, one still old but has engine computer, which doesn't work properly and wont hold idle still). I think my first crash was when playing music with mediabox, output through fm transmitter. 2nd crash I'm not sure if i was playing music or not. Still, don't know if problem solely due to charger, or something else. BUT me and zigadeboo appear to have exactly the same problem, both phones entered reboot loop instantly. I tried to fix with flash, and failed. What is really weird is service centre flash can fix, but maemo flash not. I did manage to enable rd-mode for first crash, after flashing, but didn't help. Going to go into linux now and do some more flashing. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
That's why I would *love* to see frame-buffer output - to know in which part of booting process it fails exactly. It would be possible to determine filesystem corruption fs software failure vs hardware failure.
On the other hand, I don't want to made anyone warranty attempts harder. Technically, enabling devel or flashing different kernel should not void warranty for N900 - due to nature of device and tools available (using flasher don't void warranty, and You can flash whatever You want - they won't fix broken kernel for You for free, but they *should* fix unrelated issues, even if You played with kernels), but I agree that for most lame service assistants, just seeing backupmenu or framebuffer output would scarry the s.h.i.t out of them, and they're gonna claim You've void Your warranty. Theoretically, you're able to prove that You still got warranty rights, practically, it may be hard. Of course, flashing back stock kernel - before you take it to repair center - could make them GTFO, but if you won't be able to flash back, by any reasons... So, I agree here with quokka - although, with much "sadness", cause I like to trace down sources of problems ;) Also, sorry that I didn't mentioned possible issues with warranty centers, when suggesting framebuffer. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Quote:
|
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
car charger was a cheap one (well it cost £15) but it isnt branded. My first N900 had a simular problem using the charger, the screen stopped working. It would still boot but no screen output. It was replaced under warranty as I was told it couldnt be fixed.
Anyway mines gone for repair, when they do get it into the workshop they'll find it's in R&D mode but I don't think that will void my warranty. I didn't flash the kernal as the battery was completely flat and wouldn't charge in R&D mode. However if my carrier values me as a customer, then I'd expect it to be fixed. I did have to sign a document that states if it can't be fixed then they will replace with a refurbished phone of simular stauture, which will be tricky as we all know theres nothing else like the N900 on the market. I may except this though, then sell it and buy an N900, safe in the knowledge that in 2 months my contract ends and I can then get something I want. anyone want to buy a phone car charger? :D |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
only flashing a kernel or the system(emmc..) as provided should not void warranty. i did by far more to my phone and would argue i didn't void any warranty.
but trying to solve things that need indepth knowledge is up to the nokia service. nice if people try to help and all. also fine if there are "hackers" around who want to learn the details of a device and are aware that they might break something. but if one just want to use the phone and get a more complicated issue fixed: nokia(or partner..) is the way to go. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Quote:
|
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Quote:
|
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Hardware protection circuit isn't bypassed, and isn't features of the chip... Check N900 schematics.
|
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
that happened with me once
i fixed it by flashing pr1.2 image then pr1.3 then the emmc wish it helps |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Quote:
.... |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
OK< if You try to "catch on words", it's not ONLY one included in N900, and not the one I'm referring to. That's why I told You to "check N900 schematics", not chip schematics... ;) you probably already know - stubborn one - that I'm mentioning circuit *before* chip - that one is bypassed completely, when using pins beneath battery as 5V+, ground, and DATA pins (aka additional USB). That ones - beneath battery - bypasses circuits, so they're dangerous to use "out-of-lab", i.e. without proper filtered cable, reliable peripheral devices etc. Pins beneath battery connect directly to the chip
On the other side, after USB port (but before chip) You got plenty of non-software-controlled protection elements... *That* explanation is clear enough?... |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
sorry i still haven't managed to get time to do flashing. Hopefully tonight (10hrs time)
|
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
how would i get framebuffer output to txt file?
and my limited understanding leads me to think it is watchdogs not seeing something that they want to see that is causing reboots. ^this is from the glimpses i could see when i had framebuffer kernel installed, which i wrote about earlier in thread. BUT, i couldn't even really tell you what a watchdog is, so value of my input is limited. I do have slight hope for flashing pr1.2 first, as suggested by karem, but catch .22 i would like to upload framebuffer output if possible for others here to look at, cant do if by freak chance i fix device... |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Watchdog is quite possible cause - try first flashing framebuffer in R&D mode on, it disables watchdogs.
Also, maybe it's good idea of make video - N900 screen while booting with framebuffer? ;) Ho ever, I'll ask around, about output to file. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
THINK I FIXED IT.
enabled rd mode (dont know if this helped or not) installed latest version pc suite and drivers and nokia software updater. Chose to update device, but phone would never manage a stable connection because of turning itself off, when blurb came up asking me to reconnect phone in pc-suite mode i just kept hitting retry until connection was made for long enough, chose reinstall firmware... but before download of software had even started the phone booted with the login chime. :D:D:D dunno what to do now, the phone is working but still have to wait 10min for NSU to download image... i'm a bit overwhelemed, really. Nothing makes sense. edit: it can reboot sensibly now... edit 2: it seems all i did was enable rd mode, now device boots, works |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Strange. But I think it may be R&D mode that helped, if You've used no lifeguards option via flasher.
anyway, You can check it by disabling R&D mode (fvia flasher), if it will end in reboot loop, you know what have helped ;) Still, even thought working in R&D mode doesn't have any drawbacks (you can even turn of that keyboards led blinking), it's good to know what is screwed so badly that it can't work outside R&D. you know, what watchdogs are complaining about. // Edit And don't use cheap car chargers ;) |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
sorry, i put in an edit 12hrs ago but it didnt update thread, it said yeah, i've confirmed that all i did was enable rd mode to fix, phone will not boot in normal mode.
Also, i updated again firmware again with nokia software updater and now parts of the keyboard wont work, if i go into settings -> text input -> nokia keyboard layout the best option is English, Nederlands, But for now i'm pretty happy to have a phone that works, i'll play around with settings and hopefully get a framebuffer output of failing boot in this thread later. NSU updated phone to 20.2010.36-2.207, but i can't find what this image is. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Just to update you all.
My phone couldn't be repaired and I've been given an N8 as a replacement (it's brand new). I argued for over an hour that at the very least I wanted an E7 as a replacement. I was told there was a £100 price difference between the 2 phones and that I would have to pay this excess. I offered to pay half, this was rejected. They tried to argue the N8 was a like for like replacement, I pointed out the different operating systems, lack of keyboard etc... but was told on numerous occasions, "the computers telling me it's a like for like replacement" At this point, I told them they sounded like a character from Little Britain, they wouldn't budge. When I asked what would happen if I didnt except the N8 they re-iterated my phone couldn't be repaired and that this was there best offer. Vodafone (UK) have the N8 on their books at £350 and the E7 at £450. They offered me any other phone up to the value of £350, again I pointed out there is nothing on the market like the N900. I'm tempted to buy a second hand N900, but as I've had two replacements already in 20 months and they can't be repaired for a lack of spare parts, I'm not going to. Guess I'll hold tight and see what comes to market, I only have 1 month to go before I can renew my contract. A sad day indeed :( |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
Quote:
I have two N900 devices. The first one is my primary phone, use it on a daily basis and is almost 2 years old, the second one I use for development and is younger (16 months). Both work fine, no problems. |
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
ziggadebo, I would also just buy a second-hand N900. If You look around for a while, You can buy one in perfect condition for ~150$ easily (and for 200$ without looking too much ;) ), so after selling Your brand new N8, You'll end with quite high amount of money left after trade ;)
|
Re: infinite reboot loop reflash pr1.3 and emmc wont fix...
zigedeboo- sucks, and shitty service too, Why dont they replace with n900? Did they even try a reflash?
My phone works... just doesn't charge and parts of the keyboard dont work (i think partly because of incompatible flashes i've been doing... who knows) It is a pity you can't get the broken n900 back for free, it is still very useful even without key board or self charging. And a fix is still a possibility... My phone, after numerous flashes including a sucessful flash with phoenix flasher, has made no progress. Still trying to work out how to put framebuffer output into text file, but I haven't really been exposed to much linux stuff so i quite often get distracted when reading about different parts of the os. Currently running powerkernel 48, still in rd-mode The virtual keyboard is nice, but no substitute for hw keyboard, so expect further updates as time goes on. 1st priority is to get debug info into this thread, unfortunatly i don't have a video camera to manually capture boot messages (just had a thought, the av out cords may come in useful here...). also, i'm wondering if i mucked up hw-revision information on my device, anyone know if this is easily possible? maemo flasher does have the --set-hw-revision argument.so presumably it is possible, but i haven't entered that argument at all. My phone product type is 0593611 N900 RX-51 Country Variant United Kingdom GB V1 Black - MR, but i cant find any information about hw-revision for that code. The device reports itself as revision 2204 |
| All times are GMT. The time now is 06:10. |
vBulletin® Version 3.8.8