Okay bear with me here. I received my phone back in August and it was working just fine up until two weeks ago when I got lazy and didn't want to wait for the OTA update 44s so I downloaded the zip file and flashed it. Everything seemed to be working fine because I could make phone calls out and texts so I assumed all was good.
This however was not the case. I can no longer receive incoming calls or texts. Here are the things I have done: Went up to my cell carrier( Metro Pcs) had them put in a new sim card and that didn't work. They reset my APNs still nothing. So I went home and I decide to get the OnePlus root toolkit and take my phone completely back to how it was when I first got it. All the way back to 22Q, which I did. Then, I let it update over the air all the way to 44s stopping and checking each update to see if I could get texts or calls and I couldn't. I had recently installed google voice about the same time this started but took it off the phone, even went into privacy settings and turned on privacy gaurd for all of cm11s voice+ functions even though I most likely didn't need to with google voice removed.
I also did the *#*#4636#*#* and rest my smsc number and then hit update and still nothing. Many calls to Metro Pcs and they tell me it's a device issue. Why can I make calls out and send texts just fine but I can't receive anything? Any ideas will be appreciated. I've done all I know to do unless it's a something with the radio file that got corrupted by I would think it wouldn't work at all or intermittently.
Thanks, Theo.
Haze you done a full wipe and flashed the fastboot images?
Transmitted via Bacon
timmaaa said:
Haze you done a full wipe and flashed the fastboot images?
Transmitted via Bacon
Click to expand...
Click to collapse
I've done a factory reset, then I used the OnePlus root tool kit and in fastboot mode and put my phone back to how it came out of the box 22Q . Now by full wipe, wouldn't my doing a factory reset or wiping through the OnePlus root took kit qualify as a full wipe? I was told not to wipe the internal storage, just wipe everything else.
theog72 said:
I've done a factory reset, then I used the OnePlus root tool kit and in fastboot mode and put my phone back to how it came out of the box 22Q . Now by full wipe, wouldn't my doing a factory reset or wiping through the OnePlus root took kit qualify as a full wipe? I was told not to wipe the internal storage, just wipe everything else.
Click to expand...
Click to collapse
You can't trust toolkits to do a job properly. In my guide thread (link in my signature), in section 8, there are instructions to flash the fastboot images. You can do it with or without wiping the internal storage, but I'd be wiping the internal storage to make sure it's completely fresh.
Transmitted via Bacon
timmaaa said:
You can't trust toolkits to do a job properly. In my guide thread (link in my signature), in section 8, there are instructions to flash the fastboot images. You can do it with or without wiping the internal storage, but I'd be wiping the internal storage to make sure it's completely fresh.
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah I was wondering if maybe something got corrupted. I'll check it out. Thank you for your replies by the way.
timmaaa said:
You can't trust toolkits to do a job properly. In my guide thread (link in my signature), in section 8, there are instructions to flash the fastboot images. You can do it with or without wiping the internal storage, but I'd be wiping the internal storage to make sure it's completely fresh.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay, I tried everything exactly the way you explained. I used fastboot commands to wipe my phone and install 44s. Then I installed TWRP and re rooted. The same damn thing is happening. I've heard others having the same issue as me. I took a picture for you when was I was in the *#*#4636#*#* prompt. I ran a ping test on my phone and oddly enough it came back : Fail: IP Address Not Reachable. My wifi was on and so was my data and im on my laptop now and it works fine. I read somewhere someone else said soemthing about the modemfs getting corrupted? I know this happened after I flashed 44s without waiting for the update. So damn frustrating.
Picture is down below.
theog72 said:
Okay, I tried everything exactly the way you explained. I used fastboot commands to wipe my phone and install 44s. Then I installed TWRP and re rooted. The same damn thing is happening. I've heard others having the same issue as me. I took a picture for you when was I was in the *#*#4636#*#* prompt. I ran a ping test on my phone and oddly enough it came back : Fail: IP Address Not Reachable. My wifi was on and so was my data and im on my laptop now and it works fine. I read somewhere someone else said soemthing about the modemfs getting corrupted? I know this happened after I flashed 44s without waiting for the update. So damn frustrating.
Picture is down below.
Click to expand...
Click to collapse
did you do the following commands in fastboot?
fastboot erase modemst1
fastboot erase modemst2
---------- Post added at 08:47 AM ---------- Previous post was at 08:30 AM ----------
theog72 said:
Okay, I tried everything exactly the way you explained. I used fastboot commands to wipe my phone and install 44s. Then I installed TWRP and re rooted. The same damn thing is happening. I've heard others having the same issue as me. I took a picture for you when was I was in the *#*#4636#*#* prompt. I ran a ping test on my phone and oddly enough it came back : Fail: IP Address Not Reachable. My wifi was on and so was my data and im on my laptop now and it works fine. I read somewhere someone else said soemthing about the modemfs getting corrupted? I know this happened after I flashed 44s without waiting for the update. So damn frustrating.
Picture is down below.
Click to expand...
Click to collapse
Also you mentioned in the OP you had google voice setup then uninstalled it. I'm not all that familiar with google voice, but is there a chance you had it set up to receive your calls/sms and, even though it has been uninstalled, it is still intercepting your calls and sms?
What happens when people call you? Does it go to voicemail or what?
BladeRunner said:
did you do the following commands in fastboot?
fastboot erase modemst1
fastboot erase modemst2
---------- Post added at 08:47 AM ---------- Previous post was at 08:30 AM ----------
Also you mentioned in the OP you had google voice setup then uninstalled it. I'm not all that familiar with google voice, but is there a chance you had it set up to receive your calls/sms and, even though it has been uninstalled, it is still intercepting your calls and sms?
What happens when people call you? Does it go to voicemail or what?
Click to expand...
Click to collapse
When I call my cell from my house phone I get the voice error message: DTE 01. I looked this up online and this means usually that your cell phone is not paid or there is no service. This cannot be because by bill is paid and I was on the phone with my carrier constantly since this started around Novemember 20th or so. They had their tech people look into what I've been telling you on here and they can't figure it out. I can also send sms to my brother on metropcs and he gets them but my mom who is also on metro pcs doesn't.
I took google voice completely off of my phone because I had read on these forums that others had similar issues when they installed google voice. Something to do with when google voice is installed it activates VOICE+ within Cm11s and if you don't disable it that is why it takes over all of their sms and voice calls. I uninstalled it in the past and disabled voice+ in my privacy guard settings and this was still occurring.
Anyways, I just did the complete wipe the way you said it should be done and re installed 44s, TWRP and Re-rooted. Google voice isn't even on my phone right now. I may trying getting a new cell account, closing out this one and see if that works because it's totally bizarre that I can make phone calls out and send texts to my brother but I can't get any incoming calls or texts. Some one else suggest modemst 1 and 2 through fastboot? Doesn't a complete wipe and install repair all the partitions and then put a fresh install of the rom on there? So I would think the radio files and all of that would be okay? I don't know I'm your basic Android user.
I didn't try the fastboot erase modemst1/ fastboot erase modemst2 . Wouldn't a complete wipe address this?
Thanks again for your reply, Theo.
Edit 12/2/2014 : Problem resolved!! I went and had my account closed on my original number opened a new account with the same carrier and got a new number and new sim card and now everything is working perfectly. The representitives at MetroPcs are clueless. Kept trying to tell me it was my device. The problem was on THEIR end. Thanks to those who replied.
Related
Hey,
Starting this thread up as a place to figure out the "Preparing Sim Card" problem.
Essentially, if you flash CleanROM 4.1 with CWM, you'll probably get this error. There were plethora of fixes out there, such as:
1. Clearing all cache (fastboot/recovery)
2. Clearing all data/force stopping problem apps (people/dialer/messaging)
3. RUUing back to stock
4. Flashing a new radio
5. Removing/Changing SIM cards
6. Trying dialer trick:
.....a. Go to Dialer (if you can't access it, clear the data in it first)
.....b. dial *#*#4636#*#*
.....c. Turn off the radio
.....d. Turn on the radio, and right as the toast appears, choose something from the drop down menu.
.....e. Run a ping test to make sure everything's alright.
7. Used TWRP to clear system/flash new ROM
8. Tried another ROM with GSM Patch
CURRENT STATUS: WORKING!!!! =D
The answer to all your problems issss........
Well, it's multi-step
1. Make sure to flash back via RUU (preferably 1.82 since 1.85 was a b**** for me to re-root T_T)
2. Make sure to unlock your bootloader again
3. Install back CWM (I know...wtf?!) <<THIS STEP IS IMPORTANT (believe it or not)
4. Go back and flash CleanMOD 3.1 or something (just anything below 4.1 should do the trick) [if just installing CleanMOD doesn't work, install the GSM Patch too!]
5. NOW install TWRP
6. Install CleanMOD 4.1
7. SUCCESS!!!
Also, thanks to tehdef, who also tried this method:
Here is what I did to break my phone.
I had the following MODS.
-AOKP 6.1
-CWM
Decided I wanted to test something on CleanROM 4.1
- Flashed CR4.1 in CWM
Got stuck in Boot Cycle and CWM would not load
1. Locked Bootloader
2. Installed 1.85 Evita RUU
3. Unlocked Bootloader
4. Installed TWRP
5. Flashed AOKP 6.1
At this point, I still had an issue. Instead of receiving the "Preparing SIM" Message, I had absolutely zero signal, and I could not "SAVE" an APN.
6. Rebooted to Bootloader
7. Reset to Factory while in AOKP
8. TWRP Loads
9. Reboot to System
My phone now has signal and full contacts and I can make calls and send Texts and MMS with no additional modifications. Please note that with AOKP Superuser comes installed and works just fine, so for whatever reason I did not have to root my device.
NOTE: YOU DO NOT NEED TO USE CLEANROM 3.1 IN ORDER TO GET BACK TO A WORKING STATE!!! Just any rom supporting the unofficial CWM should do. =] (at least I think so, but I'll confirm when someone get's back to me =D)
Thanks goes out to...
Scott for his awesome ROMs and his life lessons
kleeman7 for toughing it out and helping me through the entire thing
tehdef for helping me test out several of my theories
shackman716 for suggesting the idea that worked (it was so crazy it actually worked! XD)
and thanks goes out to anyone I forgot to mention. XD
Now, back to more ROM flashing
scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?
redpoint73 said:
scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?
Click to expand...
Click to collapse
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Error 170 is a usb communication error and is fixable. Turn off HTC sync. Check for it in running processes. If you still get the error reboot to the bootloader make sure the phone says fastboot usb in red then start the ruu.
tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
thats a driver error do u have htc drivers installed? good usb cable? tried a diff slot?
if not install htc sync let the first portion install. when it comes time for htc sync inself to install cancel. and just the drivers will be installed
tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".
I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync
elsupermang said:
I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync
Click to expand...
Click to collapse
Well, I tried emailing and stuff, and it seems anything regarding data seems to be alright. It just seems to be the issue with phone/sms data now. I believe it's something software related as it still reads my sim just fine, and it recognizes when it gets a call. Just when I get a call, it repeatedly FCs. I might give it a try though, so thanks!
redpoint73 said:
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".
Click to expand...
Click to collapse
Sorry, I had to go out for lunch, so I didn't really go into much detail. I have tried using TWRP and is still using that atm, and also tried flashing a rom with GSM Patch, which I'll edit the OP to match. Both of these did not work and I'm going to try and pull a logcat or something. Will update when I get it
Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.
tehdef said:
Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.
Click to expand...
Click to collapse
i feel like the dialer and the contacts are linked together. if we can solve one, we can probably solve both. I looked in my catlog and they stated that they couldnt find a particular file/db in the /data/data folder. ill look into this and see what happens
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Well, hopefully that's it.
---------- Post added at 01:12 PM ---------- Previous post was at 01:06 PM ----------
kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
I haven't unlocked my BL again because I'm at home, and frankly, I'm not sure how the process is changed once I already ahve the Auth Key, and if I can do it quickly here from work.
kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything
jojojohnson7410 said:
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything
Click to expand...
Click to collapse
Try flashing AOKP + GApps to see if the People vs Contact system is diff?
tehdef said:
Try flashing AOKP + GApps to see if the People vs Contact system is diff?
Click to expand...
Click to collapse
That's a good idea, maybe once Scott reads his thread he will have some input for everyone.
Sent from my HTC One X
Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
...actually, tehdef, did you ever unlock your bootloader with the one-click without HTCDEV unlock at any point in time? This might help me out cause this might also be the problem. Thanks!
jojojohnson7410 said:
Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
Click to expand...
Click to collapse
Clearing contacts seems to work. My list is now populating.
Attempted to send text. Prepairing SIM Card returns.
---------- Post added at 02:23 PM ---------- Previous post was at 02:12 PM ----------
Unfortunately the Android.acore process has stopped when I tried to sync my Gmail contacts after clearing everything.
I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?
Something is corrupt.
I want to put AOKP back on the phone, because I honestly think it's Sense related.
natediddydude said:
I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?
Click to expand...
Click to collapse
lol at the shaking your phone really hard XD
Anyways, I have a theory:
there are two ways we COULD possibly fix this:
1. obtain a rom that has root. Get root explorer or somehow get into /data/data/com.android.providers.contacts/databases/ and delete .db-journal if its in there. Do this in conjunction with clearing out the data of all the affected apps and their sister apps (i.e. Contacts, Contacts Storage, Contacts Sync) and force stopping all of them. Can't test this cause bootloader refuses to unlock atm)
2.lock the bootloader, RUU to 1.82 (NOTE: NOT 1.85!) and try to unlock using this: http://forum.xda-developers.com/showthread.php?t=1734558. REMEMBER take out your SIM card! but maybe this might help not 100% sure if this is what caused it for me, so it's best to consider it too. Can't test this right now because I am stuck without a BL unlock and i can't get root on this firmware
*EDIT* ahahhahahah i lied. no sim card needed, so why would it rely on mobile data? ahh im such a silly person alright here goes!
i'll let you know when i get out of my pickle, but it might be a while. That, or i might just get pissed off enough to just go to the store and look like an idiot cause i really do feel like one right now and I need to get the phone working T_T
Keep checking back!
SOLVED! see solution in the first comment.
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.
hbhc123 said:
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.
Click to expand...
Click to collapse
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.
Synyster06Gates said:
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.
Click to expand...
Click to collapse
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.
hbhc123 said:
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.
Click to expand...
Click to collapse
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.
clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.
chi_heng said:
clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.
Click to expand...
Click to collapse
Flash the newest version of TWRP. The issue is fixed.
Synyster06Gates said:
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.
Click to expand...
Click to collapse
I have done what you said and it worked perfectly
many thanks!
hbhc123 said:
I have done what you said and it worked perfectly
many thanks!
Click to expand...
Click to collapse
No problem! Glad you got it taken care of.
What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.
any one else
benbailey84 said:
What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.
Click to expand...
Click to collapse
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks
ddloco said:
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks
Click to expand...
Click to collapse
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).
benbailey84 said:
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).
Click to expand...
Click to collapse
Well in our case I have my efs on my PC from weeks ago restoring it doesn't fix whatever the ROM changed lol
I am a noob here. I am experiencing two main issues with a Boost Moto G (XT1031) that I am trying to flash to PP. It came with KK version 4.4.2. After I unlocked the bootloader and followed all the steps described on http://forum.xda-developers.com/showthread.php?t=2681166 to reset SPC to 000000, I flashed the stock US verizon firmware on it.
Problem-1:
The phone rebooted fine and even got upgraded to 4.4.4 over wifi. Even though the phone is showing that it is on verizon network (strong signal) and everything seems to be fine at the PP end, I cannot make or receive text or calls. I am totally lost. Any help will be appreciated.
Everything went fine till I flashed the CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip firmware. It gave me errors when I loaded the boot.img, recovery.img, mfastboot flash system system.img_sparsechunk1 and mfastboot flash system system.img_sparsechunk4. I followed the instructions for flashing 4.4.2. They were different errors and I was manually entering each command line (copy-pasted). I also checked the file names in the folder and they matched. I couldn't figure out why I was getting the error. The MD5 matched too, so that rules out the fact that the files were corrupted. After reboot, the system loaded up ok, but the OTA failed. I used the manual programming and *22890 to get it activated. I got the "congratulations, your device is active" message. However, any time I tried to make a call, I get the error saying, "your phone# is either not active or invalid". I called PP and they confirmed the MEID on my phone and the one in their system are the same and nothing is wrong at their end. They were even able to make a call from this number. One of the dealers at Kittywireless told me that it might be an issue with the authentication key. I saw no mention about this in the tutorial or in any of my searches on this forum. What am I doing wrong? Any help will be appreciated.
Problem-2:
Also my phone is an 8GB phone (shows that info on the fastboot menu on the phone & also in the bug report (attached)), but in the storage info section of the phone it is showing only 5.52 Gb as the total internal storage. When I flashed the phone, I also erased the userdata. Any safe way to wipe the phone and load up everything? How do I get back the lost space?
I am attaching a bug report that I generated using ADB tool. It seemed really long for a phone that was just activated. I am hoping that someone on this forum might have encountered the problems that I mentioned above before and figured out a way to fix them. I'd appreciate if you can share it. Thanks.
greenlantern2014 said:
I am a noob here. I am experiencing two main issues with a Boost Moto G (XT1031) that I am trying to flash to PP. It came with KK version 4.4.2. After I unlocked the bootloader and followed all the steps described on http://forum.xda-developers.com/showthread.php?t=2681166 to reset SPC to 000000, I flashed the stock US verizon firmware on it.
Problem-1:
The phone rebooted fine and even got upgraded to 4.4.4 over wifi. Even though the phone is showing that it is on verizon network (strong signal) and everything seems to be fine at the PP end, I cannot make or receive text or calls. I am totally lost. Any help will be appreciated.
Everything went fine till I flashed the CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip firmware. It gave me errors when I loaded the boot.img, recovery.img, mfastboot flash system system.img_sparsechunk1 and mfastboot flash system system.img_sparsechunk4. I followed the instructions for flashing 4.4.2. They were different errors and I was manually entering each command line (copy-pasted). I also checked the file names in the folder and they matched. I couldn't figure out why I was getting the error. The MD5 matched too, so that rules out the fact that the files were corrupted. After reboot, the system loaded up ok, but the OTA failed. I used the manual programming and *22890 to get it activated. I got the "congratulations, your device is active" message. However, any time I tried to make a call, I get the error saying, "your phone# is either not active or invalid". I called PP and they confirmed the MEID on my phone and the one in their system are the same and nothing is wrong at their end. They were even able to make a call from this number. One of the dealers at Kittywireless told me that it might be an issue with the authentication key. I saw no mention about this in the tutorial or in any of my searches on this forum. What am I doing wrong? Any help will be appreciated.
Problem-2:
Also my phone is an 8GB phone (shows that info on the fastboot menu on the phone & also in the bug report (attached)), but in the storage info section of the phone it is showing only 5.52 Gb as the total internal storage. When I flashed the phone, I also erased the userdata. Any safe way to wipe the phone and load up everything? How do I get back the lost space?
I am attaching a bug report that I generated using ADB tool. It seemed really long for a phone that was just activated. I am hoping that someone on this forum might have encountered the problems that I mentioned above before and figured out a way to fix them. I'd appreciate if you can share it. Thanks.
Click to expand...
Click to collapse
try flashing stock rom
I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"
AxelWexel said:
I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"
Click to expand...
Click to collapse
Can't find your video, can you paste the link as text?
gsmyth said:
Can't find your video, can you paste the link as text?
Click to expand...
Click to collapse
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it
AxelWexel said:
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it
Click to expand...
Click to collapse
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
gsmyth said:
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
Click to expand...
Click to collapse
Thx for the Links and i tried to watch on my phone and there is no imei number. I also did a full wipe after i found the issues. I also tried it via the Toolbox to flash the stock rom back but it hadnt change anything. But I will look the links you postet and reply if anything has changed. But now thx again:good:
P.S: I renamed the Video to "Oneplus One not working (23.06.2015)" to find it more easily
Edit 1: The Second Link with fixing corrupt partitions via adb wont work for me because i dont have root but my bootloader is unlocked. so i cant find the root acsess for adb in the developer options
Edit 2: I installed color os like the link said, done everything it said, but still no wifi, bluetooth and no sim card detection:crying:. Luckily the random reboot stopped Could you again help me further more because it seemed to help
Edit 3: I went back to cm11s, because in color os when i turned the phone off it turned on again, the connectivity was not there. After the install it became worse with the random reboots. I think i must send it to repair and pay 300€:crying::crying::crying::crying:
>> Partial solution was found; still looking for the root of the problem. <<
I recently decided to take the plunge and root my OnePlus One and install sultanXDA's CM 13 ROM on it. It was all going well until I booted up into the ROM and discovered that I couldn't get any mobile data. Everything else was working, calling, texting, wifi, but mobile data seemed to refuse to work. Since I initially flashed sultan's ROM with TWRP 3.0.0, I suspected it was a problem with my modem. Though unable to install TWRP 2.8.6.0 to re-flash everything, I did still flash a new modem via ADB. This didn't help.
I have tried many things to fix this. I rebooted/reflashed. I flashed different ROMs. I tried flashing on TWRP 2.8.6.1, though I believe that one has the same modem problem as the versions after it. As mentioned above I tried flashing a modem over ADB. I took out and re inserted my SIM card. In the end, I tried this guide here to restore my phone to it's original state. The guide flashes the stock versions of everything via ADB. Though it did return me to unrooted COS 12.1, it was not able to resolve my data problem.
After the total reset, all I can think that could be causing it is a hardware problem or that it is caused by something not reset in the 100% restore above.
If any of y'all can help my solve this, or at least offer insight, I would be very grateful.
Preemptive Edit I Guess: This thread was just suggested to me while writing this. I'm going to try the solution here and report back. It's OnePlus' reset to stock method. I'm not expecting much after my first 100% reset attempt, but we'll see.
EDIT: Ok, so the solution above fixed my problem... (edit again: turned out to only be a partial solution. See below.)
I would feel really dumb right now if it weren't for the fact that I slaved over this problem for a good ~8 hours before writing this post. Anyways, I'm not sure how to delete this post or mark it as solved. Sorry for the trouble y'all.
Never delete this post !!
I have the same problem, and I spent much more time to find a solution.
I will try this and will update.
Is it a clean stock rom?
Edit:
Didn't help for me ..
Still the same problem, No mobile internet connection.
Thx anyway.
Yeah, actually I was too hasty is identifying this as the solution. For me, the stock reset brought me back to CM 11 which didn't have a problem with mobile data. But if I try to flash a later ROM or update via OTA, the problem returns. I'm still trying to figure out what is causing it. The only information I can find points to it being a modem problem or APN problem, but I'm sure I have sufficiently checked both of those already.
Either way, I'll keep looking. If I find something I'll return here with it. Good luck
arkasa said:
Yeah, actually I was too hasty is identifying this as the solution. For me, the stock reset brought me back to CM 11 which didn't have a problem with mobile data. But if I try to flash a later ROM or update via OTA, the problem returns. I'm still trying to figure out what is causing it. The only information I can find points to it being a modem problem or APN problem, but I'm sure I have sufficiently checked both of those already.
Either way, I'll keep looking. If I find something I'll return here with it. Good luck
Click to expand...
Click to collapse
Try this:
1) Download the latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
2) Go here and follow step #8: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
3) Then follow step #2 to install a new recovery (you need to make sure to use TWRP 3.0.0 or the unofficial TWRP if you want to flash modems/firmwares correctly)
4) Download the latest ROM of your choice and install via your recovery
ryanmat said:
Try this:
1) Download the latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
2) Go here and follow step #8: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
3) Then follow step #2 to install a new recovery (you need to make sure to use TWRP 3.0.0 or the unofficial TWRP if you want to flash modems/firmwares correctly)
4) Download the latest ROM of your choice and install via your recovery
Click to expand...
Click to collapse
I gave this a try, but booting up after step 3 I still had the same problem. If I understand this method correctly, I think it is essentially the same as the other full restore methods I tried.
I think I may have found the problem though. I was looking at OnePlus' guide to installing OxygenOS. In it they said, "do not try to flash this build through TWRP. You will most likely lose your radio and IMEI which means a trip to our customer support." At this point I have repeatedly reset/restored my modem/radio so I don't think that is the problem, but I haven't seen anything about IMEI before. The IMEI is apparently stored in the EFS partition which as far as I can tell, is not touched by any of the restore methods I have tried. I took a look at my IMEI (about phone -> status) and it turns out my IMEI SV is 00. It's supposed to be a 16 digit number. I found a guide to fixing it, but I think I will just contact OnePlus customer support first.
I'll be back later with my results.
arkasa said:
I gave this a try, but booting up after step 3 I still had the same problem. If I understand this method correctly, I think it is essentially the same as the other full restore methods I tried.
I think I may have found the problem though. I was looking at OnePlus' guide to installing OxygenOS. In it they said, "do not try to flash this build through TWRP. You will most likely lose your radio and IMEI which means a trip to our customer support." At this point I have repeatedly reset/restored my modem/radio so I don't think that is the problem, but I haven't seen anything about IMEI before. The IMEI is apparently stored in the EFS partition which as far as I can tell, is not touched by any of the restore methods I have tried. I took a look at my IMEI (about phone -> status) and it turns out my IMEI SV is 00. It's supposed to be a 16 digit number. I found a guide to fixing it, but I think I will just contact OnePlus customer support first.
I'll be back later with my results.
Click to expand...
Click to collapse
Are you flashing each of the extracted .img files from fastboot, exactly like the guide shows, or are you doing something else?
ryanmat said:
Are you flashing each of the extracted .img files from fastboot, exactly like the guide shows, or are you doing something else?
Click to expand...
Click to collapse
Yep, I ran each command listed in the guide and my phone was definitely in fastboot. Each command had a collections of "OKAY"s and ended with a "finished", which I assume means it executed as expected.
I have tried 2 different sim cards in my OPO (of two different companies, one of them as mine), and mobile data worked perfectly. Is it possible that my phone is ok and the problem happened in the sim card?
AND... my IMEI SV is 00 too. please update here if it has a connection.
Thank you !
omersa99 said:
I have tried 2 different sim cards in my OPO (of two different companies, one of them as mine), and mobile data worked perfectly. Is it possible that my phone is ok and the problem happened in the sim card?
AND... my IMEI SV is 00 too. please update here if it has a connection.
Thank you !
Click to expand...
Click to collapse
I'm not entirely sure what you're saying. Did it not work with the first SIM card, but it worked with the second?
Mobile data problem was occured (to me), after I rooted my OPO and tried to flash a new rom.
I still can't understand how it convinced my sim card, but the fact is that I tried two (to be sure) other sim cards which are not mine, and mobile data worked well.
When I returned my original sim card, problem started again.
So I am almost sure that sim card has a connection, but can't understand why. And why it happend precisely now, cause it worked well over two years.
omersa99 said:
Mobile data problem was occured (to me), after I rooted my OPO and tried to flash a new rom.
I still can't understand how it convinced my sim card, but the fact is that I tried two (to be sure) other sim cards which are not mine, and mobile data worked well.
When I returned my original sim card, problem started again.
So I am almost sure that sim card has a connection, but can't understand why. And why it happend precisely now, cause it worked well over two years.
Click to expand...
Click to collapse
sorry to intrude...but looks like mine problem too...but no connection with provider at all...and it worked 1 month normal (stock opo)..
could u flash the modem to resolve this problem?
jpvr
http://forum.xda-developers.com/one...e-plus-one-t3030545/post65841063#post65841063
Why don't you flash twrp flashable modem?
If your network is present but no data , mostly data service problem. Are you pay your mobile bills ?
Are you activate data services ?
Try this
https://www.androidfilehost.com/?w=files&flid=28032
drmuruga said:
Why don't you flash twrp flashable modem?
If your network is present but no data , mostly data service problem. Are you pay your mobile bills ?
Are you activate data services ?
Try this
https://forums.oneplus.net/threads/cos-12-master-fix-thread.307446/
Click to expand...
Click to collapse
...yes i paid my bills ..
- my network connection to provider is dead...it worked perfecly for 1 month out of the box (see original posting for detailed action i took) this thread is about lack of data connection...but also MODEM related???
- tried the brand new simcard in my old Samsung sII... works perfetly, network connection with provider, data connection and calling..so no simcard problem
Long shot. Change any APN settings from IPv6 to IPv4. That was my problem when I had text/voice but no data.
I made a post on this and then called att gophone, due to seeing other sims working on this thread, and he helped me to fix. Posting my fix here in case others with isue find this post instead of mine.
Turned off wifi.
Turned off cellular data.
Went to APN and changed the apn (ATT Go Phone) from pta to nxtgenphone.
Turned on cellular data.
Finally had H+ above he signal bar, but had an X inside the bar.
Don't know if he did anything on his end, but the X went away after a couple of minutes.
Data was working, albeit kinda slow.
Turned off phone for three minutes per ATT rep.
Rebooted.
Data still slow, but it is at least working. Thinking I need to flash different modem. Battery usage has been higher the last day or two since I flashed c7 anyways.