Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 7 hrs, 41 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 20 hrs ago - more...
|
2013-05-02
, 14:26
|
|
Posts: 43 |
Thanked: 0 times |
Joined on Apr 2013
|
#722
|
SB
I'll check out phoenix software right away!
I purchased the phone in USA on eBay. It wasn't even a great deal so say the truth, so that's why this its totally a surprise. Now I'm starting to doubt if there is any possibly than the company that sold me the phone has changed the Sim tray. I'll check if the IMEI on the box, and the IMEI stamped on the phone do correspond.
I'll check out phoenix software right away!
I purchased the phone in USA on eBay. It wasn't even a great deal so say the truth, so that's why this its totally a surprise. Now I'm starting to doubt if there is any possibly than the company that sold me the phone has changed the Sim tray. I'll check if the IMEI on the box, and the IMEI stamped on the phone do correspond.
|
|
2013-05-03
, 02:11
|
|
Posts: 87 |
Thanked: 7 times |
Joined on Apr 2013
|
#723
|
Originally Posted by polomarko
I would do the things you have mentioned. it may take some detective work to find the real origin of your phone. the sim tray SHOULD provide the answer. I would want to confirm that somehow. possible with Phoenix by scanning the product code and see if it matches the sim tray? I doubt the sim tray would be changed, it is more likely that someone has changed the product code and forced another codes software that is not being accepted by the patient/N9.
SB
I'll check out phoenix software right away!
I purchased the phone in USA on eBay. It wasn't even a great deal so say the truth, so that's why this its totally a surprise. Now I'm starting to doubt if there is any possibly than the company that sold me the phone has changed the Sim tray. I'll check if the IMEI on the box, and the IMEI stamped on the phone do correspond.
the sim error and wifi problem tell us that you have a a problem at least with the CMT or possibly the whole PR.....?? .bin file.
|
|
2013-05-03
, 07:33
|
|
Posts: 79 |
Thanked: 37 times |
Joined on Feb 2012
|
#724
|
About downgrade thingy not allowed, its not very logical. I cannot downgrade to pr339 from pr280 no matter what i try. i upgraded to 1.3 from nokia software update (i had a flashed pr001 on 1.2) and after NSU was done i had 280 again.
Its no big deal really but i cannot choose to lock it in 2g since pr280 has that option dimmed out.
Going to try a external 2g/3g/dual switcher to se if that helps tho. But as i said, downgrading rules are not as simple as you think.
(i have soon downloaded most of new navifirm (new backup links) and tried flashing most of them. I all accompliced tho is making a monthly record in legal GB downloads :P )
Its no big deal really but i cannot choose to lock it in 2g since pr280 has that option dimmed out.
Going to try a external 2g/3g/dual switcher to se if that helps tho. But as i said, downgrading rules are not as simple as you think.
(i have soon downloaded most of new navifirm (new backup links) and tried flashing most of them. I all accompliced tho is making a monthly record in legal GB downloads :P )
|
|
2013-05-03
, 08:14
|
|
Posts: 131 |
Thanked: 22 times |
Joined on Sep 2012
@ India
|
#725
|
Originally Posted by rekemaro
As I expected , your cmt only flash has worked. So what is problem now? Please read other discussion here and try to do things logically.
I've got Virgin and tried to do cmt only flash.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 3240 kB/s]
Success
than i try to flash
bb5_rdc_cert_read failed
mmc: handle_buffer failed in lzo decompress (-1)
[Pipe 4] Finishing in error state with status 1
i will try the next fw
i hope they work
|
|
2013-05-03
, 08:16
|
|
Posts: 131 |
Thanked: 22 times |
Joined on Sep 2012
@ India
|
#726
|
Originally Posted by shma
Same here, I also downloaded almost 20GB worth data
About downgrade thingy not allowed, its not very logical. I cannot downgrade to pr339 from pr280 no matter what i try. i upgraded to 1.3 from nokia software update (i had a flashed pr001 on 1.2) and after NSU was done i had 280 again.
Its no big deal really but i cannot choose to lock it in 2g since pr280 has that option dimmed out.
Going to try a external 2g/3g/dual switcher to se if that helps tho. But as i said, downgrading rules are not as simple as you think.
(i have soon downloaded most of new navifirm (new backup links) and tried flashing most of them. I all accompliced tho is making a monthly record in legal GB downloads :P )
I would like to know if there is some way to remove this downgrade disallowed thing, I think this should be possible.
Since there are many smart guys here, I am sure someone must have figured it out,
|
|
2013-05-03
, 16:28
|
|
Posts: 87 |
Thanked: 7 times |
Joined on Apr 2013
|
#727
|
Originally Posted by suyog
suyog> is your N9 stable yet?
Same here, I also downloaded almost 20GB worth data
I would like to know if there is some way to remove this downgrade disallowed thing, I think this should be possible.
Since there are many smart guys here, I am sure someone must have figured it out,
|
|
2013-05-03
, 18:01
|
|
Posts: 131 |
Thanked: 22 times |
Joined on Sep 2012
@ India
|
#728
|
Originally Posted by rswelter
Unfortunately No
suyog> is your N9 stable yet?
It worked for almost 2 days and started giving problem again.
So it is kind of hit and miss now.
|
|
2013-05-04
, 11:44
|
|
Posts: 446 |
Thanked: 207 times |
Joined on Sep 2012
@ Austria/Germany
|
#729
|
Hey guys,
So I started the flashing process with the secure erase option and it's taking forever...
I was wondering if it's safe to abort the process and start it again without secure erase?
So I started the flashing process with the secure erase option and it's taking forever...
I was wondering if it's safe to abort the process and start it again without secure erase?
Code:
user@kiwi> flasher -f -F N9_ N9_EMMC.bin N9_MAIN.bin user@kiwi> flasher -f -F N9_MAIN.bin --erase-user-data=secure flasher 3.12.1 (Oct 5 2011) Harmattan WARNING: This tool is intended for professional use only. Using it may result in permanently damaging your device or losing the warranty. USB device found at bus 253, device address 3. Device serial number is N/A Found device RM-696, hardware revision 1603 NOLO version 2.3.6 Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001 Sending ape-algo image (7096 kB)... 100% (7096 of 7096 kB, avg. 11300 kB/s) Suitable USB interface (phonet) not found, waiting... USB device found at bus 253, device address 3. Device serial number is Raw data transfer EP found at EP2. Ping attempt 1 (250 ms) Server application: 1.7.2 Found product RM-696 rev. 1603 Server implements softupd protocol version 1.8 Battery level 19 %, continuing. Erasing, this may take a while.
|
|
2013-05-04
, 14:40
|
|
Posts: 131 |
Thanked: 22 times |
Joined on Sep 2012
@ India
|
#730
|
Originally Posted by mcbook
I would leave it running for few hours at least.
Hey guys,
So I started the flashing process with the secure erase option and it's taking forever...
I was wondering if it's safe to abort the process and start it again without secure erase?
Code:user@kiwi> flasher -f -F N9_ N9_EMMC.bin N9_MAIN.bin user@kiwi> flasher -f -F N9_MAIN.bin --erase-user-data=secure flasher 3.12.1 (Oct 5 2011) Harmattan WARNING: This tool is intended for professional use only. Using it may result in permanently damaging your device or losing the warranty. USB device found at bus 253, device address 3. Device serial number is N/A Found device RM-696, hardware revision 1603 NOLO version 2.3.6 Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001 Sending ape-algo image (7096 kB)... 100% (7096 of 7096 kB, avg. 11300 kB/s) Suitable USB interface (phonet) not found, waiting... USB device found at bus 253, device address 3. Device serial number is Raw data transfer EP found at EP2. Ping attempt 1 (250 ms) Server application: 1.7.2 Found product RM-696 rev. 1603 Server implements softupd protocol version 1.8 Battery level 19 %, continuing. Erasing, this may take a while.
Better to wait for 3-4 hours before aborting.
I agree with rswelter...use the phoenix software and start completely all over. You can find tutorials in this website and also on youtube that will walk you thru it step by step.
Where did you buy the phone from?
SB