Related
So I've flashed my phones a couple of times without backing up the EFS folder (a mistake I will not make again) and my question now is if the warranty covers an IMEI number change that occured when I flashed it.
I have not rooted the phone and have also only flashed official firmwares (some leaks) but not custom Roms.
IMEI number: 00499901064000
You normally shouldn't post your IMEI number anywhere online, but I'm pretty sure that one is the generic samsung one you get if your efs is corrupt (or sometimes you get no imei at all)
Back to your actual question: I'm not sure if the warranty covers that exactly, but what you can do (assuming you have no signal etc) is claim you were updating your phone via KIES and when it booted you had no signal etc, that's what I did when my aunt's EFS was corrupted during an unlock and Orange swapped it out for a new one.
Try GSII_Repair app from market
If that works than you are lucky
if it doesn't then check the flash counter if its zego or more(if you had rooted before sometime) and take it to Samsung and say happened while updating through kies
Sent from my GT-I9100 using Tapatalk 2 Beta-5
D3_ said:
You normally shouldn't post your IMEI number anywhere online, but I'm pretty sure that one is the generic samsung one you get if your efs is corrupt (or sometimes you get no imei at all)
Back to your actual question: I'm not sure if the warranty covers that exactly, but what you can do (assuming you have no signal etc) is claim you were updating your phone via KIES and when it booted you had no signal etc, that's what I did when my aunt's EFS was corrupted during an unlock and Orange swapped it out for a new one.
Click to expand...
Click to collapse
Ah man I went to the store and asked about it (because I wasn't able to make calls from my phone) and we just switched out sim cards and it started working again.
But the guy I was talking to was actually about to send it in for repair but we decided to try out the SIM card switch first.
For future reference, warranty will NOT cover the phone if the IMEI has changed/is corrupt. Had this issue exactly as you had, flashed an official Samsung firmware release on the phone (without backing up EFS >.<) and lost the IMEI altogether. Samsung would not cover the phone under warranty regardless of the fact it was un-rooted/official firmware.
NiTi9 said:
Ah man I went to the store and asked about it (because I wasn't able to make calls from my phone) and we just switched out sim cards and it started working again.
But the guy I was talking to was actually about to send it in for repair but we decided to try out the SIM card switch first.
Click to expand...
Click to collapse
But the IMEI is still corrupted, isn't it? If the SIM change brought it back THAT would be amazing! ;-)
brittonberkan said:
But the IMEI is still corrupted, isn't it? If the SIM change brought it back THAT would be amazing! ;-)
Click to expand...
Click to collapse
Yes the IMEI is still corrupt although I can now make calls and use the 3G network
BJ van Beethoven said:
For future reference, warranty will NOT cover the phone if the IMEI has changed/is corrupt. Had this issue exactly as you had, flashed an official Samsung firmware release on the phone (without backing up EFS >.<) and lost the IMEI altogether. Samsung would not cover the phone under warranty regardless of the fact it was un-rooted/official firmware.
Click to expand...
Click to collapse
Okay, thank you for a clear response
Obviously his imei was not corrupt after all, as changing the Sim fixed the problem. If hazard a guess that either the original Sim had become dislodged, or damaged. Our maybe the guy in the shop factory reset the phone as well as put the Sim in the phone. Either way, the imei in the first post is the original, you should take it down. Otherwise, maybe some clever fellow will use it to make a clone of your phone! :-(
Sent from my GT-I9100 using Tapatalk 2 Beta-5
mattisfaction said:
Obviously his imei was not corrupt after all, as changing the Sim fixed the problem. If hazard a guess that either the original Sim had become dislodged, or damaged. Our maybe the guy in the shop factory reset the phone as well as put the Sim in the phone. Either way, the imei in the first post is the original, you should take it down. Otherwise, maybe some clever fellow will use it to make a clone of your phone! :-(
Sent from my GT-I9100 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
No it's not, it's a generic IMEI that generates when your EFS is corrupted. You will still be able to use the phone using this IMEI number.
mattisfaction said:
Obviously his imei was not corrupt after all, as changing the Sim fixed the problem. If hazard a guess that either the original Sim had become dislodged, or damaged. Our maybe the guy in the shop factory reset the phone as well as put the Sim in the phone. Either way, the imei in the first post is the original, you should take it down. Otherwise, maybe some clever fellow will use it to make a clone of your phone! :-(
Sent from my GT-I9100 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
That can't be since it doesn't match with the IMEI number that is under the battery (which the shopkeeper explained was my real IMEI number). I think it's a generic one.
The IMEI you posted is the standard wrong IMEI usually due to damaged EFS .
The legal IMEI is the one under the battery .
jje
So, a sad and dumb tale. I rooted my phone and through the process have erased my nv_data.bin and subsequent files from the efs folder. I was dumb enough to have not created a backup of the folder before losing these files. My IMEI is now a 0/1. Now I've searched all over for a solution but there apparently have been some people claiming it can be solved but noone has ever posted a guide to how to do this. Skeptical over a fix existing for this problem, i have called in to my carrier and claimed i would like to exchange phones citing that my current S3 is getting very slow. As my device is within the return time, it was accepted. However, if a fix is possible i would like to cancel the work order and keep my current one.
So, my 2 questions are basically this;
can anyone tell me if this problem is fixable, and if so, tell me how .
secondly, i have heard of people with the same problem returning their devices for new ones. I would like to know what was the carriers return policy and if they ever called back when they found your phone had no IMEI.
Unfortunately it doesn't look like there's currently a fix, did you only root it or did you root then flash stuff as well? as far as I've heard just rooting shouldn't have made you lose the IMEI, but I'm no expert.
---------- Post added at 09:56 PM ---------- Previous post was at 09:09 PM ----------
you could try this http://forum.xda-developers.com/showthread.php?t=1308546
or search hc ktool in play store to see if either of those methods work, but since it's already corrupt it probably wont....hope it works!
As far as for returning, is your flash counter 0? if not and you un-root the phone theres really no way for them to know you messed with it and they won't care about anything and will replace it.
i didnt flash anything i dont think. i installed supersu using cwm...
so does anyone have any stories about returning their phones with broken IMEI's?
xalinhoe said:
So, a sad and dumb tale. I rooted my phone and through the process have erased my nv_data.bin and subsequent files from the efs folder. I was dumb enough to have not created a backup of the folder before losing these files. My IMEI is now a 0/1. Now I've searched all over for a solution but there apparently have been some people claiming it can be solved but noone has ever posted a guide to how to do this. Skeptical over a fix existing for this problem, i have called in to my carrier and claimed i would like to exchange phones citing that my current S3 is getting very slow. As my device is within the return time, it was accepted. However, if a fix is possible i would like to cancel the work order and keep my current one.
So, my 2 questions are basically this;
can anyone tell me if this problem is fixable, and if so, tell me how .
secondly, i have heard of people with the same problem returning their devices for new ones. I would like to know what was the carriers return policy and if they ever called back when they found your phone had no IMEI.
Click to expand...
Click to collapse
I read about someone who did this on the AOKP thread over on rootzwiki. He said he unrroted & returned it for another no problem, he had T mobile.
My dumb ass question for the day is this. What does it effect when your IMEI is erased? Does the phone still work or is it not reading the sim? I'm very gun shy to flash anything else until someone can figure out what is causing this issue...
im with a canadian carrier. virgin mobile. a subsidiary under bell mobile. so hopefully its similar case.
the imei is the number that the carriers recognize in order for them to allow u into their services. without a confirmed imei number on their network, u cannot call, text, or anything related to the mobile network. the phone still functions fine.
xalinhoe said:
im with a canadian carrier. virgin mobile. a subsidiary under bell mobile. so hopefully its similar case.
the imei is the number that the carriers recognize in order for them to allow u into their services. without a confirmed imei number on their network, u cannot call, text, or anything related to the mobile network. the phone still functions fine.
Click to expand...
Click to collapse
Ouch... That's pretty much what I figured :-( I just backed mine up to my external sd card.
androholic said:
Ouch... That's pretty much what I figured :-( I just backed mine up to my external sd card.
Click to expand...
Click to collapse
its an ongoing issue so far happening with att and tmobile sgs 3s( http://forum.xda-developers.com/showthread.php?p=28710945. backing up the /efs folder wont be of any help either if you do lose your imei as the lte sgs 3s are missing nv_data.bin in the /efs partition which contains the imei number.
something really weird happened today. I bring my IMEI broken phone around with me jus for music. but today randomly i got a bunch of texts, voicemail, and missed calls since the time my IMEI broke down. that must mean i regained access back to the mobile network somehow. when i rechecked in an hour. i did not have mobile network connectivity and my IMEI was set a 0/01 again.
maybe someone knows wth that was?
Out of curiosity, what partition does the efs folder live on? A factory reset or downloading the firmware from samsung-updates.com and flashing through Odin won't work. Forgive the ignorance. I just want to know if this applies to all S3's.
Sent from my DROIDX using xda app-developers app
oddly enough. even though i have my imei is 0/01, i randomly get connectivity to the mobiles network on occasions. this has happened a couple of times now. i received a bunch of texts and calls, and then service is gone again.
any possible explanations?
The imei number isn't in the normal efs folder. I believe some very bright devs are looking into finding it, but for now there is no way to backup the imei.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
xalinhoe said:
oddly enough. even though i have my imei is 0/01, i randomly get connectivity to the mobiles network on occasions. this has happened a couple of times now. i received a bunch of texts and calls, and then service is gone again.
any possible explanations?
Click to expand...
Click to collapse
i get data only edge and ran make and recieve text and calls
Believe it or not you can return it and play dumb and it will probably work
sent from my GSlll iphone killer
deeznutz1977 said:
i get data only edge and ran make and recieve text and calls
Click to expand...
Click to collapse
This happend to me too. My IMEI read 0 /02. Good thing I was still within the 14 day return policy. I'm not doing any modding til this IMEI mess is resolved.
Yes, this did happen to me. My IMEI = 0 and my IMEISV= 02. All works fine except data and I'm stuck on Edge. I visited two T-Mobile stores today and they were baffled, but strangely neither bothered to look at the IMEI nor for the tripped counter. I purchased my phone on 6.21.12 and will be receiving my new phone tomorrow. I'm really wanting to get back to CM9/10, but think I will now wait until there is a backup/restore for the IMEI...or, I will not use Odin and trip my counter...that is what I'm most worried about.
I have yet to see any Verizon customers with this issue, nor do I seem to have an nv_data.bin file in /efs. I did have an IMEI folder, however.
Which recovery did you guys use that lost imei. If cwm...which one?
cwalker0906 said:
Which recovery did you guys use that lost imei. If cwm...which one?
Click to expand...
Click to collapse
Not recoverable at this point. :banghead:
Sent from my SGH-T999 using xda premium
google'd all over, guess there's no solution yet =(
djricekcn said:
google'd all over, guess there's no solution yet =(
Click to expand...
Click to collapse
Not yet, but being worked on...I'll bet a fix will be out soon!
Sent from my SGH-T999 using xda premium
Recently, my line was suspended for "lost/stolen." I called and had it reactivated, but the rep couldn't tell me why it was suspended. There was no balance, I'm the account holder (family account), and there's a passcode on the account. After being asked to confirm the sim number, imei, etc., for the first time, I noticed that my imei was the generic samsung one and not my device's. I had never noticed (perhaps because I never had a reason to look) that they were mismatched. Subsequent, attempted uses of my device resulted in repeated suspensions. It now appears to be due to the generic imei (which AT&T has decided to block). I had to think back because I could not recall modifying anything that could cause such a thing; I've been on one rom for months and had not done anything other than minor theming. Then, it hit me. I had used Galaxy_S Unlock from the market (recommended by several users around here) to sim unlock it. I can confidently attribute the cause to this process because nothing else I've done could interfere with nv_data.bin (imei data in efs). Luckily, I have several EFS backups. However, to this point, I've been unsuccessful in restoring my original IMEI. There are a couple of options: continued attempts to restore original IMEI or return to stock for Samsung to fix. I hadn't quite decided what I'm going to do; my contempt for AT&T may cause me to use this opportunity to jump ship. We'll see.
For those that have used this tool, check your imei congruence (device menu + device sticker under the battery). I'm curious as to if this was just bad luck, or if other people have experienced the same thing.
UPDATE: I decided to send it off to Samsung for warranty repair (got it back 8/1/12).
Simba501 said:
Recently, my line was suspended for "lost/stolen." I called and had it reactivated, but the rep couldn't tell me why it was suspended. There was no balance, I'm the account holder (family account), and there's a passcode on the account. After being asked to confirm the sim number, imei, etc., for the first time, I noticed that my imei was the generic samsung one and not my device's. I had never noticed (perhaps because I never had a reason to look) that they were mismatched. Subsequent, attempted uses of my device resulted in repeated suspensions. It now appears to be due to the generic imei (which AT&T has decided to block). I had to think back because I could not recall modifying anything that could cause such a thing; I've been on one rom for months and had not done anything other than minor theming. Then, it hit me. I had used Galaxy_S Unlock from the market (recommended by several users around here) to sim unlock it. I can confidently attribute the cause to this process because nothing else I've done could interfere with nv_data.bin (imei data in efs). Luckily, I have several EFS backups. However, to this point, I've been unsuccessful in restoring my original IMEI. There are a couple of options: continued attempts to restore original IMEI or return to stock for Samsung to fix. I hadn't quite decided what I'm going to do; my contempt for AT&T may cause me to use this opportunity to jump ship. We'll see.
For those that have used this tool, check your imei congruence (device menu + device sticker under the battery). I'm curious as to if this was just bad luck, or if other people have experienced the same thing.
Click to expand...
Click to collapse
Hmm chainfires unlock app did say that app uses a more dangerous method, this may be why
Sent from my Sony Xperia Ion
Didn't you make a backup as it tells you of the efs?
Mine doesn't match too.
Sent from my SGH-I777 using Tapatalk 2
Odd cause my IMEI is still the same. I ran Chainfire's tool first and when that didn't work I tried the "more dangerous one"
Sent from my Nexus 7 using xda premium
I used Galaxy S Unlock too but I just checked my IMEI and it is correct. I wonder if it matters which Rom you were using when using the program.
my imei is also correct after using Galaxy_S Unlock
My IMEI # is the same. I used the GalaxySUnlock tool also. Running ShoStock 1.9.4 Siyah Kernel 2.6.9
My IMEI's match. I used Galaxy_S Unlock while on rooted, otherwise stock, I777UCKH7.
My IMEI matches too. Unlocked with the same app, and flashed I don't even remember how many ROMs/kernels/modems before and since unlocking.
I'd want to guess that your IMEI mismatch problem relates not to the unlock app itself but a subsequent flash, perhaps of a stock or stock-based ROM using Odin/Heimdall.
So 6/8 people have an intact IMEI. I suppose it was just bad luck. Glad to see that not many others are affected.
I have no problems though, constantly switch sims.
Sent from my SGH-I777 using Tapatalk 2
Biporch said:
I have no problems though, constantly switch sims.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
And neither did I, until AT&T decided to block it.
Sent from my HTC Inspire
Att and there **** lol
Since I'm thinking this was an isolated incident and the unlock tool doesn't necessarily break IMEI for everyone, maybe consider changing the name of this thread so people don't get the wrong idea
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Did the same thing to mine i spent hours on the phone with customer care and finally had to get a new sim.
BIGDADDYXXL said:
Did the same thing to mine i spent hours on the phone with customer care and finally had to get a new sim.
Click to expand...
Click to collapse
That almost makes sense except for the part where imei and sim card aren't the same.
Sent from my Nexus 7 using Tapatalk 2
Pirateghost said:
That almost makes sense except for the part where imei and sim card aren't the same.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Ya i dont know either but as soon as i got a new sim it helped. They said i was black listed.
Sent from my SAMSUNG-SGH-I777 using xda premium
Phalanx7621 said:
Since I'm thinking this was an isolated incident and the unlock tool doesn't necessarily break IMEI for everyone, maybe consider changing the name of this thread so people don't get the wrong idea
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I wouldn't exactly call 3/9 people an isolated incident.
BIGDADDYXXL said:
Did the same thing to mine i spent hours on the phone with customer care and finally had to get a new sim.
Click to expand...
Click to collapse
Band-aid solution. This problem will arise again. It's only a matter of time before AT&T's system probably blocks the new sim; the root of the problem is still there (original IMEI is not being reported). Get that fixed bro. Samsung and Mobile Tech Videos (reputable) are two options.
Hm, if AT&T somehow protected your account in some way that will override the mechanism that led to the block, I guess you'd be safe. But it sounds like they only gave you a new sim, in which case, you're still at risk in the future. I'd want to get that IMEI corrected.
Resurrecting this old thread as I was searching for an answer. I lost my IMEI code when attempting to use this app, the phone is Samsung Galaxy S locked to Orange (EE) in the UK.
Restoring the EFS files the app made reinstated the IMEI number correctly, but obviously still stuck on Orange. Tried a couple of times no dice.
drevans said:
Resurrecting this old thread as I was searching for an answer. I lost my IMEI code when attempting to use this app, the phone is Samsung Galaxy S locked to Orange (EE) in the UK.
Restoring the EFS files the app made reinstated the IMEI number correctly, but obviously still stuck on Orange. Tried a couple of times no dice.
Click to expand...
Click to collapse
You do have a galaxy s ii i777 yes?
Hi guys last week i sent my phone to be fixed due to a sound error. they said they changed the entire board so that imei number has changed. but i realized that they faked the imei number. i know that because when i checked my imei on internet, seems that its a gts8600 which is galaxy wave
now as the title i asked, does a brand new board come an imei in it or they write it themselves??
I believe the motherboard has its own generic imei number. Youll see this generic imei number instead of the shipped imei when the efs partition is formatted or corrupt. Meaning the imei that you see on your phone now is probably one that has been placed by the service center. Although what I don't understand is that why wouldn't they just input the imei no. that's mentioned underneath the battery instead.
Sent from my GT-N7100 using xda premium
was it the official Samsung service center?
bushako said:
I believe the motherboard has its own generic imei number. Youll see this generic imei number instead of the shipped imei when the efs partition is formatted or corrupt. Meaning the imei that you see on your phone now is probably one that has been placed by the service center. Although what I don't understand is that why wouldn't they just input the imei no. that's mentioned underneath the battery instead.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Here in Turkey you have to register all imei numbers to the carriers in order to use your phone. i think the generic imei wasnt registered so they needed a registered one to make it work. For the serial you mentioned about underneath the battery, i think they needed my old efs backup to replace and since they dont have that either.... but i also think and just poped up in my head right now, my old board was working fine but the sound card. they could have taken my efs from it. and that will be the first think im gonna say them on monday morning...
Glebun said:
was it the official Samsung service center?
Click to expand...
Click to collapse
of course they are not. could i complain this much if they were official. i would just give it back instead...
TheWaLeK said:
Here in Turkey you have to register all imei numbers to the carriers in order to use your phone. i think the generic imei wasnt registered so they needed a registered one to make it work. For the serial you mentioned about underneath the battery, i think they needed my old efs backup to replace and since they dont have that either.... but i also think and just poped up in my head right now, my old board was working fine but the sound card. they could have taken my efs from it. and that will be the first think im gonna say them on monday morning...
of course they are not. could i complain this much if they were official. i would just give it back instead...
Click to expand...
Click to collapse
That could explain why they added some other imei. If I'm not mistaken in Turkey they usually give you 2 weeks to register your imei before suspending it? In that case I would advice you to push the service center to place your old imei number and register your phones actual imei with the network. At least so that you don't face difficulty with updating through KIES or any other situation.
Sent from my GT-N7100 using xda premium
bushako said:
That could explain why they added some other imei. If I'm not mistaken in Turkey they usually give you 2 weeks to register your imei before suspending it? In that case I would advice you to push the service center to place your old imei number and register your phones actual imei with the network. At least so that you don't face difficulty with updating through KIES or any other situation.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
yes you are right about two weeks. my old imei number was registered. but there are some answers i need
1) what is corrupted efs? if i temper with the orijinal imei even placing my old one instaed, does the phone thinks corrupted anyway?
2) if that's so, im gonna tell them to register the new imei number that comes with the board. my present imei that im using now when i searched it from internet it seems 8600 not 9300 but also registered too.
TheWaLeK said:
yes you are right about two weeks. my old imei number was registered. but there are some answers i need
1) what is corrupted efs?
Its is the EFS folder that contains the IMEI.
if i temper with the orijinal imei even placing my old one instaed, does the phone thinks corrupted anyway?
Yes and its illegal .
The service centre should sort all the IMEI stuff not you .
jje
Click to expand...
Click to collapse
Alright, so I've looked up at least 20 solutions to my error and it seems to be a common one but none of the solutions have worked for me so far.
My phone doesn't have any bars and says emergency calls only. Before, when I booted up the phone it would have the signal for 2-3 seconds before disappearing so I could receive text messages through that, but it doesn't even do that anymore.
Things I've tried:
Wiping Dalvik Cache
Factory Reset, wiping cache, dalvik cache
Restoring the /efs folder (This just resulted in getting a generic IMEI and replacing my old one, so I think my backup is messed up but I don't have any other backups to use. Yes, I renamed nv_data.bak to nv_data.bin and same with the md5 files.)
Using someone else's efs.img to restore my own via kTool, to no avail. The IMEI is still generic.
Flashing Jellybean 4.1.2 (I'm currently on CM10.1) with SLIGHT chance. When I used 4.1.2, I could see the bars of signal (3-4) but I still could only make emergency calls, and I couldn't connect to the network.
Using this method to restore my nv_data.bin: Link
Using GSII_Repair
Using this method: I was able to complete it successfully, but I still am seeing "emergency calls only": Link
Using this method: Link
I can't find CSC since I can't dial anything except to find IMEI, but the baseband version is LS8, but in the IMEI folder the mps_code.dat file reads as XEU. Should those be matching?
Also I believe my backup EFS isn't working because the dates of nv_data.bin and nv_data.bak are the same, both dated from 2011. I didn't do all these steps in that order, but I'm not sure what to do since I don't have any other backups.
I have NOT tried wiping /system manually but I'm not sure what this would achieve and I don't know what I would flash if I did.
Please help, I'm desperate and in no financial condition to buy a new phone. Thanks to all in advance.
Flash stock rom,i tried this many times.
Sent from my GT-I9100G using xda app-developers app
arvin07143 said:
Flash stock rom,i tried this many times.
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
Sorry, I forgot to state that I already tried this too. Didn't help, and I wiped /system this time.
Alright, so the phone has gone back to letting the signal appear for a second. I'm thinking the problem is that the generic IMEI is just blocked by my carrier (I'm on T-Mobile in the USA) because I was able to test my SIM in another phone today and it was fine.
Obviously I don't expect anyone to tell me how to change my IMEI since that's illegal, but are there any more miraculous efs-restoring methods? I'm willing to do anything at this point, besides visit a service center or pitch my phone.
This will probably be my last update, sorry for bumping but I'm really hoping someone will see this and either give me a miraculous solution or tell me to give up.
I've heard from a few posts that flashing Gingerbread fixed the IMEI somehow, sadly this did not work for me. What I'm wondering now is if I take it to a service center how much it will cost, because they don't sell i9100's in the US, I bought this as an unlocked phone and it has already been rooted. Will they even attempt to fix it, and can it be done? I don't see any other option.
Someone please reply, I at least need to know if I should give up or not and if this can be fixed at all.
I'm fairly certain you're in the wrong forum. What model number from the sticker on the phone chassis under the battery ?
MistahBungle said:
I'm fairly certain you're in the wrong forum. What model number from the sticker on the phone chassis under the battery ?
Click to expand...
Click to collapse
No, it's definitely a Samsung Galaxy SII i9100 and this is the i9100 forum. My problem here is that yes, this is an i9100, which is the International version of the SII. I bought this off of eBay, used, from overseas. They don't really use this version in America (where I currently reside), we have the SGH models. Should I take this to my service provider (T-Mobile) or a Samsung service center, and will they even fix it after it's been rooted, the IMEI changed, and the fact that it's not an American phone?
They'll probably fix it but charge you an arm & a leg for it. Better off finding a local mobile repair shop with a RIFF box, will likely be much cheaper.
MistahBungle said:
They'll probably fix it but charge you an arm & a leg for it. Better off finding a local mobile repair shop with a RIFF box, will likely be much cheaper.
Click to expand...
Click to collapse
Thanks for the advice! So I'm guessing there aren't any miraculous fixes or any other methods I can try then?
There are unfortunately no miracles in technology. If you've tried all the things in OP (good job persevering) then I'm afraid it's local mobile shop as MistahBungle said.
Sent from a galaxy far, far away
About £ 20 in uk so its not that expensive really. Once you have done this bk up your efs. Good luck. :thumbup: