Please help me with my situations.
It is almost 1 week phone start making this problem. From beginning my phone getting boot loop. I have not root the phone. It is originally stock rom. I thought that the system get corrupted and then try to flash the phone with stock rom N7100XXUFNG4_N7100OLBFNG1_N7100DXUFND2_HOME.tar with odin.
This was my first time flashing this phone so I did not know anything about any EFS backup. After successfuly flashing the stock rom, at first I feel glad but suddenly I have got emergency call only. Then after what I have been searching and reading for almost a week, it was my IMEI 0049.
I have tried flash the stock rom again but the problem still remain. I have tried downgrade to 4.1.2 but the odin won't let me flash it. I have tried delete the EFS folder and paste the backup nv_data.bin but the IMEI 0049 still there. I don't have any service box so I can't repair my EFS from my computer. Is there any solutions I really really appreciate if and you guys can help with my problem. Thank you :good:
Did the imei in the phone match the imei on the label under the battery?
audit13 said:
Did the imei in the phone match the imei on the label under the battery?
Click to expand...
Click to collapse
Of course not, usually IMEI starts with 3***.
I know your phone has a generic imei.
What I meant is this: did the imei in the phone matched the imei on label before the problem started.
The phone was new when you got it?
audit13 said:
I know your phone has a generic imei.
What I meant is this: did the imei in the phone matched the imei on label before the problem started.
The phone was new when you got it?
Click to expand...
Click to collapse
Ops sorry, yes it was matched and the phone working perfectly normal before it getting boot loop. Can my phone still can be save without sending to samsung?
You try using nvwriter to inject the imei.
Have you tried flashing the stock rom again? I assume nd2 is the latest rom for your phone.
audit13 said:
You try using nvwriter to inject the imei.
Have you tried flashing the stock rom again? I assume nd2 is the latest rom for your phone.
Click to expand...
Click to collapse
I have not try the other version firmware yet, is it possible the wrong firmware corrupted my imei?
It is possible that the ROM flashed is too old.
I see stock ROMs here: http://www.sammobile.com/firmwares/database/GT-N7100/
audit13 said:
It is possible that the ROM flashed is too old.
I see stock ROMs here: http://www.sammobile.com/firmwares/database/GT-N7100/
Click to expand...
Click to collapse
Can you suggest me stock firmware? I am from Malaysia
I don't see firmware specifically for Malaysia. What is the original country or carrier for the phone? Where did you get the firmware that you flashed to the phone?
audit13 said:
I don't see firmware specifically for Malaysia. What is the original country or carrier for the phone? Where did you get the firmware that you flashed to the phone?
Click to expand...
Click to collapse
Well my country carrier starts with +6. I just ask my cousin to download that firmware for me since my house internet always disconnected I don't know why. I just ask him to download the latest firmware for my country.
That nvwriter guide is not for my phone. Is it work also with my phone?
Sorry, I'm not too familiar with nvwriter. I just know that some people have used it with Samsung phones.
The nv writer look promising, but it cannot read my phone cause when I select the rmnet/rndis/+dm+modem, it is only showing unknown device. Hmm my samsung usb driver already up to date.
Related
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
artorelis said:
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Ya, I was asking this question on the Omega forum and I am waiting for the right response.
Sent from my GT-N7100 using xda premium
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
joshphilips said:
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I did downgrade from v17 back to 16 since something went wrong with Poweramp but I forgot that if I selected for the efs backup or not since I (stupidly) didn't think that efs is important...:banghead:
Sent from my GT-N7100 using xda premium
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
Click to expand...
Click to collapse
Thanks for replying, I should have a backup, but it probably be the wrong one. Anyway I will go for a full stock restore since I have the firmware with me now.
Sent from my GT-N7100 using xda premium
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
Good luck.
Click to expand...
Click to collapse
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Dan Law 001 said:
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Click to expand...
Click to collapse
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
muppetmania said:
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
Click to expand...
Click to collapse
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Dan Law 001 said:
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Click to expand...
Click to collapse
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
muppetmania said:
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
Click to expand...
Click to collapse
Thanks for information, but how do I know that if the EFS is "totally" corrupt, "partially" corrupt, or not corrupt at all? In fact, I never touch the EFS in the root. Also, as I am not quite sure that if I have any previous EFS(S) backup or not, so, if possible, where does the backup(s) most likely to be found?
If you haven't taken an EFS backup yourself, then you won't have any.
I don't know the difference between corruption levels either, all I know is I've read a number of forum posts where someone has reflashed stock and their EFS data (i.e. the right IMEI number) is back. So I'd consider that to be a partial corruption. Others have flashed back to stock and it's still a bogus IMEI
Basically, flash back to stock. If it doesn't work, you'll have to take it in for repair.
UPDATE: Please read on - this information is incorrect - it is possible to recover with the correct modem flashed.
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
NOTE: The information from me in this post below is wrong
Dan Law 001 said:
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
Click to expand...
Click to collapse
It's normal your device got unrooted, yes. If your IMEI is still the same after ODIN and stock flash, then you have major issues (sorry!)
Doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What IMEI does *#06# show?
muppetmania said:
it's normal your device got unrooted, yes. If your imei is still the same after odin and stock flash, then you have major issues (sorry!)
doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What imei does *#06# show?
Click to expand...
Click to collapse
004999010640000 / 01
Dan Law 001 said:
004999010640000 / 01
Click to expand...
Click to collapse
Type 004999010640000 into Google...
Sorry man. Good luck getting it fixed.
just flash ME4 modem everything will be alright
bhasg1007 said:
just flash ME4 modem everything will be alright
Click to expand...
Click to collapse
Interesting to know - why does that work? (I don't doubt you, I just like to know why things work)
Just go through this thread http://forum.xda-developers.com/showthread.php?t=2333216
Even i had the same problem no network no imei nothing after downgrading so i just changed the modem and now everything is fine as it should be
Hello to everyone, I was wondering if anyone can help with this. I have a Galaxy Note 2 branded by an Italian company (3hg Italia). It recently received its update to Android 4.3 (update N7100XXUEML2). It was the official update OTA, the phone is not rooted and it had the stock ROM on it. The update somehow messed up my IMEI making it appear as the generic 0049 forcing me on "Emergency calls only" mode. I already tried flashing the same ROM with Odin and repeating the update with KIES, but while the updates always results successful the IMEI remains 0049. I never made a backup of the EFS folder for this phone since I haven't rooted it or flashed any different ROM on it yet. There is any chance that the phone made an automatic backup? I live in the States right now and Samsung tells me I need to ship it back to Italy to have it fixed, but that costs a lot and would take forever, and I would much prefer try to solve the problem locally. Any suggestions would be greatly appreciated, if not for any fix that I can try myself, at least some place on the West Coast that can fix the problem!
Thank you!
Lorenzo
Oh I forgot to add that because of Hardware problems I recently sent my phone to Samsung and they replaced the motherboard, which fixed the problem I was having. I don't know if that could be related!
rext said:
Oh I forgot to add that because of Hardware problems I recently sent my phone to Samsung and they replaced the motherboard, which fixed the problem I was having. I don't know if that could be related!
Click to expand...
Click to collapse
Here's solution : http://forum.xda-developers.com/showthread.php?t=2539731
phluid01 said:
Here's solution : http://forum.xda-developers.com/showthread.php?t=2539731
Click to expand...
Click to collapse
I'm afraid that fix works just if you have your actual IMEI, I instead have the generic IMEI that starts with 0049. But I will check it out! Thanks!
rext said:
I'm afraid that fix works just if you have your actual IMEI, I instead have the generic IMEI that starts with 0049. But I will check it out! Thanks!
Click to expand...
Click to collapse
Then you should simply flash another modem from here : http://forum.xda-developers.com/showthread.php?t=2044937 ... flash a custom recovery first.
phluid01 said:
Then you should simply flash another modem from here : http://forum.xda-developers.com/showthread.php?t=2044937 ... flash a custom recovery first.
Click to expand...
Click to collapse
Thank you so much! I'll take a look into it tomorrow and try it!
rext said:
Thank you so much! I'll take a look into it tomorrow and try it!
Click to expand...
Click to collapse
So I found someone nice enough to give me a hand with this situation, but still no luck yet! Here what they say:
At first glance, the EFS data on the phone was corrupt. I re-generated
that data and restored it to the phone without success.
The GSM radio itself is operational, and the firmware for it is
installed and functional. diagnostic data flows to the towers and back
to the phone but it's not reading the IMEI from the copy of
nv_data.bin contained within EFS. I've re-generated and installed
those files as well, again with no luck.
I rolled the device back to it's original factory firmware and radio
baseband, then ran through the update for the radio baseband, which
also regenerates the contents of EFS, and still no luck.
Given the situation, anyone have other suggestions?
Hi all,
I have a Bell Canada Samsung Galaxy S3 that I can't get the modem to work on. I have Philz recovery on it and have tried a few modem files but neither the wireless or the mobile carrier works.
I have tried putting cyanogenmod on it but am back on a stock ROM at this point. I am at a bit of a loss as to what to do.
The phone boots fine, looks all normal but I just can't get on the mobile network(tried multiple SIM's).
I am really hoping you can help!
Does your phone display the correct imei when you dial *#06#??
It does, it shows my IMEI with a /5 at the end.
At this point, I am running I747MVLUEMK5_I747MOYCEMK5_BMC
I also do show cellular signal but can't seem to connect. When I scan wireless networks, I pick nothing up.
Any ideas?
Thanks again!
audit13 said:
Does your phone display the correct imei when you dial *#06#??
Click to expand...
Click to collapse
Is the phone blacklisted?
I don't think so, how can I verify that? I did buy it used just over a year ago and it only broke about a month ago?
audit13 said:
Is the phone blacklisted?
Click to expand...
Click to collapse
You can check your imei here: http://www.protectyourdata.ca/check-the-status-of-your-device-in-canada/
All clean on there!
audit13 said:
You can check your imei here: http://www.protectyourdata.ca/check-the-status-of-your-device-in-canada/
Click to expand...
Click to collapse
You've had the phone for a while so I didn't think it would be blacklisted.
Since you have the 4.3 bootloader, you need to have a compatible modem and, from my experience, only the mk5 modem will work.
Did you use Odin to flash back to stock?
Yes, that is how I put the current stock firmware on it. I had cyanogenmod on it at one point...
audit13 said:
You've had the phone for a while so I didn't think it would be blacklisted.
Since you have the 4.3 bootloader, you need to have a compatible modem and, from my experience, only the mk5 modem will work.
Did you use Odin to flash back to stock?
Click to expand...
Click to collapse
I am at a loss as to why you cannot connect to a network. Which carrier do you want to connect with?
audit13 said:
I am at a loss as to why you cannot connect to a network. Which carrier do you want to connect with?
Click to expand...
Click to collapse
Hello i hope i can help i have to ran into this problem before and here is what i did to fix it.
Flash the modem using the dl from this forum
http://forum.xda-developers.com/showthread.php?t=2745607
also once you are done you will need the nv writer and the i747 dl froim teh same forum that will get you all fixed up i promise. Just follow the steps and ready the whole thing first. I looked for three days and finally resolved it with Larrys help
scoeas1982 said:
Hello i hope i can help i have to ran into this problem before and here is what i did to fix it.
Flash the modem using the dl from this forum
http://forum.xda-developers.com/showthread.php?t=2745607
also once you are done you will need the nv writer and the i747 dl froim teh same forum that will get you all fixed up i promise. Just follow the steps and ready the whole thing first. I looked for three days and finally resolved it with Larrys help
Click to expand...
Click to collapse
Is the i747 modem compatible with the i747m?
HI,
I have a S3 with a good IMEI but need to change the board due to bad signal. I have tried everything reflashing checking my imei everything is ok. Can I buy a bad imei unlocked board and change the imei on it to my imei number.
blainville10 said:
HI,
I have a S3 with a good IMEI but need to change the board due to bad signal. I have tried everything reflashing checking my imei everything is ok. Can I buy a bad imei unlocked board and change the imei on it to my imei number.
Click to expand...
Click to collapse
Have you tried flashing a different modem?
I would think I'd just need to flash my backup nv file that a backed up. But I've heard that the old imei may come back after a while.
blainville10 said:
I would think I'd just need to flash my backup nv file that a backed up. But I've heard that the old imei may come back after a while.
Click to expand...
Click to collapse
You didn't answer my question. Flashing a modem might save you all this trouble.
As for playing with IMEI, it's never a good idea and guides are being removed everywhere due to being illegal in some places.
Flash you mean with a jtag or flash like installing a rom with a program. Ive flashed roms through usb and I would know how to flash my nv file on another board
well if I cant change the imei forget it than
blainville10 said:
Flash you mean with a jtag or flash like installing a rom with a program. Ive flashed roms through usb and I would know how to flash my nv file on another board
Click to expand...
Click to collapse
blainville10 said:
well if I cant change the imei forget it than
Click to expand...
Click to collapse
By flash, I mean in recovery mode. I suggest you start reading on how to do it.
Changing the IMEI is possible but will be hard to find a good guide on how to do it.
BWolf56 said:
By flash, I mean in recovery mode. I suggest you start reading on how to do it.
Changing the IMEI is possible but will be hard to find a good guide on how to do it.
Click to expand...
Click to collapse
I have flashed custom roms in recovery mode but still doesnt solve my problem. What are you suggesting I should flash in recovery mode. Maybe a link
blainville10 said:
I have flashed custom roms in recovery mode but still doesnt solve my problem. What are you suggesting I should flash in recovery mode. Maybe a link
Click to expand...
Click to collapse
Searching is cool
Directly from the stickied: [MODEM] Complete Modem List for both I747U & I747M
BWolf56 said:
Searching is cool
Directly from the stickied: [MODEM] Complete Modem List for both I747U & I747M
Click to expand...
Click to collapse
I had done that lol and didn't work. I did solve my problem though. I read nv file from another board with nv-reader-writer and replaced imei with mine and works. I guess the nv file was corrupt.
Hey guys,
I've been trying to unlock my phone for a few days now. Long story short, I moved from Canada to Japan and now I want to unlock my S3 to use a Japanese SIM.
I bought an unlock code from eBay. I was previous running cyanogenmod but then I was told that rooting will cause issues, so I unrooted my phone after an unsuccessful SIM unlock attempt. (wiped the phone, installed stock TW)
Even after unrooting I still had issues, and was given directions for the Service mode. That did not work either. I have tried many different methods and troubleshooting tips and nothing seems to have worked.
Here are some screenshots of the debug mode, my phone details, and a simple root checker app I installed.
puu.sh/dPN0p.png
Here are some specs: SGH-i747m Samsung Galaxy S3 on Bell running official firmware 4.4.2
Thanks for reading, and I really hope someone can help ;_;
Does your phone display the correct imei as the one you provided to the unlocker? The imei using the dial pad is the same as the imei on label attached to the phone?
audit13 said:
Does your phone display the correct imei as the one you provided to the unlocker? The imei using the dial pad is the same as the imei on label attached to the phone?
Click to expand...
Click to collapse
Yes it displays the same IMEI on the label of the phone, and when using *#06# on the dial pad.
Despite my flashing back to stock, multiple sellers I have been through on eBay believe my phone is still rooted. One of my friends believed the people on eBay are at fault.
I then bought a code from a somewhat reputable looking website (cellunlocker.net) and received the exact same code. They had provided some additional troubleshooting methods but they did not work.
So it just won't accept the code or the prompt to enter the code doesn't appear on the screen?
audit13 said:
So it just won't accept the code or the prompt to enter the code doesn't appear on the screen?
Click to expand...
Click to collapse
The prompt appears on screen no problem. It won't accept the code. Please refer to the screenshots I posted in the OP (the puu,sh link)
Is there some extra step I can do to get my phone back to normal? I thought just flashing stock and wiping data/cache would do it but I'm still having problems and I can't figure them out.
I'm aware downgrading firmware is out of the question, but I really have no options left.
I haven't technically activated the Japanese SIM card yet. Could that be an issue?
Did you restore stock using Odin and firmware from sammobile.com?
Don't attempt to downgrade if you have a 4.4.2 bootloader as that could brick your phone.
audit13 said:
Did you restore stock using Odin and firmware from sammobile.com?
Don't attempt to downgrade if you have a 4.4.2 bootloader as that could brick your phone.
Click to expand...
Click to collapse
Yes I grabbed firmware from sammobile and flashed with Odin. I made sure to match the last four digits in the baseband of my phone which is FNH2 so I downloaded this one from sammobile
sammobile /firmwares/download/34795/I747MVLUFNH2_I747MOYCFNH2_BMC.zip/
On the Odin "Downloading..." screen, my warranty bit is 1. Could that be causing the issue?
If so how do I fix that
The warranty bit will not prevent your from unlocking the phone. When a phone is shipped, the warranty bit is set at 0. If a person flashes any non-Samsung approved software, it will change the warranty bit from 0 to 1. It cannot be reset to 0.
When flashing with Odin, I prefer 3.07. So you are just unzipping the file and flashing the tar.md5 file in PDA section? Try again but only check F reset time. Once you see reset in the status window, remove the usb cable, remove the battery, boot into recovery, do a factory wipe, and reboot.
audit13 said:
The warranty bit will not prevent your from unlocking the phone. When a phone is shipped, the warranty bit is set at 0. If a person flashes any non-Samsung approved software, it will change the warranty bit from 0 to 1. It cannot be reset to 0.
When flashing with Odin, I prefer 3.07. So you are just unzipping the file and flashing the tar.md5 file in PDA section? Try again but only check F reset time. Once you see reset in the status window, remove the usb cable, remove the battery, boot into recovery, do a factory wipe, and reboot.
Click to expand...
Click to collapse
Still no luck unfortunately ;_;
Blah. Might just sell this phone and buy a Japanese one.
The only other thing I can think of is a corrupt EFS folder.
Did you try re-injecting the imei?
audit13 said:
The only other thing I can think of is a corrupt EFS folder.
Did you try re-injecting the imei?
Click to expand...
Click to collapse
First time I've ever heard of that. Backup/restore?
I just did a quick google search and couldn't find a solid guide. Did you have a certain process in mind?
I appreciate all of your help.
http://forum.xda-developers.com/showthread.php?t=1804117
audit13 said:
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
Thank you for providing the guide. Unfortunately it's still not working. I uploaded a video just in case that might help, I also have to get a refund from an unlock website, lol.
https://www.youtube.com/watch?v=anrfCgMvBrw&feature=youtu.be
This is really weird as it looks like you are doing everything right.
audit13 said:
This is really weird as it looks like you are doing everything right.
Click to expand...
Click to collapse
Then you can understand why I am incredibly frustrated, hahaha.
It's cool. I just ended up buying a Japanese phone.
Thank you for all your help, hopefully no one else runs into thee issues in the future