Also I noted that Nemesis Suite is not able to change or even read product information now. I am not able to change mode to Test or Local.
This may not be relevant but I just wanted to mention as I had done variant code change via nemesis.
I'm confused, where it says 'replace main.bin and emmc.bin in the commands with the actual names of the image files you are flashing', does this mean I replace them with both file names? So replace 'main.bin' with 'DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_003-OEM1-958_ARN.bin DFL61_HARMATTAN_40.2012.13-7.PRC_EMMC_PRC.bin'
Do I put both with a space inbetween them like above?
@Callum You can either rename DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_003-OEM1-958_ARN.bin file to main.bin AND FL61_HARMATTAN_40.2012.13-7.PRC_EMMC_PRC.bin to emmc.bin and use same commands. Please note that there are 2 commands.
first is
flasher -f -F main.bin
Following by (This is optional, only if you want to get content loaded like videos, music, maps data and few other things) which comes with new factory condition phone
suyog post full output of the flash and device firmware version from settings->about product
I tried nitdroid and found that Cellular data or even network detection is not working there.
So I am feeling that this is hardware issue.
That guy whom I sold this N9, managed to screw cellular components somehow and now trying to put blame on me,
Is there any authentic way to verify it? Can SystemInfo app can confirm?
If this is hardware issue, I just want to be 100% sure and show that guy exact reason.
@Callum You can either rename DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_003-OEM1-958_ARN.bin file to main.bin AND FL61_HARMATTAN_40.2012.13-7.PRC_EMMC_PRC.bin to emmc.bin and use same commands. Please note that there are 2 commands.
first is
flasher -f -F main.bin
Following by (This is optional, only if you want to get content loaded like videos, music, maps data and few other things) which comes with new factory condition phone
please help me , my n9 is deth. I tray to install android and something in nat good.
when the command Prompt write flasher -i, I have a message
Suitable USB interface (bootloader/phonet) not found, waiting...
Found device RM-969, haedware revision 1603
NOLO version 2.3.6
Version of `sw-release` : DFL61_HARMATTAN_40,2012,21-3_PR_001
Success
I miss the field
device indentifier: (number) SNN/A)
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...)
My N9 switched off after an incoming call with a very low battery level. I plugged it into the original charger but it wouldn't turn on. I've tried holding power for some 10 seconds (many times). The white led either stays on for approx. a minute and then goes off or blinks and then goes off too (never fades in and out like it used to do). I once managed to get 'nokia' displayed but it stayed there for some 10 minutes with no sign of life.
NSU doesn't see the phone. Flasher -i does show the FW info some 45 seconds after I plug the phone but it still happens while the white led is on. Once it's off, neither -i nor -f work (waiting for the phone). My concern is that the device it only 'up' for a minute and then goes down so flasher will lose it soon after it starts. Or should I not be worried?
I only have Win7 (might be able to find a *nix in the office). Never tried Nitdroid or open mode, just inception+aegisctrl were installed about a week ago (a couple of planned reboots after that) and N9Qtweak with apkenv and a browser mod.
Any piece of advice on what to try next is highly appreciated.
