hallo i bought the note 4 n910f before 1 week and i would like to ask why i can not flash any rom with odin exept the german. with the other roms alwais fail or stuck to hidden.
anyone;;;
ADRIKOS22 said:
anyone;;;
Click to expand...
Click to collapse
hey there to root your Note 4 smn910f you first go to settings/security and then you will see a V behind reactivation deactivate this
after that's done connect to odin and flash cf root
you will see that it will not fail
i dont want to root yet i just want to change official rom and i can't flash via odin
it says when odin write hidden.img.ext4 volume size is too big 81920<184320
Can I ask which firmware you are trying to flash? Is it for the 910f if it's for a different variant that will probably be why
I have the German and I want to flash the Greek I downloaded them from sam mobile for the n910f
just came across the same issue something is messed with hidden partition image size, the default partition size is smaller whereas the the img file on the odin file is much bigger
bala_gamer said:
just came across the same issue something is messed with hidden partition image size, the default partition size is smaller whereas the the img file on the odin file is much bigger
Click to expand...
Click to collapse
Got the same problem today, cant flash any rom other than the latest UK (BTU) When trying to flash any other rom I get this message. Any idea how to fix it?
Some serious problem with Odin flashing the n910f. I have just gone through a night of torment, having tried flashing the newest firmware and getting a failure due to the hidden partition problem mentioned above.
Originally, my firmware was on n910fxxu1anj4. I flashed n910fxxu1ank6, the flash failed on flashing the hidden partition with:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image
and the phone was stuck in a bootloop on the first screen with the text “Note 4”.
Then even with wipe, restore of backup etc the phone wouldn't boot.
Flashed n910fxxu1ank5, same failure, didn't record the numbers, couldn't get it to boot in no way...
Flashed the original n910fxxu1anj4, flash failed also on the hidden partition with:
Volume Size is too big 81920 < 471040
Stuck in bootloop, but upon reflash of CWM recovery and cache and data clean, the phone booted, and I was able to restore a backup which works fine now...
However there must be some serious problem.
Anyone have an idea what this is?
--
白い熊
I think we need a correct PIT file for each firmware maybe ?
ADRIKOS22 said:
hallo i bought the note 4 n910f before 1 week and i would like to ask why i can not flash any rom with odin exept the german. with the other roms alwais fail or stuck to hidden.
Click to expand...
Click to collapse
From what I have gathered on some of the models is that the only firmware that you can flash to your phone are the ones made for the CSC of your phone. Navigate to system/csc then look at the different CSC files in that folder. Those are the only ones I can flash on my H model anyways.
CodeNameRedNeck said:
From what I have gathered on some of the models is that the only firmware that you can flash to your phone are the ones made for the CSC of your phone. Navigate to system/csc then look at the different CSC files in that folder. Those are the only ones I can flash on my H model anyways.
Click to expand...
Click to collapse
I had Swedish firmware with CSC NEE and could flash a firmware with CSC BTU. But I cant flash back the NEE firmware again. And looking at the hidden.img.ext4 and cache.img.ext4 in the only firmware I can flash it has the smallest. All the other firmwares have bigger hidden and cache files. So I think the phone needs to flashed with re-partition checked in Odin and that is not possible without the correct PIT file. I am relly tired of this phone, Samsung has made it too complicated to flash firmwares
easycure1974 said:
I had Swedish firmware with CSC NEE and could flash a firmware with CSC BTU. But I cant flash back the NEE firmware again. And looking at the hidden.img.ext4 and cache.img.ext4 in the only firmware I can flash it has the smallest. All the other firmwares have bigger hidden and cache files. So I think the phone needs to flashed with re-partition checked in Odin and that is not possible without the correct PIT file. I am relly tired of this phone, Samsung has made it too complicated to flash firmwares
Click to expand...
Click to collapse
Have you tried using Kies to do a firmware upgrade and initialization? When you plug your phone in Kies may warn you that it doesn't support your phone but you can still do it. You may be better off just leaving it alone though.
CodeNameRedNeck said:
Have you tried using Kies to do a firmware upgrade and initialization? When you plug your phone in Kies may warn you that it doesn't support your phone but you can still do it. You may be better off just leaving it alone though.
Click to expand...
Click to collapse
Yes tried that but with no luck, seems I am stuck with my BTU firmware. It gets the same error message on the phone "size is too big" and got a new error message on the phone [99] eMMC write fail: HIDDEN
Guys I tried flash latest Sweden and have same problem size too big and ext4 failed,then I flash Philz recovery and voila phone booted everything its ok!!!
Ogy77 said:
Guys I tried flash latest Sweden and have same problem size too big and ext4 failed,then I flash Philz recovery and voila phone booted everything its ok!!!
Click to expand...
Click to collapse
What was your original software? Could root have messed this up? Before rooting I flashed the BTU and DBT and NEE firmwares without problem. But then staying at BTU for some weeks and then rooted. And after that I can flash no other firmware. Trying to restore the phone to the NEE firmware as I am going to sell the phone.
Any more input on this? I did the same as Ogy77 and sure the phone boots but I got some strange crashes and did a factory reset and flashed back the stock recovery. So it boots but the CSC is gone as the cache.img.ext not is flashed so no OTAs will work as Kies does not regonize the phone with a firmware witout CSC?
I have the same problem, Im using xnote as i cant flash my vodafone UK stock rom
I was stuck in a bootloop but flashed twrp and installed xnote again as it was stored on my sd card luckily! I would like to know how to flash back to stock
I have same problem. I have a open 910F and get the same error on odin file size is too big. What can i do?
Related
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Robbbie said:
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2507403 flash this with cwm or twrp should work
jaythenut said:
http://forum.xda-developers.com/showthread.php?t=2507403 flash this with cwm or twrp should work
Click to expand...
Click to collapse
Hello thanks for replying.
Only problem is I cannot get into cwm or twrp. Any advice on what I can do to try to get CWM or twrp working? I can flash with ODIN. But with the CWM I tried it still just boot loops and does not allow me to get into recovery.
Thank in advanced.
Robbbie said:
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Click to expand...
Click to collapse
Same Issue here. I tried to install the 4.4.2 N9005XXUENA6_N9005OXXENA5_N9005XXUENA2 update on my Note 3 via odin 3.09.
Got an ext4 update failed error.
After this, the phone's bricked and is stuck on the Kies Recovery Screen. I tried to go into recovery mode in Kies, but it says this model does not have initialization.
I tried installing a 4.3 N9005XXUDMK3_N9005TNLDMK1_N9005XXUDMK2, but again failed. Download mode shows SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
Can someone please guide me to unbrick my phone?
I don't know what ROM I was on initially. It was the stock ROM that came with the phone.
I dont have CWM and TWRM installed.
Robbbie said:
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Click to expand...
Click to collapse
Got this response from MrAndroid12 in another thread I'd started:
"This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine."
I don't know how to add a .pit file though.
I am certain the bootloops are because it flashed the new bootloader. I think your best option is to wait for a dev like indie to release Omega V7 and try to flash that through Odin.
Or if you can extract the different partitions from the original thread you can try push them one by one with Odin.
hallydamaster said:
I am certain the bootloops are because it flashed the new bootloader. I think your best option is to wait for a dev like indie to release Omega V7 and try to flash that through Odin.
Or if you can extract the different partitions from the original thread you can try push them one by one with Odin.
Click to expand...
Click to collapse
It is the bootloader yes. But it NEEDS the bootloader to be able to boot in to KitKat. And there is no downgrading once you've installed the new BL.
Best option is to re-flash via ODIN again and not wait 2 weeks for a Dev to modify a custom ROM...
Solution
Here is the solution:
http://forum.xda-developers.com/showpost.php?p=49426283&postcount=14
m1ndst0rm said:
Here is the solution:
http://forum.xda-developers.com/showpost.php?p=49426283&postcount=14
Click to expand...
Click to collapse
Works thanks
Sent from my SM-N9005 using XDA Premium 4 mobile app
My Note 4, SM-N910F was delivered with Nordic software (NEE). As Samsung are lazy and has not bothered to update the Swedish software i flashed the UK (BTU) software and rooted and have using it some weeks. Today I wanna go back to NEE software.
But when trying to flash it using Odin 3.10 it fails and says FAIL (Ext4) and and on the phone the error message is "Volume Size is too big 81920 < 20 4000 ODIN : invalid ext4 image
Have after that tried flashing diffrent firmwares for the SM-N910F but all fails with the same message. The only firmware I can flash is the BTU one. Anyone got a clue how to fix this?
easycure1974 said:
My Note 4, SM-N910F was delivered with Nordic software (NEE). As Samsung are lazy and has not bothered to update the Swedish software i flashed the UK (BTU) software and rooted and have using it some weeks. Today I wanna go back to NEE software.
But when trying to flash it using Odin 3.10 it fails and says FAIL (Ext4) and and on the phone the error message is "Volume Size is too big 81920 < 20 4000 ODIN : invalid ext4 image
Have after that tried flashing diffrent firmwares for the SM-N910F but all fails with the same message. The only firmware I can flash is the BTU one. Anyone got a clue how to fix this?
Click to expand...
Click to collapse
What is the Android version of currently installed firmware (BTU)?
And what is the Android version of the firmwares your are attempting install?
And how did you flash the BTU on your device in the first time? With or without the PIT file?
vndnguyen said:
What is the Android version of currently installed firmware (BTU)?
And what is the Android version of the firmwares your are attempting install?
And how did you flash the BTU on your device in the first time? With or without the PIT file?
Click to expand...
Click to collapse
The one currently installed is ANK4 and I have tried ANK5 and ANK6 firmware as well as the ANJ4, the one the phone was delivered with. But all but the ANK4 fails with the same message. And the bin size in Odin is all bigger for the ones that fails. The ANK4 is the smallest.
And I flashed it with Odin but with no PIT file as that is normally not needed and there are no one available.
Hello,
I've experienced the same issue as you flashing the UK O2 Lollipop version. I fixed it by first flashing the ROM until it comes up with the error message then reboot into download mode again and flash (All samsung recovery tar)
Not sure if I can post a link to the file!!
This worked for me. I hope it works for you too.
Regards
thecrater said:
Hello,
I've experienced the same issue as you flashing the UK O2 Lollipop version. I fixed it by first flashing the ROM until it comes up with the error message then reboot into download mode again and flash (All samsung recovery tar)
Not sure if I can post a link to the file!!
This worked for me. I hope it works for you too.
Regards
Click to expand...
Click to collapse
Hi, I have the same problem with O2 version. I don't quite understand how you fixed it? When the error message comes up in ODIN you unplugged the phone then put phone into download mode again and flash with "All Samsung recovery tar" Is this a separate file? Where did you get it?
Thanks
Paul
---------- Post added at 11:53 AM ---------- Previous post was at 11:12 AM ----------
pmlfrew said:
Hi, I have the same problem with O2 version. I don't quite understand how you fixed it? When the error message comes up in ODIN you unplugged the phone then put phone into download mode again and flash with "All Samsung recovery tar" Is this a separate file? Where did you get it?
Thanks
Paul
Click to expand...
Click to collapse
Never mind figured it out. Got the file and flashed with it and Im up and runnnug again... phew
Hey there so i found on Sammobile the 5.0 version of the UK (Vodafone)
I downloaded it and tried to flash via Odin and it failed.
It fails at the last part hidden.img (FAIL) Size.
I tried other USB ports, Updated Samsung drivers , Reboot PC
I read somewhere about a PIT file (which unfortunately i don't have.
I had root but now i cannot enter recovery since its stuck in a boot loop..
Is there anything else i can do?
cyphex said:
Hey there so i found on Sammobile the 5.0 version of the UK (Vodafone)
I downloaded it and tried to flash via Odin and it failed.
It fails at the last part hidden.img (FAIL) Size.
I tried other USB ports, Updated Samsung drivers , Reboot PC
I read somewhere about a PIT file (which unfortunately i don't have.
I had root but now i cannot enter recovery since its stuck in a boot loop..
Is there anything else i can do?
Click to expand...
Click to collapse
Is your phone branded to Vodafone UK? You can flash the POLAND firmware if not.
Joku1981 said:
Is your phone branded to Vodafone UK? You can flash the POLAND firmware if not.
Click to expand...
Click to collapse
Thanx but for some reason i re-flashed a custom recovery via odin and it booted up into the new rom Lollipop.
Thank you for your reply
Could you please explain which custom recovery did you boot? I seem to have the same problem. Thanks.
Hello,
I have a note 4 SM-N910F and I'm from Belgium.
I have upgraded succesfully my note to 5.01 with a Netherlands firmware N910FXXU1BOC3_N910FTPD1BOC1_TPD. However in this firmware the APN for ZiGGO was hardcoded and I couldn't remove it.
In the mean time a new 5.01 for Belgium has become available N910FXXU1BOC5_N910FPRO1BOC1_PRO. But when I try to flash my note with Odin 3.09 I always end up with an error being hidden.img to big and an EXT4 size fail error. Then I need to flash back to the previous firmware to make it work again.
I redownloaded the firmware to make sure (MD5 was correct) and tried to erase the Note before flashing but with the same flashing error.
Any suggestions ?
Thank you
Bump
toxictoy said:
Hello,
I have a note 4 SM-N910F and I'm from Belgium.
I have upgraded succesfully my note to 5.01 with a Netherlands firmware N910FXXU1BOC3_N910FTPD1BOC1_TPD. However in this firmware the APN for ZiGGO was hardcoded and I couldn't remove it.
In the mean time a new 5.01 for Belgium has become available N910FXXU1BOC5_N910FPRO1BOC1_PRO. But when I try to flash my note with Odin 3.09 I always end up with an error being hidden.img to big and an EXT4 size fail error. Then I need to flash back to the previous firmware to make it work again.
I redownloaded the firmware to make sure (MD5 was correct) and tried to erase the Note before flashing but with the same flashing error.
Any suggestions ?
Thank you
Click to expand...
Click to collapse
toxictoy said:
Hello,
I have a note 4 SM-N910F and I'm from Belgium.
I have upgraded succesfully my note to 5.01 with a Netherlands firmware N910FXXU1BOC3_N910FTPD1BOC1_TPD. However in this firmware the APN for ZiGGO was hardcoded and I couldn't remove it.
In the mean time a new 5.01 for Belgium has become available N910FXXU1BOC5_N910FPRO1BOC1_PRO. But when I try to flash my note with Odin 3.09 I always end up with an error being hidden.img to big and an EXT4 size fail error. Then I need to flash back to the previous firmware to make it work again.
I redownloaded the firmware to make sure (MD5 was correct) and tried to erase the Note before flashing but with the same flashing error.
Any suggestions ?
Thank you
Click to expand...
Click to collapse
Make sure you are using the latest ODIN version, which is 3.10.6 and run ODIN as administrator.
I'm using latest Odin in administrator mode but with same result (hidden file failed size too big ext4 error). I see in the forum lot's of people face the same problem and they solve it by integrating it with a new PIT file in Odin. However I can't find the correct PIT file for this one..
Cheers
toxictoy said:
I'm using latest Odin in administrator mode but with same result (hidden file failed size too big ext4 error). I see in the forum lot's of people face the same problem and they solve it by integrating it with a new PIT file in Odin. However I can't find the correct PIT file for this one..
Cheers
Click to expand...
Click to collapse
Flash stock rom and when finish then flash custom recovery twrp and phone booted normally.
@toxictoy
Did you find how solve your problem?
Because I have the same problem like you. The only different that my note4 have region code BTU.
I was able to find online a PIT file for the note 4. I used this to flash the new rom and this worked perfectly.
Could you give me a link to this PIT file ?
Hi guys.
So i have an Note 3 with HongKong firmware that i want to flash new international/europe firmware as it is not working on europe sim card(i think it will solve the problem...).
The firmware that is installed on it is N9005ZHUENB5 so i thought aha then this is the Hong Kong 16GB version that have flashing problem. But then i found out that the phone is 32 GB and not 16 so it can not be the Hong Kong 16 GB version but it has for some reason the Hongkong firmware on it.
The IMEI number under the batteri is matching the IMEI nr android is showing, but the serial number is not matching.
The weird part is phone INFO app shows this:
SN under batteri: Made in Vietnam
SN andorid show: Made in CHINA
Even weirder:
imei.info is giving me N900 Galaxy Note 3 as Model????
This has made me being carefull falshing it and i am asking you guys to advice me before i start flashing any new firmware. I have rooted and done EFS and pit file backup in case i screw it up.
What do you guys think, will it be safe for me to just download a europe firmware and flash it with odin?
Download and run Phone Info from Play store and post screenshots .
This is the info from Phone info app(attached)
This is not a new phone is it as i see warranty void Knox 0x1 .
Looks like a previous owner has flash a rom .
Thanks for feedback JJEgan.
I have rooted the phone so maybe therefore? The phone has android 4.4.2, however i believe this should not have anything to do with what i want to do. I can flash 4.4.2 or flash 5.0 via odin, but just want advice before i do that.
Thanks
The_Kurd said:
Thanks for feedback JJEgan.
I have rooted the phone so maybe therefore? The phone has android 4.4.2, however i believe this should not have anything to do with what i want to do. I can flash 4.4.2 or flash 5.0 via odin, but just want advice before i do that.
Thanks
Click to expand...
Click to collapse
Well at least you're 32GB - not sure why only HK phones seem to have a 16GB model. You're right to be cautious - there seems to be partition differences also, but if you search for a EU version of the PIT file for v5 Android you will be prepared in case the Odin flash fails. I'd also get SuperSU zip file on your extSDCard and an Odin flash version of TWRP or CWM - untick the Reboot option, flash the firmware you want, (Wait for it to finish completely - it will sit for a while then let you know it is done) then Reset, untick the Reboot again, then flash the Recovery. Reboot phone into Recovery and flash the SuperSU file and restart.
All being well you should boot into the stock firmware and do the set up. Then you can flash whatever ROM you want in Recovery.
If it DOESN'T work, Search for how to fix, and if you can't find what you need, ASK, don't just go playing...
Thanks @Journyman16
Result:
Tried to flash with lolipop stock firmware and my backed up pit file( from andoird 4.4.2))--->Fail/brick with Volume size is too big 4620288 < 4718592 and invalid ext4 image error(Odin setting Auto-reboot and F. reset used)
Tried to flash with lolipop stock firmware and with pit file CSB_signed_HLTE_EUR_OPEN_32G_0805 --->Fail/brick with Volume size is too big 4620288 < 4718592 and invalid ext4 image error(Odin setting Auto-reboot and F. reset used)
Tried to flash with stock HK kitkat 4.4.2 firmware without PIT file---> Success and i am back to stock firmware but that did not solve my call/SIM and wrong serial number
Maybee i should donwload an europe 4.4.2 firmware and try flash with that?
The_Kurd said:
Thanks @Journyman16
Result:
Tried to flash with lolipop stock firmware and my backed up pit file( from andoird 4.4.2))--->Fail/brick with Volume size is too big 4620288 < 4718592 and invalid ext4 image error(Odin setting Auto-reboot and F. reset used)
Tried to flash with lolipop stock firmware and with pit file CSB_signed_HLTE_EUR_OPEN_32G_0805 --->Fail/brick with Volume size is too big 4620288 < 4718592 and invalid ext4 image error(Odin setting Auto-reboot and F. reset used)
Tried to flash with stock HK kitkat 4.4.2 firmware without PIT file---> Success and i am back to stock firmware but that did not solve my call/SIM and wrong serial number
Maybee i should donwload an europe 4.4.2 firmware and try flash with that?
Click to expand...
Click to collapse
I think when you use a PIT for such things you need to tick the re-partition box - if you're going to try it, read up on it. I haven't done it since I had an S3. Mess up the PIT process and it's a bit of work to get the phone working again.
I'm puzzled about the serial number thing - even if the main board was changed, that wouldn't explain it because the IMEI would also change AFAIK. I wonder if the wrong S/No might be the reason you have the SIM/Call issue?
You could now try a factory reset. See if it changes anything. Other than that, research about EFS repair/restore.
You DID have a backup before all this... right?
Fingers-crossed
Journyman16 said:
I think when you use a PIT for such things you need to tick the re-partition box - if you're going to try it, read up on it. I haven't done it since I had an S3. Mess up the PIT process and it's a bit of work to get the phone working again.
I'm puzzled about the serial number thing - even if the main board was changed, that wouldn't explain it because the IMEI would also change AFAIK. I wonder if the wrong S/No might be the reason you have the SIM/Call issue?
You could now try a factory reset. See if it changes anything. Other than that, research about EFS repair/restore.
You DID have a backup before all this... right?
Click to expand...
Click to collapse
Ok guys:
I have one bad news and one good news
The good news: I managed to flash with Poland firmware after advice from @FeralFire(really appreciated, thanks) following his guide here: http://forum.xda-developers.com/showthread.php?t=2613374&page=13 I believe i can now flash any firmware as it is now international pit and firmware
The bad news: I can still not call/sms only data is working, and the serial number is stil diffrent then the one under the batteri. The IMEI is correct though. So i have now ruled out that it was something with HongKong firmware as it seems like this problem is not related to which firmware is in use. I have also tried with Region lock away app but no luck
I do have backup of my EFS and pit file, but the problem is this phone has had difrent serial number from begining so no help from EFS backup i believe?
I will try to digg some more in to EFS repaire threads here on xda and see what i can find, but any threads you guys advice or other tips i can try?
Again thank you for helping me out here: )
Dont remember the solution ( probably efs) look on S2 forum as their where a number of wrong serial posts that may give you a clue .