Looking for some guidance about this situation. Had a used HTC Aria on AT&T that I sold via ebay, worked perfect, Android 2.2 great shape. 30 + days go by and the chap who bought the phone says " out of the blue it just says no service, can't make or receive calls, no data, etc." Get the phone back and I find it completely locked so no way to get in. I factory reset and find that indeed it says "no service" looking deeper I find that the IMEI field in the phone data is empty. A couple of questions, Would a failed, improper or otherwise botched unlock attempt wipe the IMEI? Would a root attempt? Can the IMEI be re-assigned to the device? If so by what method? The original IMEI is still on the device as well as the original box. The bootloader was unlocked using the HTCDEV tool and worked fine. Thanks in advance!! :fingers-crossed:
Related
Hi there, I think I may have messed the phone up a little, such as this MMI error message which comes up so I can't use speeddial, or any other # code for that matters, also I can't disable call forwarding, and a few other things.
This must have been the result of rooting, etc. Is there an easy way to get my phone back to how it was (basically how it would be straight from the manufacturer, no root at all, just exactly how it was when I first bought it brand new?), bearing in mind I have also flashed it 3 times?
Cheers.
it might help if you said what you flashed it with? Details.
But if you are just wanting to flash back to stock, here:http://forum.xda-developers.com/showthread.php?t=1075278
Read, and follow the instructions. They are very clear.
stoney73 said:
it might help if you said what you flashed it with? Details.
But if you are just wanting to flash back to stock, here:http://forum.xda-developers.com/showthread.php?t=1075278
Read, and follow the instructions. They are very clear.
Click to expand...
Click to collapse
"Hi there, I first of all rooted my previously straight out of the box T-Mobile Samsung Galaxy S2 using the xwkdd_insecure.tar (with Odin and SuperOneClick - I am a complete noob by the way, but this seemed to work after I followed a YouTube video), so that I could then unlock it to use 3 Mobile (in the UK) which I am on - I had bought this phone brand new and sealed from eBay (someone's unwanted upgrade). I then went on to using the free ChainFire sim unlock app, however I soon discovered that after all my phone can't have been locked in the first place as I just got a 00000000 code, never had to enter that and my sim worked having not previously tested it... Then I went on to flash it by using this file first - I9100XWKE7_StockKernel.tar - after seeing another YouTube video to purely debrand it but this only got rid of the yellow ! logo which appeared after rooting it, that is all.
So I then went on to using this method http://forum.xda-developers.com/showthread.php?t=1064894
in order to debrand it of all T-Mobile stuff, such as the T-Mobile logo and trademark tune which came on after switching the phone on, and get it like a standard sim free/factory unlocked phone if you know what I mean. I used this file as mentioned in the link - I9100XWKDD_I9100XXKDH_I9100XEUKD1_HOME.TAR
The latter part of the guide goes on to entering #272*<IMEI># or something like that, but I have tried that all of the other alternatives and all I get is "USS code running" and like 2 seconds later the error message
"Connection problem or invalid MMI code" appears. I basically can't enter anything in my phone dial with # or * or whatever. What is wrong?
I have also noticed that whenever I call someone a message saying "Conditional call forwarding active" appears, but then proceeds to make the call okay. I have tried to disable and fiddle around with the call forwarding settings, phoned my network provider, but again, error messages come up.
What exactly is wrong and how can I fix it - I am a bit of a noob with all this....? It is surely something to do with all that stuff I have mentioned. Please help me as I honestly don't know how to go about fixing this. What is the most straightforward thing to do which will stop these messages?
Last of all, I flashed using the following, my phone seemed to be auto-rooted as I never had to root again? I9100XWKE7_I9100XXKE4_I9100XEUKD1.tar
Thanks in advance."
Friend of mine gave me a Droid Razr from Rogers to try and fix. Phone would constantly reboot, but not at a specific interval. This all happened while it was on stock firmware. No upgrade available from Rogers, so I couldn't try that, plus factory reset/wiping cache didn't work either. Friend said I should do whatever possible, so I flashed the "The Artic" ROM. Everything works perfectly. No reboot, nothing.
It is a Rogers phone, and I need to unlock it, and when I put in the microSIM from a different provider, nothing comes up asking for SIM unlock. When I go into phone status, everything says unknown, including the IMEI.
The baseband box says unknown as well.
Anything I can do?
When I try to go *#06# the box comes up for IMEI, but it doesn't have anything on it. Corrupt IMEI?
How long ago did he get the Razr I hope he didn't get the two I returned as defective? LOL.... The two I got the first one having this random shutdown issue for some strange reason it would just turn off by itself. I can't seem to track the problem down since it was factory reset and nothing install but still did this. The second one just completely turned itself off and wouldn't come back on. The third did the same as the first but I managed to send it to Motorola for repair and they reflashed it, seems ok so far. I'm wondering if the Rogers Firmware has something to do with this?
I have no idea how long ago he got it. His warranty was out though, so Rogers wouldn't take it back.
Either way, apparently I don't have an 'EFS' folder. I used Root Explorer to check and there is nothing there.
How would I go about fixing that?
The weird thing is I can use WIFI on it. I thought it stored the WIFI addresses in the EFS folder?
Or perhaps Motorola phones don't have EFS folders. Anyone?
Did a factory reset, no EFS folder.
Originally when I got the phone, before I flashed any kind of ROM I put in a foreign SIM card and the 'network unlock' box never came up.
I'm beginning to wonder if the EFS folder was gone to begin with.
Because I just checked again, and its not there. Not even after a factory reset.
Yeah, not sure what else I can do. Went back to stock 2.3.5 and installed after market radio, and both times it says unknown IMEI. I think this phone is pretty much hooped.
Hey guys,
I ran the Suckit Verizon boot unlocker exploit, and it was successful. At which point I used TW Recovery to flash Android Revolution HD 8.0 (N7100 ROM). My phone wouldn't connect to the Verizon network, saying I did not insert the proper SIM card. I found this strange, but realized Verizon locks their network to international phones. I then used the Verizon Toolkit to flash back to stock recovery and ROM. After doing so, I still had no luck in activating my phone.
I called tech support (now having stock everything) and they told me it was likely my SIM card. After spending 2 hours at the store today, it is clearly not the SIM card. They have no idea what the problem is...
When I flashed Android Revolution, I wiped my efs. Could that be the problem? Is it possible to flash a new EFS or COM3? I have no clue how to reactivate to the network..
Anyone have this problem? I did a search on both Suckit Verizon and the Verizon toolkit thread and no one appeared to suffer from this. Please help! Any solutions are greatly appreciated. Thanks in advance. Will update if those guys at Verizon come through.
Definitely has to do with wiping my EFS and not saving it. Under Settings > About > Status IMEI is unknown as well as all other carrier info.
Can someone send me their EFS or is their a way to restore the EFS without having backed it up?
Flash the full Odin restore image and that should fix the problem. Note, it will wipe your data and re-lock the bootloader, but it should at least connect to the network again.
If the stock Odin doesn't work since your imei is unknown this may be what you need, but listen to imnuts first
http://forum.xda-developers.com/showthread.php?p=36163537
Sent from my SCH-I605 (AKA NOTE 2)
kintwofan said:
If the stock Odin doesn't work since your imei is unknown this may be what you need, but listen to imnuts first
http://forum.xda-developers.com/showthread.php?p=36163537
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Flashed stock rom. No luck. Now I have to root back, as one of the prerequisites is being rooted. Will get back.
I kind of had this same problem right after I rooted/unlocked and before flashing any ROMs. I was getting signal bars but kept getting a cannot connect to network error every time I tried to place a call. I called customer service and they "reset" my account, whatever that means but it still didn't work. Started driving to the Verizon store and decided to try one last factory reset and it started working! An IT guy at my work said the account reset plus factory reset got my device sync'd with Verizon signal again. Don't know if what he said is true...don't know why it worked...don't know if this will help you but I thought I would share my experience. I know what you are going through so good luck!
Sent from my SCH-I605 using xda app-developers app
I had almost the same problem using MIUI for AT&T's variant. I was able to get most functionality back by accessing the hidden menu and doing the ##RTN#, but still cannot get 4G LTE back. Maybe this will help you get started too.
http://forum.xda-developers.com/showthread.php?p=36163537
According to the OP instructions - which I have done entirely correct. Put phone in Debugging, Went to Qualcomm settings in Hidden menu and set to "RMNET + DM + MODEM" , connected to the proper COM port, clicked the READ on top, however when I go to click the second read to populate the information -> Says cannot set device into DM mode.
The instructions and accompanied video do not reference having to place the device into DM mode at all. The fact that I am getting this error message is also a unique problem.
Anyone know what this could mean or how to fix it? Could it be due to the USB Qualcomm settings not "taking or shifting", although it does confirm that I changed by saying "Saved"
Also, can Verizon Wireless sync my IMEI in store if I bring the original box with the IMEI barcode on it ? Can they flash / scan it to the phone?
anybody?
Can Verizon Wireless sync my IMEI in store if I bring the original box with the IMEI barcode on it ? Can they flash / scan it to the phone?
I know with a fact that the stores do not carry any flashing software for any smartphones. So there is nothing they can do.
Sent from my SCH-I605 using Tapatalk 2
Hi!!:
After reading and reading and trying every method i found on the internet, i still have not succeded with my problem which is this:
I tryed to flash an stock 4.3 to my free s3 movistar chile, but when it rebooted and after i wrote the pin code, it asks me for an unblock sim code
It presented signal but uknown network. I got back to 4.1.2 thinking that it should repair this, but no, it was worst, i got imei null,
After searching and searchingI found a cwm 3 files patch on the internet: one for cleaning kernel, other one to install kernel and the other one to install modem, and with it i got my imei back, (this is when i made efs backup, i know i sould have done long before ) but also the wknown network problem, with the phone asking me for this unblock sim code again.
I used galaxysim unlock to try to repair this, but it showed me that the phone is totally unlocked i think i remember it also showed me the state of csc and it appeared blocked, so i think this is where the problem lies, but i couldnt find any info about this.
when i go to state of the phone i see this
network: uknown
kind of network: umts
service state: out of service
mobile network state: disconnected
imei:3537.... thats ok, fits with the one on the back of the phone
device state: modified
(sorry if my einglish is not very accurate)
So resuming: my imei number is ok, wifi works ok, but even though the phone shows signal, it presents uknown network, and i cant do or receive calls.
i would be very thankful if any of you could help me
Your phone was unlocked using a crack that only worked on 4.1, by updating to 4.3 you've corrupted the efs folder.
You now need to buy an unlocking code and pay for a repair, make sure it works on 4.3 before you accept the phone back.
boomboomer said:
Your phone was unlocked using a crack that only worked on 4.1, by updating to 4.3 you've corrupted the efs folder.
You now need to buy an unlocking code and pay for a repair, make sure it works on 4.3 before you accept the phone back.
Click to expand...
Click to collapse
Thanks a lot for answering!. So, if the phone was cracked in 4.1.1, is there any chance to downgrade to that version, use the corrupt efs backup that i have, just in case i lose the imei, and try to unlock?, or would be too risky?
Not without a backup of the efs before you upgrade, no.
Okay,where do I start.
So I bought this phone off a friend of a friend(I was going to sell it on for profit as it was a good deal).
I noticed when trying to update that it was telling me it was an unauthorised software, so i took it the device was rooted.
I then factory reset the device to see would it go back to factory settings, but just stayed on the custom firmware.
I then decided to flash stock firmware onto the device from Sammobile (device boots up with Three logo so I assumed it was with Three Ireland network so that's the firmware I chose.
After flashing the device it boot up with a dm verity error and would only go as far as the Three logo. After some research I found a discussion and followed the steps in this, flashing a file called CF-Auto-Root-zerolte-zeroltexx-smg925f. After doing this the dm verity error had gone and the phone booted up fine.
I left the phone like this, as I was going to sell it at a later date. Before I sold it I had one last test of the device and noticed it would not connect to a mobile network (I don't think this issue was there when I first got the phone as I am nearly sure I tested my sim card in it, but cant be sure). I just kept getting 'not registered on network' error.
After some more research I downloaded the Samsung info app and ran it. I then noticed a few strange things.
1). The serial number of the device was just showing up as a string of 0's.
2). The imei number that was listed did not match the imei on the back of the phone.
3). The carrier was showing as O2 UK, but Im not sure if this is an issue as O2 and Three are basically the same network here in Ireland (Three took over O2 here).
After doing an imei check, I found the imei listed on the back of the phone to be fine and was showing all the right details, serial number etc. But the imei that was listed as the imei of the phone, in settings and using *#06# was showing up as not existing.
I found this very strange and I'm sure this has something to do with why it can't connect to a network.
Any suggestion on getting this device back working properly as it is just a paperweight now as it is, and after spending money to buy it so I could sell it on I don't want to have wasted that money for nothing.
Any help is appreciated.
Thanks
Nothing? ?