Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 15 hrs, 11 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 11 hrs ago - more...
|
2012-12-20
, 05:47
|
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#392
|
Originally Posted by mcbook
If you were able to use another sim card on it how can it be sim-locked? I'm not aware of what sim-lock actually does due to never experiencing it but doesn't it mean that you can't use another sim card from another carrier in the phone? If you have been able to use other sims I think your phone should not be sim-locked...
hey guys,
i'm havnig some problems with my n9 and thus decided to flash it
i'm just worried about the simlock...
i bought my n9 used and without simlock, now i'm worried that if i flash it will lock the device to a certain carrier (maybe the device was once locked who knows...)
what are the chanced of that happening?
It would be better to simply flash a ROW pr1.3 firmware with a pr_legacy_001. It is a vanilla firmware with no operator remnants...
|
|
2012-12-20
, 05:51
|
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#393
|
suyog,
I'm not very sure about your issue but if you are to use the --erase-user-data=secure flag AFAIK you should be including both the rootfs.bin and emmc.bin i.e. flasher -f -F rootfs.bin -F emmc.bin --erase-user-data=secure
Maybe do that and see if your hardware is being detected... Someone else with more knowledge of this should advice on what else should be done if its just a software issue...
I'm not very sure about your issue but if you are to use the --erase-user-data=secure flag AFAIK you should be including both the rootfs.bin and emmc.bin i.e. flasher -f -F rootfs.bin -F emmc.bin --erase-user-data=secure
Maybe do that and see if your hardware is being detected... Someone else with more knowledge of this should advice on what else should be done if its just a software issue...
| The Following User Says Thank You to thedead1440 For This Useful Post: | ||
|
|
2012-12-20
, 07:07
|
|
Posts: 35 |
Thanked: 13 times |
Joined on Sep 2012
|
#394
|
Originally Posted by thedead1440
So it's not a problem that the led goes off after a minute and flasher -i stops seeing it? As long as it's detectable when flasher -f starts, it should be fine, shouldn't it?
jorge,
What you can do is type flasher -f -F rootfs.bin in cmd and when the suitable device/phonenet not found message appears to plug in your phone... Now here you have to be extra cautious as flasher will say unable to flash due to battery being insufficient... 11% is the bare minimum required to start a flash so once you see its charged till 9-10%, you plug out your device and connect to a wall plug for at least 30minutes before attempting to switch it on etc...
Once the above is done your phone should charge normally and work as before without having had to conduct a flash...
I've had the device plugged into the chager for some 7 hours in total so the battery level should be fine.
|
|
2012-12-20
, 07:31
|
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#395
|
Originally Posted by jorge
Once the device loses all charge, plugging into a wall plug only works if its booting into Android... You can plug it in for X number of hours but it won't accept charge in the stock kernel hence you have to use the flasher method by plugging in only after the message of device not found comes up...
So it's not a problem that the led goes off after a minute and flasher -i stops seeing it? As long as it's detectable when flasher -f starts, it should be fine, shouldn't it?
I've had the device plugged into the chager for some 7 hours in total so the battery level should be fine.
|
|
2012-12-20
, 09:15
|
|
Posts: 35 |
Thanked: 13 times |
Joined on Sep 2012
|
#396
|
Originally Posted by thedead1440
Oh, I'm just a slowpoke
Once the device loses all charge, plugging into a wall plug only works if its booting into Android... You can plug it in for X number of hours but it won't accept charge in the stock kernel hence you have to use the flasher method by plugging in only after the message of device not found comes up...
Did your first reply refer to booting the device with existing firmware instead of re-flashing it?
|
|
2012-12-20
, 09:16
|
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#397
|
Originally Posted by jorge
Its the same process as doing a re-flash only you have to prevent a re-flash by plugging out your device (or pressing Ctrl+C) at the 9-10% battery level mark as once it reaches 11% a flash will be initiated...
Oh, I'm just a slowpoke
| The Following User Says Thank You to thedead1440 For This Useful Post: | ||
|
|
2012-12-20
, 11:25
|
|
Posts: 35 |
Thanked: 13 times |
Joined on Sep 2012
|
#398
|
Yep, I got it, thanks. Had the flasher show battery percentage once but then decided to abort and switch to a more powerful USB port. It did't go beyond that but when I switched it back it immeidately showed "12%, continuing"
Well, I now know how to flash It ended up too quickly though but I do see the 'Updating SW release. Success' line.
On a side note, flasher is open source, isn't it? Is it not possible to come up with a 'charger' tool that doesn't require a gigabyte image and cannot reflash if you only want to charge? Or is this situation too rare?
Even if it is rare, I think it would be useful to add this procedure description to the first post in this thread for dummies like me.
(Of course, the first thing I myself would answer would be 'do it, people will thank you!' )
Last edited by jorge; 2012-12-20 at 11:29.
Well, I now know how to flash
It ended up too quickly though but I do see the 'Updating SW release. Success' line.On a side note, flasher is open source, isn't it? Is it not possible to come up with a 'charger' tool that doesn't require a gigabyte image and cannot reflash if you only want to charge? Or is this situation too rare?
Even if it is rare, I think it would be useful to add this procedure description to the first post in this thread for dummies like me.
(Of course, the first thing I myself would answer would be 'do it, people will thank you!'
)
Last edited by jorge; 2012-12-20 at 11:29.
|
|
2012-12-20
, 13:36
|
|
Posts: 123 |
Thanked: 91 times |
Joined on Apr 2012
|
#399
|
I thought flasher wasn't open source
|
|
2012-12-20
, 18:12
|
|
Posts: 131 |
Thanked: 22 times |
Joined on Sep 2012
@ India
|
#400
|
Originally Posted by thedead1440
Thanks for reply. As I posted earlier, while using Android via nitdroid also I am unable to detect Cellular network so I am almost certain that this looks like hardware issue.
suyog,
I'm not very sure about your issue but if you are to use the --erase-user-data=secure flag AFAIK you should be including both the rootfs.bin and emmc.bin i.e. flasher -f -F rootfs.bin -F emmc.bin --erase-user-data=secure
Maybe do that and see if your hardware is being detected... Someone else with more knowledge of this should advice on what else should be done if its just a software issue...
But now I am facing issues exactly like @jorge. N9's battery was down and it switched off at end of the day. Then I plugged it in wall USB charger which comes with N9. No luck , it won't charge or turn on at all. No LED while plugged to AC Mains.
If I plug in to my laptop USB, LED blinks for a while and then goes off. It even vibrates but nothing happens after that.
I tried to check battery level by trying to run flasher and it says 0% but flasher detects it.
I will try to keep it plugged in to laptop overnight and see if that helps. I am not sure if all issues are hardware related or software but when I owned same N9 for over 3 months , I never faced anything like this. Even my earlier N9 16GB also never had any hardware issue.
I will be grateful if anyone in this forum from Poland can check in local Nokia care if they provide service as my N9 is from Poland.
I wanted to know if Nokia Care in Poland demands proof of purchase/Bill to get phone serviced by them. If that is possible I am willing to send it all the way to Poland.
What you can do is type flasher -f -F rootfs.bin in cmd and when the suitable device/phonenet not found message appears to plug in your phone... Now here you have to be extra cautious as flasher will say unable to flash due to battery being insufficient... 11% is the bare minimum required to start a flash so once you see its charged till 9-10%, you plug out your device and connect to a wall plug for at least 30minutes before attempting to switch it on etc...
Once the above is done your phone should charge normally and work as before without having had to conduct a flash...