![]() |
2010-05-12
, 13:05
|
|
Posts: 663 |
Thanked: 282 times |
Joined on Nov 2009
@ London, UK
|
#112
|
![]() |
2010-05-12
, 13:08
|
Posts: 999 |
Thanked: 1,117 times |
Joined on Dec 2009
@ earth?
|
#113
|
The Following 3 Users Say Thank You to johnel For This Useful Post: | ||
![]() |
2010-05-12
, 13:12
|
Posts: 303 |
Thanked: 175 times |
Joined on Oct 2009
@ London UK
|
#114
|
![]() |
2010-05-12
, 13:15
|
Posts: 968 |
Thanked: 974 times |
Joined on Nov 2008
@ Ohio
|
#115
|
![]() |
2010-05-12
, 13:16
|
Posts: 1,427 |
Thanked: 2,077 times |
Joined on Aug 2009
@ Sydney
|
#116
|
The main risk of damage with the O/Cing is that the device gets locked into 100% CPU sometime in the night and then stays that way for an extended period going unnoticed and fries.
Getting locked at 100% usage is a bit of a risk, especially with Devel and Testing apps installed.
![]() |
2010-05-12
, 13:26
|
Posts: 1,751 |
Thanked: 844 times |
Joined on Feb 2010
@ Sweden
|
#117
|
The thing is.. in the cmd window screenshot he posted.. it DOES see the device to start with.. it asks it to move into emmc flashing mode, then the device disappears and doesn't come back..
From a flasher perspetive, unpluging the deivce AFTER it has been moved (or asked to move) into emmc mode is likely to jump it back out of that mode anyway.. You shouldn't unplug the device between these two steps..
Go back and have a look
First it says:
USB device found at bus bus-0, device address is \\.\libusb.....
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009.....
Booting device into flash mode.
Then it says
Suitable USB device not found, waiting.
So, it never made it into flash mode.. but flasher DID see it.. Unpluging imho would be inadvisable at this point..
I saw someone earlier today with this same problem.. to solve it, we flashed the os image FIRST, then without rebooting or unplugging, we flashed the emmc..
I'm not sure windows is the problem.. it can initially see the phone, but it can't see it after asking it to go into flashing mode.. and an unhappy phone, it seems, doesn't always make it into flashing mode..
flashing the os has, in my experience, solved that problem and the subsequently allowed the emmc to be flashed.
![]() |
2010-05-12
, 13:35
|
Posts: 472 |
Thanked: 442 times |
Joined on Sep 2007
|
#118
|
The Following User Says Thank You to Laughingstok For This Useful Post: | ||
![]() |
2010-05-12
, 13:39
|
Posts: 23 |
Thanked: 5 times |
Joined on Mar 2010
@ Esbjerg - Denmark
|
#119
|
![]() |
2010-05-12
, 13:41
|
Posts: 472 |
Thanked: 442 times |
Joined on Sep 2007
|
#120
|
hmm who gives a fu... about if the n900 cant stand the overclock or the leaked firmware.. its a phone if its broken fix it or buy another one .. stop this redicouls threads they realy starts to pi.. me off ..
evry time i look in this forum there are always a couple of threads about someone whining about the phone is dead due to leaked firmware.. or due to overclock ... SOOOOO WHAT .. get a freeking life and move on.. and use this forum for the real problems regards the official firmware and the stock phone..
If you use the leaked firmware and you overclock the n900 then you must have some sort of understanding about the phone arcitecture so you know what to do when shi... happens. there are a gassilion threads in here that points to how you boot and flash the freak... phone SO SEARCH before posting.. Fuc... head
sorry for the language i just got so tired of reading this thread and having a bad day LOL
(And i don't think this has with overclocking like the topic say.. maybe PR1.2.. but most likely something els.. like a prog from devel.)
Last edited by AlMehdi; 2010-05-12 at 13:07.